[Fluxus] cvs to PLT 3.99

[Dave Griffiths]

Hi Nik,

Good question. Mutibility wise, there is none in the core fluxus code, so
no problems there. However I used list-set! in the asteroids and qflux
games, so I've switched to r5rs mode for them - and I'll rewrite them soon
(or do some new games), so there are better examples! :)

Betablocker suffers from this as well, but my more recent code seems to
work fine without much change.

The main difference I've found is that:

(if (question?) (do-something))

is no longer valid - as if's now always need else expressions, it's
recommended to use this instead:

(when (question?) (do-something))

I guess this helps remove bugs where you mess up the implicit if-then-else
order.

The other big changes are with the module system, mainly from:

(module mymodule mzscheme
  (require (lib "something.ss" "somewhere"))
  ...)

to

#lang scheme
(require somewhere/something)
...

which is much nicer.

cheers,

dave

> hi dave,.
>
> i had a quick look (well, grep actually) and didn't notice too many of
> the obvious mutibility candidates in the existing code. have you noticed
> anything from the user (live coder) perspective that doesn't behave as
> under 372?
>
> nk
>
>> Major work in cvs to port everything to version 3.99 of PLT Scheme.
>> There is probably more work needed, but the examples all run, and it's a
>> bit faster...
>>
>> The major change is probably this one:
>> http://blog.plt-scheme.org/2007/11/getting-rid-of-set-car-and-set-cdr.html
>>
>> I've also removed obj-import/export as they are replaced by
>> load/save-primitive in C++.
>>
>> cheers,
>>
>> dave
>>
>
>