In regard to: Re: guile 1.3.4 & CVS: label without statement bug in...: >Tim Mooney <[EMAIL PROTECTED]> writes: > >> I think a correct fix for this problem is to move the label to the very >> top of the while, just before the --i;. That causes the label to be followed >> by a statement, and I think the overall effect is the same (though if I'm >> wrong, please let me know). > >Your fix changes the semantics of the code since a jump to that label >will skip the loop test. A fix which doesn't change the semantics is >an empty statement after the label: > >cont_except: ; Mikael- My apologies for the delay in responding -- I postponed this response and then forgot about it until today. You're right, I completely missed the obvious reason for having the label at the bottom. That was a pretty boneheaded error on my part. I'll claim lack of sleep, but I obviously wasn't thinking... 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? Tim -- Tim Mooney [EMAIL PROTECTED] Information Technology Services (701) 231-1076 (Voice) Room 242-J1, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164
