FWIW, Steve Jobs had a Pancreatic Neuroendocrine Tumor (often called a PNET or islet cell cancer). What most people think of when they hear pacreatic cancer is an extremely agressive, fast growing cancer that has single digit survival percentages at 12 months. Steve Jobs' cancer was a neuroendocrine tumor which can have survival times much greater than typical pancreatic cancer. I know this because I have a carcinoid cancer which is a neuroendocrine tumor and have been fighting this for years (14 this October).
Actually, the lasers use a very low wattage generator of the like you can get at Radio Shack. This impulse is them amplified by successively sending the pulse through amplifiers until the final 500+TW is achieved.
--Ron
Even funnier, it says "Additionally, signal directional markings are provided for optimum signal transfer". A close up picture of the plug shows a double ended arrow....
--Ron
The Dark Tower series is my all time favorite series of books and I have read them all multiple times. I worry about how it will adapt to both the big and little screen although the adaption of The Stand did fairly well. It is a huge story and I love it all (except for the last half of the last book).
I want one but a 7" screen is just a bit too small. I would drop my money in a second if they put out one with a 10" screen. Asus said they would months ago and then retracted the statement. The small screen size is the only thing holding me back right now...
--Ron
I have a rare form of cancer for which I am about 30 years younger than the average person with this cancer. I don't expect my doctor to know much about carcinoid because there are so few of us (he has only treated about half a dozen people with carcinoid).
Therefore, I feel it is my job to research as much as possible, find experts in carcinoid with which to consult and the latest paper to forward on to my current doc. Medicine should be a cooperative venture between doctor and patient, never just one or the other.
--Ron
believe me, comparing the debug assembler is not a big deal - you either run the debug code, with its additional instructions embedded in it, stack checks etc etc, or you run nice optimised release build code.
Comparing what the plonker wrote with the debug code is not a big deal - I think I can guarantee the release build is faster
That would be the case except the release code is generally the code with debug... It is an odd situation but, for various reasons, we run the debug code for our release.
I do agree with most of what you say b/c the compiler is almost always smarter than the C/C++ coder. The same is not true of an experienced assembler coder but that is another story altogether.
Yes, it was the most optimal code for this situation.
This code may have been optimal if the only measure was lines of code but that doesn't mean it would have executed any faster. Having fewer lines of code doesn't necessarily lead to better performance. Additionally, it can (and did in this case) lead to problems maintaining the code.
Believe it or not, it actually was faster. I checked the assember after I unraveled all of the convoluted crap that he had done and the unoptimized assember was a few statements shorter. Of course, the compiler might have optimized them to the same result but we generally run the unoptimized version of the code here so we can debug in case of failure.
I, for example, severely abuse short-circuit evaluation -- I'll often put five or more function calls into an if() conditional, ||ing their error conditions together -- but there's nothing wrong with that; you'll never find it in a textbook, but once you're used to reading that sort of code, it is more compact, easy to understand, and easy to maintain than the alternatives.
There is nothing wrong with that as long as the persons who are going to maintain the code are also of the fifth type of programmer. Generally, the people maintaining your code are of the second type and this code is going to confuse the hell out of them
We had a guy on our project that wrote an if statement that had three levels of embedded ?: operators along with several function calls, several of which took parameters that were generated by ?: operators with other function calls within them. There were half a dozed each of ||, && and ! along with a few |'s and &'s thrown in for good measure.
Yes, it was the most optimal code for this situation. However, this situation did not require that level of optimization and, when I had to fix it 2 years later because of a subtle bug that could have been obvious, I was ready to ?: the guy that wrote that code!
I really would like do use one of these but how does one power it? It would seem insane to hook a standard atx powersupply up to one of these mini pcs...
I was probably a bit strong on my opinions on printfs. I use them myself but it is usually only for the initial debugging. When the problem starts to get deeper, it is generally faster to run it in a debugger if only because building the entire application takes too long (half a day or more if you change the wrong file...).
Also, I am frequently the one called in when someone else's code does not work. Since I don't know the code, as you say, debuggers help greatly in figuring out the flow...
Reversibility. I'd like to be able to step backwards through code. No, this isn't a joke. Only a small amount of information needs to be stored as each instruction is executed in order to have an emulator go backwards again. You don't necessarily want to run an entire application reversibly. You might want to run a small loop until it crashes and then work backwards to find the cause.
This is obviously not always possible as many functions (squaring a number, sin of a number,...) are not reversible
One of my biggest problems with people on my current project is the lack of knowledge of how to use even the most basic tools. We program in C++ on Unix and many developers find calling up dbx to be a chore and, even when they get dbx up, have trouble using it. We have many other tools, ddd, other graphical debuggers but people just don't use them, relying on printfs and couts...
Actually, TiVo does have a 30 second skip feature. It is just not enabled by default and it is not well known how to enable it. See this link for details on how to enable it.
Slashdot Mirror
FWIW, Steve Jobs had a Pancreatic Neuroendocrine Tumor (often called a PNET or islet cell cancer). What most people think of when they hear pacreatic cancer is an extremely agressive, fast growing cancer that has single digit survival percentages at 12 months. Steve Jobs' cancer was a neuroendocrine tumor which can have survival times much greater than typical pancreatic cancer. I know this because I have a carcinoid cancer which is a neuroendocrine tumor and have been fighting this for years (14 this October).
http://xkcd.com/927/
Actually, the lasers use a very low wattage generator of the like you can get at Radio Shack. This impulse is them amplified by successively sending the pulse through amplifiers until the final 500+TW is achieved. --Ron
Even funnier, it says "Additionally, signal directional markings are provided for optimum signal transfer". A close up picture of the plug shows a double ended arrow.... --Ron
The Dark Tower series is my all time favorite series of books and I have read them all multiple times. I worry about how it will adapt to both the big and little screen although the adaption of The Stand did fairly well. It is a huge story and I love it all (except for the last half of the last book).
I want one but a 7" screen is just a bit too small. I would drop my money in a second if they put out one with a 10" screen. Asus said they would months ago and then retracted the statement. The small screen size is the only thing holding me back right now... --Ron
So, they tested this at altitude? Like Mount Everest
with real current!
I have a rare form of cancer for which I am about 30 years younger than the average person with this cancer. I don't expect my doctor to know much about carcinoid because there are so few of us (he has only treated about half a dozen people with carcinoid).
Therefore, I feel it is my job to research as much as possible, find experts in carcinoid with which to consult and the latest paper to forward on to my current doc. Medicine should be a cooperative venture between doctor and patient, never just one or the other.
--Ron
ditto! I may have to steal your idea of using 'O' for a variable. Nice how it confuses with '0'.
How does he expect people to try out his code without any screen shots????
Now people will be accused of heightening to get a job/raise
I do agree with most of what you say b/c the compiler is almost always smarter than the C/C++ coder. The same is not true of an experienced assembler coder but that is another story altogether.
There is nothing wrong with that as long as the persons who are going to maintain the code are also of the fifth type of programmer. Generally, the people maintaining your code are of the second type and this code is going to confuse the hell out of them
We had a guy on our project that wrote an if statement that had three levels of embedded ?: operators along with several function calls, several of which took parameters that were generated by ?: operators with other function calls within them. There were half a dozed each of ||, && and ! along with a few |'s and &'s thrown in for good measure.
Yes, it was the most optimal code for this situation. However, this situation did not require that level of optimization and, when I had to fix it 2 years later because of a subtle bug that could have been obvious, I was ready to ?: the guy that wrote that code!
I really would like do use one of these but how does one power it? It would seem insane to hook a standard atx powersupply up to one of these mini pcs...
And here I thought it was yet another SCO article...
is runnong on one of these wireless links... Bittorrent anywhere???
I was probably a bit strong on my opinions on printfs. I use them myself but it is usually only for the initial debugging. When the problem starts to get deeper, it is generally faster to run it in a debugger if only because building the entire application takes too long (half a day or more if you change the wrong file...).
Also, I am frequently the one called in when someone else's code does not work. Since I don't know the code, as you say, debuggers help greatly in figuring out the flow...
Reversibility. I'd like to be able to step backwards through code. No, this isn't a joke. Only a small amount of information needs to be stored as each instruction is executed in order to have an emulator go backwards again. You don't necessarily want to run an entire application reversibly. You might want to run a small loop until it crashes and then work backwards to find the cause.
This is obviously not always possible as many functions (squaring a number, sin of a number,
To do this in dbx do:
"stop at 99 if (x == 17)"
or in gdb:
(gdb) break main.C:99
Breakpoint 1 at 0x8048776
(gdb) cond 1 (x = 17)
(gdb)
One of my biggest problems with people on my current project is the lack of knowledge of how to use even the most basic tools. We program in C++ on Unix and many developers find calling up dbx to be a chore and, even when they get dbx up, have trouble using it. We have many other tools, ddd, other graphical debuggers but people just don't use them, relying on printfs and couts...
Actually, TiVo does have a 30 second skip feature. It is just not enabled by default and it is not well known how to enable it. See this link for details on how to enable it.
It would be hard to write an emacs Macro that inserted "GNU" everytime one typed "Linux"
I can see it now, the Emacs office assistant: "I see you are trying to type 'Linux' Wouldn't you prefer the official name 'GNU/Linux'?