Passing arrays to C funcions

[ds]

Hi all,

I have to pass an array of doubles to a legacy C function that copies
some data using memcpy. The code would look like this:

extern "C"{
void legacyCFunctionFill(void* arg);
}
....
int number=5;
double *my_array=(double*)calloc(number,sizeof(double));
legacyCFunctionFill((void*)my_array);
// Do sth useful
free(my_array);

The question is: if I change calloc() and free() with new and delete
[] will there be any issues, including portability issues? At first it
seems that it works, having tested that in my program. But I am not
sure if the memory allocated by calloc is the same and can be used the
same way as the memory allocated with new, especially on windows,
Linux and Sun.

Tahnks a lot!!!

-- dimitris

[=?ISO-8859-1?Q?Erik_Wikstr=F6m?=]

On 2007-09-04 17:54, ds wrote:

Hi all,

I have to pass an array of doubles to a legacy C function that copies
some data using memcpy. The code would look like this:

extern "C"{
void legacyCFunctionFill(void* arg);
}
...
int number=5;
double *my_array=(double*)calloc(number,sizeof(double));
legacyCFunctionFill((void*)my_array);
// Do sth useful
free(my_array);

The question is: if I change calloc() and free() with new and delete
[] will there be any issues, including portability issues? At first it
seems that it works, having tested that in my program. But I am not
sure if the memory allocated by calloc is the same and can be used the
same way as the memory allocated with new, especially on windows,
Linux and Sun.

As long as legacyCFunctionFill() does not try to deallocate the memory
using free() everything is fine. There is no difference in the memory
but you can not allocate memory with malloc and deallocate it with
delete (or the other way around).

--
Erik Wikström

[red floyd]

ds wrote:

Hi all,

I have to pass an array of doubles to a legacy C function that copies
some data using memcpy. The code would look like this:

extern "C"{
void legacyCFunctionFill(void* arg);
}
...
int number=5;
double *my_array=(double*)calloc(number,sizeof(double));
legacyCFunctionFill((void*)my_array);
// Do sth useful
free(my_array);

The question is: if I change calloc() and free() with new and delete
[] will there be any issues, including portability issues? At first it
seems that it works, having tested that in my program. But I am not
sure if the memory allocated by calloc is the same and can be used the
same way as the memory allocated with new, especially on windows,
Linux and Sun.

Assuming that legacyCFunctionFill() doesn't overrun the buffer (how
*does* it know how much space to fill?), it's fine to use
new[]/delete[]. A pointer is a pointer.
double *my_array = new double[number];
legacyCFunctionFill(my_array); // no cast to void* needed
delete[] my_array; // note use of delete[]

Alternatively:

std::vector<doublemyvec(number);
legacyCFunctionFill(&myvec[0]);
// no deletion necessary

[ds]

On Sep 4, 6:05 pm, red floyd <[e-mail]:

ds wrote:

Hi all,

I have to pass an array of doubles to a legacy C function that copies
some data using memcpy. The code would look like this:

extern "C"{
void legacyCFunctionFill(void* arg);
}
...
int number=5;
double *my_array=(double*)calloc(number,sizeof(double));
legacyCFunctionFill((void*)my_array);
// Do sth useful
free(my_array);

The question is: if I change calloc() and free() with new and delete
[] will there be any issues, including portability issues? At first it
seems that it works, having tested that in my program. But I am not
sure if the memory allocated by calloc is the same and can be used the
same way as the memory allocated with new, especially on windows,
Linux and Sun.

Assuming that legacyCFunctionFill() doesn't overrun the buffer (how
*does* it know how much space to fill?), it's fine to use
new[]/delete[]. A pointer is a pointer.

double *my_array = new double[number];
legacyCFunctionFill(my_array); // no cast to void* needed
delete[] my_array; // note use of delete[]

Alternatively:

std::vector<doublemyvec(number);
legacyCFunctionFill(&myvec[0]);
// no deletion necessary

Hi floyd,

it is clear that number has to be passed to the legacy function, which
performs a memcpy - no allocation/deallocation on the passed array.
Are you sure that std::vector allocates a continuous block? That would
be a nice solution for what I want to do, but I am afraid that not
all std::vector implementations allocate continuous memory....

thanks a lot!!

[red floyd]

ds wrote:

On Sep 4, 6:05 pm, red floyd <[e-mail]:

>>
std::vector<doublemyvec(number);
legacyCFunctionFill(&myvec[0]);
// no deletion necessary

Hi floyd,

