On Wed, Jan 23, 2013 at 03:08:57PM +0100, Marcus Denker wrote:
On Jan 23, 2013, at 7:28 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
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.
Ok, this should end up in the image by tomorrow:
Issue 7306: un-deprecate OSPlatform osVersion for compatibility http://code.google.com/p/pharo/issues/detail?id=7306
Thank you :)) Dave