3 ms·
One issue worth pointing out is that this slots nicely into the various "Why should we have to learn C?" discussions that pop up here from time to time. This i
by ajross 18y ago
One issue worth pointing out is that this slots nicely into the various "Why should we have to learn C?" discussions that pop up here from time to time.
This is why. Eventually, something dumb will happen inside your tools, and you'll need to figure it out. Blind faith in any of the software you rely on is bad, you need to know how it works. And to first approximation, all the software you rely on is written in C.
- etal 18y agoWhich, in turn, relies on gcc (usually). Turtles all the way down...
- kingkongrevenge 18y agoI don't disagree but diagnosing this particular problem didn't require knowing any C, just the perl profiler and another perl build.
- ajross 18y agoOnly if by "diagnosing" you mean "lucking out and finding a pre-existing bugzilla entry on the problem". Someone earlier had to identify the problem and crawl through the RH patch sets looking for it. The author, who doesn't want to think beyond perl, was stuck without this. Not everyone is so lucky.
- kingkongrevenge 18y agoUh, no. Diving in to C was unnecessary to solve this problem any way you slice it. In fact, it would have been the most inefficient way to figure out that another perl build was needed.