unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Wolfgang J Moeller <wjm@heenes.com>
To: Andy Wingo <wingo@pobox.com>
Cc: Wolfgang J Moeller <wjm@heenes.com>, guile-devel@gnu.org
Subject: Re: enhancement requests
Date: Tue, 29 Mar 2011 16:40:55 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1103291554580.7221@gwdw03.gwdg.de> (raw)
In-Reply-To: <m38vvy9rwx.fsf@unquote.localdomain>

On Tue, 29 Mar 2011, Andy Wingo wrote:

>[...]
> >  (a) undo MACRO definitions - you can't re-DEFINE a name after DEFINE-SYNTAX;
>
> You can certainly re-define a name after define-syntax.  This used to
> not be the case, at least with psyntax, but this changed at some point
> in upstream psyntax, and I merged in similar functionality in our copy
> sometime last year or the year before.

Sorry. I could have sworn ... but I must have confused it with GUILE 1.8.

> >  (b) recover built-in functions once you have re-defined them;
>
> Hummmm.  However, functions which have been defined in your module in
> terms of your local functions might keep a hold on your local functions.
> Whether this happens depends on whether the code in question has been
> run or not, and whether the code was introduced from a macro or not.
> For the mechanism, see "Compiled Procedures are VM Programs" in the
> manual.
>
> Basically I'm hesitant to include such functionality in Guile itself,
> because it gets harder for me (as maintainer, bug-hunter, etc) to reason
> about users' code after you ,undefine.

OK, that's a rather exotic point. I came across it since my "prelude"
traditionally re-defines the "while" macro [to work as it should have
in GUILE 1.6, i.e. allowing for an optional result argument to "break"].

> >  (c) test code that uses UNDEFINED? .
>
> How is this different from (not (defined? 'sym)) ?  And what kind of
> code would you use this for?

Sorry, in fact I did mean the function "defined?".
Used in my prelude, because GUILE - my first Scheme - used to provide it.

===

On Thu 17 Mar 2011 12:50, Andy Wingo <wingo@pobox.com> writes:

>>> (3) documentation: Please do document that ~/.guile is (often) invoked
>>>     automatically (old omission), and what options (including
>>>     _undocumented_ "-q") inhibit this.
>>
>> Will do.
>
> Done.

Thanks a lot!

Best regards,

Wolfgang J. Moeller, Tel. +49 551 47361, wjm<AT>heenes.com
37085 Goettingen, Germany | Disclaimer: No claim intended!
http://www.wjmoeller.de/ -+-------- http://www.heenes.com/



  reply	other threads:[~2011-03-29 14:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 11:50 enhancement requests Andy Wingo
2011-03-21  0:24 ` Wolfgang J Moeller
2011-03-21  8:23   ` Andy Wingo
2011-03-29  9:50   ` Andy Wingo
2011-03-29 14:40     ` Wolfgang J Moeller [this message]
2011-04-15  9:29   ` Andy Wingo
2011-04-18  9:53     ` Wolfgang J Moeller
2011-04-21  9:34       ` Andy Wingo
2011-04-21 10:21         ` enhancement requests ("load-ignoring-cached-go") Wolfgang J Moeller
2011-04-21 14:04           ` Andy Wingo
2011-04-21 15:56             ` Wolfgang J Moeller
2011-06-30 11:38               ` Andy Wingo
2011-04-23 19:17             ` Mark Harig
2011-03-29 10:18 ` enhancement requests Andy Wingo

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=alpine.LNX.2.00.1103291554580.7221@gwdw03.gwdg.de \
    --to=wjm@heenes.com \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /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).