From: Emmanuelle <eraffenne@teleline.es>
To: sourcenav@sourceware.cygnus.com
Subject: Re: Tcl parser
Date: Thu, 16 Aug 2001 05:21:00 -0000 [thread overview]
Message-ID: <3B7BBA3B.3908486A@teleline.es> (raw)
In-Reply-To: <34168E9E775CD411A4430000F80768621B4432@unclassfs03.rlmsystems.com.au>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
Hi:
Thanks for your answer. Sorry if I didn't write before but I'd problems
with my email account...
I've downloaded puma from http://www.first.gmd.de/cocktail/ Is this
version ok?
I've translated the menu items to spanish, it's not finished yet (I have
to verify the hotkeys). Where should I send it? Maybe I'll translate it
to french too if I have time.
--
Emmanuelle
"Keogh, Craig" escribió:
>
> > I want to modify the Tcl parser
> > that it can parse procedures declared that way but I need a
> > little help
> > to do that; the source code of SN is very large and I don't know from
> > where to start.
>
> The TCL parser can be found in:
>
> /source/snavigator/parser/tcl
>
> There is documentation on how to add parsers:
>
> /source/snvavigator/doc/html/enterprise/progref
>
> But the TCL parser does not follow use this API. Do as we say, not as we do.
> It inserts symbols with put_symbol. The TCL parsers uses a parser-generator
> / compiler-compiler, but it doesn't use yacc/bison. Puma or something. If
> you wish to modify the code, you will need this tool.
>
> Happy hacking,
> Craig Keogh
next prev parent reply other threads:[~2001-08-16 5:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 16:49 Keogh, Craig
2001-08-16 5:21 ` Emmanuelle [this message]
2001-08-16 8:47 ` Cocktail is open source? [Was: Tcl parser] Ian Roxborough
-- strict thread matches above, loose matches on Subject: below --
2001-08-08 13:24 Tcl parser Emmanuelle
2001-08-08 16:45 ` Mo DeJong
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=3B7BBA3B.3908486A@teleline.es \
--to=eraffenne@teleline.es \
--cc=sourcenav@sourceware.cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).