Switch is usually more compact than lots of nested if else and therefore, more readableIf you omit the break between two switch cases, you can fall through to the next case in many C-like languages. With if else you'd need a goto (which is not very nice to your readers ... if the language supports goto at all).In most languages, switch only accepts primitive types as key and constants as cases. This means it can be optimized by the compiler using a jump table which is very fast.It is not really clear how to format switch correctly. Semantically, the cases are jump targets (like labels for goto) which should be flush left. Things get worse when you have curly braces:case XXX: { } break; Or should the braces go into lines of their own? Should the closing brace go behind the break? How unreadable would that be? etc.In many languages, switch only accepts only some data types.
1 5 1
sorry i didnt specify abt the programming language .. its JAVA!!
can u please make it fast
soory i have worked with net beans only not JAVA program
yaa thats okay i have also worked with netbeans