You had 56k dialup 20 years ago? According to Wikipedia, even 14.4k wasn't available before 1991. With 9600bps, you'd need 70 hours, or about 3 days, to transmit your 300MB. That's more than the modern Japanese 58 hours.
The interaction of light with air causes the twinkling of the stars. It's also the reason why the sky is blue and sunsets are red (well, actually dust in the air does also contribute to that effect). Also Fata Morganas wouldn't exist without this interaction. So I'd say the interaction of air with light is quite visible.
Oops, sorry, there was indeed an ampersand missing; I first typed the code in the Slashdot edit box (forgetting the ampersand), then copied it into my editor, noted the omission and fixed it there, but forgot to fix it in the Slashdot edit box as well.
OTOH, if my intent had been to write to memory address 3, the following assert wouldn't make sense at all. So that should at least have been a strong hint that what I've posted isn't what I actually intended to post, and that I actually intended to "modify" p.
However my point stays: Most C programmers would think my (corrected) code snippet works, when it actually doesn't.
I think photons would contribute to dark matter, not to dark energy. Note that those two are quite different concepts. Dark matter is "ordinary" matter which just doesn't interact with photons (or other known forms of matter), except through gravitation. Dark energy is an antigravitational force of which we don't even have a clue what it is.
Well, brainfsck would make a file system check/repair on your brain. Could be quite useful, especially if it created a "lost+found" where all those things you've forgotten can be found again. However, if it went wrong, your whole brain may be damaged so much that only reformatting helps.
Pretty much anything is correct: it just depends on what your definition of "correct" is.
Well, that's the basic misunderstanding. Most C programmers would interpret my snippet as follows: "First, the variable p is initialized with 3. So the memory where this variable lives contains the machine's representation of 3. Then, the first sizeof(short) bytes of the variable are overwritten with the representation of (short)4. Since there isn't any allowed int representation where the whole number can be interpreted as 3, while the first sizeof(short) bytes contain the representation of 4, there's no way that p is still 3 after that assignment, therefore the assert will not trigger." And maybe they will test their code with some compiler, say using gcc -O, and will observe that it indeed does what they expect. Then they use that type of cast (without the assert, of course) in real world code, and everything seems to be fine.
Much later someone decides "-O" isn't fast enough, and compiles the code with "-O3". And suddenly the code shows strange behaviour. Or worse, it only shows that strange behaviour under certain conditions which evade testing, but later happen on using the released code.
The code isn't valid C, and some compilers (like gcc -O3) make use of that. The result in general isn't what the author expected.
C++ cannot be Islam because it's a faithful extension (i.e. descendant) of C, and not a sibling to it. Islam and Judeo-Christianity are related by blood as siblings. The root of Islam traces back to Ismael, the illegitimate son of Abraham who has another son Issac who begets Jacob, the father of Israelites. Many of the Christian doctrines have analogy in Islam but they're quite different. This is more like comparing Java and C#, if Java is Christianity and C# is Islam.
Java doesn't have anything from C except for syntactic similarity and a few fundamental types. If there's something like Christianity, then it's C++: Just like Christianity includes most of Judaism as the Old Testament, C++ includes most of C. And as with Judaism/Christianity, while the old religion is actually somehow included, things which were considered good practice there are now considered bad practice, because there are now alternatives which are considered better.
Quite the contrary. The people who tab-indent are those who should be burned. The tab character was the worst invention in the history of character sets. You cannot even prefix them (line numbers, diff line change prefix, email quote prefix etc.) without breaking the indentation.
Oh, and try to get people to agree how many spaces a tab should be!:-)
Well, C is more restrictive than many people know. The problem is that many forbidden things not only don't give an error, but moreover often seem to work, yet some time in the future it may fail.
For example, most C programmers expect that the following code works:
Easy: Just have a bot add "untagged" tags to everything not yet tagged. Then it's tagged, because it's tagged "untagged".
2) Information must be TRUE (otherwise you will get bad deductions).
Also easy: Just remove all wrong information before making your deduction. OK, so how is the computer to know what is wrong? Well, that's of course again semantic information, so just tag anything wrong as "wrong". If some "wrong" tagging happens to be wrong, you can still tag that as "wrong" as well.
3) Ontologies, that is schemas stating what IT IS, should be shared (please don't die laughing)
Just upload them onto any p2p network. Sharing is what they are for, aren't they?
3) Not all "SCHEMAS" can be deductible (the complexity of what you state is a huge COMPUTATIONAL problem).
Well, if the software gets stuck, it still can ask a human.
Note to the humour impaired: Imagine a smiley after each sentence!
*Please note that centrifugal is a made-up non existent word. The real word should be centripetal. Centrifugal is a made up force that physics people HATE! So please, everyone use the world centripetal, not centrifugal. Thanks!
Just call telnet, and handle all the HTTP yourself. This also gives you complete control about what your browser sends to anyone, because you are the browser.
Slashdot Mirror
Well, for a hostile takeover, just donate your brain, but for transplant, not for research.
Of course, if you don't use it on a device like a digital camera, there's no reason to use an SD card at all.
You had 56k dialup 20 years ago? According to Wikipedia, even 14.4k wasn't available before 1991. With 9600bps, you'd need 70 hours, or about 3 days, to transmit your 300MB. That's more than the modern Japanese 58 hours.
Why is this on slashdot????
This should be on some AOL board for christ sake.
He couldn't find the card with his AOL password.
Actually they were good for nothing, unless you were surrounded by an environment struck constantly by conflict and horror.
In other words, unless he had a TV running somewhere around him.
The interaction of light with air causes the twinkling of the stars. It's also the reason why the sky is blue and sunsets are red (well, actually dust in the air does also contribute to that effect). Also Fata Morganas wouldn't exist without this interaction. So I'd say the interaction of air with light is quite visible.
Oops, sorry, there was indeed an ampersand missing; I first typed the code in the Slashdot edit box (forgetting the ampersand), then copied it into my editor, noted the omission and fixed it there, but forgot to fix it in the Slashdot edit box as well.
OTOH, if my intent had been to write to memory address 3, the following assert wouldn't make sense at all. So that should at least have been a strong hint that what I've posted isn't what I actually intended to post, and that I actually intended to "modify" p.
However my point stays: Most C programmers would think my (corrected) code snippet works, when it actually doesn't.
It also interacts with the photons we can see. Otherwise, the refractive index of air would be exactly 1, instead of 1.00029
I think photons would contribute to dark matter, not to dark energy. Note that those two are quite different concepts. Dark matter is "ordinary" matter which just doesn't interact with photons (or other known forms of matter), except through gravitation. Dark energy is an antigravitational force of which we don't even have a clue what it is.
I'm pretty sure that if you e.g. hit the thumbs of a Mafia boss with a hammer, you have even more problems than if you hit your own thumbs :-)
Well, brainfsck would make a file system check/repair on your brain. Could be quite useful, especially if it created a "lost+found" where all those things you've forgotten can be found again. However, if it went wrong, your whole brain may be damaged so much that only reformatting helps.
Well, that's the basic misunderstanding. Most C programmers would interpret my snippet as follows:
"First, the variable p is initialized with 3. So the memory where this variable lives contains the machine's representation of 3. Then, the first sizeof(short) bytes of the variable are overwritten with the representation of (short)4. Since there isn't any allowed int representation where the whole number can be interpreted as 3, while the first sizeof(short) bytes contain the representation of 4, there's no way that p is still 3 after that assignment, therefore the assert will not trigger."
And maybe they will test their code with some compiler, say using gcc -O, and will observe that it indeed does what they expect. Then they use that type of cast (without the assert, of course) in real world code, and everything seems to be fine.
Much later someone decides "-O" isn't fast enough, and compiles the code with "-O3". And suddenly the code shows strange behaviour. Or worse, it only shows that strange behaviour under certain conditions which evade testing, but later happen on using the released code.
The code isn't valid C, and some compilers (like gcc -O3) make use of that. The result in general isn't what the author expected.
Admit it: You only posted that sentence in order to get moderated "Informative"!
Idle, of course.
Java doesn't have anything from C except for syntactic similarity and a few fundamental types. If there's something like Christianity, then it's C++: Just like Christianity includes most of Judaism as the Old Testament, C++ includes most of C. And as with Judaism/Christianity, while the old religion is actually somehow included, things which were considered good practice there are now considered bad practice, because there are now alternatives which are considered better.
And I always thought camels only contain tobacco. Evil camel smokers! :-)
Note: There's no need to teach me about the animal.
Quite the contrary. The people who tab-indent are those who should be burned. The tab character was the worst invention in the history of character sets. You cannot even prefix them (line numbers, diff line change prefix, email quote prefix etc.) without breaking the indentation.
Oh, and try to get people to agree how many spaces a tab should be! :-)
Well, C is more restrictive than many people know. The problem is that many forbidden things not only don't give an error, but moreover often seem to work, yet some time in the future it may fail.
For example, most C programmers expect that the following code works:
Also, what about Unlambda? Whitespace? Shakespeare?
But those only become a problem after hitting them with a hammer.
Seems you didn't read the very last sentence of my post:
Or in short: Whoosh!
Easy: Just have a bot add "untagged" tags to everything not yet tagged. Then it's tagged, because it's tagged "untagged".
Also easy: Just remove all wrong information before making your deduction. OK, so how is the computer to know what is wrong? Well, that's of course again semantic information, so just tag anything wrong as "wrong". If some "wrong" tagging happens to be wrong, you can still tag that as "wrong" as well.
Just upload them onto any p2p network. Sharing is what they are for, aren't they?
Well, if the software gets stuck, it still can ask a human.
Note to the humour impaired: Imagine a smiley after each sentence!
http://www.xkcd.com/123/
Just call telnet, and handle all the HTTP yourself. This also gives you complete control about what your browser sends to anyone, because you are the browser.
Well, maybe it's just frontotemporal dementia.