[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] [RFC] PMT succession: experts' opinions on serial
From: |
Sylvain Munaut |
Subject: |
Re: [Discuss-gnuradio] [RFC] PMT succession: experts' opinions on serialization libs |
Date: |
Mon, 30 Sep 2019 08:37:14 +0200 |
Hi,
>> Tbh, I'd just assume that in all these formats, being tight-packing by
>> default, std::complex<float> can just be represented by the equivalent
>> of struct {float re; float im;} complex;.
I haven't delved into the code, but do you know if it handles properly
architecture differences between sender and receiver ?
Things like 32b long vs 64b long and little endian vs big endian ?
Because the message end up send across network, this matters, there
historically has been at least one instance of a bug because PMT was
not resilient to that when exchanging data between a x86_64 PC and an
E310 for instance.
Cheers,
Sylvain
- [Discuss-gnuradio] [RFC] PMT succession: experts' opinions on serialization libs, Marcus Müller, 2019/09/28
- Re: [Discuss-gnuradio] [RFC] PMT succession: experts' opinions on serialization libs, Nick Foster, 2019/09/28
- Re: [Discuss-gnuradio] [RFC] PMT succession: experts' opinions on serialization libs, Marcus Müller, 2019/09/29
- Re: [Discuss-gnuradio] [RFC] PMT succession: experts' opinions on serialization libs, West, Nathan, 2019/09/29
- Re: [Discuss-gnuradio] [RFC] PMT succession: experts' opinions on serialization libs, Marcus Müller, 2019/09/29
- Re: [Discuss-gnuradio] [RFC] PMT succession: experts' opinions on serialization libs, West, Nathan, 2019/09/29
- Re: [Discuss-gnuradio] [RFC] PMT succession: experts' opinions on serialization libs,
Sylvain Munaut <=
- Re: [Discuss-gnuradio] [RFC] PMT succession: experts' opinions on serialization libs, CEL, 2019/09/30
- Re: [Discuss-gnuradio] [RFC] PMT succession: experts' opinions on serialization libs, Sylvain Munaut, 2019/09/30