Related articles |
---|
magic/absurd bash interpreter/compiler ? Avoid9Pdf@gmail.com (2012-12-23) |
Re: magic/absurd bash interpreter/compiler ? miller@yoyo.ORG (J G Miller) (2012-12-24) |
Re: magic/absurd bash interpreter/compiler ? jthorn@astro.indiana.edu (Jonathan Thornburg) (2012-12-24) |
Re: magic/absurd bash interpreter/compiler ? eric@deptj.eu (Eric) (2012-12-24) |
Re: magic/absurd bash interpreter/compiler ? barmar@alum.mit.edu (Barry Margolin) (2012-12-24) |
Re: magic/absurd bash interpreter/compiler ? gah@ugcs.caltech.edu (glen herrmannsfeldt) (2012-12-25) |
Re: magic/absurd bash interpreter/compiler ? eric@deptj.eu (Eric) (2012-12-26) |
Re: magic/absurd bash interpreter/compiler ? gah@ugcs.caltech.edu (glen herrmannsfeldt) (2012-12-28) |
Re: magic/absurd bash interpreter/compiler ? barmar@alum.mit.edu (Barry Margolin) (2012-12-28) |
From: | "Jonathan Thornburg" <jthorn@astro.indiana.edu> |
Newsgroups: | comp.compilers,comp.unix.shell,comp.os.linux.misc |
Date: | 24 Dec 2012 03:57:39 GMT |
Organization: | Compilers Central |
References: | 12-12-014 |
Keywords: | design |
Posted-Date: | 24 Dec 2012 00:09:16 EST |
In comp.compilers Avoid9Pdf@gmail.com wrote:
> But this bash nonsense is infuriating me! We
> need a rigorous/formal syntax for computing.
[[...]]
> Does this thing use multiple passes. Eg. where the complete command-line
> is FIRST analysed for "<", ">", and then LATER any function/s who's input
> and/or output is not specified, can use the previous scan's stuff.
If you want a shell with a well-defined formal structure, you might
find rc of interest. It uses a YACC (i.e., LALR(1)) parser. As usual,
Wikipedia has a reasonable intro with links to more information:
http://en.wikipedia.org/wiki/Rc
--
-- "Jonathan Thornburg [remove -animal to reply]" <jthorn@astro.indiana-zebra.edu>
Dept of Astronomy, Indiana University, Bloomington, Indiana, USA
"C++ is to programming as sex is to reproduction. Better ways might
technically exist but they're not nearly as much fun." -- Nikolai Irgens
Return to the
comp.compilers page.
Search the
comp.compilers archives again.