> We've talked for a while about needing better error messages, links, > more descriptions on the website, etc. How about we modify panic(), > fatal(), and warn() to hash the format string for the message and > print out a url with some portion of that hash.
This is a pretty cool idea. The only realistic alternative is to give error codes to the various functions. It's more work up front, but it means that we don't need to do anything if the actual message changes. I'm sure a little perl magic could assign error codes to all instances of these calls in the source tree. Of course, one would have to be careful not to duplicate the error codes. I'd probably lean towards Ali's proposal due to its simplicity, but I think we'd need to run ispell on all of the messages to make sure that they're ok and I think we also need to find out how many duplicates we have because the same message is in multiple places. One final thing, is there a way to have a default page pop up to explain that the error message has not yet been written about and to give instructions? Maybe URL rewriting can do that sort of thing too? Certainly if rewrite can run a snippet of python code or something else, it could. While you're at it, I created an info() that is just like warn(), there are probably things that should be converted so people don't keep wondering about them. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
