Wandering Thoughts archives


An advantage of interpreted languages

One of the useful things about interpreted languages like Python for programming, especially system administration, is that there is no distinction between the source code and the executable program. This means that you never have to play the exciting game of 'where's the source, and for that matter the build instructions, and does it even build with a modern compiler?'

(I once had the interesting assignment of converting a program written for the V6 Unix version of C into something that would compile on a more conventional C compiler. For those that have not encountered it before, the V6 version of C put the operator on the right side of the = for in-place assignment (eg =+ instead of the modern +=), among other differences.)

This means that when I write something in Python, Perl, or so on, everything is right there and complete; I do not have to worry that I may be abandoning co-workers with infrastructure that they have no idea how to reproduce. I find this reassuring, because it means that we have at least a fighting chance if something goes wrong.

(I once heard a story about a pretty much irreplaceable machine, which was that way because the developer of the program running on it had died and no one had any idea where the source code was. That's the kind of thing that can all too easily lead to an appearance in comp.risks.)

programming/InterpretedLanguageAdvantage written at 23:51:52; Add Comment

By day for May 2008: 1 2 3 4 5 6 7 8 9 11 12 13 15 17 18 19 20 21 23 24 25 26 28 29 30 31; before May; after May.

Page tools: See As Normal.
Login: Password:
Atom Syndication: Recent Pages, Recent Comments.

This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.