Re: [Swig-user] unsigned char* manipulations

[Christopher B. <Chr...@no...>]

hannit wrote:
> Seems like the problem is related to the fact that the original data is
> binary ans python (of course) converts it to a string.

well, despite its name, a python string is really just an array of 
bytes, so it is an appropriate type for a char pointer.

>> I have a c++ class that has the following data functions:
>> unsigned char* getSentDataP();

This is a pointer, how do you know how long the data block is? SWIG is 
going to need to know that to create a python string.

-Chris


-- 
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chr...@no...