Slava Pestov wrote: > A more radical idea is to remove duplex streams altogether. Instead, > words like <process-stream> and <client> would return a pair of > streams, a reader and a writer. A with-streams combinator with stack > effect ( in out quot -- ) could be used here.
What's the main motivation for removing duplex streams? I'd like to point out that it sort of moves in away from the direction I've argued for in general; that of "combining" objects on the stack instead of splitting them up. Areas where I've emphasized this principle are the encodings api and cursors. Let me just say that exceptions to principles should be made when they're justified. You might not subscribe to this principle, but from my perspective, I'm very interested in the reasons behind the change. Ed ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
