unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: new-model.text, please comment
Date: 13 Sep 2002 19:53:05 +0100	[thread overview]
Message-ID: <m3admlyb5a.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <871y80tn9r.fsf@zagadka.ping.de>

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

    Marius>   guile/workbook/compilation/new-model.text

    Marius> Please have a look and comment on it.

Here are my few thoughts.  I don't have much experience or expertise
in this area, so feel free to explain the obvious to me if that's what
I've asked for :-)

    Marius> The output of the compiler is not specified.  Also,
    Marius> execution of languages other than Scheme is not
    Marius> considered.  It is assumed that additional languages are
    Marius> first translated to Scheme (or whatever variant of Scheme
    Marius> we offer) and then compiled normally."

High level thought -- is all of this new thinking necessary?  Are we
unnecessarily ignoring useful stuff that has already been worked
through on other projects?

    Marius> A module contains a set of bindings, and a binding is a
    Marius> pair consisting of a symbol and another object.  The other
    Marius> object in a binding can be a macro transformer or a
    Marius> variable.

    Marius> When a module is created, the set of bindings is empty.
    Marius> You can add bindings to the set, but you can not remove
    Marius> them.  Existing bindings can not be changed.  There can be
    Marius> at most one binding with a given symbol.

So it is impossible to change an existing macro definition?

    Marius> During compilation of a file that defines a module, that
    Marius> module is partially constructed (via code executed by
    Marius> eval-case).  The constructed module is made the current
    Marius> module, but it is not registered in the system.  Requests
    Marius> for a module with the name of the module-being-compiled
    Marius> will not find the partially constructed module.  When the
    Marius> compiler wants to follow a :module-ref statement with an
    Marius> explicit name, it must check whether that name refers to
    Marius> the partially constructed current module.

Don't understand the point here.  What are you trying to say by "will
not find the partially constructed module"?

Regards,
        Neil



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


  parent reply	other threads:[~2002-09-13 18:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11 18:05 new-model.text, please comment Marius Vollmer
2002-09-12 22:48 ` Tom Lord
2002-09-14 22:48   ` Marius Vollmer
2002-09-15  0:50     ` Tom Lord
2002-09-15  0:55     ` Tom Lord
2002-09-21 20:27       ` Marius Vollmer
2002-09-12 23:28 ` Rob Browning
2002-09-13 20:22   ` Marius Vollmer
2002-09-13 20:34     ` Rob Browning
2002-09-13 18:53 ` Neil Jerram [this message]
2002-09-13 22:06   ` Rob Browning
2002-09-14  1:15     ` Lynn Winebarger
2002-09-14 22: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=m3admlyb5a.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).