A kernel message catalog

Posted Aug 8, 2008 20:10 UTC (Fri) by giraffedata (subscriber, #1954) [Link]

Of all the code changes that break the documentation, grammar and typo corrections will be an insignificant minority.

There's no need to do something fancy like a hash -- just use the literal format string as the identifier. It's already in the documentation code anyway.

Another idea, more searchable than actual text but less of a development PITA than a number: an alphanumeric message ID. Have the macro turn it into a name that would make the compilation fail if it isn't unique.