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: Smart variables, dumb variables
Date: Wed, 14 Aug 2002 21:43:40 -0500	[thread overview]
Message-ID: <87n0rog7tv.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87y9bajzfp.fsf@zagadka.ping.de> (Marius Vollmer's message of "13 Aug 2002 22:06:50 +0200")

Marius Vollmer <mvo@zagadka.ping.de> writes:

> A future execution model (that is slowly forming in my head) will
> make it so that most variable flags can be tested at compile time.
> Thus, a compiler can emit more efficient code for dumb variables.

Are you thinking about testing the flags on the C side or on the
Scheme side, and if you have more thoughts (even preliminary ones)
about how the compile time tests would work, could you elaborate?  I'm
trying to get a picture in my head of how all this might work
internally, and how it might look in the external API so I can think
about it.  I was also trying to imagine any potential interactions
with the various potential forms of compilation we might consider in
the future (i.e. Scheme -> C, for example).

(only marginally-relevant aside: anyone know the status of C inline
 functions these days -- do other non-gcc compilers support them, do
 we compile under non-gcc compilers, etc.?)

Thanks

-- 
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


  parent reply	other threads:[~2002-08-15  2:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-13 20:06 Smart variables, dumb variables Marius Vollmer
2002-08-14  8:07 ` tomas
2002-08-14 19:35   ` Marius Vollmer
2002-08-14 20:28     ` tomas
2002-08-14 20:48       ` Marius Vollmer
2002-08-14 21:06         ` rm
2002-08-14 21:09           ` Marius Vollmer
2002-08-15  8:06             ` rm
2002-08-15  8:01               ` Lynn Winebarger
2002-08-15  9:51                 ` rm
2002-08-15 14:44               ` Rob Browning
2002-08-15 16:34               ` Marius Vollmer
2002-08-15 17:27                 ` rm
2002-08-15 19:43                   ` Marius Vollmer
2002-08-15 20:02                     ` rm
2002-08-15 20:02                       ` Marius Vollmer
2002-08-15 20:25                         ` rm
2002-08-17 11:59                         ` Neil Jerram
2002-08-19 23:29                         ` Marius Vollmer
2002-08-20 12:01                           ` rm
2002-08-26 22:06                             ` Marius Vollmer
2002-08-15 10:52         ` tomas
2002-08-15 16:36           ` Marius Vollmer
2002-08-14 21:31 ` Rob Browning
2002-08-14 21:45   ` Marius Vollmer
2002-08-15  2:43 ` Rob Browning [this message]
2002-08-15  6:29   ` Marius Vollmer
2002-08-15 14:38     ` Rob Browning

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=87n0rog7tv.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).