[prev in list] [next in list] [prev in thread] [next in thread] 

List:       vtk-developers
Subject:    Re: [Fwd: [vtk-developers] Modification to vtkPythonUtil to support
From:       David Gobbi <dgobbi () imaging ! robarts ! ca>
Date:       2003-03-23 21:23:02
Message-ID: Pine.GSO.4.44.0303231617170.16658-100000 () theremin ! irus ! robarts ! ca
[Download RAW message or body]

On Sun, 23 Mar 2003, Charl P. Botha wrote:

> On Fri, Mar 21, 2003 at 04:59:20PM -0500, David Gobbi wrote:
> > I like the idea, but I don't really like the use of "string0" as a
> > data type descriptor.  Maybe the use of a python 'type' object would
> > be better, i.e. types.StringType would signify a string.  Also I
>
> The reason why I chose "string0" is because it refers to the C++ type and
> NOT the Python type.  The calldata could be a null-terminated string
> ("string0") or a C++ string ("string").  Both would however map to a Python
> StringType, so it would seem that using a types.StringType is not the best
> option.  Your thoughts?

True enough, the CallData is indeed C/C++ data.

I've also thought that, since any particular type of 'Event' is going to
have a particular type of 'CallData' (or at least this _should_ be
the case) maybe eventually the CallDataType can be set automatically.

 - David


[prev in list] [next in list] [prev in thread] [next in thread]