HDTenEightyP/NetNews huggingface dataset:
From: 841613t@dragon.acadiau.ca (Don Tyzuk)
Subject: Re: Jovial J3B Compiler
Keywords: Jovial
Organization: Acadia University
Date: Wed, 27 Jan 1993 13:38:25 GMT

I too would be interested in other military languages
such as CMS-2, etc.  I doubt if there is enough interest
for a newsgroup, so does anyone mind if we post 
questions here?
-- 
don.tyzuk@acadiau.ca
Newsgroups: comp.lang.ada
Newsgroups: comp.lang.ada



>mfeldman@seas.gwu.edu (Michael Feldman @ George Washington University) writes
>
>    They hired a _really_ big-name consultant (NOT a professor, Mark!)
>    to teach them his OO methodology and take a first crack at a design
>    for them. After collecting a very large fee, he walked away from the
>    project, leaving behind what they say is an unworkable design. 

>bs@alice.att.com (Bjarne Stroustrup) writes:
>I realize you probably can't name names, but it would be nice if you could
>for two reasons. Firstly because charaltans ought to be exposed, secondly
>because someone could misinterpret your statement into something condemning
>lange groups of ``OO-experts'' as windbags who don't deliver. (there are
>no shortage of windbags and self-proclaimed ``experts,'' but no one field
>has a monopoly on them).

In comp.lang.ada, rlk@VisiCom.COM (Bob Kitzberger) writes:
> There is a possibility, of course, that the design was indeed 'good', but
> the engineers on the project weren't qualified enough (read: OO-educated,
> open-minded, etc.) to implement it.

This would still indicate that he walked away to soon.  It would seem that
part of his responsibilities would be to get the engineers sufficiently
up to speed to successfully carry out the design.  On the other hand, he 
may have had the misfortune to walk into a very politicized situation where 
he counldn't win no matter how good his solution was...

David Hawk
Newsgroups: comp.lang.ada
From: campbell@src.honeywell.com (Terry Campbell)
Subject: Re: Ada spec of IEEE 488 GPIB ???
Originator: campbell@analysis.src.honeywell.com
Organization: Honeywell Systems & Research Center, Mpls. MN, USA.
Date: Fri, 22 Jan 1993 20:16:14 GMT


In article <1993Jan21.093454.9206@hellgate.utah.edu> matwood%peruvian.cs.utah.edu@cs.utah.edu (Mark Atwood) writes:

>> I have just about finished, and am now working on my second Ada project
>> where we will be controlling intruments via an IEEE 488 bus.  I was
>> wondering, this cannot be unusual, especially in the ATE world.

>> Does there exist a "standard" binding to the IEEE 488 GPIB bus?

The IEEE P1226 standards group (The Ada-Based Environment for Test) is
curently defining standard interfaces to IEEE-488, 802.3, VXI etc as well as
other Ada interfaces (including Ada interfaces to object-oriented information
defined in EXPRESS).  The point of contact for the bus interface effort is:

  T. Winston Griffin
  Westinhouse Electric Corp.
  111 Schilling Rd.
  MS 7356
  Hunt Valley, MD 21031-1205
  Phone: 410-584-3308
  fax: 410-584-3634


I handle the information interfaces.
From: Oleg Y.Ledov <oleg@bk901.exnet.msk.su>
Newsgroups: comp.lang.ada
Subject: <none>
Date: Wed, 27 Jan 93 10:24:17 -0500
Distribution: world
Organization: InterEVM (dep. 044)
Reply-To: oleg@bk901.exnet.msk.su

PACK
GROUP relcom.commerce.jobs
ART	59
GROUP relcom.sources
ART	2264



Newsgroups: comp.lang.ada
From: yow@sweetpea.jsc.nasa.gov (Bill Yow)
Subject: Re: DIANA (Was Re: ASIS (Was Re: IrisAda))
Keywords: Diana Ada Tool Books
Organization: MDSSC
Date: Thu, 21 Jan 1993 22:58:52 GMT

