On Tue, 14 Dec 1999, M. Uli Kusterer wrote:
> >So is CGI, and compatibility with the terminology used for that is far
> >more important than trying to "disguise" it by giving it non-matching
> >"user friendly" names. Allowing the full names sounds like a good
> >idea, though.
>
> Since the app I'm working on is a text-only screen-centric program, not a
> CGI, should I invent my own syntax instead of using stdin/stdout, to make
> sure I don't water down CGI terminology, or should I stick with this? I
> don't want to hurt xTalk in any way by introducing duplicate syntax, but
> mis-using existing stuff for different uses might be even worse.
I'm not sure I understand what you're planning to build, but it sounds
like a character-based application (though I had thought that these
had pretty much gone the way of the dodo ;-) If so, the standard I/O
terms (stdin/stdout/stderr) would probably apply, even if you're
doing terminal I/O related stuff like moving the cursor around. It's
not just CGIs that use these terms, they're standard parts of the C
language.
Regards,
Scott
> Cheers,
> -- M. Uli Kusterer
>
> ------------------------------------------------------------
> http://www.weblayout.com/witness
> 'The Witnesses of TeachText are everywhere...'
>
> --- HELP SAVE HYPERCARD: ---
> Details at: http://www.hyperactivesw.com/SaveHC.html
> Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
>
>
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
