Blog of Jitu

Generics

Also, few blog enteries on generics and variance in generics. Find them to be really useful.

First one and another one by Rick Byers.

Also, we should have a good generics support in the Managed JScript soon.

Object Lifetime and Dispose Pattern

IronRuby

This week IronRuby got released. First look on it can be found at John's blog.

This was a incredile work by the Ruby team and this came out really fast. I tried out and the result was very good. Found many reference to it on the web.
Scott followed up with a post on his blog, with a good WPF sample as well. On the roadmap for open source, Jason gives insite into that on his blog.

People have really started using it and there has been good feedback to it so far. There were some complains also and then some fast responses to them.
For of one of such by Antonio, the patch also was released given by Fepy. Open source really would go a long way here.

Managed JScript Limitations...

Managed JScript implementation, on Silverlight is a full implementation of Javascript Ecmascript 3.0 version. This supports interop with all other .NET languages and also other dynamic languages.

But other day, someone asked me about what doesn't work yet there. So could get the following from the silverlight site, where it talks about How to: Program Silverlight with Dynamic Languages

In the Silverlight 1.1 Alpha release, Managed JScript has the following limitations:

- The mapping between .NET Framework objects and Managed JScript objects is currently limited. For example, the Managed JScript String object cannot be used in places where System.String is expected, but the string primitive can be used. Managed JScript arrays cannot be used where .NET Framework arrays are expected.

- There is limited support for Javascript-style enumeration (that is, listing names instead of values); it is supported only for objects that implement IList and IDictionary. Enumeration on other .NET Framework objects lists values instead of names.

- Generics are not yet supported.

- Method overload resolution for candidate methods with numeric types other than double is not yet supported.

- Exceptions thrown in event handlers that are hooked up from Managed JScript code are not logged at the top of the HTML. Exceptions that are hooked up in markup are logged.

- The Eval function does not produce a correct value unless its input is a sequence of statements ending in a simple expression statement.

- The arguments.callee property is not supported.

 Will try to keep this list up to date , as and when things gets added or removed from here.

For-in in JScript

For-in the JScript is unique to other languages, in a way that it iterates over the keys, where as in most other languages ( C#, Python.. ), it iterates over the values.

 
var location = { x : 100, y : 200 }
for (var i in location) { print(i); }

Now, suppose the location was not a Jscript object, but a .NET object. ( from C#). This gives a interesting issue. What should be printed in the above case? Should it be 100, 200 or x, y ?
In the Managed Jscript, it iterates over the keys, because that’s what a Jscript programmer would expect, irrespective of, from where the object came from.

Introducing Managed JScript

introducing Silverlight

Silverlight sees the light!!

Finally Silverlight is out to the public.

More details to follow @ http://www.visitmix.com/