Re: RFC 14 (v3) Modify open() to support FileObjects and
[email protected] (Nathan Wiger) Mon, 14 Aug 2000 16:15:44 -0700
| Newsgroups | perl.perl6.language.io |
|---|---|
| Organization | Sun Microsystems |
| Message-ID | <[email protected]> |
Chaim Frenkel wrote: > > >>>>> "NW" == Nathan Wiger <[email protected]> writes: > > NW> # Replaced by 'open sys' > NW> sysopen > NW> sysread # sys->read instead > NW> syswrite # sys->write instead > > sysread and syswrite also work on files that were opened via standard > open. It bypasses the stdio library. Yeah, I know. The question is how frequently this is used. Since you can't mix read/print with sysread/syswrite, my suspicion is that most people use sysopen and then sysread/syswrite, or open then read/print. This is what I've always done, personally (but then again I'm not everyone either). :-) Since sysopen only takes a few extra args, I don't think it's too much of a hassle to require sysopen for sysread/syswrite access. It also makes it clear this is a special type of file access that doesn't (and shouldn't!) obey formats, regular reads/prints, etc. That's my input. If lots of people are against me we can change this. -Nate