Julian -<div><br></div><div>It was a lot more work to shape my head around the idea than it was to do the code :-)</div><div><br></div><div>John O'Keefe [|], Principal Smalltalk Architect, Instantiations Inc.<br>
<br><br><div class="gmail_quote">On Tue, Jan 6, 2009 at 2:07 PM, Julian Fitzell <span dir="ltr"><<a href="mailto:jfitzell@gmail.com">jfitzell@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Oh, cool. Was it difficult to get working?<br>
<br>
The ANSI standard is confusing and ambiguous in places so it's not<br>
surprising that implementations still vary. The fact that all the<br>
implementations seem to require some modifications to make this work<br>
shows, if nothing else, that nobody else is implementing their own<br>
Exception Selectors, though. :)<br>
<br>
I just tried a simple test on GemStone and it looks like they will<br>
have to implement #try:on:do: at the moment to make it work. Though,<br>
from a quick glance, they may be able to tweak things so only the ANSI<br>
ExceptionSelector protocol is necessary.<br>
<br>
Julian<br>
<br>
On Tue, Jan 6, 2009 at 7:02 PM, John O'Keefe<br>
<<a href="mailto:wembley.instantiations@gmail.com">wembley.instantiations@gmail.com</a>> wrote:<br>
> Julian -<br>
> OK, it now works on VA Smalltalk -- at least the SUnit tests think so :-)<br>
> You are right that many of us implementors of ANSI don't always get it<br>
> correct. Clearly the standard separates the idea of an <exceptionSelector><br>
> from the various other exception protocols.<br>
> John O'Keefe [|], Principal Smalltalk Architect, Instantiations Inc.<br>
><br>
><br>
> On Thu, Jan 1, 2009 at 9:33 AM, Julian Fitzell <<a href="mailto:jfitzell@gmail.com">jfitzell@gmail.com</a>> wrote:<br>
>><br>
>> Hi John,<br>
>><br>
>> Darn... I was following the ANSI standard... ;) it says that an<br>
>> exception selector needs to implement #handles: and #, which we do on<br>
>> both the class and instance side. On most systems this would include<br>
>> the Exception class and instances of ExceptionSet. How does VA<br>
>> implement ExceptionSet if #on:do: is so restrictive?<br>
>><br>
>> Lukas took a quick look at his VA image and says it looks like<br>
>> WAExceptionHandler might just need an implementation of #handles:do:<br>
>> added in the VA port but I don't have a Windows install handy to look<br>
>> myself. I added some tests in Seaside-Tests-Core-jf.32 that should<br>
>> help verify directly if it's working or not, though.<br>
>><br>
>> Do you think it's a solvable problem on VA? I just looked at VW and it<br>
>> looks like they would need to implement #isExceptionHandler in their<br>
>> compatibility package.<br>
>><br>
>> Dale, I haven't got Gemstone installed on this new laptop yet either.<br>
>> Do you foresee problems getting this to work on your end?<br>
>><br>
>> Obviously if this is going to be a huge compatibility problem we<br>
>> should rethink but I think the implementation is cleaner this way<br>
>> otherwise.<br>
>><br>
>> Julian<br>
>><br>
>> On Wed, Dec 31, 2008 at 8:28 PM, John O'Keefe<br>
>> <<a href="mailto:wembley.instantiations@gmail.com">wembley.instantiations@gmail.com</a>> wrote:<br>
>> > Julian -<br>
>> > I'm back to work after a week and got a bad surprise.<br>
>> > Seaside-Core-jf.349 and the associated changes to other packages has<br>
>> > completely broken the VA Smalltalk port. Our implementation of<br>
>> > Block>>#on:do: expects a class as its first argument (and in particular,<br>
>> > the<br>
>> > class must be Exception or a subclass of Exception). The same seems to<br>
>> > be<br>
>> > true of VW.<br>
>> ><br>
>> > But with Seaside-Core-jf.349 #on:do: is getting a WAExceptionHandler<br>
>> > class<br>
>> > (or subclass of it) as the first argument <exception selector> and then<br>
>> > with<br>
>> > Seaside-Core-jf.353 #on:do: is getting an instance of WAExceptionHandler<br>
>> > (or<br>
>> > a subclass of it) as the first argument. In either case, we fall over<br>
>> > because the WAExceptionHandler class/instance does not understand any of<br>
>> > the<br>
>> > messages sent by #on:do: to the <exception selector>.<br>
>> > Since WAExceptionHandler is in the base, I assume it should be portable.<br>
>> > I have reverted to Seaside-Core-lr.348 and Seaside-Development-lr.53 for<br>
>> > the<br>
>> > time being and things seem to be working OK again.<br>
>> > John O'Keefe [|], Principal Smalltalk Architect, Instantiations Inc.<br>
>> _______________________________________________<br>
>> seaside-dev mailing list<br>
>> <a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
>> <a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> seaside-dev mailing list<br>
> <a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
> <a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
><br>
><br>
_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</blockquote></div><br></div>