The new GOTO Statement?

Lost User

Yes, you can abuse lambda's and make a mess. You can abuse goto and make a mess. You can abuse boolean variables to simulate some forms of goto and make just as big a mess. You can abuse operator overloading and make a mess, and when James Gosling says you can't have operator overloading in Java, you can make just as big a mess with method overloading and virtual methods if you set your mind to it. You can abuse switch in atrocious ways in C and C++ (case goes pretty much anywhere, it doesn't even look like valid syntax but it is), which is like a goto where you don't even know for sure where it will go. You can abuse pretty much every aspect of a general purpose programming language.

Joan M

You've just abused of your own post... and you've made a mess when you've painted some words in blue like links without being true links... :rolleyes:

[www.tamautomation.com] Robots, CNC and PLC machines for grinding and polishing.

Manfred Rudolf Bihy

Amen to that!

"With sufficient thrust, pigs fly just fine."

Ross Callon, The Twelve Networking Truths, RFC1925

OriginalGriff

Yes, I agree. Every element of a language has it's use - even goto and var in C#- it's just that if you use them inappropriately you get less readable code instead of more. Personally, I find lambdas are useful in their place, but I avoid using them most of the time. var should be banned outside Linq!

Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water

Pete OHanlon

God gave rock and roll to you. Rock and roll to you. Put it in the soul of everyone.

*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington

"Mind bleach! Send me mind bleach!" - Nagy Vilmos

CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

Nemanja Trifunovic

sisnaz wrote:

What's the difference between using embedded functions and a goto statement?

:~ How are they similar? One is a flow control statement and another is a scope for a function. Or am I missing something?

utf8-cpp

CPallini

Bad 'software engineers' are to blame if goto has such a bad fame.

Veni, vidi, vici.

PIEBALDconsult

Me and the boys will be playing all night.

Lost User

sisnaz wrote:

What's the difference between using embedded functions and a goto statement? It seems to me it's no different and just as difficult to follow and maintain. I'd be curious on other opinions of this practice.

:doh: A GoTo breaks the flow where as a embedded function becomes part of the flow. Here is some psuedo code to show you the difference

bool flag = GetFlag() //Embedded but the point is made elsewhere

if flag
GOTO: SomeLabel

EmbeddedMethod();

SomeOtherEmbeddedMethod();

OK, so this code will ONLY run the EmbeddedMethod if the flag is false. One would think in that case it will also run the SomeOtherEmbeddedMethod and here is lies the evil of GoTo. What if the EmbeddedMehtod is defined in the same manner using a GoTo? i.e.

bool flag = GetSomeOtherFlag()
if flag
GoTo: SomeOtherLabel

Now as a user when I am looking at the first code snippet I have to account for that extra GoTo that could happen. Maybe I must run some logic if the EmbeddedMethod runs. How do I ensure it in the most simple manner? Solution, Dont't use GoTo!

Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.

Lost User

Bad Software languages breed bad software engineers....

Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.

PIEBALDconsult

Hear hear!

Bassam Abdul Baki

You're abusing him and his thread. ;P

Web - BM - RSS - Math - LinkedIn

Bassam Abdul Baki

I fell in love with Goto when I first learned it. What can I say, I was able to follow it rationally. :)

Web - BM - RSS - Math - LinkedIn

lewax00

var is great for foreach loops when you have long types like KeyValuePairs with a generic type for the value. I don't use it often outside that.

lewax00

I don't know if the complexity increases significantly, but people well versed in imperative languages, like the majority of C#, may not be familiar with functional programming constructs, making it a little tougher to figure out just from lack of exposure. And they are harder to debug, can't seem to put breakpoints inside of them. But I probably abuse them a little, some sections of my code look more like LISP than a C-family language...especially when I realized I could use them to make wrappers out of certain loops and similar constructs that were being used over and over again in my code...

jschell

sisnaz wrote:

What's the difference between using embedded functions and a goto statement?

Because one is cool and the other isn't. It is of course related to the difference between understanding the syntax of a language and being able to write syntax that is maintainable.

ekolis

harold aptroot wrote:

You can abuse switch in atrocious ways in C and C++ (case goes pretty much anywhere, it doesn't even look like valid syntax but it is)

Are you saying that you can have a case statement without an enclosing switch? :wtf: What does THAT look like, and what would one use it for?

sisnaz

YES! I completely agree. I have a team member that declares EVERYTHING as var. He says it's because it makes it loosely coupled and also C Sharpner tells him too.

sisnaz

Perhaps embedded method is a loose term. This is what I'm referring to. In my opinion it reflects the same goto example you posted.

public string ReturnSomething()
{
// ... some logic
// ...
var compare = new Func<string, string, string, string, bool>((compare1, compare2, compare3, compare4) =>
{
return (compare1.Equals(compare2, StringComparison.InvariantCultureIgnoreCase) &&
compare3.Equals(compare4, StringComparison.InvariantCultureIgnoreCase));
});

        // some more logic flow
        // ....

        if (compare("a", "b", "c", "d")) {
            // some logic
        }

        return "Something";
    }

Mycroft Holmes

OriginalGriff wrote:

var should be banned outside Linq!

Oh you CAN use them elsewhere!

Never underestimate the power of human stupidity RAH