unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@lexort.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: <guile-devel@gnu.org>
Subject: Re: Add internal definitions to derived forms
Date: Wed, 25 Jan 2023 10:38:14 -0500	[thread overview]
Message-ID: <rmiv8ku62vt.fsf@s1.lexort.com> (raw)
In-Reply-To: <87y1pqslab.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 25 Jan 2023 16:09:48 +0100")

Ludovic Courtès <ludo@gnu.org> writes:

> The reason I’m hesitant is that, while I think it’s nice to be able to
> have local ‘define’ in these contexts, I’m wary of diverging from R5RS
> and R6RS.  Since it’s a one-way change (we won’t be able to revert it
> once people rely on it), I thought we’d rather be careful.

My reaction, without thinking much, and being fuzzy on a lot of things
is that part of the point of guile is that it is Scheme which to me
means RnRS conformance.   Of course it's not exactly and every other
Scheme impl is not exactly.  But mostly I think that's a bug as it leads
to incompatible programs.

For example, there are many shell scripts out there that use == in test,
because bash decided to have an extension.  This is not useful, except
perhaps to people writing in sh that think they are writing C :-) but it
does mean that these scripts become limited to bash rather than any
"POSIX sh implementation".

Does the new feature advance the goal of guile as an extension language?

Is this heading for inclusino in the next RnRS?



  reply	other threads:[~2023-01-25 15:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 15:32 Add internal definitions to derived forms Linus Björnstam
2022-11-09 15:46 ` Damien Mattei
2022-11-17  7:25 ` lloda
2022-11-18  9:04   ` Linus Björnstam
2022-11-18  9:27     ` Lassi Kortela
2022-11-18  9:50       ` Linus Björnstam
2022-11-18 10:22         ` Lassi Kortela
2022-11-18 12:53           ` Linus Björnstam
2022-11-18 13:18             ` Lassi Kortela
2023-01-19 17:54             ` lloda
2023-01-20 17:37               ` lloda
2023-01-23 22:13                 ` Ludovic Courtès
2023-01-23 23:28                   ` lloda
2023-01-24  7:33                     ` Linus Björnstam
2023-01-24  9:02                     ` Ludovic Courtès
2023-01-24 17:59                       ` lloda
2023-01-25 10:33                         ` Ludovic Courtès
2023-01-25 15:09 ` Ludovic Courtès
2023-01-25 15:38   ` Greg Troxel [this message]
2023-01-25 21:38     ` Linus Björnstam
2023-01-25 21:06   ` Linus Björnstam
2023-02-02 11:17   ` lloda

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=rmiv8ku62vt.fsf@s1.lexort.com \
    --to=gdt@lexort.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).