linton@marktwain.rad.sgi.com (Mark Linton) (05/03/91)
In article <9105021411.AA18463@mrj.com>, pwb@mrj.com (Peter W. Brewer) writes: |> Steams again..... |> |> I have no problem if someone else (Doug Lea or me) does it. The problem I |> foresee is one of .. yes I can implement a compatible streams library, |> but how do I do it such that I can freely distribute it and not get in |> trouble with AT&T for doing so? It seems InterViews solved that problem at |> least at IV-2.6. All it takes to avoid AT&T trouble is to implement it yourself without any AT&T code. The fundamental problem is that "compatible" is undefined right now--ANSI streams will not be compatible with g++ streams and not compatible with AT&T streams. Streams aren't particularly efficient anyway, so I'm inclined to implement something that can use memory-mapped files on systems that provide them.