Python from Wise Guy's Viewpoint

[Greg Menke]

prunesquallor at comcast.net writes:

> Fergus Henderson <fjh at cs.mu.oz.au> writes:
> 
> > prunesquallor at comcast.net writes:
> >
> >>Fergus Henderson <fjh at cs.mu.oz.au> writes:
> >>
> > (Anyway, type-checking hardware would only solve part of the problem, I think.
> > Dynamic type checking imposes two costs: one is the time cost of performing
> > the checks, and the other is the locality cost due to the code size increase.
> > Type-checking hardware avoids the code size increases, but I don't think it
> > helps with the time cost of performing the checks.)
> 
> Actually it works quite well with performing the checks.  In general,
> type checking is much quicker than computation, and in general it can
> be performed in parallel with computation (you simply discard the
> bogus result if it fails).  You don't need very much hardware, either.

As is also amply demonstrated by ECC hardware that operates right
alongside the memory- considerably easier than doing it in software.

Gregm