Arved, It _is_ a Monty Python sketch. You had punched cards? Luxury! (Pronounced looksh-ary.) We had coding sheets on which we wrote assembler which we then hand-translated into hex codes which were keyed into the machine. Storage was a magnetic stripe on an accounts card. I _graduated_ to punched cards. I always wanted to start a machine by loading the boot sequence through the register switches, but I never actually used one that required it.
I know what you mean about the "natural" association of variable styles with particular languages, although I did get into the habit of camelCasing C variables (because it saved a couple of characters). I still use "i" as my array scanning variable, and make no apologies for it. It is a matter of habit, and habit makes the difficult process of inventing the code a great deal easier. It is something which should be kept in mind by those who sincerely believe that their particular habits have inherent advantages, a view which may indeed have some merit. Ah, the rich diversity of life on earth! (Incidentally, I think the red stars might be disappearing from mozilla. Perhaps the name of God has been spoken in some remote monastery.) Peter Arved Sandstrom wrote: >>-----Original Message----- >>From: Peter B. West [mailto:[EMAIL PROTECTED]] >>Sent: August 20, 2002 9:51 PM >>To: [EMAIL PROTECTED] >>Subject: Re: Style issues. > > [ SNIP ] > >> > The only encoding rule I'd realy like to have: >> > Don't mix underscores with camelCase. >> > Beside looking *really* ugly, it screws up Emacs' dynamic >> > identifier completion, and I'd rather like to do >> > something for FOP than fixing this. >> >>It comes down to "ugliness", doesn't it? "camelCase" is nice. I >>haven't heard it before, and I agree with your admonition. > > > This one is weird. :-) I have associated camelCase with Java, and expect to > see it. I dislike Microsoft naming conventions for VB and C# (I guess you > could call it capitalized camelCase, or Camelcase), without being able to > say why. And for C I cannot abide anything but underscore separators and all > lowercase. I think it is all a mater of habit. > > I may be a person who is ill-qualified to comment on variable names. I like > assembler and machine code, and I never had a problem with the variable > naming conventions for FORTRAN (I, J, K, L, M, N are INTEGER, etc). :-) Of > course, I started with punched cards so I was overjoyed to actually have > variables...sounds like a Monty Python skit (_you_ had _variables_?! I > walked 10 miles both ways to school, uphill, in deep snow, and I had to > hardcode the machine addresses on paper tape..._You_ had paper tape?! I > lived in a culvert, didn't go to school, and flipped switches on vacuum > tubes to set the program). > > Arved > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ "Lord, to whom shall we go?" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