In article <1993Jan21.205719.14359@inmet.camb.inmet.com>, ryer@inmet.camb.inmet.com (Mike Ryer) writes:
|> 
> Our compiler (for MVS) currently generates DIANA; it would be a very simple
|> matter to add ASIS generation -- just send money.  However, I've been lobbying
|> in-house to scrub down the DIANA to a much simpler internal form, deleting a

Where can one get a good book or information about DIANA?

|> 
|> 
|> Mike Ryer
|> Intermetrics
						Later,
						Bill Yow
						(713) 283-4051
						yow@sweetpea.jsc.nasa.gov
						byow@mcimail.com

My opinions are my own!
From: bs@alice.att.com (Bjarne Stroustrup)
Newsgroups: comp.lang.ada
Subject: Re: Why and how do organizations select th
Date: 25 Jan 93 23:54:46 GMT
Article-I.D.: alice.24708
Organization: AT&T Bell Laboratories, Murray Hill NJ



breland@cobweb.mcc.com (Mark A. Breland @ MCC) writes

 > Careful now, the overtaxed people trying to get their job done usually
 > would give anything to learn something new that will ease their workload.

I know. I know very well. However, many organizations seem significantly
less able to adapt to circumstanses and to make rational decisions than the
individuals out of which such organization are composed.
From: koehnema@enuxha.eas.asu.edu (Harry Koehnemann)
Subject: Re: Why and how do organizations select the OO
Followup-To: comp.lang.ada
Reply-To: koehnema@enuxha.eas.asu.edu (Harry Koehnemann)
Organization: Arizona State University
Date: Mon, 25 Jan 1993 15:59:37 GMT

In article <1993Jan22.203706.29355@seas.gwu.edu> mfeldman@seas.gwu.edu (Michael Feldman) writes:
>
>    They hired a _really_ big-name consultant (NOT a professor, Mark!)
>    to teach them his OO methodology and take a first crack at a design
>    for them. After collecting a very large fee, he walked away from the
>    project, leaving behind what they say is an unworkable design. 
>    Conceivably we (I and another professor friend) will get involved 
>    helping them sort it all out. Might be fun.

Interesting.  I saw the same thing out here.  A friend of mine works at
a company (also nameless) developing a very large real-time system.  There
were many variables in this project  - new processor, new language (Ada),
very large project, drastically reduced cycle time, and new development
method (OO) - ie. lots of risk.  They had hired a consultant to help in
specification and design who basically told them that "if you're going to
use Ada, you have to use OO spec/design"  Hmmm.  Does Ada preclude other
design methods?  You can't get encapsulation/info hiding from other
methodologies?

Of course, everyone followed the consultant.  Not because he was right
(although he may have been), but because I'm sure no one in a decision
making power really knew any better.  As you say it's kindof like
religion - like the congregation following the preacher and assuming
it's his responsibility to get them to heaven.

BTW, last I heard it's behind schedule and way over budget - imagine that.
Too many variables for onw project.
--
Harry Koehnemann			Arizona State University
koehnema@enuxha.eas.asu.edu		Computer Science Department
Newsgroups: comp.lang.ada
From: paster@dna.lth.se (Christian S. Collberg)
Subject: Re: private types and recompilation
Organization: Department of Computer Science, Lund University
Date: Thu, 28 Jan 1993 08:07:43 GMT

In article <9301271722.aa25516@Paris.ics.uci.edu> kanderso@mabillon.ICS.UCI.EDU (Kenneth Anderson) writes:
>In comp.lang.ada you write:
>
>>When Ada 83 was designed, why did the designers choose to put
>>the details of private types in package specifications, rather than
>>in package bodies (which is more in the spirit of information hiding, and
>>better supports independent compilation).
>
>I'm not sure, but I think because the compiler needs to know the size
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>of the types so that it can allocate space for parameters in the
^^^^^^^^^^^^^
>subprograms that are defined in the spec.
>
>


Yes, this is correct. See my thesis "Flexible Encapsulation" (Yes, this is a
blatant plug :-)) for a description of an Ada-like language (Zuse) which --
through the use of novel translation techniques -- allows private parts of
hidden types to be hidden within package bodies.

