Exception >> #description vs. messageText portability

Hi

I had a look at the Gemstone Seaside port and they converted some
Exception >> #description  to Exception >> #messageText. This was also
done in later Seaside versions (Walback and friends).

How do these messages compare from a portability standpoint? Which
should we use were?

Cheers
Philippe
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> How do these messages compare from a portability standpoint? Which
> should we use were?

The two are not just synonyms in Squeak. #messageText returns the
string  provided by the singaller or nil, whereas #description returns
an automatically generated print string of the exception. In most
cases it probably makes sense to use #descriptions, but I am not sure
if we also need #messageText.

The exception hierarchy is really painful for portability. For
example: Warning, Notification, Error, Halt is at completely different
places in VW compared to Squeak. Therefor it is almost impossible to
write compatible handlers.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside