3 ms·
What you say has nothing to do with languages and it precedes 80s; Watcom, VC++ etc. comes with a debugger because the proprietary system they run on doesn't ha
by tagrun 8y ago
What you say has nothing to do with languages and it precedes 80s; Watcom, VC++ etc. comes with a debugger because the proprietary system they run on doesn't have one. GNU/Linux always had gdb.
So if you want me to spell it out, here you go: it's bizarre to expect a debugger from modern compiled languages which have been FOSS from the beginning.
- pjmlp 8y agoThat statement fails on the face of mainframes and commercial UNIX environments, which also have platform debuggers. Also fails regarding other FOSS languages like Python, which have had a debugger since ever.
- tagrun 8y agoWhat fails? Some commercial C/C++ compiler producers invest into a debugger typically because some of their customers use it on a platform without a good built-in debugger. Yes, some systems had debuggers. The point is, some didn't. I said compiled language, which Python isn't. Yes, gdb won't help you debugging scripting/VM languages. Anyway, this is getting off topic, as we're talking about the alleged lack for debuggers for Go binaries for today's Go users, and neither of the things you mentioned are relevant. In my experience, nitpicking rarely leads to anything fruitful.
- pjmlp 8y agoThose some commercial producers as you put it, have invested in debuggers for BASIC, Pascal, Modula-2, PL/S, PL/8, NEWP, C, C++ and Ada for IBM/360, VAX/VMS, IBM 400, Solaris, Aix, HP-UX, Tru64, Irix, by IBM, Unisys, DEC, Compaq, SGI and HP themselves. And if I have to mention a FOSS compiled language instead of Python, with debugger support out of the box, then Oberon, Modula-2, FreeBasic, Gambas and FreePascal come to mind.