Re: *caution* severely OT!!

2011-09-14 Thread Chip Camden
Quoth Michel Talon on Wednesday, 14 September 2011: > Chad wrote: > > > I really don't think I'd say that Common Lisp is "syntactically very > > close to python [sic]". It's not fair to either Common Lisp or Python, > > On the contrary python is strikingly similar to a simplified version of > li

Re: *caution* severely OT!!

2011-09-14 Thread Michel Talon
Chad wrote: > I really don't think I'd say that Common Lisp is "syntactically very > close to python [sic]". It's not fair to either Common Lisp or Python, On the contrary python is strikingly similar to a simplified version of lisp without parentesis. It is not an original opinion by far, see t

Re: *caution* severely OT!!

2011-09-13 Thread Alejandro Imass
On Tue, Sep 13, 2011 at 4:42 PM, C. P. Ghost wrote: > On Tue, Sep 13, 2011 at 9:34 PM, Gary Kline wrote: >> guys, >> [...] > But if you really must, I suggest to port the program to > C++ instead of C, because there, you can make use of > the excellent STL data types and containers, that match

Re: *caution* severely OT!!

2011-09-13 Thread Chad Perrin
On Tue, Sep 13, 2011 at 11:37:48PM +0200, Michel Talon wrote: > > In the case of the example cited above, there was 0 performance benefit > of using C++ over pyrex. There is a language which is syntactically > very close to python and has the same facilities, but ends up in > machine code, this co

Re: *caution* severely OT!!

2011-09-13 Thread Gary Kline
On Tue, Sep 13, 2011 at 11:37:48PM +0200, Michel Talon wrote: > Date: Tue, 13 Sep 2011 23:37:48 +0200 > From: Michel Talon > Subject: Re: *caution* severely OT!! > To: Gary Kline , freebsd-questions@freebsd.org > > "C. P. Ghost" wrote: > > On Tue, Sep 13,

Re: *caution* severely OT!!

2011-09-13 Thread Michel Talon
"C. P. Ghost" wrote: > On Tue, Sep 13, 2011 at 9:34 PM, Gary Kline wrote: > > guys, > > > > can anyone start me on the way of porting a python program to C? > > tia, > > Gary, > > if you experience a performance bottleneck somewhere, > you may be better off performing some timings to > determin

Re: *caution* severely OT!!

2011-09-13 Thread C. P. Ghost
On Tue, Sep 13, 2011 at 9:34 PM, Gary Kline wrote: > guys, > > can anyone start me on the way of porting a python program to C? > tia, Gary, if you experience a performance bottleneck somewhere, you may be better off performing some timings to determine the exact cause, and then to port the spec

Re: *caution* severely OT!!

2011-09-13 Thread Alejandro Imass
On Tue, Sep 13, 2011 at 3:34 PM, Gary Kline wrote: > guys, > > can anyone start me on the way of porting a python program to C? > tia, > Porting as in re-write and it will depend on the complexity and perhaps objective/motivation of such rewrite. In any case, you will have to re-write the progra

Re: *caution* severely OT!!

2011-09-13 Thread Chuck Swiger
On Sep 13, 2011, at 12:34 PM, Gary Kline wrote: > can anyone start me on the way of porting a python program to C? Learn Python. Learn C. Analyze the Python program and document its functionality. Use this document as the functional spec for writing the C program. Regards, -- -Chuck _

*caution* severely OT!!

2011-09-13 Thread Gary Kline
guys, can anyone start me on the way of porting a python program to C? tia, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.o