×
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.
The parser would be looking at a name (file name or job name) and the /
would indicate a qualified name. Within the name portion of a qualified
name, it'd see the * as an indicator for special value.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Tuesday, December 15, 2009 11:32 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Parsing CL comments
I'm not an expert ( it's been a while since my formal languages course
:) but recursive decent parsing provides an answer to your OQ in the
following manner:
At the point that the parser is looking at /*ALL or /*PART1 the parser
wouldn't be looking for a comment.
Thanks, Charles. You see something that I don't. With what we know,
what would prevent the parser from looking for a comment there? I look
at this and say, Is a blank allowed here? Yes, so a comment may appear
here.
Right? What am I missing?
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Most people spend their lives going to bed when they're not sleepy and
getting up when they are."
-- Cindy Adams
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
