On 12/08/2010, at 8:59 AM, Barbara Morris wrote:

When it sees the first P spec, it has to generate all the =O specs so
that they will be available in case one of the later procedures is going
to do a WRITE or an UPDATE opcode.

This has been festering in the back of my mind ...

Shouldn't the RPG compiler track whether such an operation actually occurred in a procedure and if the O-specs are not needed then drop them from its internal representation before it gives control to the back-end?

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




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.