Subj : Re: Evolution of a Progr To : Deuce From : Grymmjack Date : Sun Jun 26 2005 10:53 pm Re: Re: Evolution of a Progr By: Deuce to Grymmjack on Thu Jun 16 2005 11:51 am > Re: Re: Evolution of a Progr > By: Grymmjack to Digital Man on Thu Jun 16 2005 00:31:00 > > > > If it's a Unix editor, it needs to use standard I/O or socket-based I/ > > > it's a DOS or Win32 editor it needs to use either standard I/O, FOSSIL > > > socket-based I/O. Pretty much the same as doors on Synchronet (see > > > http://doors.synchro.net for details). > > > > i didn't realize that pico and nano used 'standard i/o' ? maybe i'm > > thinking the wrong way about stdio. i'm thinking pipes and redirection an > > standard input and output and standard error.. i thought that when you > > edit files since it's coming in live, and not from somewhere else, it > > would not be possible to be stdio? > > Right, that's the Windowsy way to look at stdio. In the *nix world we have > much richer stdio interface. In general, no Windows program uses stdio. In > general, every *nix program does. does this relate directly to the way *nix handles all devices as text files or streams or whatever i'm assuming? i read somewhere that every device and stream (i guess i/o would qualify there) in *nix os' is handled in the file system. - grymmjack .