Spent most of the day doing biology things, but managed to help clean up a small CGIHTTPServer problem and also contributed a doc patch to distutils to fix my earlier complaints.
A couple of short responses to advogato users:
gnutizen asks about learning good C programming style. My suggestions are:
- Read other people's code, a lot. Back in the early '90s when I first
dove into C, I spent some time getting GNU utilities to compile on both
an SGI and a weird BSD/SYSV crossover machine we had. I learned a helluva
lot about C programming from that, especially with respect to portability.
- Fix other people's code, a lot. Ditto above.
- Work on small parts of some open source project or another. I worked
on a conquer-like game called dominion, with a group of pretty good hackers.
In the end I think the overall design was lacking, but the nitty gritty
of each individual code file was crafted by very experienced C hackers.
- Read a lot. For large-scale program design, Lakos's
C++ book is fantastic; Stevens'
book on UNIX Network Programming was a prime source of material
for me before that. Books like Pragmatic
Programmer and so on offer a lot of advice that seems too obvious
to be useful, but is in fact quite useful.
Anyway, that's my 2 cents (FWIW, IMO ;). These days I find myself writing relatively little C++ code, and even less straight C code, but it's incredibly useful for hacking on other people's code.
etrepum says that "Platypus is not what you want for packaging Python applications". Without more of a reason, and never having used Platypus myself, I don't know why. However the page he points me towards contains not only py2app, which looks pretty cool, but also a variety of other very nifty looking Python tools for interaction with OS X.
--titus