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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,6609c40f81b32989 X-Google-NewGroupId: yes X-Google-Thread: 1094ba,9bdec20bcc7f3687 X-Google-NewGroupId: yes X-Google-Thread: 101deb,e67cdb1dcad3c668 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,gid8d3408f8c3,gidbda4de328f,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news2.google.com!goblin1!goblin3!goblin.stu.neva.ru!exi-transit.telstra.net!news.telstra.net!exi-spool.telstra.net!exi-reader.telstra.net!not-for-mail From: "robin" Newsgroups: comp.lang.ada,comp.lang.fortran,comp.lang.pl1 References: <4bb9c72c$0$6990$9b4e6d93@newsspool4.arcor-online.net> <4bba8bf1$0$56418$c30e37c6@exi-reader.telstra.net> <4bbb2246$8$fuzhry+tra$mr2ice@news.patriot.net> <4bbb5386$0$56422$c30e37c6@exi-reader.telstra.net> <4bbdf5c6$1$fuzhry+tra$mr2ice@news.patriot.net> <4c0a2e36$0$34205$c30e37c6@exi-reader.telstra.net> <4c0b234f$1$fuzhry+tra$mr2ice@news.patriot.net> <4c0cc11c$0$56569$c30e37c6@exi-reader.telstra.net> Subject: Re: Why is Ada considered "too specialized" for scientific use Date: Tue, 8 Jun 2010 00:30:09 +1000 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 Message-ID: <4c0d0278$0$56572$c30e37c6@exi-reader.telstra.net> NNTP-Posting-Host: 58.163.129.68 X-Trace: 1275921017 exi-reader.telstra.net 56572 58.163.129.68:1042 Xref: g2news2.google.com comp.lang.ada:12390 comp.lang.fortran:26445 comp.lang.pl1:1512 Date: 2010-06-08T00:30:09+10:00 List-Id: "Peter Flass" wrote in message news:huiia5$2k1$1@news.eternal-september.org... | If you want to talk *really* old assemblers, look at SOAP. The hardware | had no core, only drum memory, and each H/W instruction contained the | drum address of the next instruction to be executed. A big function of | the assembler was figuring out where to store the instructions on the | drum so that the next instruction was under the R/W head just as the | previous finished executing -- based on the instruction timings. Try | doing that by hand for a large program! That was done by hand for many early machines that relied on mercury delay line (or nickel) memories. Some of those progrems were gigantic. Nevertheless, done in stages (building blocks) it was managable.