LooKing at ProGrams and LooKing at an EmAil are two DifFerent ThiNgs. WhEn I
ReAd a LetTer FrOm SomeOne I ExPect it to be in MiXed CaSe BecAuse ThAt is
WhAt I was TauGht to do.
Not many people will be using mnemonics and made up words in a letter
either. With programs I expect to see mnemonics and made up words for
variables and since I was taught to use uppercase in programming (shoot they
didn't even have a lower case in the earlier systems) that is what I expect
to see. Mixed case programming looks like a foreign language to me. You may
as well put the letters in backwards. If I see mixed case in a program I
expect it to be a comment line, not code. Now you can call me primitive if
you want but I'll bet you that 90% of all code that is out there, in this
environment, is not mixed case and is readable by me. If someone said to
stop using upper case I would probably switch to all lower case. Reading
mixed case words almost sends me into an epileptic fit. By the way the
spellchecker barfed on the first paragraph of this email.
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <u2-users@listserver.u2ug.org>
Sent: Wednesday, March 14, 2007 3:16 AM
Subject: Spam:Re: [U2] Error in report generation.
Mark
I WAS WAITING FOR YOU TO RESPOND THERE!
SO YOU PREFER CODE THAT SHOUTS BACK AT YOU?
THERE ARE GOOD REASONS WHY THE REST OF THE WORLD HAS SWITCHED TO MIXED
CASE CODING - IT IS GENUINELY QUICKER TO SCAN AND READ. FORTUNATELY I'VE
ONLY BEEN WITH MULTIVALUE FOR TWENTY YEARS SO I WAS ABLE TO DITCH UPPER
CASE AS SOON AS UNIVERSE CAME ALONG. PROVING WHAT YOU SAID IN YOUR EMAIL
ABOUT NOT FOLLOWING 'BUT THAT'S HOW I WAS TAUGHT' :)
I'm not being frivolous (or personal - you obviously *read* these emails!)
here.
Whether we like it or not, perception is important. Whilst we are trying
to position/encourage UniVerse, UniData et al as modern and up to date
systems with a strong history, it makes sense to write in ways that match
the expectations of new developers who are brought up with current
conventions: that includes mixed case coding, legible styles and formats
that can be genuinely expressive - like not using field numbers for
example (a REAL bugbear of mine). Not using ED helps, of course.
Before anyone jumps in - no I don't advocate rewriting existing code in
this way. But quickly scan the following two sections and see which one
reads faster. If you've been brought up around Delphi, Java, C#, VB, ASP
or any of the 'modern' languages I'm willing to bet the first will be
considerably quicker.
Loop
ReadNext Id From MYLIST Else
Fin = @True
End
Until Fin Do
ReadU CustomerRec From CUSTOMERS, Id Then
GoSub ProcessRecord
End
Repeat
LOOP
READNEXT ID FROM MYLIST ELSE
FIN = @TRUE
END
UNTIL FIN DO
READU CUSTOMERREC FROM CUSTOMERS, ID THEN
GOSUB PROCESS.RECORD
END
REPEAT
Brian
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
