Hey, thanks for addressing the issue.

On Mon, 2015-11-16 at 15:25 -0500, Martin Peach wrote:
> So I updated packOSC in svn to detect reentrancy and post a message.

The message says:
error: packOSC: Use bundle to send multiple messages

I find this message a bit misleading as I'm not at all trying to create
a bundle. I'm simply creating an OSC packet that in returns triggers
another OSC packet to be generated. I expect [packOSC] to treat them
absolutely separately.

> It seems too complicated to allow it.

I see. It's not complicated at all on a patch level to make [packOSC]
allow reentrancy. See attached patch. I can live easily without it being
fixed in [packOSC].

And this is the _expected_ output from my previous patch (and it
actually _is_ the output of the currently attached patch with the
work-around):

FIRST: /i/am/reentrant 64
SECOND: now

> Here's a patch that does what I believe you want using the preferred
> method of bundles.

That's not quite what I want. I don't mean to create a bundle. For
certain reasons it's hard to avoid reentrancy in the framework I'm
working on, but buffering the output of [packOSC] as shown in the
attached patch works.

Roman

#N canvas 224 44 477 380 10;
#X declare -stdpath osc -stdpath mrpeach;
#X obj 17 180 unpackOSC;
#X msg 17 16 /trigger/osc/message now;
#X msg 44 258 /i/am/reentrant 64;
#X obj 17 202 routeOSC /trigger/osc/message;
#X obj 17 224 t a b;
#X obj 17 290 print SECOND;
#X obj 188 298 print FIRST;
#X obj 208 16 declare -stdpath osc -stdpath mrpeach;
#N canvas 0 44 379 233 packOSC 0;
#X obj 80 114 packOSC;
#X obj 17 79 t b a;
#X obj 17 144 list append;
#X obj 17 30 inlet;
#X obj 17 175 outlet;
#X connect 0 0 2 1;
#X connect 1 0 2 0;
#X connect 1 1 0 0;
#X connect 2 0 4 0;
#X connect 3 0 1 0;
#X restore 17 119 pd packOSC (reentrancy fixed);
#X connect 0 0 3 0;
#X connect 1 0 8 0;
#X connect 2 0 8 0;
#X connect 3 0 4 0;
#X connect 3 1 6 0;
#X connect 4 0 5 0;
#X connect 4 1 2 0;
#X connect 8 0 0 0;

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Reply via email to