From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a50a3c40267219cc X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-10-15 14:42:08 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!psinet-eu-nl!psiuk-p4!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: Why not combine Ada and C++? Date: Mon, 15 Oct 2001 17:27:54 -0400 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: <9qfkcr$8kc$1@nh.pace.co.uk> References: <3105e154.0110150021.32ff5426@posting.google.com> <9qeg5r$266$1@trog.dera.gov.uk> <9qesee$s5b$1@nh.pace.co.uk> <3BCB0C10.636D110E@icn.siemens.de> <9qf394$1rt$1@nh.pace.co.uk> <9qfg4v02t20@drn.newsguy.com> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1003181275 8844 136.170.200.133 (15 Oct 2001 21:27:55 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 15 Oct 2001 21:27:55 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.google.com comp.lang.ada:14605 Date: 2001-10-15T21:27:55+00:00 List-Id: Similar cases have been given here before and been vigorously debated. I personally would not program this way because of the easy misreading or mistyping of "Car" vs "car" - and that's (one of the reasons) why Ada doesn't do it that way. It is also just a naming convention that might not get adhered to and might cause problems switching from one app to another or one programmer's code to another. (Yes, I favor adherence to coding conventions but they are difficult to enforce.) In a sense, it is fundamentally no different than "Car" vs "Car_Type" or some similar convention, so generally speaking, you can get the same effect with a different style. (You'll find about as much religious fervor over the pro _Type vs anti _Type adherents! :-) As I said elsewhere, people are going to have preferences and there will be good reasons on either side supporting what people prefer. Ada had to decide to be either case sensitive or insensitive and either way it was going to displease some segment of the population. It opted for insensitivity because it was generally viewed to be the safer alternative - for a language heavily concerned with avoiding errors. You give something up and you gain something. At least it wasn't done for no reason at all and I think any reasonable programmer can learn to work with it (and might discover that it *does* avoid some collection of errors.) MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com Web: http://www.mcondic.com/ "Robert*@" wrote in message news:9qfg4v02t20@drn.newsguy.com... > > in some cases, case sensitivity can be very good. > > for example, in Java, the convention is to use lower case first letter for > a name of a method. and Upper case first letter for a Class and interface > name, lower case all letters for a package name. > > This is very usefull, becuase if you'r reading code, and you see an Upper case > first letter on an identifier, then you know without having to look aroud, that > the name represent a Class name. and the same for method names. > > This means you can write > > Car car= new Car("buick"); > > and it is clear as a bird which is the type and which is the variable. > (In Ada, you have to add "_Type" to the type to try to distinguish things). > > This is a convention, not enforced by the language, but it is so strong, that > any java programmer cought not doing it, will be immeadiatly taken out and > shot in clear day light without a question being asked :) > > Myself, I prefer case sensitive. But it is not a very important feature, there > are more important things to look at first. But if I am designing a new > lang, i'd make case sensitive. >