From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development List <guile-devel@gnu.org>
Subject: Re: Syntax checks
Date: 08 Apr 2002 19:27:20 +0100 [thread overview]
Message-ID: <m33cy6xczb.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0204070827330.6652-100000@marvin.ida.ing.tu-bs.de>
>>>>> "Dirk" == Dirk Herrmann <dirk@ida.ing.tu-bs.de> writes:
Dirk> No, certainly not. However, the evaluator has to check for it. The
Dirk> reason is the following: SCM_CEVAL _must_ be called with a non-immediate.
Dirk> That means that whereever SCM_CEVAL is to be called with some expression,
Dirk> the special case of an immediate has to be checked before doing the actual
Dirk> call.
Dirk> In the execution of the 'do body, every expression is checked to be an
Dirk> immediate, and if it isn't, then SCM_CEVAL is called. It is this kind of
Dirk> check (and a couple of similar ones) that I try to remove, since it slows
Dirk> down the evaluator.
That sounds fine.
Dirk> As you may have noticed, I have already started to clean up the evaluator
Dirk> code (although that process is far from finished yet). The number of jump
Dirk> labels has been reduced, the intra-function communication has been
Dirk> simplified and the code has been made somewhat easier (IMO) to understand.
Dirk> Things are going slowly, but they are proceeding :-)
Yes, I had noticed, although I'm not sure I'd call the code
understandable yet :-) (not by me, anyway) Good luck!
>> >From the debugging point of view, the requirements are that
>>
>> - breakpoint positions are preserved as code is transformed
>>
>> - when a breakpoint is hit, it is possible to map back from the
>> transformed breakpoint location to the coordinates of the breakpoint
>> in the original source.
Dirk> I have to admit that I have not taken a look at how debugging works. If
Dirk> you agree, we can work together: Before doing any changes to the
Dirk> evaluator, I would double check with you.
Sure; the only possible problem is that I don't have much time during
the week these days, so I might slow you down. I'd be happy to check
things over the weekend.
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-08 18:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 6:25 Syntax checks Dirk Herrmann
2002-04-06 15:38 ` Neil Jerram
2002-04-07 7:09 ` Dirk Herrmann
2002-04-08 18:27 ` Neil Jerram [this message]
2002-04-07 10:40 ` Marius Vollmer
2002-04-09 20:48 ` Lynn Winebarger
2002-04-13 9:01 ` Dirk Herrmann
2002-04-13 12:48 ` Neil Jerram
2002-04-13 18:28 ` Lynn Winebarger
2002-04-13 18:10 ` Lynn Winebarger
2002-04-14 18:18 ` Marius Vollmer
2002-04-14 18:11 ` Marius Vollmer
2002-04-23 21:55 ` Thien-Thi Nguyen
2002-04-14 17:52 ` Marius Vollmer
2002-04-29 23:55 ` Lynn Winebarger
2002-05-07 19:24 ` Marius Vollmer
2002-05-09 5:59 ` Lynn Winebarger
2002-04-07 10:05 ` Marius Vollmer
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=m33cy6xczb.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@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.
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).