> I got my first real programming job in a shop that was all K&R C with > tons of legacy code written by people who had taught themselves the > language.... Believe me, I hacked like a machete never could, and > statements like > > band = intmax(strtok(NULL,seps)[0]-64,0); > > were considered *quite* tame. :)
I know barely enough C to hang myself with but the above does make sense, in a real twisted way :D I don't know really, usually the projects I write for myself, or the code I write that gets sold to multiple people I try to make as "obfuscated" as possible in a way - at least the chances are better I'll be the one who gets called on to maintain it ;) Gotta promote job longevity somehow. Code that's written for others, or when I get hired as a programmer is usually well commented, neatly spaced and if I feel particularly good that day I'll run it thru prettyperl just so it looks good and has all the right indents and stuff. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
