how to copy a part of a binary file

[pedagani]

I want to copy only a part of the binary file delimited by offset
values say START_OFFSET_ & END_OFFSET_ which can be as huge as a 50
Giga. Below is the program where I could set a START_OFFSET_ but could
not specify the END_OFFSET_ value.
Any thoughts? Please advise. Thanks.

#include <fstream>
#include <iostream>
#include <algorithm>
#include <ios>
#include <iterator>
#include <string>
#define START_OFFSET_ 5000000
#define END_OFFSET_ 10000000
using namespace std;
void main()
{

ifstream is("c:\\test.bi n",ios_base::bi nary);
ofstream os("c:\\testpar se.bin",ios_bas e::binary);
if (!is || !os)
{
cout<<"Could not open the file for read/write";
exit(1);
}

is.seekg(START_ OFFSET_,ios::be g);

copy(istream_it erator<char(is) ,
istream_iterato r<char(),
ostream_iterato r<char(os));

is.close();
os.close();

/* I wanted to have something like this
//basic_istream<c har,char_traits <char& start =
is.seekg(START_ OFFSET_,ios::be g);
//basic_istream<c har,char_traits <char& end =
is.seekg(END_OF FSET_,ios::beg) ;
//copy( istream_iterato r<char(start),
// istream_iterato r<char(end),
// ostream_iterato r<char(os)); //Apparently, this does not work
*/

}

[Jens Theisen]

pe******@gmail. com wrote:

I want to copy only a part of the binary file delimited by offset
values say START_OFFSET_ & END_OFFSET_ which can be as huge as a 50
Giga. Below is the program where I could set a START_OFFSET_ but could
not specify the END_OFFSET_ value.
Any thoughts? Please advise. Thanks.

Try using the read and write functions of streams instead, they are also
much faster than using iterators that way.

Jens

[pedagani]

Jens Theisen wrote:

pe******@gmail. com wrote:

I want to copy only a part of the binary file delimited by offset
values say START_OFFSET_ & END_OFFSET_ which can be as huge as a 50
Giga. Below is the program where I could set a START_OFFSET_ but could
not specify the END_OFFSET_ value.
Any thoughts? Please advise. Thanks.

Try using the read and write functions of streams instead, they are also
much faster than using iterators that way.

Jens

thank you for your reply. speed isn't very imp at this point, i'm
looking for a neat code. ny alternatives? thanks

[Jerry Coffin]

In article <11************ **********@75g2 000cwc.googlegr oups.com>,
pe******@gmail. com says...

I want to copy only a part of the binary file delimited by offset
values say START_OFFSET_ & END_OFFSET_ which can be as huge as a 50
Giga. Below is the program where I could set a START_OFFSET_ but could
not specify the END_OFFSET_ value.

Assuming (for the moment) that your implementation has something like
64-bit ints that have the range to directly address all possible file
sizes:

const std::ifstream:: fpos start(START_OFF SET);
const std::ifstream:: fpos stop(END_OFFSET +1);

std::copy(istre am_iterator<cha r>(is),
isstream_iterat or<char>(is)+ stop-start,
ostream_iterato r<char>(os));

There are, however, a fair number of implementations that simply don't
have any standard type with a range as large as the file sizes they
support (and specifically less than the 50 gigabytes you mention). In a
case like this, there's probably no standard/portable code to do what
you want.

--
Later,
Jerry.

The universe is a figment of its own imagination.

[pedagani]

Jerry Coffin wrote:

In article <11************ **********@75g2 000cwc.googlegr oups.com>,
pe******@gmail. com says...

I want to copy only a part of the binary file delimited by offset
values say START_OFFSET_ & END_OFFSET_ which can be as huge as a 50
Giga. Below is the program where I could set a START_OFFSET_ but could
not specify the END_OFFSET_ value.

Assuming (for the moment) that your implementation has something like
64-bit ints that have the range to directly address all possible file
sizes:

const std::ifstream:: fpos start(START_OFF SET);
const std::ifstream:: fpos stop(END_OFFSET +1);

std::copy(istre am_iterator<cha r>(is),
isstream_iterat or<char>(is)+ stop-start,
ostream_iterato r<char>(os));

There are, however, a fair number of implementations that simply don't
have any standard type with a range as large as the file sizes they
support (and specifically less than the 50 gigabytes you mention). In a
case like this, there's probably no standard/portable code to do what
you want.

--
Later,
Jerry.

The universe is a figment of its own imagination.

Thank you. Although it could not be directly applied for my
application, very insightful solution.