Hrvoje Niksic, 11.03.2012 02:03:
> Stefan Behnel writes:
>>> which is the standard way of extending Python with high-performance
>>> (and/or system-specific) C code.
>>
>> Well, it's *one* way. Certainly not the easiest way, neither the most
>> portable and you'll have a hard time making it the fa
On 3/10/2012 8:03 PM, Hrvoje Niksic wrote:
Stefan Behnel writes:
which is the standard way of extending Python with high-performance
(and/or system-specific) C code.
Well, it's *one* way. Certainly not the easiest way, neither the most
portable and you'll have a hard time making it the fast
Stefan Behnel writes:
>> which is the standard way of extending Python with high-performance
>> (and/or system-specific) C code.
>
> Well, it's *one* way. Certainly not the easiest way, neither the most
> portable and you'll have a hard time making it the fastest.
I didn't say it was easy, but
Hrvoje Niksic, 07.03.2012 16:48:
> Alec Taylor writes:
>
>> The source-code used has been made available:
>> http://www.cosc.canterbury.ac.nz/research/RG/alg/ttheap.h
>> http://www.cosc.canterbury.ac.nz/research/RG/alg/ttheap.c
>>
>> I plan on wrapping it in a class.
>
> You should get acquainted
Alec Taylor writes:
> The source-code used has been made available:
> http://www.cosc.canterbury.ac.nz/research/RG/alg/ttheap.h
> http://www.cosc.canterbury.ac.nz/research/RG/alg/ttheap.c
>
> I plan on wrapping it in a class.
You should get acquainted with the Python/C API, which is the standard
Alec Taylor, 07.03.2012 15:25:
> I am planning to port the 2-3 heap data-structure as described by
> Professor Tadao Takaoka in Theory of 2-3 Heaps published in 1999 and
> available in PDF:
> http://www.cosc.canterbury.ac.nz/tad.takaoka/2-3heaps.pdf
>
> The source-code used has been made available
