Your second question is much easier: Yes. Regular expressions can be built from any string, including those supplied by users. Generally, you should use quotemeta or the \Q and \E markers to make sure the string is free from regular expression meta characters like *, ., and more evil eval-type expressions. In your case, you could also check that the string is a valid nt sequence:
my $string = quotemeta shift;
die "Not a valid nucleotide sequence" if $string =~ /[^AGTC]/;
As for the first question, one way would be to build a regex for each possibility. An example:
my $string = "TGAT";
my @nts = map {
my $tmp = $string;
substr $tmp, $_, 1, '.';
$tmp;
} (0 .. length ($string) -1);
my $groupings = join '|', @nts;
my $sample = "TGATTGGAATGTTAGAT";
while ( $sample =~ /($groupings)/go )
{
print "Matched $1 ending at position ", pos $sample, "\n";
}
@_=qw;
Just another Perl hacker,;
;$_=q=print
"@_"= and eval;
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|