http://bugzilla.slf4j.org/show_bug.cgi?id=163 --- Comment #13 from Thomas Mueller <thomas.tom.mueller@gmail.com> 2009-12-15 16:14:22 ---
my proposal does not make SLF4J rely nor depend on features of a particular IDE.
Well, it does. It requires to use a template to solve the usability problem.
if there is tooling support
As I already wrote, I prefer to not rely on this tooling support. I don't want to be forced to use a specific feature of the IDE (templates). I want to use the most logical solution to the problem (copy & paste).
rethink "how" one works
Do you tell me that developers should not use copy & paste? I'm sure most developers use copy & paste as well. They don't bother creating a template. And even if you document it nicely, they wont. That doesn't mean it shouldn't be documented.
error-prone programming patterns
Copy & paste is 'usually' not error prone. It is only error prone because copy & paste doesn't do what I expect - in this case - and I don't get an error message or warning. And that's the problem. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.