Igor Stasenko wrote:
you can open .changes file in another image to rescue your code.
Thanks Igor. I gave that a go but couldn't work it out. I tried the
following: Unzipped a fresh image, copied the .changes file into the
folder to overwrite the existing .changes file, then after
On Mon, Aug 27, 2012 at 8:44 AM, Ben Coman b...@openinworld.com wrote:
Igor Stasenko wrote:
you can open .changes file in another image to rescue your code.
Thanks Igor. I gave that a go but couldn't work it out. I tried the
following: Unzipped a fresh image, copied the .changes
On 27 August 2012 17:44, Ben Coman b...@openinworld.com wrote:
Igor Stasenko wrote:
you can open .changes file in another image to rescue your code.
Thanks Igor. I gave that a go but couldn't work it out. I tried the
following: Unzipped a fresh image, copied the .changes file into
Igor Stasenko wrote:
On 4 August 2012 04:11, Ben Coman b...@openinworld.com wrote:
As probably many newbies do from time to time, I am learning the system
splattering 'self halt' around, and once again slipped one into the wrong
place where I should have used 'haltOnce' and had a massive
you can open .changes file in another image to rescue your code.
also you can patch the image's bytecode to avoid entering an offending method
(like a method which enters the drawing , just see its bytecode in
another image,
and the find same byte sequence in crashing image, and put return self
Sean P. DeNigris wrote:
Igor Stasenko wrote
in pharo you can use
Halt now.
which is imo the right way to do it..
but i so get used to type 'self halt' .. its hard to get rid of bad
habits. :)
One little carrot to use Halt now. is that it opens the debugger on the
method with the
Igor Stasenko wrote
in pharo you can use
Halt now.
which is imo the right way to do it..
but i so get used to type 'self halt' .. its hard to get rid of bad
habits. :)
One little carrot to use Halt now. is that it opens the debugger on the
method with the halt in it instead of on
I also find using self is a bit of a roulette wheel... When I use
this tactic, I always say 3 halt instead.
-C
--
Craig Latta
www.netjam.org/resume
+31 6 2757 7177
+ 1 415 287 3547 (no SMS)
On 10 August 2012 14:41, Craig Latta cr...@netjam.org wrote:
I also find using self is a bit of a roulette wheel... When I use
this tactic, I always say 3 halt instead.
in pharo you can use
Halt now.
which is imo the right way to do it..
but i so get used to type 'self halt' .. its hard
Igor Stasenko wrote
but i so get used to type 'self halt' .. its hard to get rid of bad
habits. :)
Ha ha, I wanted to remove it but Steph wouldn't let me ;)
--
View this message in context:
http://forum.world.st/self-halt-safety-net-tp4643012p4643771.html
Sent from the Pharo Smalltalk
Oh no! Now I'm going to have to port all of the `self halts` in my code, too:)
Dale
- Original Message -
| From: Sean P. DeNigris s...@clipperadams.com
| To: pharo-project@lists.gforge.inria.fr
| Sent: Friday, August 10, 2012 8:51:10 AM
| Subject: Re: [Pharo-project] 'self halt' safety
| To: pharo-project@lists.gforge.inria.fr
| Sent: Friday, August 10, 2012 8:51:10 AM
| Subject: Re: [Pharo-project] 'self halt' safety net
|
|
| Igor Stasenko wrote
|
| but i so get used to type 'self halt' .. its hard to get rid of bad
| habits. :)
|
|
| Ha ha, I wanted to remove
Igor Stasenko wrote:
On 4 August 2012 04:11, Ben Coman b...@openinworld.com wrote:
As probably many newbies do from time to time, I am learning the system
splattering 'self halt' around, and once again slipped one into the wrong
place where I should have used 'haltOnce' and had a massive
On Sat, Aug 4, 2012 at 4:11 AM, Ben Coman b...@openinworld.com wrote:
As probably many newbies do from time to time, I am learning the system
splattering 'self halt' around, and once again slipped one into the wrong
place where I should have used 'haltOnce' and had a massive number of
Mariano Martinez Peck wrote:
On Sat, Aug 4, 2012 at 4:11 AM, Ben Coman b...@openinworld.com wrote:
Another thought, are there any plans for a breakpoint facility, so that
I don't dirty a package by only inserting 'self halt' to aid debugging.
it already exists. Right click on a
Mariano Martinez Peck wrote
Another thought, are there any plans for a breakpoint facility, so that
I don't dirty a package by only inserting 'self halt' to aid debugging.
it already exists. Right click on a method - Add breakpoint
I, too would love to have the features you suggest.
What about a Nautilus plugin, that allows browsing all the methods
that send #halt, #flag:,#log:? (the development messages).
Since finding all the halts, doesn't seem something that needs to be
performed all the time, an optional Nautilus plugin would suffice.
Fernando
On Sat, Aug 4, 2012 at
On Sat, Aug 4, 2012 at 3:44 PM, Fernando Olivero fernando.oliv...@usi.chwrote:
What about a Nautilus plugin, that allows browsing all the methods
that send #halt, #flag:,#log:? (the development messages).
That's a great idea. In fact, I remember being sit at my desk in Douai and
doing that
I do :)
A plugin that shows all the #flag: messages
Ben
On Aug 4, 2012, at 5:40 PM, Mariano Martinez Peck wrote:
On Sat, Aug 4, 2012 at 3:44 PM, Fernando Olivero fernando.oliv...@usi.ch
wrote:
What about a Nautilus plugin, that allows browsing all the methods
that send #halt,
As probably many newbies do from time to time, I am learning the system
splattering 'self halt' around, and once again slipped one into the
wrong place where I should have used 'haltOnce' and had a massive number
of pre-debugger windows come up. I managed to get it back this time
with the
On 4 August 2012 04:11, Ben Coman b...@openinworld.com wrote:
As probably many newbies do from time to time, I am learning the system
splattering 'self halt' around, and once again slipped one into the wrong
place where I should have used 'haltOnce' and had a massive number of
pre-debugger
21 matches
Mail list logo
