Hi, I was looking at nil (already funny) and found a very interesting method: suspend "Kills off processes that didn't terminate properly" "Display reverse; reverse." "<-- So we can catch the suspend bug" Processor terminateActive It means that the following code is probably the shortest way to kill your image (save first!) nil suspend It terminates a UI process if evaluated from anywhere using CMD+d :D Cheers, Alex
It sounds like a left over... no time stamp in Squeak, so it must be old. Display reverse; reverse means we wanted to catch when such oddity was necessary. (I would do it differently with an Exception and a MessageTally like I already exhibited several times) The fact that reverse; reverse was commented is more difficult to interpret... Is it really necessary? I removed the method in a Squeak image, and so fare nothing wrong happened, but it does not prove anything. The best is to ask in Squeak lists, maybe someone can remember... Or carefully analyze all senders of suspend... 2017-11-18 22:36 GMT+01:00 Aliaksei Syrel <alex.syrel@gmail.com>:
Hi,
I was looking at nil (already funny) and found a very interesting method:
suspend "Kills off processes that didn't terminate properly" "Display reverse; reverse." "<-- So we can catch the suspend bug" Processor terminateActive
It means that the following code is probably the shortest way to kill your image (save first!)
nil suspend
It terminates a UI process if evaluated from anywhere using CMD+d :D
Cheers, Alex
Yes, it doesn't sound right. I vote for removal :) On Sat, Nov 18, 2017 at 11:04 PM, Nicolas Cellier < nicolas.cellier.aka.nice@gmail.com> wrote:
It sounds like a left over... no time stamp in Squeak, so it must be old. Display reverse; reverse means we wanted to catch when such oddity was necessary. (I would do it differently with an Exception and a MessageTally like I already exhibited several times) The fact that reverse; reverse was commented is more difficult to interpret... Is it really necessary? I removed the method in a Squeak image, and so fare nothing wrong happened, but it does not prove anything. The best is to ask in Squeak lists, maybe someone can remember... Or carefully analyze all senders of suspend...
2017-11-18 22:36 GMT+01:00 Aliaksei Syrel <alex.syrel@gmail.com>:
Hi,
I was looking at nil (already funny) and found a very interesting method:
suspend "Kills off processes that didn't terminate properly" "Display reverse; reverse." "<-- So we can catch the suspend bug" Processor terminateActive
It means that the following code is probably the shortest way to kill your image (save first!)
nil suspend
It terminates a UI process if evaluated from anywhere using CMD+d :D
Cheers, Alex
-- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13
+1 On Mon, Nov 20, 2017 at 10:06 AM, Guillermo Polito < guillermopolito@gmail.com> wrote:
Yes, it doesn't sound right. I vote for removal :)
On Sat, Nov 18, 2017 at 11:04 PM, Nicolas Cellier < nicolas.cellier.aka.nice@gmail.com> wrote:
It sounds like a left over... no time stamp in Squeak, so it must be old. Display reverse; reverse means we wanted to catch when such oddity was necessary. (I would do it differently with an Exception and a MessageTally like I already exhibited several times) The fact that reverse; reverse was commented is more difficult to interpret... Is it really necessary? I removed the method in a Squeak image, and so fare nothing wrong happened, but it does not prove anything. The best is to ask in Squeak lists, maybe someone can remember... Or carefully analyze all senders of suspend...
2017-11-18 22:36 GMT+01:00 Aliaksei Syrel <alex.syrel@gmail.com>:
Hi,
I was looking at nil (already funny) and found a very interesting method:
suspend "Kills off processes that didn't terminate properly" "Display reverse; reverse." "<-- So we can catch the suspend bug" Processor terminateActive
It means that the following code is probably the shortest way to kill your image (save first!)
nil suspend
It terminates a UI process if evaluated from anywhere using CMD+d :D
Cheers, Alex
--
Guille Polito
Research Engineer
Centre de Recherche en Informatique, Signal et Automatique de Lille
CRIStAL - UMR 9189
French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>*
*Web:* *http://guillep.github.io* <http://guillep.github.io>
*Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
https://pharo.manuscript.com/f/cases/21237/Remove-UndefinedObject-suspend https://github.com/pharo-project/pharo/pull/798
On 22 Nov 2017, at 21:25, Stephane Ducasse <stepharo.self@gmail.com> wrote:
+1
On Mon, Nov 20, 2017 at 10:06 AM, Guillermo Polito <guillermopolito@gmail.com> wrote: Yes, it doesn't sound right. I vote for removal :)
On Sat, Nov 18, 2017 at 11:04 PM, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote: It sounds like a left over... no time stamp in Squeak, so it must be old. Display reverse; reverse means we wanted to catch when such oddity was necessary. (I would do it differently with an Exception and a MessageTally like I already exhibited several times) The fact that reverse; reverse was commented is more difficult to interpret... Is it really necessary? I removed the method in a Squeak image, and so fare nothing wrong happened, but it does not prove anything. The best is to ask in Squeak lists, maybe someone can remember... Or carefully analyze all senders of suspend...
2017-11-18 22:36 GMT+01:00 Aliaksei Syrel <alex.syrel@gmail.com>: Hi,
I was looking at nil (already funny) and found a very interesting method:
suspend
"Kills off processes that didn't terminate properly"
"Display reverse; reverse." "<-- So we can catch the suspend bug"
Processor terminateActive It means that the following code is probably the shortest way to kill your image (save first!)
nil suspend It terminates a UI process if evaluated from anywhere using CMD+d :D
Cheers, Alex
--
Guille Polito Research Engineer
Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - http://www.cnrs.fr
Web: http://guillep.github.io Phone: +33 06 52 70 66 13
participants (5)
-
Aliaksei Syrel -
Guillermo Polito -
Nicolas Cellier -
Stephane Ducasse -
Sven Van Caekenberghe