In any sane code, you'd have the open and close brackets anyways, so all this code does is trade a few '\n' characters for a few parentheses characters. I'd opt for the former still.
Along the same vane from the math world is how natural numbers (which can then be used to build the reals, etc) are represented using only empty sets. Pretty awesome.
Can someone explain to me how the first queue example's (using singly link lists) dequeue method gives the expected result? Isn't head->m_pNext always NULL, so the new head will always be NULL and tail will be set to NULL losing the rest of the queue?
Seems like you should need to traverse the list to dequeue.
Credit card companies are a good example of the this too. Since they're responsible for fraudulent charges, there's a huge incentive for them to detect them.
They are not financially responsible. If there's a chargeback, stolen credit card, etc they reverse the charge on the merchant. In other word the merchant pays for the items purchased with stolen credit cards. All the credit car companies need to do is keep theft low enough so that the perception on them is good. Make no mistake the crest card companies do NOT pay for items purchased with stolen credit cards, the merchants do.
This happens everywhere, not just in Silicon Valley. Maybe I'm missing it, but where does this article give evidence that this is the biggest in the US?
My home town has 20k people, and has winters with weeks of sustained below 0F temperature. Yet, there is a forested section behind a low budget grocery store where a 30-50 person homeless community exists perpetually. I know this is smaller than the 175 mentioned in the article, but its in a 20k person winter town in the middle of nowhere.
A similar issue was responsible for one of the V22 crashes ([1], page 4). In that case the gyro wires were hooked up backwards, instead of the unit installed backward. Both cases are good examples of small design details that make or break a project.
I thought the same, but as chance should have it I finally installed Ubuntu on my mpb yesterday. It went off without a hitch, and as far as I can tell everything works out of the box (wireless, dual monitors, sound, even all of the Mac function keys!).
The "I want to do something else!" button does nothing for me. I have many "MUST" todos and only 1 "WANT" while trying this button. The button just brings me to the same single "WANT" I have.
I should probably have been more clear about that. When you indicate that you want to do something else, it will only pick from your "WANT" items - so if you only have one, it will keep coming up with the same item.
This is actually intentional; I've noticed that I got tempted to move aside a fun project to get more 'work' stuff done. The idea of only giving you a "MUST" after finishing the current "WANT" is that you'll have to take a break from work, before you can start with it again.
Another reason for doing this is that it would be quite unfair to give you a 'work' item when you don't feel like the 'play' suggestion it's making and just want to relax with something else - it would defeat the point of the 'play' part, and would make you afraid of clicking "something else", because it might come up with a 'work' item. It's all part of the "balance between work and play" thing :)
I'll change around the sidebar text in a few minutes, to clarify on this.