add option in JUCE to allow forbidden characters in OSC addresses.

[benkuper]

I've been struggling with a lot of people and software designers who decided to prioritize "user-friendly" osc addresses (e.g. with spaces : /my super/address) against OSC specification compliance. Those are famous software in digital art, like MadMapper or Millumin.
The way OSC is handled in JUCE right now doesn't allow programmers to decide whether they want to allow those addresses, and it can be a blocker if you really need to be able to communicate with those not standard softwares.

The proposal is to add a module option (disabled by default), that bypasses the special chars check when enabled

[FigBug]

This would be very useful. TouchOSC illegal characters in it's default maps.

[benkuper]

Thank you for the very thorough explanation.
How do you suggest I should do that while still using the juce_osc module ? If the proposed solution means "deal with your own OSC implementation", then I don't find it very constructive..
If there is a "JUCE friendly" way to still use the juce_osc module but being able to receive and parse those adresses, then I would love to discuss how and propose a PR going this direction.

[benkuper]

I totally agree that stepping out of the standard is NOT a good idea and the real fix should be done on the other side.
But I don't have source code access to the [many] software that don't respect it, and my goal developing the software I build is to be as compliant as possible with all of them, still trying to "educate" people on respecting the standard.
I thought it would be a nice addition to JUCE to allow that in a simple way that proves working for all the cases I've encountered, but I guess this would need way more work to have something that you would be happy with, unfortunately I don't have that time :)
FYI, this one of the main projects I have had the need for that : https://benjamin.kuperberg.fr/chataigne

Cheers and thank you for taking the time to explain