[chuck-users] determining the type of an Object in code

[mike clemow]

A proposal:

This is great stuff, actually.  I'm really excited about the prospect
of putting together a really great List/Collection/Array class lib so
that we no longer have to look on in envy of SuperCollider's arrays
(just speaking from experience here ;-).

I'm totally willing to re-work my current code, which abstracts a
pattern of grain definitions for granular synthesis, to use or extend
a more abstract superclass of objects in an array.  I have time to
work on this (and get course credit for it, happily).

So, there's Michael's List, ListArray, etc classes and we also have
heard from Dan, who's working on something similar.  I'm wondering if
we can pool our efforts and make something really useful and complete.

Is there any interest in this?  If yes, how should we go about setting this up?

-Mike

On Mon, Sep 8, 2008 at 1:57 AM, Kassen <signal.automatique at gmail.com> wrote:
> 2008/9/7 Michael Heuer <heuermh at gmail.com>
>>
>> Hello Kas,
>>
>> ChucK has a cast operator, so you should be able to cast the result of
>> List.get(int), Iterator.next(), or the object parameter in a
>> forEach(UnaryPredicate) to what you expect the Object to be.  This
>> works:
>
> Wow! Great stuff!
>
> Thanks a lot for taking the time to figure this out and share.
>
> Kas.
>
>
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
>



-- 
http://semiotech.org
http://semiotech.org/michael