21–30 of 36 posts
I hope it replaces the notoriously hard to use gdb. I actually like doing things on the commandline and am used to using minimalistic tools like vim, but gdb's obscure commandline behavior makes it very hard for me to use it for any real project.
Earlier quoted context omitted.
Sounds like 'better', being built around a set of libraries first, with the ability to write plugins/extension in a reasonable language like Python. Most software written originally 20 years ago is going to seem crusty, and have issues in a field as young as computer science -- there are just better ideas and practices these days compared to when GDB was first started, not even considering licensing issues. Compare t…
Yes -- antirez who wrote Redis wrote linenoise, a replacement of the 20k lines of the old GNU readline in about 400 lines of C for only the 99.99% of users who are on VT100 terminals. http://github.com/antirez/linenoise
readline is "bloated" because it actually does something.
Earlier quoted context omitted.
Hum, I'd rather wait and see first. What about the truckloads of tools built around gdb (ddd, etc)? And why this should be any better, because it comes from Apple?
Apple employs a few (more than 1?) LLVM people, but it's hardly an Apple project by any means. LLVM is a substantial and fantastic project. At the basis, it's a compiler backend in-a-box. Additional projects, like clang and this, are providing a modern compiler platform for us, finally. gcc & friends have made great advances, relative to other compilers, but they all do suck. It's been 12 years and I still can't use…
They employ around two dozen LLVM developers, comprising half to two-thirds of the regular committers.
Earlier quoted context omitted.
Apple employs a few (more than 1?) LLVM people, but it's hardly an Apple project by any means. LLVM is a substantial and fantastic project. At the basis, it's a compiler backend in-a-box. Additional projects, like clang and this, are providing a modern compiler platform for us, finally. gcc & friends have made great advances, relative to other compilers, but they all do suck. It's been 12 years and I still can't use…
> Apple employs a few (more than 1?) LLVM people, but it's hardly an Apple project by any means. They employ around two dozen LLVM developers, comprising half to two-thirds of the regular committers.
Earlier quoted context omitted.
Hum, I'd rather wait and see first. What about the truckloads of tools built around gdb (ddd, etc)? And why this should be any better, because it comes from Apple?
Apple employs a few (more than 1?) LLVM people, but it's hardly an Apple project by any means. LLVM is a substantial and fantastic project. At the basis, it's a compiler backend in-a-box. Additional projects, like clang and this, are providing a modern compiler platform for us, finally. gcc & friends have made great advances, relative to other compilers, but they all do suck. It's been 12 years and I still can't use…
I hope it replaces the notoriously hard to use gdb. I actually like doing things on the commandline and am used to using minimalistic tools like vim, but gdb's obscure commandline behavior makes it very hard for me to use it for any real project.
"step" to step, "backtrace" to get a backtrace, ...? Yeah, that's confusing.
I hope it replaces the notoriously hard to use gdb. I actually like doing things on the commandline and am used to using minimalistic tools like vim, but gdb's obscure commandline behavior makes it very hard for me to use it for any real project.
"step" to step, "backtrace" to get a backtrace, ...? Yeah, that's confusing.
Earlier quoted context omitted.
Well, my company only works on gpl stuff and doesn't suffer any inconvenience from that. So I call bluff.
You're saying that being able to statically link a library into a commercial app has no business value to anybody because you are fortunate enough to have found a niche where you didn't need to. Your personal experience is enviable, but I don't see how it speaks to the general case.