errata/597: whitespace/comments within compiler directive

From: eric_mahurin@yahoo.com
Date: Mon Jul 19 2004 - 21:47:01 PDT

  • Next message: eric_mahurin@yahoo.com: "errata/598: "$" ambiguity in PATHPULSE$"

    >Number: 597
    >Notify-List:
    >Category: errata
    >Originator: Eric Mahurin
    >Environment:
    >Description:

    In general, I think there needs to be clarification of where and what kind of whitespace and comments can/should appear for compiler directives. I think whitespace and comments should be explicitly addressed for compiler directives because compiler directives are handled before parsing occurs and likely while lexing occurs (identifying identifiers, numbers, whitespace, and comments). The C preprocessor which is quite similar also has restrictions in this area and it would be good to give the same level of clarification.

    Here are the positions that I think need clarification about whitespace/comments:

    - Preceding a compiler directives on a line (excluding macro calls). Ex: assign a = `ifdef XYZ b `endif
    - Following a compiler directives command (excluding macro calls and `define - already specified). Ex: `else assign a=b;
    - Between the backtick and the directive keyword. Ex: `/**/define MAC
    - Between the directive keyword and/or its arguments. Ex: `line/**/1/**/"test.v" 1
    - Between the `define and macro call macro identifier and "(" starting the macro argument list. Ex: `define MAC /**/ (a) a*a
    - Within the `define and macro call macro argument list. Ex: `define MAC( a /* , b ) */ , c )
    - Multi-line comments within `define macro text. Ex: `define MAC(a,b) c /* (newline) */ * d

    This archive was generated by hypermail 2.1.4 : Mon Jul 19 2004 - 21:47:16 PDT and
    sponsored by Boyd Technology, Inc.