Enhancement proposal: Addition of blocks for storing/reading received bursts to/from a file about gr-gsm

[romankh]

I haven't look very deep into gnuradio, but as far as I have seen pmt support serialization, so maybe we can just serialize the bursts and write them to the output file, and vice versa

[ptrkrysik]

This would be great. I was looking (maybe not very carefully) for a gnuradio block that does that but I didn't find any. If pmt supports serialization - there should be such block in gnuradio definitely.

[romankh]

I also just had a brief research, saw it in some pmt documentation.
Will try it out, then give you feedback

[romankh]

Serialization of pmt isn't a big deal, however i am not sure if it would be possible to have a sync_block have pmt message port in? Also, the Gnuradio BlocksCodingGuide says:

The sync block allows users to write blocks that consume and produce an equal number of items per port. A sync block may have any number of inputs or outputs. When a sync block has zero inputs, its called a source. When a sync block has zero outputs, its called a sink.

So, do we have any drawbacks if we just stay with gr::block in this case ?

[ptrkrysik]

Gnuradio takes care only of sample inputs and outputs to be synchronous in case of gr::sync_block. So gr::sync_block in case of message only blocks is no different than gr::block.

[ptrkrysik]

I think we can close this issue. The blocks implemented by you @romankh can be probably used for writing/reading any pmt objects.