On 11/25/2011 10:28 AM, Dean Michael Berris wrote:
When someone says that it's difficult to use, the response seems to be
to argue with them and tell them they're wrong. That's not solving the problem, it's making it worse.
When someone says it's difficult to use, it doesn't say anything useful. Difficult is relative -- difficult compared to what? Because it's a very relative thing (like whether something is ugly or beautiful) discussing anything that pertains to 'difficulty'.
What are the problems can be solved? Those that are demonstrably quantifiable. If the problem is there's 100KB of error messages generated by compiler A using library X, should it be a matter of the library being broken automatically or should it be that the compiler is broken? I'd wager if the compiler didn't barf 100KB of error messages for a seemingly "innocent" mistake done by the human in the equation, then maybe that human wouldn't be complaining regardless of whether library X was used or not.
I just want to be clear here: there are two tools involved, one is the library and the other is the compiler. Fixing the correct broken tool should be the solution. Any discussion on fixing the wrong "not broken" tool is moot.
Or somewhere in between the compiler and user (i.e. UI). See my other post: Re: TMP error messages I'd really like to pin this down. Regards, -- Joel de Guzman http://www.boostpro.com http://boost-spirit.com