destiny_socket_sendto() falsely returns value != -1

[Lotterleben]

This is by no means urgent, but I recently stumbled across that, if you forget to call sixlowpan_lowpan_init(), destiny_socket_sendto() still returns the length of the data you wanted to send, even though nothing is delivered over the air.
I created a small application to demonstrate this:
https://github.com/Lotterleben/RIOT/tree/msg_send_bug/examples/msg_send_test

[Lotterleben]

It seems that sixlowpan_mac_send_ieee802154_frame() of mac.c calls msg_send_receive(&mesg, &transceiver_rsp, transceiver_pid); without checking whether transceiver_pid was initialized. My naive idea to correct this would be to check if transceiver_pid == -1 in ipv6_sendto() and return -1 if this is the case. Does that make sense? If so, I'd open a corresponding PR.

[miri64]

I will open a pull request in the next few days, that will decouple the network stack from the transceiver layer and wil set it on the link layer defined in #460. When I'm at it, I probably can fix this bug on the way.

[Lotterleben]

Great, thank you!

[mehlis]

fixed in #644

[miri64]

As @OlegHahm states in various other issues: #644 is not merged yet

[miri64]

Now #644 is merged.