You jest but there's actually over 300 commandments in Exodus 20-31.
The only place where is says "Ten Commandments" in The Bible is Exodus 34:28.
The commandments in Exodus 34 are more "Do not cook a young goat in its mother’s milk" than "Thou shalt not kill" but don't tell the Christians because it upsets them.
The article doesn't say who they'll deliver it to.
What exactly will it be useful for? Factoring 50-bit numbers? Any ideas?
$15 million seems an awful lot of money just for bragging rights. It'd better come in a really pretty box so people can put it in the lobby when they get bored with it.
Use std::string and std::vector instead. You can use them perfectly well in "C" code so there's no excuse.
Uhm, no. Both are C++ additions that are not in any ISO C standard. If you want to use them, you need to compile with a C++ compiler and you need to link against C++ libraries, which may or may not be available for your target platform, even if you don't mind the additional clutter without any real added functionality.
I didn't say they were in the ISO C standard, that's why I out "C" in quotes.
You can write old fashioned C code but use std::string instead of malloc/strcpy/strdup/etc. There's no clutter or overhead, std::string most likely uses malloc/free underneath so in effect the compiler will produce the exact same code as you.
The difference is that the compiler never has a bad hair day and messes up the size of a malloc. It's also easier, you don't have to worry about ownership, you can throw exceptions in a deeply nested file reader and all the temporary strings will be freed for you automatically (assuming they're stack-based objects). etc., etc.
Anybody using malloc/free to manage strings in 2017 is doing it wrong.
And by extension: Anybody managing data arrays without std:vector is also doing it wrong.
Slashdot Mirror
Made in Japan .... at our facilities in China.
Just like the iPhone, then.
You jest but there's actually over 300 commandments in Exodus 20-31.
The only place where is says "Ten Commandments" in The Bible is Exodus 34:28.
The commandments in Exodus 34 are more "Do not cook a young goat in its mother’s milk" than "Thou shalt not kill" but don't tell the Christians because it upsets them.
I prefer to chisel the 0s and 1s into a stone tablet.
I know the OP said "forever" but what he really meant was "until by grandchildren throw all the old crap in the dumpster".
(assuming he has offspring).
A much better question is: WTF is an "ill-colored" image?
(also: "Why didn't you make two or three copies if disks are so cheap?")
For that price it'd better have a REALLY pretty box.
The article doesn't say who they'll deliver it to.
What exactly will it be useful for? Factoring 50-bit numbers? Any ideas?
$15 million seems an awful lot of money just for bragging rights. It'd better come in a really pretty box so people can put it in the lobby when they get bored with it.
Yeah, I forgot Linux, sorry. No reason it won't work there too but I don't have a Linux machine to develop on ATM.
Will Java?
There's more ways than Java.
Java? LOL! Good luck with that.
I'm currently writing a 3D CAD platform that runs on all devices (Windows, Mac, Android, iOS) and it isn't using Java.
What about Osmotic filters?
So water evaporates, pee does not?
(facepalm)
"Pee" isn't an element.
"Pee" is water with stuff dissolved in it. The pee water evaporates. The pee solutes do not. This process concentrates the solutes.
Also interesting is that this gives us a demographic, and ... it's not _just_ the beer drinkers that pee in Hotel Jacuzzis.
I like the bit about hotel Jacuzzis being much worse. Pee in Jacuzzis is obviously done deliberately.
"Stop peeing in the pool, kid!"
"But ... everybody does it!"
"Yeah but not from the diving board..."
Betteridge's law of headlines applies...?
https://en.wikipedia.org/wiki/...
Why is it that people see gun control as smart but immigration control as stupid?
Um because we're not inbred hicks? Immigrate control=hate. Gun ownership=paranoia/vigilantism.
ISIS is taking your jobs!!!
So that the Playstation Generation can do all that work? Construction, cleaning, picking cotton, etc.
It'll make good reality TV, that's for sure. I can't wait to see their tears.
You realize it's what people used to call an "Iron Curtain", right?
Look at Trump's policies carefully, which part of them doesn't look like old-style Communist Russia?
That's going to require that basically all cars get retrofitted with transponders.
Which will cost about as much as filling the gas tank.
Even if insurance was fairly cheap, this would make a car cost WAY more than it does today.
Sure, unless the self-driving cars actually have less accidents than the stupid self-centered meatsacks that are controlling them at the moment.
(which is a distinct possibility)
Maybe $23 billion could answer these questions.
Nonsense! For $23 billion we could have another F35 instead, and run it for two years.
PS: Where would this "ship" sail to...?
Yeah, 'cos send all those buildings and machinery to the moon is easy.
So is growing food, etc.
OK, I'll give you that.
Still, people like Linus Torvalds aren't helping by insisting that Linux never be tainted by a single C++ feature.
Even if he only allowed STL usage (std::string/std::vector/std::list, etc) and stack unwinding it would still be a huge step forwards.
I am sure he can learn more than you in 24 hours about launching satellites.
His attention span is about 10 seconds. The idea of him spending 24 hours learning something is laughable.
PS: Check his Twitter sometime. The idiot has over 34000 (thirty four thousand) tweets to his name. How is that even possible?
https://twitter.com/realdonald...
Use std::string and std::vector instead. You can use them perfectly well in "C" code so there's no excuse.
Uhm, no. Both are C++ additions that are not in any ISO C standard. If you want to use them, you need to compile with a C++ compiler and you need to link against C++ libraries, which may or may not be available for your target platform, even if you don't mind the additional clutter without any real added functionality.
I didn't say they were in the ISO C standard, that's why I out "C" in quotes.
You can write old fashioned C code but use std::string instead of malloc/strcpy/strdup/etc. There's no clutter or overhead, std::string most likely uses malloc/free underneath so in effect the compiler will produce the exact same code as you.
The difference is that the compiler never has a bad hair day and messes up the size of a malloc. It's also easier, you don't have to worry about ownership, you can throw exceptions in a deeply nested file reader and all the temporary strings will be freed for you automatically (assuming they're stack-based objects). etc., etc.
Anybody using malloc/free to manage strings in 2017 is doing it wrong.
And by extension: Anybody managing data arrays without std:vector is also doing it wrong.