× 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. October 2003

Re: Please vote for Syntax check in /FREE!

Bob cozzi wrote:

The only enhancement RPG IV needs to make it more usable today is to allow a
COMMA to be used as the parameter separator. No single thing causes me more
delays in development than this one "feature". I would give up function
overloading, semi colon at the end of statements in free format, and a bunch
of other things for this one capability. Oh for the days I could write:

   Callp   GetLibInfo('QGPL',nObjCnt, nLibSize)
Instead of...

Callp GetLibInfo('QGPL':nObjCnt:nLibSize)

Even today, I still enter a COMMA, compile the code, then have to figure out
what the error is telling me (because it never says COLON missing from
expression) it says things like "expected token not found" or "right
parameter missing from expression" and I look at the code (with the COMMAs
in it) and it looks perfectly fine to me, then I realize, COLOTIS is the
cause the problem


And Bob, you also know full well that that's not going to change any time soon. As you know, you can code "CALLP PROC(12,34);" today. And since release to release compatibility is rather important to us (probably to you too), the meaning of that particular bit of syntax can't change.

Believe me, I think all of us here would have preferred the comma to the colon.

Cheers! Hans



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.