From: CRDGW2::CRDGW2::MRGATE::"SMTP::WSMR-SIMTEL20.ARMY.MIL::INFO-ADA-REQUEST" Date: 3-JUN-1991 20:52:51 Description: INFO-ADA Digest V91 #146 From: INFO-ADA-REQUEST@WSMR-SIMTEL20.ARMY.MIL@SMTP@CRDGW2 To: SWENG@arisia@MRGATE Received: by crdgw1.ge.com (5.57/GE 1.99) id AA12059; Mon, 3 Jun 91 17:15:47 EDT Date: Mon, 3 Jun 91 12:15:10 MDT From: INFO-ADA-REQUEST@AJPO.SEI.CMU.EDU Reply-To: INFO-ADA-REQUEST@AJPO.SEI.CMU.EDU Subject: INFO-ADA Digest V91 #146 To: INFO-ADA@AJPO.SEI.CMU.EDU Message-Id: <910603121510.V91N146@WSMR-SIMTEL20.ARMY.MIL> INFO-ADA Digest Mon, 3 Jun 91 Volume 91 : Issue 146 Today's Topics: aflex/ayacc available via FTP Re: Ada books for undergraduate computer science Re: OOP and large systems (was: Ada vs C++, ...) Re: Types defining h/w r/o or w/o registers ---------------------------------------------------------------------- Date: 3 Jun 91 17:32:35 GMT From: ucivax!self@ucbvax.Berkeley.EDU (John Self) Subject: aflex/ayacc available via FTP Message-ID: <284A7D33.28608@ics.uci.edu> The long awaited public release of the Arcadia project tools aflex and ayacc is now ready. I'm enclosing the README file from the distribution below. At the end of this file you will find instructions on how to retrieve the source code via FTP. If you do retrieve this distribution please take a minute to return the registration form so we can put you on a mailing list to receive e-mail announcements of bug fixes and additional software we are releasing. Thanks, John Self self@ics.uci.edu sdcsvax!ucivax!self JTSELF@UCI.BITNET ------------------------------- cut here ------------------------------- Copyright (c) 1990 Regents of the University of California. All rights reserved. This software was developed by the Arcadia project at the University of California, Irvine. Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Irvine. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. ********************************************************************** This is the IRUS (Irvine Research Unit in Software) aflex/ayacc public distribution. Aflex and ayacc are similar to the Unix tools lex and yacc, but they are written in Ada and generate Ada output. They were developed by the Arcadia Project at the University of California, Irvine. Aflex is based on the tool 'flex' written by Vern Paxson. These tools are copyrighted, but are freely redistributable. There is no warranty of any kind (see the copyright notice above.) However we do ask that you report any problems you encounter as we use these tools ourselves and we want to fix any bugs that are found. You may give this software to others, but we prefer that those who can get it directly from us to insure that all users are running the latest version. We also ask that you send electronic mail to the address irus-software-request@ics.uci.edu giving your name, your organization, a paper mail address, and your e-mail address (either an Internet address or a UUCP path relative to a well-known site such as uunet.) A form is provided below for your convenience. We will use this information to set up a mailing list to announce new versions of aflex and ayacc, as well as new software that is expected to be made available. The distribution is currently available on the machine liege.ics.uci.edu in ~ftp/pub/irus/aflex-ayacc_1.1.tar.Z. Full instructions for retrieving and unpacking are enclosed below. If you have trouble retrieving or unpacking the distribution send mail to irus-software-request@ics.uci.edu (or via UUCP to uunet!sdcsvax!ucivax!irus-software-request) If you have trouble with the tools information on how to report bugs is present within their directories. ------------------------------- cut here ------------------------------- IRUS software user registration form 1. Your Name: 2. Your Organization: 3. Mailing Address: 4. E-mail address for contact person: ------------------------------- cut here ------------------------------- How to obtain aflex and ayacc via anonymous FTP 1. FTP to the machine liege.ics.uci.edu (internet address 128.195.1.5) 2. When asked for a username use 'anonymous' 3. When asked for a password use your username on your local machine. 4. Change directory (cd) into the pub/irus directory. 5. Set a file transfer mode that will allow you to transfer binary files. One way to do this that usually works is to issue the command 'type tenex' 6. Type the command 'get aflex-ayacc_1.1.tar.Z' 7. Quit FTP. 8. You now have a compressed tar file containing the source for aflex. 9. You need to uncompress the file by typing 'uncompress aflex-ayacc_1.1.tar.Z' 10. Now untar the file to create the source and documentation tree by typing 'tar xvf aflex-ayacc_1.1.tar' at the Unix prompt. 11. Read the README files in the aflex/README and ayacc/src/READ_ME to find out how to compile the tools. If you are using the Verdix Ada Developemnt System Version 6 be sure to read the VADS6.README files in the aflex and ayacc directories before building them. -- Thanks, John ------------------------------ Date: 3 Jun 91 10:47:18 GMT From: fernwood!uupsi!sunic!fuug!funic!news.funet.fi!tukki.jyu.fi!sakkinen@apple.com (Markku Sakkinen) Subject: Re: Ada books for undergraduate computer science Message-ID: <1991Jun3.104718.3124@jyu.fi> In article <3246@sparko.gwu.edu> mfeldman@seas.gwu.edu () writes: > ... >Dale/Weems) are writing or co-authoring Ada adaptations. Doug Cooper >has just done a Modula-2 version of "Oh! Pascal," called, would you >believe, "Oh, My! Modula-2." I don't know if we'll see an Ada version of this. Hm, check whether he has already registered the name "Ah, Madam! Ada" :-) > ... Markku Sakkinen Department of Computer Science and Information Systems University of Jyvaskyla (a's with umlauts) PL 35 SF-40351 Jyvaskyla (umlauts again) Finland SAKKINEN@FINJYU.bitnet (alternative network address) ------------------------------ Date: 4 Jun 91 01:16:55 GMT From: mintaka!think.com!spool.mu.edu!munnari.oz.au!murtoa.cs.mu.oz.au!csv.viccol.edu.au!dougcc@bloom-beacon.mit.edu (Douglas Miller) Subject: Re: OOP and large systems (was: Ada vs C++, ...) Message-ID: <1991Jun3.201656.6692@csv.viccol.edu.au> In article <085657.19195@timbuk.cray.com>, gbt@sequoia.cray.com (Greg Titus) writes: > In article <1991May30.004144.24252@netcom.COM> jls@netcom.COM (Jim > Showalter) writes: >> [Somebody else writes:] >>>I won't argue the point that Ada is far superior when it comes to large system >>>development. This is a fact, plain and simple, and C++ cannot hold a candle >>>to Ada's abilities to decompose a problem into managable pieces and insure >>>the consistency between them. However, Ada is not all things to all programming >>>tasks, and one of the things it isn't is an object oriented programming >>>language. >> >>From the above paragraph, we have these two statements: >> >>1) Ada is a superior language for engineering large complex systems. >>2) Ada is not particularly supportive of OOP. >> >>These two statements lead to the following conclusion: >> >>3) OOP is largely irrelevant when it comes to engineering large complex systems. >> >>Now, far be it from me to actually MAKE this claim [;-)], I'm merely >>pointing out that it is the inevitable subtext of the above paragraph. > > I don't see that, Jim. I'd replace your 3) with "Ada is not the best > language when it comes to engineering large complex OO systems." What is a "large complex OO system", as opposed to a large complex system developed useing OO? You appear to be assuming what Jim has asked to be shown. > My own feeling is that we simply don't *have* a true object-oriented > language that is also appropriate for large systems. Might be a neat > thing to work on, though ... You have definitely missed the point. Jim want to know how useful "true" OO features (inheritance et al) are to large-scale development as compared with those boring old OO features (static data abstraction et al). So do I. Does anyone have any evidence one way or the other? -- Douglas Miller Phone: +61 3 805 3262 Fax: +61 3 808 9497 Post: Computer Services, Victoria College, BURWOOD 3125, AUSTRALIA Location: Building A, 221 Burwood Highway, Burwood, Victoria, Australia ------------------------------ Date: 3 Jun 91 07:57:41 GMT From: weyrich!orville@uunet.uu.net (Orville R. Weyrich) Subject: Re: Types defining h/w r/o or w/o registers Message-ID: <1991Jun3.075741.1945@weyrich.UUCP> In article <1991Jun2.095459.1@east.pima.edu> rharwood@east.pima.edu writes: >In article <3949@titan.tsd.arlut.utexas.edu>, >gardner@titan.tsd.arlut.utexas.edu (Don Gardner) writes: > >> Is there some way to define a type such that all variables of that >> type can be only read or only written? For instance, I have a type that >> defines the status register of some peripheral which can only be >> read. It would be best if the compiler could flag any assignments >> to variables of such a type as errors. >> >> Is there some other means for commonly handling this problem? The >> compiler being used is VADSWorks, if an implementation-defined solution >> is required. > >Well, it's been 2.5 years since I did this, but IMHO "the right way" to do what >you are trying is to encapsulate the READ operation in a FUNCTION and the WRITE >operation in a one-parameter procedure. Several replies to your message I have one concern about this approach: What happens if the compiler optimizer is SO CLEVER that it notices a write to a location that is never referenced, and optimizes away the write? Does anyone know of a compiler that is this clever? In any event, you had best check the machine language generated each time your compiler is upgraded ... Is there any issue pending before the 9x committee to address the issue of declaring certain memory locations as VOLATILE? -------------------------------------- ****************************** Orville R. Weyrich, Jr., Ph.D. Certified Systems Professional Internet: orville%weyrich@uunet.uu.net Weyrich Computer Consulting Voice: (602) 391-0821 POB 5782, Scottsdale, AZ 85261 Fax: (602) 391-0023 (Yes! I'm available) -------------------------------------- ****************************** ------------------------------ End of INFO-ADA Digest V91 Issue #146 *************************************