From: "Volkmann, Mark" Date: 2002-08-28T05:09:18+09:00 Subject: RE: compile time type checking This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C24E05.894C57C0 Content-Type: text/plain; charset="iso-8859-1" > -----Original Message----- > From: Michael Campbell [mailto:michael_s_campbell@yahoo.com] > Sent: Tuesday, August 27, 2002 2:50 PM > To: ruby-talk@ruby-lang.org > Subject: Re: compile time type checking > > --- William Djaja Tjokroaminata wrote: > > Hi, > > > > In my opinion, compile time type checking helps, but it is by > > itself not > > sufficient. > > I don't think that was the assertion, was it? > > If I read the original poster correctly, he was saying compile time > checking *helps* a lot; it obviates the need for _some_ unit tests. That is what I meant. It seems to me that having compile-time type checking allows certain coding errors to be found more quickly and reduces the possibility that users will experience the equivalent of a Java ClassCastException or whatever happens in Ruby when you attempt to invoke a method on an object that doesn't support it. *********************************************************************************** WARNING: All e-mail sent to and from this address will be received or otherwise recorded by the A.G. Edwards corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. ************************************************************************************ ------_=_NextPart_001_01C24E05.894C57C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: compile time type checking

> -----Original Message-----
> From: Michael Campbell [mailto:michael_s_campbell@yahoo.com]
> Sent: Tuesday, August 27, 2002 2:50 PM
> To: ruby-talk@ruby-lang.org
> Subject: Re: compile time type checking
>
> --- William Djaja Tjokroaminata <billtj@z.glue.u= md.edu> wrote:
> > Hi,
> >
> > In my opinion, compile time type checking help= s, but it is by
> > itself not
> > sufficient.
>
> I don't think that was the assertion, was it?
>
> If I read the original poster correctly, he was say= ing compile time
> checking *helps* a lot; it obviates the need for _s= ome_ unit tests.

That is what I meant.  It seems to me that having co= mpile-time type checking allows certain coding errors to be found more quic= kly and reduces the possibility that users will experience the equivalent o= f a Java ClassCastException or whatever happens in Ruby when you attempt to= invoke a method on an object that doesn't support it.



***************************************************************************= ********
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
***************************************************************************= *********
 ------_=_NextPart_001_01C24E05.894C57C0--