Christian
-- 
Christian.Collberg@dna.lth.se
Department of Computer Science, Lund University, BOX 118, S-221 00 LUND, Sweden
From: victor@cs.concordia.ca (KRAWCZUK victor)
Newsgroups: comp.lang.ada
Subject: TeleSoft's RiscADA and RPC's
Date: 22 Jan 93 01:23:25 GMT
Organization: Computer Science, Concordia University, Montreal, Quebec


Hi,

	I was wondering if anyone in Ada-land is using TeleSoft's
RiscADA compiler on a Sun Sparc (SunOS 4.1.3) *and* is using
TeleSoft's AdaLan LAN product, specifically AdaLan's RPC facility, in
conjunction with the TeleSoft RiscAda.  I don't know if it's just me
or what, but if I write a very simple multitasking client program and
have both tasks send RPC's (both tasks are in a loop issuing RPC's) to
the same server, the server usually starts hogging the CPU after about
3 minutes of reliable service.  In general, I have found AdaLan to be
quite unpredictable when incorporating Adalan-based RPC's into a
multi-tasking client.  In fact, AdaLan comes with an example program
that demonstrates how to write the client (stub and application) and
server code when the client is multi-tasking.  Even this "canned"
example (slightly modified to send a steady stream of RPC's to the
server) didn't perform up to expectations; the server started hogging
the CPU after about 3 minutes for no apparent reason.

	My main goal is (or was :-) to use the RISCAda compiler with
TeleLan and a TeleSoft Motif GUI builder called "TeleUSE."  Problems
only multiply when TeleUSE is brought into the picture.  The good
folks at TeleSoft assured me that some of their customers use these
three products together with success.  Has anybody had any luck with
the combination of these three products?  Inquiring minds would love
to know!!




-- 
-----------------------------------------------------------------------
|     Victor Krawczuk   (e-mail : victor@cs.concordia.ca )            |
|     Concordia University, Dept. of Computer Science  (H-961)        | 
|     1455 De Maisonneuve Blvd. W., Montreal, Quebec, Canada, H3G 1M8 | 
Newsgroups: comp.lang.ada
From: emery@goldfinger.mitre.org (David Emery)
Subject: Re: private types and recompilation
Organization: The Mitre Corp., Bedford, MA.
Date: Thu, 28 Jan 1993 14:13:29 GMT

In this particular situation, Ada can do what you want.  You can
complete an incomplete type in the package body.  So, given:

	private
	  type LIST;
	  type POSITION is access LIST;
	  type LIST is record
	    A: ATOM;
	    NEXT: POSITION;
	  end record;
	end LIST_ADT;

you can do the following:

	private
	  type LIST;
	  type POSITION is access LIST;
	end LIST_ADT;

	package body LIST_ADT is

	  type LIST is record
	    A: ATOM;
	    NEXT: POSITION;
	  end record;

	...
	end LIST_ADT;

(Thanks to Tucker Taft who argued for this feature in Ada 83.)

				dave
