ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: BNF grammar for ConTeXt (was: What happened with sectionworld?)
Date: Thu, 30 Apr 2009 10:57:04 +0200	[thread overview]
Message-ID: <fe8d59da0904300157i1dfc223cm1acaee9af52a05ba@mail.gmail.com> (raw)
In-Reply-To: <20090430101646.237ad726@KUBUNTU64>


[-- Attachment #1.1: Type: text/plain, Size: 2032 bytes --]

On Thu, Apr 30, 2009 at 10:16 AM, R. Bastian <rbastian@free.fr> wrote:

> On Thu, 30 Apr 2009 09:48:40 +0200
> luigi scarso <luigi.scarso@gmail.com> scribit:
>
> > R. Bastian:
> >
> > > CONTEXT_SOURCE ::= PREAMBLE "\starttext" TEXT "\stoptext" |
> CONTEXT_SOURCE
> > >>>  TEXT ::= STARTSTOPS | SETUPS | DEFINES | OTHERS [ TEXT
> > >>
> > >> luigi:
> >
> > >   To be general, i think
> > >>   MY_CONTEXT_SOURCE ::= MACRO* END
> > >>
> > >
> > R. Bastian:
> >
> > > I dont understand the sense of "\end\starttext"
> >
> > sense==semantic
> >
> > "\end""\starttext" is a valid string for a hypothetical  bnf grammar of
> > ContTeXt
> > which is not valid for your bnf ;
> > "\end""\starttext""\stoptext" is in your bnf grammar
> > and has the same semantic of  "\end""\starttext" .
> >
> > The point is : a bnf for Context can be hard to define
> >
> >
> >  luigi:
> >
> > think that a bnf or lpeg grammar is really useful for a sort of
> > >> standard-ConTeXt
> > >> or minimal-ConTeXt or light-ConTeXt
> > >> ie a ConTeXt to use as "reference"
> > >>
> > >
> > R. Bastian:
> >
> > > Exactly what I need : standard, minimal and light
> > >
> >
> > Exactly what can be hard to define and capture in a bnf .
> >
> > wolfgang
> >
> > >
> > > How could a BNF grammar help to learn ConTeXt,
> >
> > a bnf can help to build a syntax checker, a highlighter etc.
> > Actually the only way to say that you have a valid ConTeXt string
> > is running context on that string .
> >
> > The semantic is another story.
>
> OK - but isn't it not worth to try it ?
>
sure, and I encourage you to go on and possibly write something x next
eurotex.

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"
2) make a bnf grammar spec
3) build a parser lex/yacc for 2)
4) make a lpeg grammar
5) user lpeg inside context for 3)

PS
it was just a coincidence , but for other reasons I have found this link
http://martinfowler.com/dslwip/

-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 3028 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2009-04-30  8:57 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 [this message]
2009-04-30 10:05                                 ` R. Bastian
2009-04-30 10:12                                   ` luigi scarso
2009-04-30 20:03                                     ` R. Bastian
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=fe8d59da0904300157i1dfc223cm1acaee9af52a05ba@mail.gmail.com \
    --to=luigi.scarso@gmail.com \
    --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).