ThatThrowsException(): Expression denotes a `variable', where a `method group' was expected

[FodderMK]

I am getting the following error on the ThatThrowsException when I import the UnTest package into Unity 4.2.0f4 on Windows 7:

Assets/UnTest/Editor/Assert.cs(44,13): error CS0119: Expression denotes a variable', where a method group' was expected.

Not sure what other information you need in order to debug this issue.

[tenpn]

UnTest 0.4.0, right? Just downloaded the package from github and imported to fresh project, and it went fine, but that was on OSX.

Can you post that line and the surrounding context, post-import? Want to check it's exactly the same as mine.

[FodderMK]

Yes, 0.4.0.

public static void ThatThrowsException(Action lambda, Type exceptionType) {

    bool isThrown = false;

    try {
        lambda();
    } catch(Exception e) {
        isThrown = e.GetType() == exceptionType;

    } finally {
        if (isThrown == false) {
            throw new Exception("Did not get exception of type " 
                                + exceptionType.ToString());
        }
    }
}

I removed that chunk of code (and corresponding tests) so I could try out the rest of the package and haven't encountered any other problems yet.

[tenpn]

How odd... Maybe lamda is a keyword in some version of mono you have installed? Would you try search-replacing it with, say, "throwingAction" and see if that fixes the issue? I'm not asking you to make a pull request.

[FodderMK]

That didn't seem to make any difference in the error message.

[tenpn]

Ok, thanks anyway! Don't suppose you can send me the game project you're adding UnTest to?

[FodderMK]

Unfortunately no. If I get time today I'll try creating a project from scratch and seeing if that makes a difference.

Are you testing on Unity 4.2 by chance?

[tenpn]

Yep. I'm wondering if it's a conflict with something in a global namespace. I know that produces very uninformative error messages.

[FodderMK]

Installed the plugin at home and didn't see a problem. Will spend a little time tomorrow at work to see if I can see what is different.

[tenpn]

Ok, let's leave this open until you're happy either way.

[tenpn]

Did you figure out what the problem at work was?

[FodderMK]

Sorry, no. I took another quick stab at it but can't seem to find the
cause.

On Sun, Aug 18, 2013 at 8:22 AM, Andrew Fray notifications@github.comwrote:

Did you figure out what the problem at work was?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/15#issuecomment-22832222
.