Good point.

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";
    }

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.

After coming down off of the "That's pretty cool" factor and as members on my team have increasingly been using anonymous methods, lambda expressions and new Func<> routines embedded in methods. The complexity (IMO) as increased significantly. I've begun to question this seemingly popular approach as; 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.

:laugh: Well in that case I have 5 unknown errors LOL!

One of my biggest pet peeves in the software industry is the infamous "An unknown error as occurred". How can this be?? Surely somebody knows something about it, otherwise why is it there? So I ask, is there REALLY such thing as an unknown error? I don't get why this has become the catch all of "I give up, something happened and I'm too lazy to figure out why"