Re: Programming in Python with a view to extending in C at a later date.

2009-04-22 Thread Stefan Behnel
Hi, dug.armad...@googlemail.com wrote: > Say you set out to program in Python knowing that you will be > converting parts of it into C ( or maybe C++) at a later date, but you > do not know which parts. > > Can you give any general Python structure / syntax advice that if > implemented from the s

Re: Programming in Python with a view to extending in C at a later date.

2009-04-21 Thread bobicanprogram
On Apr 20, 2:57 pm, "dug.armad...@googlemail.com" wrote: > Hi, > > Say you set out to program in Python knowing that you will be > converting parts of it into C ( or maybe C++) at a later date, but you > do not know which parts. > > Can you give any general Python structure / syntax advice that if

Re: Programming in Python with a view to extending in C at a later date.

2009-04-21 Thread Carl Banks
On Apr 20, 11:57 am, "dug.armad...@googlemail.com" wrote: > Say you set out to program in Python knowing that you will be > converting parts of it into C ( or maybe C++) at a later date, but you > do not know which parts. > > Can you give any general Python structure / syntax advice that if > impl

Re: Programming in Python with a view to extending in C at a later date.

2009-04-20 Thread Terry Reedy
dug.armad...@googlemail.com wrote: Hi, Say you set out to program in Python knowing that you will be converting parts of it into C ( or maybe C++) at a later date, but you do not know which parts. I presume because you intend to wait for profile results. Good. Of course, you might even find y

Re: Programming in Python with a view to extending in C at a later date.

2009-04-20 Thread Lawson English
Lawson English wrote: Daniel Stutzbach wrote: On Mon, Apr 20, 2009 at 1:57 PM, dug.armad...@googlemail.com > wrote: Say you set out to program in Python knowing that you will be converting parts of it into C ( or

Re: Programming in Python with a view to extending in C at a later date.

2009-04-20 Thread Lawson English
Daniel Stutzbach wrote: On Mon, Apr 20, 2009 at 1:57 PM, dug.armad...@googlemail.com > wrote: Say you set out to program in Python knowing that you will be converting parts of it into C ( or maybe C++) at a later d

Re: Programming in Python with a view to extending in C at a later date.

2009-04-20 Thread Scott David Daniels
dug.armad...@googlemail.com wrote: Say you set out to program in Python knowing that you will be converting parts of it into C ( or maybe C++) at a later date, but you do not know which parts. Can you give any general Python structure / syntax advice that if implemented from the start, will make

Re: Programming in Python with a view to extending in C at a later date.

2009-04-20 Thread Daniel Stutzbach
On Mon, Apr 20, 2009 at 1:57 PM, dug.armad...@googlemail.com < dug.armad...@googlemail.com> wrote: > Say you set out to program in Python knowing that you will be > converting parts of it into C ( or maybe C++) at a later date, but you > do not know which parts. > I often use Python for rapid pro

Programming in Python with a view to extending in C at a later date.

2009-04-20 Thread dug.armad...@googlemail.com
Hi, Say you set out to program in Python knowing that you will be converting parts of it into C ( or maybe C++) at a later date, but you do not know which parts. Can you give any general Python structure / syntax advice that if implemented from the start, will make this future task less painful.