Stop using 'short' for line and allocation sizes (2013)
git.kernel.org
Stop using 'short' for line and allocation sizes (2013)
1–10 of 50 posts
Re: Stop using 'short' for line and allocation sizes (2013)
#2So has Linus learnt another editor, as threatened??
Re: Stop using 'short' for line and allocation sizes (2013)
#3Original Title, for Posterity:
"Linus has been polishing a turd for two years"
Re: Stop using 'short' for line and allocation sizes (2013)
#4It was astounding to me when I watched that talk and he mentioned this issue. Part of me still hopes he uses this same editor.
Re: Stop using 'short' for line and allocation sizes (2013)
#5[deleted]
Re: Stop using 'short' for line and allocation sizes (2013)
#6"32,767 characters in a line should be enough for anyone."
I guess there's one constant with humans and infrastructure - people will always find ways to hit its limits.
Re: Stop using 'short' for line and allocation sizes (2013)
#7"32,767 characters in a line should be enough for anyone." I guess there's one constant with humans and infrastructure - people will always find ways to hit its limits.
"And if you have a line that is longer than
2GB, you only have yourself to blame."
Typing in machine code programmes for the ZX81, and ZX Spectrum consisted of REM statements with 1000s of zeros, which then you had to poke the machine code from data statements. Converting magic numbers, to magic.
Re: Stop using 'short' for line and allocation sizes (2013)
#8And then: “Don't use 'char' for number of lines” (2014: https://git.kernel.org/cgit/editors/uemacs/uemacs.git/commit...)
Re: Stop using 'short' for line and allocation sizes (2013)
#9So has Linus learnt another editor, as threatened??
He had one commit to uemacs after that, in 2014 (with a similar objective). Either he gave up after that or that fixed all his problems so far...
Re: Stop using 'short' for line and allocation sizes (2013)
#10Original Title, for Posterity: "Linus has been polishing a turd for two years"
It's turds all the way down.