> -----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]
