Related articles |
---|
Supporting multiple input syntaxes mijoryx@yahoo.com.dmarc.email (luser droog) (2020-08-12) |
Re: Supporting multiple input syntaxes 793-849-0957@kylheku.com (Kaz Kylheku) (2020-08-13) |
Re: Supporting multiple input syntaxes DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2020-08-13) |
Re: Supporting multiple input syntaxes minforth@arcor.de (2020-08-13) |
Re: Supporting multiple input syntaxes mijoryx@yahoo.com.dmarc.email (luser droog) (2020-08-13) |
Re: Supporting multiple input syntaxes mijoryx@yahoo.com.dmarc.email (luser droog) (2020-08-13) |
Supporting multiple input syntaxes davidlovemore@gmail.com (David Lovemore) (2020-08-15) |
Re: Supporting multiple input syntaxes mijoryx@yahoo.com.dmarc.email (luser droog) (2020-08-15) |
Re: Supporting multiple input syntaxes davidlovemore@gmail.com (David Lovemore) (2020-08-16) |
Re: Supporting multiple input syntaxes mijoryx@yahoo.com.dmarc.email (luser droog) (2020-08-20) |
Re: Supporting multiple input syntaxes gah4@u.washington.edu (gah4) (2020-08-23) |
Re: Supporting multiple input syntaxes mijoryx@yahoo.com.dmarc.email (luser droog) (2020-08-23) |
[6 later articles] |
From: | luser droog <mijoryx@yahoo.com.dmarc.email> |
Newsgroups: | comp.compilers |
Date: | Thu, 13 Aug 2020 21:37:55 -0700 (PDT) |
Organization: | Compilers Central |
References: | 20-08-002 20-08-005 |
Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="99998"; mail-complaints-to="abuse@iecc.com" |
Keywords: | C, tools |
Posted-Date: | 15 Aug 2020 10:45:04 EDT |
In-Reply-To: | 20-08-005 |
On Thursday, August 13, 2020 at 5:24:36 PM UTC-5, minf...@arcor.de wrote:
> Am Donnerstag, 13. August 2020 00:32:56 UTC+2 schrieb luser droog:
> > I've got my project successfully parsing the circa-1975 C syntax
> > from that old manual. I'd like to add parsers for K&R1 and c90
> > syntaxes.
> >
> > How separate should these be? Should they be complete
> > separate grammars, or more piecewise selection? ...
>
> Why not settle for one master dialect and use awk to translate between dialects?
>
> [Probably because there is a great deal of C code written to comply with
> the various versions of the standard, users want error messages that match
> the code they wrote rather than some intermediate code, and it would be quite
> an awk program that could reconcile all the differences among C flavors. -John]
One of the possible goals for this project is exactly such a translator
that can downgrade or upgrade code from one standard version to another.
Another possible application is a source code formatter. Currently the
CST produced by the parser keeps all the original whitespace attached
to each token.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.