From: matz@... (Yukihiro Matsumoto)
Date: 2001-04-27T09:51:20+09:00
Subject: [ruby-talk:14278] Re: Ruby vs. Tcl input/output question

Hi,

In message "[ruby-talk:14236] Ruby vs. Tcl input/output question"
    on 01/04/26, bw <donotreply@interbulletin.bogus> writes:

|* line-buffering: gets() has \n at the end
|   so that 99% of all code looks like this: gets(); chomp() (from Perl?)
|   why not doing it like Tcl, strip the EOL on input
|   and add the EOL later at output (if needed).

I don't use chomp() that often.  Plus auto treatment of EOL hide
non-existence of EOL at the end of file.

|* autoflush as default
|   don't know actually, but wouldn't it be nice to make it the
|   default (less surprise)?
|   If I want to write huge data, usualy I know this in advance and can
|   turn autoflush off anyway

What's wrong with buffering?  In addition, autoflush turned on for
sockets and tty connected IOs.

|* Tcl-Eventloop:
|   the greatest thing of Tcl is for sure the Eventloop which
|   combines File/Pipe/Socket readable/writeable-events AND Tk-GUI
|   AND 'decoupled callbacks' via [after <time> command]
|   I could not find such a thing in Ruby (where to look?)

Ruby chooses thread model.  So

  Thread.start{
    sleep <time>
    <command>
  }

would do without 'event loops'.

							matz.