On any sane platform, "long" has that property, and can also hold the machine word or more. Win64 is not sane.
Because of it, the standard had to add intptr_t which is the only type portably known to be of same width as void* and char* (but _not_ necessarily the same as a pointer to any other type!). Of course, MSVC doesn't follow standards and doesn't have this type nor stdint.h/inttypes.h at all.
Thus, your code will not work there, and will cut pointers. To make things worse, it will actually work if your pointers are within the first 2GB of address space and not on the stack.
I do fully agree with your core point, though: Pascal strings would suffer from all these problems as well, and not only.
It's not just software patents, that's bullshit. Patents are bad in all fields of technology, full stop.
Just look at Edison's patent trolling. Or how US patents of Wright brothers made the US the only side of WW1 without planes usable in war. Or the effects of patents on medicine.
Yeah, it's no different from ON ERROR RESUME NEXT, with the added benefit of adding a cost to correct programs.
They'd have to save the state of the whole machine on every watchdog tick. Hashing the whole memory is out of question, you'd need to hash just pages written to since the last tick, and that requires setting up page faults on the rest (or some custom architecture with generational memory, also costly).
Plus, there's absolutely no way to resume from such a loop when you detect it and still have the program's state be useful. The resume code would need to solve an uncomputable problem if it's supposed to be generic -- and if it's not, you can just as well not have the infinite loop bug in the first place.
I do agree with distributing the code as widely as possible, but not with:
You're whining like you're being harmed. You're not.
The thing with GPL is, the code is not a gift. It does have a cost attached: they have to pay back the public (especially you) with code rather than money, releasing all future improvements.
BSD/MIT vs proprietary is a prisoner's dilemma: and with current emphasis on short-term profits, it's certain the opponent will defect. The beauty of GPL is that it makes defecting a copyright violation: the opponent may only cooperate or not play at all (by not using the code), and if if they defect, you get to sue them.
Of course, as an individual, good luck suing a large company.
Wikileaks data was thoroughly vetted. And revealing the misdeeds and, even worse, incompetence, of both the government and the chain of command has a serious potential of saving lives, both of Afgani civilians (whom I don't really care about) and our soldiers.
To the contrary. Nothing in this data is really interesting, except for the fact that the FBI is paying mountains of taxpayers' money to their friends for basically nothing. What AnonSec proved here (yet again) is that these "security contractors" have nothing to do with security.
Yet your boss will read things on glossy paper and make you use it.
Re:3D - and Resolution Maxed-Out?
on
Beyond HDTV
·
· Score: 1
That "retina" gimmick is marketing bullshit, individual pixels there are not only visible but even somewhat annoying. I'm nearsighted and that gives a bonus to close range sight, but I can't believe a "normal person" wouldn't be able to see this.
Re:Joe Sixpack isn't even using his 1080p right
on
Beyond HDTV
·
· Score: 1
If you use it on a TV, resolution doesn't really matter. For a better display like a monitor, going below 1200p vertical is bad. Ok, assuming you weren't sold some shitty 768p piece of junk.
Uhm no, this is not bi-arch crap that keeps dragging us down -- as in, 32 bit libs on a 64 bit system. This is about having any library and any header co-installable with its versions from other architectures. Just think how much easier this makes cross-building things...
The House of the Future was funded by Monsanto who now is a scarily powerful biotech and genetically modified food conglomerate but who in the 1960s was all about plastics.
I don't see this as a likely outcome, yet the very idea is interesting. Apple wouldn't be where it is currently without replacing the OS9 junk with BSD, replacing NT with Linux could make Windows actually usable for something more than rootkit-laden games.
Well, that's better than Google's typo-jacking that sadly got into most browsers. I have that misfeature disabled -- to do a search, I type "g furry squid porn" (the default Firefox config has it on "google" which might be good enough for most, I shortened it to "g").
No matter if you blacklist or whitelist parts to pass to the client, you still need to parse the page well enough. Randomizing the page might make it hard enough for the fuckhats to implement the parsing, and when they do, Google can make a small change to throw them off again.
It's trivial to remove javascript, and losing Instant is hardly noticeable. For Google, I'd try randomizing the page and the warning, so the proxy has a hard time parsing it. Change the randomization algorithm once in a while, too.
Slashdot Mirror
On any sane platform, "long" has that property, and can also hold the machine word or more. Win64 is not sane.
Because of it, the standard had to add intptr_t which is the only type portably known to be of same width as void* and char* (but _not_ necessarily the same as a pointer to any other type!). Of course, MSVC doesn't follow standards and doesn't have this type nor stdint.h/inttypes.h at all.
Thus, your code will not work there, and will cut pointers. To make things worse, it will actually work if your pointers are within the first 2GB of address space and not on the stack.
I do fully agree with your core point, though: Pascal strings would suffer from all these problems as well, and not only.
It's not just software patents, that's bullshit. Patents are bad in all fields of technology, full stop.
Just look at Edison's patent trolling. Or how US patents of Wright brothers made the US the only side of WW1 without planes usable in war. Or the effects of patents on medicine.
Yeah, it's no different from ON ERROR RESUME NEXT, with the added benefit of adding a cost to correct programs.
They'd have to save the state of the whole machine on every watchdog tick. Hashing the whole memory is out of question, you'd need to hash just pages written to since the last tick, and that requires setting up page faults on the rest (or some custom architecture with generational memory, also costly).
Plus, there's absolutely no way to resume from such a loop when you detect it and still have the program's state be useful. The resume code would need to solve an uncomputable problem if it's supposed to be generic -- and if it's not, you can just as well not have the infinite loop bug in the first place.
Those dual screens are stacked vertically, right? Since that's the only way to make modern monitors useful.
Actually, it should be cap/time. If you have a "100mbit" connection with a 5GB monthly cap, a listed speed above 1.9kbps is false advertising.
The 100mbit number might be listed as "burst speed", since it's what it is.
... and they give me an allergy. And like in your analogy, you lose a lot if you can't do it directly.
I do agree with distributing the code as widely as possible, but not with:
You're whining like you're being harmed. You're not.
The thing with GPL is, the code is not a gift. It does have a cost attached: they have to pay back the public (especially you) with code rather than money, releasing all future improvements.
BSD/MIT vs proprietary is a prisoner's dilemma: and with current emphasis on short-term profits, it's certain the opponent will defect. The beauty of GPL is that it makes defecting a copyright violation: the opponent may only cooperate or not play at all (by not using the code), and if if they defect, you get to sue them.
Of course, as an individual, good luck suing a large company.
Wikileaks data was thoroughly vetted. And revealing the misdeeds and, even worse, incompetence, of both the government and the chain of command has a serious potential of saving lives, both of Afgani civilians (whom I don't really care about) and our soldiers.
To the contrary. Nothing in this data is really interesting, except for the fact that the FBI is paying mountains of taxpayers' money to their friends for basically nothing. What AnonSec proved here (yet again) is that these "security contractors" have nothing to do with security.
Unless you're selling an end-user product, which hardly ever happens in IT, you rarely get to choose what you need to interface with.
Yet your boss will read things on glossy paper and make you use it.
That "retina" gimmick is marketing bullshit, individual pixels there are not only visible but even somewhat annoying. I'm nearsighted and that gives a bonus to close range sight, but I can't believe a "normal person" wouldn't be able to see this.
If you use it on a TV, resolution doesn't really matter. For a better display like a monitor, going below 1200p vertical is bad. Ok, assuming you weren't sold some shitty 768p piece of junk.
Uhm no, this is not bi-arch crap that keeps dragging us down -- as in, 32 bit libs on a 64 bit system. This is about having any library and any header co-installable with its versions from other architectures. Just think how much easier this makes cross-building things...
that doesn't even cover congress's salary
That's the main point!
"git describe". It will give you a revision number since the last tag, plus a disambiguation hash. That number can be then used as a commit reference.
I'd boycott PayPal, but sadly, I can't boycott them any more than I already do.
The House of the Future was funded by Monsanto who now is a scarily powerful biotech and genetically modified food conglomerate but who in the 1960s was all about plastics.
So nothing really changed.
I don't see this as a likely outcome, yet the very idea is interesting. Apple wouldn't be where it is currently without replacing the OS9 junk with BSD, replacing NT with Linux could make Windows actually usable for something more than rootkit-laden games.
Well, that's better than Google's typo-jacking that sadly got into most browsers. I have that misfeature disabled -- to do a search, I type "g furry squid porn" (the default Firefox config has it on "google" which might be good enough for most, I shortened it to "g").
No matter if you blacklist or whitelist parts to pass to the client, you still need to parse the page well enough. Randomizing the page might make it hard enough for the fuckhats to implement the parsing, and when they do, Google can make a small change to throw them off again.
You see, most people these days type "facebook login" into Google, but some old geezers still use a thing named "DNS".
It's trivial to remove javascript, and losing Instant is hardly noticeable. For Google, I'd try randomizing the page and the warning, so the proxy has a hard time parsing it. Change the randomization algorithm once in a while, too.
Except, GTK had this for ages already.
You mean, your phone doesn't have a keyboard? :p