as I don't believe anything is unequivocal i will leave that for you all to
   argue over

   For me .. i find mixed case much easier to read and review.  I attempt to
   follow "humpBack" or "camelBack" as my prefered method of typing but not a
   mandate.

   The  system  i  work  on mostly is an OLD d3 system which has the same
   programmers doing it the same way as in the olden days <G> just like i used
   to do.  But bringing up a big program all in upper case with none or little
   spacing (1space max) and no blank lines (always using ed)  is very hard to
   read.

   it is funny on email groups like this .. when someone types all in caps
   people complain that they are yelling <G>
   DSig
   David Tod Sigafoos
   SigsSolutions, Inc.

     -------- Original Message --------
     Subject: RE: [U2] blank lines in code / mixed case
     From: "Brian Leach" <[EMAIL PROTECTED]>
     Date: Mon, March 10, 2008 7:51 am
     To: <[email protected]>
     Kevin
     That's not a full lifecycle test - which is where the casing difference
     really comes in.
     If you want to set a test, have the two groups scan through reams of
     unfamiliar code, make sense of it, identify the bits to change and only
     then
     do the changes. That's where the benefit lies. Though I prefer mixed case,
     I
     am willing to admit that it takes me marginally longer to type in the
     first
     instance. When I come back to read and modify it months later, that's
     where
     the pain was worthwhile.
     Regards
     Brian
     > -----Original Message-----
     > From: [EMAIL PROTECTED]
     > [mailto:[EMAIL PROTECTED] On Behalf Of Kevin King
     > Sent: 10 March 2008 14:12
     > To: [email protected]
     > Subject: Re: [U2] blank lines in code / mixed case
     >
     > Bill, I followed you until this:
     >
     > * Upper case is an anachronism and ! should be treated as such
     > rather than defended. It is unwield y for far too many and,
     > in fact, interferes with efficient typing at every turn.
     > Forcing people to use [Caps Lock] in U2 while all other used
     > applications require [Caps Lock] to be off is a egalitarian
     > ruse for autocracy. :-)
     > *
     > While I understand this is intended to be slightly
     > tongue-in-cheek, saying that it unequivocally "interferes
     > with efficient typing at every turn" is quite possibly much
     > more generalized of a statement than the discussion warrants.
     > While I agree with your assessment about the mix of
     > applications that we are using at any given moment which are
     > using the caps lock in the off position, I find this to be a
     > non-issue and rarely miss more than a couple of characters
     > when switching between apps. For me personally, a couple of
     > caps mistakes a week beats the thousands of times pressing
     > the Shift key where I - notably a tw! o-finger typist - have to
     > get both hands involved.
     >
     > But rather than rely upon conjecture, why not actually test
     > this theory?
     > Let's setup a meeting at Spectrum where we each create a
     > simple sample program using our case of choice, and we'll
     > appoint an "official" timer to see which method produces the
     > fastest results. Game?
     >
     > -K
     > -------
     > u2-users mailing list
     > [email protected]
     > To unsubscribe please visit http://listserver.u2ug.org/
     -------
     u2-users mailing list
     [email protected]
     To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to