[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Explanations on MappedFile
From: |
David Sugar |
Subject: |
Re: Explanations on MappedFile |
Date: |
Sun, 6 Oct 2002 12:17:36 -0400 |
User-agent: |
KMail/1.4.3 |
Generally I had been assuming people would use MappedFile to construct more
complete objects that manage mapped memory in specific ways, rather than use
MappedFile itself as a generic mapped file access class.
On Thursday 26 September 2002 12:22, Damien Vincent wrote:
> Hi,
>
> I'd like to know why all types (Mapping, Access, ...) are in the protected
> section of the class "File". With this design, you can't make a MappedFile
> object since in the constructor of this class, you need to specify an
> access mode (-> MappedFile (const char *fname, Access mode) ). So, the only
> way to create a mapped file is to make a class which derives from
> MappedFile. With the version 1.6.4 of the library, you can make an instance
> of the MappedFile class.
>
> Thanks,
>
> Damien
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: Explanations on MappedFile,
David Sugar <=