I know mod_rewrite used “$1” to print what was found be the prior regex. I am really a regex noob having only used them a few times in PHP, Perl and Apache mod_rewrite so this was all new to me. The problem came when I wanted to do the replacement. I drafted a regular expression that would find only what I was looking for. Fortunately all the the “PC” prefixes were intact but the number only entries were not (that data was collected into an Excel file with cells set to the “number” format instead of “text”). First, I knew that the correct format should be something like this: 0# or pc0#. Together, Extended and Regular Expression search modes give you the power to search, replace and reorder your text in ways that were not previously possible in. Rather than scripting the fix I figured notepad++ would do the trick. The problem was that this format was not ready to be inserted into our database. The data was a list of our internal PCs and their serial number. Perl regular expressions are the default behavior in Boost.Regex or you can pass the flag perl to the basicregex constructor, for example: // e1 is a case sensitive Perl regular expression: // since Perl is the default option theres no need. I was working with tabular data that looked something like this: The Perl regular expression syntax is based on that used by the programming language Perl. From time to time I would use a regex to search and then replacing everything that was found. When using find and replace in the past I stuck mostly to the basics. I have been using if for years but just recently have come to love the program even more. It’s easy to use, includes syntax coloring for just about anything, folds code nicely and even supports regular expression find and replace features. When scripting or manipulating text data I prefer using notepad++.
0 kommentar(er)
