-
wzdd: On computer programming
Is this really what we do? funny programming -
YouTube - PostSecret Video made by the owner of postsecret.com Post Secret is the bleeding of an entire species. art video blog
-
armstrong_thesis_2003.pdf (application/pdf Object) erlang programming concurrency distributed thesis
-
Wikidbase: the ultimate groupware application, possibly Very interesting project here. Wiki with formatting that controls a database.
-
Teach a Kid to Program / Wired How To's programming education parenting
-
Cleversafe Open Source Community storage distributed grid
-
eBay My World - crystal-forest
-
WinSplit Revolution Still trying to find better ways to utilize my screens. This looks promising. display productivity monitor software windows free
- diagrammes modernes: Friendly Readable ID Stringspython algorithm generation debugging
-
The Independent Gaming Source's (Opinionated) Guide to Indie Gaming Really good list of great indie games. games indie list free fun
-
The Wii Remote API - Opera Developer Community web wii interface javascript
-
Multiverse mmorpg games development
-
Paul Buchheit: The first thing that you need to understand about humans brain people interesting psychology
-
Not Worried About the Future future religion children intelligence
At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful
Comments