× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. May 2006

RE: Compile failed when try to do return not SUCCESSFUL where SUCCESSFULis declared as const

Hi Lim -


Go figure these out:

This one failed to compile:
D ind1            c                   const(*on)
C                   if        ind1
C                   endif
C                   eval      *inlr = *on

This one compiled just fine:
D ind2            c                   const('1')
C                   if        ind2
C                   endif
C                   eval      *inlr = *on
Perhaps in the first example the compiler is creating a three-byte character constant that contains either '*ON' or '*on' rather than interpreting it as a true/false value and creating a one-byte character constant that contains '1'.
You can test this by creating a three-byte field, eval SUCCESSFUL into it when defined as const(*on) and see what the value of the field is. 

Ken
http://www.kensims.net/
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.