Support for binary data defined with the '!!binary' YAML tag #175

Activity

1. tlsa commented on Nov 16, 2021

   

   tlsa

   on Nov 16, 2021

   Owner

   More actions

   That's a good idea, I could make a CYAML_BINARY type that does that.

   At the moment, it would load as a string, and you would need to base64 decode manually.

   I'll have a bit more of a think about it and get back to you. I want to avoid breaking the ABI if I can.
2. tlsa commented on Nov 16, 2021

   

   tlsa

   on Nov 16, 2021

   Owner

   More actions

   Once we have CYAML_BINARY, the YAML !!binary tag becomes redundant.

   It would be simple to implement CYAML_BINARY in the same way as CYAML_SEQUENCE is implemented at the moment. However, CYAML_SEQUENCE has the limitation that you can't have a CYAML_SEQUENCE directly inside a CYAML_SEQUENCE. The same restriction would apply here, so a CYAML_BINARY would not be allowed directly inside a CYAML_SEQUENCE.

   That means the following would not be possible:

   - !!binary "DEADBEEF"
   - !!binary "CAFEF00D"

   It would to be a sequence of mappings containing the binary data, for example:

   - data: !!binary "DEADBEEF"
   - data: !!binary "CAFEF00D"

   This is because the mapping allows a structure to be used, which allows the data length to be stored in a structure.

   So for an array of binaries, the client data structure would need to be something like:

   struct binary {
   	uint8_t data;
   	size_t len;
   };
   
   struct my_prog_data {
   	struct binary *binary;
   	size_t binary_count;
   };
3. tlsa

   added this to the Version 2 milestone on May 29, 2023
4. tlsa commented on Nov 14, 2026

   

   tlsa

   on Nov 14, 2026

   Owner

   More actions

   Done in #237.
5. tlsa

   closed this as completedon Nov 14, 2026