From: Nando D. <na...@de...> - 2005-09-08 22:56:48
|
Michael, M> again, this is information for us, that the user would most probably M> never see. See my previous posting. And as I wrote, the name of the M> method would of course better than an error number, for locating the M> cause of the problem. I think everyone agrees that exceptions may cover both bugs in the product (a database should be selected but it's not) and run time errors (like a "file not found" error). So, there's room for both a user-understandable message and a "details" part (the context Michael is talking about, basically) that the user should generally ignore, or only see on request, or be enabled only in debug builds, whatever. Personally I'd prefer all info to be available in the release build, since nobody ever really uses debug builds, and perhaps we can create a special dialog to display the two parts of the exception separately. About keeping things in sync: if we content ourselves with file name and line number, perhaps we can use __FILE__ and __LINE__ (although I'm not sure about the former in Unicode builds). Ciao -- Nando Dessena http://www.flamerobin.org |