[Pkg] The Trunk: 51Deprecated-topa.8.mcz

commits at source.squeak.org commits at source.squeak.org
Thu Oct 8 19:11:12 UTC 2015

Tobias Pape uploaded a new version of 51Deprecated to project The Trunk:

==================== Summary ====================

Name: 51Deprecated-topa.8
Author: topa
Time: 8 October 2015, 9:11:07.323 pm
UUID: f038f092-9136-4d33-b8d7-474efe928e4d
Ancestors: 51Deprecated-topa.7

Retain some meta information to see where that came from

=============== Diff against 51Deprecated-topa.7 ===============

Item was changed:
+ SystemOrganization addCategory: #'51Deprecated-Files-Kernel'!
- SystemOrganization addCategory: #'51Deprecated'!

Item was changed:
  StandardFileStream subclass: #CrLfFileStream
  	instanceVariableNames: 'lineEndConvention'
  	classVariableNames: 'Cr CrLf Lf LineEndDefault LineEndStrings LookAheadCount'
  	poolDictionaries: ''
+ 	category: '51Deprecated-Files-Kernel'!
- 	category: '51Deprecated'!
  !CrLfFileStream commentStamp: 'ul 12/26/2010 03:13' prior: 0!
  This class is now obsolete, use MultiByteFileStream instead.
  I am the same as a regular file stream, except that when I am in text mode, I will automatically convert line endings between the underlying platform's convention, and Squeak's convention of carriage-return only.  The goal is that Squeak text files can be treated as OS text files, and vice versa.
  In binary mode, I behave identically to a StandardFileStream.
  To enable CrLfFileStream as the default file stream class for an entire image, modify FileStream class concreteStream .
  There are two caveats on programming with CrLfFileStream.
  First, the choice of text mode versus binary mode affects which characters are visible in Squeak, and no longer just affects whether those characters are returned as Character's or as Integer's.  Thus the choice of mode needs to be made very carefully, and must be based on intent instead of convenience of representation.  The methods asString, asByteArray, asCharacter, and asInteger can be used to convert between character and integer representations.  (Arguably, file streams should accept either strings or characters in nextPut: and nextPutAll:, but that is not the case right now.)
  Second, arithmetic on positions no longer works, because one character that Squeak sees (carriage return) could map to two characters in the underlying file (carriage return plus line feed, on MS Windows and MS DOS).  Comparison between positions still works.  (This caveat could perhaps be fixed by maintaining a map between Squeak positions and positions in the underlying file, but it is complicated.  Consider, for example, updates to the middle of the file.  Also, consider that text files are rarely updated in the middle of the file, and that general random access to a text file is rarely very useful.  If general random access with specific file counts is desired, then the file is starting to sound like a binary file instead of a text file.)

More information about the Packages mailing list