Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/12/84; site aero.ARPA Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!trwrb!trwrba!aero!warack From: warack@aero.ARPA (Chris Warack) Newsgroups: net.lang Subject: Re: What language do you use for scientific programming? Message-ID: <387@aero.ARPA> Date: Thu, 22-Aug-85 13:57:38 EDT Article-I.D.: aero.387 Posted: Thu Aug 22 13:57:38 1985 Date-Received: Sun, 25-Aug-85 13:26:48 EDT References: <909@oddjob.UUCP> <163@ho95e.UUCP> <367@ttrdc.UUCP> <1612@watdcsu.UUCP> <371@ttrdc.UUCP> Reply-To: warack@aero.UUCP (Chris Warack) Followup-To: net.lang Organization: The Discordian Society Lines: 42 Summary: A different choice ... 4] Theoretically, CLU can handle any precision specified. This is implementation dependent. In any case, if precision is a problem, it's not to difficult to add your own type -- to the precision you need. Other disadvantages: 1] It's VAX implementation is a resource hog. Each CLU program has a copy of the garbage collector and other 'system' functions linked in, thus they are large. Also the CLU compiler and linker suck up a good amount of the CPU. The language is not too difficult to learn especially if someone is fimiliar with type-checked and/or object-oriented languages. The CLU Reference Manual is Lecture Notes in Computer Science #114. Edited by G. Goos and J. Hartmanis. Published by Springer-Verlag. CLU was developed by Barbara Liskov, Toby Bloom, Robert Scheifler, J.C. Schaffert, Lab of Comp Sci, MIT; Russell Atkinson, Xerox Research Center; Alan Snyder, Hewlett Packard; Eliot Moss. [taken from CLU Reference Manual]. Chris -- _______ |/-----\| Chris Warack (213) 648-6617 ||hello|| || || warack@aerospace.ARPA |-------| warack@aero.UUCP |@ ___ | seismo!harvard!talcott!panda!genrad!decvax!ittatc!dcdwest! |_______| sdcsvax!sdcrdcf!trwrb!trwrba!aero!warack || || \ Aerospace Corporation, M1-117, El Segundo, CA 90245 ^^^ ^^^ `---------(|=