OK, my bad, Robert, I assumed the first part was from the example, and the second was from you. Well, then the code in the help browser is wrong, we'll have to kill whoever wrote that. BTW, I am older than you think, not that it is relevant. On 19 Mar 2013, at 17:24, Robert Shiplett <grshiplett@gmail.com> wrote:
"your code"
Are you sure you read MY mail, Sven ?
The snippet in not MINE ! It is in the Pharo 2.0 HelpBrowser !
Were you even born when I was first unhappy with Smalltalk Digitalk/ParcPlace fiasco ?
Do you know anything about MY code over the last decades ?
Have I EVER troubled you with MY code ?
... me relatives in Appalachia are also friendlie after a fashion ... even those that cain t reed
On 19 March 2013 13:13, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 19 Mar 2013, at 17:04, Robert Shiplett <grshiplett@gmail.com> wrote:
"RUN" is the issue ... Sven is sure I was doing INSPECT when I am sure I was using CTRL-D
Sorry to be persistent but I am unhappy when people don't read correctly what I write ;-)
I did take the time to run your code, I don't have to do that.
This was your second example:
Transcript open.
| announcer | World announcer on: WindowOpened send: #value to: [:ea | ea inspect. Transcript show: 'A new window was opened';cr].
Whether you did a 'Do it' or 'Inspect it' is irrelevant, you executed it.
It has 2 separate problems:
1.
you have to say #value: not #value because your block takes an argument.
that is a mistake that you introduced yourself and that was not in the original example.
but as I said, there should not be an emergency evaluator (although it contained the explanation) - so that is something we can try to improve.
thanks again for reporting that.
2.
ea inspect opens an inspector, which is a window, which triggers your code, which is an infinite loop.
I can't say this any other way.
Sven