xazax.hun added a comment. Thank you for pointing this out. I think it would be great to be forward compatible. Right now one could use a heuristic such as for every hash the key has the "hash" string in its name. This information might not be sufficient, however, since it would be great to have some kind of ordering between the generated hashes, so a tool could choose the latest (and possibly greatest) one.
In http://reviews.llvm.org/D10305#286113, @seaneveson wrote: > To resolve the forwards compatibility issues, what are peoples opinions on: > > - Having a consistent name with an incrementing number (i.e. issue_hash_1)? > - Adding an ordered list of all the hash names to the plist file? A third alternative would be to have both semantic names (containing hash) and a number suffix which indicates the ordering. http://reviews.llvm.org/D10305 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
