From: Per Bothner <per@bothner.com>
To: Mark Raynsford <list+org.sourceware.kawa@io7m.com>
Cc: kawa@sourceware.org
Subject: Re: Difference in define behaviour between kawa.jar and embedded Scheme example
Date: Thu, 23 Nov 2017 12:51:00 -0000 [thread overview]
Message-ID: <272ebb79-2749-b158-e922-04940a5789b5@bothner.com> (raw)
In-Reply-To: <20171123105212.0e8cbd1d@copperhead.int.arc7.info>
On 11/23/2017 11:52 AM, Mark Raynsford wrote:
>
> OK, thanks. This is something I'm going to be looking into at the
> source. As you know, I'm putting together a gratuitously incompatible
> subset of the language, so I have no need for compatibility with
> tradition. I'd rather get hard errors up front. To be honest, I'd
> rather all redefines at the top-level be errors, but I assume this is
> something I'm going to have to implement myself.
Re-definitions are not allowed in files (modules), but they are allowed
in line-by-line mode (a REPL or a file processed with -f).
> I actually ran into this behaviour because I was informally testing my
> subclasses of Scheme/SchemeCompilation and was surprised that I could
> override existing bindings like this (because being able to affect the
> internals of existing definitions wasn't the behaviour I was used to
> from other Schemes).
Surely in most Schemes if f is implemented using gm and g is redefined,
then f will use the new definition (at least in a REPL)?
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2017-11-23 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 22:33 Mark Raynsford
2017-11-23 2:26 ` Per Bothner
2017-11-23 10:52 ` Mark Raynsford
2017-11-23 12:51 ` Per Bothner [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=272ebb79-2749-b158-e922-04940a5789b5@bothner.com \
--to=per@bothner.com \
--cc=kawa@sourceware.org \
--cc=list+org.sourceware.kawa@io7m.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).