Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: current
    • Fix Version/s: milestone 1
    • Component/s: node types
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      385

      Description

      I propose to add an extension syntax for CND, so that vendors that want to provide additional semantics can do
      so in a semi-standardized manner. This way parsers at least won't choke on the files.

      For instance I would suggest that any occurrence of a section

      { myvendor foo bar baz ... }

      (including braces) be ignored (and treated as /* */ comments) by a parser that doesn't understand the
      myvendor prefix.

        Issue Links

          Activity

          Hide
          stefan_guggisberg added a comment -

          resolved as fixed as per F2F decision in Basel, Sept 07:

          fix as proposed

          Show
          stefan_guggisberg added a comment - resolved as fixed as per F2F decision in Basel, Sept 07: fix as proposed
          Hide
          reschke added a comment -

          (I don't think this is already resolved, right?)

          Show
          reschke added a comment - (I don't think this is already resolved, right?)
          Hide
          fguillaume added a comment -

          This is still an issue in RC17.
          I suggest that after § 9.2.2.20 (Comments) be included an additional section with content like:

          § 9.2.2.21 Extension Syntax

          { vendorname foo bar baz ... }

          The extension syntax is provided to allow for vendor-specific extensions. It is parsed in the same way that a
          multi-line comment would be, except that the starting and closing delimiters are braces. It can appear anywhere a
          comment can appear.

          The first whitespace-delimited token of the extension should be a unique vendor-specific identifier. The
          semantics of the extension is implementation-specific.

          I also suggest that in the Comment paragraph we say that:
          A comment may appear between any two valid tokens of the grammar.

          Show
          fguillaume added a comment - This is still an issue in RC17. I suggest that after § 9.2.2.20 (Comments) be included an additional section with content like: § 9.2.2.21 Extension Syntax { vendorname foo bar baz ... } The extension syntax is provided to allow for vendor-specific extensions. It is parsed in the same way that a multi-line comment would be, except that the starting and closing delimiters are braces. It can appear anywhere a comment can appear. The first whitespace-delimited token of the extension should be a unique vendor-specific identifier. The semantics of the extension is implementation-specific. — I also suggest that in the Comment paragraph we say that: A comment may appear between any two valid tokens of the grammar.
          Hide
          Peeter Piegaze added a comment -

          Fixed. New section "9.2.2.21 Extension Syntax" added. Section "9.2.2.20 Comments" updated to say that
          comments may appear between any two CND tokens.

          Show
          Peeter Piegaze added a comment - Fixed. New section "9.2.2.21 Extension Syntax" added. Section "9.2.2.20 Comments" updated to say that comments may appear between any two CND tokens.

            People

            • Assignee:
              jsr-283-issues
              Reporter:
              fguillaume
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: