[Seaside-dev] Current load-order test failures

[Lukas Renggli]

> I understand that you are trying to provoke Seaside developers to work on
> Squeak/Pharo to improve ANSI compliance. As a contributor to the GemStone
> port of Seaside this leaves me feeling a bit manipulated. In order to
> validate a port (by comparing test results in two environments), I need to
> investigate test failures that have nothing to do with Seaside
> functionality.

FYI, there are 19 senders of #asInteger in the Seaside code, not
counting the tests and the code that is only for the Squeak platform.
I wrote the tests because it caused code to fail on a platform that
has a correct implementation of #asInteger. I assume you agree that it
is worth to test such a functionality?

Maybe you should just make a distinction between tests that fail in
both environments, those that fail in Squeak but not in the other
environment, and those that fail in the other environment but not in
Squeak?

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch