W3C home > Mailing lists > Public > www-style@w3.org > July 2013

Re: [css-syntax] string to number feedback

From: Marc O'Morain <marc@marcomorain.com>
Date: Sat, 20 Jul 2013 16:15:17 +0100
Message-ID: <CAP2Q2S6aO7rLuh8UuB9Jw9cSLvdmDYogrRDoNPPCTL6CjvbgKw@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Simon Sapin <simon.sapin@exyr.org>, www-style list <www-style@w3.org>
Hi guys,

I have another question – section "5.4.3 Consume a qualified rule"
doesn't match the railroad diagram for "Qualified rule" in section
5.1.

5.4.3 says that a qualified rule contains a simple block (incorrect I
think?), whereas the railroad diagram says it contains a declaration
list (correct I think?).

Marc


On Wed, Jul 10, 2013 at 6:20 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Wed, Jul 10, 2013 at 9:21 AM, Marc O'Morain <marc@marcomorain.com> wrote:
>> Hi Simon,
>>
>> My tokenizer is complete and I have started work on my parser. I think
>> I have found another issue:
>>
>>> 5.4.3 Consume a qualified rule
>>>
>>>〈{〉
>>> Consume a simple block and assign it to the qualified rule's block. Return the qualified rule.
>>>
>>> simple block with an associated token of 〈{〉
>>> Assign the block to the qualified rule's block. Return the qualified rule.
>>
>> The second of the statements above does not seem to make sense – I
>> don't think that a token can be of type 'simple block' – I think you
>> can just remove that second section and leave the first. (consume a
>> simple block...).
>>
>> Or am I wrong?
>
> The parser algorithms are explicitly designed to be agnostic as to
> whether you call them with a stream of tokens or of component values.
> This mostly doesn't matter, but it does mean that I have to have a few
> lines like that, where you can see either a brace or a block,
> depending on which type of stream you're using.
>
> ~TJ



-- 
Marc O'Morain
http://marcomorain.com
Received on Saturday, 20 July 2013 15:15:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:32 UTC