Skip to main content

Invoking methods with Out and Ref !!!

Straight to code.....

int SomeMethod(string arg1,
    string arg2,
    ref DayOfWeek arg3)
{
    // Wildest implementation!
}

The above method had to be executed on its dispatcher thread. So let unravel a bit of the wildest implementation above.

int SomeMethod(string arg1,
    string arg2,
    ref DayOfWeek arg3)
{
    if (Disptacher.CheckAccess())
    {
        var funcDelegate = (Func<string, string, DayOfWeek, int>)SomeMthod;

        return Dispatcher.Invoke(funcDelegate,
            arg1,
            arg2,
            ref arg3);
    }

    // Wilder implementation!!
}

Before you say anything, yes, the compiler spat the following errors:-

Error 1  No overload for 'SomeMethod' matches delegate 'System.Func<string,string,DayOfWeek,int>

Error 2 The best overloaded method match for 'System.Windows.Threading.Dispatcher.Invoke(System.Delegate, params object[])' has some invalid arguments

Error 3  Argument '4': cannot convert from 'ref System.DayOfWeek' to 'object'

I had some experience with Error 3 earlier, and I had written about it. That came in handy to resolve Error 3. So code is getting better...

int SomeMethod(string arg1,
    string arg2,
    ref DayOfWeek arg3)
{
    if (Disptacher.CheckAccess())
    {
        var funcDelegate = (Func<string, string, DayOfWeek, int>)SomeMethod;

        var args = new object[] {
            arg1,
            arg2,
            arg3
        };

        return Dispatcher.Invoke(funcDelegate, args);
    }

    // Wilder implementation!!
}

Then I was left with one Error 1. I felt I needed a hammer to bang my head to get rid of the error. And it was all nothing but stupidity, or I should have been sleepy. I have been using Func so much that I had got the feeling that it is a keyword (for lack of a better word). To realize that Func delegate had no overload of the type/sort (I was using) took an hour or so.

We can declare a delegate with same name Func as follows:-

public delegate TResult Func<T1, T2, T3, TResult>(T1 arg1,
    T2 arg2,
    ref T3 arg3);

But I declared with a different name to avoid confusion and clear up my misconception. Now the wildness of the implementation was almost unraveled except the method was not working as expected. Let us see the code cleared of all compiler errors:-

int SomeMethod(string arg1,
    string arg2,
    ref DayOfWeek arg3)
{
    if (Disptacher.CheckAccess())
    {
        var funcDelegate = (Func<string, string, DayOfWeek, int>)SomeMthod;

        var args = new object[] {
            arg1,
            arg2,
            arg3
        };

        return Dispatcher.Invoke(funcDelegate, args);
    }

    // No more implementation
    arg3 = DayOfWeek.Friday;

    return 1234;
}

What is that expected behavior that is not experienced? And what is the reason? I will write about in a short while cuz my beer stole the preference.

Hint: Why does not the client code (Code calling SomeMethod) get the correct value in DayOfWeek argument? In our case, DayOfWeek.Friday.

Post a Comment

Popular posts from this blog

Passing CComPtr By Value !!!

This is about a killer bug identified by our chief software engineer in our software. What was devised for ease of use and write smart code ended up in this killer defect due to improper perception. Ok, let us go!CComPtr is a template class in ATL designed to wrap the discrete functionality of COM object management - AddRef and Release. Technically it is a smart pointer for a COM object.void SomeMethod() { CComPtr siPtr; HRESULT hr = siPtr.CoCreateInstance(CLSID_SomeComponent); siPtr->MethodOne(20, L"Hello"); }Without CComPtr, the code wouldn't be as elegant as above. The code would be spilled with AddRef and Release. Besides, writing code to Release after use under any circumstance is either hard or ugly. CComPtr automatically takes care of releasing in its destructor just like std::auto_ptr. As a C++ programmer, we must be able to appreciate the inevitability of the destructor and its immense use in writing smart code. However there is a difference between …

jqGrid: Handling array data !!!

This post is primarily a personal reference. I also consider this a tribute to Oleg, who was fundamental in improving my understanding of the jqGrid internals - the way it handles source data types, which if I may say led him in discovering a bug in jqGrid.

If you are working with local array data as the source for jqGrid, meaning you will get the data from the server but want the jqGrid not to talk to the server anymore, and want to have custom handling of the edit functionality/form and delete functionality, it is not going to be straightforward - you need to have a decent understanding of how jqGrid works, and you should be aware of the bug Oleg pointed in our discussion. I repeat this is all about using jqGrid to manage array data locally, no posting to server when you edit or delete, which is where the bug is.

$('#grid').jqGrid('navGrid', '#pager', { recreateForm: true, add: false, search: false, refresh: false, …

Offering __FILE__ and __LINE__ for C# !!!

THIS POST USES SYNTAXHIGHLIGHTER AND HAS ISSUES RENDERING CODE ONLY IN CHROME
Not the same way but we could say better.
Visual Studio 2012, another power packed release of Visual Studio, among a lot of other powerful fancy language features, offers the ability to deduce the method caller details at compile time.
C++ offered the compiler defined macros __FILE__ and __LINE__ (and __DATE__ and __TIME__), which are primarily intended for diagnostic purposes in a program, whereby the caller information is captured and logged. For instance, using __LINE__ would be replaced with the exact line number in the file where this macro has been used. That sometimes beats the purpose and doesn't gives us what we actually expect. Let's see.

For instance, suppose you wish to write a verbose Log method with an idea to print rich diagnostic details, it would look something like this.
void LogException(const std::string& logText, const std::string& fileName, …