uucp%ihnp4.UUCP@HARVARD.HARVARD.EDU (UUCP Admin) (10/17/85)
We have been unable to contact machine 'delftcc' since you queued your job.
delftcc!mail sam (Date 10/14)
The job will be deleted in several days if the problem is not corrected.
If you care to kill the job, execute the following command:
uustat -kdelftccN14f8
Sincerely,
ihnp4!uucp
#############################################
##### Data File: ############################
From seismo!harvard!USC-ECLB.ARPA:INFO-ADA Mon Oct 14 16:37:50 1985 remote from ihnp4
Received: by ihnp4.ATT.UUCP id AA02447; 14 Oct 85 16:37:50 CDT (Mon)
Received: from harvard.ARPA (HARVARD.HARVARD.EDU) by seismo.CSS.GOV with SMTP; Mon, 14 Oct 85 04:48:43 EDT
Received: from USC-ECLB.ARPA by harvard.ARPA; Mon, 14 Oct 85 04:49:45 EDT
Return-Path: <allegra!princeton!siemens!gypsy!rosen@ucb-vax.Berkeley.EDU>
Received: from UCB-VAX.ARPA by USC-ECLB.ARPA; Fri 4 Oct 85 15:26:46-PDT
Received: by UCB-VAX (5.28/5.12)
id AA14247; Fri, 4 Oct 85 14:12:00 PDT
From: ihnp4!seismo!ucb-vax.Berkeley.EDU!harvard!allegra!princeton!siemens!gypsy!rosen
Date: 3 Oct 85 17:29:00 GMT
Subject: Please Test This
Message-Id: <38000023@gypsy.UUCP>
Precedence: junk
Sender: ihnp4!seismo!harvard!ucb-vax.Berkeley.EDU:usenet
Errors-To: ihnp4!seismo!harvard!ucb-vax.Berkeley.EDU:usenet
To: UCB-VAX.Berkeley.EDU!info-ada
Resent-Date: Sun 13 Oct 85 15:47:07-PDT
Resent-To: USC-ECLB.ARPA!info-ada
Resent-Message-Id: <12150885421.35.INFO-ADA@USC-ECLB.ARPA>
Can someone run this small program through their Ada compiler and let me
know what it has to say. I've already run it though the Verdix compiler and
the Ada/ED compiler both for Unix 4.2 on a Vax. If you have a different
compiler, then I'd like to know what it has to say.
The error concerns the importation of the equality operator for objects that
are of an access type and are declared in a different package. The Verdix
compiler says that if I do not issue a "use" clause for the imported package
(the one with the access type definitions), then I must qualify the "="
operator since it is not directly visible. The Ada/ED compiler doesn't
require this. I believe the Verdix compiler is right since it is taking the
LRM literally, but I would like to know what other compilers say.
Here's the program:
----------------------------------------------------------------------------
package IMPORT_ACCESS_TYPE is
type POINTER is access INTEGER;
--
-- Declaration of a public access type.
--
end IMPORT_ACCESS_TYPE;
----------------------------------------------------------------------------
with IMPORT_ACCESS_TYPE; -- Notice the the lack of a 'use' clause
-- which is very important in this example
procedure MAIN is
X,Y: IMPORT_ACCESS_TYPE.POINTER;
begin
--
-- The compiler will/should complain about the test for equality in the
-- following statement since the "=" operator is not directly visible.
--
if (X = null) then
Y := X;
end if;
--
-- The compiler should not complain about the test for equality in the
-- following statement. This form is required if there is no "use" clause
-- for the package which declares the access types.
--
if (IMPORT_ACCESS_TYPE."=" (X, null)) then
Y := X;
end if;
end MAIN;
----------------------------------------------------------------------------
------------
Steve Rosen
Siemens Research and Technology Laboratories
Princeton, NJ
USENET: {ihnp4|princeton|adrvax}!siemens!gypsy!rosen
ARPA: siemens!gypsy!rosen@TOPAZuucp%ihnp4.UUCP@HARVARD.HARVARD.EDU (UUCP Admin) (10/17/85)
We have been unable to contact machine 'delftcc' since you queued your job.
delftcc!mail sam (Date 10/14)
The job will be deleted in several days if the problem is not corrected.
If you care to kill the job, execute the following command:
uustat -kdelftccN14f9
Sincerely,
ihnp4!uucp
#############################################
##### Data File: ############################
From seismo!harvard!USC-ECLB.ARPA:INFO-ADA Mon Oct 14 16:56:19 1985 remote from ihnp4
Received: by ihnp4.ATT.UUCP id AA03373; 14 Oct 85 16:56:19 CDT (Mon)
Received: from harvard.ARPA (HARVARD.HARVARD.EDU) by seismo.CSS.GOV with SMTP; Mon, 14 Oct 85 05:46:56 EDT
Received: from USC-ECLB.ARPA by harvard.ARPA; Mon, 14 Oct 85 05:48:14 EDT
Return-Path: <@rand-unix:hermix!fischer@rand-unix>
Received: from RAND-UNIX.ARPA by USC-ECLB.ARPA; Sat 5 Oct 85 04:07:02-PDT
Return-Path: <hermix!fischer>
Received: from hermix.UUCP by rand-unix.ARPA; Sat, 5 Oct 85 04:09:23 pdt
Message-Id: <8510051109.AA21325@rand-unix.ARPA>
From: Herm Fischer <ihnp4!seismo!rand-unix.ARPA!harvard!hermix!fischer>
Reply-To: HFischer@USC-ECLB
To: eclb.ARPA!info-ada
Subject: Draft for Comments, Mil Hndbook, Ada Programming Guidelines
Cc: ECLB.ARPA!HFISCHER
Date: Fri Oct 4 23:26:17 1985
Resent-Date: Sun 13 Oct 85 15:47:25-PDT
Resent-To: USC-ECLB.ARPA!info-ada
Resent-Message-Id: <12150885474.35.INFO-ADA@USC-ECLB.ARPA>
A new DoD document, released for comment on a short schedule, covers use
of Ada -- with DoD-STD-2167 (SDS), and provides Ada programming guidelines
(really in the form of "coding standards"). I presume it will be in the
interests of many readers to participate in a review of this.
The Electronic Industries Association (EIA G-34) has released for comments
the 6-Sep-85 Draft of DoD-HDBK-287 (Superseding DoD-HDBK-281), titled
"Defense System Software Development Handbook". Comments are due in
no later than 15 Oct 85, in order to meet a deadline of 18 Oct 85 imposed
by the JLC/CSM (the deadline is under protest and may be extended).
This handbook "provides guidance to Development Agency and Software
Support Agency personnel charged with planning, establishing, and
managing Software Development Programs for any phase of the System
Development cycle. It is designed to supplement the DoD Joint
Regulation on Management of Computer Resources in Defense Systems and
to provide specific guidelines for applying DoD-STD-2167 (SDS) to
software acquisition, development or support projects. Specific
topics covered are as follows:
- Acquisition, development, and support of systems and software
- the four steps of the tailoring approach
- procedural guidelines for contract commencement and administration
- topics of concern for the software acquisition manager (incl. Ada)
- defense system software development
- how to tailor DIDs to a software acquisition
- Examples of DID selection
- ADA PROGRAMMING GUIDELINES <==== NEEDS YOUR CAREFUL REVIEW!!!
If you'd like to know who in your company might have received this
document, or if you would like a copy of the Ada-relevant sections
to review, time is short to get started. (The Ada section is reasonably
compact, and shouldn't take too long to study.)
You can contact me or the CODSIA coordinator as you wish:
Herm Fischer Arpanet: HFischer@ECLB
UUCP: {randvax, cepu!ucla-an}!hermix!fischer
AT&T: (818)995-7671
toll-free via SBS in most cities: dial 950-1088, wait
for 2nd tone, then tone-dial FISHER (347437)
Snail-mail: Mark V, 16400 Ventura Bl, Encino CA 91436
CODSIA Coordinator: Ole Golubjatnikov (315)456-4744
uucp%ihnp4.UUCP@HARVARD.HARVARD.EDU (UUCP Admin) (10/17/85)
We have been unable to contact machine 'delftcc' since you queued your job. delftcc!mail sam (Date 10/14) The job will be deleted in several days if the problem is not corrected. If you care to kill the job, execute the following command: uustat -kdelftccN14fa Sincerely, ihnp4!uucp ############################################# ##### Data File: ############################ From seismo!harvard!USC-ECLB.ARPA:INFO-ADA Mon Oct 14 16:57:50 1985 remote from ihnp4 Received: by ihnp4.ATT.UUCP id AA03469; 14 Oct 85 16:57:50 CDT (Mon) Received: from harvard.ARPA (HARVARD.HARVARD.EDU) by seismo.CSS.GOV with SMTP; Mon, 14 Oct 85 06:42:45 EDT Received: from USC-ECLB.ARPA by harvard.ARPA; Mon, 14 Oct 85 06:43:35 EDT Return-Path: <uwvax!pokey!dan@ucb-vax.Berkeley.EDU> Received: from UCB-VAX.ARPA by USC-ECLB.ARPA; Tue 8 Oct 85 01:38:20-PDT Received: by UCB-VAX (5.28/5.12) id AA20989; Tue, 8 Oct 85 00:30:39 PDT From: ihnp4!seismo!ucb-vax.Berkeley.EDU!harvard!uwvax!pokey!dan Date: 7 Oct 85 15:05:08 GMT Organization: U of Wisconsin CS Dept Subject: bug-free programs Message-Id: <260@pokey.UUCP> Precedence: junk Sender: ihnp4!seismo!harvard!ucb-vax.Berkeley.EDU:usenet Errors-To: ihnp4!seismo!harvard!ucb-vax.Berkeley.EDU:usenet To: UCB-VAX.Berkeley.EDU!info-ada Resent-Date: Sun 13 Oct 85 15:47:28-PDT Resent-To: USC-ECLB.ARPA!info-ada Resent-Message-Id: <12150885483.35.INFO-ADA@USC-ECLB.ARPA> For anyone who is used to reading the horror stories in Software Engineering News, the idea of bug-free large programs is a bit hard to grapple with. Large programs are so complex, and have so many states, that exhaustive testing would take hundreds or thousands of years. Even in the unlikely event that you do have a mechanical proof system, that system is vulnerable to the input and output predicates for a given code fragment. The important thing about Ada exceptions is that they include the ability to trap constraint and range violations like the one which would supposedly appear on the pilot's display. Proper coding standards will enforce the creation of programs in which these (unlikely but possible) errors would be trapped and dealt with in an orderly way. Sure beats the heck out a C program that goes off the end of an array and fires your ejection seat . . . -- Dan
uucp%ihnp4.UUCP@HARVARD.HARVARD.EDU (UUCP Admin) (10/17/85)
We have been unable to contact machine 'delftcc' since you queued your job. delftcc!mail sam (Date 10/14) The job will be deleted in several days if the problem is not corrected. If you care to kill the job, execute the following command: uustat -kdelftccN14fb Sincerely, ihnp4!uucp ############################################# ##### Data File: ############################ From seismo!harvard!USC-ECLB.ARPA:INFO-ADA Mon Oct 14 17:01:17 1985 remote from ihnp4 Received: by ihnp4.ATT.UUCP id AA03681; 14 Oct 85 17:01:17 CDT (Mon) Received: from harvard.ARPA (HARVARD.HARVARD.EDU) by seismo.CSS.GOV with SMTP; Mon, 14 Oct 85 07:39:20 EDT Message-Id: <8510141139.AA08503@seismo.CSS.GOV> Received: from USC-ECLB.ARPA by harvard.ARPA; Mon, 14 Oct 85 07:40:38 EDT Return-Path: <@MIT-MC:godwin@UCI-ICSE> Received: from MIT-MC.ARPA by USC-ECLB.ARPA; Sat 12 Oct 85 17:40:20-PDT Received: from UCI-ICSE.ARPA by MIT-MC.ARPA 12 Oct 85 16:45:15 EDT Received: from localhost by UCI-ICSE.ARPA id a017160; 12 Oct 85 13:42 PDT To: brl-voc.ARPA!info-pascal, mit-mc.ARPA!info-ada, brl-vgr.ARPA!info-micro Subject: Languages in use Date: 12 Oct 85 13:42:08 PDT (Sat) From: Dave Godwin <ihnp4!seismo!harvard!UCI-ICSE.ARPA:godwin> Resent-Date: Sun 13 Oct 85 15:47:30-PDT Resent-To: USC-ECLB.ARPA!info-ada Resent-Message-Id: <12150885489.35.INFO-ADA@USC-ECLB.ARPA> Hi folks. I have a small favor to ask from a lot of people here. This message is addressed to all you folks out there teaching classes at universities, or doing new research and development stuff in large scale industry. From the academic areas, I need to know what languages you are teaching your freshmen. Are these langauges used in later courses they take ? From the R&D people, both in industry and academia, what languages are you using most frequently ? Why do you use that particular language ( please keep this answer down to a few chapters :-> ) ? Please send your replies to me direct; there is no need to clutter any net space up with this. If I get enough replies, I will post a summary to the net. Thank you all much, Dave Godwin University of California, Irvine godwin@icse.uci.edu <---- new arpa mailer address godwin@uci-icse.arpa <---- old arpa mailer address
uucp%ihnp4.UUCP@HARVARD.HARVARD.EDU (UUCP Admin) (10/17/85)
We have been unable to contact machine 'delftcc' since you queued your job.
delftcc!mail sam (Date 10/14)
The job will be deleted in several days if the problem is not corrected.
If you care to kill the job, execute the following command:
uustat -kdelftccN14fc
Sincerely,
ihnp4!uucp
#############################################
##### Data File: ############################
From seismo!harvard!USC-ECLB.ARPA:INFO-ADA Mon Oct 14 17:01:41 1985 remote from ihnp4
Received: by ihnp4.ATT.UUCP id AA03712; 14 Oct 85 17:01:41 CDT (Mon)
Received: from harvard.ARPA (HARVARD.HARVARD.EDU) by seismo.CSS.GOV with SMTP; Mon, 14 Oct 85 08:48:24 EDT
Received: from USC-ECLB.ARPA by harvard.ARPA; Mon, 14 Oct 85 08:49:38 EDT
Return-Path: <@MIT-MC:jcm@ORNL-MSR>
Received: from MIT-MC.ARPA by USC-ECLB.ARPA; Sun 13 Oct 85 08:39:18-PDT
Received: from ORNL-MSR.ARPA by MIT-MC.ARPA 13 Oct 85 10:50:14 EDT
Received: by ORNL-MSR.ARPA (4.12/4.9)
id AA17858; Sun, 13 Oct 85 10:50:06 edt
Date: Sun, 13 Oct 85 10:50:06 edt
From: ihnp4!seismo!harvard!ORNL-MSR.ARPA:jcm (James A. Mullens)
Message-Id: <8510131450.AA17858@ORNL-MSR.ARPA>
To: UCI-ICSE.ARPA!godwin, MIT-MC.ARPA!info-ada, BRL-VGR.ARPA!info-micro,
BRL-VOC.ARPA!info-pascal
Subject: Re: Languages in use
Resent-Date: Sun 13 Oct 85 15:47:31-PDT
Resent-To: USC-ECLB.ARPA!info-ada
Resent-Message-Id: <12150885494.35.INFO-ADA@USC-ECLB.ARPA>
From Jim Mullens / Oak Ridge National Lab
Oak Ridge is a large government research lab. I, and most people here, are
part-time programmers and full time engineering/scientific researchers so we
tend to stick with the common coin of the scientific programming world,
FORTRAN. Most people have grown up with IBM mainframes and DEC minis, where
FORTRAN is well-supported. On DEC minis at least, the language is highly
integrated into the operating system, so you can even do most systems programming
from FORTRAN... I think the major reason we do not change languages is that
we have some very good reasearchers who only know FORTRAN, and could not
participate fully in a computer project using another language -- plus, we
simply cannot afford to learn a new language just because it is claimed to be
the optimum for this year's computer project.
Lately I think we are seeing the growth of easy-to-use speciality packages
which are almost languages, instead the learning of new languages. CSMP is
an early version of this, spreadsheets another, advanced data base packages,
statistical packages like SAS, and so on. This is, to me, an interesting way
to go... In AI, expert systems are characterized by the incorporation of
"domain-specific knowledge" instead of general rules of reasoning. These
language-like application packages seem like languages with domain knowledge
embedded in them.
I would like to hear the results of your survey. Thanks.