Compile time type checking

ruby-talk
1

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

···

-----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.

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.