Supplying Flag to utils.SendMessage

[Dragomir-Ivanov]

Hi there,
Is there any reason why we can't suppli Flag(DONTWAIT) to utils.SendMessage functions. If there is no particular reson, perhaps I can supply a pull request.

Thanks,
Dragomir

[pebbe]

Never thought about using DONTWAIT on this function.

One practical reason is that one of the flags, SENDMORE, is already set or unset by the function internally. An other reason is that you can't add an argument after an argument with three dots. (Or can you?)

I could add a function SendMessageDontwait or SendMessageDontWait. What would be the best name?

[pebbe]

Done.

[Dragomir-Ivanov]

Technically, SendMessage accepts interface{} arguments, so it can be easy to check if the last one is of type zmq3.Flag. This way it will backward compatible and ideomatic.
Thanks :)

[pebbe]

But what if the user wants to send a flag as the last part of the message?

[Dragomir-Ivanov]

Okay you are right, but I find it unlikely someone will need to send zmq3.Flag as a payload. That way as you did it today is fine, though. Thank you.

[Dragomir-Ivanov]

Also I see that EAGAIN = Errno(C.EAGAIN) is missing from zmq3 (errors.go). Can you add it too. Thanks.

[pebbe]

EAGAIN is a standard error and available in package syscall.

For usage, see: http://godoc.org/github.com/pebbe/zmq3#AsErrno