Re: copying arrays
- From: Pascal Bourguignon <pjb@xxxxxxxxxxxxxxxxx>
- Date: Mon, 30 Apr 2007 18:56:23 +0200
Ken Tilton <ken@xxxxxxxxxxxxxxxxxx> writes:
[...]
The problem with PP is that, if our assumption is that people cannot
program, then we cannot program. It is one of those complexity
deals. That's wrong, let me try again: we cannot /in our programming/
make allowances for programmer fallibility. It's a slippery
slope. Once we make that bet, er, hedge, where do we stop? If we want
to say this bit of code might be flawed or this programmer might be a
loose cannon, where does the descent into paranoia halt?
In a way, and language specified error signaling is defensive programming.
Why should (/ 1 0) signal an error? It's obvious to everybody that you
should never try to divide 1 by 0. So there's no need to consider
this case in the code of /.
My point would be that DP or PP might be good ideas in some
circumstances and in some places, like near "interfaces".
--
__Pascal Bourguignon__ http://www.informatimago.com/
Small brave carnivores
Kill pine cones and mosquitoes
Fear vacuum cleaner
.
- Follow-Ups:
- Re: copying arrays
- From: Ken Tilton
- Re: copying arrays
- References:
- copying arrays
- From: Q
- Re: copying arrays
- From: Alan Manuel K. Gloria
- Re: copying arrays
- From: Dan Bensen
- Re: copying arrays
- From: Kent M Pitman
- Re: copying arrays
- From: Dan Bensen
- Re: copying arrays
- From: Ken Tilton
- copying arrays
- Prev by Date: Re: Writing HTML parser wasn't as hard as I thought it'd be
- Next by Date: Re: copying arrays
- Previous by thread: Re: copying arrays
- Next by thread: Re: copying arrays
- Index(es):