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=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11232c,59ec73856b699922 X-Google-Attributes: gid11232c,public X-Google-Thread: 1108a1,59ec73856b699922 X-Google-Attributes: gid1108a1,public X-Google-Thread: fdb77,5f529c91be2ac930 X-Google-Attributes: gidfdb77,public X-Google-Thread: 103376,583275b6950bf4e6 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-04-25 12:38:30 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: softeng3456@netscape.net (soft-eng) Newsgroups: comp.lang.java.advocacy,comp.object,comp.lang.ada,misc.misc Subject: Re: the Ada mandate, and why it collapsed and died (was): 64 bit addressing and OOP Date: 25 Apr 2003 12:38:29 -0700 Organization: http://groups.google.com/ Message-ID: <9fa75d42.0304251138.7b15cc88@posting.google.com> References: <9fa75d42.0302260618.7506cba7@posting.google.com> <3E5CF5C6.84822F57@adaworks.com> <8qkczsAcGcn+Ew83@nildram.co.uk> <3EA04A1E.CAFC1FEF@adaworks.com> <9fa75d42.0304221126.7112b7d5@posting.gOrganization: LJK Software <9fa75d42.030423Organization: LJK Software NNTP-Posting-Host: 32.97.239.26 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1051299510 5625 127.0.0.1 (25 Apr 2003 19:38:30 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 25 Apr 2003 19:38:30 GMT Xref: archiver1.google.com comp.lang.java.advocacy:62678 comp.object:62007 comp.lang.ada:36571 misc.misc:13694 Date: 2003-04-25T19:38:30+00:00 List-Id: Kilgallen@SpamCop.net (Larry Kilgallen) wrote in message news:... > In article <9fa75d42.0304230515.48064263@posting.google.com>, softeng3456@netscape.net (soft-eng) writes: > > Kilgallen@SpamCop.net (Larry Kilgallen) wrote in message news:... > >> In article <9fa75d42.0304221126.7112b7d5@posting.google.com>, softeng3456@netscape.net (soft-eng) writes: > > >> > (C and later C++ style of type-safety turned out to > >> > be good enough for real-world projects.) > >> > >> Like Windows ? > > > You don't like Windows, so you must be using > > what? Unix and X-Windows? Written/extended/in Ada? > > At this instant I am using VMS, which thankfully written mostly before > the current C-mania started. Even when they use C on Alpha and Itanium > now, those who develop VMS tend to use the safer techniques they learned > with Bliss in place of the null-terminated strings and other garbage that > is encouraged by C. You are living in a Jurassic Park world. When VMS was first done, C was not on the lansdcape. But as awareness of C grew, it was adopted very widely within VMS Product Engineering. Many of the products in your VMS product-listing book were done in C! But if you are complaining of null-terminated strings, you couldn't have very well actually seen much Bliss code now, could you? It was hardly what you would call a "safe" language. Very far from it, it didn't even have standard data types. And you could do all kinds of address arithmetic. In fact, you had to be aware of memory address issues all the time in Bliss. In Bliss, you don't write (except when you mean it) A = B; instead you write A = .B; so the compiler knows that you want to store the contents of memory address B into the contents of memory address A, (as opposed to storing the memory address B into the contents of memory address B, which is what it would happily do if you forgot the dot!) The rules got worse as you got into procedure calls... Soon you find yourself fixing bugs involving wrong number of dots. Bliss was certainly not for the faint of heart!