[Ometa] CSS suitable?

[John Leuner]

If parsers have been written using recursive descent, then OMeta should
work fine. Handling invalid content sounds tricky though, if I were you
I would start by only trying to parse valid input.

John

On Fri, 2008-10-24 at 10:32 -0500, dylan austin wrote:
> I've just discovered this OMeta project and find it to be quite
> fascinating. I don't really have any experience in parsing so I'm just
> trying grok it all at the moment. All I know is this looks like the
> most approachable system I've yet seen with the added bonus that it
> seems extra powerful.
> 
> I'm particularly interested in the JS version and I'd like to see if I
> can get CSS parsed and converted into a live JS object. It will likely
> take me a while to figure this out and I'd just like to make sure it's
> feasible with OMeta. I would assume parsing CSS is no problem compared
> to actual programming languages but I think it might have a unique
> challenge. Apparently, to comply with the spec for parsing CSS you
> have to allow for invalid content. From what I understand there is
> currently no parsing grammar for CSS that meets that requirement. I'm
> raising this concern based on what I read here:
> http://markmail.org/message/h5hkolxgbv3lfsdf
> 
> Any thoughts? Thanks for the excellent tool and the list to which to
> send this.
> 
> _______________________________________________
> OMeta mailing list
> OMeta at vpri.org
> http://vpri.org/mailman/listinfo/ometa