User Ratings

★★★★★
★★★★
★★★
★★
0
0
0
0
1
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • Previous review was pretty close - though there are usage strings and such that aren't too hard to find: "msearch -s(-e) <search string 1>+...+<search string 10> -f <filename>" Will show with command line -h ... But I found that without using -s or -e, it returned no results, and with -s, it returned a LOT of lines that didn't match - I broke out after it spewed many screens full. It's also true that the code is very difficult to read - virtually *all* variables and functions are 2-4 letters, maybe with an underscore. It's not huge, so you could probably figure it out without much trouble if you ran it through a debugger.. and it does seem to need some debugging. That, with the handful of tiny comments, including the ones that are just commented out printf's... makes it hard to even want to work with the code. (at this time) Maybe if the author adds some comments/docs/better variable names... or some such thing.
  • Previous
  • You're on page 1
  • Next