froydnj

10 ms·

61.
by froydnj 16y ago
Disclaimer up-front: my day job is hacking on GCC and related GNU pieces of infrastructure, so that colors my opinions somewhat. I speak only for myself, not for my employer. My level of experience in both: I hacked a specialized LLVM inli
62.
by froydnj 16y ago
> I can't imagine how C++ standardization efforts could possibly correlate in any way with industry adoption. The two things are completely orthogonal. I don't think they're orthogonal: standardization efforts don't happen until you hav
63.
by froydnj 16y ago
Fair enough. Perhaps all the C++ effort is simply a dying gasp from the collective industry. In any event, we're talking to different sets of embedded vendors. The embedded vendors I talk to are still using C++ and so are their customers.
64.
by froydnj 16y ago
I don't buy that. Maybe it's true in the "reads Hacker News" monoculture (or the "comments on Hacker News" monoculture), but that sample is not representative of the wider programming world. Apple's not going to spend several million dolla
65.
by froydnj 16y ago
This is true; it's unfortunate that Stross is misinformed on this point. But it's also true that all the weaknesses of C are still present in C++. (I suppose std::string mitigates the char* damage in C somewhat, though I suspect there are
66.
by froydnj 16y ago
Sure you can. This is how user-level threading packages work if you don't have kernel support.
67.
by froydnj 16y ago
> C hardcodes assumptions about the stack that prevent certain low level optimizations. Would you please expand on this? I can't think of any assumptions C makes about the stack that C++ wouldn't make; neither can I think of low-level
68.
by froydnj 16y ago
Thanks for the information. Your microbenchmark appears to be alignment sensitive. With your assembly code on my machine (quad-core 2.66 Core2 Quad) running for 250 tests I get: test1 usecs: avg 1.16759e+06 stddev 13917.6 test2 usecs
69.
by froydnj 16y ago
A couple of points: - It's hard to reproduce the benchmarking results, as source code for the benchmarks is not provided. - The original bug report was for 32-bit code, not 64-bit code, as the post assumed throughout. - If you compile the c
70.
by froydnj 16y ago
Finding a dynamically scoped statically typed language would be quite a trick: dynamic scope doesn't seem to have caught on outside the Lisp community. (I remember reading academic papers (separately for C++ and Haskell) that tried to expl