it is clear that number has to be passed to the legacy function, which
performs a memcpy - no allocation/deallocation on the passed array.
Are you sure that std::vector allocates a continuous block? That would
be a nice solution for what I want to do, but I am afraid that not
all std::vector implementations allocate continuous memory....

Yeah, TC1 aka 14882:2003 guarantees contiguous memory.

[karthikbalaguru]

On Sep 4, 9:21 pm, ds <[e-mail]:

On Sep 4, 6:05 pm, red floyd <[e-mail]:

ds wrote:

Hi all,

I have to pass an array of doubles to a legacy C function that copies
some data using memcpy. The code would look like this:

extern "C"{
void legacyCFunctionFill(void* arg);
}
...
int number=5;
double *my_array=(double*)calloc(number,sizeof(double));
legacyCFunctionFill((void*)my_array);
// Do sth useful
free(my_array);

The question is: if I change calloc() and free() with new and delete
[] will there be any issues, including portability issues? At first it
seems that it works, having tested that in my program. But I am not
sure if the memory allocated by calloc is the same and can be used the
same way as the memory allocated with new, especially on windows,
Linux and Sun.

Assuming that legacyCFunctionFill() doesn't overrun the buffer (how
*does* it know how much space to fill?), it's fine to use
new[]/delete[]. A pointer is a pointer.

double *my_array = new double[number];
legacyCFunctionFill(my_array); // no cast to void* needed
delete[] my_array; // note use of delete[]

Alternatively:

std::vector<doublemyvec(number);
legacyCFunctionFill(&myvec[0]);
// no deletion necessary

Hi floyd,

it is clear that number has to be passed to the legacy function, which
performs a memcpy - no allocation/deallocation on the passed array.
Are you sure that std::vector allocates a continuous block? That would
be a nice solution for what I want to do, but I am afraid that not
all std::vector implementations allocate continuous memory....

thanks a lot!!- Hide quoted text -

- Show quoted text -

continuous memory ??

[=?ISO-8859-1?Q?Erik_Wikstr=F6m?=]

On 2007-09-04 18:21, ds wrote:

On Sep 4, 6:05 pm, red floyd <[e-mail]:

>ds wrote:

Hi all,

I have to pass an array of doubles to a legacy C function that copies
some data using memcpy. The code would look like this:

extern "C"{
void legacyCFunctionFill(void* arg);
}
...
int number=5;
double *my_array=(double*)calloc(number,sizeof(double));
legacyCFunctionFill((void*)my_array);
// Do sth useful
free(my_array);

The question is: if I change calloc() and free() with new and delete
[] will there be any issues, including portability issues? At first it
seems that it works, having tested that in my program. But I am not
sure if the memory allocated by calloc is the same and can be used the
same way as the memory allocated with new, especially on windows,
Linux and Sun.

Assuming that legacyCFunctionFill() doesn't overrun the buffer (how
*does* it know how much space to fill?), it's fine to use
new[]/delete[]. A pointer is a pointer.

double *my_array = new double[number];
legacyCFunctionFill(my_array); // no cast to void* needed
delete[] my_array; // note use of delete[]

Alternatively:

std::vector<doublemyvec(number);
legacyCFunctionFill(&myvec[0]);
// no deletion necessary

Hi floyd,

it is clear that number has to be passed to the legacy function, which
performs a memcpy - no allocation/deallocation on the passed array.
Are you sure that std::vector allocates a continuous block? That would
be a nice solution for what I want to do, but I am afraid that not
all std::vector implementations allocate continuous memory....

All standards compliant std::vectors allocate continuous blocks of memory.

--
Erik Wikström

[ds]

On Sep 4, 6:51 pm, Erik Wikström <[e-mail]:

On 2007-09-04 18:21, ds wrote:

On Sep 4, 6:05 pm, red floyd <[e-mail]:

ds wrote:
Hi all,

I have to pass an array of doubles to a legacy C function that copies
some data using memcpy. The code would look like this:

extern "C"{
void legacyCFunctionFill(void* arg);
}
...
int number=5;
double *my_array=(double*)calloc(number,sizeof(double));
legacyCFunctionFill((void*)my_array);
// Do sth useful
free(my_array);

The question is: if I change calloc() and free() with new and delete
[] will there be any issues, including portability issues? At first it
seems that it works, having tested that in my program. But I am not
sure if the memory allocated by calloc is the same and can be used the
same way as the memory allocated with new, especially on windows,
Linux and Sun.

Assuming that legacyCFunctionFill() doesn't overrun the buffer (how
*does* it know how much space to fill?), it's fine to use
new[]/delete[]. A pointer is a pointer.

