unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: compilation
Date: Tue, 23 Apr 2002 10:04:09 -0500	[thread overview]
Message-ID: <87elh65udy.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <200204231216.FAA01993@cmn14.stanford.edu> (Bill Schottstaedt's message of "Tue, 23 Apr 2002 05:16:25 -0700")

Bill Schottstaedt <bil@ccrma.Stanford.EDU> writes:

>  and I'm swamped (as is everyone) with other things to do, so a big
> project to do it right doesn't resonate. But, maybe I'd get seduced
> into helping once it got started.

 :>

At the moment Marius' arguments that we should clean up guile's
execution model with an eye toward future "compilation" before we dive
back in to any particular strategy sound pretty good to me.

I have this suspicion that if this is done right (with hooks in
suitable places and well defined semantics) then it might make it a
lot easier to try out various approaches.  However, without more
investigation, it's possible that I'm just falling victim to wishful
thinking.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


      reply	other threads:[~2002-04-23 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 12:16 compilation Bill Schottstaedt
2002-04-23 15:04 ` Rob Browning [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=87elh65udy.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --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).