From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Bugs <bug-guile@gnu.org>
Subject: Re: Fix for 1001-local-eval-error-backtrace-segfaults - please review
Date: 07 May 2002 20:30:17 +0100 [thread overview]
Message-ID: <m3adrbeoxi.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <87bsbrls99.fsf@zagadka.ping.de>
>>>>> "Marius" == Marius Vollmer <mvo@zagadka.ping.de> writes:
Marius> Neil Jerram <neil@ossau.uklinux.net> writes:
>> Basically, avoid modifying the environment in hand by making new list
>> structure instead. This is similar to almost all the other cases in
>> unmemocopy, which use EXTEND_ENV.
Marius> Great! (In case you are waiting for a go ahead: Go Ahead! :)
>> Fix isn't very elegant, though; is there a nicer way of doing this?
Marius> I don't think we should worry too much about elegance in this part of
Marius> the code.
OK. Any thoughts on whether this is worth putting into the stable
branch as well? I assume it's Rob's decision...
Neil
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-05-07 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 12:59 Fix for 1001-local-eval-error-backtrace-segfaults - please review Neil Jerram
2002-05-03 3:50 ` Thien-Thi Nguyen
2002-05-05 14:00 ` Neil Jerram
2002-05-15 12:43 ` Thien-Thi Nguyen
2002-05-18 13:47 ` Neil Jerram
2002-05-07 18:36 ` Marius Vollmer
2002-05-07 19:30 ` Neil Jerram [this message]
2002-05-07 19:39 ` Marius Vollmer
2002-05-11 15:52 ` Neil Jerram
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=m3adrbeoxi.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bug-guile@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).