Re: Re: Data copied with fork() -> how to access true data?

Replies are listed 'Best First'.
Re: Re: Re: Data copied with fork() -> how to access true data? by Joost (Canon) on May 31, 2004 at 22:00 UTC
If you're reading data immediately from STDIN, you might take a look at the `select` documentation for info about non-blocking IO - so you can do something useful while waiting for user input. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply] [d/l]
Re: Re: Re: Re: Data copied with fork() -> how to access true data? by muba (Priest) on May 31, 2004 at 22:12 UTC
This looks most interesting! Although the select documentation only mentions how to block (not how to unblock) a FH. It would be logical if unblocking is just the opposite, but I don't quite understand the $rin, $rout, $win, $wout bit things. Could you maybe give some more clues?	[reply]
Re: Re: Re: Re: Re: Data copied with fork() -> how to access true data? by Joost (Canon) on May 31, 2004 at 22:18 UTC
the docs for IO::Select and this recipe from the perl cookbook might explain more. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re: Re: Re: Re: Re: Re: Data copied with fork() -> how to access true data? by muba (Priest) on May 31, 2004 at 22:32 UTC
Re: Re: Re: Re: Re: Re: Re: Data copied with fork() -> how to access true data? by Joost (Canon) on May 31, 2004 at 22:37 UTC
Re^3 Data copied with fork() -> how to access true data? by cLive ;-) (Prior) on Jun 01, 2004 at 00:01 UTC
"...not internet connected..." Wouldn't that make it a SUD? :) cLive ;-)	[reply]
Re: Re^3 Data copied with fork() -> how to access true data? by muba (Priest) on Jun 01, 2004 at 19:10 UTC
Actually, it would. "single player MUD like". Single Player. MUD like. But yes, you're right :)	[reply]