Tuesday, September 23, 2008
Sunday, September 7, 2008
So let’s talk a little about how IronRuby fits into the .Net world, something that you should know at this point is that Microsoft is building a common platform for dynamic languages called the Dynamic Language Runtime or DLR for the short, which runs as a service on top of the CLR.
DLR provides common functionalities like MSIL generation, GC, so that dynamic language implementers can focus on the implementing there dynamic language on top of this without worrying about the “gooing” part to the CLR.
At the next step the DLR is going to generate MSIL from these trees, and the MSIL would execute under the CLR. Some pretty interesting things to note here is that when the DLR does not know how an operation should be actually executed, it looks at the currently executing dynamic language and ask it how the operation should be done, then the language responds with another tree on how the operation should be done, if the language does not know how the operation should be executed than the DLR takes a default action into evaluating the expression.
Something interesting to note here is that, these trees that the DLR gets back from asking questions on how to do certain thing in a language is actually cached, so that the next time the DLR encounters something like that, it looks at the cache for an answer, and does not go through asking the language for help.
The DLR is still being built and up to now developers involved in the DLR , says there are lot more work to be done.
The whole point of the DLR and the language actually complies into MSIL and gets executed under the CLR is interoperability between these dynamic languages built on top of the DLR and other .Net languages. This would actually mean that you can consume a library that was written on one of these languages inside C# or vise versa, i.e. consuming a C# library from these dynamic languages.
This brings us to the advantages of this hectic effort, something that most developers face is covering unit testing of there respective module, one the problems that they face is the time limit when writing these in something like C# or Java.
Now, with dynamic languages being able to interop, you can write your unit testing in a language like IronRuby and consume your .Net APIs. This is much easier cos' writing your test cases in a dynamic language is must faster, and increase your productivity.
Another area where this can help is in the area of domain specific languages (DSL), where your domain specific grammar can be written in a language like IronRuby or IronPython and where your actual code generation can happen in a statically type language like C#.
This effort is also worth while in places where we use XMl as “processing” language, like in build scripts, where your build "logic" can be written in a language like IronRuby, after all writing logic in a programming language is much easier then writing in XML, I never liked XML for these purposes anyway..
There are some dynamic languages that are being implemented now, like IronRuby and IronPython, and there initial implementation can be downloaded and played around with. I choose IronRuby as the language and trying it out a little bit now a days, you can try it out too, but before that, try learning the real power in dynamic languages and try playing around with Ruby before you go ahead with IronRuby.
Wednesday, September 3, 2008
One thing that came up last week was that the sorting on one of the paged grid did not work, ok…so we were hunting the bug down, but lucky something popped up in the log file and saved the day.
Clicking on the sort headers, makes a service call to retrieve the sorted data, and the UI code was written in such a way that the service call is trapped inside a try-catch block, and if any exception occurred, the exception is logged and empty data returned.
And unfortunately the service query had a bug on it. So which brings me to the point, you should catch exceptions only when you can handle it, for example, you might have anticipated that a DuplicateNameException would be thrown, well go ahead, catch it and show a nice message to the user, but if you cant, don’t put it inside a catch block and bypass the exception just for the sake of not crashing the UI.
If you really want to log it, fine, log it then remember to re-throw the exception although re-throwing as its own performance cost.
And to be amazed, the error was there al the time and no one noticed it, which brings to the justifiation the if you dont handel exceptions that you cant handle, you would have seen the issue so much earlier.