This page leads you towards possible incompatibility problems,
when migrating from an older ST/X version.
Although we try to mention all possible trouble spots, we can
neither guarantee 100% compatibility, nor to not forget trouble spots in this list.
(however, we put a lot of effort in trying to maintain backward compatibility as much as possible.)
Encoding: utf8
and are typically placed into a comment (or a compiler pragma comment).
Make sure to clear any existing changeFiles, as change records will be appended utf8-encoded by the new version (if you want to use old change-files with the new release).
Application code should be prepared to get Unicode16Strings as the result of messages like #asLowercase etc.
Starting with 4.1.9, 4 methods were added to aid in writing portable code:
These methods are still (and will still be) present, to allow for code to be written
which works on any system.
position0Based / position0Based:
position1Based / position1Based:
All code which computes a stream position or takes a stream position as collection index,
using position and/or position: should either:
position1Based and/or position1Based:
Prior to release 5 no error exception has been raised when opening or creating of a FileStream
failed. A Notification has been signaled to those, who explicitly handled this notification.
Most classes did not handle this notification and got a nil-return, when doing e.g.
'/nonExistingFile' asFilename readStream.
From Release 5 on, FileStream openErrorSignal is an error exception and the same as
ExternalStream openErrorSignal.
Filename>>readStreamOrNil has been introduced. Please use the Filename interface,
and avoid using FileStreams directly.
Bytecode binaries, source files or autoloaded classes are not affected, and do not need special care.
Copyright © 1996 Claus Gittinger Development & Consulting, all rights reserved
Copyright © 2003 eXept Software AG, all rights reserved
<info@exept.de>
Doc $Revision: 1.10 $ $Date: 2004/03/15 13:01:03 $