Epicea redoVisitor does not handle protocol changes
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
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 <stepharo@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
Ah, you can try: Metacello new smalltalkhubUser: 'MartinDias' project: 'Epicea'; configuration: 'Epicea'; version: '7.98'; load. you should be working in a Pharo 6 that has an old Epicea version. Martin On Tue, Aug 9, 2016 at 11:19 AM, Martin Dias <tinchodias@gmail.com> wrote:
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 <stepharo@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
Ah, you can try:
Metacello new smalltalkhubUser: 'MartinDias' project: 'Epicea'; configuration: 'Epicea'; version: '7.98'; load.
you should be working in a Pharo 6 that has an old Epicea version.
ah yes I should migrate. I took an old pillar image. I will change now. Stef
Martin
On Tue, Aug 9, 2016 at 11:19 AM, Martin Dias <tinchodias@gmail.com <mailto:tinchodias@gmail.com>> wrote:
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 <stepharo@free.fr <mailto:stepharo@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
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 <stepharo@free.fr <mailto:stepharo@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
participants (2)
-
Martin Dias -
stepharo