There are some amazing sets of abstractions being released recently, which has served to highlight the many extant styles of patching. I was wondering if there was interest in establishing a set of guidelines for patching in the vein of PEP 8 for Python; I've found that document to be very relaxing as it is a standardized approach to OCD. More seriously, it greatly helps when reading other people's code or collaborating. http://www.python.org/dev/peps/pep-0008/

I've begun to collect some of my practices to start things off.

I was hoping we could all lazy-vote the document together in this thread and I'll then compile it into a PdPedia/Pd.info document. So, feel free to object to or replace my propositions.

Style: * If giving $0 as an argument to an abstraction, it is always first in the argument list [1]

* * When possible, pass parent arguments in numeric order, like [child $0 $1 $2 other1 other2] etc. * Sends and Receives are written in camelCase, with "R" appended to complementary receives (e.g. in GUIs, $0mySlider for the send and $0mySliderR for the receive)

* When prepending $0 to a symbol, only add a "-" to separate it from another number, like [r $0-1stSend]. Otherwise the symbol should immediately follow, like [r $0mySend].

* When working with stereo, Left and Right pairs are written with Le and Ri appended (to distinguish them from an R denoting "receive", above)