Oops, should have looked closer at preview, that was supposed to be
You forgot about the articles on how great Apple's <insert product here> is or how much Microsoft's <insert product here> sucks... sometimes both in the same article.
For reference, since I forgot to go back and link them, Title 35102 a and b both deal with works that have already been known or patented anywhere prior to the filing, in or out of the US.
It hasn't. However, the moment he tries to use it on one of the large companies, they'll haul the matter in to court, most likely bankrupting Mr. Cox in the process.
Or did you forget that these are filthy rich companies we're talking about?
Good idea, lets publicize a patent that might have been able to slip past Apple, Microsoft, etc...
Except that, by bringing it to the public limelight, you've just guaranteed that the aforementioned companies will attempt to get the patent thrown out due to section 102 a or b of Title 35 of the US Code (Patents).
Creative Labs is a small player? That's news to me, considering that they're extremely well known in the PC market for the Sound Blaster line of sound cards.
I have to disagree. I have yet to read an article on roughlydrafted that isn't intentionally misrepresenting data (I originally put facts there, but they aren't facts if they aren't true) to make Apple look better.
For a good example, go read the OSX vs. Vista articles.
x. Any comment mentioning Firefox in a bad light will be modded Flamebait or Troll. y. Any comment mentioning Internet Explorer in a good light will be modded Overrated or Troll. z. Any comment mentioning Firefox in response to an IE or Opera article, but isn't subject to x above, will be modded Interesting or Insightful.
I don't get why people want to see plain text emails when they can be more expressive with simple styling.
Simple, because it never stops with simple styling. People go "WOW! I can put purty graphix in muh emails! And tables! and music!" and down the slope we go.
Also, doctypes aren't "valid" or "invalid", they either trigger strict mode or quirks mode. Saying that your doctype is valid is meaningless.
Just because browsers do not implement real DTD checking yet does not mean valid doctypes are meaningless. We call this feature "not adhering to the standard."
Before anyone accuses me of straw-manning this, I made mention of display_errors and php.ini-dist as well as php.ini-dist and shared hosting in my last post.
People who use shared hosting systems have one of three problems: 1. The errors are shown for everyone to see. (display_error on) 2. The errors are hidden in the syslog or error_log where they can't see them. (display_error off, log_error on) 3. The errors are thrown away completely. (display_error off, log_error off)
The other catch is that packaging systems tend to preinstall php.ini-dist as php.ini rather than using php.ini-recommended. This means that, if you just install it from apt without checking the ini, you get the one with behavior that isn't recommended by default. Which is, in itself, a problem.
To the first part: When you're using like statements, you will have to pre-process things, yes. Most notably, escaping % and _ plus any other rules you want to implement (* to %, ? to _, explode on spaces with multiple LIKE statements to search on keywords, etc...).
SELECT * FROM myData WHERE CONTAINS (column, 'FORMSOF (INFLECTIONAL, ?)')
Parameters are intended for user input. I certainly hoping you aren't allowing users to type functions in directly...
As for IN, I build up the placeholders using something like... $placeholders = array_fill(0, count($search_params), '?'); $placeholders = implode(', ', $placeholders); $query = "SELECT last_name, first_name FROM patients WHERE disorder IN ($placeholders) ORDER BY last_name"; Then bind the parameters when running the query. (I use ADODB for PHP.)
Slashdot Mirror
I wish I could get my family to appreciate video game music, but they won't. They refuse to even listen to it, let alone appreciate it.
Disclosure: I'm the current webmaster of VGMusic.com, and have worked for the site as far back as 1997.
You forgot about the articles on how great Apple's is or how much Microsoft's sucks... sometimes both in the same article.
For reference, since I forgot to go back and link them, Title 35 102 a and b both deal with works that have already been known or patented anywhere prior to the filing, in or out of the US.
It hasn't. However, the moment he tries to use it on one of the large companies, they'll haul the matter in to court, most likely bankrupting Mr. Cox in the process.
Or did you forget that these are filthy rich companies we're talking about?
Good idea, lets publicize a patent that might have been able to slip past Apple, Microsoft, etc...
Except that, by bringing it to the public limelight, you've just guaranteed that the aforementioned companies will attempt to get the patent thrown out due to section 102 a or b of Title 35 of the US Code (Patents).
Psst... the year changed when you weren't looking. It's 2007 now.
Minesweeper? What do you think this is, the 90s?
Everyone knows it's World of Warcraft these days!
Damn, no mod points on me... and I already commented to this article, so even if I did, I counted use them.
Creative Labs is a small player? That's news to me, considering that they're extremely well known in the PC market for the Sound Blaster line of sound cards.
I have to disagree. I have yet to read an article on roughlydrafted that isn't intentionally misrepresenting data (I originally put facts there, but they aren't facts if they aren't true) to make Apple look better.
For a good example, go read the OSX vs. Vista articles.
For a limited time only, order one coaster and get a DVD case absolutely free*!
* Offer not valid in countries whose names contain vowels.
Nice Freudian slip. :D
er... three. I apparently can't count today.
You forgot two:
x. Any comment mentioning Firefox in a bad light will be modded Flamebait or Troll.
y. Any comment mentioning Internet Explorer in a good light will be modded Overrated or Troll.
z. Any comment mentioning Firefox in response to an IE or Opera article, but isn't subject to x above, will be modded Interesting or Insightful.
Only if you ignore that FreeBSD is a fork of 386BSD, which is itself a fork of 4.3BSD (or more accurately Net/2).
They removed every file, causing a spike in 404s for all of them.
Simple, because it never stops with simple styling. People go "WOW! I can put purty graphix in muh emails! And tables! and music!" and down the slope we go.
What do Macworld and Cisco's iPhone(tm) have to do with each other?
Didn't Kirk get killed off in Star Trek VII (Generations)?
In soviet russia the motherboard POSTs you!
Happy now?
Just because browsers do not implement real DTD checking yet does not mean valid doctypes are meaningless. We call this feature "not adhering to the standard."
Syntax checkers, for example, do recognize DTDs.
Before anyone accuses me of straw-manning this, I made mention of display_errors and php.ini-dist as well as php.ini-dist and shared hosting in my last post.
People who use shared hosting systems have one of three problems:
1. The errors are shown for everyone to see. (display_error on)
2. The errors are hidden in the syslog or error_log where they can't see them. (display_error off, log_error on)
3. The errors are thrown away completely. (display_error off, log_error off)
The other catch is that packaging systems tend to preinstall php.ini-dist as php.ini rather than using php.ini-recommended. This means that, if you just install it from apt without checking the ini, you get the one with behavior that isn't recommended by default. Which is, in itself, a problem.
When you're using like statements, you will have to pre-process things, yes. Most notably, escaping % and _ plus any other rules you want to implement (* to %, ? to _, explode on spaces with multiple LIKE statements to search on keywords, etc...).
Parameters are intended for user input. I certainly hoping you aren't allowing users to type functions in directly...
As for IN, I build up the placeholders using something like...
$placeholders = array_fill(0, count($search_params), '?');
$placeholders = implode(', ', $placeholders);
$query = "SELECT last_name, first_name FROM patients WHERE disorder IN ($placeholders) ORDER BY last_name";
Then bind the parameters when running the query. (I use ADODB for PHP.)
P.S. If you don't have a call to get_magic_quotes_gpc() in your program somewhere, you don't have the ability to write good PHP code.