MCMethodDefinition class>>forMethodReference:
forMethodReference: aMethodReference | definition | definition := self cachedDefinitions at: aMethodReference compiledMethod ifAbsent: []. (definition isNil or: [definition selector ~= aMethodReference methodSymbol] or: [definition className ~= aMethodReference classSymbol] or: [definition classIsMeta ~= aMethodReference classIsMeta] or: [definition category ~= aMethodReference category]) ifTrue: [definition := self className: aMethodReference classSymbol classIsMeta: aMethodReference classIsMeta selector: aMethodReference methodSymbol category: aMethodReference category timeStamp: aMethodReference timeStamp source: aMethodReference source. self cachedDefinitions at: aMethodReference compiledMethod put: definition]. ^ definition MethodReference(Object)>>doesNotUnderstand: #category |
Sorry, not installing but updating...
Em 12-12-2009 15:24, Casimiro de Almeida Barreto escreveu: > MCMethodDefinition class>>forMethodReference: > > forMethodReference: aMethodReference > | definition | > definition := self cachedDefinitions at: aMethodReference > compiledMethod ifAbsent: []. > (definition isNil > or: [definition selector ~= aMethodReference methodSymbol] > or: [definition className ~= aMethodReference classSymbol] > or: [definition classIsMeta ~= aMethodReference classIsMeta] > or: [definition category ~= aMethodReference category]) > ifTrue: [definition := self > className: aMethodReference classSymbol > classIsMeta: aMethodReference classIsMeta > selector: aMethodReference methodSymbol > category: aMethodReference category > timeStamp: aMethodReference timeStamp > source: aMethodReference source. > self cachedDefinitions at: aMethodReference > compiledMethod put: definition]. > ^ definition > > > MethodReference(Object)>>doesNotUnderstand: #category |
In reply to this post by CdAB63
The cause of the problem is that MethodReference >> #category was added to
the System package, while was still included in Monticello as an extension method. I removed it from Monticello in Monticello-ul.335 (IIRC) and added a new mcm, in hope that it will fix this issue. You can continue the update if you recreate the method in the debugger. Levente On Sat, 12 Dec 2009, Casimiro de Almeida Barreto wrote: > MCMethodDefinition class>>forMethodReference: > > forMethodReference: aMethodReference > | definition | > definition := self cachedDefinitions at: aMethodReference compiledMethod > ifAbsent: []. > (definition isNil > or: [definition selector ~= aMethodReference methodSymbol] > or: [definition className ~= aMethodReference classSymbol] > or: [definition classIsMeta ~= aMethodReference classIsMeta] > or: [definition category ~= aMethodReference category]) > ifTrue: [definition := self > className: aMethodReference classSymbol > classIsMeta: aMethodReference classIsMeta > selector: aMethodReference methodSymbol > category: aMethodReference category > timeStamp: aMethodReference timeStamp > source: aMethodReference source. > self cachedDefinitions at: aMethodReference > compiledMethod put: definition]. > ^ definition > > > MethodReference(Object)>>doesNotUnderstand: #category > > |
Em 12-12-2009 15:41, Levente Uzonyi escreveu:
> The cause of the problem is that MethodReference >> #category was > added to the System package, while was still included in Monticello as > an extension method. I removed it from Monticello in Monticello-ul.335 > (IIRC) and added a new mcm, in hope that it will fix this issue. You > can continue the update if you recreate the method in the debugger. > > Problem is still there (update-ul77.mcm / Multilingual-ar75 / Snapshotting Methods & bang. Now tried from a clean image. > Levente > > > On Sat, 12 Dec 2009, Casimiro de Almeida Barreto wrote: > >> MCMethodDefinition class>>forMethodReference: >> >> forMethodReference: aMethodReference >> | definition | >> definition := self cachedDefinitions at: aMethodReference >> compiledMethod ifAbsent: []. >> (definition isNil >> or: [definition selector ~= aMethodReference methodSymbol] >> or: [definition className ~= aMethodReference classSymbol] >> or: [definition classIsMeta ~= aMethodReference classIsMeta] >> or: [definition category ~= aMethodReference category]) >> ifTrue: [definition := self >> className: aMethodReference classSymbol >> classIsMeta: aMethodReference classIsMeta >> selector: aMethodReference methodSymbol >> category: aMethodReference category >> timeStamp: aMethodReference timeStamp >> source: aMethodReference source. >> self cachedDefinitions at: aMethodReference >> compiledMethod put: definition]. >> ^ definition >> >> >> MethodReference(Object)>>doesNotUnderstand: #category >> >> > > |
In reply to this post by Levente Uzonyi-2
FYI -
I think I have a fix but I need to test it so I'll be breaking the update temporarily again before posting it. You have been warned :-) Cheers, - Andreas Levente Uzonyi wrote: > The cause of the problem is that MethodReference >> #category was added > to the System package, while was still included in Monticello as an > extension method. I removed it from Monticello in Monticello-ul.335 > (IIRC) and added a new mcm, in hope that it will fix this issue. You can > continue the update if you recreate the method in the debugger. > > > Levente > > > On Sat, 12 Dec 2009, Casimiro de Almeida Barreto wrote: > >> MCMethodDefinition class>>forMethodReference: >> >> forMethodReference: aMethodReference >> | definition | >> definition := self cachedDefinitions at: aMethodReference >> compiledMethod ifAbsent: []. >> (definition isNil >> or: [definition selector ~= aMethodReference methodSymbol] >> or: [definition className ~= aMethodReference classSymbol] >> or: [definition classIsMeta ~= aMethodReference classIsMeta] >> or: [definition category ~= aMethodReference category]) >> ifTrue: [definition := self >> className: aMethodReference classSymbol >> classIsMeta: aMethodReference classIsMeta >> selector: aMethodReference methodSymbol >> category: aMethodReference category >> timeStamp: aMethodReference timeStamp >> source: aMethodReference source. >> self cachedDefinitions at: aMethodReference >> compiledMethod put: definition]. >> ^ definition >> >> >> MethodReference(Object)>>doesNotUnderstand: #category >> >> > > |
We should be all clear now. My little change to MC seems to have done
the trick. Thanks for your patience. Cheers, - Andreas Andreas Raab wrote: > FYI - > > I think I have a fix but I need to test it so I'll be breaking the > update temporarily again before posting it. You have been warned :-) > > Cheers, > - Andreas > > Levente Uzonyi wrote: >> The cause of the problem is that MethodReference >> #category was >> added to the System package, while was still included in Monticello as >> an extension method. I removed it from Monticello in Monticello-ul.335 >> (IIRC) and added a new mcm, in hope that it will fix this issue. You >> can continue the update if you recreate the method in the debugger. >> >> >> Levente >> >> >> On Sat, 12 Dec 2009, Casimiro de Almeida Barreto wrote: >> >>> MCMethodDefinition class>>forMethodReference: >>> >>> forMethodReference: aMethodReference >>> | definition | >>> definition := self cachedDefinitions at: aMethodReference >>> compiledMethod ifAbsent: []. >>> (definition isNil >>> or: [definition selector ~= aMethodReference methodSymbol] >>> or: [definition className ~= aMethodReference classSymbol] >>> or: [definition classIsMeta ~= aMethodReference classIsMeta] >>> or: [definition category ~= aMethodReference category]) >>> ifTrue: [definition := self >>> className: aMethodReference classSymbol >>> classIsMeta: aMethodReference classIsMeta >>> selector: aMethodReference methodSymbol >>> category: aMethodReference category >>> timeStamp: aMethodReference timeStamp >>> source: aMethodReference source. >>> self cachedDefinitions at: aMethodReference >>> compiledMethod put: definition]. >>> ^ definition >>> >>> >>> MethodReference(Object)>>doesNotUnderstand: #category >>> >>> >> >> > > > |
On Sat, 12 Dec 2009, Andreas Raab wrote:
> We should be all clear now. My little change to MC seems to have done the > trick. Thanks for your patience. > Thanks for the fix, and sorry for breaking the update process. Levente > Cheers, > - Andreas > > Andreas Raab wrote: >> FYI - >> >> I think I have a fix but I need to test it so I'll be breaking the update >> temporarily again before posting it. You have been warned :-) >> >> Cheers, >> - Andreas >> >> Levente Uzonyi wrote: >>> The cause of the problem is that MethodReference >> #category was added to >>> the System package, while was still included in Monticello as an extension >>> method. I removed it from Monticello in Monticello-ul.335 (IIRC) and added >>> a new mcm, in hope that it will fix this issue. You can continue the >>> update if you recreate the method in the debugger. >>> >>> >>> Levente >>> >>> >>> On Sat, 12 Dec 2009, Casimiro de Almeida Barreto wrote: >>> >>>> MCMethodDefinition class>>forMethodReference: >>>> >>>> forMethodReference: aMethodReference >>>> | definition | >>>> definition := self cachedDefinitions at: aMethodReference >>>> compiledMethod ifAbsent: []. >>>> (definition isNil >>>> or: [definition selector ~= aMethodReference methodSymbol] >>>> or: [definition className ~= aMethodReference classSymbol] >>>> or: [definition classIsMeta ~= aMethodReference classIsMeta] >>>> or: [definition category ~= aMethodReference category]) >>>> ifTrue: [definition := self >>>> className: aMethodReference classSymbol >>>> classIsMeta: aMethodReference classIsMeta >>>> selector: aMethodReference methodSymbol >>>> category: aMethodReference category >>>> timeStamp: aMethodReference timeStamp >>>> source: aMethodReference source. >>>> self cachedDefinitions at: aMethodReference >>>> compiledMethod put: definition]. >>>> ^ definition >>>> >>>> >>>> MethodReference(Object)>>doesNotUnderstand: #category >>>> >>>> >>> >>> >> >> >> > > > |
Levente Uzonyi wrote:
> On Sat, 12 Dec 2009, Andreas Raab wrote: > >> We should be all clear now. My little change to MC seems to have done >> the trick. Thanks for your patience. > > Thanks for the fix, and sorry for breaking the update process. You're welcome. This was one of those MC edge cases that come from having the server do the diff instead of downloading the full version and do the diff locally. I'm wondering if this should require an additional verification step along the lines of the local version first checking for any existing local modifications and somehow unify those with the changes coming from the server. Anyway. Cheers, - Andreas > > > Levente > >> Cheers, >> - Andreas >> >> Andreas Raab wrote: >>> FYI - >>> >>> I think I have a fix but I need to test it so I'll be breaking the >>> update temporarily again before posting it. You have been warned :-) >>> >>> Cheers, >>> - Andreas >>> >>> Levente Uzonyi wrote: >>>> The cause of the problem is that MethodReference >> #category was >>>> added to the System package, while was still included in Monticello >>>> as an extension method. I removed it from Monticello in >>>> Monticello-ul.335 (IIRC) and added a new mcm, in hope that it will >>>> fix this issue. You can continue the update if you recreate the >>>> method in the debugger. >>>> >>>> >>>> Levente >>>> >>>> >>>> On Sat, 12 Dec 2009, Casimiro de Almeida Barreto wrote: >>>> >>>>> MCMethodDefinition class>>forMethodReference: >>>>> >>>>> forMethodReference: aMethodReference >>>>> | definition | >>>>> definition := self cachedDefinitions at: aMethodReference >>>>> compiledMethod ifAbsent: []. >>>>> (definition isNil >>>>> or: [definition selector ~= aMethodReference methodSymbol] >>>>> or: [definition className ~= aMethodReference classSymbol] >>>>> or: [definition classIsMeta ~= aMethodReference classIsMeta] >>>>> or: [definition category ~= aMethodReference category]) >>>>> ifTrue: [definition := self >>>>> className: aMethodReference classSymbol >>>>> classIsMeta: aMethodReference classIsMeta >>>>> selector: aMethodReference methodSymbol >>>>> category: aMethodReference category >>>>> timeStamp: aMethodReference timeStamp >>>>> source: aMethodReference source. >>>>> self cachedDefinitions at: aMethodReference >>>>> compiledMethod put: definition]. >>>>> ^ definition >>>>> >>>>> >>>>> MethodReference(Object)>>doesNotUnderstand: #category >>>>> >>>>> >>>> >>>> >>> >>> >>> >> >> >> > > |
Free forum by Nabble | Edit this page |