|
>Bob Cozzi said: > >The only caveat on not using CALLP, however is >that if the program or >procedure name is the same as an RPG IV opcode, >then you must use the CALLP >opcode to avoid confusion. Very true: of course this can be avoided by renaming the prototype to something that would not be an OPCODE name, preferably a little more descriptive. At least for myself I hope the days of writing programs called "XLATE" or "BITON" are past LOL! >Also, I think using >CALLP makes it more clear >what you're doing should an novice RPG IV coder >have to go in and change >your program later. Personally, NOT using opcodes is one of my personal favorite things about /free, but we don't need to go there... <vbg> Joel http://www.rpgnext.com
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
