What are the Progress Developer Studio for OpenEdge Parsing preferences? - Progress Community

Loading

Skip to Main Content

What are the Progress Developer Studio for OpenEdge Parsing preferences?

What are the Advanced > Parsing preferences in OpenEdge Architect 10.2B06 or higher and Progress Developer Studio for OpenEdge 11.1 or higher? What are the -Dastopt, -Dastinc and -Dastskp flags for the OpenEdge Eclipse plug-ins ? How are they used, and what are the risks ?

Aug 21, 2015
Knowledge

Title

What are the Progress Developer Studio for OpenEdge Parsing preferences?

URL Name

000028573

Article Number

000149804

Environment

Product: OpenEdge Version: 10.2B06 and higher service packs, 11.x OS: Windows Other: OpenEdge Architect, Progress Developer Studio for OpenEdge

Question/Problem Description

What are the Advanced > Parsing preferences in OpenEdge Architect 10.2B06 or higher and Progress Developer Studio for OpenEdge 11.1 or higher?

What are the -Dastopt, -Dastinc and -Dastskp flags for the OpenEdge Eclipse plug-ins ?

How are they used, and what are the risks ?

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Resolution

In the OpenEdge 10.2B service packs and OpenEdge 11, several changes were made to improve performance in the OpenEdge Architect / Progress Developer Studio for OpenEdge, specifically in the processing of include files.

Some of these changes need to be activated explicitly because they may introduce other unwanted side effects. They impact how the Abstract Syntax Tree (AST) for a file is built. Because the AST is a fundamental part of the Eclipse environment and drives the Outline view, code completion assistants and other major features, these changes potentially have a very large impact on functionality and the risk of enabling them without prior notice is considered too big.

To activate these fixes, Parsing preferences were added to the Advanced preferences in the OpenEdge Architect or Progress OpenEdge node of the Preferences dialog.

The Parsing preferences are:

Add file only once
Cache the file content
Trim the content

"Trim the content" is only available if "Cache the file content" is enabled.

These preferences correspond to the -Dastopt, -Dastkinc and -Dastskp flags respectively. The flags are inserted into the eclipse.ini file by the Preferences dialog when the corresponding preferences are set. In OpenEdge 11.0 the Parsing preferences are not available in the Preferences dialog, so the flags must be entered on the javaw.exe command line or into eclipse.ini by hand to enable the preferences.

The meaning of each flag is as follows:

1. –Dastopt (Available starting with OpenEdge 10.2B04 and OpenEdge 11.0)

Enabling this flag causes the includes to be expanded fewer times. When the same file is getting included many many times, this will decrease the size of the Abstract Syntax Tree (AST).
This will cause no problems if the code in includes are independent statements, and not partial snippets .
The risk is that when include files contain partial statements, this may cause minor damage to AST.

2. –Dastinc (Available starting with OpenEdge 10.2B06 and OpenEdge 11.0)
Select this option to cache the include file contents. This stores the contents of an include file in the memory until the program is closed.

3. –Dastskp (Available starting with OpenEdge 10.2B06 and OpenEdge 11.0)

Enabling this flag causes the tokens from include files to be trimmed, such that only definitions used in outline view, and the tokens required to correctly understand the structure of the including file will be retained and other tokens are discarded. For example, If there is a internal procedure in a include file, only the procedure declaration and the parameters are retained, and all other statements in the internal procedure body will be discarded.
The risk is that, any bugs in the logic that skips/discards the AST tokens will cause significant damage to the AST, and visible impact.

To activate these flags:

In OpenEdge 10.2B06 to 10.2B08, and in OpenEdge 11.1.0 onward
There are 3 check boxes in Preferences -> OpenEdge Architect -> Advanced -> Parsing:

1. Add file only once

2. Cache the file content

3. Trim the content

Check all the above three check boxes.

In OpenEdge 11.0.x:
Activate the desired options by adding the Java arguments for the JVM in one of the following locations:

On the javaw.exe command line that starts OpenEdge Architect / Progress Developer Studio
In %DLC%\oeide\eclipse\eclipse.ini

Use the following format for each flag to be activated:

-Dastopt=true
-Dastinc=true

-Dastskp=true

IMPORTANT NOTICE
PLEASE BACKUP / COPY THE WORKSPACE BEFORE ACTIVATING ANY OF THESE FLAGS
THESE FLAGS HAVE THE POTENTIAL TO CORRUPT THE WORKSPACE, RENDERING IT UNUSABLE

Workaround

Notes

OpenEdge Architect was renamed Progress Developer Studio for OpenEdge in OpenEdge 11. This article applies to the component under both names for the versions specified.

References to Other Documentation:

Progress Developer Studio for OpenEdge Online Help, Chapter 10, "Introducing the ABL Editor > Reference > ABL Editor preferences > Parsing options"

Progress Articles:

OE Architect / PDSOE: Java out of memory errors when code uses many Include file references

Keyword Phrase

Last Modified Date

11/20/2020 7:27 AM

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

What are the Progress Developer Studio for OpenEdge Parsing preferences? - Progress Community