From: "R. Bastian" <rbastian@free.fr>
To: ntg-context@ntg.nl
Subject: Re: BNF grammar for ConTeXt (was: What happened with sectionworld?)
Date: Thu, 30 Apr 2009 22:03:38 +0200 [thread overview]
Message-ID: <20090430220338.1f3e1002@KUBUNTU64> (raw)
In-Reply-To: <fe8d59da0904300312t16e6fd2et9202029d30d5aa2f@mail.gmail.com>
On Thu, 30 Apr 2009 12:12:10 +0200
luigi scarso <luigi.scarso@gmail.com> scribit:
> >
> >
> > > My suggestions to start :
> > > 1) define a **simple but significative** domain ,ie "this grammar is for
> > > subset of ConTeXt language dedicated to variable-data pdf forms"
> >
> > yes
> >
> > > 2) make a bnf grammar spec
> >
> > yes
> >
> > > 3) build a parser lex/yacc for 2)
> >
> > later
> >
> why ? There is no difference between 2 and 3
True, but I think that the aim of such a BNF-grammar
is to help in a concise way the newbie and tell him _what_ can be
made and _when_ {\it in quel tempo}.
(In fact, I dont like lex/yacc because it seems not a good idea to
intervene on the generated code).
>
>> I think a wiki would be a better forum than this mailing-list ?
> >
> hmm
> "this" mailing-list is ok for this kind of discussions
> "a wiki" is wiki.contextgarden.net
> and you should put your results in your personal page
>
>
> --
> luigi
___________________________________________________________________________________
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:[~2009-04-30 20:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 17:42 What happened with sectionworld? Henning Hraban Ramm
2009-04-28 18:53 ` Wolfgang Schuster
2009-04-28 21:25 ` Henning Hraban Ramm
2009-04-29 8:24 ` Hans Hagen
2009-04-29 10:24 ` Wolfgang Schuster
2009-04-29 12:35 ` R. Bastian
2009-04-29 12:54 ` Wolfgang Schuster
2009-04-29 15:07 ` Idris Samawi Hamid ادريس سماوي حامد
2009-04-29 15:43 ` R. Bastian
2009-04-29 15:55 ` luigi scarso
2009-04-29 16:46 ` R. Bastian
2009-04-29 18:00 ` luigi scarso
2009-04-29 21:16 ` R. Bastian
2009-04-29 21:24 ` BNF grammar for ConTeXt (was: What happened with sectionworld?) Wolfgang Schuster
2009-04-30 7:48 ` luigi scarso
2009-04-30 8:16 ` R. Bastian
2009-04-30 8:57 ` luigi scarso
2009-04-30 10:05 ` R. Bastian
2009-04-30 10:12 ` luigi scarso
2009-04-30 20:03 ` R. Bastian [this message]
2009-04-29 15:57 ` footnote numbers size in heads Horacio Suarez
2009-04-29 21:17 ` Wolfgang Schuster
2009-04-29 18:14 ` What happened with sectionworld? Wolfgang Schuster
2009-04-29 18:23 ` Idris Samawi Hamid ادريس سماوي حامد
2009-04-29 18:27 ` Hans Hagen
2009-04-29 18:31 ` Wolfgang Schuster
2009-04-29 18:34 ` Wolfgang Schuster
2009-04-29 18:40 ` Idris Samawi Hamid ادريس سماوي حامد
2009-04-29 13:12 ` Hans Hagen
2009-04-29 13:53 ` Mohamed Bana
2009-04-29 15:11 ` Henning Hraban Ramm
2009-04-29 21:07 ` Wolfgang Schuster
2009-04-30 15:40 ` Henning Hraban Ramm
2009-04-30 17:06 ` Wolfgang Schuster
2009-04-30 18:33 ` Henning Hraban Ramm
2009-04-30 18:46 ` Wolfgang Schuster
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=20090430220338.1f3e1002@KUBUNTU64 \
--to=rbastian@free.fr \
--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).