No, Java has the class member and instanceof operator, which would take care of this problem. These are missing in ChucK.
That may already have it by its implementation. When looking into the sources, I think I saw a base class object from which all others were derived. If so, it is the Java grammar imposed on top that restricts it.On 4 Sep 2010, at 17:46, Kassen wrote:
It is not having a type system that is causing problems, but that it often is a bit underdeveloped.
Yes, and malnourished. >:-)
For example, if one wants dynamic typing, that can be done by having a type by which the other types can be derived dynamically. Then the problems like the one above cane be done by introducing a new type.
We can do that for non-primitives, but we can't ask a given object "Hey, what's your type?". Exactly that is high on my wishlist.
_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users