Tim Mooney <[EMAIL PROTECTED]> writes:
> Regarding the change, maybe I'm being boneheaded again, but wouldn't the
> affect be the same (and perhaps the code a little clearer) if the label was
> instead outside the loop, right at the top? That way the loop test happens
> right away and if it fails you don't even enter the loop, which is the
> goal you're after, right?
Well, the bug is fixed, the code works. I think we should put our
energy into other Guile problems right now.
(I haven't looked at the code again, but if I remember correctly,
there's a reason of symmetry: If the label would be moved to the top,
the except case would be handled by code different in structure from
the code for read and write, so I think the present solution is more
clear. Not that I claim that iselect.c is particularly clear. :)
