Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jibal
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
88 ms
·
1891.
▲
by
jibal
8y ago
"In C especially, static arrays are quite common as struct members and as static objects at file scope" Not among good programmers (unless the array is immutable).
1892.
▲
by
jibal
8y ago
He said "array type". There isn't one in C. "It's just that arrays become pointers when passed between functions" Oh, is that all? Did you read the article, or the comment you're responding to? They point
1893.
▲
by
jibal
8y ago
> You say strlen() but you probably mean "code has to iterate all the string elements". Yes, but that's much more expensive than a memcpy (of the two source strings) or just knowing the length (of the string in the target
1894.
▲
by
jibal
8y ago
" I don't see any way without either double-fat pointers, or terminating NUL." You don't seem to have followed the discussion or the paper. The array length is known; a slice is a "fat pointer", but not "d
1895.
▲
by
jibal
8y ago
"Interestingly, the idea of hashing over the bytes of a data structure would be possible in C++, but it is non-idiomatic" Because it's not conformant . Those possible C++ programs are broken.
1896.
▲
by
jibal
8y ago
"Except that "far less serious than predicted" is not the same as non-existent" Pure strawman. The statement was that program correctness is far less serious than predicted, not totally benign. "and that quote in no
1897.
▲
by
jibal
8y ago
"I am curious why you say cost-free." What's the cost? It's an optional feature. "Using std::vector/array/string::at would literally eliminate buffer overflows and yet programmers aren't generally usi
1898.
▲
by
jibal
8y ago
I think Walter gave a very good argument for why it's the biggest mistake, and no warning will help with the consequences that he pointed out. That C has UBE is not a mistake, it's fundamental to the language design, which allows
1899.
▲
by
jibal
12y ago
"It's funny, because there's actually a language just like that: Smalltalk." I don't see how that's "funny" or relevant, as there are many other things about Scala that Smalltalk isn't just lik
1900.
▲
by
jibal
12y ago
"he doesn't give any specific reasons why he created this fork" This is somewhat like asking why Richard Dawkins just assumes the Theory of Evolution without justification in his tweets. Googling Paul Phillips Scala brings
1901.
▲
by
jibal
16y ago
tu quoque fallacy -- the worst possible form of argument FOR something.
1902.
▲
by
jibal
16y ago
It's an interesting way to enforce K&R indentation style.
1903.
▲
by
jibal
16y ago
> I don't really follow what in your example shows "gross mishandling of whitespace". That truly speaks poorly of you. OTOH, the problem can easily be fixed by requiring a statement to contain at least one token.