| From | Sent On | Attachments |
|---|---|---|
| Mathieu Bouchard | Nov 20, 2005 10:57 am | |
| Miller Puckette | Dec 15, 2005 9:49 am | |
| Hans-Christoph Steiner | Dec 15, 2005 3:55 pm | |
| Frank Barknecht | Dec 16, 2005 12:47 am | |
| Hans-Christoph Steiner | Dec 16, 2005 9:05 am | |
| Mathieu Bouchard | Dec 17, 2005 6:15 am | |
| Mathieu Bouchard | Dec 17, 2005 6:32 am | |
| Mathieu Bouchard | Dec 17, 2005 6:52 am |
| Subject: | Re: [PD-dev] class_addmethod2 | |
|---|---|---|
| From: | Frank Barknecht (fb...@footils.org) | |
| Date: | Dec 16, 2005 12:47:39 am | |
| List: | at.iem.pd-dev | |
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
I have to say that I like the A_FLOAT, etc names better (you can probably guess why). Code should document itself. "pffsFFS" is easy to skim over while "A_POINTER, A_FLOAT, A_FLOAT, A_SYMBOL, A_DEFFLOAT, A_DEFFLOAT, A_DEFSYMBOL" is very clear. I won't miss the A_NULL though.
Maybe a "best of both worlds" approach could be used, that allows both long names and short aliases for methods, that accept veryveryverymany arguments and thus aren't readable with A_POINTER,... anyways.
I could think of using a field delimiter like ":" in the argument type string: "p:f:f:s" or "A_POINTER:A_FLOAT:A_FLOAT:A_SYMBOL" then could be allowed. And we would get rid of A_NULL in both cases.
Ciao
-- Frank Barknecht _ ______footils.org_ __goto10.org__





