Smalltalk › Squeak › Squeak - Dev

Gutting the Exceptions package

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Frank Shearar-3

Gutting the Exceptions package

I like packages that are functionally related. Compression is an
excellent example of this.

Exceptions is not. It's a bunch of things grouped together just
because they do the same kind of thing.

I ripped a number of Exception's classes and put then in Kernel (the
base of the exception handling system), Collections (because
KeyNotFound's part of how Dictionary works), and so on.

The remaining exceptions are:
* Abort.
* EndOfStream (which looks unused),
* ProgressNotification,
* a bunch of Project notifications.

I propose we gut the Exceptions package:
* move Project notifications to System,
* move ProgressNotification to Kernel (I'd prefer a better place, but...),
* move PickAFileToWriteNotification to MorphicExtras (where all its users live)

I don't know what to do with Abort. Sounds Kernel-ish, but there
aren't any users.

This would empty Exceptions completely.

frank

Nicolas Cellier

Re: Gutting the Exceptions package

Either you keep EndOfStream in Streams (Collection-Streams) or simply put it in proper Deprecated package

I was one user of it with SqueaXTream experiments www.squeaksource.com/XTream.html, but I do not much care.

2013/7/22 Frank Shearar <[hidden email]>

I like packages that are functionally related. Compression is an
excellent example of this.

Exceptions is not. It's a bunch of things grouped together just
because they do the same kind of thing.

I ripped a number of Exception's classes and put then in Kernel (the
base of the exception handling system), Collections (because
KeyNotFound's part of how Dictionary works), and so on.

The remaining exceptions are:
* Abort.
* EndOfStream (which looks unused),
* ProgressNotification,
* a bunch of Project notifications.

I propose we gut the Exceptions package:
* move Project notifications to System,
* move ProgressNotification to Kernel (I'd prefer a better place, but...),
* move PickAFileToWriteNotification to MorphicExtras (where all its users live)

I don't know what to do with Abort. Sounds Kernel-ish, but there
aren't any users.

This would empty Exceptions completely.

frank

Casey Ransberger-2

Re: Gutting the Exceptions package

In reply to this post by Frank Shearar-3

I like it. If abort isn't obsolete or Kernel maybe it's System.

On Jul 22, 2013, at 7:09 AM, Frank Shearar <[hidden email]> wrote:

> I like packages that are functionally related. Compression is an
> excellent example of this.
>
> Exceptions is not. It's a bunch of things grouped together just
> because they do the same kind of thing.
>
> I ripped a number of Exception's classes and put then in Kernel (the
> base of the exception handling system), Collections (because
> KeyNotFound's part of how Dictionary works), and so on.
>
> The remaining exceptions are:
> * Abort.
> * EndOfStream (which looks unused),
> * ProgressNotification,
> * a bunch of Project notifications.
>
> I propose we gut the Exceptions package:
> * move Project notifications to System,
> * move ProgressNotification to Kernel (I'd prefer a better place, but...),
> * move PickAFileToWriteNotification to MorphicExtras (where all its users live)
>
> I don't know what to do with Abort. Sounds Kernel-ish, but there
> aren't any users.
>
> This would empty Exceptions completely.
>
> frank
>