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



Actually, you can use the // comment syntax in fixed format too. Hans
pointed that out to me about a year ago.

.....C     CUSTNO     CHAIN     CUSTMAST
         //  If customer not found, send error
.....C                if        NOT %Found()
.....C                eval      errmsg = 'Customer Not found'
     C                ITER
     C                ENDIF
       //  Go get the customer sales history.
       //  If there is no customer, then the heck with the user. 
     C                CallP     GetSalesHist(CustNo)

-Bob Cozzi

-----Original Message-----
From: rpg400-l-bounces+cozzi=rpgiv.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+cozzi=rpgiv.com@xxxxxxxxxxxx] On Behalf Of Fisher,
Don
Sent: Wednesday, July 28, 2004 4:07 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: converting string to a numeric

Actually, it would have to be a blank in positions 6 and 7, because an
asterisk in position 7 indicates a comment, except in /free where a slash is
required, and a plus indicates an SQL continuation.  Come to think of it,
position 7 is also used for level break indicators.

I'm with you on this one, Joe, I don't understand why the need for a special
section marker unless they felt the need to be consistent with /Exec.
Perhaps it makes distinguising /free from fixed easier in the event some
people like mixing the two together?  Perhaps it made the compiler code
easier to write?

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx

<clip>
But I'll weigh in (once) on this issue: we don't like /free and /end-free
because they aren't
needed.  By simply saying that a blank in position 6 makes the spec a
free-form calculation, we wouldn't have an issue.  But the compiler team
decided it would be better for us if we had to code the bracketing
statements.  Heck if I know why.
<clip>
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.