Hi all, Kind of new to Pharo, so not sure if this is intended behaviour or not, but "Object>>deprecated:on:in:" doesn't respect the current state of the "Deprecation class>>showWarning" setting.
This was unexpected for me --- in a headless setting the warning dialog causes the VM to exit. To reproduce (in 1.4 14399): Deprecation showWarning: false. true and: [ true ] and: [ true ]. "Boolean>>and:and: sends deprecated:on:in:" Fix seems straightforward: wrap the current contents of "deprecated:on:in:" in "Deprecation showWarning ifTrue: [...]". If there are no objections, I'll raise a bug in the tracker. Cheers, Martin
