|Techniques for writing an interpreter firstname.lastname@example.org (Simon Chapman) (1998-03-06)|
|Re: Techniques for writing an interpreter email@example.com (1998-03-12)|
|Re: Techniques for writing an interpreter firstname.lastname@example.org (W. Craig Trader) (1998-03-15)|
|Re: Techniques for writing an interpreter email@example.com.OZ.AU (1998-03-15)|
|Re: Techniques for writing an interpreter firstname.lastname@example.org (1998-03-18)|
|recursive comments and Re: Techniques for writing an interpreter email@example.com (Stefan Monnier) (1998-03-20)|
|Re: recursive comments (Was: Techniques for writing an interpreter) firstname.lastname@example.org (1998-03-20)|
|From:||email@example.com (Mark K. Gardner)|
|Date:||20 Mar 1998 23:42:02 -0500|
|Organization:||University of Illinois at Urbana-Champaign|
|References:||98-03-032 98-03-098 98-03-141 98-03-147 98-03-159 98-03-183|
On 20 Mar 1998 Stefan Monnier <firstname.lastname@example.org> wrote:
>What languages allow recursive comments ?
The Oberon language does. The following is a quotation from
6. Comments may be inserted between any two symbols in a program. They are
arbitrary character sequences opened by the bracket (* and closed by *).
Comments may be nested. They do not affect the meaning of a program.
>What languages enforce a "lexing" of the content of comments (so that an
>end-comment inside a string inside a comment is ignored) ?
It is not clear if this implies that comments should be able to contain end
of comment delimiters in a string or not. I believe that most compiler
implementors would exclude the closing comment delimiter from the arbitrary
character sequence if for no other reason than expediency.
Mark K. Gardner (email@example.com)
University of Illinois at Urbana-Champaign
Real-Time Systems Laboratory
Return to the
Search the comp.compilers archives again.