From: "Volkmann, Mark" Date: 2002-08-28T03:47:03+09:00 Subject: 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_01C24DF9.FEA16260 Content-Type: text/plain; charset="iso-8859-1" I think the main reason that languages such as Ruby, Python, Perl and TCL *tend* to be used for "scripting" as opposed to "real applications" is that they lack compile time type checking. Since there is no compile step in Ruby, maybe this should be called pre-release type checking. I'm curious how some of you that have written real applications in Ruby have dealt with this. Don't you have problems where an application crashes on a user because the wrong type of object gets passed to a method and it tries to invoke a method of the object that it doesn't have? It seems to me that it's nearly impossible to write enough unit tests to catch all of these issues before code is released for production use. I love Ruby syntax, but this issue may be one that keeps many people using Java instead. *********************************************************************************** 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_01C24DF9.FEA16260 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable compile time type checking

I think the main reason that languages such as Ruby, Pyth= on, Perl and TCL *tend* to be used for "scripting" as opposed to = "real applications" is that they lack compile time type checking.= Since there is no compile step in Ruby, maybe this should be called pre-re= lease type checking.

I'm curious how some of you that have written real applic= ations in Ruby have dealt with this. Don't you have problems where an appli= cation crashes on a user because the wrong type of object gets passed to a = method and it tries to invoke a method of the object that it doesn't have?<= /FONT>

It seems to me that it's nearly impossible to write enoug= h unit tests to catch all of these issues before code is released for produ= ction use.

I love Ruby syntax, but this issue may be one that keeps = many people using Java instead.



***************************************************************************= ********
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_01C24DF9.FEA16260--