[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Centaur1.2
In article <42366@sophia.inria.fr>, jbenz@cnam.cnam.fr (Judith Benzakki) writes:
=>
=> Nous demarrons avec Centaur1.2
=> Nous avons pu ecrire un fichier L.metal, que nous compilons
=> correctement, et le parser marche
=> Mais a chaque fois que nous lancons Centaur
=> et que nous voulons lire un fichier en langage L
=> Nous avons le message suivant
=> ---------
=> connect:Connection refused
=> Restarting on Judith:server -wait -name L /home/users/liu/centaur/tables/L/syntax/metal//L
=> L:tables read
=> L_code.ll:loaded
=> L_sch:loaded
=> -------
=> puis il charge le fichier
Hi Judith,
Regarding your parser: with Metal generated parsers, which are now external it is
normal that each time you restart centaur and try to read an L program, the
centaur process must try to connect to the external parser's server, which is not
terminated when you terminate a centaur session. Now, everytime you change your
L.metal and *remake* the parser, then it is true that you'd like to kill the
existing parser (not the parser server) and restart the parser. Note that the
machine on which the parser is started is determined by a resource (according to
your message, one can assume that your machine bears your name :-).
Thus, from the above we can determine that in your new centaur session you've
tried reading an L program, the existing parser is not in a correct state and
the parser's server is restarted on your machine, Judith, then the tables are
loaded and your file is read.
So it seems all goes well, what doesn't seem to work?!
regards
janet
--------------------------- FYI (for your information)
Places of interest in the doc on this subject:
The Centaur Tutorial (vol 1) :
pg17 explains the resources for the hostname
The Metal Manual (vol 2):
pg6 explains how one goes about *make*ing the parser
The Centaur Tools Manual (vol 3):
pg12 gives details on language and parser manipulation. In particular,
the function #:centaur:remove-syntax is appealing for killing the
parser from within Centaur, but one must be careful since if you use
this to kill a parser, say because you've changed the language, then
any editors having programs in the target language may lead to problems
to do inconsistencies in the metal specifications.
of having editors
on the screen with
manipulations. Note
- References:
- Centaur1.2
- From: jbenz@cnam.cnam.fr (Judith Benzakki)