I don't agree. BNF is basically the only proper and efficient way for a
nice formal descrition of a LR parsable language. No accident most
programming
languages out there are defined in some sort of BNF.
> description of what each field is would suffice. I would go so far as to
> say there needs to be a standard established in how /proc data is formatted
> so that we can create templates for the standard tools.
>
> (I have to ask, have you ever used flex? I used to hand-code scanners, but
> I find that flex is so much easier and generates smaller faster code than I
> can do by hand. Changes are easy, too)
Short answer: yes I know them, yacc bison pure flex and lex whatever,
and
I used to use them for job projects not just toys. Trust me they are
the only proper practical way to define the syntax of something parsable
and beeing complete about it. Unless you wan't to reach the stability of
the usual perl-web hackkery.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/