[Seaside] Class Variable Browser Fix
renggli at gmail.com
Thu Jul 14 13:20:43 UTC 2011
Not really, the behavior with the lazy and eager evaluation can be
understood even without looking at the code (#and: expects a block, #&
On Thursday, 14 July 2011, Ted Wrinch <ted.wrinch at gmail.com> wrote:
> Damn - I suspected something like that and did a few tests; but not well enough it seems. It's a shame, as '&' is much simpler to write (some things I was never too keen on in the original Smalltalk). '&&' might be a candidate for an 'and:' alternative; but I could understand people not liking this ugly C syntax either.
> Ted Wrinch
> On 14 Jul 2011, at 09:10, Sven Van Caekenberghe wrote:
>> On 14 Jul 2011, at 09:56, Ted Wrinch wrote:
>>> by using '&' instead of the older 'and:'
>> Ted, beware, these are not equivalent !
>> & always evaluates its argument
>> and: only evaluates its argument when necessary ('short circuit boolean evalution').
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside