Front page | perl.perl5.porters |
Postings from January 2012
On Tue, Jan 03, 2012 at 05:22:50PM +0000, Nicholas Clark wrote: > On Tue, Jan 03, 2012 at 09:16:23AM -0800, David E. Wheeler wrote: > > On Jan 3, 2012, at 2:49 AM, Nicholas Clark wrote: > > > > > For the next 12 days Google Codesearch will report that *nothing* uses it. > > > > > > After which, Google becomes a bit less useful for me. Have Bing or Yahoo! > > > written a codesearch yet? > > > > Tried Koders? > > > > http://www.koders.com/ > > > > I rarely use code search, so I honestly don't know if it's an effective replacement. Hope so. > > Interesting. Thanks for the the suggestion. > > Sadly it fails on the first test. Badly. > > Not only can't it search on the fixed string POSIX::SigRT > It doesn't even generate any feedback that it can't, just its title page. > > It *does* work if I wrap it in quotes. "Spoke too soon". #11906 Look at the error message! Look at the error message! In this case, read the output. A search for "POSIX::SigRT" throws up results seemingly for POSIX. I *think* that they are all instances of POSIX.pm, so the files do contain POSIX::SigRT within them, but the section it presents as a highlight has the POSIX of C<package POSIX;> emboldened. So, um, fail. I hope it gets better. It's going to need to, to be useful. Nicholas ClarkThread Previous | Thread Next