ICES(ID:226/ice001)Integrated Civil Engineering SystemIntegrated Civil Engineering System. Subsystems include COGO, STRUDL, BRIDGE, LEASE, PROJECT, ROADS and TRANSET. Internal languages include ICETRAN and CDL. Someone who wished to make an extension to must write the functionality in ICETRAN and then describes its role in the system using CDL Places Related languages
References: in [AFIPS JCC 27] Proceedings of the 1965 Spring Joint Computer Conference SJCC 1965 view details in [AFIPS JCC 27] Proceedings of the 1965 Spring Joint Computer Conference SJCC 1965 view details in [AFIPS JCC 27] Proceedings of the 1965 Spring Joint Computer Conference SJCC 1965 view details in [AFIPS JCC 27] Proceedings of the 1965 Spring Joint Computer Conference SJCC 1965 view details in [AFIPS JCC 27] Proceedings of the 1965 Spring Joint Computer Conference SJCC 1965 view details in [AFIPS JCC 27] Proceedings of the 1965 Spring Joint Computer Conference SJCC 1965 view details in [AFIPS JCC 27] Proceedings of the 1965 Spring Joint Computer Conference SJCC 1965 view details in Computers & Automation 16(6) June 1967 view details Following the successful systems [COGO and STRESS], work to create a much more generalized system was started at the M.I.T. Civil Engineering Department under the supervision of Professor C. L. Miller. ICES (Integrated Civil Engineering System) was first implemented on the IBM System/360 round 1967. It was released in November 1967 and ordered by over 300 organizations. ICES consists of four major elements: (1) A set of engineering subsystems, each of which is designed to solve problems in a particular area of civil engineering, such as structural analysis and design, soil mechanics, and highway engineering; some specific systems are COCO, STRUDL, ROADS, BRIDGE, TRANSIT, PROJECT, (2) a set of special application area languages which are used to operate these subsystems, (3) facilities whereby people can relatively easily design new languages and embed them in the system and modify existing subsystems, and (4) an executive system which combines all these modules in the correct fashion. It is hoped that one of the most useful characteristics of ICES will be its facility to allow the user access to subroutines from more than one particular branch of engineering. in Computers & Automation 16(6) June 1967 view details in [ACM] CACM 15(07) (July 1972) view details in Computers & Automation 21(6B), 30 Aug 1972 view details in ACM Computing Reviews 15(04) April 1974 view details The exact number of all the programming languages still in use, and those which are no longer used, is unknown. Zemanek calls the abundance of programming languages and their many dialects a "language Babel". When a new programming language is developed, only its name is known at first and it takes a while before publications about it appear. For some languages, the only relevant literature stays inside the individual companies; some are reported on in papers and magazines; and only a few, such as ALGOL, BASIC, COBOL, FORTRAN, and PL/1, become known to a wider public through various text- and handbooks. The situation surrounding the application of these languages in many computer centers is a similar one. There are differing opinions on the concept "programming languages". What is called a programming language by some may be termed a program, a processor, or a generator by others. Since there are no sharp borderlines in the field of programming languages, works were considered here which deal with machine languages, assemblers, autocoders, syntax and compilers, processors and generators, as well as with general higher programming languages. The bibliography contains some 2,700 titles of books, magazines and essays for around 300 programming languages. However, as shown by the "Overview of Existing Programming Languages", there are more than 300 such languages. The "Overview" lists a total of 676 programming languages, but this is certainly incomplete. One author ' has already announced the "next 700 programming languages"; it is to be hoped the many users may be spared such a great variety for reasons of compatibility. The graphic representations (illustrations 1 & 2) show the development and proportion of the most widely-used programming languages, as measured by the number of publications listed here and by the number of computer manufacturers and software firms who have implemented the language in question. The illustrations show FORTRAN to be in the lead at the present time. PL/1 is advancing rapidly, although PL/1 compilers are not yet seen very often outside of IBM. Some experts believe PL/1 will replace even the widely-used languages such as FORTRAN, COBOL, and ALGOL.4) If this does occur, it will surely take some time - as shown by the chronological diagram (illustration 2) . It would be desirable from the user's point of view to reduce this language confusion down to the most advantageous languages. Those languages still maintained should incorporate the special facets and advantages of the otherwise superfluous languages. Obviously such demands are not in the interests of computer production firms, especially when one considers that a FORTRAN program can be executed on nearly all third-generation computers. The titles in this bibliography are organized alphabetically according to programming language, and within a language chronologically and again alphabetically within a given year. Preceding the first programming language in the alphabet, literature is listed on several languages, as are general papers on programming languages and on the theory of formal languages (AAA). As far as possible, the most of titles are based on autopsy. However, the bibliographical description of sone titles will not satisfy bibliography-documentation demands, since they are based on inaccurate information in various sources. Translation titles whose original titles could not be found through bibliographical research were not included. ' In view of the fact that nany libraries do not have the quoted papers, all magazine essays should have been listed with the volume, the year, issue number and the complete number of pages (e.g. pp. 721-783), so that interlibrary loans could take place with fast reader service. Unfortunately, these data were not always found. It is hoped that this bibliography will help the electronic data processing expert, and those who wish to select the appropriate programming language from the many available, to find a way through the language Babel. We wish to offer special thanks to Mr. Klaus G. Saur and the staff of Verlag Dokumentation for their publishing work. Graz / Austria, May, 1973 in ACM Computing Reviews 15(04) April 1974 view details in Proceedings of the 12th Annual ACM IEEE Design Automation Conference 1975 view details in SIGPLAN Notices 13(11) Nov 1978 view details in Journal of the Technical Councils of ASCE, Vol. 105, No. 1, April 1979 view details in Journal of the Technical Councils of ASCE, Vol. 105, No. 1, April 1979 view details in Journal of the Technical Councils of ASCE, Vol. 105, No. 1, April 1979 view details |