>I don't see too much wrong with gotos as long as they are used correctly to
I agree, but GOTOs  ( from experience of translating BASIC->C ) allow to much

freedom to deviate from a rational ( structured ) program flow which is readable

for others ( cleaning up spag code is much akin to programming in C64 ML IMHO
> I wonder if CS even teaches the             
proper use of GOTO's anymore?

 I started my BSCS @ SJSU in 1989 ( when the CS dept wuz part of the Math dept )
GOTOs weren't taught & their appearace in hmwrk source code could lower your grade
( actually 1 teacher allowed them w/o penalty but all other professors complained
about his spagehtti coding eventhough his projectss where (nearly) always on time
while the rest of the Ph.D's projects where always behind schedule )

>>
Once you start adding if then else structures             
then you start opening up a bigger can of worms like, while, do until, for,
do for, case, sub, function, etc.
>>
	you forgot about C's venerable switch {break} structure & its 'fallthru'
hazards  ;)
	( I heard a buggy switch structure miscommings caused one of AT&T's