Re: Static/Dynamic typing, lessons from the field
- From: Pascal Costanza <pc@xxxxxxxxx>
- Date: Tue, 31 Jan 2006 09:32:05 +0100
Kaz Kylheku wrote:
Firstly, ignoring for a second the idea that catching type exceptions can be incorporated into the logic of a software system, type checking is not strictly required. A program that is free of type mismatch errors will run properly whether or not type checking is performed. It chugs along and always correct operations to correctly typed data.
That's not quite correct. When you have an object system in which messages are dispatched dynamically, you are effectively relying on type checks to determine the meaning of your program.
Pascal
-- My website: http://p-cos.net Closer to MOP & ContextL: http://common-lisp.net/project/closer/ .
- References:
- Static/Dynamic typing, lessons from the field
- From: pp
- Re: Static/Dynamic typing, lessons from the field
- From: Marcin 'Qrczak' Kowalczyk
- Re: Static/Dynamic typing, lessons from the field
- From: Kaz Kylheku
- Static/Dynamic typing, lessons from the field
- Prev by Date: Re: Help with one benchmark test needed
- Next by Date: Re: Interesting developments since "Beating the averages"?
- Previous by thread: Re: Static/Dynamic typing, lessons from the field
- Next by thread: Re: Static/Dynamic typing, lessons from the field
- Index(es):