What are you listening to? [CONTENTLESS][MUSIC] (599)

126 Name: (*゚ー゚) : 1993-09-9149 20:02

>>120
By idiots who never actually read the C spec, of all the things that are actually harmful: uninitialized arrays, old string functions relying on null term, preprocessed shit for platform specificity; goto is not even close, itfs how the compiler code is going to work anyway. Hell the branch fond instructions that come from an if, for, or while are more harmful given specexec bugs. Goto is harmful if you donft understand the scope of your code, but so is ever actually using code you donft get the scope of.

127 Name: (*゚ー゚) : 1993-09-9150 20:35

>>126
I don't consider Dijkstra an idiot! Bit vociferous tho. Of course, one is not a genius for parroting an opinionated fellow.

But considering what passed for programming in 1968, it was hardly unjustified to very often say "hang on, WTF are you actually trying to do here?" every time you manually GOTO'd (dmr: 'Bob Morris asked, almost conversationally, "what are the arguments to ld?" Someone told him.'), not unlike I ask myself every time I copy-paste code from SO like the nubcake I am.

The second edition of "The Elements of Programming Style" (1978) makes no less than nine mentions of avoiding GOTO and labels. We can surmise it was still a thing breaking code in the 70s.

Not so today, we have much nicer programming languages (C is one of them, this is how old 1968 is) and are still perfectly capable of producing absolute shit in very different ways, but at least in ways that don't wreck up the place like manually placed GOTOs were doing rather often, even unto newbies retyping typo'd BASIC code from a magazine. Today, a C programmer using "goto" probably knows why they've resorted to it (and there's a strong chance the reason is a nested for that can't be renegotiated).

129 Name: (*゚ー゚) : 1993-09-9156 16:23

>>127
Most modern C gotos I've typed are to handle LLVM/clangfs constant fucking terrible forwarding decisions about noops. Usually this gotofs label is on the next line but this forces it to put the variables in the register before a print or math operation rather than dumping uninitialized garbage out of variables I had already been using in a for loop or some such. Somehow the longer I have been writing code the worse the bleeding edge gets.

Name: Link:
Leave these fields empty (spam trap):
More options...
Verification: