Re: [Swarm-Support] Followup: found work-aroundfor missing~/swarmarchiver.scm too

[Bill Northcott]

I don't know what the others feel, but I for one am very unhappy  
about this change.

This seems to me to be deliberately introducing a bug (behaviour not  
consistent with documentation).  What is worse, from what I have read  
in discussions and Paul has seen at Swarmfest, there are a number of  
Objective-C programmers out there who rely on the documented  
behaviour of messages to nil.

If we want to preserve old Swarm code which relies on old  
(undocumented) behaviour then it should be optional not the default.   
The existing way, before Marcus' recent change, of having some  
compile time option for the library behaviour seems to be  
appropriate, but even that should be documented.   I am happy to do  
that.

Bill Northcott

On 20/08/2006, at 12:18 PM, Marcus G. Daniels wrote:

> Paul wrote:
> > when Swarm used to crash on messages to nil, it would have stopped  
> > and forced me to fix it.  This newer behavior of ignoring messages  
> > to nil allows the problem to slide by.
> I've changed it back in CVS.   It will send a message to stderr and  
> then abort.
> _______________________________________________
> Support mailing list
> address@hidden
> http://www.swarm.org/mailman/listinfo/support