Browsing possible translations in Google Translate (where "union" refers to a labor union), the 4 letter word could be one of a few Slavic languages, or possibly Polish.
Once again, Boost comes to the rescue! Provide a couple of operators, and it fills in the other ones you may want. Very well thought out, as most Boost libraries are -- for example, NaNs mean floating point numbers can't necessarily be given a strict ordering, so they provide "partially_ordered" if you need that.
When it comes to efficiency, compilers are remarkably capable these days. I just ran a test with GCC 3.4.5. It optimized "a < b || a == b" to the exact same as it generated with "a <= b" (at -O1). Source code available on request, but just try it yourself.
The lesson here: never make assumptions as to what is most efficient until you actually compile and see what happens. Instead, give the programmer the tools to make the code readable and maintainable, and then fix inefficiencies as you find them. "Premature optimization is the root of all evil." (Donald Knuth)
But how do you know if NASA is supposed to be spoken as a word or spelled out? For the most part, this is determined by convention, but here's a rule of thumb:
1) Anything that forms an actual word is spoken as a word 2) 2-3 character acronyms are spelled out 3) 4+ character acronyms are spoken as a word
If you're creating long acronyms that can't be spoken as a word (HMMWV comes to mind), expect people to come up with a word that fits (Humvee).
I had to read many scripts in English class. An excruciating exercise, honestly (scripts aren't meant to be read, they're meant to be performed!).
Fact is, scripts are in themselves useful. Not to you or me, but to some crazy nuts out there it has entertainment value. I guess they just perform it in their head or something.
No, dude. You pay exactly as much as you're willing to pay, no more. If it's not worth $150 to go to a concert, don't go. The problem is that the Market is willing to pay $150. Don't blame the labels or the artists for charging what others are willing to pay.
And yes, changing what you eat is essential, too. The key, however, is not to "diet"... but instead to change your lifestyle. So, I now bike to work whenever possible and go on longer recreational rides on the weekend. 100 miles per week, give or take. Smaller portions, with a good balance of carbs, fat, and protein. Plenty of fruit, vegetables, and whole grain.
And, as long as I keep this up, and have no qualms about treating myself to periodic high-fat, high-sugar items.
This is a lifestyle I can continue indefinitely: it's fun, and I'm not starving myself. (Just need to figure something out for the winter... biking in the snow doesn't interest me all that much).
That bio-feedback sensor only works if people pay attention to it. Unfortunately, way too many people eat way too much to begin with, and have a nice energy reserve that would power that bicycle for many, many miles (1 lb of fat is 3500 calories, which translates to something like 50 to 100 miles, depending on your riding style).
For people who cycle to lose weight (like me), a bicycle is effectively a zero-emissions vehicle. For everyone else, it's the equivalent of riding a 700+ mpg vehicle that runs on fully-renewable biofuel. Even better if it's a recumbent with full fairings.
First off, [Citation Needed]. This is simply not true from my experience. I've done this many times with GCC and produced identical output (or so diff says). One caveat: make sure you start from a clean directory structure each time, because your Makefile might list dependencies in different orders for the linker if not everything is recompiled, and I think that can produce different result. But this is the build system presenting different input to the compiler, not the compiler itself producing different output. Please provide a citation to set me straight, if my experience does not cover some other situation.
However... why should we be relying on the compiler to produce identical output in the first place? Shouldn't we instead be fingerprinting the source code and shipping that alongside (or even inside) the binary? That fingerprint would be enough to verify that their binary matches a certain revision of the code, regardless of whatever magic the compiler might do. (For extra bonus points, include the compile arguments in the fingerprint!)
Who says it's "all lies"... that's not the claim coming from the article, at least. Just read the summary:
He clearly has over-inflated his position, he has over-inflated his access and he's even over-inflated what the actual technology of the programs would allow one to do.
Interpretation: he revealed secrets, but highly exaggerated some things along the way.
This especially applies if your company refuses to use anything under a GPL license. Most projects would be more than willing to negotiate a different license for a small fee (and maybe even provide a level of support). The small fee gives your boss the impression that the software actually has value, instead of being "free crap" (a phrase I've heard management use).
My argument is not that signed values should be used instead of unsigned. My argument is that unsigned values don't help, and you need to look elsewhere for a solution.
I find it fascinating that the financial industry can solve this, while the gaming industry seems to have so many issues. Part of it, I think, is that games allow much more flexibility in how money is used than you see in real life. Also, the fact that game money isn't real money means that mistakes aren't as important... but now that line is blurred a bit. Don't trust a gaming company with real money (shocker, I know).... these sorts of bugs are insanely common.
Your an idiot and shouldn't be let near anything more complicated then a stick. A small one.
Pardon me while I cry in the corner. "Your an idiot"... priceless.
The 'x' is the problem. If you just make it a primitive type, then all you did was move the problem elsewhere. All intermediate values need to have the same checks.
Mixing signed and unsigned values can result in unexpected behavior. Trust me, don't mix them if you can avoid it.
You get a bit of a larger upper range (2x more, not all that much really), while introducing a whole new set of problems at the bottom end (what if you underfow?).
Avoid unsigned unless there's a good reason to use it. There are definitely good reasons -- it's a pain that Java got rid of unsigned! -- but avoid in general. Don't just use unsigned if your values are never supposed to go negative. If you need larger range, go to a larger data type.
Integer underflow. Imagine a situation where a player has 100 gold and a bug in the code subtracts 101 gold for whatever reason. If you use a 32-bit unsigned integer, that player now has 4,294,967,295 gold. A 64-bit unsigned is even worse, of course.
A simple if statement would catch this as well, right? But think of how often you do addition and subtraction (and everything else) throughout your code! Do you put an if around each one? Can you handle the error situation in each case? How do you ensure that you found every addition and subtraction, including future changes?
A better solution is to make a Money class with well-defined operations, and throw an exception if you try to exceed the boundaries. Sounds easy... but it has to be flexible enough to handle all situations (the class has to be used for all intermediate values -- it's no good to resort to an int, where problems might come back) while still being robust. ("I know, I'll use a class!"... now you have two problems. "I know, I'll use exceptions!"... now you have three.)
This is not an easy problem to solve for non-trivial software, which is why bugs like this come up periodically.
It's the deviations from the Hero's Journey that make a story interesting. The human brain is very good at looking for patterns; once a pattern is learned, the subtle changes away from the pattern are what provides the interest. This is how we distinguish faces, and it's why all Asians look alike to a westerner (the base pattern is tuned to one facial style, but Asian faces introduce more than just subtle differences from that pattern, which really throws things off).
Instead of cutting out the double cheeseburgers, we just removed all the tomatoes and lettuce. You know, the only parts that have any nutritional value.
That's the point of the original comment in this thread, I believe.
Wikipedia says that Provo's population is 112,488. If you include surrounding communities it's 526,810 (but who knows how many of them would be reached). So, still not so good.
Slashdot Mirror
Browsing possible translations in Google Translate (where "union" refers to a labor union), the 4 letter word could be one of a few Slavic languages, or possibly Polish.
Once again, Boost comes to the rescue! Provide a couple of operators, and it fills in the other ones you may want. Very well thought out, as most Boost libraries are -- for example, NaNs mean floating point numbers can't necessarily be given a strict ordering, so they provide "partially_ordered" if you need that.
When it comes to efficiency, compilers are remarkably capable these days. I just ran a test with GCC 3.4.5. It optimized "a < b || a == b" to the exact same as it generated with "a <= b" (at -O1). Source code available on request, but just try it yourself.
The lesson here: never make assumptions as to what is most efficient until you actually compile and see what happens. Instead, give the programmer the tools to make the code readable and maintainable, and then fix inefficiencies as you find them. "Premature optimization is the root of all evil." (Donald Knuth)
But how do you know if NASA is supposed to be spoken as a word or spelled out? For the most part, this is determined by convention, but here's a rule of thumb:
1) Anything that forms an actual word is spoken as a word
2) 2-3 character acronyms are spelled out
3) 4+ character acronyms are spoken as a word
If you're creating long acronyms that can't be spoken as a word (HMMWV comes to mind), expect people to come up with a word that fits (Humvee).
I had to read many scripts in English class. An excruciating exercise, honestly (scripts aren't meant to be read, they're meant to be performed!).
Fact is, scripts are in themselves useful. Not to you or me, but to some crazy nuts out there it has entertainment value. I guess they just perform it in their head or something.
No, dude. You pay exactly as much as you're willing to pay, no more. If it's not worth $150 to go to a concert, don't go. The problem is that the Market is willing to pay $150. Don't blame the labels or the artists for charging what others are willing to pay.
Your "gag" is actually spot-on.
My hearing is fine, and I want subtitles, too.
The art of diction is lost on many actors. It's amazing how much more dialog is understandable when you know what they're supposed to be saying.
Add in loud special effects and noises in my home (kids, neighbor's A/C, etc), and it's nice to know what that word that you missed was.
I am a lawyer. I am not your lawyer. This isn't legal advice. Assume that I'm deliberately misleading you.
Assuming you're misleading me ... does that mean I really can make a derivative without violating the Les Mis copyright? Now I'm confused...
15 lbs so far, 25 to go.
And yes, changing what you eat is essential, too. The key, however, is not to "diet" ... but instead to change your lifestyle. So, I now bike to work whenever possible and go on longer recreational rides on the weekend. 100 miles per week, give or take. Smaller portions, with a good balance of carbs, fat, and protein. Plenty of fruit, vegetables, and whole grain.
And, as long as I keep this up, and have no qualms about treating myself to periodic high-fat, high-sugar items.
This is a lifestyle I can continue indefinitely: it's fun, and I'm not starving myself. (Just need to figure something out for the winter ... biking in the snow doesn't interest me all that much).
Proper source: http://xkcd.com/221/
But I'm guessing 90% of ./ already caught the XKCD reference.
That bio-feedback sensor only works if people pay attention to it. Unfortunately, way too many people eat way too much to begin with, and have a nice energy reserve that would power that bicycle for many, many miles (1 lb of fat is 3500 calories, which translates to something like 50 to 100 miles, depending on your riding style).
For people who cycle to lose weight (like me), a bicycle is effectively a zero-emissions vehicle. For everyone else, it's the equivalent of riding a 700+ mpg vehicle that runs on fully-renewable biofuel. Even better if it's a recumbent with full fairings.
Origin:
before 900; Middle English mot ( e ) meeting, assembly, Old English gemt; cognate with Old Norse mt, Dutch gemoet meeting. See meet1
Wow! I finally understand the term Entmoot. Thanks!
First off, [Citation Needed]. This is simply not true from my experience. I've done this many times with GCC and produced identical output (or so diff says). One caveat: make sure you start from a clean directory structure each time, because your Makefile might list dependencies in different orders for the linker if not everything is recompiled, and I think that can produce different result. But this is the build system presenting different input to the compiler, not the compiler itself producing different output. Please provide a citation to set me straight, if my experience does not cover some other situation.
However ... why should we be relying on the compiler to produce identical output in the first place? Shouldn't we instead be fingerprinting the source code and shipping that alongside (or even inside) the binary? That fingerprint would be enough to verify that their binary matches a certain revision of the code, regardless of whatever magic the compiler might do. (For extra bonus points, include the compile arguments in the fingerprint!)
Who says it's "all lies" ... that's not the claim coming from the article, at least. Just read the summary:
He clearly has over-inflated his position, he has over-inflated his access and he's even over-inflated what the actual technology of the programs would allow one to do.
Interpretation: he revealed secrets, but highly exaggerated some things along the way.
Don't turn this into a black-and-white strawman.
Discovering a new way of putting things together == patentable
Discovering something that already exists == not patentable
It doesn't matter if it's nature or prior art: if it already exists, is shouldn't be covered by a patent.
This especially applies if your company refuses to use anything under a GPL license. Most projects would be more than willing to negotiate a different license for a small fee (and maybe even provide a level of support). The small fee gives your boss the impression that the software actually has value, instead of being "free crap" (a phrase I've heard management use).
Everybody wins!
If the Answer is 42, then maybe you found the Question to Life, the Universe and Everything. Douglas Adams fans rejoice!
The shortest distance between coasts in the US is San Diego to Jacksonville. 2092 miles. 3367 km. 43.2 meters per person.
Meters, not centimeters.
So, either we have a units problem, or it's the wrong country.
Calm down! You missed the point entirely!
My argument is not that signed values should be used instead of unsigned. My argument is that unsigned values don't help, and you need to look elsewhere for a solution.
I find it fascinating that the financial industry can solve this, while the gaming industry seems to have so many issues. Part of it, I think, is that games allow much more flexibility in how money is used than you see in real life. Also, the fact that game money isn't real money means that mistakes aren't as important ... but now that line is blurred a bit. Don't trust a gaming company with real money (shocker, I know) .... these sorts of bugs are insanely common.
Your an idiot and shouldn't be let near anything more complicated then a stick. A small one.
Pardon me while I cry in the corner. "Your an idiot" ... priceless.
The 'x' is the problem. If you just make it a primitive type, then all you did was move the problem elsewhere. All intermediate values need to have the same checks.
Too bad you're an AC. This post is spot-on.
Mixing signed and unsigned values can result in unexpected behavior. Trust me, don't mix them if you can avoid it.
You get a bit of a larger upper range (2x more, not all that much really), while introducing a whole new set of problems at the bottom end (what if you underfow?).
Avoid unsigned unless there's a good reason to use it. There are definitely good reasons -- it's a pain that Java got rid of unsigned! -- but avoid in general. Don't just use unsigned if your values are never supposed to go negative. If you need larger range, go to a larger data type.
Integer underflow. Imagine a situation where a player has 100 gold and a bug in the code subtracts 101 gold for whatever reason. If you use a 32-bit unsigned integer, that player now has 4,294,967,295 gold. A 64-bit unsigned is even worse, of course.
A simple if statement would catch this as well, right? But think of how often you do addition and subtraction (and everything else) throughout your code! Do you put an if around each one? Can you handle the error situation in each case? How do you ensure that you found every addition and subtraction, including future changes?
A better solution is to make a Money class with well-defined operations, and throw an exception if you try to exceed the boundaries. Sounds easy ... but it has to be flexible enough to handle all situations (the class has to be used for all intermediate values -- it's no good to resort to an int, where problems might come back) while still being robust. ("I know, I'll use a class!" ... now you have two problems. "I know, I'll use exceptions!" ... now you have three.)
This is not an easy problem to solve for non-trivial software, which is why bugs like this come up periodically.
It's the deviations from the Hero's Journey that make a story interesting. The human brain is very good at looking for patterns; once a pattern is learned, the subtle changes away from the pattern are what provides the interest. This is how we distinguish faces, and it's why all Asians look alike to a westerner (the base pattern is tuned to one facial style, but Asian faces introduce more than just subtle differences from that pattern, which really throws things off).
Also interesting reading, a list of examples of the Hero's Journey: http://en.wikipedia.org/wiki/List_of_monomyths
Maybe the film will be nothing like the trailer, just like every other movie. I guy can hope, can't he?
Instead of cutting out the double cheeseburgers, we just removed all the tomatoes and lettuce. You know, the only parts that have any nutritional value.
That's the point of the original comment in this thread, I believe.
Wikipedia says that Provo's population is 112,488. If you include surrounding communities it's 526,810 (but who knows how many of them would be reached). So, still not so good.