Maybe it’s the weather; or maybe I’m bored. I was just thinking – why am I still doing all my Objective C coding with XCode? Is it that good? Meeehh.
Seriously, I used to type less code. In fact I was annoyed enough with your average off the shelf IDE that I used to write all my code using my own tools. While it’s gonna take more than a rain check for me to pick up ee-ide and integrate with ObjC, there’s something left from this bygone era – the urge to meta-program.
So putting aside the more interesting question (what do I want to analyze? What would I use meta-programming for?) I found myself wondering once again: if not java, what am I supposed to write my utilities in?
I’m pretty used to Objective C by now, but it’s not the kind of language that I want to use to write rough and ready utilities. Python comes to mind. I have this unqualified connection with Python: using it to write our blender scripts, suffering from the lack of straight OO semantics, irked by the lack of typing and compile time checking, amused by the syntactic sugar (e.g. sequences), encouraged by the no-nonsense, generous approach to standard libraries.
I prepared a bunch of references to skim through. I think I’ll be going old school, approaching utilities with the command line before (hopefully) integrating with XCode.
Yea that’s it for today. My refs are below. Just basic stuff.
Varied tutorials for working with files
- Working with files in Python (dream.in.code)
- Working with file objects (diveintopython.net)
- Top 4 ways to work with files in python (python.about.com)
- Working with files (marakana.com)
- The pathutils module (voidspace.org.uk)
And some n00b references to run our py scripts:
- Run a python script in Mac OS X terminal (beckism.com)
- Running python scripts on Mac OS X (theatre of noise)