Re: Future Objective-C changes
Re: Future Objective-C changes
- Subject: Re: Future Objective-C changes
- From: David P Henderson <email@hidden>
- Date: Fri, 16 May 2003 07:16:59 -0400
On Friday, May 16, 2003, at 02:58 US/Eastern, David Cittadini wrote:
To better support type checking without having to make up new method
names all the time. Even though Objective-C/C++ is a wonderful
dynamic type language it also supports type checking. I would have
thought it would make sense that if it is going to provide some
ability to check types it might as well do it well. The system checks
for a clash of method names, why can't that check be extended (if
required) to the parameter types?
The complier does type checking but can not enforce it. Obj-C is a
dynamic language which means that the runtime will pretty much ignore
typing. Type checking exists as a nicety for the programmer writing the
code. The runtime depends on the programmer to do the right thing wrt
suppling parameters to methods. IOW, you the programmer are responsible
for making sure that you are doing the correct thing when passing data
types around. See quote below.
Dave
--
Chaos Assembly Werks
"The Trend over the last 20 years or so has been to design computer
languages that enforce a state of paranoia. You're expected to program
every module as if it were in a state of siege In Perl culture, by
contrast, you're expected to stay out of someone's home because you
weren't invited in, not because there are bars on the windows."
from Programming Perl
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.