🚀 go-pugleaf

In article <fW0DHHa@quack.sac.ca.us> dfox@quack.sac.ca.us (David Fox) writes:
>
>>Honestly it's the definition of IO that's missing here. C/UNIX
>>have standardized on NOT sequential but flat direct-access files
>>for the filesystem and sequential access for pipes, some devices,
>>input format for most system commands, etc.
>
>That's an interesting point.  I am not an expert in Unix file access
>but I'd guess that Unix has standardized on both sequential
>and flat direct-access files, and that sequential access is just a
>special case of direct access: read so many bytes sequentially from
>a randomly-accessible point in a file.  Or, it has standardized on
>sequential file access, and that direct access is a special case, using
>the fseek() library call.

But, given that 'fseek' is incredibly slow on most Unix systems,
one could almost assume that Unix doesn't support random-access files.

---
Conor O'Neill, Software Group, INMOS Ltd., UK.
UK: conor@inmos.co.uk		US: conor@inmos.com
"It's state-of-the-art" "But it doesn't work!" "That is the state-of-the-art".