I hope not, since mysql_escape_string() will also allow for SQL injection by not respecting the character set of the MySQL connection. The PHP Group, in all its brilliance, decided to add another function, which they named mysql_real_escape_string(), rather than simply fixing the first one./me sighs
Original Intel Pentium 75MHz-133MHz processors used Socket 5, not Socket 7, but Socket 7 was backward-compatible to Socket 5. The voltage needed for later processors was set using a jumper block on the mainboard, so there was no issue with voltage differences, except that Socket 7 CPUs weren't compatible with Socket 5, and the later "Super Socket 7" CPUs couldn't be run at their full speed on a regular Socket 7. Anyway, all of that is documented at Wikipedia. Socket A is the socket that AMD used for their entire K7 line of CPUs, from the original 700MHz Athlon Thunderbird all the way through the last Athlon XP processor. Maybe you know of it as Socket 462 -- it's the same thing.
That's true, but Socket 7 was used from 1995 until 2000, and Socket A from 1999 until 2005 -- each for 5 years. In contrast, Socket 754 was introduced in fall of 2003; the last desktop processor to be made for Socket 754 was in spring of 2005 (Athlon 64 3400+), giving it a run of 1.5 years for desktops, and the last laptop processor to be made for Socket 754 was in fall of 2005 (Turion 64 MT-40), giving it about a 2 year run for laptops. The writing was already on the wall for Socket 754 when AMD released Socket 939 just 9 months after Socket 754, re-adding support for dual-channel RAM that Socket A systems had but Socket 754 lacked. Either way, I'd hardly say it is long-lived compared to Socket 7 or Socket A.
Well, except for the fact that pretty much all recording these days is done straight to digital. Sampled higher than 16-bit 44kHz, sure, but then again, DVD-Audio supports 24-bit 192kHz stereo, and as far as I know that's the rate at which most recording is done these days. So, better than CD? Perhaps. Better than DVD-Audio? No way.
I find it funny that the four other people that have responded to you have all said the same thing. Thinking freely and creatively, indeed. Really outside the box, guys!
Chances are it works fine on a current Safari nightly. The current release version of Safari really sucks in terms of DOM implementation; the nightlies work much, much better.
Remember that a toaster's job is to get really hot in order to toast things -- it makes sense that there would be a higher incidence of fire. Batteries, on the other hand, are not supposed to get hot enough to toast things, let alone explode. For a better example, try to find out how many power supplies have caught fire/blown up/caused significant injury.
Now, granted, I am not a battery specialist and so can't tell you the probability of an overheating battery catching fire, but I do know that most Li-Ion batteries have overload and short-circuit protection built-in, and I'd reckon that such circuitry is supposed to prevent the sort of overheating issues that Sony reported. (I could be totally off-base, but it's what I'm basing my comment on.) Wouldn't it stand to reason that if Sony was able to reproduce incidences of these batteries overheating that they should have been doing something about it sooner rather than later, since it meant that a catastrophic failure like the one in Osaka was highly likely? I guess it's all a moot point now. Personally, I'm more concerned now about the "new and improved" batteries that they claim to have made -- they don't seem to have done too well since the last recall.
(PS, I apologise to the great-grandparent for being a douchebag.)
You can read well, but your critical thinking is not so good.
Dell is reported to have known about incidents of laptops overheating, albeit in small numbers, for years. It and CPSC recalled 22,000 laptop batteries in December, 2005, because of overheating problems. Metal particle contamination was the cause behind that recall, as well, said Scott Wolfson, a CPSC spokesman.
Dell knew full well what would most likely result from this problem, because the exact same thing had happened before.
The story here is that they knew that their batteries were defective and had the potential for damage or loss of life but they didn't do anything about it when they found out.
"A times B times C equals X. If X is less that the cost of a recall, we don't do one."
I'm not sure you realise quite how many people have wireless network connections. Many cable and DSL companies now provide modem/wireless router combination boxes to their customers when they subscribe. In my experience, I would say more people than not have wireless connectivity with their broadband connections.
Maynor said he and Ellch have been in contact with Apple, Microsoft and other companies responsible for vetting the device drivers that power the embedded or third-party wireless card devices meant for those systems, and that both companies are working with wireless card vendors and original equipment manufacturers (OEMs) to remedy the problems.
Also, christ, I'd say they're being pretty responsible about it.
Maynor said he and his colleague opted in favor of a videotaped demonstration versus a live one because of the possibility that someone in the audience could intercept the traffic sent to a potentially live target and deconstruct the attack -- possibly to use the exploit in the wild against other Macbook users.
Currently, the only way to create elements that are side-by-side with variable widths and the ability to control vertical positioning is by floating block-level elements. The float makes it impossible for them to be centered on the page. There are many other good reasons for inline-block, this just happens to be one I ran up to most recently. It REALLY needs to be implemented.
Conditional comments still work, but a lot of the nasty hacks for IE6 will break horribly in IE7, and well-formed code will also break horribly in IE7.
Slashdot Mirror
At 4:20, it may not be sleep deprivation inhibiting his ability to speak correctly...
I hope not, since mysql_escape_string() will also allow for SQL injection by not respecting the character set of the MySQL connection. The PHP Group, in all its brilliance, decided to add another function, which they named mysql_real_escape_string(), rather than simply fixing the first one. /me sighs
Original Intel Pentium 75MHz-133MHz processors used Socket 5, not Socket 7, but Socket 7 was backward-compatible to Socket 5. The voltage needed for later processors was set using a jumper block on the mainboard, so there was no issue with voltage differences, except that Socket 7 CPUs weren't compatible with Socket 5, and the later "Super Socket 7" CPUs couldn't be run at their full speed on a regular Socket 7. Anyway, all of that is documented at Wikipedia. Socket A is the socket that AMD used for their entire K7 line of CPUs, from the original 700MHz Athlon Thunderbird all the way through the last Athlon XP processor. Maybe you know of it as Socket 462 -- it's the same thing.
Cheers,
That's true, but Socket 7 was used from 1995 until 2000, and Socket A from 1999 until 2005 -- each for 5 years. In contrast, Socket 754 was introduced in fall of 2003; the last desktop processor to be made for Socket 754 was in spring of 2005 (Athlon 64 3400+), giving it a run of 1.5 years for desktops, and the last laptop processor to be made for Socket 754 was in fall of 2005 (Turion 64 MT-40), giving it about a 2 year run for laptops. The writing was already on the wall for Socket 754 when AMD released Socket 939 just 9 months after Socket 754, re-adding support for dual-channel RAM that Socket A systems had but Socket 754 lacked. Either way, I'd hardly say it is long-lived compared to Socket 7 or Socket A.
Cheers,
You're thinking of Socket A, not Socket 754. 754 was actually the shortest lived of the sockets.
Well, except for the fact that pretty much all recording these days is done straight to digital. Sampled higher than 16-bit 44kHz, sure, but then again, DVD-Audio supports 24-bit 192kHz stereo, and as far as I know that's the rate at which most recording is done these days. So, better than CD? Perhaps. Better than DVD-Audio? No way.
I find it funny that the four other people that have responded to you have all said the same thing. Thinking freely and creatively, indeed. Really outside the box, guys!
Microsoft learned their lesson and changed it back in Windows Vista. "Numbnuts" indeed.
Chances are it works fine on a current Safari nightly. The current release version of Safari really sucks in terms of DOM implementation; the nightlies work much, much better.
Actually IE7RC1 was released 2 days ago.
Cheers,
Remember that a toaster's job is to get really hot in order to toast things -- it makes sense that there would be a higher incidence of fire. Batteries, on the other hand, are not supposed to get hot enough to toast things, let alone explode. For a better example, try to find out how many power supplies have caught fire/blown up/caused significant injury.
Now, granted, I am not a battery specialist and so can't tell you the probability of an overheating battery catching fire, but I do know that most Li-Ion batteries have overload and short-circuit protection built-in, and I'd reckon that such circuitry is supposed to prevent the sort of overheating issues that Sony reported. (I could be totally off-base, but it's what I'm basing my comment on.) Wouldn't it stand to reason that if Sony was able to reproduce incidences of these batteries overheating that they should have been doing something about it sooner rather than later, since it meant that a catastrophic failure like the one in Osaka was highly likely? I guess it's all a moot point now. Personally, I'm more concerned now about the "new and improved" batteries that they claim to have made -- they don't seem to have done too well since the last recall.
(PS, I apologise to the great-grandparent for being a douchebag.)
Dell knew full well what would most likely result from this problem, because the exact same thing had happened before.
The story here is that they knew that their batteries were defective and had the potential for damage or loss of life but they didn't do anything about it when they found out.
"A times B times C equals X. If X is less that the cost of a recall, we don't do one."
I'm not sure you realise quite how many people have wireless network connections. Many cable and DSL companies now provide modem/wireless router combination boxes to their customers when they subscribe. In my experience, I would say more people than not have wireless connectivity with their broadband connections.
And imagine that, they've done it. (Well, except for the Voodoo. But I bet that would happen eventually.)
Also, christ, I'd say they're being pretty responsible about it.
Ironically (or not), Major League Baseball is trying to do just that...
As opposed to "Now browse to /media/cdrom0, where '/media/cdrom0' is the location of your CD-ROM drive" ?
Currently, the only way to create elements that are side-by-side with variable widths and the ability to control vertical positioning is by floating block-level elements. The float makes it impossible for them to be centered on the page. There are many other good reasons for inline-block, this just happens to be one I ran up to most recently. It REALLY needs to be implemented.
Sounds like you're looking for the 'em' unit of measurement, which is proportional based on the size of the font.
No, didn't you hear? All the tubes are filled up. She should send it in a truck instead.
I prefer the term douchebaggery, personally. Much more colourful.
Conditional comments still work, but a lot of the nasty hacks for IE6 will break horribly in IE7, and well-formed code will also break horribly in IE7.
/> />
So you will need to have:
<!--[if IE lt 7]>
<link rel="stylesheet" type="text/css" href="iesucks.css"
<![endif]-->
<!--[if IE eq 7]>
<link rel="stylesheet" type="text/css" href="iestillsucks.css"
<![endif]-->
That hack won't work in IE7. Have fun fixing everything all over again. :\