|There's more than one way to do things|
Re^3: ack 2.0 has been released (?wishlist?)by Anonymous Monk
|on Apr 29, 2013 at 16:14 UTC||Need Help??|
Do you have an actual use case for these? Or are you just imagining things that might possibly potentially be cool in the future maybe?
Um, what? That was it, that was my actual use case, use ack in a program for the same reason I'd use ack from the commandline , to get a list of files, or get a list of lines, or get a list of files and lines
only the iterator portion inspired by File::Find::Rule/Iterator::Files iteration interfaces is a might-as-well-implement-it-if-you-re-implementing-it-thought-of-it-now
The most important thing ack does that I can't do as trivially /easily myself already is all the filetype stuff
that's the killer feature ack has over grep, is simple/easy filetype/mimetype ... recognition with --perl --cpp ...
Sure, I could cobble something together using MIME::Type/mmagic... and file::find,
ack does a good job on the cli, the interface is compact , I know it already, no need for File::Find::Rule->oopy->verbosity or all find2perl reams-of-machine-generated-stuff or different-interfac
compact interface for commandline? why not compact interface for commandline for our programs?
Is it too obvious? Too useful?