Robert Graham 
BrendanEich
@ErrataRob Comment at 12:16 PM cites premature optimization for unoptimizing compilers (PCC) and old CPU arches. Root of much evil. @etrepum
The shockingly obsolete code of bash: http://blog.erratasec.com/2014/09/the-shockingly-bad-code-of-bash.html … (changed title: it's more 'obsolete' than 'bad')
-
-
- View other replies
-
@BrendanEich@etrepum by the mid 1980s, my compilers class taught optimizing as part of the standard thing you'd do in a compiler -
@ErrataRob Torktown work (SSA), Preston Briggs' thesis a bit later, and tools in use took a while into 90s catching up.@etrepum
-
-
-
@ErrataRob excellent writeup. I've been saying for a while that apps need to be completely rebuilt every so many years to avoid surprises -
@tbertling I don't think it's necessary to completely rebuild bash -- only that 30 years of technical debt needs to be repaid. - View other replies
-
Tweet unavailable
-
@Libertardian@tbertling "Don't fit what ain't broken" wars with "cleanup your technical debt"
-
-
-
@ErrataRob "The shockingly obsolete code of bash" -- dear everyone who is complaining: quit complaining and figure out what to do about it. - View other replies
-
@johnregehr The first step is to agree on what's wrong. It's be a big debate to come to agreement on whether "strcpy()" is wrong.
-
-
-
@ErrataRob Why is it "3 + string_length + char_index" in line 356? Isn't "char_index + 1 /* space */ + string_length + 1 /* '\0' */" enough? -
@stderrdk good point
-
-
@ErrataRob note that new (and hence hypothetical style-fixed) versions of bash use GPL3. That is not kosher everywhere -
@ErrataRob It's still damn useful. If you don't like the obsolescence, audit it and contribute bug reports.
Tom Bertling
John Regehr
stderr.dk
Ville M. Vainio
((Curious Reptile))
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.