Related articles |
---|
EBNF open letter 72634.2402@CompuServe.com (1994-09-11) |
Re: EBNF open letter mabp@bga.com (1994-09-14) |
Re: EBNF open letter fjh@munta.cs.mu.OZ.AU (1994-09-17) |
Re: EBNF open letter dbaarda@ozemail.com.au (Don Baarda) (1994-09-18) |
Newsgroups: | comp.compilers |
From: | Don Baarda <dbaarda@ozemail.com.au> |
Keywords: | parse, EBNF |
Organization: | OzEmail Pty Ltd |
References: | 94-09-030 94-09-062 |
Date: | Sun, 18 Sep 1994 03:55:55 GMT |
Hey, by your own syntax, shouldn't that be
>For example:
>
> (* floating-point literals *)
> float number token = integer constant, fraction, [exponent];
you forgot the ^
Trivial, I know, but without it you would have got;
Syntax error: expected ; , |
:-)
Also, the standard presented only allows for string terminals. This is
usualy fine, but what if you want to use EBNF syntax to represent a binary
languages? I often use psedo-EBNF to represent binary file formats.
However, I must admit that this is the first I've heard of an EBNF
standard, and I must say, about time and not a bad job too (I haven't seen
it all, but it looks like it hasn't been stuffed up).
If anyone wants ideas for a standard with binary terminals, I have a few
ideas.
ABO =:-)
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.