<div class="gmail_quote">On Wed, Apr 28, 2010 at 11:30 AM, David Gobbi <span dir="ltr"><<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
There were no comments about my changes to the wrappers so I went<br>
ahead and pushed them. So if anyone found vtkWrapPython.c to be<br>
completely incomprehensible before, they should find the code to be a<br>
little bit friendlier now.<br>
<br>
In the longer term, I'm looking at how the wrappers can be made to<br>
handle special types (with vtkVariant being the favorite). The<br>
wrappers used to handle special types fairly well, many years ago, but<br>
support for special types fell by the wayside when vtkObjectBase was<br>
introduced. Last night I did some work to resurrect the old<br>
special-type handling code with good results.<br></blockquote><div><br></div><div>I would love to see handling for vtkVariant, along with vtkStdString, and the unicode variant. It would also be great to have a way to wrap some C++ data structures so that they could be used from the wrapped languages. Is there a document on how this is/could be achieved? </div>
<div><br></div><div>Marcus</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class="h5"><br>
On Tue, Apr 27, 2010 at 8:23 AM, David Gobbi <<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>> wrote:<br>
> Hi All,<br>
><br>
> I've made a header file called vtkParseType.h that defines all of the<br>
> type constants used by vtkParse. The type constants are as follows:<br>
><br>
> #define VTK_PARSE_FLOAT 0x01<br>
> #define VTK_PARSE_VOID 0x02<br>
> #define VTK_PARSE_CHAR 0x03<br>
> #define VTK_PARSE_UNSIGNED_CHAR 0x13<br>
><br>
> etcetera. I've also modified vtkWrapPython.c to use these constants.<br>
> Any objections if I drop this new header file into VTK/Wrapping?<br>
><br>
> David<br></div></div></blockquote></div>