From: Jonathan Bartlett <johnnyb@eskimo.com>
Cc: guile-devel@gnu.org
Subject: Re: Ideas
Date: Sun, 1 Jun 2003 14:46:07 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSU.4.44.0306011445540.28940-100000@eskimo.com> (raw)
In-Reply-To: <87vfvpjy43.fsf@zagadka.ping.de>
Thanks for the code! I'll take a look at it.
Jon
On 1 Jun 2003, Marius Vollmer wrote:
> Jonathan Bartlett <johnnyb@eskimo.com> writes:
>
> > Basically, have a procedure called (end-compile-time-evaluation)
> > which would do the following:
>
> You might want to check out this
>
> http://www-dt.e-technik.uni-dortmund.de/~mvo/guile-unexec.tar.gz
>
> It's very old and unmaintained but i might give you some hints.
>
> --
> GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-06-01 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 22:18 Ideas Jonathan Bartlett
2003-06-01 21:18 ` Ideas Marius Vollmer
2003-06-01 21:46 ` Jonathan Bartlett [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=Pine.GSU.4.44.0306011445540.28940-100000@eskimo.com \
--to=johnnyb@eskimo.com \
--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).