On the other hand, would clrtype be something good enough to be developed
as a part of `clr`?
2015-05-04 11:00 GMT-04:30 Slide :
> The other option is to use ctypes. This is more like CPython.
>
> On Mon, May 4, 2015 at 8:15 AM Markus Schaber
> wrote:
>
>> Hi,
>>
>> Von: Sebastián Magrí
>> > Wel
The other option is to use ctypes. This is more like CPython.
On Mon, May 4, 2015 at 8:15 AM Markus Schaber wrote:
> Hi,
>
> Von: Sebastián Magrí
> > Well that's actually my fault for not checking out that first (wrt
> clrtype). Is there any other well tested/standard option to do what clrtype
>
Hi,
Von: Sebastián Magrí
> Well that's actually my fault for not checking out that first (wrt clrtype).
> Is there any other well tested/standard option to do what clrtype does
> nowadays?
> I've actually opted for installing IronPython in the client machines, but I
> will look at fuslogvw to c
Well that's actually my fault for not checking out that first (wrt
clrtype). Is there any other well tested/standard option to do what clrtype
does nowadays?
I've actually opted for installing IronPython in the client machines, but I
will look at fuslogvw to check this out.
Best Regards,
2015-04
Dear all
I'd like to propose https://github.com/kunom/ipy-weakref (the ipy-27-maint
branch) to be included into the main IronPython code base. It fixes for me
various random SystemError and ValueError exceptions in the _weakref.cs module.
Please note that while my patch changes (and hopefully imp
