Back to General and Gameplay Programming

Thoughts on switchs.

Tim · 2012-12-26T12:03:04

so, i was thinking of switch's the other night, and one of the annoyances i find with switchs is that in many cases, i simply write out code that boils down to being an if/else if/else statement's because all the switch wants to do is break out after each case, and I only potentially want to use w/e the compiler optimizations switchs with. so i was thinking of a potential design solution for this, that doesn't require adding a break after every statement, and came up with this: int Foo(int value){ int r=0; switch(Value; break){ //think of w/e is after the ; as a goto at the bottom of each case, so with this one statement, i append a break to every single case, this could be used for anything, but break is just a common example. case 0: r=1; case 1(): r=2;//appending a () before the : and after the value overrides what the switch statement's conditional does, with what is specefied in the (), in this case, nothing is specefied, so we have default switch behavior here. case 2: r=r+2; default: r=100; } return r; //I know i can just return in the switch to do what i want, but this is suppose to be an example. } int main(int argc, char **argv){ Foo(0) //R = 1 Foo(1) //R = 4 Foo(2) //R = 2 Foo(3) //R = 100 return 0; } any thoughts on this, is their a more elegant design that i'm missing, or are my thoughts on this just crazy/stupid? and yes, their is plenty of room for discussion on why one would design code that essentially boils down to an if/else if/else code block, and i suspect that this discussion might fall into that, but we'll see what people's thoughts on this is.

General and Gameplay Programming Programming

Started by slicer4ever December 25, 2012 07:16 PM

9 comments, last by Khatharr 11 years, 3 months ago

Khatharr

8,814

December 26, 2012 12:03 PM

My winprocs often end up with each line looking something like:

case LABEL: labelProc(); break;

If you are going to do that, you may as well just have a container of pointers to function, or a container of std::function, or a container of signals (like boost::signal). You just "register" in that container any behavior you need to have in response to events, and then the function itself is very clean. I have done this type of thing before around select() for network programming in Unix, and it works great.

That sounds like a good idea. I'll look in to it.

void hurrrrrrrr() {__asm sub [ebp+4],5;}

There are ten kinds of people in this world: those who understand binary and those who don't.

Thoughts on switchs.

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Thoughts on switchs.

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines