Re: comment syntax

From: Shalom Bresticker (Shalom.Bresticker@freescale.com)
Date: Thu Jan 20 2005 - 08:27:22 PST

  • Next message: Shalom.Bresticker@freescale.com: "p1364-2005 introduction and clause numbering"

    I agree with that.

    Shalom

    "Geoffrey.Coram" wrote:

    > OK, it it a little nit-picky, but I think the \n
    > should be changed to "newline" (which is used in
    > the definition of white_space), because \n is
    > only identified as an escape sequence in strings.
    >
    > -Geoffrey

    On Thu, 20 Jan 2005, Geoffrey.Coram wrote:

    > Hi, Shalom -
    >
    > On an issue I brought up before, in A.9.2:
    >
    > one_line_comment ::= // comment_text \n
    >
    > I think this should read
    >
    > one_line_comment ::= // {Any_ASCII_Characters_except_newline} newline
    >
    > following the definition of string (A.8.8) and of
    > white_space (A.9.4).
    >
    >
    > I don't really have a good suggestion for block_comment,
    > other than something like
    >
    > block_comment ::= /* {Any_ASCII_Characters_except_*/} */
    >
    >
    > -Geoffrey 

    --
Shalom Bresticker                        Shalom.Bresticker @freescale.com
Design & Verification Methodology                    Tel: +972 9  9522268
Freescale Semiconductor Israel, Ltd.                 Fax: +972 9  9522890
POB 2208, Herzlia 46120, ISRAEL                     Cell: +972 50 5441478

    [ ]Freescale Internal Use Only      [ ]Freescale Confidential Proprietary

    This archive was generated by hypermail 2.1.4 : Thu Jan 20 2005 - 08:10:44 PST and
    sponsored by Boyd Technology, Inc.