Top-posting is sublime. Embrace it. Why scroll through 10 pages of emails you've already read when you can get to the meat of it all in the first few lines of an email? :)
Plus trying to quickly separate all the previous replies from the latest one when some emailers indent, indent with leading character (ie. "> "), use horizontal dividers, etc. No standardization there. Top posting lets you read until you find the first divider, not the last.. hah The problem is the lack of agreement on this perfectly logical assessment. Mixing top and bottom posting gets ugly, I agree on that. But since I don't need to re-read what's already been said in a conversation that's fresh in my mind, I don't have to see all the mix of top/bottom and non-standardized reply dividers. Top-posting is the only logical choice. (why do I always have to rattle the hornet's nest? god.. this used to be a nice list before I started messing it all up with OT subjects) -TG = = = Original message = = = No. Despite the fact that I replied to your message as it was the "last" one, and that caused threaded mail readers to place my post directly under yours as a "reply", my comment was not specifically directed at your post. I had deleted the "way wrong" posts by the time I realized I wanted to say something about them... Apologies that my email/reading/posting habits are only somewhat conformant with threaded readers... Damn! And I just top-posted too! :-v On Tue, April 10, 2007 7:53 pm, Jim Lucas wrote: > Richard Lynch wrote: >> I am amazed by the sheer number of just plain WRONG answers to this >> one... >> >> Were they all from April 1 or something?... >> > so, are you saying that my answer was wrong, or just making a > statement. > > If my answer was wrong, it was because it was too simple, which is > what I was trying to get at, so > as not to confuse the OP. > > Anyways, here is the expanded version hopefully to your liking. > > > <?php > > // do that db connection thing... > // select you database > > $sql = "SELECT > ~~Client > ~FROM > ~~booked > ~WHERE > ~~Name = 'larry' > "; > > if ( ( $result = mysql_query($sql) ) === false ) > ~# Your request failed. Make up your own custom way of displaying the > error. > else > ~if ( mysql_num_rows($results) > 0 ) > ~~while ( $row = mysql_fetch_assoc($result) ) > ~~~if ( isset($row['client']) && !empty($row['client']) ) > ~~~~echo $row['client'] . '<br />'; > ~~~ > ~~ > ~ else > ~~echo 'No results found!'; > ~ > > ?> > > Does this satisfy you? > > > -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php ___________________________________________________________ Sent by ePrompter, the premier email notification software. Free download at http://www.ePrompter.com. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
