Re: [Pharo-users] not yet / should be implemented

[Thierry Goubier]

Le 28/09/2015 21:53, Peter Uhnák a écrit :
On Mon, Sep 28, 2015 at 9:36 PM, Thierry Goubier
<thierry.goub...@gmail.com <mailto:thierry.goub...@gmail.com>> wrote:
    Le 28/09/2015 21:09, Peter Uhnák a écrit :

        What is the difference?

        —————————————————————————————————————
        *ShouldBeImplemented*
        *
        *
        I am ShouldBeImplemented, an exception signaled when some method
        should
        have been implemented but was not.


    Usually in a abstract class to signal that a concrete subclass
    should have implemented that method... defines the API all
    subclasses must answer to.


Well the abstract class uses SubclassResponsibility;
SBI is autogenerated by debugger and Class Refactoring > Realize.

Yes, you're right. I tend to mix the two :(

    Hum, should be and not yet have different semantics.


Oh, so it's actually ShouldHaveBeenImplemented (past tense --- as in:
"it was supposed to be already done").

so

ShouldBeImplemented - this was supposed to be already implemented
NotYetImplemented - this will be implemented in very soon

Would be interesting to see that in code, to have a feel about how to 
use it.

Thierry

Okay, now understand it.

Thanks :)

Peter