[chuck-users] A modest proposal (caps).

Ge Wang gewang at CS.Princeton.EDU
Sat Aug 5 18:18:16 EDT 2006

Hi Kassen!

Perry and I have been considering this consistency issue from a while 
back.  Currently, all STK ugen's have uppercase convention.  Also, all 
the non-UGen classes, like Object, Event, HID, Midi*, OSC* all use the 
same.  In fact the base UGen class uses it.  So it would be more 
consistent for the likes of sinosc, gain, sawosc, fullrect, impulse,
etc. to also follow suit.

Perhaps the way to go for now is to provide uppercase convention for
the native chuck ugen's (SinOsc, Impulse, Gain etc), but also keep the 
lowercase versions (sinosc, impulse, others) for backward compatibility. 
It's extra stuff in the namespace for now, but overall that might make 
more sense.  Thoughts?


On Sun, 6 Aug 2006, Kassen wrote:

> On 8/5/06, Perry R Cook <prc at cs.princeton.edu> wrote:
>> Classes from STK (The Synthesis ToolKit in C++) obey
>> the original caps convention.  New classes that are
>> unique to ChucK area all lower case.
> Yes, I realised this, in fact it's nice to recognise bits from the book as
> ChucK ugens. However, for normal ChucK use there isn't that much difference
> between the two and where to cap and where not to seems fairly arbitrary
> from that perspective.
> Maybe it's just me being dyslexic again but every time the compiler
> complains I go "now what's wrong?" and have to remember this. To me it would
> seem sensible that if you go "TwoPole" then you also go "SawOsc". If I'm the
> only one who thinks this is odd/ confusing then I'll happily try to remember
> what bit comes from where but personally I'm in favour of languages being
> consistend and having as few exceptions as possible; natural languages are
> confusing enough as it is already.
> Just my perspective; nothing more.
> Kas.

More information about the chuck-users mailing list