[NewbieQ] Why are the methods for filing in code in the generic FileStream hierarchy?

R. A. Harmon harmonra at webname.com
Tue Feb 8 22:38:17 UTC 2000


At 10:47 AM 2/7/00 -0700, you wrote:
>Why are the methods filing in code in the generic FileStream hierarchy?
>
>I am in the process of creating a sub-class of StandardFileStream and
>this question has crossed my mind.
>
>It seems that the gereric/abstract super classes for file streams should
>not be burdened with methods which apply only to a specific application.
>I thought that application specific code should be in a sub class (which
>is what I am doing.)
>
>Am I wrong to expect that the hierarchy would be something like this:
>
>FileStream
>	StandardFileStream
>	HTMLFileStream
>	GraphicsFileStream	
>		GZIPFileStream
>		JPEGFileStream
>	FileInStream
>		BangFileInStream
>		SifFileInStream

In my implementation of SIF I segregate SIF reader and writer classes as
sub-classes of SIF readerWriter (a subclass of Object) as you thought--it is
application specific code.

--
Richard A. Harmon          "The only good zombie is a dead zombie"
harmonra at webname.com           E. G. McCarthy
Spencer, Iowa





More information about the Squeak-dev mailing list