52North
Anonymous names in error messages
Anonymous names are passed to issuelogger when an error/warning occurs. Sometimes this is the result of a lower level operation that failed and that also causes an failure of some higher level action. Nothing wrong with it and it is handeld correctly. But the anonymous names are useless to outside. Blocking them is not correct in all cases. At the level were the log is created no additional info is available and because it is an error state it is doubtfull if the mastercatalog contains any info (yet) on the object.
If something goes wrong, it should be good practice to to tell (somewhere) what happened, where it happened and under what context the error occured.
Not that I could tell (so far) if c++ provides good tools for that (in Java there are stacktraces). However, there are ways to generate that kind of error messages. Not sure if that is the preferred way to go, but that is what I found on a quick google run.
I agree, that telling technical details is not very informative to the enduser in most cases, but at least an appropriate error message should indicate that something has went wrong (in the UI).
However, for developers detailed error context is essential so that in some (hopefully most) cases no debugging is needed (which saves a lot of time) to see what has gone wrong. This is particular true for developers using the kernel but do not know the details (which actually is a requirement that no detailed knowledge about the internals is neccessary, as far as I understood).
maybe not the full name of the _ANONYMOUS_XIDX object is important for the user, but at least it should be indicated, that an anonymous object caused or resulted from the ERROR/WARNING.
