the parameters or in the
> fields of your Union and compare them between CPython and IronPython that’d
> probably be useful. Or even just how MaxLColumnDefine is created would be
> useful.
>
>
>
> *From:* users-boun...@lists.ironpython.com [mailto:
> users-boun...@lists.iron
uffer.pszVal. With CPython the correct code is:
print pBuffer.pszVal[0].value
which results in an error in IronPython:
'str' object has no attribute 'value'
IronPython ctypes wants this line to be:
print pBuffer.pszVal[0]
On Tue, Mar 15, 2011 at 1:27 PM, David Welden wrote:
&
I have a ctypes module that is failing under Iron Python. The module is
hosted at http://essbasepy.googlecode.com if anyone wants to view the
source.
I have a union defined as:
class output_buffer(Union):
_fields_ = [('pdVal', c_double * MAX_REC),
('pbVal', c_ubyte * MAX_REC),
Any news on work item 25106: ctypes: no support for Union? ctypes is not
really done if unions are unsupported.
1. [ANN]: IronPython 2.6 final (Dino Viehland)
>
>
___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.
First a comment: Absolutely wonderful stuff you have been doing (socket, db-api, etc.)! Please keep up the good work.And now the question: I notice you have begun some exploratory work on a port of ctypes. I would like to use this to port one of my ctypes interfaces to Iron Python, but alas, I am n
