[FIX] nil and #nil and a fix for RxParser

Andrew P. Black black at cs.pdx.edu
Tue Dec 7 09:08:41 UTC 2004


Did the meaning of

	array  :=  #(12 nil foo)

change at some point?   array last is of course #foo.  array first is 
1. array third is now nil.  Was array third #nil at some point in the 
past?

I'm asking because  RxParser class >> 
test:with:expect:withSubexpressions: is driven off a table of array 
literals.  It has a test "subxpr ~= #nil" that now has to be modified 
to read "subxpr ~= nil" to get the tests to run.

I'm sure that Vassilli would have had this right at some time in the 
past, maybe in "Some Other Smalltalk".  Is this an incompatibility 
with VisualWorks?

	Andrew
-------------- next part --------------
Skipped content of type multipart/appledouble


More information about the Squeak-dev mailing list