From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Jan Skibinski <jans@numeric-quest.com>
Cc: Jonathan Coupe <jonathan@meanwhile.freeserve.co.uk>, caml-list@inria.fr
Subject: Re: [Caml-list] OCaml related article
Date: Mon, 23 Apr 2001 10:12:20 +0200 [thread overview]
Message-ID: <20010423101220.B517@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.LNX.4.21.0104220745180.28550-100000@info.numeric-quest.com>; from jans@numeric-quest.com on Sun, Apr 22, 2001 at 08:12:34AM -0400
> His conclusion though is that it is practically impossible
> to introduce any kind of static typing to Perl.
Dominus' claim is that if it could be done, it would still be largely
useless: since Perl has so many context-dependent automatic coercions,
nearly all programs would be correct, and the type system wouldn't
help much finding programming errors.
Actually, I believe one could do a soft typing system for Perl along
the lines of Mr. Spidey for Scheme
(http://www.cs.rice.edu/CS/PLT/packages/mrspidey/), using
constraint-based flow analysis. Of course, uses of "eval" would not
be checked at all. But Dominus' point that it would be largely
useless is probably true.
> Contrast it
> with http://www.cc.gatech.edu/~lex/ti/ti.html
> where Lex Spoon attempts to deliver a type inference engine to
> Smalltalk (sic!).
Why not? Constraint-based flow analysis can be applied to Smalltalk
(at least without the reflection features -- if you change the
behavior of method invocation, all bets are off), and since Smalltalk
has cleaner, more restrictive dynamic semantics than Perl, it could
actually be useful in finding errors.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-04-23 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 13:55 Jonathan Coupe
2001-04-22 12:12 ` Jan Skibinski
2001-04-23 8:12 ` Xavier Leroy [this message]
2001-04-23 5:13 ` Jan Skibinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010423101220.B517@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=jans@numeric-quest.com \
--cc=jonathan@meanwhile.freeserve.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox