Email list hosting service & mailing list manager

where is srfi-17 going? Per Bothner (23 Jan 2000 21:32 UTC)
where is srfi-17 going? Shriram Krishnamurthi (23 Jan 2000 22:03 UTC)
Re: where is srfi-17 going? Per Bothner (23 Jan 2000 23:18 UTC)
Re: where is srfi-17 going? Shriram Krishnamurthi (24 Jan 2000 02:17 UTC)
Re: where is srfi-17 going? Michael Livshin (24 Jan 2000 11:01 UTC)
Re: where is srfi-17 going? Mikael Djurfeldt (24 Jan 2000 16:27 UTC)
Re: where is srfi-17 going? Mikael Djurfeldt (24 Jan 2000 17:25 UTC)

where is srfi-17 going? Shriram Krishnamurthi 23 Jan 2000 22:03 UTC

Per Bothner wrote:

> One reason for using a single name is that I'm interested in
> experimenting with alternative syntaxes, including use of infix
> operators. [...]

I fail to see why a new operator, GENERALIZED-MUTATE (say), could not
meet your needs just as well.  You can already define
GENERALIZED-MUTATE as a macro over SET! in your translator's preamble
for the target code.  If you decide it's a good thing to use the same
syntax for both identifier and structure mutation, you can then extend
GENERALIZED-MUTATE's macro.  Why does the chosen name have to be SET!
and nothing else?

Note that I am *not* being critical of either an infix syntax, or of a
conflated mutator, or of anything else.  I just want to know why that
one name, which already has a fixed syntax and semantics in standard
Scheme.  After all, if your source language has := rather than SET!
(which would likely be a poor choice of name in a traditional infix
syntax, since `!' may well mean something else), then your translator
can pick any old name it wishes in the target language.

'shriram