Re: voting on GOTO
Chris Bensler wrote:
>
> I personally do not have much of an opinion on the implementation of goto.
> Either
> way, I won't use it. My main concern is having to be aware the potential for
> others to have used goto in any code I may procure from the archives and
> attempt
> to fix or otherwise modify. Perhaps a warning that can be toggled to indicate
> if goto has been used would be handy. Then I could avoid any code with goto
> whatsoever, or at least know they are there and where.
>
Not to pick on any one person because I have heard this many times. I personally
am for goto because in some situations it can be very helpful. In those
situations where there is a better way of doing things, I will use the better
way.
Anyway, the above statement... goto can make code very clear and easy to
maintain if used properly. goto can make code very dirty and a mess to maintain
if used incorrectly. while, for, if, nested loops, too many functions, too little
functions can all make code easy/hard to understand as well.
The thing here is if the library author knows what they are doing, their use of
goto will be invaluable. If the library author does not know what they are doing,
I don't want to use their code if it has goto or not!
A library programmed correctly is a good library regardless of it's use of goto.
A library programmed incorrectly is a mess regardless of it's use of goto.
--
Jeremy Cowgar
http://jeremy.cowgar.com
|
Not Categorized, Please Help
|
|