double *my_array = new double[number];
legacyCFunctionFill(my_array); // no cast to void* needed
delete[] my_array; // note use of delete[]

Alternatively:

std::vector<doublemyvec(number);
legacyCFunctionFill(&myvec[0]);
// no deletion necessary

Hi floyd,

it is clear that number has to be passed to the legacy function, which
performs a memcpy - no allocation/deallocation on the passed array.
Are you sure that std::vector allocates a continuous block? That would
be a nice solution for what I want to do, but I am afraid that not
all std::vector implementations allocate continuous memory....

All standards compliant std::vectors allocate continuous blocks of memory.

--
Erik Wikström

I agree. But are all stl implementations complying to the standard?
Especially the MSVC implementation deviates in some cases...

[red floyd]

ds wrote:

On Sep 4, 6:51 pm, Erik Wikström <[e-mail]:

>All standards compliant std::vectors allocate continuous blocks of memory.

I agree. But are all stl implementations complying to the standard?
Especially the MSVC implementation deviates in some cases...

MSVC uses Dinkumware, so it should be pretty good. If you're talking
MSVC 7.1 or 8.0, it should be pretty compliant. If you're talking
MSVC6, then you need to upgrade.

Also, please don't quote sigs.

[=?ISO-8859-1?Q?Erik_Wikstr=F6m?=]

On 2007-09-04 18:44, karthikbalaguru wrote:

On Sep 4, 9:21 pm, ds <[e-mail]:

>On Sep 4, 6:05 pm, red floyd <[e-mail]:

ds wrote:
Hi all,

I have to pass an array of doubles to a legacy C function that copies
some data using memcpy. The code would look like this:

extern "C"{
void legacyCFunctionFill(void* arg);
}
...
int number=5;
double *my_array=(double*)calloc(number,sizeof(double));
legacyCFunctionFill((void*)my_array);
// Do sth useful
free(my_array);

The question is: if I change calloc() and free() with new and delete
[] will there be any issues, including portability issues? At first it
seems that it works, having tested that in my program. But I am not
sure if the memory allocated by calloc is the same and can be used the
same way as the memory allocated with new, especially on windows,
Linux and Sun.

Assuming that legacyCFunctionFill() doesn't overrun the buffer (how
*does* it know how much space to fill?), it's fine to use
new[]/delete[]. A pointer is a pointer.

double *my_array = new double[number];
legacyCFunctionFill(my_array); // no cast to void* needed
delete[] my_array; // note use of delete[]

Alternatively:

std::vector<doublemyvec(number);
legacyCFunctionFill(&myvec[0]);
// no deletion necessary

Hi floyd,

it is clear that number has to be passed to the legacy function, which
performs a memcpy - no allocation/deallocation on the passed array.
Are you sure that std::vector allocates a continuous block? That would
be a nice solution for what I want to do, but I am afraid that not
all std::vector implementations allocate continuous memory....

thanks a lot!!- Hide quoted text -

- Show quoted text -

continuous memory ??

Meaning that all the elements in the vector will be placed one after
another without any gaps (except padding), in other words that the
elements will be allocated just like in an array.

--
Erik Wikström

[blangela]

On Sep 4, 9:21 am, ds <[e-mail]:

On Sep 4, 6:05 pm, red floyd <[e-mail]:

ds wrote:

Hi all,

I have to pass an array of doubles to a legacy C function that copies
some data using memcpy. The code would look like this:

extern "C"{
void legacyCFunctionFill(void* arg);
}
...
int number=5;
double *my_array=(double*)calloc(number,sizeof(double));
legacyCFunctionFill((void*)my_array);
// Do sth useful
free(my_array);

The question is: if I change calloc() and free() with new and delete
[] will there be any issues, including portability issues? At first it
seems that it works, having tested that in my program. But I am not
sure if the memory allocated by calloc is the same and can be used the
same way as the memory allocated with new, especially on windows,
Linux and Sun.

Assuming that legacyCFunctionFill() doesn't overrun the buffer (how
*does* it know how much space to fill?), it's fine to use
new[]/delete[]. A pointer is a pointer.

double *my_array = new double[number];
legacyCFunctionFill(my_array); // no cast to void* needed
delete[] my_array; // note use of delete[]

Alternatively:

std::vector<doublemyvec(number);
legacyCFunctionFill(&myvec[0]);
// no deletion necessary

Hi floyd,

