I think that the "list", "float" and "symbol" selectors are somewhat obvious and should be types, not selectors. Those selectors bring some ankward constructs like that. For this (pd!) software, it might be too late, but for the next dataflow generation, it is not...
a 2007/6/19, IOhannes m zmoelnig <[EMAIL PROTECTED]>: > Frank Barknecht wrote: > >> > >> might be that my reasoning is not completely in-line with pd-vanilla > >> (compare the "send" message to [netsend]) > > > > At first I thought, changing [netsend] so that it behaves the same would > > be cool as well, however [netreceive] differentiates between "foo 1" > > and "list foo 1". Hm, ... > > true. > and there is almost[1] no way to prepend "send" to "list a b c" with > native objects...: the result will most likely be "send a b c" which > will become "a b c" after [netreceive] (actually after [netsend]) which > is not "list a b c". > > hmm, hmm... > > mfga.sdr > IOhannes > > > [1] of course it IS possible, but somehow awkward: > > | > [route list ] > | | > | [list prepend send] > | | > [list prepend send list] | > | | > +-------------------------+ > | > [list trim] > | > > _______________________________________________ > PD-dev mailing list > [email protected] > http://lists.puredata.info/listinfo/pd-dev > -- Alexandre Quessy http://alexandre.quessy.net http://www.puredata.info/Members/aalex _______________________________________________ PD-dev mailing list [email protected] http://lists.puredata.info/listinfo/pd-dev
