From: Ian Macdonald Date: 2002-06-22T04:11:31+09:00 Subject: Re: Why is I/O slow? On Sat 22 Jun 2002 at 03:06:20 +0900, Chris Ross wrote: > On Sat, Jun 22, 2002 at 02:26:15AM +0900, Ian Macdonald muttered... > > Because it makes debugging easier? Trust me, going just down one route > to solve a problem in a cross platform way can provide enough issues, let > alone having multiple paths depending on a strange array compile > options. It doesn't need to be an option. Just have autoconf detect the presence of glibc and build accordingly. > And if you want tight control over buffering [as matz stated he > does] the easiest way to do it is to implement it himself touching > the real world as little as possible until necessary [eg. flushing > that buffer]. Sure, that's a valid approach, too. I guess I just don't see the benefit of not using the resources of the OS when they equate with what you're trying to do on a given platform. It's a small point, though. I would not actually expect I/O to be as fast when running a scripted application, so I'm not dissatisfied with Ruby's performance in any way. Ian -- Ian Macdonald | Who does not love wine, women, and song, ian@caliban.org | Remains a fool his whole life long. -- | Johann Heinrich Voss | |