ions of the the initial prototype was written
> on a 286 box under MS-DOS, but the bulk was developed on tru64 and
> deployed on tru64...)
Well, there's 64-bit support and then there's 64-bit support. While all Unix
or Unix like OSs follow LP64 model, I believe Win64 follow
t supported by ctypes. The underlying issue is
lack of closure API support for ARM in libffi. I see a patch available at
http://handhelds.org/~pb/arm-libffi.dpatch, that should be hopefully a good
starting point. ctypes CVS has a libffi_arm_wince directory, which also
seems to support closure API.
Gan
>>>>> Thomas Heller <[EMAIL PROTECTED]> writes:
> Ganesan Rajagopal wrote:
>>>>>>> Neal Norwitz <[EMAIL PROTECTED]> writes:
>>
>>> Please add your project ideas to the existing set at
>>
>>> http://wiki.python.o
>>>>> "Guido" == Guido van Rossum <[EMAIL PROTECTED]> writes:
> On 4/20/06, Ganesan Rajagopal <[EMAIL PROTECTED]> wrote:
>> I started editing the page, then I thought I'd first post here to get your
>> feedback :-).
> That appro
ould mean establishing which *was* the best available
> which, as we've seen this week, may not be easy.
There is a C aync event notification library called libevent which wraps
kqueue, epoll, /dev/poll etc and provides a unified interface (See
http://www.mo
only missing significant architecture is ARM because of
lack of FFI support.
Ganesan
--
Ganesan Rajagopal (rganesan at debian.org) | GPG Key: 1024D/5D8C12EA
Web: http://employees.org/~rganesan| http://rganesan.blogspot.com
___
Python-Dev
