comp.lang.idl-pvwave archive: archive » Re: C Alignment/IDL structures

Home » Public Forums » archive » Re: C Alignment/IDL structures

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: C Alignment/IDL structures [message #43068]

Wed, 23 March 2005 08:20

joey
Messages: 5
Registered: March 2005

Junior Member

Nigel Wade <nmw@ion.le.ac.uk> wrote:
>>
>> // Copy the real data
>>
>> unsigned long pos = 0;
>> unsigned char *myStructureThatLooksLikeTags = malloc
> (_totalSpaceNeeded
>> * _dataIDL.size
> ());
>> for (unsigned int i = 0; i < _dataIDL.size (); i++) {
>> memcpy (&(myStructureThatLooksLikeTags [pos]), _dataIDL [i],
>> _totalSpaceNeeded);
>> pos += _totalSpaceNeeded;
>> }
>>

> In your code you copy memory from two disimilar data structures using
> memcpy() taking no account of alignment. Your memory allocation uses the
> construct _dataIDL.size(), what is that? Since you haven't shown us the

_dataIDL is actually a C++ vector of unsigned char *'s. This group of
char * is created from a C++ map of data. The map is a tagname and data
value. Complex, isn't it? I'd like to think its elegant since I can very
simply wrap any C/C++ and interface it with IDL. However, if one of the
items in the map is a structure itself, I think it has problem.

Randall: I got your code and I am going to look at it. I appreciate the
example! I am going to try throwing a structure with a double in there
and see if I can generate the same problem I am seeing on my code.

Cheers,
Joey

Report message to a moderator

[Message index]

		Re: C Alignment/IDL structures By: joey on Wed, 23 March 2005 08:20
		Re: C Alignment/IDL structures By: Nigel Wade on Tue, 22 March 2005 02:34
		Re: C Alignment/IDL structures By: Randall Skelton on Mon, 21 March 2005 15:03
		Re: C Alignment/IDL structures By: Nigel Wade on Thu, 31 March 2005 02:46

Previous Topic:	Matrix expansion performance
Next Topic:	Re: MISSING_VALUE

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Nov 30 10:18:43 PST 2025

Total time taken to generate the page: 1.35889 seconds