Actually, reading this thread for me has shown me that one idea that I have been using is a lot more common that I had thought. The idea of naming the receives on an object with an "r" at the end (or whatever) to distinguish it from the send was something that I wasn't really sure if it was a "Pd Idiom" or not, and I really had no idea how to ask a question about it...
Mike
On Tue, Jul 29, 2008 at 1:25 PM, marius schebella < marius.schebella@gmail.com> wrote:
Hans-Christoph Steiner wrote:
On Jul 29, 2008, at 1:31 AM, Frank Barknecht wrote:
Hallo, Luke Iannini hat gesagt: // Luke Iannini wrote:
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 think, it would be important to first collect every possible style element in the wild and document what people are using in reality. That would be interesting. I'm not too much in favour of a style "guide" however. Let people be creative.
Nobody is talking about requirements. If you don't like style guides, don't use them. But it is really not useful to squelch other people's efforts, especially when you don't even have an intention of using this stuff.
I actually liked frank's idea to collect different people's ideas and compare them. maybe there is some common sense in all of them? marius.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list