Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cis.ohio-state.edu!ucbvax!BRFAPESP.BITNET!UNBCIC
From: UNBCIC@BRFAPESP.BITNET
Newsgroups: comp.lang.modula2
Subject: RE: Why no ** operator in Modula2?
Message-ID: <INFO-M2%91061907542707@UCF1VM.BITNET>
Date: 19 Jun 91 11:51:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Modula2 List <INFO-M2%UCF1VM.BITNET@ucf1vm.cc.ucf.edu>
Organization: The Internet
Lines: 30

=> Date: Tue, 18 Jun 91 18:13:10 GMT
=> From: Larry Smith
=>  <cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!balrog!smith@UCBVAX.BI
TNET>
=> Subject: RE: Why no ** operator in Modula2?

=> In article <1991Jun18.171233.22657@rock.concert.net> mcmahan@cs.unca.edu (Sco
tt
=>         McMahan) writes:
=> >
=> >and I *HATE* CaseSensiTivityInModulesAndProcedures!  I never *use*
=> >uppercase/lowercase names (:-)) but the library modules do.
=>
=> Of course, it *does* enforce a consistancy of spelling which makes for
=> more readable programs, at the expense of typing them properly in the
=> first time.

Well, in other languages I *do* use a lot upper/lowercase names. I use
uppercase names for external (to the module) names, lowercase for functions and
Uppercase just the first letter for procedures. This can't be done in Modula 2.

=> Larry Smith
=> smith@ctron.com

                              (8-DCS)
Daniel C. Sobral                           Errare Humanum Est...
UNBCIC@BRFAPESP.BITNET                     ...Perseverare Autem Diabolicum
UNBCIC@FPSP.FAPESP.ANSP.BR
--------------------------------------------------------------------------
No one, but me, is responsible for the above message.