>Who says we need to use a spoecial term? Standard input, error, and
>output are files -- so:
>
> write xxxx to [standard ]out[put]|stdout
> write zzzz to [standard ]error[ output]|stderr
> read yyyy from [standard ]in[put]|stdin
>
>So:
>
> write "Hello, World!" to standard output
> write "Hello, World!" to output
> write "Hello, World!" to standard out
> write "Hello, World!" to out
> write "Hello, World!" to stdout
>
>
>Some system specific things coould also be used -- something like
>/proc/self/ on Linux (not that we'd document that or recommend it, we
>just would not prohibit it).
Why don't just make it a global object? For CGIs, stdin and stdout might
be something else than files (the data will be directly transferred across
the web), and I don't see what using write would gain here. Just let the
users "put" into it. I'm for making files regular objects anyway (in 2.0 or
whatever). I.e.:
put "hello" into line 2 of file "textfile.txt"
or whatever.
put "hello" after standardOutput
won't be that bad either. Whether there's a space or not, I don't really
care. Scott might, though, for compatibility reasons.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
