3 ms·
Sounds a bit like perl but at a lower level ?
by bamboozled 2y ago
Sounds a bit like perl but at a lower level ?
- high_priest 2y agoSounds a bit like JavaScript, but at a tower level?
- TingPing 2y agoI wouldn’t compare them, C is very simple.
- codr7 2y agoYes, but there are similarities, it has the same hacker mind set imo.
- ThinkBeat 2y agoYou can certainly do entirely absurd things in Perl. But it is a lot easier / safer work with. You get / can get a wealth of information when you the wrong thing in Perl. With C segmentation fault is not always easy to pinpoint. However the tooling for C, with sone if the IDEs out there you can set breakpoints/ walk through the code in a debugger, spot more errors during compile time. There is a debugger included with Perk but after trying to use it a few times I have given up on it. Give me C and Visual Studio when I need debugging. On the positive side, shooting yourself in the foot with C is a common occurrence. I have never had a segmentation fault in Perl. Nor have I had any problems managing the memory, the garbage collector appears to work well. (at least for my needs)
- TinkersW 2y agoEh Segfaults are like the easiest error to debug, they almost always tell you exactly where the problem is.
- relistan 2y agoExcept when they don’t. I’m debugging something right now that runs fine under debugging conditions and crashes with a segfault in real life. It’s not randomized memory (messed with that), it’s likely some race where the timing is changed by the debugger.
- bamboozled 2y agoruns fine under debugging conditions and crashes with a segfault in real life There's your clue right there...
- relistan 2y agoYes. Did you read what I wrote?
- randomNumber7 2y agoAdressSanitizer is an absolute gamechanger and should amost always spare you the effort of the nightmare debugging of undefined behaviour.