[sc-users] top five sclang pet peeves

[stefaan.himpe@xxxxxxxxx]

Sclang has a lot of incredibly good stuff to offer but sometimes it makes me
curse. Without wanting to sound too negative, here are my top 5 pet peeves
with sclang in supercollider.

Feel free to add your own, or bash mine (or ignore the post altogether) :)

1. Order of mathematics operations. I understand it's an OO thing, but I
have shot myself in the foot too many times with this already. For a
language that is somewhat math-centric to adopt "alternative conventions" is
rather evil. [Read: apparently it's hard to unlearn old habits]. 
2. Having to declare all variables at the beginning of a function. It works
miracles for unreadability and breaking the flow.
3. The lack of an Sclang debugger - breakpoints, watch, ... those kinds of
things. Debugging code based on postln is entirely possible, but can be
frustrating, especially in combination with point 2.
4. Calling add on an array returns a new array instead of adding to the
existing one. I understand it has its advantages for chaining operations
etc. This, admittedly, is mostly a matter of me having to get used to the
conventions again.
5. No number five! I told you I'd keep it positive :D




--
Sent from: http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/SuperCollider-Users-New-Use-this-f2676391.html

_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/