Status: FixToInclude
Owner:
[hidden email]
Labels: Milestone-1.3
New issue 4305 by
[hidden email]: Put back ObjectScanner
http://code.google.com/p/pharo/issues/detail?id=4305... it is used by SmartRefStream:
appendClassDefinitions
"Make this a fileOut format file. Class name conflicts during reading
will be resolved then. Assume instVarInfo: has already been done."
byteStream ascii.
byteStream position = 0 ifTrue: [
byteStream setFileTypeToObject.
"Type and Creator not to be text, so can attach correctly to an email
msg"
byteStream header; timeStamp].
byteStream cr; nextPutAll: '!ObjectScanner new initialize!'; cr; cr.
byteStream trailer. "Does nothing for normal files.
HTML streams will have trouble with object data"
"Append the object's raw data"
byteStream cr; cr; nextPutAll: '!self smartRefStream!'.
byteStream binary. "get ready for objects"
Wow...what an ugly, ugly hack. We should put Fuel in and remove
SmartRefStream.
(and for now put ObjectScanner back)
Attachments:
ObjectScanner.st 5.0 KB
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Locked
