I have been trying to route OSC messages from TouchOSC using only Vanilla objects. One message for example (after [oscparse] is:
list 4 multitoggle 35 0

[listen "port#"]
I
[netreceive -u -b]
I
[oscparse]
I
[list trim]
I
[route 4] This is the tab number in TouchOSC

[route 4] is blocking any data from passing through to [print], but I figured out that if I type [route \4] the \ character disappears and it routes the data perfectly. I am glad that I got it to work, but don't understand why it is now working. Does anyone have info on this issue?

Thanks in advance.
I am running PD 0.52.2 on Mac OS

@CalBassist Does it still work if you save the patch and then reopen it? I've been burned by that several times before. Backslash is an escape character that doesn't seem to work consistently in Pd. My theory about why it works temporarily for you is that in Pd's implementation of OSC, numbers in the path are encoded as symbols, not floats. Escaping the number in the route object makes it look like a symbol temporarily. If I'm right, then this recent topic will be useful to you: https://forum.pdpatchrepo.info/topic/13956/parse-a-symbol-with

@jameslo Thanks, I will check that other thread out. You're correct that the backslash doesn't work after saving and reopening. I just figured that one out.

@CalBassist The workaround that I was taught was:

[oscparse]
|
[fudiformat]
|
[fudiparse]
|
[list trim]

... and then numbers in the command path will be true floats.

hjh