mark florisson, 07.08.2012 13:00:
> On 7 August 2012 11:59, mark florisson wrote:
>> On 7 August 2012 11:44, Stefan Behnel wrote:
>>> mark florisson, 07.08.2012 12:33:
I'd say write a wrapper function that does the check, or use an object
that encapsulates the buffer allocation and functi
On 7 August 2012 11:59, mark florisson wrote:
> On 7 August 2012 11:44, Stefan Behnel wrote:
>> mark florisson, 07.08.2012 12:33:
>>> I'd say write a wrapper function that does the check, or use an object
>>> that encapsulates the buffer allocation and functions. I'm not sure
>>> we'd want extra
On 7 August 2012 11:44, Stefan Behnel wrote:
> mark florisson, 07.08.2012 12:33:
>> I'd say write a wrapper function that does the check, or use an object
>> that encapsulates the buffer allocation and functions. I'm not sure
>> we'd want extra syntax for this. Calling functions is already
>> comp
mark florisson, 07.08.2012 12:33:
> I'd say write a wrapper function that does the check, or use an object
> that encapsulates the buffer allocation and functions. I'm not sure
> we'd want extra syntax for this. Calling functions is already
> complicated, this will complicate it even further.
Funn
On 7 August 2012 10:53, Stefan Behnel wrote:
> Hi,
>
> given how ubiquitous manual memory management is in C, I think it would be
> nice to let Cython generate the exception raising also for C, not only for
> C++. The difference is this:
>
> cdef extern from "...":
> char* make_new_buffer(
Hi,
given how ubiquitous manual memory management is in C, I think it would be
nice to let Cython generate the exception raising also for C, not only for
C++. The difference is this:
cdef extern from "...":
char* make_new_buffer() except NULL as MemoryError
int append_to_buffer(char
On 6 August 2012 22:58, Stefan Behnel wrote:
> Hi,
>
> please correct me if I'm missing something, but besides the fused types
> default value thing, I currently see two open issues for 0.17. One is the
> 32bit problem we have in the buffer code, the other one is the "vile hack"
> that Robert adde
Hi,
building the documentation currently yields a number of Sphinx warnings:
https://sage.math.washington.edu:8091/hudson/job/cython-docs/lastSuccessfulBuild/warnings1Result/
It would be nice if someone found the time to clean some of them up.
Stefan
