Re: Coding style article with interesting section on white space

[EMAIL PROTECTED] wrote: The recent Pystone Benchmark message says that Python is only 75% as fast on Linux as on Windows. no, it really only says that the Pystone benchmark is 75% as fast as Linux as on Windows, on the poster's hardware, using his configuration, and using different compilers.

Re: Coding style article with interesting section on white space

[EMAIL PROTECTED] wrote: Michael Tobis wrote: (unwisely taking the bait...) If you like your language to look like this http://www.cs.rpi.edu/~szymansk/OOF90/bugs.html then more power to you. Thanks for pointing out that interesting article on Fortran 90 bugs. How long would a

Re: Coding style article with interesting section on white space

Alex Martelli wrote: snip For scientific computation, consider the case of Numeric and Numarray. I don't think Numeric binaries are available for Python 2.4, http://www4.ncsu.edu/~jdbrandm/Numeric-23.6.win32-py2.4.exe ? Just googled and visited the first hit -- I don't currently use

Re: Coding style article with interesting section on white space

In article [EMAIL PROTECTED], Alex Martelli [EMAIL PROTECTED] writes You're saying that using a different and better compiler cannot speed the execution of your Fortran program by 25% when you move it from one platform to another...?! This seems totally absurd to me, and yet I see no other way

Re: Coding style article with interesting section on white space

[EMAIL PROTECTED] wrote: I had in mind the Polyhedron Fortran 90 benchmarks for Windows and Linux on Intel x86 at http://www.polyhedron.co.uk/compare/linux/f90bench_p4.html and http://www.polyhedron.co.uk/compare/win32/f90bench_p4.html . The speed differences of Absoft, Intel, and Lahey

Re: Coding style article with interesting section on white space

[EMAIL PROTECTED] wrote: Michael Tobis wrote: (unwisely taking the bait...) If you like your language to look like this http://www.cs.rpi.edu/~szymansk/OOF90/bugs.html then more power to you. Thanks for pointing out that interesting article on Fortran 90 bugs. How long would a

Re: Coding style article with interesting section on white space

On 30 Jan 2005 [EMAIL PROTECTED] wrote: Sparring with Alex Martelli is like boxing Mike Tyson, except that one experiences brain enhancement rather than brain damage :). +1 QOTW :-) Michael. -- http://mail.python.org/mailman/listinfo/python-list

Fortran pros and cons (was Re: Coding style article with interesting section on white space)

Michael Tobis wrote: Fortran programmers are generally happy with the portability of the language. Until they try to port something...? Honestly, I can't imagine where anyone would get this impression. From the fact that Fortran has been used on hundreds of platforms and that many

Re: Fortran pros and cons (was Re: Coding style article with interesting section on white space)

Michael Tobis wrote: [EMAIL PROTECTED] wrote: Michael Tobis wrote: Fortran 90/95 is more expressive than Fortran 77 in many ways, as described in ... http://www.nr.com/CiP97.pdf . ... expresses more science per line of code and per programming workday. The example shown on p 10

Coding style article with interesting section on white space

Thought some folks here might find this one interesting. No great revelations, just a fairly sensible piece on writing readable code :) The whole article: http://www.acmqueue.com/modules.php?name=Contentpa=showpagepid=271page=1 The section specifically on white space:

Re: Coding style article with interesting section on white space

Thanx Nick -- http://mail.python.org/mailman/listinfo/python-list

Re: Coding style article with interesting section on white space

Nick Coghlan wrote: Thought some folks here might find this one interesting. No great revelations, just a fairly sensible piece on writing readable code :) The whole article: http://www.acmqueue.com/modules.php?name=Contentpa=showpagepid=271page=1 The section specifically on white space:

Re: Coding style article with interesting section on white space

In article [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: . . . One ought to do a little research before publishing an article. Apparently, many authors and editors are too lazy to do so. ... and/or ignorant or uncultured.

Re: Coding style article with interesting section on white space

[EMAIL PROTECTED] wrote: The suggestions in the cited article, How Not to Write FORTRAN in Any Language, are reasonable but elementary and can be followed in Fortran 90/95/2003 as well as any other language. What infuriates me is that the author writes as if Fortran has not evolved since the

Re: Coding style article with interesting section on white space

(unwisely taking the bait...) If you like your language to look like this http://www.cs.rpi.edu/~szymansk/OOF90/bugs.html then more power to you. I prefer my languages to be portable, terse and expressive. That's why I like Python. If you want your language to be obscure, ill-defined and

Re: Coding style article with interesting section on white space

Michael Tobis wrote: (unwisely taking the bait...) If you like your language to look like this http://www.cs.rpi.edu/~szymansk/OOF90/bugs.html then more power to you. Thanks for pointing out that interesting article on Fortran 90 bugs. How long would a comparable C++ list be? Even Python has