From: finkbine@nmt.edu (Smilin' Ron Finkbine)
Newsgroups: comp.lang.ada
Subject: WANTED::::Call(s) for Papers for ADA specific systems.
Date: 25 Jan 93 13:43:12 GMT
Distribution: na
Organization: New Mexico Tech

Newsgroups: comp.lang.ada
Subject: calls for papers
Distribution: usa
Organization: New Mexico Tech

Are there any recent CALLS for PAPERS that have been distributed by 
netnews? A group of my students is attempting to write a substantial 
project in ADA and might be interested in writing a pub.

Thanks.

ron

Newsgroups: comp.lang.ada
Subject: CALLS FOR PAPERS FOR ADA LANGUAGE SYSTEMS Wanted
Distribution: usa
Organization: New Mexico Tech

Newsgroups: comp.lang.ada
Subject: calls for papers
Distribution: usa
Organization: New Mexico Tech

Are there any recent CALLS for PAPERS that have been distributed by 
netnews? A group of my students is attempting to write a substantial 
project in ADA and might be interested in writing a pub.

Thanks.

ron

Newsgroups: comp.lang.ada
Subject: WANTED:::: Calls for papers for ada specific systems
Distribution: usa
Organization: New Mexico Tech

Newsgroups: comp.lang.ada
Subject: calls for papers
Distribution: usa
Organization: New Mexico Tech

Are there any recent CALLS for PAPERS that have been distributed by 
netnews? A group of my students is attempting to write a substantial 
project in ADA and might be interested in writing a pub.

Thanks.

ron

Newsgroups: comp.lang.ada
Subject: CALLS FOR PAPERS FOR ADA LANGUAGE SYSTEMS Wanted
Distribution: usa
Organization: New Mexico Tech

Newsgroups: comp.lang.ada
Subject: calls for papers
Distribution: usa
Organization: New Mexico Tech

Are there any recent CALLS for PAPERS that have been distributed by 
netnews? A group of my students is attempting to write a substantial 
project in ADA and might be interested in writing a pub.

Thanks.

ron
From: pk115050@wvnvms.wvnet.edu
Newsgroups: comp.lang.ada
Subject: Programs wanted
Date: 25 Jan 93 18:03:34 EST
Organization: West Virginia Network for Educational Telecomputing


I am looking for two pieces of source code, preferably written in C (though
not necessary):

1. Determine the number of nodes and edges that are present in a piece of
ADA code.

2. Determine the following from a piece of ADA code:
   A. The number of unique operators.
   B. The number of unique operands.
   C. The total number of operators.
   D. The total number of operands.

Any help will be appreciated.
From: alex@cs.umd.edu (Alex Blakemore)
Newsgroups: comp.lang.ada
Subject: Re: Isomorphic variant question
Date: 22 Jan 93 01:00:47 GMT
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742

In article <C16FuD.E5L@dale.cts.com> jhb@dale.cts.com (John Bollenbacher) writes:
> So far so good.  My recurring problem arises when I have a code fragment
> which is responsible for building such a piece of mail which does not need
> to distinguish between these isomorphich variants

   procedure POST(KIND : SHAPES) is
   begin
     case KIND is
       when CIRCLE | SQUARE =>
         SEND((KIND   => KIND,
               CENTER => CENTER_OF_OBJECT,
               RADIUS => RADIUS_OF_OBJECT));              




-- 
---------------------------------------------------
Alex Blakemore alex@cs.umd.edu   NeXT mail accepted
From: alex@cs.umd.edu (Alex Blakemore)
Newsgroups: comp.lang.ada
Subject: Re: private types and recompilation
Date: 28 Jan 93 23:44:26 GMT
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742

erickson@taurus.cs.nps.navy.mil (David Erickson) writes:
> When Ada 83 was designed, why did the designers choose to put
> the details of private types in package specifications, rather than
> in package bodies

The private part info is for use by the compiler which must know how much
storage to reserve for objects of a private type based solely on
information in the spec.  Even if the program cannot know the
representation details, the compiler must.

So if you change the private part, you must recompile clients since
that info has changed.  But you are "guaranteed" that the compilation
will succeed since the client cannot reference the implementation
details.

Rational allows you to change the private parts without invalidating
clients if you use their subsystems.

*** But there is a really nice trick that makes this much less of a
problem. You can define a private type as an access type which
designates an incomplete type to defer defining the representation to
the package body.  That gives the compiler enough info to allocate the
proper amount of storage for objects of the private type.  The only
disadvantage to this is the extra time and complexity of using an
access type.

But you are already using access types anyway.  So you can simply move
the following lines to the package body and then any modifications to
the type LIST do not force recompilations of the specification.

>   type LIST is record
>     A: ATOM;
>     NEXT: POSITION;
>   end record;

You must leave these lines in the private part.
  type LIST;
  type POSITION is access LIST;

-- 
---------------------------------------------------
Alex Blakemore alex@cs.umd.edu   NeXT mail accepted
From: Maxim A.Titov <xim@bk901.exnet.msk.su>
Newsgroups: comp.lang.ada
Subject: <none>
Date: Wed, 27 Jan 93 18:32:58 -0500
Distribution: world
Organization: InterEVM (dep. 044)
Reply-To: xim@bk901.exnet.msk.su

GROUP comp.std.mumps
ART   65
GROUP comp.theory
ART   3989
From: robart@agora.rain.com (Joe Bob)
Newsgroups: comp.lang.ada
Subject: Re: Comments on Ada vs. C++ panel
Date: 24 Jan 93 15:37:32 GMT
Article-I.D.: agora.C1D7EL.BIF
Distribution: world
Organization: a gora

>Yes, please do, especially if the panel discussed the economics aspects of
>Ada and C++ market advocacy and policies vis-a-vis what is the best ways
>to inevst(waste) tax dollars to push languages and mandates.
>
>Greg Aharonian
>Greg Aharonian


  This guy is quite biased.
Newsgroups: comp.lang.ada
From: Maxim A.Titov <xim@bk901.exnet.msk.su>
Newsgroups: comp.lang.ada
Subject: <none>
Date: Tue, 26 Jan 93 12:06:41 -0500
Distribution: world
Organization: InterEVM (dep. 044)
Reply-To: xim@bk901.exnet.msk.su

Hi,

how could i get the ACVC 1.11x tests to certificate an Ada compiler
implemented in Russia?

Thanks in advanse.

Maxim A. Titov,
SW analyst
From: kumard@sybil.cs.Buffalo.EDU (Deepak Kumar)
Newsgroups: comp.lang.ada
Subject: Introductory Ada Workbook idea
Date: 27 Jan 93 21:46:51 GMT
Organization: State University of New York at Buffalo/Comp Sci
Originator: kumard@sybil.cs.Buffalo.EDU


This semester I am teaching a 1-credit hands-on Ada class
(newly created course). The objective of the course is to
introduce the Ada environment in a semester with several
hands-on exercises. Prerequisites are CS1 & 2. Since it is
a completely lab oriented course (meets in a master-slave-indep
set up lab once a week for 2 hours) I am thinking of developing
a lab manual for it. We are using Bray & Pokrass as the text
for reading specifics on Ada. The lab manual will evolve 
and will supplement this text (or other similar texts). I was
wondering if there are any such Ada Workbooks out there...(before
someone shoots me down with a pointer to AJPO adabooks...I have
checked that list)....and if not, are there people interested
in something like this...

It would serve the following purposes:

1) Serve as a self-help workbook for the Ada Language (and environement)
2) Will introduce Ada features to the extent that the workbook CAN
   be stand-alone (however, it will have to be complemented by a real
   Ada text).
