Comments on: Find and Replace http://blog.tomorrowevening.com/fla/find-and-replace/ Digitally Driven Fri, 19 Mar 2010 15:42:54 -0700 hourly 1 http://wordpress.org/?v=3.0 By: Colin http://blog.tomorrowevening.com/fla/find-and-replace/comment-page-1/#comment-21 Colin Fri, 19 Mar 2010 03:28:46 +0000 http://blog.tomorrowevening.com/?p=165#comment-21 Ha! How right you are. It's funny how knowing the basics can make life so much easier. I'm definitely swapping out my method with that haha. Ha! How right you are. It’s funny how knowing the basics can make life so much easier. I’m definitely swapping out my method with that haha.

]]> By: Jens http://blog.tomorrowevening.com/fla/find-and-replace/comment-page-1/#comment-18 Jens Thu, 18 Mar 2010 01:46:12 +0000 http://blog.tomorrowevening.com/?p=165#comment-18 I love those kind of utility functions that make your life easier... I use a different method in my StringUtils class to achieve the find and replace functionality. Basically does the same thing, just with less lines of code :P public static function replace(searchString:String, find:String, replace:String):String { return searchString.split(find).join(replace); } It uses the split() method of String classes, that turns the original string into an array with the search string being the delimiter, thus removing it. Then you join the array back together with the new string as seperator (which inserts it). Should the searchterm not exist, then the array will only have 1 node, so nothing will have to be joined and the old string gets returned... Same result, different method... I love to see how everyone approaches those problems differently. By comparing the methods you can learn so much... Just found (and bookmarked) your blog btw since you linked it on Kontain... I always have big plans for mine but never find the time to really get it going... I love those kind of utility functions that make your life easier… I use a different method in my StringUtils class to achieve the find and replace functionality. Basically does the same thing, just with less lines of code :P

public static function replace(searchString:String, find:String, replace:String):String {
return searchString.split(find).join(replace);
}

It uses the split() method of String classes, that turns the original string into an array with the search string being the delimiter, thus removing it. Then you join the array back together with the new string as seperator (which inserts it). Should the searchterm not exist, then the array will only have 1 node, so nothing will have to be joined and the old string gets returned… Same result, different method… I love to see how everyone approaches those problems differently. By comparing the methods you can learn so much…

Just found (and bookmarked) your blog btw since you linked it on Kontain… I always have big plans for mine but never find the time to really get it going…

]]>