ShowUsYour<Blog>

At lunchtime today I was discussing my WordWrap component with a fellow developer which - of course - led us into discussions as to the merit of the task and also how "optimal" we could make the underlying "wrapping" algorithm. When I started talking about my current algorithm we discovered that I'm doing several Split's and then speculated as to what the faster algorithm might be. We decided that it would be good to benchmark our final wrapping algorithm against the time it takes to perform a single Split() operation against the same input. It will be interesting to see how close we can get to Split() time.

About 6 months ago I enabled comments on the RegexLib.com site. Basically users can leave comments against individual patterns (there's actually an Rss feed for them too: http://www.regexlib.com/RssComments.aspx). One of my requirements was that people should be able to leave code samples which would then render correctly (line-breaks, spaces, etc). Because I'm basically a lazy guy I implemented the quickest, dirtiest thing that I could think of... yep, you guessed it, the good old PRE tag :-)

Frank has just blog'ged some more info about the Msdn Connection program:

Yesterday I blogged about the MSDN Connection programme and mentioned that I thought that it would be a good thing to get involved in and today I thought that I might expand upon that a little - just so that I can't be accused of being a .NET shill! :-) But seriously, many people have asked in the past how it is that people become MVP's or ASPInsiders or whatever, and it got me thinking...

Frank is doing a great job of keeping us Aussie blog'gers posted as to what's happening on the developer scene. Recently he announced a new initiative:

Following on from my post yesterday about FindStr.exe I noticed that kayodeok's Weblog have dug up the online link to FindStr documentation, here it is:

    How to Use Findstr

I've long thought of writing a little tool like grep (or egrep) which would allow me to quickly use regex to search for text within files. This weekend while reading an article about Standard I/O and Console Applications I discovered the Windows command-line tool FindStr.