With Few Exceptions, the String Remains the Same
211371
Professional and recreational players are unlikely to see major developments in racket string technology any time soon.
192641
DevShed has posted the second and last part of a series of two articles based around the Composite design pattern - using it to work with strings in PHP5.   Are you a PHP developer who wants to improve your skills in pattern-based programming in PHP? If the answer to this question is a emphatic yes, then you should begin reading this article now! Welcome to the final part of the series "Implementing the composite pattern with PHP 5." Comprised of two instructive tutorials, this series walks you through the basic concepts of this important design pattern, and shows you how to apply it with some educational examples.   They start by defining a simple StringProcessor class as an abstract interface to build from. From there, they create two other classes - the SingleStringProcessor and the MultipleStringProcessor. Each of these takes in either a single file or multiple filenames and spits back out the value of the string and the length of the string.
579233
Ed Finkler has pointed out a handy resource for those trying to cope with using the UTF-8 support included in several of PHP's functions - this page on the Web Application Component Toolkit wiki.   This page is intended as a reference for functionality PHP provides which can either help with handling UTF-8 or should be regarded as a risk when used in conjunction with UTF-8 encoded strings. Further information can be found on the Internationalization (I18N) and Character Sets / Character Encoding Issues pages.   It talks about the "dangerous" functionality PHP has (issues that the language has in current functions) when using things like the PCRE extension, the string extension, the array methods, handling variables, the XML extensions (DOM and SAX), image manipulation, and URL parsing functionality.
563255
Harry Fuecks is back today on the SitePoint PHP Blog with part two of his "joy of regular expressions" series, continuing on from this previous entry.   He jumps right in, summarizing the first part in a small section before getting back into the examples:  Hunting for .jp(e)gs Escaping Meta-Characters Search and Replace preg_quote() preg_replace() Word Boundaries, Word Characters...and everything else Sub patterns Spot the XSS Hole eval() is evil! preg_replace_callback()  As you can see, it's crammed with just as much infromation as the first part and covers a wide range of topics to help you get more in tune with your inner regular expression guru.
691015
Some habits aren't meant to be broken.
297586
Worm is traveling by e-mail, but does not appear to cause much damage.
731858
Really cool blog post about hidden Java features.  These are little tricks that you forget about from time to time but that make life more pleasant.  This is a good one:  "Instance initializers -- I've been exploiting these lately to abbreviate list initialization (in unit tests only): > List triple = new ArrayList(3) { >   { add("a"); add("b"); add("c"); } > };"  I've been using static code blocks but this looks like it might be a better trick.  Example:  "public static List = new ArrayList(); > static {     list.add( "foo" ); }"  Also this final Closure  hack seems pretty cool:
370525
The names of the characters have also changed.
114037
An old-style SQL injection hack is the suspected culprit in a malicious attack on the RIAA's Web site. During the weekend, its framework was still going, though its content had been erased.
161537
Agilists can miss the point Column â¦
120786
Tests are carried out to see how the net's addressing system  copes with international character sets such as Chinese and Arabic.
634592
If an Internet stock story falls in the woods, it does make a sound.
641397
The other day Tim Bray wrote up an interesting piece on java.util.regex.  I sent him off a quick email detailing my past experiences  and he just blogged his feedback .  "Well... yeah, but here's a story. I was kind of surprised at the results on my OS X box, so I took the code and data over to a nearby Windows XP box and got similar results, so I took 'em to a Debian-stable box I had handy and once again, about the same story. "  "Only, not quite the same. Because it was Perl 5.8.1 on one box and 5.8.3 on another and 5.6.1 on the third, and the i18n/regex code was slightly different in each version, and no two of them gave quite the same results. "  "Now, I'll grant that Unicode/i18n is one ...
272837
It is my first CMS, which is earlier a framework or something like that. Please be patient and feel free to use/edit it. -- Dies ist mein erstes CMS, welches eher einem Framework gleicht. Benutzt und verÃÂ¤ndert es nach eigenem Ermessen.   I decided to upload a new package, including page-support for different charset-types.  Default charset is UTF-8, but if you want to change it, you only have to edit the class-file.
29670
We can still read words on papyrus; we don't know how long it will be possible to read a text inscribed in a 2004 CD. This is not a complaint, just a reminder.
475941
Stick to the basics to win in the long run.
148300
On Greg Beaver's blog today, there's his look at string comparison with the "equals equals" (==) operator in PHP and some issues he found around it.    Recently, an obscure detail in the way PHP processes strings came to my attention in the form of an endless loop occasionally found in phpDocumentor's parsing of a file.   This is processed by code that checks for simple lists (like 1. blah 2. blah, or - blah - blah, etc.). However, an innocent call to in_array($x, array('1.', '0.')) had surprising and unexpected results: our friendly PHP determined that '01' was in the array('1.', '0.')!! This is of course patently false, and made little to no sense until I realized that unlike my previous understanding (when comparing an integer to a string, the string is converted to an integer), PHP actually converts all numeric-like strings into integers when comparing them.    To help avoid these kinds of situations repeating themselves, he makes a few suggestions when comparing your values: "use === instead of ==", "use the third parameter in in_array, set to true", and "use strcmp() or one of its cousins". In his opinion, though, this kind of auto-conversion is a bit dangerous - bit it's all about perspective...