Oops.. the test patch is bogus. If [packOSC] wouldn't throw away the second message, the patch would trigger a stack overflow. Attached is a patch that wouldn't trigger any problems if [packOSC] would support reentrancy.
Roman On Thu, 2015-11-05 at 13:54 +0100, Roman Haefeli wrote: > Hi all > > I noticed that [packOSC] does not support reentrancy (check attached > patch). > > Many object classes _do_ support reentrancy. At the same time it seems > common in other environments not to support reentrancy. I wonder if this > is considered bug. If so, I'll file a bug report. > > Roman
#N canvas 224 44 450 300 10; #X declare -stdpath osc -stdpath mrpeach; #X obj 17 98 packOSC; #X obj 17 120 unpackOSC; #X msg 17 16 /trigger/osc/message now; #X msg 44 198 /i/am/reentrant 64; #X obj 17 142 routeOSC /trigger/osc/message; #X obj 17 164 t a b; #X obj 17 230 print SECOND; #X obj 188 238 print FIRST; #X obj 208 16 declare -stdpath osc -stdpath mrpeach; #X connect 0 0 1 0; #X connect 1 0 4 0; #X connect 2 0 0 0; #X connect 3 0 0 0; #X connect 4 0 5 0; #X connect 4 1 7 0; #X connect 5 0 6 0; #X connect 5 1 3 0;
signature.asc
Description: This is a digitally signed message part
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