3) Could be used for the kind of 1-credit courses mentioned above.

Any suggestions?

Deepak.


-- 
I'm not a teacher but I play one at school.
kumard@cs.buffalo.EDU                    Deepak Kumar, Department of Comp. Sc.
kumard%cs.buffalo.edu@ubvm.bitnet        226 Bell Hall, SUNY@Buffalo, NY 14260.
Newsgroups: comp.lang.ada
From: wallsj@CS.ColoState.EDU (jeffrey joel walls)
Subject: Reuse in Ada
Originator: wallsj@CS.ColoState.EDU
Date: Wed, 27 Jan 1993 17:32:32 GMT
Organization: Colorado State University, Computer Science Department



Hi! 

  I am new to this newsgroup, so please forgive me if I am asking 
something that has already been posed.

Pretend that you are a software manager (even if you are, pretend anyway)
and that you have to prove to YOUR manager that software reuse increases
reliability, decreases development time, etc.  What would be the most
important things you would like to show him/her?  What concrete evidence
would you like to have to show?  Not just, "look, it seems to work well"
but, "look, we doubled our ??? "

Thanks!

Jeff
Newsgroups: comp.lang.ada
From: matwood%peruvian.utah.edu@cs.utah.edu (Mark Atwood)
Subject: Re: On-line lrm in GNU Info format
Date: 26 Jan 93 18:33:02 MST
Keywords: info ada lrm 1815a ftp
Organization: University of Utah CS Dept


About a week ago Mark Priestley (priestm@westminster.ac.uk) asked if anyone
had a GNU Info version of the LRM, and I replied that I had one, but not on
the net.  Because several people asked by email for it, I have sent it to
these FTP sites:

