Re: report progress from C function

2006-11-02 Thread Hendrik van Rooyen
"Fredrik Lundh" <[EMAIL PROTECTED]> wrote: > Michael S wrote: > > > I downloaded Pyrex and ran it through their own > > example. The code looks quite messy, and I even saw a > > few "goto"s. > > looked at the assembler output from your C compiler lately? > > LOL! - is it even possible to c

Re: report progress from C function

2006-11-01 Thread John Machin
On 2/11/2006 12:53 AM, Michael S wrote: > I downloaded Pyrex and ran it through their own > example. The code looks quite messy, and I even saw a > few "goto"s. > I think I will stick with my own code for now. > Thanks in any case. If your own code is doing the right amount of reference counting,

Re: report progress from C function

2006-11-01 Thread Fredrik Lundh
Michael S wrote: > What if it doesn't do exactly what you need to? How do > you debug through that code? same way as you'd hunt for bugs in the Python-to-bytecode compiler, or your C compiler. -- http://mail.python.org/mailman/listinfo/python-list

Re: report progress from C function

2006-11-01 Thread Michael S
What if it doesn't do exactly what you need to? How do you debug through that code? --- Fredrik Lundh <[EMAIL PROTECTED]> wrote: > Michael S wrote: > > > My assembler is very basic, so it wouldn't help, > while > > my C is OK, well sort of. > > > > BTW. Neither have I looked at the machine code

Re: report progress from C function

2006-11-01 Thread Fredrik Lundh
Michael S wrote: > My assembler is very basic, so it wouldn't help, while > my C is OK, well sort of. > > BTW. Neither have I looked at the machine code that > the assembler produces. so why does the output from Pyrex worry you? it's a compiler, after all. -- http://mail.python.org/mailman

Re: report progress from C function

2006-11-01 Thread Michael S
My assembler is very basic, so it wouldn't help, while my C is OK, well sort of. BTW. Neither have I looked at the machine code that the assembler produces. --- Fredrik Lundh <[EMAIL PROTECTED]> wrote: > Michael S wrote: > > > I downloaded Pyrex and ran it through their own > > example. The co

Re: report progress from C function

2006-11-01 Thread Fredrik Lundh
Michael S wrote: > I downloaded Pyrex and ran it through their own > example. The code looks quite messy, and I even saw a > few "goto"s. looked at the assembler output from your C compiler lately? -- http://mail.python.org/mailman/listinfo/python-list

Re: report progress from C function

2006-11-01 Thread Michael S
I downloaded Pyrex and ran it through their own example. The code looks quite messy, and I even saw a few "goto"s. I think I will stick with my own code for now. Thanks in any case. --- John Machin <[EMAIL PROTECTED]> wrote: > Michael S wrote: > > Good day all. > > > > I rewrote part of my progr

Re: report progress from C function

2006-10-31 Thread Michael S
> BTW, why did you rewrite in C rarher than using > Pyrex? I was not aware of pyrex. I didn't really mind doing some C, it made me remember the syntax. Thanks a lot. I did think that I could pack a function address as a parameter. --- John Machin <[EMAIL PROTECTED]> wrote: > Michael S wrote: > >

Re: report progress from C function

2006-10-31 Thread John Machin
Michael S wrote: > Good day all. > > I rewrote part of my program in C, it's a usually a > long task. I wanted to be able to report the progress > back to my python program. In my module (in addition > to the function that performs the above-mentioned > task) there is a function that returns the v

report progress from C function

2006-10-31 Thread Michael S
Good day all. I rewrote part of my program in C, it's a usually a long task. I wanted to be able to report the progress back to my python program. In my module (in addition to the function that performs the above-mentioned task) there is a function that returns the variable, indicating the progre