As do NUL (not NULL) terminated strings. They have a limit defined by addressable memory. So, you want longer strings with a length at the beginning? Make your strings have a 32 (or 64) bit integer at the beginning instead of 8 bit like Pascal. Four bytes are cheap nowadays, and the reduction in problems would be worth it.
Actually, as long as the high-level semantics are preserved, the compiler does not have to short circuit the evaluation. If the compiler can figure out that A && B is exactly equivalent to (including any potential side effects) ((bool)A) & ((bool)B) then the compiler is free to make that replacement and avoid the costly branch. The standard dictates behavior, not implementation. Should a pointer dereference have no adverse effects, the compiler is free to do that, as well as through in a call to sin(42).
Another option is a corporate sponsor. Many FOSS projects have time being invested by people that are simply employees of some corporation that has found that they would benefit from the improvements/software.
No, I have to disagree with you there, Mister Former Riddick Employee. If someone is actually selling cliparts, well, OK. That's worthy of legal action. But merely using a picture and not remembering if you bought it or not? Please. You may as well accuse me of shoplifting because I can't produce the receipt for the jeans on me arse.
That mixes the notion of copyright (where images can be duplicated) with actual objects that can't. But, just for fun let's say I can prove only I make/sell those jeans. Well, if I know I'm the only one who sells the jeans, and I didn't sell you the jeans, and you're wearing the jeans...
...Then yeah, you either stole the jeans or are in receipt of stolen property. Just like in the current scenario.
Or you sold the jeans to someone that then resold them to me.... First sale doctrine, anyone?
Obvious nonsense. Powerful development environments hide the complexity behind simple idioms. The real problem is that the developers who created the Windows APIs simply didn't bother to think through the use cases that programmers would have to deal with. (To be fair, early Mac and X Window APIs were even worse.)
Hardly. A Mac program that did nothing but throw up a dialog that said "Hello World" with a button that quit is two lines, one to init Quickdraw and one to pop up the dialog. The reason you couldn't do this in Windows was that the Mac had a powerful resource model from the very beginning and APIs that used them. Only if you didn't use resources did the code look as nasty as the Windows version.
The ingredients in a lithium phosphate battery aren't much different from what you'd find in mineral water plus a can of coke: lithium carbonate, phosphoric acid, iron, sugar, etc. There's also a plastic film and a corrosive but generally nontoxic electrolyte. They're so environmentally benign that in Canada you can literally just throw them in the trash, legally (not sure about the US). And they're perfectly recycleable; the biggest thing holding it back is that the raw ingredients aren't worth much and there's no big environmental consequences if you don't.
In CA at least (not sure about the rest of the US) batteries are classified as toxic waste, and are illegal to discard in the trash. However, this does not stop people from doing so. Maybe the batteries you are talking about are not the ones we have?
The point is that your car needs some way to store energy while it is driving around, unless you want electric wires or rails following every street, like some parts of SF have for their electric buses, and that batteries right now are not quite good enough. Batteries are improving and oil costs go up, so eventually they will make sense, unless biofuel works out, but meanwhile hydrogen is a possibly quicker route. You do not need to have an infrastructure to ship hydrogen, as it can be made on the spot with water and a power source. Heck, your "electric car" that you plug in could simply be an electrolysis machine that stores hydrogen that gets generated until it is burned while driving. Or something like that.
With respect to text or data entered into and stored by publicly-accessible site features such as forums, comments and bug trackers ("SourceForge Public Content"), the submitting user retains ownership of such SourceForge Public Content; with respect to publicly-available statistical content which is generated by the site to monitor and display content activity, such content is owned by SourceForge. In each such case, the submitting user grants SourceForge the royalty-free, perpetual, irrevocable, non-exclusive, transferable license to use, reproduce, modify, adapt, publish, translate, create derivative works from, distribute, perform, and display such Content (in whole or part) worldwide and/or to incorporate it in other works in any form, media, or technology now known or later developed, all subject to the terms of any applicable license.
There are enough minority people and a general social mentality that racism is bad (compare the small number of people that would actually make such comments) so that the trade-off is the other way. They would lose more than they would gain by allowing racist content.
Do note, I do not justify anything, but rather simply explain what I see as the real reason behind the policies or lack therof, i.e. profit. Piss off the fewest customers as possible for the largest revenue.
Yeah, you're absolutely right. Why confront bigotry and set clear rules against it, when you can just ignore the problem and maintain an environment where mentioning an alternative sexual orientation will get you harassed?
Because the potential number of bigoted customers you lose is higher than the potential number of harassed customers you lose. The easiest, cheapest, and most profitable model is simply do that the largest number of your potential customers want you to do, and hang the rest. To all that say "vote with your feet/dollars", this can be the result.
I think the significance of the ruling is that it stated that forums of this type were public and so subject to libel proceedings, as opposed to private and thus immune as Ajith claimed. The article was not clearly written, but that is what I got out of it.
When the Elevate America page contains things like "Learn about Microsoft Certifications", "Acquire new skills through Microsoft IT Academy", and "Learn modern Web design with Microsoft Expression software", methinks it may be, as in trying to trap people into an MS-only mindset.
As an aside, this is the first site (outside of the/. Silverlight news items) that asked me to install Silverlight.
Re:Ant-style ** globbing
on
BASH 4.0 Released
·
· Score: 2, Informative
There is a new shell option: `globstar'. When enabled, the globbing code
treats `**' specially -- it matches all directories (and files within
them, when appropriate) recursively.
H.G.Welles agreed with you. In his Outline of History, he posited that the area now covered by the Mediterranean Sea was dry until about ten thousand years ago, the Atlantic being held back at Gibraltar until its level rose above the isthmus and indundated the whole area.
There a couple of recent mysteries that are better explained by Welles' theory than the current "scientific" ones:
I assume you speak of the Messinian Salinity Crisis? It even speaks of Wells. Though the current belief is that he was off by over 5 million years....
To bolster your comment, I note that they state that there is only a 70% accuracy (at this time) which goes to 90% if it is trained to a specific user. Not exactly very reliable.
Maybe next time, NASA should include some type of cleaning devices, so that when the panels get dusty, then a brush or something could wipe the panels. Sure, it's more weight, but it could increase the productivity of the mission.
I was responding to the question of why wood vs. asphalt. Except now I go back and reread and see that it was really a question of shingle vs. non-shingle. Whoops.
As do NUL (not NULL) terminated strings. They have a limit defined by addressable memory. So, you want longer strings with a length at the beginning? Make your strings have a 32 (or 64) bit integer at the beginning instead of 8 bit like Pascal. Four bytes are cheap nowadays, and the reduction in problems would be worth it.
Actually, as long as the high-level semantics are preserved, the compiler does not have to short circuit the evaluation. If the compiler can figure out that A && B is exactly equivalent to (including any potential side effects) ((bool)A) & ((bool)B) then the compiler is free to make that replacement and avoid the costly branch. The standard dictates behavior, not implementation. Should a pointer dereference have no adverse effects, the compiler is free to do that, as well as through in a call to sin(42).
Another option is a corporate sponsor. Many FOSS projects have time being invested by people that are simply employees of some corporation that has found that they would benefit from the improvements/software.
No, I have to disagree with you there, Mister Former Riddick Employee. If someone is actually selling cliparts, well, OK. That's worthy of legal action. But merely using a picture and not remembering if you bought it or not? Please. You may as well accuse me of shoplifting because I can't produce the receipt for the jeans on me arse.
That mixes the notion of copyright (where images can be duplicated) with actual objects that can't. But, just for fun let's say I can prove only I make/sell those jeans. Well, if I know I'm the only one who sells the jeans, and I didn't sell you the jeans, and you're wearing the jeans...
...Then yeah, you either stole the jeans or are in receipt of stolen property. Just like in the current scenario.
Or you sold the jeans to someone that then resold them to me.... First sale doctrine, anyone?
Obvious nonsense. Powerful development environments hide the complexity behind simple idioms. The real problem is that the developers who created the Windows APIs simply didn't bother to think through the use cases that programmers would have to deal with. (To be fair, early Mac and X Window APIs were even worse.)
Hardly. A Mac program that did nothing but throw up a dialog that said "Hello World" with a button that quit is two lines, one to init Quickdraw and one to pop up the dialog. The reason you couldn't do this in Windows was that the Mac had a powerful resource model from the very beginning and APIs that used them. Only if you didn't use resources did the code look as nasty as the Windows version.
The ingredients in a lithium phosphate battery aren't much different from what you'd find in mineral water plus a can of coke: lithium carbonate, phosphoric acid, iron, sugar, etc. There's also a plastic film and a corrosive but generally nontoxic electrolyte. They're so environmentally benign that in Canada you can literally just throw them in the trash, legally (not sure about the US). And they're perfectly recycleable; the biggest thing holding it back is that the raw ingredients aren't worth much and there's no big environmental consequences if you don't.
In CA at least (not sure about the rest of the US) batteries are classified as toxic waste, and are illegal to discard in the trash. However, this does not stop people from doing so. Maybe the batteries you are talking about are not the ones we have?
The point is that your car needs some way to store energy while it is driving around, unless you want electric wires or rails following every street, like some parts of SF have for their electric buses, and that batteries right now are not quite good enough. Batteries are improving and oil costs go up, so eventually they will make sense, unless biofuel works out, but meanwhile hydrogen is a possibly quicker route. You do not need to have an infrastructure to ship hydrogen, as it can be made on the spot with water and a power source. Heck, your "electric car" that you plug in could simply be an electrolysis machine that stores hydrogen that gets generated until it is burned while driving. Or something like that.
You do realize that an A/C IS a heat pump, right? Simply pointing the other way? And those A/Cs soak up the power.
With respect to text or data entered into and stored by publicly-accessible site features such as forums, comments and bug trackers ("SourceForge Public Content"), the submitting user retains ownership of such SourceForge Public Content; with respect to publicly-available statistical content which is generated by the site to monitor and display content activity, such content is owned by SourceForge. In each such case, the submitting user grants SourceForge the royalty-free, perpetual, irrevocable, non-exclusive, transferable license to use, reproduce, modify, adapt, publish, translate, create derivative works from, distribute, perform, and display such Content (in whole or part) worldwide and/or to incorporate it in other works in any form, media, or technology now known or later developed, all subject to the terms of any applicable license.
Thank you for playing. Better luck next time.
The web.
There are enough minority people and a general social mentality that racism is bad (compare the small number of people that would actually make such comments) so that the trade-off is the other way. They would lose more than they would gain by allowing racist content.
Do note, I do not justify anything, but rather simply explain what I see as the real reason behind the policies or lack therof, i.e. profit. Piss off the fewest customers as possible for the largest revenue.
Steve from Stephan or Stephanie? Remember Sister Steve from the Father Dowling Mysteries?
Yeah, you're absolutely right. Why confront bigotry and set clear rules against it, when you can just ignore the problem and maintain an environment where mentioning an alternative sexual orientation will get you harassed?
Because the potential number of bigoted customers you lose is higher than the potential number of harassed customers you lose. The easiest, cheapest, and most profitable model is simply do that the largest number of your potential customers want you to do, and hang the rest. To all that say "vote with your feet/dollars", this can be the result.
You're right -- ** sorts, which means /** would cause /bin to be listed before /bin/*, so rm would fail to delete /bin. Whoops.
Here is good response to this meme: http://www.mrc-cbu.cam.ac.uk/people/matt.davis/Cmabrigde/ The most interesting analysis is after "Update 2". Also click on Graham's thesis summary.
I think the significance of the ruling is that it stated that forums of this type were public and so subject to libel proceedings, as opposed to private and thus immune as Ajith claimed. The article was not clearly written, but that is what I got out of it.
Here is the version I had given to me back in the 80's (still have it on my shelf, too!): http://wiretap.area.com/Gopher/Library/Humor/Jokes/litebulb.jok
It's a trap.
When the Elevate America page contains things like "Learn about Microsoft Certifications", "Acquire new skills through Microsoft IT Academy", and "Learn modern Web design with Microsoft Expression software", methinks it may be, as in trying to trap people into an MS-only mindset.
As an aside, this is the first site (outside of the /. Silverlight news items) that asked me to install Silverlight.
There is a new shell option: `globstar'. When enabled, the globbing code treats `**' specially -- it matches all directories (and files within them, when appropriate) recursively.
which would imply the buildings and cars go too. See also: http://www.bash-hackers.org/wiki/doku.php/bash4
First, note that Chris Kula is NOT a receptionist, but a comedic writer. You can read how the email was actually used by Cian Kelliher. The original is on Chris Kula's site.
H.G.Welles agreed with you. In his Outline of History, he posited that the area now covered by the Mediterranean Sea was dry until about ten thousand years ago, the Atlantic being held back at Gibraltar until its level rose above the isthmus and indundated the whole area.
There a couple of recent mysteries that are better explained by Welles' theory than the current "scientific" ones:
I assume you speak of the Messinian Salinity Crisis? It even speaks of Wells. Though the current belief is that he was off by over 5 million years....
To bolster your comment, I note that they state that there is only a 70% accuracy (at this time) which goes to 90% if it is trained to a specific user. Not exactly very reliable.
A post below gave this link: http://www.newscientist.com/blogs/shortsharpscience/2008/11/why-dont-the-mars-rovers-have.html
Maybe next time, NASA should include some type of cleaning devices, so that when the panels get dusty, then a brush or something could wipe the panels. Sure, it's more weight, but it could increase the productivity of the mission.
I was responding to the question of why wood vs. asphalt. Except now I go back and reread and see that it was really a question of shingle vs. non-shingle. Whoops.