25 Mar
2013
25 Mar
'13
3:55 a.m.
The overhead occurred by MethodWrapper is higher than Spy. Spy comes with a faster
implementation of the methodwrapper.
The other thing is that Spy offer ways to automatically install/uninstall the wrappers,
run the unit tests and so on.
Alexandre
On Mar 24, 2013, at 4:44 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote:
Do not reinvent the wheel.
MethodWrapper should work on Pharo else we should fix them.
They should be published on SmalltalkHub
Then Spy should work or another spying framework because Alex is using them.
So let us know so that we can take actions.
Stef
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I'm was exploring some methods to build method wrappers and I discovered Spy.
Unfortunately the sample code provided on http://www.moosetechnology.org/tools/Spy does
not run.
When you reach this point
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev You can simply invoke it with:
| packageSpy |
packageSpy := DemoTestCoveragePackageSpy runTestAndGatherForPackageNamed:
'Mondrian'.
There is no "DemoTestCoveragePackageSpy" yet.
Afterward this class is defined but still there is no message
"runTestAndGatherForPackageNamed".
Any hep would be appreciated.
Thanks in advance,
Roberto
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev