Re: Parsing CL comments

On 16/12/2009, at 8:24 AM, Dennis Lovelady wrote:

WDSC/RDi doesn't do things exactly this way - if you
use the formatting. And it's not consistent. But often
it will put the comment right after the end of the command,
with a space after the '/*' - if you try to enter a space
before the leading indicator, it takes it out.

I don't have RDi so cannot test. But if I read that correctly, then this
product will build that "invalid" statement from your third example (and
from my latest two).

I'm afraid that IBM client tools have always left much to be desired-- starting with CODE/400 on OS/2 (the only good part of that was it ran on OS/2--once they moved it to WinDOS it went downhill quickly), then something I forget, then WDSC, the WebFacing client, and now the various flavours of RDi. It appears that just maybe they've got something right with the EGL tools but I'm not jumping on that bandwagon.

However, if you re-read Vern's comment you'll see the client tool forces a space after the /* pair thus the comment will be valid in spite of the defect where it removes a space before the /* pair.

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 / \
--------------------------------------------------------------------