Regular expressions are a powerful feature of the FindStr utility. However, they can also prove frustrating to use in some cases because the documentation Microsoft provides is lacking in good examples and difficult to follow. You can see some usage instructions for FindStr starting on page 82 of the Windows Command-Line Administration Instant Reference .
A reader recently commented that there is a problem with the dollar sign ($) regular expression. It must actually appear after the search term to be useful. Of course, the problem is creating a test file to sufficiently check the use of the regular expressions, so I came up with this test file:
Now, let’s perform some tests with it. Here is the result of some tests
that I performed using this test file and FindStr regular expressions:
The first test case shows what happens when you try
the command on page 82 of the book. It appears to work, but you’ll see
in a moment that it actually doesn’t. Let’s take the two parts of the
regular expression apart. Using FindStr “^Hello” *.TXT seems to work just fine. However, the command FindStr “$World” *.TXT doesn’t produce any output.
Only when the $ appears after World does the command produce an
output. Consequently, page 82 should show the rather counterintuitive
command, FindStr “^Hello World$” *.TXT to produce the correct output.
It’s also important to be careful about making generalizations when
using FindStr. For example, when working with the test file originally
shown in this example, the FindStr /B /C:”Hello World” *.TXT command produces the same output as FindStr “^Hello” *.TXT as shown here:
If you change the test file like this though:
you’ll see these results:
As you can see, you must exercise care when using FindStr to obtain the
desired results. What other odd things have you noticed when using
regular expressions with FindStr? Add a comment here or write me at John@JohnMuellerBooks.com to let me know.
At least some readers try to hand type the source code found in C++ All-In-One Desk Reference For Dummies. Working with source code when you’re learning a new programming language is hard enough; typing it in by hand and getting a good result is nearly impossible in many cases. I recommend that you always use the code from the book’s CD so that you can avoid potential typos. If you experience problems using the code from the book’s CD, please query me at John@JohnMuellerBooks.com; there may be something that isn’t set up correctly on your system. The examples on the CD should compile and work, but I always emphasize the word “should”
because each system and setup is slightly different (making things exciting for all of us).
To use the code on the CD, follow these steps:
- Copy the Author folder from the CD to your hard drive.
- Right click the Author folder and choose Properties from the
context menu. You’ll see the Author Properties dialog box.
- Clear the Read-only check box. Click OK. You’ll see a Confirm
Attribute Changes dialog box.
- Click OK. Windows will remove the read-only attribute from all
of the files. You’re ready to begin using the source code supplied with the
To use a particular example, navigate to that examples folder under the Author folder. Say you want to work with the AddInteger example in Book I Chapter 2. You’d navigate to the \Author\BookI\Chapter02\AddInteger. To open the project, simply double click the associated .CBP file. In this case, you’d double click the AddInteger.cbp file and CodeBlocks will open with the example loaded and ready for you to work with.
I’ve been thinking about something for quite a while now. For me, there is nothing better than sitting by my wood stove, coffee cup next to me, reading a favorite book. Of course, I’m talking about a hard cover or paperback book. Nothing quite matches the feel and smell of paper, especially when you’re reading a book for leisure. The hours I’ve spent reading books have been pleasurable to the extreme. I’m transported to worlds of mystery in some cases, worlds of the future in others. Fantasy, science fiction, techno-thriller; they all hold a certain thrill.
It’s a different matter when I start working with technical material. As you might imagine, I’ve collected quite a few technical books in 23 years. In fact, I’ve discarded quite a few books during that time; a mountain of technical knowledge that no longer seems important to anyone but a historian. That is, until I figure out that I discarded the one antique I really did need for a particular project. Suddenly I’m looking somewhere, anywhere, for that book. Even when I know where the book resides and I peruse its well thumbed pages by instinct, finding just the right information can prove difficult.
Unfortunately, no book cataloging system in the world will solve my problem. I could catalog each of my hundreds of books and still not find the information I actually need with any speed. Of course, the ability search quickly is one of the benefits of electronic storage. If I had my books in electronic format, I might avoid the hours upon hours of search time for that one piece of information I actually need. Then again, I’ve accidentally found many pieces of useful subsidiary information during such searches, so it’s not possible to discount paper as unworthy. Still, speed is of the essence while I’m working on my next project.
For now, it appears that my future will rely on two media for books: paper for leisure and electronic for work related materials. It’s a sad thing for me to admit, but the paper book has become a bit too cumbersome for a world where speed is prized above all. What about you? What do you feel about e-books?