rhdjebejdbd
Joined 2 years ago
Joined 2 years ago
Otherwise they're right, it's not the intersection that matters but just the total bits available
There is only a single printf written in the source code.
Source?
A source. I need a source.
Sorry, I mean I need a source that explicitly states your argument. This is just tangential to the discussion.
No, you can't make inferences and observations from the sources you've gathered. Any additional comments from you MUST be a subset of the information from the sources you've gathered.
You can't make normative statements from empirical evidence.
Do you have a degree in that field?
A college degree? In that field?
Then your arguments are invalid.
No, it doesn't matter how close those data points are correlated. Correlation does not equal causation.
Correlation does not equal causation.
CORRELATION. DOES. NOT. EQUAL. CAUSATION.
You still haven't provided me a valid source yet.
Nope, still haven't.
Maybe you think it's not a _good_ lubricant? But a lot of its use is to extract stuck things which requires a thin lubricant
Pointers and arrays are basically interchangeable in C, and you have to do that constantly in any large program. Even the blog post has a malloc in it.
Once you start passing around a pointer to the middle of the array all size info is lost.
Are you talking about -fsanitize=address? It's too slow to be used in production