Am Tue, 14 Jun 2011 17:49:57 +0200 (CEST)
schrieb Michael Matz
Hi,
On Sat, 11 Jun 2011, Stefan Seyfried wrote:
And no, GCC does not embed a spell checker.
Will it somewhen in the future?
I guess not, as the main goal of the g* tools (gcc, gdb, glibc...) seems to be "Make them deliberately hard to use".
So, in which way do you use (which excludes development of) glibc that you find hard? Really curious.
I sometimes need to cross-compile it. Not funny.
I find gdb to be the best command line driver debugger there is, so without a [TG]UI you can't get better (that includes Etnus, though it has some nice features, but the cmdline is worse).
Maybe my problems with gdb are actually that I'm not good enough at using it. It's a powerful tool, granted, so maybe it needs more powerful users ;) But valgrind is IMHO just a more "feel good" tool, but that might just be me :-)
As for gcc, well, I'm not sure a spell checker really improves usability. I think you would be one of the first to admit that the sometimes awkward suggestions of real spell checkers in Office suites are often less than helpful.
Actually, it was not the spell checking part that impressed me about clang, but the useful error messages. However, gcc 4.6 also seems getting better at that: seife@server:~/tmp> gcc -dumpversion 4.5 seife@server:~/tmp> cat test.c int main(int argc, char **argv) { intt foo = 0; return foo; } seife@server:~/tmp> gcc test.c test.c: In function ‘main’: test.c:3:2: error: ‘intt’ undeclared (first use in this function) test.c:3:2: note: each undeclared identifier is reported only once for each function it appears in test.c:3:7: error: expected ‘;’ before ‘foo’ test.c:5:9: error: ‘foo’ undeclared (first use in this function) seife@susi:/dev/shm> gcc -dumpversion 4.6 seife@susi:/dev/shm> gcc test.c test.c: In function ‘main’: test.c:3:2: error: unknown type name ‘intt’ So it is moving in the right direction :-) -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org