Kas,

(This conversation is faster that I can keep up with!)

No, not a type: Keyword, more likely a type: Class.  Or, it may be easier to deal with strings, or arrays of string.  I thought that strings, being mutable, might be dangerous.  I think that we could get more specific errors if we had this all built into the language.  

Mike



2010/11/9 Kassen <signal.automatique@gmail.com>
Mike;
 
However, if the reserved word-- SinOsc --could be made equivalent to what was returned from .typeOf() or .className(), then it would be totally great.


Are you proposing a new type representing "keyword"? I don't think that would fly in the long term, unless we could add to the keywords. I still want this to -one day- fly:

class Distortion extends UGen
  {
  fun float tick() { .....etc...}
  }


Furthermore there are more object types than UGens; so far we only discussed UGens but we need a general solution that will be able to deal with a array containing -say- objects of type "note" and type "melody" or "loop" and whatever. Without needing to implement what would amount to a custom type system.

Yours,
Kas.

_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users




--
http://michaelclemow.com
http://semiotech.org