Timeline for toString() in a model or view layer?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2017 at 5:46 | comment | added | Hakanai | Ah, that makes sense then. Those default toString() methods Java put in, I wonder why they thought that was better than, say, a dump of the fields and their values. :/ | |
| Jan 6, 2017 at 5:33 | comment | added | rolfl |
@Trejkaz - It may not be as clear as it should be, but when I say "I file bugs against code ... which throws exceptions where the exception has an Object.toString() in the message" I mean exceptions that have the raw output from toString() from the Object base class.... i.e. not an overridden toString(). e.g. It is a bug if an exception has things like Illegal characters in: my.class.Name@106d69c instead of Illegal characters in: "Joe Blogs!!"
|
|
| Jan 6, 2017 at 3:28 | comment | added | Hakanai | Exceptions should only be seen by the programmer too, so I'm curious as to why you would think toString() should not be used from those. | |
| Feb 7, 2014 at 15:38 | history | edited | rolfl | CC BY-SA 3.0 |
spelling
|
| Feb 7, 2014 at 13:29 | history | edited | rolfl | CC BY-SA 3.0 |
Found an additional reference for using toString for debugging.
|
| Nov 29, 2013 at 13:04 | vote | accept | radekEm | ||
| Nov 29, 2013 at 13:04 | comment | added | radekEm | Thanks! "But, in general, toString() Is a tool for the PROGRAMMER, not for the user" - this is exactly what I wanted to know. | |
| Nov 29, 2013 at 11:54 | history | edited | rolfl | CC BY-SA 3.0 |
link, typo
|
| Nov 29, 2013 at 11:33 | history | answered | rolfl | CC BY-SA 3.0 |