Improved error reporting when _sprintf is called before __INIT or create.
Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=1928
Reported by Johan H Sundström, IDA jhs@pike.ida.liu.se
As discussed in the infokom thread starting at 312400, the error reporting when an object's _sprintf method is called before proper initialization has occurred leaves little details about what really happened and where - "Sprintf: Wrong type for argument 2: expected string, got int.", and some reference to where in master.pike the sprintf to show the object was called, instead of the object itself is hard to decipher.
Any improvement at all in the error reporting would be warmly welcome. (And no, this ticket does not really address the core dump discussed in the thread, but rather how to get more info in similar situations.)