Thanks martin.
I do not remember may be this is related to the fact this is in alpha.
Can you check if you get the same behavior and the same code in deprecated:on:…
in 1.3
Stef (running now to catch a train)
On Mar 19, 2012, at 10:47 PM, Martin Sandiford wrote:
Hi all,
Kind of new to
Hope you made the train. Good advice to look into 1.3 --- on closer
inspection it turns out this actually works fine, and I just didn't
understand how things work. raiseWarning: false does what I want;
showWarning just affects transcript logs.
I've updated the issue --- it should probably be
Hope you made the train. Good advice to look into 1.3 --- on closer
inspection it turns out this actually works fine, and I just didn't
understand how things work. raiseWarning: false does what I want;
showWarning just affects transcript logs.
I've updated the issue --- it should
Hi all,
Kind of new to Pharo, so not sure if this is intended behaviour or
not, but Objectdeprecated:on:in: doesn't respect the current state
of the Deprecation classshowWarning setting.
This was unexpected for me --- in a headless setting the warning
dialog causes the VM to exit.
To reproduce
Hi Martin,
no objections!
please create the issue, and attach the fix.
Fernando
On Mon, Mar 19, 2012 at 10:47 PM, Martin Sandiford m...@mcdev.com.au wrote:
Hi all,
Kind of new to Pharo, so not sure if this is intended behaviour or
not, but Objectdeprecated:on:in: doesn't respect the current
OK, done.
http://code.google.com/p/pharo/issues/detail?id=5521
On Tue, Mar 20, 2012 at 8:25 AM, Fernando Olivero
fernando.oliv...@usi.ch wrote:
Hi Martin,
no objections!
please create the issue, and attach the fix.
Fernando
