Re: [Pharo-dev] Epicea redoVisitor does not handle protocol changes

[stepharo]

tx martin.

Stef


Le 9/8/16 à 16:19, Martin Dias a écrit :

Hi,

I'm looking at it. Vincent reported it a couple of weeks ago and I fixed it (apparently not?!)

Martin

On Tue, Aug 9, 2016 at 8:56 AM, stepharo <steph...@free.fr <mailto:steph...@free.fr>> wrote:

    Hi

    I just tried to replay a change today in Pharo60 and I got an
    error in epicea.

    EpRedoVisitor>>visitEvent: aChange
        ^ self error: 'Should not be reached'.

    EpRedoVisitor>>visitCodeChange: aChange
        "Default behavior for any change."

        ^ self visitEvent: aChange

    EpRedoVisitor>>visitBehaviorChange: aChange
        ^ self visitCodeChange: aChange

    EpRedoVisitor>>visitProtocolChange: aProtocolAddition
        ^ self visitBehaviorChange: aProtocolAddition.


    visitProtocolAddition: aProtocolAddition
        ^ self visitProtocolChange: aProtocolAddition


    Apparently it was a

        EpProtocolAddition


    And the RedoVisitor does not handle them.

    I do not have the time to check further - I just want to rescue my
    code for now.


    Stef