On Sun, 18 Mar 2007, Luiz Fernando N. Capitulino wrote: > Other possibility is to let the caller do the job. > > I mean, if the information needed to print the error message (packfile > name and version in this example) is available to the caller, or the > caller can get it someway, then the caller could check which error > he got and build the message himself. Nah... The error details should be handled at the failure location. Any error code based mechanism is bound to get out of synch at some point, or people simply won't bother adding new codes for new error conditions but simply reuse an existing generic enough code instead. We already have this nice error() function. Right now it simply dumps the message to stderr but it could be made more sophisticated if needed. Nicolas - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html