Regex Hero Blog

Regex Analysis Bug Fixes

noreply@blogger.com (Steve Wortham) — Sat, 13 Apr 2013 16:26:00 +0000

All of these updates relate to the analyzer, so if you're not a Regex Hero Professional user, then this won't affect you.

I received a report of an analysis bug related to character classes. The regex analyzer wouldn't handle opening brackets inside a character class properly.

It's one of the finer details of the regular expression syntax. You wouldn't think that [[abc] would be valid, but it is. You don't have to escape the opening bracket inside the character class. So now the analyzer interprets this as it should.

I've also fixed bugs around interpreting the \x00 (hex), \u0000 (unicode), and \k<group> (backreference) expressions.

P.S. The major updates I mentioned recently are still in the works. So the price for Regex Hero Professional is still $20 for now.

Regex Hero Professional: Improvements and Pricing

noreply@blogger.com (Steve Wortham) — Sun, 24 Mar 2013 23:33:00 +0000

I'm working on some new features for Regex Hero, focusing primarily on bringing more advanced functionality to Regex Hero Professional.

New Regex Hero Professional features in the works...

The analyzer will give you the option of automatically formatting your regular expression with comments.
The tool will analyze your regular expression and offer suggestions to improve the performance. For instance, there's a performance penalty in using IgnoreCase. And it's pointless to use it when there's nothing case-sensitive in your regular expression. There are many other things it'll look for, and this is something that will evolve and improve with time.

There will be various other things I'll be working on, but these are the big 2 features. When all of this is released, I'll also be raising the price for the Professional edition to $30.

I never make customers pay for updates. So if you're interested in the Professional edition, I'd suggest buying it now for $20 while you still can. Look out for the new improvements within the next couple months.

"Redo" on a Mac, and a Group Name Warning

noreply@blogger.com (Steve Wortham) — Fri, 01 Feb 2013 18:42:00 +0000

Today I released a minor update, fixing a couple bugs:

"Redo" functionality now works as it should on a Mac via the Command-Shift-Z keyboard shortcut.
I've added a group name warning. There's a weird issue with the way the .NET Regex engine allows numeric entries in group names. For instance (?<2>abc)|(?<4>def) will not throw an error upon instantiation. However, when you enumerate through the groups that's when you get a runtime error. So I've added a rule to show a warning in this case that says, "Group names must begin with a word character, or if they're numeric they cannot have gaps between numbers."

C# Strings and Code Generation Bug Fixed

noreply@blogger.com (Steve Wortham) — Tue, 25 Sep 2012 23:22:00 +0000

It was brought to my attention yesterday that there was a bug with the C# code generation feature inside Regex Hero. Thanks Blake for pointing it out. It turns out that I had made a stupid mistake in the way I was adding \r and \n to the string. I mostly rely on the @"string" literals because they're convenient and generally cleaner for what I need to do. But of course, the escaped notations \r and \n don't work inside those strings.

So this has been updated this morning. From now on Regex Hero will generate C# strings more like this...

@"line1" + "\n" + @"line2"

Optimized Memory Consumption

noreply@blogger.com (Steve Wortham) — Sat, 15 Sep 2012 23:23:00 +0000

Today's update includes a minor change to the custom undo/redo system in all of the textboxes within Regex Hero. They will now only store history on the OnKeyUp event, rather than storing history for every change. In other words, if you hold down a key on the keyboard for a long time it's not going to store history for every single character individually anymore.

This is a subtle difference, but in real world usage this should have a substantial impact on how much memory is used to hold the text history.

ASP.NET MVC DataAnnotations and the RegularExpressionAttribute

noreply@blogger.com (Steve Wortham) — Tue, 11 Sep 2012 15:27:00 +0000

A fellow Regex Hero user emailed me this morning about an inconsistency between what they were seeing in Regex Hero vs what they were seeing with the RegularExpression DataAnnotation in ASP.NET MVC.

As a test, they were trying the following regular expression...

^A|B|C$

Against this string...

ABC

In Regex Hero you see 3 matches (as you should). But in ASP.NET MVC it doesn't match, and validation fails.

Why is this?

As it turns out, the RegularExpressionAttribute is hiding an implementation detail. In fact, I couldn't even find any mention of this on MSDN.

It's most plainly visible if you open up the Javascript file that comes with an MVC project template, MicrosoftMvcValidation.js. Inside you'll find this bit of code...

var $0=new RegExp(this.$0);

var $1=$0.exec(value);

return (!Sys.Mvc._ValidationUtil.$0($1) && $1[0].length===value.length);

I've highlighted the important piece. It's checking to make sure the text value's length is equal to the match's length. In other words, the validation is designed to prevent any extraneous input beyond what a single regular expression match contains. And it does the same thing server side as well.

So for RegularExpressionAttribute testing purposes in Regex Hero you could just always use ^ and $ anchors for every regular expression. And then check to make sure that you're getting 1 match, and 1 match only.

Improved TextBoxes With Better Whitespace Support

noreply@blogger.com (Steve Wortham) — Mon, 06 Aug 2012 22:23:00 +0000

Today's update is all about whitespace. I've created a new textbox control for Regex Hero which is now being used for the 4 main textboxes: Regular Expression, Replacement String, Target String, and Final String.

The new features are as follows:

Figure 1: Matching Line Feeds

Handles tab characters as it should. You can test this by entering \t in your regular expression and then hitting tab in your target string.
Matching carriage returns or line feeds are now visible with a half-width character block (as seen in the figure 1).
You may preserve the formatting of pasted text with the new "Preserve pasted formatting" option. This will retain the existing line endings of your source text as was suggested about a month ago.
Cycling through your matches with the up & down buttons is now much more responsive.

Now Supporting Facebook and Twitter Logins

noreply@blogger.com (Steve Wortham) — Sat, 30 Jun 2012 20:46:00 +0000

This is something I've wanted to have for a long time but I simply haven't set aside the time to do it.

Well, no more waiting, Regex Hero now supports logging in with Facebook and Twitter...

If you already have an account with Regex Hero and want to sign in with something else (such as Facebook or Twitter) then you can add it to your account. Or if you're a brand new user of Regex Hero, create your account here.

New Benchmarking Features and a New Homepage Design

noreply@blogger.com (Steve Wortham) — Sun, 17 Jun 2012 23:21:00 +0000

Today I updated the benchmarking tool in Regex Hero with some new functionality.

There were essentially two things I was looking to accomplish:

Create insight into the benchmarking tool so that developers know exactly what it's doing.
Add the ability to benchmark your regular expression with the IsMatch() function. IsMatch() simply returns true if your regular expression has even 1 match in the specified string. As such, it actually stops searching after the first match is found. In some cases this makes it many times faster than iterating through every match.

So now you'll see some new options to take care of all this...

You can click the Show/Hide benchmarking code button at any point if you want to know exactly what Regex Hero is going to do under every benchmarking loop. There are effectively 4 different benchmarking modes: 2 modes when the Match tab is selected, 1 mode for Replace, and 1 mode for Split.

Homepage Redesign

And of course I've redesigned the homepage. It's not too drastic of a departure from the old design. One problem I wanted to solve was that the Regex Hero character used to point to the big "Regex Hero" title at the top of the page as you see here...

The problem with this was that the Regex Hero title at the top is actually a link back to the homepage. So if you click it, all you'll see is the page reload. And I found through Google Analytics there were a good number of people clicking this link from the homepage, suggesting that maybe the chubby pointing finger was influencing where people clicked.

So the new design takes this idea and uses it to point to where you should actually click...

Highlighting for Regex Group Pairings

noreply@blogger.com (Steve Wortham) — Wed, 13 Jun 2012 03:07:00 +0000

I added a new feature where the respective group starting and ending will be highlighted in gray when the cursor is on either the start or end of the group. This is especially useful when you have a large regular expression with many groups, or perhaps nested groups as below...

The idea for this comes right from Visual Studio 2010 which of course I use everyday. And this feature is very responsive because of the fact that Regex Hero doesn't have to reparse anything when you're simply moving the cursor around. Once again, the new parser is doing its job very well.

Improved Regex Code Completion and Bug Fixes

noreply@blogger.com (Steve Wortham) — Mon, 11 Jun 2012 02:17:00 +0000

I've taken another step towards leveraging the new regex parser this weekend. This time I've completely removed all dependencies on the old parser for the purposes of regex code completion. So the syntax highlighter and code completion features are both running on the new parser. This saves precious clock cycles and makes Regex Hero a little more efficient. And then I've introduced full support for Unicode general categories and named blocks denoted by the \p{name} or \P{name} syntax. So you'll get regex code completion for this as well.

In addition to this I've solved a few bugs:

The analyzer would get out of sync under certain situations, causing the list to be tabbed over needlessly.
Code completion would have issues when you try to navigate down the list and then back past the top result with the arrow keys. Hitting down again wouldn't return focus to the list as it should. I actually changed this behavior so the list will disappear if you do this.
Copying and pasting multiple lines of text within Regex Hero would create carriage returns which prevented the "End" button on the keyboard from advancing to the end of the line.

New Regex Parser, Improved Syntax Highlighter, and More on the Way

noreply@blogger.com (Steve Wortham) — Sun, 03 Jun 2012 21:51:00 +0000

During the past couple weeks I've been working on a revised version of my regex parser. For those who haven't followed my old posts about this parser, it's what makes some of the more advanced features in Regex Hero possible. It's being used for code completion, regex analysis, and the syntax highlighter.

Well, my new & improved parser is both faster and more powerful. Today I released an update which uses the new parser for the syntax highlighter. It's roughly twice as fast as the old parser. And the syntax highlighting is a little smarter now about detecting unclosed brackets or parentheses, and highlighting the offending section in red. It'll also highlight invalid character constructs such as \g in red.

But this is just the tip of the iceberg. There are a lot of improvements coming that'll be made possible by this new parser. Stay tuned for updates.

Faster Load Times for Regex Hero

noreply@blogger.com (Steve Wortham) — Sun, 01 Apr 2012 20:36:00 +0000

I took a lesson from my own blog post yesterday about lazy loading and made some drastic improvements to the load time of Regex Hero today. Essentially I'm now loading things like the analyzer and benchmark tool only when they're first called. This reduces the amount of work that has to be done when Regex Hero is first launched. And it should even reduce memory consumption a little bit if you're not using these features. The end result is that Regex Hero loads about half a second faster than before. This affects both the web version and the desktop version. Enjoy.

A Quick Tip About Using RegexOptions.Compiled

noreply@blogger.com (Steve Wortham) — Sat, 31 Mar 2012 22:29:00 +0000

Since Silverlight doesn't support RegexOptions.Compiled, it's the one option that's missing from Regex Hero.

In a full .NET application there may be times when it's worth it to use this option. It adds significant cost to initializing the Regex instance, but it can also double the speed of the regular expression itself in some cases. Therefore it's best to use when you can instantiate the Regex object once, and reuse it many times. Jeff Atwood talks about this very point in his article, To Compile or Not to Compile.

So if you've determined in your case that RegexOptions.Compiled is worth the initial cost of compilation, then I'm going to offer one simple solution that we as programmers often forget about.

Lazy Loading
The advantage with lazy loading is that the object we're concerned about is only instantiated when it's first accessed. Therefore, we can use RegexOptions.Compiled without necessarily hurting the initial start-up time of our application. In some cases we can even avoid needlessly instantiating objects...

private static Regex _LibraryTagsRegex = null;
public static Regex LibraryTagsRegex
{
 get
 {
  if (_LibraryTagsRegex == null)
  {
   _LibraryTagsRegex = new Regex(@"^library/tagged/(?<Tags>.+)", RegexOptions.Compiled);
  }
  return _LibraryTagsRegex;
 }
}

We can then call the static LibraryTagsRegex in the example above from anywhere in our code, and it's only going to be instantiated the first time it's accessed.

By the way, in my test I was able to perform 2 million LibraryTagsRegex.IsMatch() calls in 256 ms with the Compiled option (as above) vs 461 ms without it. The compilation time for a Regex this simple is very small and this scenario completely justifies the use of RegexOptions.Compiled.

You can also pull this off with the Lazy type new to C# 4.0...

public static Lazy<Regex> LibraryTagsRegex = 
    new Lazy<Regex>(() => new Regex(@"^library/tagged/(?<Tags>.+)", RegexOptions.Compiled));

Then you'd just reference LibraryTagsRegex.Value in your code.

Faster Regex Syntax Highlighter

noreply@blogger.com (Steve Wortham) — Tue, 20 Mar 2012 16:58:00 +0000

After the recent performance improvements to the analyzer I found that the next bottleneck was the regex syntax highlighter. You know, that's what paints your regular expression pretty colors.

The slowness has probably affected fewer than 1% of the Regex Hero population. I say that because it was only really perceivable when dealing with a regular expression over 2,000 characters long.

Nevertheless, I had an idea for how I can improve it. The slowness had nothing to do with parsing speed, and everything to do with how I was drawing the characters. I was dynamically adding characters in colored sections to a single text block to create the colored effect. This, as it turns out, is not optimal. So what I did is I created text blocks on top of eachother (one for each color), and then simply assign the appropriate text values to each one.

For example, the text blocks might be composed of...

test
( )
\d\w
+

And since they're all on top of eachother this is what you see...

test(\d\w)+

The effect is exactly the same as it was before, but this is at least 3 times faster.

Faster Regex Analysis

noreply@blogger.com (Steve Wortham) — Mon, 19 Mar 2012 00:18:00 +0000

Today I got rid of the tree view in the analyzer in favor of a staggered listbox. It was kind of cool to be able to expand or collapse individual items in the tree view, but it came at a cost. The tree view is extremely slow when you're constantly updating it. And of course, since everything in Regex Hero is supposed to happen in real-time, the tree view had to go.

With today's changes the analyzer feature is now at least 5 times faster. And with the staggered listbox we can still easily visualize the nested nature of a regular expression, as you can see in the example below...

Optimizing Your Regular Expressions

noreply@blogger.com (Steve Wortham) — Sat, 17 Mar 2012 23:26:00 +0000

Regular expressions will backtrack. That's an unfortunate thing about them because backtracking can be slow. And in certain (rare) cases the performance can become so awful that executing the regular expression against a relatively short string could take over a minute. There's a good article about catastrophic backtracking over at regular-expressions.info.

And today I created a video about all of this called Regex Lesson 5: Optimization. In the video I start with a very poorly written regular expression and make several improvements to it, using the benchmarking feature along the way. By the end of the video I make the regular expression over 3 million times faster.

In addition, today's update to Regex Hero provides a little message in the event that you encounter a regular expression that takes over 10 seconds to evaluate...

And then last of all, I changed the benchmarking feature a bit. In the past it would simply test your regular expression against your string and iterate over the matches. It would repeat this process as many times as it could in 1 second. The trouble was that it did the same thing even if you had the Replace or Split tab selected. But now the benchmarking will actually do replacement operations when the Replace tab is selected, and it'll do split operations when the Split tab is selected.

Benchmarking Bug Fix

noreply@blogger.com (Steve Wortham) — Fri, 02 Mar 2012 02:37:00 +0000

Today's update is a small one. I discovered that under certain situations the benchmarking feature in Regex Hero would fail and return NaN values. I solved this problem today so we shouldn't be seeing that again.

I also made a couple recent changes to the site for better performance. For one, I switched from the Rackspace CDN I was using back to Amazon CloudFront. Amazon's CDN isn't necessarily the fastest in all countries, but it's very reliable and consistent. Then I extended the cache/expiration settings for the site's CSS file and the loading screen for Regex Hero so repeat visitors should enjoy improved responsiveness.

Asynchronous Regex Matching and Highlighting

noreply@blogger.com (Steve Wortham) — Thu, 06 Oct 2011 18:09:00 +0000

I came across a question on StackOverflow the other day where someone was trying to find the culprit for an unusually slow running regular expression. In fact it'd take around 30 seconds to execute. This was a rather extreme case of catastrophic backtracking. With just a few minor tweaks someone was able to drastically improve the performance, making it about 48,000 times faster. Yeah, pretty drastic and it really illustrates the importance of running a simple benchmark to test any regular expression that'll see heavy use.

It's rare that someone will write such a poor performing regular expression, especially by accident. But nevertheless, this circumstance is one where Regex Hero failed miserably. The trouble is that the regular expression was evaluated synchronously as you type. So if you're dealing with a slow running regular expression, this would actually hang the UI temporarily until it's finished. It was an ugly thing. But no more. As of today, Regex Hero now evaluates the regular expression on a separate thread, returns the results, and then highlights the matches. This asynchronous approach is much more user friendly as the UI is always responsive. In addition to this, by running the regular expression on a separate thread from the UI, Regex Hero is able to take better advantage of multi-core processors, actually improving the overall performance of the application. These are all good things. I hope you enjoy it.

Alternating highlighting, new string copy options, and more

noreply@blogger.com (Steve Wortham) — Tue, 16 Aug 2011 22:57:00 +0000

Alternating Highlighting
I got some great feedback recently. First, magneticmail on GetSatisfaction suggested that I create two colors for Regex Hero's highlighting: an odd color and an even color. This had crossed my mind before but I hadn't really given it much thought. My initial concern is that introducing a new color could cause some confusion. What does the color mean? But after thinking about it, implementing it, and playing with it myself, I think it's simple enough. Once you actually write an expression that has 3 or more matches, it becomes obvious that the two colors simply alternate to provide some visual distinction. And the value that the visual distinction brings with it outweighs any potential confusion, I believe. So, thank you magneticmail for the suggestion. It's a simple change, but hopefully a change for the better. Let me know what you guys think in the comments.

Move to target string and start a new expression
This idea came from the author of RegexRenamer. The idea is to improve the workflow slightly when using the replace functionality to make incremental changes to a block of text. So you perform your replace operation, click the "Final String" heading, and then click "Move to target string and start a new expression". This will do just what it says, moving the final string to the target string, and clearing out the regular expression and replacement strings so you can start your next replacement operation.

Copy as a C# String or Copy as a VB.NET String
The .NET code generation feature has always created C# or VB.NET friendly code snippets, with properly escaped strings. Now you can actually grab properly escaped C# or VB.NET strings from any of the 4 subheadings: Regular Expression, Replacement String, Target String, or Final String.

Skype Screen Sharing with Steve

noreply@blogger.com (Steve Wortham) — Tue, 09 Aug 2011 20:44:00 +0000

I've had good Regex Hero feedback slowly trickle in through GetSatisfaction, email, and a few phone calls over the past couple years. It's great to hear from you guys as I've been made aware of problems that I never knew I had.

And so in the spirit of improving Regex Hero, I want to try something new. I'm inviting all Regex Hero fans to contact me via Skype for a 30 minute one-on-one screen sharing session. This will be an opportunity for me to learn about problems you're having with Regex Hero and help out any way I can. Perhaps you're having trouble figuring out how to do something very specific in Regex Hero. It could be that a feature is missing, or simply isn't as obvious as it should be. Or perhaps you're having trouble with a regular expression and just need a little help. In either case, you'll share your screen with Regex Hero open as we dive into it. Email me if you're interested and we'll set up a time.

What you'll need...

Skype 4.0 or greater
Speakers and a microphone, or a headset
A computer capable of running Regex Hero

Bug fixes around undo/redo and copy/paste

noreply@blogger.com (Steve Wortham) — Sun, 12 Jun 2011 19:52:00 +0000

I found a report of a case recently where Regex Hero would sporadically cause Chrome to crash. It was in a comment on StackOverflow, and I'm lucky to have found it. I didn't have much to go on, but I take reports like this seriously.

First of all, I had never seen this actually happen before. But I began by banging on things trying to make anything and everything break that I possibly could. My method is perhaps a bit crude and it simply takes time and some knowledge of what's going on in the code to get anywhere.

Here's what I managed to fix, in order of discovery:

There was a layout problem involving the minimum vertical height of Regex Hero. After you shrink the window beyond a certain point a scroll bar appears so as not to fold the UI on top of itself. Well there was a logic problem in this calculation which could actually throw an error in certain circumstances. The error was being trapped though, and couldn't have caused the crash.
The expand/collapse options button along the right hand side of the app had an unusual bug where, after clicking, the tooltip would be reused for other UI elements. I fixed it by using just one button rather than hiding/showing two different ones. Again, this was a weird bug but not one that could've caused the crash.
Whenever you right click text and choose Cut/Copy/Paste, Regex Hero accesses the clipboard programmatically. On first use, this will throw a security warning from Silverlight (there's no way around that). The trouble is that if you choose not to allow Regex Hero access to the clipboard, Regex Hero would kind of fall on its face and not handle that condition gracefully. Again, an exception would be thrown, but it was caught and couldn't have caused anything to crash. I improved this process a bit and I now provide a follow up dialog.
I took a couple days and came back to this. And just yesterday I finally reproduced the problem. The problem, it turns out, comes from another bug in the RichTextBox. And it's not isolated to Chrome. The same behavior occurs in IE9. Regex Hero was programmatically replacing line feeds with carriage returns when loading your previously stored text from isolated storage. I do this to ensure consistent behavior within the app. A separate string variable assigned to the text value of each textbox is then reshaped as necessary depending on if you have the CrLf option checked within Regex Hero. However, if you have more than 10 lines of text, then cut the top 9, then hit undo, the built-in undo functionality fails. The RichTextBox undo system seems to have a serious problem with carriage returns. It can't seem to fully restore from its history, only actually rendering 3 lines of text. The rendering pipeline then seems to be out of sync with what the text value actually equals. It's odd. And it causes Silverlight to freeze, sometimes bringing the whole browser down. I'm reporting this to Microsoft. My solution is to now replace all carriage returns with line feeds instead. Behind the scenes we have the same effect and the app works as it should, but it effectively avoids this bug.

Bug fixes concerning tabs and syntax highlighting

noreply@blogger.com (Steve Wortham) — Sat, 30 Apr 2011 18:04:00 +0000

The tab spacing bug

This problem stems from a bug in the RichTextBox. Basically, the tab spacing in the RichTextBox is inconsistent and very strange. Sometimes a tab will be bigger than a space, and sometimes it'll be smaller than a space. I have informed Microsoft of the bug and I'm hoping they'll fix it for Silverlight 5.

What this means for Regex Hero is that tabs would throw the highlighting out of alignment. So my fix was to override tabs with spaces. I had made this change weeks ago. But today's release has this same treatment on pasting tabbed text.

This isn't ideal and basically means the \t regular expression will never match anything in Regex Hero. If I can find a better workaround I will do it. But at least today's fix means that the yellow highlighting will always be in alignment and is reliable again.

To help ensure Microsoft fixes this bug in the RichTextBox in a timely manner, you can help by up-voting the bug here on MS Connect.

Syntax highlighting

The syntax highlighter had a minor bug with back slashes. The following regular expressions are valid, but the syntax highlighter was painting them red...

(abc\\)

[abc\\]

It was seeing the \ before the ending parenthesis, escaping the parenthesis, and then thinking that these constructs were not closed. It didn't look far enough back to see the \\. So I fixed the bug, and now it works properly.

Syntax Highlighting

noreply@blogger.com (Steve Wortham) — Sun, 06 Mar 2011 05:18:00 +0000

Syntax Highlighting

This feature was requested back in 2009. I didn't do it back then because I wasn't sure how I was going to do everything I wanted with it. Ever since the beginning I've always said that if I can't implement a feature right, then I wouldn't bother with it.

But I've learned since then and this week I gave it a try. It took a little experimenting to find the right approach, but I'm pleased with the end result.

The syntax highlighter is built off of my existing parsing engine. In addition to highlighting basic constructs, it'll also detect unclosed parenthesis or brackets and paint them red. So for example (abc(def) would all be red. I think this makes it easier to find mistakes. And I hope you enjoy it.

In addition to this I've fixed a few bugs and made a few improvements:

I improved code completion when working with a multi-line regular expression. The down arrow key now responds more like you'd expect a good code completion system would.
I optimized some initialization code and sped up the app slightly.
I was able to remove an unneeded assembly. The app is now about 40KB smaller.

Which Trial Experience Do You Prefer?

noreply@blogger.com (Steve Wortham) — Thu, 17 Feb 2011 15:33:00 +0000

I've tried a couple different variations of trials over the past couple years. But I've never asked you guys which you prefer.

Regex Hero Blog

Regex Analysis Bug Fixes

Regex Hero Professional: Improvements and Pricing

"Redo" on a Mac, and a Group Name Warning

C# Strings and Code Generation Bug Fixed

Optimized Memory Consumption

ASP.NET MVC DataAnnotations and the RegularExpressionAttribute

Why is this?

Improved TextBoxes With Better Whitespace Support

Now Supporting Facebook and Twitter Logins

New Benchmarking Features and a New Homepage Design

Highlighting for Regex Group Pairings

Improved Regex Code Completion and Bug Fixes

New Regex Parser, Improved Syntax Highlighter, and More on the Way

Faster Load Times for Regex Hero

A Quick Tip About Using RegexOptions.Compiled

Faster Regex Syntax Highlighter

Faster Regex Analysis

Optimizing Your Regular Expressions

Benchmarking Bug Fix

Asynchronous Regex Matching and Highlighting

Alternating highlighting, new string copy options, and more

Skype Screen Sharing with Steve

Bug fixes around undo/redo and copy/paste

Bug fixes concerning tabs and syntax highlighting

Syntax Highlighting

Which Trial Experience Do You Prefer?

Which Regex Hero trial experience do you prefer?