Closed Bug 742141 Opened 12 years ago Closed 12 years ago

Need to support the 'float' type in the WebIDL parser

Categories

(Core :: DOM: Core & HTML, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla15

People

(Reporter: bzbarsky, Assigned: khuey)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 1 obsolete file)

Attached patch Maybe patch (obsolete) — Splinter Review
Right now, the parser dies on it.

Attached patch makes things work, but may be bogus.
Attachment #612067 - Attachment description: Maybe patc → Maybe patch
Attached patch PatchSplinter Review
The "Maybe patch" fixes this, but it's a step in the wrong direction because it makes float consts more broken than they already are.  This patch doesn't make float consts any worse.
Attachment #612067 - Attachment is obsolete: true
Attachment #619526 - Flags: review?(justin.lebar+bug)
So FLOAT_ is the "float" keyword, while FLOAT is a floating-point literals?

If so, can we indicate in the token names which are keywords and which are literals, by putting a prefix / suffix on the names?  That would be helpful for sanity, I think.  (It looks like the spec does this, using "Literal" as a suffix for the literals tokens.)
Comment on attachment 619526 [details] [diff] [review]
Patch

r=me, but I'd really prefer for us to change to a saner set of token names.  But you can do that as a followup if you'd like...
Attachment #619526 - Flags: review?(justin.lebar+bug) → review+
Float and FloatLiteral sound good to me.  The *Literal stuff is pretty new in the spec, I think.
Flags: in-testsuite+
Target Milestone: --- → mozilla15
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: