Xref: utzoo comp.lang.misc:7466 comp.object:3208
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!news.cs.indiana.edu!arizona.edu!ece.arizona.edu!dan
From: dan@ece.arizona.edu (Dan Filiberti)
Newsgroups: comp.lang.misc,comp.object
Subject: Re:  Type Systems and Dynamic Binding
Message-ID: <1991Apr16.183750@ece.arizona.edu>
Date: 17 Apr 91 01:37:50 GMT
References: <3843@ssc-bee.ssc-vax.UUCP> <27313:Apr1623:30:0391@kramden.acf.nyu.edu>
Reply-To: dan@ece.arizona.edu (Dan Filiberti)
Distribution: world,local
Organization: University of Arizona Dept. of Electrical and Computer Engineering
Lines: 30
Nntp-Posting-Host: dialsun.ece.arizona.edu

In article <27313@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu writes:
>You can implement all real-world EXAMPLES---or, at least, every example
>that's come up in this group---of dynamic typing directly in C. That's
>exactly what I've been doing. People say ``hey, here's a use of dynamic
>typing,'' and I show them how a C programmer would accomplish the same
>result.


So what?  I don't see your point.  Sure, you could probably accomplish
the same result, but at an unreasonable production cost.  And, no matter
how much you insist, C DOES NOT SUPPORT DYNAMIC TYPING.  Period.  The
whole point of having dynamic typing is reusability of code.  And, if
I wanted to reuse the modules you have written, I'd have to use your
interface...what makes you think that I would want to do that!  Sorry,
but your point is dumb.  If you're argueing against using C++, I can 
give you at least two great reasons to use it:

1.  Dynamic Typing is easily and readily available, done the same way
	every time.

2.  If you don't want to use dynamic typing, then DON'T.  C++ doesn't
	force you to do anything, just write C if you want.


So please, tell me your point, and end this useless thread....



		Daniel Filiberti
		dan@helios.ece.arizona.edu [:)}