At 09:41 AM 02/22/02 +0800, Stas Bekman wrote:
Is that doable? If that is, will that solve our problem?
It's doable, but I'm not sure if it solves the problem ;)
why not?
I think too much junk will be returned that is not perl code, but just punctuation. Have to see what happens.
I'm still not sure how to index -- that is, what characters to say are allowable in words.
I suppose you want more indexed than just the example code blocks, that is, if $| is in text then it should be indexed, right?
let's see what chars we want, which aren't really punctuation.
We can safely leave out '.,?!', but we want to keep '->$%@:*[]' I think that's all. None of these is really used in normal text (but '-', but we want it to be indexed for $r->foo). Not sure about '()', I'd want these to be indexed, but that's not very good since it's an active punctuation used in text.
I guess that if we won't be able to handle it altogether, this is the way to go.The other option would be on the results page to have a check box:
_ I'm searching for perl code
But ideally we should a single smart search.
Try compiling the query to see if it's perl code? Eh, maybe not such a safe thing ;).
;) sure not
I think most people searching for perl code can handle dealing with a check box.
I say let's leave it out for now, and concentrate on normal text with perl strings like foo::bar, $r->foo, @array, etc. '->$%@:*[]'. I believe this will satisfy 99% of the searches.
What do you think?
_____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
