(Illustration by Gaich Muramatsu)
>>>>> "Troy" == Troy Benjegerdes <hozer_at_drgw.net> writes: Troy> Heh, well, IMHO, the GOTO's are evil and should be shot, Troy> killed, mangled, etc. Well, what really should happen is that an exception should be thrown. I don't know what all compilers y'all are committed to supporting so I can't insist on that. But if one must work with some lowest common denominator, "goto error_return"s are OK in my book, especially if the compiler will catch errors like the one in question. YM obviously does V. Troy> Following this theory, managed to rework the offending Troy> section of code to not need a goto. (althoug it then Troy> required about 3 move levels of 'if then else' blocks) Ughly; IMHO that's not a win. The biggest one would cover, what, about 50-60 lines? Troy> I posted the patch to the list earlier, let me know if you Troy> want it. Thanks, I saw it; I want to stick to the main line for the moment, is all. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules."Received on 1999-09-06 23:27:10