Feedback
Did this article resolve your question/issue?

   

Article

Two-pass compile broken for class-based variable definitions

Information

 
TitleTwo-pass compile broken for class-based variable definitions
URL Nametwo-pass-compile-broken-for-class-based-variable-definitions
Article Number000178397
EnvironmentProduct: OpenEdge
Version: All Supported Versions
OS: All Supported Platforms
Question/Problem Description

The following class should compile, but instead the following error is returned instead:

** Unknown Field or Variable name - isTmp. (201)

BLOCK-LEVEL ON ERROR UNDO, THROW.

CLASS TwoPass:
    DEFINE PUBLIC PROPERTY TwoPassTest AS LONGCHAR NO-UNDO
        GET:
            IF isTmp THEN
                THIS-OBJECT:TwoPassTest = "1".
            RETURN THIS-OBJECT:TwoPassTest.
        END GET.
        PRIVATE SET.

    DEFINE VARIABLE isTmp AS LOGICAL NO-UNDO.

END CLASS.


Classes should be processed by a two-pass compiler, which should mean variables are scoped to the class, however this is not happening.
 
Steps to Reproduce
Clarifying Information
Error Message** Unknown Field or Variable name - <field-name>. (201)
** <program> Could not understand line <number>. (198)
Defect/Enhancement NumberDefect PSC00351187
Cause
The exact cause is not known at this time.
 
Resolution
None at this time.
 
Workaround

If the reference to the variable is qualified it will work.

For example:

IF THIS-OBJECT:isTmp THEN

 
Notes
Last Modified Date10/10/2016 7:34 PM
Attachment 
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.