> Such use of goto is really no different then > exceptions in C++ > Using goto is a great way to create memory leaks. C++ exceptions guarantee that all objects going out of scope have their destructors invoked to allow resource deallocation.
"Transmitting private information over publically accessible airwaves is not the answer. It's an interesting approach, but it's not a solution."
You are misunderstanding how the system works. If the SMS message contains a single-use code that must be entered to complete the authentication process the transmission medium does not matter. The process will not allow that combination to be reused by anyone who intercepted the message. This system is still vulnerable to man-in-the-middle attacks but it is very solid for user identification.
> planes can be flown by hand > Not always. A complete computer failure (about as close to impossible as is possible) in a fly-by-wire plane could really ruin your day.
I started on Slackware many years ago. Then I made the rounds of the "easy" distros with their fancy package management systems. Finally I rescued myself from dependency hell by returning to Slackware. Tarballs are the best package system for me.
The Food Pyrimid is only a few years old. When I was a kid and up until the introduction of the Food Pyrimid they told us to equally balance the four food groups. Back when the government was running short of butter to send to the troops in WWII they told the people margarine was the way to go. Somewhere along the way lard became evil. Since then better science has shown margarine to be no better than butter and worse than lard. The government folks make their health recommendations from committees influenced by anti-everything activists and food industry money. Their recommendations are as reliable as an Arthur Andersen audit.
Any code that dereferences a null pointer cannot be using good quality smart pointers. I am a little skeptical about working ten years w/o a debugger but I have seen the importance of the debugger shrink dramatically as I adopt modern C++ design practices. In the past two or three years virtually every bug that has forced me to use a debugger was caused by old C code or C++ code inherited from C programmers. Correct use of smart pointers and const declarations would have prevented 90% of those bugs.
I don't recall this report specifically mentioning Fox News but it does show the same difference between informed and uninformed Americans. http://www.pipa.org/OnlineReports/Iraq/IraqRealiti es_Oct04/IraqRealities%20Oct04%20rpt.pdf
People who sling mod points around without engaging their sense of humour first should be banned.
> Such use of goto is really no different then
> exceptions in C++
>
Using goto is a great way to create memory leaks. C++ exceptions guarantee that all objects going out of scope have their destructors invoked to allow resource deallocation.
And before the terrorists killed a few thousand people governments killed millions. Saying it can't happen here is an invitation for it to happen.
"Transmitting private information over publically accessible airwaves is not the answer. It's an interesting approach, but it's not a solution."
You are misunderstanding how the system works. If the SMS message contains a single-use code that must be entered to complete the authentication process the transmission medium does not matter. The process will not allow that combination to be reused by anyone who intercepted the message. This system is still vulnerable to man-in-the-middle attacks but it is very solid for user identification.
I so wanted to experience that hard drive corruption but my darned journaling file system thwarted me.
Isn't that the same thinking that brought kudzu to the southern United States?
The only career advice book I ever read left me with one solid, timeless rule. Never work for an insurance company. Sounds like you missed that book.
> planes can be flown by hand
>
Not always. A complete computer failure (about as close to impossible as is possible) in a fly-by-wire plane could really ruin your day.
I started on Slackware many years ago. Then I made the rounds of the "easy" distros with their fancy package management systems. Finally I rescued myself from dependency hell by returning to Slackware. Tarballs are the best package system for me.
The closet.
Considering the price of Rational software IBM might make up the difference in license fees alone.
The Food Pyrimid is only a few years old. When I was a kid and up until the introduction of the Food Pyrimid they told us to equally balance the four food groups. Back when the government was running short of butter to send to the troops in WWII they told the people margarine was the way to go. Somewhere along the way lard became evil. Since then better science has shown margarine to be no better than butter and worse than lard. The government folks make their health recommendations from committees influenced by anti-everything activists and food industry money. Their recommendations are as reliable as an Arthur Andersen audit.
Any code that dereferences a null pointer cannot be using good quality smart pointers. I am a little skeptical about working ten years w/o a debugger but I have seen the importance of the debugger shrink dramatically as I adopt modern C++ design practices. In the past two or three years virtually every bug that has forced me to use a debugger was caused by old C code or C++ code inherited from C programmers. Correct use of smart pointers and const declarations would have prevented 90% of those bugs.