On 2012-10-28 22:38, David Nadlinger wrote:
Do really think that your typical Java programmer is familiar with the
term »symbol« in the compiler/linker sense? Also, don't underestimate
the perceived scariness/ugliness of mangled names in linker error
messages. I'm pretty much fluent in reading D mangled names by now, but
most newcomers definitely aren't.
That, coupled with the absence of the typical source location
information (IDE integration!), is probably enough to make encountering
such errors a significantly more unpleasant experience for most people
than compiler errors.
Again, maybe not for you, maybe not for me, but I think it is clear that
this is a problem to some, so the discussion should not be about talking
the problem away, but rather about evaluating possible
solutions/mitigation strategies in terms of feasibility (e.g. name
demangling in linker output?).
I completely agree. I can handle the mangled symbols as well but it
would be much nicer with demangled symbols, source location and so on.
Just because I can read HTML I'm not surfing the web with "curl", I use
a GUI browser that renders the HTML. It's much nicer that way.
--
/Jacob Carlborg
