Comment #5 on issue 3019 by [email protected]: Need a better way to
stringify functions in error messages
http://code.google.com/p/v8/issues/detail?id=3019
Sorry I missed the notifications earlier. Just want to say this is
definitely a step in the right direction. My only concern is that 256
characters still seemed a bit too long to me. Most other error messages are
quite concise and can fit into a single line (so you can quickly scan it
and have a good idea of whats wrong).
In this case (TypeError: %1 has no method %0), if %1 (the function) is over
a hundred characters long, it will easily span over a few lines and be very
difficult to read. Worse, the other pieces of information – "has no
method", and the method name (arguably even more helpful in debugging this
issue) will be pushed very far to the end.
This is not ideal, because your error collection service might has some
limit on the length of the error message (and they should) and the chop off
anything after that, then you are left with "TypeError: Object
function(){ ......", which is not very helpful. Same thing when you get an
email alert for this error (length limit on subject line) or push
notification etc.
As for suggestions, first of all I think the limit should be way lower
(like 32). Secondly maybe we can improve the error message to put the
important stuff first, like "TypeError: No method %0 on %1".
What do you think?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
