× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. December 2009

RE: Parsing CL comments

Simon Coulter Wrote:

<SNIP>
For a generalised text parser without access to the CDO you'd have to
set some rules that are likely not onerous such as the opening /* of a
comment must have a space either before or after it. Most programmers
are likely to this anyway because it makes the code tidier. For example:

dspobjd mylib/*all *jobq /* Show the object information */
vs.
dspobjd mylib/*all *jobq /*Show the object information*/
vs.
dspobjd mylib/*all *jobq/*Show the object information*/

The CL parser will accept the 3rd example but I don't know anyone who
would write code like that.
</SNIP>

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

My take is that people will usually write descriptive comments with a space
but a change reference or other notation of some kind might not get the same
treatment.

Regards
Evan Harris



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.