At 07:45 AM 5/11/2001 -0700, Dave Storrs wrote:
>On Wed, 9 May 2001, Larry Wall wrote:
>
> > Dave Mitchell writes:
> > : My thinking behind "if fails on one, avoid on all" was that if it failed
> > : on at least one, then it may well fail on others that you dont have
> access
> > : to - either now or in the future, and thus perhaps isnt as good an
> optimisation
> > : as you figured. The other way would to be only enable for those
> architectures
> > : that experience a speedup.
> >
> > Makes sense.
> >
> > Larry
> >
>
> It does, however, mean that the code ends up *riddled* with with
>#ifdef's instead of merely shot full of them. I don't know about the rest
>of you, but I find this annoying and difficult to read:
[#ifdef nest snipped]
Right, I loathe those too. In that case the code should be abstracted out
to a function which can be overridden on a per-platform basis.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
