Benoit St-Jean <lamneth at aei.ca> wrote...
>Just curious,
>
>Anybody heard about new developments regarding Exceptions?  Will they be
>implemented in Squeak 2.5?  If so, will they follow the ANSI draft?  Can we
>use Craig Latta's exception package in the meantime (till exceptions make
>it in the image) or another exception package (TFEI, Vassili Bykov, etc).
>
>What's the status on this long debated issue?

Exceptions will not be in 2.5.  however, as soon as 2.5 is out (hopefully later this week (I got called out of town both of the last two weeks)) I'm hoping we can organize ourselves around half a dozen major improvements including exception handling.  I'll send out a message concerning this today.

To quote from my mesage of 7/14, which I'm still following...

>1.  I am NOT going to deal with the big projects [incl exceptions], some of which I listed in my first message on this topic (but keep reading).  Me feeling is that these will take time to sort out appropriately.
>
>2.  I AM going to get out a 2.5 release as soon as I can stop communicating and get to work.
>
>3.  At the time of the 2.5 release, a new version will also be declared on the update servers called, eg, 'Squeak2.6test'.  As before, bug-fixes and no-brainer enhancements will be issued for normal users of the 2.5 release.  Anyone who wishes to be a test pilot can simply advance their version to Squeak2.6test and fetch updates again.  Knowing that only test pilots will receive them, we can cheerfully issue the latest updates weekly (I will still buffer them, since we do occasionally foul up).
>
>4.  Regarding the larger projects that Squeak needs but that we are not controlling, I want to try a new approach.  A couple of people have suggested voting.  I'm not really in favor of this and, what's more, it doesn't address the real problem.  My proposal is that we identify a list of such projects (we have a start already) and then, for each one, identify a group of 3 to 5 competent people to carry it through to completion.  I'm going to suggest that one of these people be from Squeak Central, even if they don't actually do any coding.  This will ensure that any concerns we have will get addressed, that we can track the progress, and that whoever is doing the hard work will know there is buy-in at Squeak Central from the start.  As used above, "to completion" means that it's ready to be issued as an update to the test pilots.