unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: Guile Users <guile-user@gnu.org>,
	djurfeldt@nada.kth.se, guile-devel@gnu.org
Subject: Re: Guile warts
Date: Thu, 05 Feb 2004 14:03:04 -0500	[thread overview]
Message-ID: <xy7u125qrh3.fsf@nada.kth.se> (raw)
In-Reply-To: <1075664499.3688.125.camel@localhost> (Andy Wingo's message of "Sun, 01 Feb 2004 21:41:39 +0200")

Andy Wingo <wingo@pobox.com> writes:

> I don't want to sound negative. I'm so much happier programming in guile
> scheme than in any other language I've tried. But I do want feedback
> from the devs: are these complaints valid, and is there anyone who is
> working on them? The boot-9 problems are prolly the worst and most
> difficult.

Although I don't have time for Guile development work right now, I
think I can speak for the other developers when saying that your
points are very valid.

Regarding the name space, this is something which should have been
done long ago.  If you want a workaround, note that you can construct
a module with hand-picked bindings:

(define-module (pure-r5rs)
  :pure
  :use-module (ice-9 r5rs))

Also lookup :select in the Guile NEWS file.

M


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


  reply	other threads:[~2004-02-05 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87smkc5b22.fsf@alice.rotty.yi.org>
     [not found] ` <874qwhsa2u.fsf@zip.com.au>
     [not found]   ` <1074535797.1517.64.camel@localhost>
     [not found]     ` <87fze6x5bu.fsf_-_@alice.rotty.yi.org>
     [not found]       ` <xy74quhpgjj.fsf@chunk.mit.edu>
2004-02-01 19:41         ` Guile warts (was: [GOOPS] Specializing <generic> to allow lazy method addition) Andy Wingo
2004-02-05 19:03           ` Mikael Djurfeldt [this message]
2004-02-18 22:22           ` Guile warts 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=xy7u125qrh3.fsf@nada.kth.se \
    --to=djurfeldt@nada.kth.se \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@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).