Hi Ben, ok, I collect all I find and will report them after finishing. >>maybe it would be good for the opening screen of the Pharo 3 release to link to a tutorial on how to run those Deprecated-Rules-only on a package.
The description was clear and easy. I am not sure if I understood.
I made a movie with an example, do you think sth like this? (BTW adding only Pharo3 was not possible - walkback)
Sabine On Fri, Jan 17, 2014 at 1:50 PM, btc [via Smalltalk] <[hidden email]> wrote: Can you report those to be added? |
What you can do is load your code in a Moose image, and tell it to calculate the invocations
In deprecationFinder I used findDeprecationsFor: aVersion in: aProject | mooseModel | mooseModel := (MooseMonticelloHTTPImporter new setRepositoryCache: aProject monticelloRepository; importFileNamed: (aVersion at: #filename)). mooseModel allInvocations do: [ :each| aProject addInvocation: each inVersion: aVersion ] and addInvocation: aFAMIXInvocation inVersion: aDictionary |sigs| self signatures add: aFAMIXInvocation signature. sigs := aDictionary at: #signatures ifAbsentPut: Set new. sigs add: aFAMIXInvocation signature. monticelloRepository ^ MCSmalltalkhubRepository owner: self owner project: self projectName You can then at least check if methods with the same signature are still in the Pharo3 image If you use a Pharo2 based Moose to build the list, you’ll be able to resolve more invocations Stephan |
Free forum by Nabble | Edit this page |