# HG changeset patch # User Claus Gittinger # Date 1373128994 -7200 # Node ID 9a4e6bbb20d5a80fbfca8f7b6d81c181c22e56c9 # Parent 7f6fdc8ff911a272ec4924a2155543e164a93628 class: FileStream comment/format in: #documentation diff -r 7f6fdc8ff911 -r 9a4e6bbb20d5 FileStream.st --- a/FileStream.st Sat Jul 06 18:40:00 2013 +0200 +++ b/FileStream.st Sat Jul 06 18:43:14 2013 +0200 @@ -226,21 +226,23 @@ positioning a file stream. For example, poor VMS does not allow positioning onto arbitrary byte boundaries if the file is a variable-record-RMS file. - (stupid enough, this is the default for textfiles as created by - some tools ...) + (stupid enough, this is the default for textfiles as created by some tools ...) Therefore, the instance variable canPosition is set according to this and an error is raised, if a position: is attemted. I know, this is ugly, but what else could we do ? + Late note: who cares for VMS these days? + (and how much useless effort has been put in the past, + to support lousy operating systems?) [instance variables:] - pathName the files path (if known) - canPosition positionable - read above comment + pathName the files path (if known) + canPosition positionable - read above comment [author:] - Claus Gittinger + Claus Gittinger [see also:] - Filename DirectoryStream PipeStream Socket + Filename DirectoryStream PipeStream Socket " ! @@ -1974,11 +1976,11 @@ !FileStream class methodsFor:'documentation'! version - ^ '$Header: /cvs/stx/stx/libbasic/FileStream.st,v 1.161 2013-07-06 16:40:00 cg Exp $' + ^ '$Header: /cvs/stx/stx/libbasic/FileStream.st,v 1.162 2013-07-06 16:43:14 cg Exp $' ! version_CVS - ^ '$Header: /cvs/stx/stx/libbasic/FileStream.st,v 1.161 2013-07-06 16:40:00 cg Exp $' + ^ '$Header: /cvs/stx/stx/libbasic/FileStream.st,v 1.162 2013-07-06 16:43:14 cg Exp $' ! !