W3C home > Mailing lists > Public > public-css-bugzilla@w3.org > October 2012

[Bug 19484] New: Inconsistency in regards to EOF (and EOF token)

From: <bugzilla@jessica.w3.org>
Date: Thu, 11 Oct 2012 21:12:07 +0000
To: public-css-bugzilla@w3.org
Message-ID: <bug-19484-5148@http.www.w3.org/Bugs/Public/>

          Priority: P2
            Bug ID: 19484
          Assignee: jackalmage@gmail.com
           Summary: Inconsistency in regards to EOF (and EOF token)
        QA Contact: public-css-bugzilla@w3.org
          Severity: normal
    Classification: Unclassified
                OS: Linux
          Reporter: bfrohs@gmail.com
          Hardware: PC
            Status: NEW
           Version: unspecified
         Component: Syntax
           Product: CSS

In the "Data state", an "end-of-file token" is emitted:

>     Emit an end-of-file token. 

In the Tree Construction Definitions, an "EOF token" is mentioned:

> next input token
>     The token following the current input token in the list of tokens produced by the tokenizer. If there isn't a token following the current input token, the next input token is an *EOF token*.

In the "Top-level mode", "At-rule-prelude mode", "Rule-block mode", and several
other modes, an "EOF token" is expected. E.g.:

> EOF token
>     Finish parsing. 

However, neither "EOF token" or "end-of-file token" is mentioned in the list of
possible tokens in the Tokenization overview:

> The output of the tokenization step is a series of zero or more of the following tokens: identifier, function, at-keyword, hash, string, bad-string, url, bad-url, delim, number, percentage, dimension, unicode-range, whitespace, comment, cdo, cdc, colon, semicolon, [, ], (, ), {, }.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 11 October 2012 21:12:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:40 UTC