If I might jump to conclusion, he meant that there was no difference between the two, in meaning. Thus, the difference is clearly not semantic. As such, he used the wrong term.
For the record, the right term would syntactic. Re-read the OP post.
This post was brought to you by Pedantis. Pedantis, the right solution to the wrong problems!
You shouldn't have to use the HTML encoding of those letters. Most browsers support them inlined now so what's the big deal about using UTF8 in your DB/comment system?
According the vgchartz, 20.35M and 14.89M as the writing of this message. Also, please note that the PS3 is currently outselling week after week the XBox, although TBH at this trend it's gonna take 3-4 years before they reach it. I don't think Sony is having financial problems, for those worried; the PSP is selling good and with a profit on each unit.
C++ often occurs imperceptible code (for example, constructors, destructors, temporary variables, copy-ctor,...) that can slow the final product. This can be circumvented, but in most case is not because the programmer is not experienced enough.
The case is, although I prefer C++ as a language, I'm well aware that people needs a hell of a lot more experience in C++ than in C to write code that is both faster and easier to maintain. Also, if readability by none-expert is an issue, C is always easier to understand. If you have a team of talented C++ developer, it's going to be 99.5% as fast as C, and will take less time to maintain and code new features. The level of expertise of such a team is an order of magnitude more than the same results in C, though.
What part of "motorized vehicle driven on public roads" did you miss?
Re:Boost epitomizes everything that is wrong with
on
Boost 1.36 Released
·
· Score: 2, Informative
I've given you two keywords (restrict, export) and two features (implicit functions, inlining) that aren't well implemented (okay, lets say different enough so that one code might not be compatible) across the mainstream compilers, but I'll tell you another one: template metaprogramming and typename.
I don't know about the state of VC2008 and Comeau since I've stopped working with them a while ago (working on OSX with intelc and g++), but I remember by my young self having a lot of difficulties building cross-compiler expression templates and dynamic type resolution libraries. I'm not talking export here, just using templates of templates to build expressions that should be inlined correctly at the end of the compiler pipeline. If it's compiled at all.
I won't find a real world code example, lets just say that when you enter the templates recursion, template operators and heavy template worlds, and you throw in some functors, binding and dynamic typeinfo (which are all standards, not some unsupported feature like export), what works on one compiler will choke the next one. I've had my share of "Internal Compiler Error". Those are nasty and almost impossible to resolve. And sometimes G++ just give up without an error code... oO
Saying that what works on one mainstream compiler should work on the other if you follow standard is the same as saying that coding POSIX guarantees you to work on all mainstream operating system. Theory is fine, practice showed us otherwise.
And boost came across these problems as well. Do you think the HEAVY use of macros and preprocessing is only there to render the code unreadable?:)
Re:Boost epitomizes everything that is wrong with
on
Boost 1.36 Released
·
· Score: 1
VC++, GCC, Intel, Comeau... That's just off the top of my head
Out of my head: the restrict and export keywords. If I remember correctly, only one of the compilers you mentioned really respect export, three respecs restrict, and they are errors for the others (left as an exercise to the reader). And let's talk a bit about inlining and implicit functions...
None of them are perfect, but they're close enough as makes no difference.
They do make a difference. They are not 100% compatible to the standard, and it means that code that would work on one compiler may not on the other. I've faced this in projects, and I'm sure the Boost guys are aware of it a lot (and use preprocessing to circumvent the differences).
We're talking mainstream here. Wanna go see what's going on on the lowest tiers of the market?
By the time you are working on the Linux kernel as a contributor, you'd have accumulated enough knowledge/experience to get employed at Microsoft. I think at that point, it's more a matter of ideology.
At Microsoft, working on the kernel pays as a fulltime job, while you still have to find a way to get money if you're just working on the Linux kernel as a hobby. And if you can get employed by some corp to get paid working on the Linux kernel, I'd think their employment standards would be comparable to MS's.
I don't care much about cut-and-paste, never really used it before. It's a feature I'm missing a bit, but the advantages of the whole thing outweighs the engineering bugs and missing features by much. If the only complain you have about the iPhone is cut-n-paste, you should revise your reviews.
On topic, I haven't had a single call drop since I bought it. Some slow down on 3G, but the phone reception is working good for me. Guess what? I love the "phont".;)
Slashdot Mirror
1000000+ UIDs, these days...
"The proton absorbs a photon and emits two morons, a lepton, a boson, and a boson's mate. Why did I ever take high-energy physics?"
Yeah, my family is just as screwed as this proton's....
If I might jump to conclusion, he meant that there was no difference between the two, in meaning. Thus, the difference is clearly not semantic. As such, he used the wrong term.
For the record, the right term would syntactic. Re-read the OP post.
This post was brought to you by Pedantis. Pedantis, the right solution to the wrong problems!
Whoosh
And why there are so much anonymous cowards talking about penis size. Just askin...
I thought he was talking about egos...
I learnt Sanskrit and it's sooo overrated.
You, sir, should go to Europe to look upon the real definition of slow bureaucracy. We are speedy-gonzalez-fast here compared to some cases.
Also, I know some American lawsuits that have been taken forever as well, this is not localized to Canada.
Do we at least know who the mother is??
You shouldn't have to use the HTML encoding of those letters. Most browsers support them inlined now so what's the big deal about using UTF8 in your DB/comment system?
According the vgchartz, 20.35M and 14.89M as the writing of this message. Also, please note that the PS3 is currently outselling week after week the XBox, although TBH at this trend it's gonna take 3-4 years before they reach it. I don't think Sony is having financial problems, for those worried; the PSP is selling good and with a profit on each unit.
No sir, he's X. Gotta love roman numerals.
Not on slashdot, for sure :)
Please. Stop. Just stop.
Blizz charges for transfering char. But it's possible.
I never signed anything.
C++ often occurs imperceptible code (for example, constructors, destructors, temporary variables, copy-ctor, ...) that can slow the final product. This can be circumvented, but in most case is not because the programmer is not experienced enough.
The case is, although I prefer C++ as a language, I'm well aware that people needs a hell of a lot more experience in C++ than in C to write code that is both faster and easier to maintain. Also, if readability by none-expert is an issue, C is always easier to understand. If you have a team of talented C++ developer, it's going to be 99.5% as fast as C, and will take less time to maintain and code new features. The level of expertise of such a team is an order of magnitude more than the same results in C, though.
What part of "motorized vehicle driven on public roads" did you miss?
I've given you two keywords (restrict, export) and two features (implicit functions, inlining) that aren't well implemented (okay, lets say different enough so that one code might not be compatible) across the mainstream compilers, but I'll tell you another one: template metaprogramming and typename.
I don't know about the state of VC2008 and Comeau since I've stopped working with them a while ago (working on OSX with intelc and g++), but I remember by my young self having a lot of difficulties building cross-compiler expression templates and dynamic type resolution libraries. I'm not talking export here, just using templates of templates to build expressions that should be inlined correctly at the end of the compiler pipeline. If it's compiled at all.
I won't find a real world code example, lets just say that when you enter the templates recursion, template operators and heavy template worlds, and you throw in some functors, binding and dynamic typeinfo (which are all standards, not some unsupported feature like export), what works on one compiler will choke the next one. I've had my share of "Internal Compiler Error". Those are nasty and almost impossible to resolve. And sometimes G++ just give up without an error code... oO
Saying that what works on one mainstream compiler should work on the other if you follow standard is the same as saying that coding POSIX guarantees you to work on all mainstream operating system. Theory is fine, practice showed us otherwise.
And boost came across these problems as well. Do you think the HEAVY use of macros and preprocessing is only there to render the code unreadable? :)
VC++, GCC, Intel, Comeau... That's just off the top of my head
Out of my head: the restrict and export keywords. If I remember correctly, only one of the compilers you mentioned really respect export, three respecs restrict, and they are errors for the others (left as an exercise to the reader). And let's talk a bit about inlining and implicit functions...
None of them are perfect, but they're close enough as makes no difference.
They do make a difference. They are not 100% compatible to the standard, and it means that code that would work on one compiler may not on the other. I've faced this in projects, and I'm sure the Boost guys are aware of it a lot (and use preprocessing to circumvent the differences).
We're talking mainstream here. Wanna go see what's going on on the lowest tiers of the market?
By the time you are working on the Linux kernel as a contributor, you'd have accumulated enough knowledge/experience to get employed at Microsoft. I think at that point, it's more a matter of ideology.
At Microsoft, working on the kernel pays as a fulltime job, while you still have to find a way to get money if you're just working on the Linux kernel as a hobby. And if you can get employed by some corp to get paid working on the Linux kernel, I'd think their employment standards would be comparable to MS's.
Yeah, sure. You blame the prostitutes? I blame society.
Aside of that, how've you been?
I don't care much about cut-and-paste, never really used it before. It's a feature I'm missing a bit, but the advantages of the whole thing outweighs the engineering bugs and missing features by much. If the only complain you have about the iPhone is cut-n-paste, you should revise your reviews.
On topic, I haven't had a single call drop since I bought it. Some slow down on 3G, but the phone reception is working good for me. Guess what? I love the "phont". ;)