unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: syncase merged to master
Date: Tue, 21 Apr 2009 00:03:59 +0100	[thread overview]
Message-ID: <87tz4japwg.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m31vrnoyft.fsf@pobox.com> (Andy Wingo's message of "Mon\, 20 Apr 2009 22\:35\:50 +0200")

Andy Wingo <wingo@pobox.com> writes:

> Hi all,
>
> I went ahead and merged the syncase branch to master. So syntax-case /
> syntax-rules macros in master will be hygienic with respect to modules
> in addition to lexical bindings.

Cool, thanks.  I still need to go through your response to my
comments, will do that soon.

> If I might rhapsodize a moment: it's fashionable in the Scheme world to
> criticize Guile. There are four major points:
>
>   1) Syncase macros are unhygienic with respect to modules
>   2) Syncase macros not available by default
>   3) Guile is slow (many flavors of this argument)
>   4) Guile doesn't even do unicode
>
> We're fixing all of these. Within the next couple months. We're doing
> great work, and we should be proud.

Yes indeed, and thanks in large part to you.  As far as the criticism
is concerned, though, I'm not sure what's there is totally rational,
so I wouldn't expect that it will go away.

My impression is that Guile is mentioned quite rarely on the general
Scheme lists; when it is mentioned, it is most often as part of a poll
of implementation behaviours.  Guile had a reputation for a while of
not being completely R5RS compliant - which was true, but based on a
very small number of quite corner cases.  We fixed those, and - as
shown by the list above - the criticism has moved on.  In my view the
biggest point since then has been slowness - which was true also,
although in many scenarios unimportant.  And as you say, we're
addressing that.

(I think there may be a sense, in the wider Scheme community, that (i)
Guile has an unfair advantage in terms of usage because of being the
GNU project's scheme, and (ii) that it isn't quite proper because of
being developed by non-academics; and we could also be criticized for
not taking more part in wider discussions.  Perhaps that is part of
the reason why there is always another criticism.)

> #scheme can go to hell.

FWIW, what I care most about is feedback from Guile's existing users
and from people trying it out.  If _they_ are concerned about hygienic
syncase, I'll try to look into that (and then Andy will actually fix
it :-)).
   
Regards,
        Neil




  parent reply	other threads:[~2009-04-20 23:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 20:35 syncase merged to master Andy Wingo
2009-04-20 20:56 ` Julian Graham
2009-04-20 21:21   ` Andy Wingo
2009-04-20 21:30     ` Julian Graham
2009-04-20 23:28     ` Neil Jerram
2009-04-20 23:03 ` Neil Jerram [this message]
2009-04-28 20:10 ` Ludovic Courtès

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=87tz4japwg.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --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).