https://d.puremagic.com/issues/show_bug.cgi?id=11714
--- Comment #7 from Joseph Rushton Wakeling <[email protected]> 2013-12-12 02:18:32 PST --- (In reply to comment #6) > With *a* reference to – I stripped out the articles trying to make the error > message as concise as possible, and missed that it would distort the meaning. Easier to use "with a reference to" and "with respect to" respectively, for the two different cases (just for future reference:-). What I'm really concerned about, though, is that to me that message is still pretty much incomprehensible about what it is that I actually did wrong. Even when clarified with instructions about what to do to resolve it (initialize to null or use static this) it's not obvious about what I got wrong or why it's wrong. If I understand the logic right, the result of "new MyClass" is not knowable at compile time --> hence, a compile time constant; but inferring the former meaning from the latter is not obvious unless one already knows. Rather than requiring the programmer's knowledge and understanding to comprehend the error message, we should aim to use the error message to _increase_ the programmer's knowledge and understanding. So, I want an error message that idiots like me can read and go, "Oh! THAT's why it's wrong," as well as understanding how to fix it. :-) -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
