You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been looking into how to manually translate IDL files (or perhaps write a tool at some point to do so) to the required ctypes definitions used in this library, but I'm somewhat confused as to how sequences are handled. Are you supposed to represent something like this:
struct SomeElement
{
string someData;// ... and some other fields
};
struct SomeKey
{
unsigned longlong low; // first eight bytes
unsigned longlong high; // last eight bytes
};
struct SomeSequence
{
long id;
unsigned long sequenceIndex;
sequence<SomeElement> elements;
};
#pragma keylist SomeSequence id.low id.high sequenceIndex
Specifically I'm unsure of how to handle:
Sequences. Do I have to use DDSSequence and manually serialize the elements to the _buffer member? (I don't really know how the low level API used by the generated files from idlpp works, I have previously only used the isocpp2 generator, I looked at the code now and it seems to treat everything as void* pointers and call C API functions to allocate for example arrays)
Keys: Do I actually need to care about this at all? Looking at DDSKeyValue for example I don't see anything specific to mark what part is the key, like in the IDL file.
It would be great to either have some slightly non-trivial examples included, or perhaps some basic documentation.
The text was updated successfully, but these errors were encountered:
I have been looking into how to manually translate IDL files (or perhaps write a tool at some point to do so) to the required ctypes definitions used in this library, but I'm somewhat confused as to how sequences are handled. Are you supposed to represent something like this:
Specifically I'm unsure of how to handle:
It would be great to either have some slightly non-trivial examples included, or perhaps some basic documentation.
The text was updated successfully, but these errors were encountered: