I've worked with Jbase for several years, and, even though Jbase changes EQUATEs to assignments when it renders its C code, I still use EQUATE for CHAR(nn), FALSE and TRUE. Just long-term habits from the old Microdata days when we bummed CPU microseconds instead of today's picoseconds, and worried about runtime page faults. Regards, Charlie Noah In a message dated 6/3/2005 6:30:37 PM Central Standard Time, [EMAIL PROTECTED] writes:
Actually I like them as assignments for the very reasons you posted. Namely that you can 'see' them when using RAID. Or maybe some day, the IBM system programmers will include an Equate table with the other compiler tables, that would be the best of both worlds, then RAID could look in that table as well, but the code could still be rendered at compile time. Will Johnson Fast Forward Technologies From: Stevenson, Charles [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) Yes , very helpful, but those should be EQUATEs, not assignments. Equates of quoted texts, CHAR(27), and even concatenations of these will all be resolved to strings by the compiler. Nothing gets executed at runtime. If the file as written were $INCLUDEd in a utility routine that gets called frequently, all those concatenations and assignments would happen each time. The only reason not to use EQUATEs that I can think of is for readability in VLIST, I_pgm listings, and RAID, where literal escape sequences are going to start appearing. From: Joe Walter Excellent! Thanks for the include code. Very helpful. ----- Original Message ----- From: <[EMAIL PROTECTED]> > 0001 *(HP.LASER) - HP LASER CODES > 0002 * > 0003 ESC = CHAR(27) ; *Escape Character [snip] ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
