News for hackers. Stuff that matters.
Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by fluoridation on Wednesday April 20, 2022 @04:27PM (#31102550)
I don't agree at all. For example, some of the best debuggers I've used have been for C/++. As far as I understand it, even after years, debugging in Node.js still hasn't progressed beyond the level of printf() debugging.

Also, by their very nature, dynamic languages offer less information at development time about things such as types and function signatures, so very often IDEs can't even tell you the type associated with a name by hovering over it.

Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by mumphster on Wednesday April 20, 2022 @05:20PM (#31103165)
I think you understand wrong. https://nodejs.org/api/debugger.html Combined with chrome dev tools or an ide of your choice has been some of the best tooling I’ve used in any programming language
Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by winrid on Wednesday April 20, 2022 @08:34PM (#31104817)
Debugging in NodeJS is very easy and works in an IDE just like Java or C++. My IDE can tell me the types of things, hover over variables, and even provides a REPL where I can call functions while the debugger is paused to debug.
Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by jhgb on Wednesday April 20, 2022 @06:11PM (#31103734)
Common Lisp implementations allowed you to change your program's code while debugging decades ago. Microsoft added bare minimum of similar functionality like fifteen years ago or so, if I remember correctly. I'm not even sure they've caught up on class redefinition and instance upgrade at runtime yet, which has been supported in CL since the 1980s.
Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by fluoridation on Wednesday April 20, 2022 @07:54PM (#31104556)
>Common Lisp implementations allowed you to change your program's code while debugging decades ago. Microsoft added bare minimum of similar functionality like fifteen years ago or so, if I remember correctly.

Fair enough. I did say "some of the best debuggers I've used". I've never used Common Lisp. I have no idea what the debugging experience is like on it.

Incidentally, I don't find edit & continue to be a terribly useful feature.

>I'm not even sure they've caught up on class redefinition and instance upgrade at runtime yet, which has been supported in CL since the 1980s.

That has nothing to do with the tooling, though. C++ just doesn't support those features. You also say "caught up" as if committee members had been trying to add those features to C++ but just hadn't been able to. It's much more likely that there hasn't been enough (or any) interest to add them.

Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by jhgb on Wednesday April 20, 2022 @08:24PM (#31104744)
> That has nothing to do with the tooling, though. C++ just doesn't support those features.

In principle I don't see how language definition not supporting this would make this entirely impossible. It's just not possible to ask for such a running program transition to be requested from within the language, but with some modest restrictions on program behavior this might be possible to request from within the IDE. The restrictions I imagine to be similar to the restrictions that would enable C++ code to be subject to code-agnostic tracing GC, such as no user-defined XOR-linked lists.

Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by pjmlp on Thursday April 21, 2022 @01:19AM (#31106234)
Energize C++, not surprisingly out of Common Lisp shop.

Visual Age for C++ v4, a Smalltalk like experience.

Live++ used by Unreal.

Edit-and-Continue has been replaced by hot reload on VS.

Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by astrange on Wednesday April 20, 2022 @06:48PM (#31104064)
Apple platforms used to have that ("zero-link") and removed it quickly because nobody actually liked it. I think this and Lisp/Smalltalk's image model is actually mistaken.

It goes against the principle of "crash-only recovery" to try to recover from a bad state instead of being able to start over from the beginning.

Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by jhgb on Wednesday April 20, 2022 @07:17PM (#31104307)
Generally in CL you should be able to recover from a usable intermediate state and restart from there.
Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by astrange on Thursday April 21, 2022 @08:34PM (#31116882)
That encourages you to live off the intermediate image forever (like autogenerating code and then not maintaining the source for it), but if you miss some data corruption then you're stuck with it.
Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by jhgb on Friday April 22, 2022 @09:31AM (#31121333)
You already are autogenerating code in Lisp (using macros), but not without keeping the source for it, which still lives in the source files. If those files are not loadable into a clean image, you're doing something wrong (like CMUCL people find out a long time ago).