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;
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
Can you report those to be added?
btw, 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.
cheers -ben
Sabine Knöfel wrote:
Hi Andre,
thanks, I used it and it worked fine but as you said
Hi Andre,
thanks, I used it and it worked fine but as you said - several methods are
not covered.
Sabine
On Thu, Jan 16, 2014 at 2:02 PM, Andre Hora [via Smalltalk] <
ml-node+s1294792n4737198...@n4.nabble.com> wrote:
> Hello Sabine,
>
> I have a set of smalllint rules I have created by mining
Hello Sabine,
I have a set of smalllint rules I have created by mining code history
between Pharo 2.0 and 3.0.
Note however they do not cover all deprecated methods and classes.
If you want to give a try, just load them (using the code below), and run
the rules using the Critic Browser to find th
Hi,
I am currently moving my application from pharo2 to pharo3.
I am asking myself if there is an easy way to find all deprecated methods I
used in my app.
The only way I see currently is to use the app and testing for walkbacks and
run the test cases.
How did others manage this?
Sabine
--
V
