From: "A. Soare" <alinsoar@voila.fr>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Backus Naur
Date: Fri, 8 Oct 2010 21:14:52 +0200 (CEST) [thread overview]
Message-ID: <29477536.423381286565292991.JavaMail.www@wwinf4617> (raw)
> Emacs has already some major modes for working with extended bnf, which is =
> standardized. This is not the case for my implementation, that I wrote only=
> for my own use.
>
> I don't understand what you mean -- could you explain the difference?
I do not know exactly to explain you the difference, as I do not know ebnf. I made the major mode for my own use, in order to help me for the problems I want to solve, with no intention for learning the extended bnf.
Vinicius Jose Latorre published "Links for ebnf2ps package" on his wiki page:
http://www.emacswiki.org/emacs/ViniciusJoseLatorre. He known the ebnf protocol.
I can say just I suppose the difference consist of regular expressions.
My code:
1. marks the terminals (defined by the regexp "all words inside apostrophe '' " ) using font-lock.
scans the file 1 second after the file was changed. It uses the regular expression "all words starting at the beginning of line and finishing by ':' newline " to collect left nonterminas. Afterwards, for every left nonterminal X from the list, it adds properties to right nonterminal X, if it is not terminal (terminals are marked in this moment with the properties defined by the properties of font-lock).
Apart from this, I do not know what to tell you the diff is. I do not want to spend time now on exptending the code to be ebnf compatible. But I suppose that it is not much difference.
Alin.
____________________________________________________
Découvrez les nouveaux modèles de voitures présentés au Mondial de l’Automobile à Paris : http://actu.voila.fr/evenementiel/salon-auto-paris-2010/
next reply other threads:[~2010-10-08 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 19:14 A. Soare [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-02 11:09 Backus Naur A. Soare
2010-10-04 2:03 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29477536.423381286565292991.JavaMail.www@wwinf4617 \
--to=alinsoar@voila.fr \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).