Re: Function calling
Re: Function calling
- Subject: Re: Function calling
- From: Ondra Cada <email@hidden>
- Date: Thu, 26 May 2005 03:02:43 +0200
On 26.5.2005, at 2:44, Thomas Davie wrote:
Nope. Strong typing is more or less irrelevant. There are only two
things it is good for:
(a) to check for programmer's mistakes;
(b) to allow for proper argument and return value automatic casting.
Both of them are *completely* compile-time, and (but for them
proper casting of (b)) have no run-time consequence at all.
Sorry for the multiple replies, but I must disagree. Strong typing
has a huge impact on the runtime because checks do not need to be
made in the runtime – we have already verified in the typechcker
that it will all work.
Wrong. The information compiler has is *principially and profoundly*
incomplete, and you cannot use it reliably -- just have a look at
Java or C++.
For example, compile-time you can't know what changes will be caused
by a category or by a poseAsClass:. Either you forbid such things,
which cripples the language to total unusability like Java's, or you
just have to live with the fact compile-time checks are good for
nothing (but catching a few typos).
Unfortunately for a C derivative like O-C, strong typing is never
going to happen.
Fortunately.
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden