Re: [PD] Basic send historical issue 32 bits / 64 bits

2022-12-20 Thread Roman Haefeli
On Tue, 2022-12-20 at 10:43 +0100, IOhannes m zmoelnig wrote: > On 12/20/22 08:10, Lucas Cordiviola wrote: > > hi, > > > > you should *not* convert the list to a symbol: > > totally. > [l2s] just adds a lot of overhead, for no benefit. The reason it used to work even with [l2s] is unrelated to 3

Re: [PD] Basic send historical issue 32 bits / 64 bits

2022-12-20 Thread IOhannes m zmoelnig
On 12/20/22 08:10, Lucas Cordiviola wrote: hi, you should *not* convert the list to a symbol: totally. [l2s] just adds a lot of overhead, for no benefit. you should send a list so that later [route] can do its job: [pack 0 0 ] | [list prepend send] | [netsend] that should read | [li

Re: [PD] Basic send historical issue 32 bits / 64 bits

2022-12-19 Thread Lucas Cordiviola
hi, you should *not* convert the list to a symbol: {l2s}    ->   (send $1> you should send a list so that later [route] can do its job: [pack 0 0 ] | [list prepend send] | [netsend] -- Mensaje telepatico asistido por maquinas. On 20/12/2022 03:00, Jean-Marie Adrien wrote: Hello list

[PD] Basic send historical issue 32 bits / 64 bits

2022-12-19 Thread Jean-Marie Adrien
Hello list Upgrading some old historical patches I wrote twenty five years ago (yeah, some of you were not born!) with having two instances of PD extended 32 bits communicating with each other, via {netsend} and {netreceive} objects. The need was to send from one instance two the other a messag