wuarchive.wustl.edu /pub/ada-info.Z
ajpo.sei.cmu.edu /tmp/ada-info.Z

Here is the disclaimer i inserted into the file.

This GNU info file was converted by Mark Atwood <matwood@peruvian.cs.utah.edu>
from the machine readable ASCII file stored on the AJPO FTP internet site
(ajpo.sei.cmu.edu).

In the process of converting this file to info format, I may have introduced
errors.  In fact, I know I screwed up the margins, spacing, indentation, and
examples in several places.  Also, neither my employer nor my school are in any
way responsable for this file.  The act of converting it to Info format was a
personal project.  Any copyright that I may have aquired on the reformating,
structuring, or conversion of this file is released into the public domain.

This info file is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE.  No guarantee the accuracy of this file, as compared
with the contents of ANSI/MIL-STD-1815A-1983, "Ada Programming Language", is
offered.  Use this file at your own risk.  If errors or discrepancies are found
in the information or structure of this info file, fix them yourself.

-- 
Mark Atwood                  :: Being a kitten is it's own excuse.
matwood@peruvian.cs.utah.edu :: 
The University has enough problems without being blamed for mine.
From: ke_kimmell@vax.cns.muskingum.edu (DER KOENIG VON KIMMELL)
Newsgroups: comp.lang.ada
Subject: PC Ada Wanted!
Date: 21 Jan 93 18:32:24 -0500
Organization: Muskingum College

HELP!

	I'm looking for an Ada compiler/linker for the PC (hopefully share/free
ware so that I can test it.  Anyone know where I can find one?

Kevin
Newsgroups: comp.lang.ada
From: progers@ajpo.sei.cmu.edu (Pat Rogers)
Subject: Re: private types and recompilation
Organization: Ada Joint Program Office
Date: Thu, 28 Jan 1993 10:58:29 EST

In article <9301271722.aa25516@Paris.ics.uci.edu> kanderso@mabillon.ICS.UCI.EDU (Kenneth Anderson) writes:
>In comp.lang.ada you write:
>
>>When Ada 83 was designed, why did the designers choose to put
>>the details of private types in package specifications, rather than
>>in package bodies (which is more in the spirit of information hiding, and
>>better supports independent compilation).
>
>I'm not sure, but I think because the compiler needs to know the size
>of the types so that it can allocate space for parameters in the
>subprograms that are defined in the spec.
>
>

Well, not really that, so much as that objects of the private type can be 
allocated by users of the package before the package body is ever compiled.  
So the compiler must have sufficient info from the package spec.  Incomplete
type definitions might help you (sometimes called the "Deferred Implementation
Scheme"):

package P is

  type Exported is private;
  ...  operations on the type Exported ...
private
  type Implementation; -- incomplete type def
  type Exported is access Implementation;
end P;

package body P is
  
  type Implementation is ...

end P;

Note however that the language doesn't always force a recompilation, say,
when a comment is added, or a private part is altered. It depends upon
what was changed, but some implementations are "smart" about it.

Pat
Newsgroups: comp.lang.tcl
From: andy@awds.imsd.contel.com (Andy Moskoff)
Subject: Bug in Tcl_CommandComplete ?
Organization: GTE Federal Systems, Westlake Village, CA
Date: Fri, 22 Jan 1993 16:47:43 GMT


Fellow TCLers:

I want to be able to pipe a tcl script into wish and sometime later from
another program (maybe C) send commands to the wish interpreter. For example:

 (cat tcl_script; my_program) | wish. (NOTE: tcl_script set up a Text widget

and my_program issued text commands to standard output.)

This never really worked though. After tracing through a lot of wish code,
we determined that Tcl_CommandComplete was returning 1 even though a partial
command was present. For example, ".w insert end {abc}\n.w" was considered
a complete command, because it was at the end of the command buffer! Note:
we modified StdinProc to do a fread of BUFSIZ, NOT a fgets. So, any time
the piped script stradled the command buffer boundary, the error 
"ambiguous command .w" appeared.

If anybody has a solution to 1) doing what I want to do conceptually or 2)
a fix to the tcl code I would appreciate hearing from you. 


-Andy