Where Is IntelliSense For "goto" statements?

[RichardM1]

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.

[Mycroft Holmes]

Richard Blythe wrote:

Does anyone know why Visual Studio does not implement IntelliSense for goto statements?

Probably so newbies will not use it until they get to the point of understanding it's consequences. I took the lemonade in the 90s that discredited that particular set of structures and have not used a goto in more that 12 years. I do not regret the decision!

Never underestimate the power of human stupidity RAH

[PIEBALDconsult]

I was waiting for someone else to make a serious answer. I suspect it's because a label doesn't exist like a function or variable does. They don't allocate memory. Are they in the name/symbol table (or whatever)?

[PIEBALDconsult]

It's more a language concern; modern languages have more robust sets of flow control constructs and so don't require it. I still have to use it DCL.

[Mycroft Holmes]

PIEBALDconsult wrote:

modern languages have more robust sets of flow control

Absolutely, I can't understand why it has not been, what's that word, deprecated. For the life of me I can't think of a reason for it to be there, I wonder if GoSub is still in there as well.

Never underestimate the power of human stupidity RAH

[Richard Blythe]

Somewhere in this thread, it has been assumed that I'm a VB guy. I write C#, read C#, eat C#. (Okay, maybe not that die hard) :) I've been trying to dig up a good example of me using the "goto" statement. However, in most cases, I would probably get a pile of contradictory replys. I guess I should take the nearest exit on this "goto" road. :laugh:

The mind is like a parachute. It doesn’t work unless it’s open.

[Leslie Sanford]

Richard Blythe wrote:

I've been trying to dig up a good example of me using the "goto" statement.

I haven't used goto's, but my understanding is that they can be helpful in error handling, e.g. goto HandleError. It allows you to write code after such goto statements in such a way that it can assume that no error has occurred, thus simplifying things. One could argue that this is what exceptions are for. But the same reasoning that says that goto's are bad would seem to apply to exceptions, maybe even more so. Using goto to jump ahead within a function to execute some error handling code would seem less confusing than throwing the control flow completely out of the current context to who knows where.

[Nish Nishant]

