On Jan 22, 2013, at 11:55 PM, David T. Lewis <lewis@mail.msen.com> wrote:
On Tue, Jan 22, 2013 at 01:51:56PM -0800, Chris Cunningham wrote:
On Tue, Jan 22, 2013 at 12:13 PM, David T. Lewis <lewis@mail.msen.com>wrote:
On Tue, Jan 22, 2013 at 08:05:02PM +0100, Marcus Denker wrote:
On Jan 22, 2013, at 5:27 PM, H. Hirzel <hannes.hirzel@gmail.com> wrote:
Dave
This works in Pharo 2.0?
Yes, "Smalltalk os version" is right for Pharo 2.0.
I'm looking for a way to modify the following method so that it adds support for Pharo 2.0, so that it continues to work in the other images, and so that it does not raise deprecation warnings or DNUs in any of the images.
Could you capture for deprecation of OSPlatform osVersion, and resend the other method (Smalltalk osVersion current osVersion)? Or, trap for Deprecation and resume it (ignore deprecation - once it is removed, you'll automatically fail-over to the new code).
No, Pharo 2.0 is writing console output whenever an exception occurs, so catching the exception is not good. But not raising the exception in the first place works just fine ;)
I will un-deprecate the osVersion methods in 2.0 and mark it as compatibility. Marcus