Re: Parsing CL comments

On 15/12/2009, at 9:57 AM, Evan Harris wrote:

Over the years I've run into a fair amount of code containing comments like
/*CR1234*/

So have I but there's usually a leading space before the /*. Refer to my last example which had no space before OR after the /*

My take is that people will usually write descriptive comments with a space

By which I presume you mean a space between the /* and the first word of the comment ...

but a change reference or other notation of some kind might not get the same
treatment.

Accepted, but again usually has a leading space before the /* even if it doesn't have one after it. You only need a space EITHER before or after the /* to distinguish a comment from a special value. It's only when neither of those are present that misinterpretation could occur. However, I did say that some coding styles could break whatever "rules" are presumed by the parser.

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