🚀 go-pugleaf

>brianw@microsoft.com (Brian Willoughby) writes:
>> [...] First of all,
>> NXMapFile() is redundant since its purpose is to memory map the contents of
>> a file which will be accessed multiple times.[...]

jml@taco.visus.com (Jim Large) writes:
>Not necessarily true!  Even if you only intend to read a file once from
>start to finish, NXMapFile() is the preferred way to do it.  Why? because
>it does not have to allocate a buffer to read() file bytes into.  This
>could mean less swap space used.

I understand what you're saying, but I'm not sure that I am convinced.
Can you point me to a Technical Note, FAQ or even a posting which suggests
this?  I'm always looking for tips like those in "Making your app fly".

>Also, that the documentation says:
>     "NXOpenFile() opens a stream on the file specified by the file 
>      descriptor argument, fd, which can refer to a pipe or a socket."
>                                                    ^^^^^^^^^^^^^^^^
>We all know that this WILL work for a regular file too, but it's bad
>habit to break NeXT's rules :-)

What you quoted says that the fd *can* refer to a pipe or socket, NOT
that it *must* refer to one of them.  Are you sure that regular files
are specifically excluded?

Perhaps NeXT is listening and the author can clear this up.

-- 
Brian Willoughby  Software Design Engineer
Microsoft Corp.   Multimedia Systems Division
brianw@microsoft