Xref: utzoo comp.lang.misc:6876 comp.object:2734
Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!news.cs.indiana.edu!arizona.edu!arizona!gudeman
From: gudeman@cs.arizona.edu (David Gudeman)
Newsgroups: comp.lang.misc,comp.object
Subject: Re: Dynamic typing -- To Have and Have Not (was R
Message-ID: <650@optima.cs.arizona.edu>
Date: 15 Mar 91 07:40:28 GMT
Sender: news@cs.arizona.edu
Followup-To: comp.lang.misc
Lines: 35

In article  <PCG.91Mar13185855@aberdb.test.aber.ac.uk> Piercarlo Antonio Grandi writes:
]...
]1) Don't provide dynamic typing as a language primitive and make it
]prohibitive...
]
]2) Don't provide dynamic typing as a language primitive, and make it
]possible to implement it...
]
]3) Provide dynamic typing only...
]
]4) Provide *both* dynamic and static typing...
]
]I reckon that Gudeman thinks that Bernstein advocates 1), while
]Bernstein really advocates 2); Gudeman himself advocates 3), and I
]advocate 4).

No, Gudeman thinks that Bernstein advocates (2), Gudeman himself
advocates (4), and Gudeman is willing to accept Grandi's word that
Grandi advocates (4).

Didn't anyone read "Runtime Polymorphism... part 2"?  OK, maybe part 1
one was so uninspiring that no one bothered with the sequal.  Anyway,
in that posting I described my preference for a system with optional
static typing.

Maybe my bickering with the B&D language people over the importance of
static typing has lead people to believe that I am opposed to static
typing in all forms, but I am not.  I am opposed to any language
feature that restricts my options and increases my effort in the name
of security.  The language designer has no idea how much security my
program requires.
--
					David Gudeman
gudeman@cs.arizona.edu
noao!arizona!gudeman