Ctrl-Space will drop down all available keywords/symbols (but it won't show just the labels). Maybe they never considered this a big enough priority since not many people use gotos these days.

Regards, Nish

---

Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application

[Nish Nishant]

Richard Blythe wrote:

I've been trying to dig up a good example of me using the "goto" statement. However, in most cases, I would probably get a pile of contradictory replys.

Here's one case where "some people" think it's okay:

private static void Foo(int x)
{
Console.WriteLine(String.Concat("Option: ", x));

switch (x)
{
    case 0:
        Console.WriteLine("English");
        goto case 1;

    case 1:
        Console.WriteLine("Spanish");
        break;

    default:
        Console.WriteLine("English");
        break;
}

Console.WriteLine();

}

And here's the refactored goto-less version:

private static void AltFoo(int x)
{
Console.WriteLine(String.Concat("Option: ", x));

switch (x)
{
    case 0:
        DisplayEnglish();
        DisplaySpanish();                
        break;

    case 1:
        DisplaySpanish();                
        break;

    default:
        DisplayEnglish();
        break;
}

Console.WriteLine();

}

private static void DisplaySpanish()
{
Console.WriteLine("Spanish");
}

private static void DisplayEnglish()
{
Console.WriteLine("English");
}

Regards, Nish

---

Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application

[Mycroft Holmes]

Richard Blythe wrote:

Somewhere in this thread, it has been assumed that I'm a VB guy

I think goto started life in basic which morphed into VB so the assumption seems reasonable to me. There are a lot of us around that code in both VB and C#, most seem to have a preference to C# but VB is so very common. I moved our teams to C# because all the best examples are in that flavour (and I needed to learn something new/different about then anyway).

Never underestimate the power of human stupidity RAH

[Lost User]

I can see no reason, it's not particularly hard to get the set of valid target labels for a given goto

[urbane tiger]

I'd like to know why C# doesn't have a comefrom, with or without Intellisense

"we shall patiently bear the trials that fate imposes on us" -- Anton Chekhov Uncle Vanya

[Richard Blythe]

If a developer plans to work heavily with MS Office projects, I would encourage them to learn VB. Other than that, I would strongly advise C#. I realize that most of the compiled funtionality between VB and C# is the same but by learning C#, you have a leg up on several languages: Java, JavaScript, C++, etc.

Mycroft Holmes wrote:

all the best examples are in that flavour

Your right, and C# hasn't become popular by accident.

The mind is like a parachute. It doesn’t work unless it’s open.

[glennPattonWork3]

Hi, Not a proper softy (I'm a hardware guy who programs on occasion) I have used a goto only in RTOS situations where if the program counter/accumlator goes beyond a certain point it will make a whole in the wall as it goes beyond reach. I was one of the spagetti basic guys who gave the goto a bad rep. It's just a way of moving around the memory so thats why the .NET compilers use it (or a jmp or jump instruction) it's only when people who didn't know what it was or how to use it got involved did it get a bad reputation. Glenn (let the abuse begin!)

[cgh1977]

Sorry.. I see the case you are trying to make, but in this specific case there is a simpler goto-less construct:

private static void AltFoo(int x)
{
Console.WriteLine(String.Concat("Option: ", x));

if (x != 1)
{
    Console.WriteLine("English");
}
if (x == 0 || x == 1)
    Console.WriteLine("Spanish");
}

Console.WriteLine();

}

I expect your response will be something along the line of 'extend the example to more complex cases and the if-then approach becomes unwieldy'. Granted. Of the three examples (mine and your two), your second example is the best solution. It is considerably easier to understand and is more maintainable. Suppose the specification adds support for three other languages: French, German, and Italian. The goto version becomes impossible (without a lot of convoluted spaghetti code), but this code is very clear:

private static void AltFoo(int x)
{
Console.WriteLine(String.Concat("Option: ", x));

switch (x)
{
    case 0:
        DisplayEnglish();
        DisplaySpanish();
        DisplayGerman();
        DisplayItalian();
        break;

    case 1:
        DisplaySpanish();
        break;

    case 2:
        DisplayGerman();
        break;

    case 3:
        DisplayItalian();
        break;

    default:
        DisplayEnglish();
        break;
}

Console.WriteLine();

}

private static void DisplayItalian()
{
Console.WriteLine("Italian");
}

private static void DisplayGerman()
{
Console.WriteLine("German");
}

private static void DisplaySpanish()
{
Console.WriteLine("Spanish");
}

private static void DisplayEnglish()
{
Console.WriteLine("English");
}

[chrissb]

This may be heresy, but is optimising yourself feasible? In which case goto would be allowed.

[chrissb]

Off topic. :P First thought is, wouldn't it be quicker to type goto than to use intellisense anyway? You hit "g", all available commands starting with G show up, then you select the one you want, then hit enter. Three key presses assuming it's top of the list, otherwise it would be easier to just type it up. It would be like waiting for intellisense to give you the IF command instead of just typing it. Amusing if I'm observing, useless otherwise.

[Avatar_generic]

Or conversely the non serious could just goto hell.

[englebart]

To answer the poster: Here are some reasons why I would not if I was writing the IDE on a deadline: I wonder if some Microsoft developer could post the number of "goto" statements present in the VS 2010 code base. This might be a hint. If there is not a huge number, I would love to know how many goto statements were used that were NOT for exiting an inner loop. 0. Assumption: gotos are rarely used. 1. Assumption: A goto will only be used to break a nested loop. This means that you will type "goto done;" and a few seconds later type "done:". 2. Assumption: each label will only be referenced once (maybe twice) 3. Assumption: It will probably be a short label. (e.g. done: ) 4. Assumption: A developer will never do this more than once (maybe twice) in a C# method. If they need more than one label, they will probably split the method up. 5. Given: The label is always local to a method. (You are not trying to retrieve a property or method from some object that you did not write) 6. Given: If you type the goto and label so that they mismatch, the compiler will catch it. See #2 and #7. 7. Given: If the IDE developer goes through all of the trouble to give a list of valid labels, and you select the WRONG label, you are just as screwed as if you had typed the wrong label! 8. Given: Workaround: Since it is local editing, just use Copy+Paste. Closed - Feature Not Needed.
P.S. Java killed the goto via the break [label]; and continue [label]; statements. goto is a Java reserved word, but also a compile error. C# decided to follow C++ and keep goto;

[englebart]

I think he means, type goto ! ! = Now give me my label.