msgpack-d icon indicating copy to clipboard operation
msgpack-d copied to clipboard

Published 20 hours ago • verified publisher icon msgpack

Support new format specification

Open repeatedly opened this issue 10 years ago • 7 comments

See: https://github.com/msgpack/msgpack/blob/master/spec.md

Maybe, separating versions is needed for DUB. 0.9.x is for old specification. 1.x.x is for new specification.

repeatedly avatar Feb 06 '14 17:02 repeatedly

Do you have a timeline for adding support for the new spec? I'm looking at playing with Neovim's msgpack-rpc interface, but it requires spec v5 support.

jwhear avatar Jan 20 '15 04:01 jwhear

Ah, I see. I delayed the v5 spec support until someone want this because v4 spec is enough in D. Okay, I will try implement it in this weekend.

repeatedly avatar Jan 20 '15 05:01 repeatedly

I tried parsing some data from Neovim and got segfaults, so I reckon it's due to it using the newer spec. Are segfaults accepted behavior for spec-mismatch, or would you like me to open an issue with a reproduction case?

jwhear avatar Jan 20 '15 17:01 jwhear

would you like me to open an issue with a reproduction case?

Yes please. segfaults is unexpected behaviour. Attaching actual binary data is awesome.

repeatedly avatar Jan 21 '15 06:01 repeatedly

Opened #45

jwhear avatar Jan 21 '15 16:01 jwhear

I am I right in assuming that msgpack-d doesn't currently support the Ext type family? I'm using msgpack-rpc with an API and it works fine for many calls, but when the return value includes Ext objects, it gets stuck polling the underlying socket.

jwhear avatar Feb 05 '15 23:02 jwhear

@jwhear Yes. Currently, msgpack-d doesn't support Ext type because there is no Ext type users with msgpack-d. Hmm... time to support v5 spec.

repeatedly avatar Feb 15 '15 13:02 repeatedly