Thanks for the reply Jon, Do you have some quick example code of how to properly use the TCPSocket with stdio? I need to be able to access the Events inside of the TCPSocket instance while attached to the StandardInputStream if at all possible.
In this environment would TCPSocket call its events properly, being "attached" to stdin/stdout? The origin of the issue has been CPU usage differences between Linux and Windows while "waiting for data" in a stdin.read, stdin.readline or Input, which is why I turned towards this direction and it doesn't seem as thought there is *any* example code even similar in nature on the net...anywhere. Thanks for any help you could provide, Kraig Beahn XS Communications On 3/7/06, Jonathan Johnson <[EMAIL PROTECTED]> wrote: > > On 3/7/06, Kraig Beahn <[EMAIL PROTECTED]> wrote: > > > For the life of me, it wont compile or run. TCPSocket1 has a super of > TCPSocket. > > Correct. StdIn and StdOut know how to convert to a TCPSocket, but not > to a TCPSocket1. The conversion operators return a new instance of the > class in question, and since the StandardInputStream and > StandardOutputStream don't know anything about your TCPSocket1, it > can't return an instance of it. The compiler catches this, and lets > you know it's a type-mismatch. > > HTH, > Jon > > > -- > Jonathan Johnson > REAL Software, Inc. > > REAL World 2006, The REALbasic User's Conference > <http://www.realsoftware.com/realworld> > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives of this list here: > <http://support.realsoftware.com/listarchives/lists.html> > _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
