> It's based on 'C' syntax, which itself isn't very far removed > from machine code - the switch statement is really just a > glorified set of goto statements. > > If you don't put the break in, it drops through to the next case. > > But it can be useful sometimes if you want to do some processing > for case A and then some processing for case A or B - though > making use of that results in very un-maintainable code. > > It's certainly a rich source of bugs, whatever language you're using.
Thanks for the info. I can't really see the rationale of requiring "break;" where the syntax of every other bit of CFML is geared towards making it a simple language that can be picked up very quickly. Aidan -- Aidan Whitehall <[EMAIL PROTECTED]> Macromedia ColdFusion Developer Fairbanks Environmental +44 (0)1695 51775 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
