Hi Sunanda,
On Tuesday, September 27, 2005, 4:54:40 PM, you wrote:
Sac> As far as I know, that simply isn't possible with REBOL -- it does not
write
Sac> to STDOUT -- so we may want to stop the whole exercise right now until that
Sac> issue is resolved.
REBOL *does* read from STDIN, and it *does* write to SDTOUT, it's
just that Windows does not make it easy enough. On Linux, any
Unix, Mac OS X and so on, PRINT and INPUT simply work with STDIN
and STDOUT. On Windows, you can still write to STDOUT and read
from STDIN if you use -c *AND* pipe REBOL's output somewhere.
I.e.
DOS PROMPT> rebol some-script.r
won't print on the dos prompt, but use the console
DOS PROMPT> rebol -c some-script.r
won't print, seems like nothing is happening
DOS PROMPT> rebol -c some-script.r | more
*WILL* print to STDOUT.
Blame Windows. I agree it should be made to work anyway, but I
guess noone put effort in this because 99% of the people using
Windows don't care about STDIN and STDOUT. (You only do that in
CGI, and indeed REBOL works as CGI on Windows.)
If they're using anything other than Windows for the language
shootout tests, you don't even have to worry; what you see on the
console in Windows, they will see in STDIN/STDOUT on the other
platforms.
P.S.: don't forget that a lot of rebolers are in Italy already for
the conference, so this week it's likely there won't be much
contribution to these threads. ;)
Regards,
Gabriele.
--
Gabriele Santilli <[EMAIL PROTECTED]> --- http://www.rebol.com/
Colella Chiara software division --- http://www.colellachiara.com/
--
To unsubscribe from the list, just send an email to
lists at rebol.com with unsubscribe as the subject.
