Hm,
after thinking about it a while, I figured, there is nothing like a
packed type.
I suppose you always unpack the data from disc into the given memory area.
This has the advantage, of using the same code path later on, for
handling the
member access.
So for the binding part to ruby, I would simply unpack into the given
memory area, and not care at all, if this is a system type, or not.
I don't really like this, as one would rely on the caller to make sure
that the given memory area is preinitialized properly.
Just out of curiosity, is there a way in typelib, to get a preinitialized
memory area for a type containing a virtual method ?
Greetings
Janosch
Am 08.06.2014 11:12, schrieb Janosch Machowinski:
> A packed type is the the representation on the disc.
> A unpacked type would be a correct initialized type
> with the data from the packed type copied to the correct
> offsets.
> Greetings
> Janosch
>
> Am 08.06.2014 11:01, schrieb Sylvain Joyeux:
>> On Sat, Jun 7, 2014 at 11:13 PM, Janosch Machowinski
>> <[email protected] <mailto:[email protected]>> wrote:
>>
>> Anyway, giving out unpacked types, seems not to work,
>> as one needs the RTT typesystem for unpacking (if I
>> understood the code right...)
>> How would I create a packed typelib::Value on the C++
>> side ?
>>
>> What do you call "packed" and "unpacked" there ? /me very confused
>>
>> Sylvain
> _______________________________________________
> Rock-dev mailing list
> [email protected]
> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
_______________________________________________
Rock-dev mailing list
[email protected]
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
