From: "Charles P. Schaum" <verbo.solo@sbcglobal.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context manuals sources
Date: Sun, 29 Jun 2008 09:07:34 -0500 [thread overview]
Message-ID: <1214748454.5778.7.camel@elbereth> (raw)
In-Reply-To: <326847810806290409x2f5b984eu80a8b6b76b8f937e@mail.gmail.com>
In a parser, a piece of code that interprets a set of structured rules
(grammar) from a (partially or fully) tokenized input stream from the
lexical analyzer at the front end, LHS is something on the left hand
side of an equation or term (thus, on the left-hand parse tree) and RHS
is on the right hand side.
There are free sources out there to find stuff on parsing so you don't
have to go and buy the Dragon book (Aho, Sethi, Ullmann), which I
nevertheless consider a vade mecum. You will find links to such
documentation under the computer -> reference category at:
http://yoel.info/links.htm
Best wishes, and welcome to the world of artificial languages.
Charles
On Sun, 2008-06-29 at 13:09 +0200, Alan Stone wrote:
> Euuuh, other than constant and variable...
>
> LHS, RHS and enumeration are like klingon to me. :O)
>
> Are these terms important to understand the code ?
>
> Alan
>
>
> On Sun, Jun 29, 2008 at 12:52 PM, Taco Hoekwater <taco@elvenkind.com> wrote:
> > Alan Stone wrote:
> >> Hi,
> >>
> >> I'm trying to figure out the meaning and use
> >> of the c! and v! prefixes in commands in, for
> >> example, the layo-xx.tex source files at
> >> http://context.aanhet.net/svn/manuals/context/
> >> aka...
> >
> > c is a constant (LHS), v is a variable (RHS enumeration).
> >
> > Best wishes,
> > Taco
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-29 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 10:41 Alan Stone
2008-06-29 10:52 ` Taco Hoekwater
2008-06-29 11:09 ` Alan Stone
2008-06-29 14:07 ` Charles P. Schaum [this message]
2008-06-29 15:53 ` Aditya Mahajan
2008-06-29 17:02 ` Alan Stone
2008-06-30 17:53 Alan Stone
2008-07-01 6:18 ` Wolfgang Schuster
2008-07-01 8:02 ` Alan Stone
2008-07-01 8:16 ` Wolfgang Schuster
2008-07-01 8:56 ` Hans Hagen
2008-07-01 9:18 ` Alan Stone
2008-07-01 9:32 ` Hans Hagen
2008-07-01 9:57 ` Alan Stone
2008-07-28 9:12 Alan Stone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1214748454.5778.7.camel@elbereth \
--to=verbo.solo@sbcglobal.net \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).