Activity
From 02/26/2025 to 03/27/2025
03/26/2025
- 03:05 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Greg, as you suggested in the last call, I created a new task about that performance gap described in #1745-27.
- 03:00 AM Bug #9835: The same rules files are loaded and compiled multiple times
- During a tags count in TRPL, it was found that many @.rules@ files are loaded and compiled multiple times. This sugge...
- 02:54 AM Bug #9835 (WIP): The same rules files are loaded and compiled multiple times
03/24/2025
- 11:00 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I've added some changes to avoid multiple uploads of the same @.rules@ file. The numbers seem accurate, so I hope I'v...
- 09:50 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I added another class (@TRPLFeatureTracker@) to search for all @.xml@ files and process them with the @processTrees@ ...
03/20/2025
- 02:02 PM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- > I committed the initial implementation of TRPL feature tracking system
These are interesting results. Some feed... - 01:49 PM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- > Updated the [[p2j:Writing_TRPL_Expressions#Features|Expression Features]] documentation. I added an introduction to...
- 11:00 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I committed the initial implementation of TRPL feature tracking system into task branch *1745a/15792*. I added a clas...
- 07:46 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Please, let me know if improvements are needed.
- 07:44 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Updated the [[p2j:Writing_TRPL_Expressions#Features|Expression Features]] documentation. I added an introduction to t...
03/19/2025
- 01:21 PM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Greg Shah wrote:
> > Still looking for the *Automatic Null Checking* implementation to expand its documentation.
> ... - 01:04 PM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Octavian Adrian Gavril wrote:
> Eric, is *Automatic Null Checking* related to code sections similar to this?
>
> ... - 10:26 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Yes, that works.
- 10:16 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Is it OK if I start with the items mentioned in the table in [[p2j:Writing_TRPL_Rule-Sets#Pipeline-and-Ruleset-Profil...
- 08:27 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Question from Octavian:
> Should I configure ConfigLoader and Compiler to track each .rules file/.xml file/rule-se...
03/14/2025
- 05:44 AM Feature #9770: Change annotation key type from plain string to Enum
- Ovidiu, I will be honest, I don't know. I just created a patch that prints the keys in a file, and that's it, I didn'...
03/13/2025
- 01:11 PM Feature #9770: Change annotation key type from plain string to Enum
- Radu,
I had peeked at the list you compiled. I am puzzled by something: why are there customer-specific values saved... - 07:20 AM Feature #9770: Change annotation key type from plain string to Enum
- Remove the customer-specific stuff (you can leave behind description of what was removed) and post it in #9721.
- 07:16 AM Feature #9770: Change annotation key type from plain string to Enum
- Greg Shah wrote:
> We need to post that somewhere else, it has customer table names in it. Also, this is better don... - 06:41 AM Feature #9770: Change annotation key type from plain string to Enum
- We need to post that somewhere else, it has customer table names in it. Also, this is better done in a FWD sub-proje...
- 05:04 AM Feature #9770: Change annotation key type from plain string to Enum
- Here's a list of all annotations that were identified in at least one customer application. They are already sorted i...
03/12/2025
- 01:14 PM Feature #9770: Change annotation key type from plain string to Enum
- > If the point is for TRPL to be independent of what the annotations are, can a provider for the annotations be plug...
- 11:03 AM Feature #9770: Change annotation key type from plain string to Enum
- If the point is for TRPL to be independent of what the annotations are, can a provider for the annotations be plugge...
- 10:54 AM Feature #9770: Change annotation key type from plain string to Enum
- It is an interesting idea.
Pros:
* There would be a simple way to check if an annotation name was valid.
* Pe... - 10:41 AM Feature #9770: Change annotation key type from plain string to Enum
- The main reason is the performance of the @AnnotateAst.annotations@ map - this was optimized in the past, especially ...
- 10:33 AM Feature #9770: Change annotation key type from plain string to Enum
- Because I'm currently working on gathering all annotation types (or as many as I can find), this idea was brought up....
- 10:28 AM Feature #9770 (New): Change annotation key type from plain string to Enum
03/10/2025
- 09:03 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Eric, is *Automatic Null Checking* related to code sections similar to this?...
03/05/2025
- 08:01 PM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- > Still looking for the *Automatic Null Checking* implementation to expand its documentation.
Eric: Can you please... - 07:57 PM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- > I've updated the description of the first two features from [[p2j:Writing_TRPL_Expressions#Features|Expression Feat...
03/04/2025
- 06:50 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I added some documentation for *Property Notation* feature. Still looking for the *Automatic Null Checking* implement...
03/03/2025
- 09:24 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Greg Shah wrote:
> I'm worried that these [[p2j:Writing_TRPL_Expressions#Features|Expression Features]] are not docu...
02/28/2025
- 09:53 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Octavian Adrian Gavril wrote:
> I've reviewed [[p2j:Writing_TRPL_Expressions]] along with the associated code and it... - 09:49 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Look for any location that instantiates @new PatternEngine()@. For example, in @TransformDriver.processTrees()@.
- 09:44 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- Greg, where is @PatternEngine.main@ called in order to run the entire TRPL rule-set? I saw some targets in @build_db....
- 08:46 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I've reviewed [[p2j:Writing_TRPL_Expressions]] along with the associated code and it seems fully documented to me. I'...
- 05:10 AM Feature #1745 (WIP): review, decide upon and document the 1.0 features which will be retained in 2.0
02/27/2025
- 09:09 AM Feature #1745: review, decide upon and document the 1.0 features which will be retained in 2.0
- I reviewed @ConfigLoader.java@ along with [[p2j:Writing_TRPL_Rule-Sets]] and these are some features that I found und...
Also available in: Atom