kenn humborg kennlinuxie mon aug 12 2002 080558pm 0100 nick murtagh wrote mon 20020812 1956 kenn humborg wrote well consider break inside select statement part syntax rather control flow modifier comes assembly level gets turned kind jump instruction pretend dont know im programming know shouldnt see _mandatory_ part syntax mandatory leave break flow control continue next case useful certain circumstances know however discussion tending towards dont use things like goto break alter flow control program valid 100 time reasonable rule thumb idea looking code easier see control moves function basic control blocks work specific example replacing break loop modified expression shows look one place see youll run end loop hunt whole loop although particular example wasnt really good since extra test adding done setting done true loop much break really idea surprise next programmer little possible sees code similar vein break every case select block makes flow much clearer flow goes zero one case blocks executed flows comes bottom leaving break statements breaks assumption point situations makes sense leave breaks usually tend consider break end case like brace end block fact maybe wouldnt bad idea language designed continue statement meant fall break wasnt needed select x case 1 something doesnt fall case 2 something falls next case continue case 3 something doesnt fall default something doesnt fall still hindsight sigh later kenn irish linux users group iluglinuxie httpwwwlinuxiemailmanlistinfoilug unsubscription information list maintainer listmasterlinuxie tue 13 aug 2002 012346 0100 ilug slashdot ew dijkstra humor