perhaps I've missed something ...
John Clements
(20 Jan 2000 22:21 UTC)
|
Re: perhaps I've missed something ...
Lars Thomas Hansen
(20 Jan 2000 22:38 UTC)
|
Re: perhaps I've missed something ...
Shriram Krishnamurthi
(20 Jan 2000 22:52 UTC)
|
Re: perhaps I've missed something ...
Lars Thomas Hansen
(20 Jan 2000 23:02 UTC)
|
Re: perhaps I've missed something ...
John Clements
(20 Jan 2000 22:58 UTC)
|
Re: perhaps I've missed something ...
Lars Thomas Hansen
(20 Jan 2000 23:05 UTC)
|
Re: perhaps I've missed something ...
John Clements
(20 Jan 2000 23:12 UTC)
|
Re: perhaps I've missed something ...
sperber@xxxxxx
(21 Jan 2000 07:38 UTC)
|
Re: perhaps I've missed something ...
Lars Thomas Hansen
(20 Jan 2000 22:44 UTC)
|
Re: perhaps I've missed something ...
John Clements
(20 Jan 2000 23:09 UTC)
|
Re: perhaps I've missed something ...
Per Bothner
(20 Jan 2000 23:01 UTC)
|
Re: perhaps I've missed something ...
Matthias Felleisen
(20 Jan 2000 23:18 UTC)
|
Re: perhaps I've missed something ...
Per Bothner
(20 Jan 2000 23:55 UTC)
|
Re: perhaps I've missed something ...
Matthias Felleisen
(21 Jan 2000 01:04 UTC)
|
Re: perhaps I've missed something ...
Per Bothner
(21 Jan 2000 01:49 UTC)
|
Re: perhaps I've missed something ...
Matthias Felleisen
(21 Jan 2000 02:40 UTC)
|
Re: perhaps I've missed something ...
thi
(21 Jan 2000 09:58 UTC)
|
Re: perhaps I've missed something ...
Per Bothner
(21 Jan 2000 18:36 UTC)
|
Re: perhaps I've missed something ...
sperber@xxxxxx
(22 Jan 2000 10:32 UTC)
|
Re: perhaps I've missed something ...
Per Bothner
(23 Jan 2000 20:02 UTC)
|
Re: perhaps I've missed something ...
Shriram Krishnamurthi
(23 Jan 2000 20:50 UTC)
|
Re: perhaps I've missed something ...
Per Bothner
(23 Jan 2000 21:25 UTC)
|
Re: perhaps I've missed something ...
sperber@xxxxxx
(24 Jan 2000 07:30 UTC)
|
Re: perhaps I've missed something ...
Michael Livshin
(24 Jan 2000 16:55 UTC)
|
Re: perhaps I've missed something ... sperber@xxxxxx (25 Jan 2000 07:43 UTC)
|
Re: perhaps I've missed something ...
Michael Livshin
(25 Jan 2000 11:02 UTC)
|
Re: perhaps I've missed something ...
sperber@xxxxxx
(25 Jan 2000 11:31 UTC)
|
Re: perhaps I've missed something ...
Matthias Felleisen
(25 Jan 2000 13:47 UTC)
|
Re: perhaps I've missed something ...
sperber@xxxxxx
(24 Jan 2000 07:29 UTC)
|
Re: perhaps I've missed something ...
John Clements
(20 Jan 2000 23:59 UTC)
|
Re: perhaps I've missed something ...
Per Bothner
(21 Jan 2000 00:18 UTC)
|
Re: perhaps I've missed something ...
Shriram Krishnamurthi
(21 Jan 2000 00:03 UTC)
|
Re: perhaps I've missed something ...
Per Bothner
(21 Jan 2000 00:37 UTC)
|
Re: perhaps I've missed something ...
Shriram Krishnamurthi
(21 Jan 2000 08:39 UTC)
|
>>>>> "Michael" == Michael Livshin <xxxxxx@bigfoot.com> writes: Michael> xxxxxx@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: >> >> [ snipped discussion about education ] Michael> hi there, all of you. I am but a humble programmer, 5 years away from Michael> the academia, and here is my view on the subject of "set!" Michael> overloading. if you are only interested in academically rigorous Michael> discussion, don't bother reading further. Michael> 1. what I, in my naivete about PL design, take "set!" to be? Michael> (set! <name> <value>) translates, in my mind, to: dear Scheme, please Michael> make it so that next time I say <name>, and <name> denotes the same Michael> thing as now, I get <value>. But this intuition is wrong, because SET! has interaction with *place* (in the program source code) in addition to interaction with time. (define x 23) (let ((x 5)) (set! x 17)) x => 23 This is precisely the case students struggle with. The intuition is right for data structure mutators. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla