Activity
From 03/28/2025 to 04/26/2025
04/25/2025
- 08:33 PM Feature #9942: syntax for tree structure defintion and usage as templates or for pattern matching
- We have a mechanism for implementing templates in TRPL v1, using the @TemplateWorker@ (TW). The idea is that the TW ...
04/24/2025
- 04:27 PM Feature #9942 (New): syntax for tree structure defintion and usage as templates or for pattern ma...
- 04:03 PM Feature #9941: natural/integrated scoping for resources
- Today we use the @DictionaryWorker@ to implement scoped dictionaries. This allows us to explicitly push/pop state ba...
- 03:35 PM Feature #9941 (New): natural/integrated scoping for resources
- 03:34 PM Feature #9940: array syntax for referencing parent, child or sibling nodes
- It is common to use chaining to reference parent nodes. Instead of @copy.parent.parent.parent@ or @copy.getAncestor(...
- 03:28 PM Feature #9940 (New): array syntax for referencing parent, child or sibling nodes
- 02:10 PM Feature #9938: property syntax for annotations
- Something else to mention: we allow @node.getAnnotation(someVar)@ (and put/is), especially from TRPL functions I thin...
- 02:09 PM Feature #9938: property syntax for annotations
- > for the @this.name@ syntax, the @name@ must not collide with a @Aast@ getter method (as we can do a @node.firstChil...
- 01:09 PM Feature #9938: property syntax for annotations
- Greg, a few caveats:
* for the @this.name@ syntax, the @name@ must not collide with a @Aast@ getter method (as we ca... - 01:04 PM Feature #9938: property syntax for annotations
- In TRPL 1.0, annotations are "second class" features. The syntax of the language itself does not provide any facilit...
- 11:51 AM Feature #9938 (New): property syntax for annotations
04/23/2025
- 09:31 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I've completed some rules testcases covering all the expression/token/tag rules I monitor. These are not loaded in *1...
04/14/2025
- 10:44 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Is @AUTOMATIC NULL CHECKING@ really only used 5 times? That is suspicious.
- 10:25 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I've committed some updates to *15800*, which include:
* Added compilation support for @<action>@ expressions. This ...
04/11/2025
- 08:30 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- The idea here is that the language features match the parser structure, not the individual tokens.
- 08:29 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Octavian Adrian Gavril wrote:
> Greg Shah wrote:
> > Also, we don't need to track @protected@ lexer rules since the... - 08:10 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Greg Shah wrote:
> Also, we don't need to track @protected@ lexer rules since they don't actually generate tokens us... - 07:57 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Also, we don't need to track @protected@ lexer rules since they don't actually generate tokens used by the parser. I...
- 07:55 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- > I assumed that if logging occurs within the @try@ block and no exception is thrown by @match()@ up to that point, w...
- 06:41 AM Feature #1745 (WIP): review, decide upon and document the 1.0 features which will be retained in 2.0
- Greg Shah wrote:
> On the other hand, @CAST@ looks wrong (there should be around 2100) and @LT@ seems wrong.
I co...
04/10/2025
- 12:09 PM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I've done some quick checking of the results. Most of the numbers look pretty reasonable, even the ones that are ver...
- 09:58 AM Bug #9835: The same rules files are loaded and compiled multiple times
- Yes, you can use 1745a.
- 09:33 AM Bug #9835: The same rules files are loaded and compiled multiple times
- I've started implementing a mechanism to prevent loading the same @.rules@ file multiple times. While analyzing @Conf...
- 02:21 AM Bug #9835 (WIP): The same rules files are loaded and compiled multiple times
04/09/2025
- 09:52 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- The table in #1745-44 was incomplete due to an issue while attempting to reformat the data into multiple tables. Apol...
04/07/2025
- 09:05 AM Feature #1745 (Review): review, decide upon and document the 1.0 features which will be retained ...
- Greg Shah wrote:
> I think we will need a custom driver that loads everything (all rule set files) and forces all co...
04/03/2025
- 08:41 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I think we will need a custom driver that loads everything (all rule set files) and forces all content to parse and a...
- 07:21 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I'm starting a new approach similar to @Expression.main()@ to compile expression rules.
- 06:33 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I tried different ways to compile expressions without any @ast@, but without success. I used @AstSymbolResolver.getRe...
04/02/2025
- 09:18 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- After some investigation, I believe the only way the TRPL expression can be compiled is by processing it together wit...
04/01/2025
- 08:11 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Greg Shah wrote:
> Please try to confirm all of your numbers using other matching techniques (even something like gr... - 07:19 AM Feature #1745 (WIP): review, decide upon and document the 1.0 features which will be retained in 2.0
- 05:56 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Please try to confirm all of your numbers using other matching techniques (even something like grep). Many of the nu...
- 04:51 AM Feature #1745 (Review): review, decide upon and document the 1.0 features which will be retained ...
- Instrumented @expression.g@, both rules and tokens, into *1745a/15796*. Now, the results look like this:
|_.Featur...
03/31/2025
- 09:25 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Greg Shah wrote:
> > Greg, what do you think about the numbers above? Also, what should I continue tracking with?
>... - 09:24 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- > Greg, what do you think about the numbers above? Also, what should I continue tracking with?
Please instrument @... - 04:32 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Octavian Adrian Gavril wrote:
> I reviewed @ConfigLoader.java@ along with [[p2j:Writing_TRPL_Rule-Sets]] and these a... - 03:08 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I've added the elements mentioned in [[p2j:Writing_TRPL_Expressions#Features|Features]] to be tracked. I've also incl...
Also available in: Atom