From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: [ANN] Nyacc version 0.83.0 released
Date: Sat, 07 Apr 2018 14:21:38 +0200 [thread overview]
Message-ID: <87tvsnyzot.fsf@gnu.org> (raw)
In-Reply-To: <abaceeaf-aa5d-2b7c-704f-00d98a18b033@gmail.com> (Matt Wette's message of "Fri, 6 Apr 2018 17:20:01 -0700")
Matt Wette writes:
> I think it will take me a while to make a release.
That's fine. Although all my tests pass, I found that to compile mes.c
I need string-fold-right. So I added that to Mes.
After that, tcc.c hangs while parsing. Will have to investigate later,
for now I'm reverting to 0.80.42.
>> I added some tracing
>> to stderr. Possibly you have a better way to do this, esp. the
>> NYACC_TRACE environment variable kludge...
>
> There is a #:debug option to the parser that provide a trace through
> the parsing.
Yes, I'm using that; great.
> And if you look in examples/nyacc/lang/c99/Tmach.scm there is code to
> show how
> to generate a file with parser states.
OK.
The NYACC_TRACE=1 feature is meant for users. Parsing tcc with
Mes+MesCC currently takes ~1h (with Guile+MesCC only 40s), so printing
some minimal feedback to the user (e.g., al functions and global
variables) is helpful.
I'll try to change my patch to use something like
#:trace '(function global)
similar to #debug.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
prev parent reply other threads:[~2018-04-07 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 18:19 [ANN] Nyacc version 0.83.0 released Matt Wette
2018-04-06 12:38 ` Jan Nieuwenhuizen
2018-04-07 0:16 ` Matt Wette
2018-04-07 0:20 ` Matt Wette
2018-04-07 12:21 ` Jan Nieuwenhuizen [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvsnyzot.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.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).