The Trunk: Exceptions-fbs.43.mcz

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

The Trunk: Exceptions-fbs.43.mcz

commits-2
Frank Shearar uploaded a new version of Exceptions to project The Trunk:
http://source.squeak.org/trunk/Exceptions-fbs.43.mcz

==================== Summary ====================

Name: Exceptions-fbs.43
Author: fbs
Time: 5 February 2013, 11:06:32.257 pm
UUID: 1a5409d5-3bfb-4728-9945-6898e8c3adca
Ancestors: Exceptions-cmm.37
Backported From: Exceptions-fbs.42

Stay in the debugger for longer. Part 2 of 3.

New exception hierarchy lets interesting parties catch NotImplemented errors to encourage developers to implement missing parts.

=============== Diff against Exceptions-cmm.37 ===============

Item was changed:
+ NotImplemented subclass: #MessageNotUnderstood
- Error subclass: #MessageNotUnderstood
  instanceVariableNames: 'message receiver reachedDefaultHandler'
  classVariableNames: ''
  poolDictionaries: ''
  category: 'Exceptions-Kernel'!
 
  !MessageNotUnderstood commentStamp: '<historical>' prior: 0!
  This exception is provided to support Object>>doesNotUnderstand:.!

Item was added:
+ Error subclass: #NotImplemented
+ instanceVariableNames: ''
+ classVariableNames: ''
+ poolDictionaries: ''
+ category: 'Exceptions-Kernel'!

Item was changed:
+ NotImplemented subclass: #NotYetImplemented
- Error subclass: #NotYetImplemented
  instanceVariableNames: 'receiverClass selector context'
  classVariableNames: ''
  poolDictionaries: ''
  category: 'Exceptions-Kernel'!
 
  !NotYetImplemented commentStamp: 'jcg 10/21/2009 01:20' prior: 0!
  Sent by #notYetImplemented.  Better than the age-old behavior of opening a notifier window, because this can be caught and handled.
  !

Item was removed:
- ----- Method: NotYetImplemented>>defaultAction (in category 'handling') -----
- defaultAction
- self inform: 'Not yet implemented (', self messageText, ')'!

Item was added:
+ NotImplemented subclass: #SubclassResponsibility
+ instanceVariableNames: ''
+ classVariableNames: ''
+ poolDictionaries: ''
+ category: 'Exceptions-Kernel'!
+
+ !SubclassResponsibility commentStamp: 'fbs 1/26/2013 00:20' prior: 0!
+ I am signalled when a subclass fails to implement an "abstract method" and something sends an instance of this subclass the unimplemented message.!


Reply | Threaded
Open this post in threaded view
|

Re: The Trunk: Exceptions-fbs.43.mcz

Frank Shearar-3
On 7 February 2013 22:33,  <[hidden email]> wrote:

> Frank Shearar uploaded a new version of Exceptions to project The Trunk:
> http://source.squeak.org/trunk/Exceptions-fbs.43.mcz
>
> ==================== Summary ====================
>
> Name: Exceptions-fbs.43
> Author: fbs
> Time: 5 February 2013, 11:06:32.257 pm
> UUID: 1a5409d5-3bfb-4728-9945-6898e8c3adca
> Ancestors: Exceptions-cmm.37
> Backported From: Exceptions-fbs.42
>
> Stay in the debugger for longer. Part 2 of 3.

I really need to (a) learn to count properly and (b) figure out a
better way to do cross-package changes.

I can avoid (a), I guess, by not putting in "n of m" messages!

frank

Reply | Threaded
Open this post in threaded view
|

Re: The Trunk: Exceptions-fbs.43.mcz

David T. Lewis
On Thu, Feb 07, 2013 at 10:40:53PM +0000, Frank Shearar wrote:

> On 7 February 2013 22:33,  <[hidden email]> wrote:
> > Frank Shearar uploaded a new version of Exceptions to project The Trunk:
> > http://source.squeak.org/trunk/Exceptions-fbs.43.mcz
> >
> > ==================== Summary ====================
> >
> > Name: Exceptions-fbs.43
> > Author: fbs
> > Time: 5 February 2013, 11:06:32.257 pm
> > UUID: 1a5409d5-3bfb-4728-9945-6898e8c3adca
> > Ancestors: Exceptions-cmm.37
> > Backported From: Exceptions-fbs.42
> >
> > Stay in the debugger for longer. Part 2 of 3.
>
> I really need to (a) learn to count properly and (b) figure out a
> better way to do cross-package changes.
>
> I can avoid (a), I guess, by not putting in "n of m" messages!
>

I think your "n of m" messages are fine. The occasional cut-and-paste
mistake is fairly obvious to us readers of the comments, and not really
a problem. Personally I like being able to just read a set of update
comments like this, mistakes notwithstanding.

Dave