Where Is IntelliSense For "goto" statements?
-
Richard Blythe wrote:
I don't use the: "goto" statement very often but I have started using it more frequently.
>SMACK!!< You what? :| I haven't found a need for a GOTO in the last, oh, 15 years...
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009...Thanks for your informative post. :laugh:
The mind is like a parachute. It doesn’t work unless it’s open.
-
Richard Blythe wrote:
I don't use the: "goto" statement very often but I have started using it more frequently.
>SMACK!!< You what? :| I haven't found a need for a GOTO in the last, oh, 15 years...
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009... -
I don't use the: "goto" statement very often but I have started using it more frequently. Does anyone know why Visual Studio does not implement IntelliSense for goto statements? For example: // VS code editor does not show IntelliSense with //available "Label_" when entering this goto statement if (condition == true) goto Label_ExitCode; //... Label_ExitCode: //...
The mind is like a parachute. It doesn’t work unless it’s open.
Richard Blythe wrote:
I don't use the: "goto" statement very often but I have started using it more frequently.
Richard Blythe wrote:
Does anyone know why Visual Studio does not implement IntelliSense for goto statements?
See above link. :) Seriously though see this.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
-
YES _ NOW PUT DOWN THAT GOTO IMMEDIATELY AND TAKE TWO STEPS BACK! I WILL FIRE ON YOU! :laugh:
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009... -
Hey guys, give it a break;
-
Hey guys, give it a break;
Why not continue?
It's time for a new sig. Seriously.
-
Why not continue?
It's time for a new sig. Seriously.
I'll do a feasibily first, but I'll keep you in the loop on changes foreach sprint.
-
Why not continue?
It's time for a new sig. Seriously.
We probably need to switch things, at least I think that's the case.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Why not continue?
It's time for a new sig. Seriously.
I don't use goto statements to exit a loop. Why is Dave thumbing his nose about using "goto"? If you decompile the .Net Framework, their developers still use "goto" statements. By the way, my original question has yet to be answered.
The mind is like a parachute. It doesn’t work unless it’s open.
-
We probably need to switch things, at least I think that's the case.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
It would be fun if we do drag this thing for a while.
It's time for a new sig. Seriously.
-
It would be fun if we do drag this thing for a while.
It's time for a new sig. Seriously.
In the event that we can't, we'd better delegate someone to release the thread.
-
I don't use goto statements to exit a loop. Why is Dave thumbing his nose about using "goto"? If you decompile the .Net Framework, their developers still use "goto" statements. By the way, my original question has yet to be answered.
The mind is like a parachute. It doesn’t work unless it’s open.
a goto in some decompilation output does not prove there was a goto in the original source; it could be the decompiler did not recognize the original (looping) construct. In the end, every construct that changes the program flow is bound to get translated in an elementary jump/goto/branch/call/return instruction. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
-
I don't use the: "goto" statement very often but I have started using it more frequently. Does anyone know why Visual Studio does not implement IntelliSense for goto statements? For example: // VS code editor does not show IntelliSense with //available "Label_" when entering this goto statement if (condition == true) goto Label_ExitCode; //... Label_ExitCode: //...
The mind is like a parachute. It doesn’t work unless it’s open.
What language?
-
In the event that we can't, we'd better delegate someone to release the thread.
We could always repeat until the next topic comes up.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
What language?
C# Have you noticed that no one has even remotely answered the original question?
The mind is like a parachute. It doesn’t work unless it’s open.
-
a goto in some decompilation output does not prove there was a goto in the original source; it could be the decompiler did not recognize the original (looping) construct. In the end, every construct that changes the program flow is bound to get translated in an elementary jump/goto/branch/call/return instruction. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
Point well taken.
The mind is like a parachute. It doesn’t work unless it’s open.
-
We could always repeat until the next topic comes up.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
You could always try to override the topic.
-
You could always try to override the topic.
-
a goto in some decompilation output does not prove there was a goto in the original source; it could be the decompiler did not recognize the original (looping) construct. In the end, every construct that changes the program flow is bound to get translated in an elementary jump/goto/branch/call/return instruction. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
Luc Pattyn wrote:
translated in an elementary jump/goto/branch/call/return instruction
Good for the goose, good for the gander. There are instances where nothing else works, but they tend to be when you are implementing threads (not using them, implementing them). And when you are using VB. Wait, you are a VB programmer, why do you want to get rid of the only errorarrow in your quiver? Damn, that was a good line. :sigh: Except I wrote it after I read Dave Kreskowiak's signature, not yours, so it doesn't apply here. Well, I hope someone else can re-use it later. :)
Opacity, the new Transparency.