DV Hardware software and download news

Improvements:

• Create: Exporting to HTML no longer results in an HTML page with a needless scroll bar.
• Create: The fact that _ is an error in the .NET regex flavor is now indicated with a specific error message rather than a generic "invalid token" error message.
• Create: When flagging < and > in flavors that don't support these as word boundaries, indicate how to match them as a literal character in addition to saying such word boundaries aren't supported.
• Debug: The Debug tab now shows an explanation instead of only white space when the regex debugger hasn't been used yet.
• Library: Use the label the regex has in the History list as the default description when adding a regex to the Library.
• Portable installation: Lists of files previously opened files should survive changing drive letters.
• Use: When converting a regex to Perl, always escape $ signs in character classes to prevent unintended variable interpolation in Perl. Perl tries to be clever about interpreting $ signs in regular expressions. Depending on where a $ occurs, it will be treated as the start of a variable name, or as the regex anchor $. An escaped $ is always treated as a literal $. Therefore, RegexBuddy can't just escape all $ signs when formatting a regex as a Perl m// operator. Escaping $ signs in character classes when converting the regex to the Perl flavor works around this limitation.

Bug fixes:

• Copy: Basic-style strings missed the _ line continuator when RegexBuddy converted a multi-line free-spacing regular expression into a concatenation of multiple strings.
• Create: [}] is indicated as matching U+0000 rather than a literal }.
• Create: XML character class subtraction immediately after a hyphen was not handled correctly. The JGsoft flavor treats the first hyphen in [a--[x]] as a literal. The .NET and XML flavors treat the first hyphen as an error, because the range is incomplete.
• Debug: Clicking on the white space in the debug tab before actually debugging the regex caused a harmless access violation.
• Flavors: Backslashes were not properly treated as literal characters with the .NET and JavaScript replacement text flavors.
• Flavors: Python does not support to insert the whole regex match into the replacement text, but does support g<0>. RegexBuddy did correctly support g<0> in the regex and on the Test tab, but did not convert or $0 into g<0> on the Use tab when generating a Python source code snippet from a regex in another flavor.
• Paste: Pasting a regex in free-spacing mode that is a concatenation of multiple string in a string format that doesn't support multi-line strings did not properly interpret the line break characters in the string that are added to the string by the Copy command (as of 3.2.0).
• Regex: An character class with two subtracted classes such as [x-[x]-[x]] caused RegexBuddy to get stuck on access violations if the current flavor supports character class subtraction (JGsoft, .NET, XML Schema, and XPath). The second subtraction is now correctly marked as an error for these flavors.
• Test: , and did not work in character classes if the flavor was set to Tcl or one of the POSIX or GNU flavors. E.g. the regex a[ ]*b did not match a and b when separated by a line break.
• Test: Listing the results for a capturing group, turning on automatic update, and then removing the capturing group from the regex, caused an error.
• Test: The POSIX classes [[:space:]] and [[:blank:]] did not match tab characters.
• Use: Regular expressions using XML or .NET character class subtraction lost the -[ characters that begin the character class subtraction.
• Vista: RegexBuddy would lock up under Windows Vista if you edited the regular expression while the last List All/Replace/Split command on the Test tab was still running.