good catch , now we know why it does what it does. The reason why I did
this is that there is an example method in OSCMessage that use this bad
syntax in the comment.
So it seems the Socket does send the message because Pharo does not perform
a check on the argument, the Socket fails obviously but it may send the
message to an unknown address. I think Supercollider watches for any kind
of messages on various addresses and ports. At least that is only
explanation I can think of.
Or maybe I used the address string method and I forgot to mention it.
Anyway thanks will keep this in mind.
On Wed, Nov 2, 2016 at 9:07 PM Henrik Sperre Johansen <
henrik.s.johan...@veloxit.no> wrote:
> I'm amazed that ever works, as (in general, maybe mac is special,) you need
> to specify the ipv4 address as a ByteArray, not a string.
>
> (OSCMessage for:{'/mixer.volume'. 1 . 0.2})sendTo: #[127 0 0 1] port: 57120
>
> Cheers,
> Henry
>
>
>
> --
> View this message in context:
> http://forum.world.st/UDP-Socket-primitive-failure-tp4920870p4921195.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
>
