Outline not displayed/updated on error

RDP LPEX Outline will not create when opening a member that contains (in LPEX's opinion) certain types of errors. If an error is written into the source, then the outline will no longer be updated. If the source is then saved and re-opened, the existing outline is removed.

Example 1. If I use "convert all to free-form", then remove the "/end-free" and following "/free" lines, without first manually converting the unconverted line(s), the Outline is then no longer updated. If I exit the editor and re-enter, the complete outline disappears.

Example 2. Most of Infor's System21 source code contains fields beginnig with @ and in addition many of the copybook source members start with the character @. This prevents the Outline from creating. While we know that this is a CCSID issue as the source members are supplied with CCSID 37, our system is set to 273. The catch here is that the old static parser (WDSC) will still create an Outline.

Would it not be possible for the parser to just ignore those lines for the purpose of Outline creation/updating? They would still be highlighted as errors.

This, IMO, is normal everyday use. At the moment, we're either having to continually switch between using the old parser (in RDP), or having to use WDSC.

The outline is a critically important feature of the LPEX editor, especially when dealing with (vendor) software that has programs, 1000's of lines long and where (for example) all indicators are used.