[chuck-users] is some_id runnig?

Spencer Salazar ssalazar at CS.Princeton.EDU
Tue Nov 28 19:12:10 EST 2006

Kassen, Atte,

I agree that these features would be good ideas.  (For the record  
size 0 arrays are legal/possible, and, predictably, doing anything  
other than .cap() will produce an array out-of-bounds exception.)

With regards to the wiki feature requests, let me say that you should  
definitely put feature requests on the wiki if you don't see them  
there already, in addition to mentioning them on the mailing list.   
For a developer thinking about new features it is a lot easier to  
look at the wiki page than to comb through the mailing list  
archives.  Id say its disorganization is just a natural consequence  
of an "unmoderated" wiki; it is still fairly easy to read through  
despite this disorganization.

So if you feel inclined please do add these and the file i/o /object  
serialization/etc. feature requests up to the wiki, along with any  
other ideas.


On Nov 28, 2006, at 3:59 PM, Kassen wrote:

> I think it would generally be a good idea to make the results of  
> commands like --status and --probe accessible from within ChucK in  
> the future, maybe with extra information on what a shred's partents  
> and childeren are (if any) and so on.
> Maybe something like a array returned by a function (something like  
> "machine.shredList()" ?)that would list the active ID's and  
> functions like "machine.childeren(shred-id)" that would return a  
> array of a shred's childeren by id, " machine.sporkTime(shred-id)"  
> and so on.
> The big question would be what to return if a shred has no  
> childeren, it should be possible to do something to all of a  
> shred's childeren provided it has any but I don't think zero length  
> arrays are legal so I'm not sure what condition we'd test on in  
> that case.
> Kas.
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

More information about the chuck-users mailing list