Here is an example of using the ast to remove -all- halts from the code if one
or more is encountered during execution.
| haltTypes haltingMethods testCode |
haltTypes := #( halt halt: haltIf: haltIfNil haltOnCount: haltOnce).
Hi Stef,
see an idea below..
Stephane Ducasse wrote:
I would love to get a functionality that dynamically removes from my
code all the self halt that are encountered during test execution.
This way I will not need to run the test, walk the stack, edit the
code and retart the process.
It
I would love to get a functionality that dynamically removes from my code
all the self halt that are encountered during test execution.
This way I will not need to run the test, walk the stack, edit the code and
retart the process.
It would be really cool
Thanks guys,
The forum.world.st didn't send me your replies and only now I'm aware of
your replies.
Thanks again
Davide
Clément Bera-4 wrote
> Hi,
>
> This will be fixed by using the alternative bytecode set, likely in the
> next few weeks in Pharo 6 alpha/beta. Basically control flow messages
Hi Folks,
Actually It seems on the linux vm the AioPlugin isn't included.
I worked on old vm, but I also downloaded the latest vm
http://files.pharo.org/vm/pharo-spur32/linux/latest.zip and the result is
the same.
See the screenshot here http://imgur.com/a/9jhMy
How can I add the plugin?
TIA
There is #newAnonymousSubclass for creating a subclass from the current class.
It seems that this is what this code is trying to do.
Marcus
> On 15 Jan 2017, at 09:40, stepharong wrote:
>
> HI
>
> I need to migrate
>
> pvtNewSubclass
>
> | newClass |
>