
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
Joseph Kiniry <[EMAIL PROTECTED]> wrote: > Marcel Weiher <[EMAIL PROTECTED]> originally wrote in the > comp.lang.objective-c newsgroup: >> The problem is that this warning is easily circumvented and gives >> you no actual guarantee at runtime. The type-system is quite leaky, >> and necessarily so for it not to hobble Objective-C's dynamic >> nature. Heck, even Eiffel's type system is leaky, and it is one of >> the more strict ones around... > I am unsure what you mean by "Eiffel's type system is leaky". > If you are referring to what are known as CAT-calls in the Eiffel > community, then a solution to this issue (which is fairly type > theoretic and has less practical impact than one would think) That must have been it. The argument "has less practical impact than one would think" is exactly what people in the dynamic programming camp apply to the largely theoretical problems proponents of static typing bring up... ;-) There are supposed to be all these problems, but we just don't see them in practice... Marcel
| <-- __Chronological__ --> | <-- __Thread__ --> |