From: "Volkmann, Mark" Date: 2002-08-28T04:37:48+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_01C24E00.EF103AE0 Content-Type: text/plain; charset="iso-8859-1" > -----Original Message----- > From: Mark Probert [mailto:probertm@nortelnetworks.com] > Sent: Tuesday, August 27, 2002 2:03 PM > To: ruby-talk@ruby-lang.org > Subject: Re: compile time type checking > > >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. > > I think that it depends on your needs. The "real > applications" that I create > using Ruby tend to have very simple user interfaces, usually > just a bunch of > command-line options. I hid all of the complicated stuff at > arms length from > the user. > > So, all of the "input" is strings, which are valid or not > (such as an IP > address). > I guess you could say that I design around the type issue. I wasn't referring to errors in user input. I'm talking about finding errors in my code. *********************************************************************************** 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_01C24E00.EF103AE0 Content-Type: text/html; charset="iso-8859-1" RE: compile time type checking

> -----Original Message-----
> From: Mark Probert [mailto:probertm@nortelnetworks.com]
> Sent: Tuesday, August 27, 2002 2:03 PM
> To: ruby-talk@ruby-lang.org
> Subject: Re: compile time type checking
>
> >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.
>
> I think that it depends on your needs.  The "real
> applications" that I create
> using Ruby tend to have very simple user interfaces, usually
> just a bunch of
> command-line options.  I hid all of the complicated stuff at
> arms length from
> the user.
>
> So, all of the "input" is strings, which are valid or not
> (such as an IP
> address).
> I guess you could say that I design around the type issue.

I wasn't referring to errors in user input.
I'm talking about finding errors in my code.



***********************************************************************************
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_01C24E00.EF103AE0--