it is clear that number has to be passed to the legacy function, which
performs a memcpy - no allocation/deallocation on the passed array.
Are you sure that std::vector allocates a continuous block? That would
be a nice solution for what I want to do, but I am afraid that not
all std::vector implementations allocate continuous memory....

thanks a lot!!- Hide quoted text -

- Show quoted text -

Isn't the correct term "contiguous", not "continuous" ?

[Default User]

Erik Wikstrom wrote:

On 2007-09-04 18:44, karthikbalaguru wrote:

continuous memory ??

Meaning that all the elements in the vector will be placed one after
another without any gaps (except padding), in other words that the
elements will be allocated just like in an array.

I think "contiguous" is somewhat more common, but either should work
fine.

Brian

[Jim Langston]

"blangela" <Bo***********@telus.netwrote in message
news:11**********************@o80g2000hse.googlegr oups.com...

On Sep 4, 9:21 am, ds <[e-mail]:

>On Sep 4, 6:05 pm, red floyd <[e-mail]:

ds wrote:
Hi all,

I have to pass an array of doubles to a legacy C function that copies
some data using memcpy. The code would look like this:

extern "C"{
void legacyCFunctionFill(void* arg);
}
...
int number=5;
double *my_array=(double*)calloc(number,sizeof(double));
legacyCFunctionFill((void*)my_array);
// Do sth useful
free(my_array);

The question is: if I change calloc() and free() with new and delete
[] will there be any issues, including portability issues? At first
it
seems that it works, having tested that in my program. But I am not
sure if the memory allocated by calloc is the same and can be used
the
same way as the memory allocated with new, especially on windows,
Linux and Sun.

Assuming that legacyCFunctionFill() doesn't overrun the buffer (how
*does* it know how much space to fill?), it's fine to use
new[]/delete[]. A pointer is a pointer.

double *my_array = new double[number];
legacyCFunctionFill(my_array); // no cast to void* needed
delete[] my_array; // note use of delete[]

Alternatively:

std::vector<doublemyvec(number);
legacyCFunctionFill(&myvec[0]);
// no deletion necessary

Hi floyd,

it is clear that number has to be passed to the legacy function, which
performs a memcpy - no allocation/deallocation on the passed array.
Are you sure that std::vector allocates a continuous block? That would
be a nice solution for what I want to do, but I am afraid that not
all std::vector implementations allocate continuous memory....

Isn't the correct term "contiguous", not "continuous" ?

Continuous memory is contiguous, and contiguous memory is continuous.
Contiguous is the offical term, but it means continuous anyway.

From dictionary.com definition #1 (which is what we use) for contiguous:
1. touching; in contact.

From dictoinary.com definition #2 (which woudl apply) for continuous:
2. being in immediate connection or spatial relationship: a continuous
series of blasts; a continuous row of warehouses.

They are fairly synonymous in this context.

[ds]

red floyd wrote:

ds wrote:

Erik Wikström wrote:

All standards compliant std::vectors allocate continuous blocks of memory.

I agree. But are all stl implementations complying to the standard?
Especially the MSVC implementation deviates in some cases...

MSVC uses Dinkumware, so it should be pretty good. If you're talking
MSVC 7.1 or 8.0, it should be pretty compliant. If you're talking
MSVC6, then you need to upgrade.

Also, please don't quote sigs.

Sorry...

I am talking MSVC 8.0 pro. For example check out this one:

http://www.cplusplus.com/reference/i...uf/setbuf.html

this is not implemented in <sstream- at least in my stl...

[=?ISO-8859-1?Q?Erik_Wikstr=F6m?=]

On 2007-09-05 10:35, ds wrote:

red floyd wrote:

>ds wrote:

Erik Wikström wrote:
All standards compliant std::vectors allocate continuous blocks of memory.

I agree. But are all stl implementations complying to the standard?
Especially the MSVC implementation deviates in some cases...

MSVC uses Dinkumware, so it should be pretty good. If you're talking
MSVC 7.1 or 8.0, it should be pretty compliant. If you're talking
MSVC6, then you need to upgrade.

Also, please don't quote sigs.

Sorry...

I am talking MSVC 8.0 pro. For example check out this one:

http://www.cplusplus.com/reference/i...uf/setbuf.html

this is not implemented in <sstream- at least in my stl...

What do you mean is not implemented?

#include <sstream>
int main()
{
std::stringstream ss;
char* buf = new char[512];
ss.rdbuf()->setbuf(buf, 512);
}

Fails to compile on my MSVC 8.0 Pro because setbuf() is protected, that
seems like it is implemented to me.

--
Erik Wikström