Path: utzoo!utgpu!watmath!clyde!att!rutgers!mailrus!ukma!cwjcc!gatech!hubcap!billwolf From: billwolf@hubcap.clemson.edu (William Thomas Wolfe,2847,) Newsgroups: comp.lang.ada Subject: Re: Collective response to := messages Message-ID: <3720@hubcap.UUCP> Date: 2 Dec 88 19:31:28 GMT References: <10918@ulysses.homer.nj.att.com> Sender: news@hubcap.UUCP Reply-To: billwolf@hubcap.clemson.edu Lines: 18 From article <10918@ulysses.homer.nj.att.com>, by dsr@hector.UUCP (David S. Rosenblum): > > The ADT-handling package may feel like leaving a component undefined, but > Ada doesn't feel like leaving variables undefined after an assignment. > That's why such a user-defined assignment violates Ada's strong typing. Really? Consider the following: procedure FUN_WITH_UNDEFINED_VARIABLES is A : INTEGER; -- A is undefined... B : INTEGER; -- B is undefined... begin A := B; -- Quick, what value does A have? end FUN_WITH_UNDEFINED_VARIABLES; This compiles and executes under Alsys Ada.