[rb-general] SOURCE_PREFIX_MAP format specification proposals

[Ximin Luo]

Daniel Shahaf:
> My opinion:
> 
> a) Avoid the characters 0x00 through 0x1F inclusive (note: this includes tab)
> 
> b) Avoid the character 0x7F (DEL)
> 
> This is to make things as portable as possible.  (Even through
> screenshots, printouts, contexts that don't permit control characters
> (like email subject lines), etc)
> 
> [..]
> 

Could you explain in some more detail what you mean by "portable" and what you think are important use-cases? A comparison table like I did for characters in the first email, would be very useful.

> 2) Like (1a) but escape any backslash and colon in the keys and values
> with a backslash; that is:
> 
> [..]
> 
> This format is fully general, printable non-whitespace ASCII only,
> round-trips through everything including dead trees and screenshot, and
> so on.  Yes, parsing this requires more code than just split(), which
> means the consumers' code is a little longer; but in return the
> producers' code is dead simple.  I think that'd be a good trade-off to
> make.
> 
> [..]
> 

If this would be similar to SOURCE_DATE_EPOCH, we would have more consumers to convince and they would also approach it more critically, than producers (most of whom already like reproducible builds and treat it with significant priority).

Anyway, I will play with your code samples in the meantime, thanks for those!

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git