32 lines
1.3 KiB
Plaintext
32 lines
1.3 KiB
Plaintext
From: doylep at ecf.toronto.edu (doylep at ecf.toronto.edu)
|
|
Date: Thu, 29 Apr 1999 19:25:23 GMT
|
|
Subject: Python IS slow ! [was] Re: Python too slow for real world
|
|
References: <613145F79272D211914B0020AFF6401914DAD8@gandalf.digicool.com> <p5g15lmb35.fsf@bidra241.bbn.hp.com> <slrn7ieipq.8uk.wtanksle@dolphin.openprojects.net> <372769B0.3CE8C0F3@prescod.net> <slrn7if4d4.9lh.wtanksle@dolphin.openprojects.net> <p54slzn7rt.fsf@bidra241.bbn.hp.com>
|
|
Message-ID: <7gabmt$jm$1@nnrp1.dejanews.com>
|
|
X-UID: 459
|
|
|
|
In article <p54slzn7rt.fsf at bidra241.bbn.hp.com>,
|
|
Markus Kohler <markus_kohler at hp.com> wrote:
|
|
>
|
|
> As far as I remember Eiffel requires a global system analysis to be type
|
|
> safe at compile time.
|
|
|
|
Well, the story is a bit more complicated. The bottom line is that current
|
|
compilers use run-time checks in the dangerous situations, and that the
|
|
dangerous situations are easily avoided anyway.
|
|
|
|
If you avoid covariant arguments and feature hiding, as many do, Eiffel is
|
|
statically typesafe with no global analysis. Personally, I'd prefer if Eiffel
|
|
didn't offer these language "features" at all.
|
|
|
|
--
|
|
Patrick Doyle
|
|
doylep at ecf.toronto.edu
|
|
|
|
-----------== Posted via Deja News, The Discussion Network ==----------
|
|
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
|
|
|
|
|
|
|
|
|