[boost] Re: A library: out-of-core containers and algorithms

From: Roman Dementiev (dementiev_at_[hidden])
Date: 2005-02-07 10:04:41

Thorsten Ottosen wrote:
> "Roman Dementiev" <dementiev_at_[hidden]> wrote in message 
> news:cu7m3l$lfo$1_at_sea.gmane.org...
> | Thorsten Ottosen wrote:
> | > "Roman Dementiev" <dementiev_at_[hidden]> wrote in message
> | > news:cu62pe$a1i$1_at_sea.gmane.org...
> | > | Hello,
> | > |
> | > | I am developing a library called Stxxl.
> | >
> | >
> | > | Would such a library be interesting for Boost users? Does it fit here?
> | > | Is it worth to boostify it?
> | > |
> | > | I would be very glad to know your opinion.
> | >
> | > if you intend to submit it, would it then be possible to make it
> | > work on more platforms, unix (mac), windows?
> |
> | yes. One must rewrite only the lower layer of Stxxl using native
> | file access methods and native multithreading.
> 
> is that because you need mem.mapped files? Otherwise, why don't you use boost
> filsystem and boost threads?

I do not necessarily need memory mapped files.

The Boost filesystem library is more about manipulating files and 
directories.
But what I need is the file access itself: create/open/read/write/close 
file. I would
have been using std::fstream as a portable file access method, but it lacks
support of files larger than 2 GB. It is really big disadvantage in my case.

The boost threads library does fit my requirements. I would use
when it comes to boostifying Stxxl.

Roman