On 10/8/07, Jenda Krynicky <[EMAIL PROTECTED]> wrote:
> From: "Chas. Owens" <[EMAIL PROTECTED]>
> > On 10/3/07, Jonathan Lang <[EMAIL PROTECTED]> wrote:
> > snip
> > > Chas shows one possibility. However, that approach generally involves
> > > slurping the entire file into the perl script, applyin
From: "Chas. Owens" <[EMAIL PROTECTED]>
> On 10/3/07, Jonathan Lang <[EMAIL PROTECTED]> wrote:
> snip
> > Chas shows one possibility. However, that approach generally involves
> > slurping the entire file into the perl script, applying the regex to
> > the whole thing, and then spitting the result
on rewriting grep
in perl so that it ignores the contents of /* and */ comments?
Instead of rewriting grep, consider writing a comment filter. Have it
read from standard input and write to standard output; pipe the file
that you want to grep into it, and pipe its output into grep.
Thanks, but if
siegfried wrote:
> Thanks, but if I am piping from stdin to stdout I see two problems:
>
> (1) how do I implement the -n flags that tell me the line number and
> file name where the matches are
Well, as long as you're only piping one file at a time, the line
number part isn't a problem; but I see
>
>siegfried wrote:
>> I need to search large amounts of source code and grep is not doing the
job.
>> The problem is that I keep matching stuff in the comments of the
>> C++/Java/Perl/Groovy/Javascript source code.
>>
>> Can someone give me some hints on wher
On 10/3/07, Jonathan Lang <[EMAIL PROTECTED]> wrote:
snip
> Chas shows one possibility. However, that approach generally involves
> slurping the entire file into the perl script, applying the regex to
> the whole thing, and then spitting the result out again. From what I
> understand, this genera
siegfried wrote:
> I need to search large amounts of source code and grep is not doing the job.
> The problem is that I keep matching stuff in the comments of the
> C++/Java/Perl/Groovy/Javascript source code.
>
> Can someone give me some hints on where I might start on rewriting gr
ints on where I might start on rewriting grep in
> perl so that it ignores the contents of /* and */ comments?
snip
perldoc -q comments
will get you halfway there
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/
me some hints on where I might start on rewriting grep in
> perl so that it ignores the contents of /* and */ comments?
>
> Thanks,
> Siegfried
>
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> http://learn.perl.
I need to search large amounts of source code and grep is not doing the job.
The problem is that I keep matching stuff in the comments of the
C++/Java/Perl/Groovy/Javascript source code.
Can someone give me some hints on where I might start on rewriting grep in
perl so that it ignores the
[EMAIL PROTECTED] wrote:
> Help a perl newbie coding for a bioinfo guy please.
>
> I have a shell script that contains the following code
>
> # $1=sequence_file, $2=input_file, $3=output file, $4=chain.
>
> if [ $# != 4 ]
> then
> echo "Usage: parse_pdb.sh sequence_file pdb_file output_f
[EMAIL PROTECTED] wrote:
Help a perl newbie coding for a bioinfo guy please.
You appear to have misunderstood the purpose of this list. It's *not*
a "write my Perl program for me for free" list.
If you want to learn Perl:
http://learn.perl.org/
If you want somebody who does the work for you:
Help a perl newbie coding for a bioinfo guy please.
I have a shell script that contains the following code
# $1=sequence_file, $2=input_file, $3=output file, $4=chain.
if [ $# != 4 ]
then
echo "Usage: parse_pdb.sh sequence_file pdb_file output_file chain"
exit
fi
TEMP_FILE=$$;
On Feb 3, Cy Kurtz said:
>I'm trying to write a little program to take all of the fun out of the
>daily jumble.
>
>My plan is to get a sequence of letters from the user, move the letters
>around and bounce the resulting sequence of letters off of a spell check
>dictionary until the program generat
Cy Kurtz wrote:
>
> I'm trying to write a little program to take all of the fun out of the
> daily jumble.
>
> My plan is to get a sequence of letters from the user, move the letters
> around and bounce the resulting sequence of letters off of a spell check
> dictionary until the program generates
Cy Kurtz wrote:
I'm trying to write a little program to take all of the fun out of the
daily jumble.
My plan is to get a sequence of letters from the user, move the letters
around and bounce the resulting sequence of letters off of a spell check
dictionary until the program generates an English wor
I'm trying to write a little program to take all of the fun out of the
daily jumble.
My plan is to get a sequence of letters from the user, move the letters
around and bounce the resulting sequence of letters off of a spell check
dictionary until the program generates an English word.
When I call
17 matches
Mail list logo
