Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Inspired by Loops' suggestion, I made it a bit more flexible and easier to use. As you will note, the position information is directly extracted from the regex variables without the need for a second regex. It should be a little bit faster as well.
use Modern::Perl '2014'; my $delim = '&'; my @findme = ( '.#', '#', '..#\.' ); my @data = <DATA>; chomp @data; my $data; $data .= "$delim$_" for @data; for my $column ( 0 ... length( $data[0] ) - 1 ) { my $regex = build_regex( $column, @findme ); while ( my $result = $data =~ m/$regex/g ) { my $row = ( $-[0] / length( $data[0] . $delim ) ); say "Hit at row $row, column $column"; } } sub build_regex { my $column = shift; my @pattern = @_; my $pre = '[^' . $delim . ']{' . $column . '}'; my @accumulator; push @accumulator, quotemeta($delim) . $pre . $_ . '[^' . $delim . + ']*' for @pattern; my $regex = join '', @accumulator; return qr/$regex/; } __DATA__ #..#.....#. ..#...##... .#....#..## #..#....#.. ..#...#..#. .......#.#. ...........


A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

My blog: Imperial Deltronics

In reply to Re: Two-dimensional match/regex? (2) by CountZero
in thread Two-dimensional match/regex? (2) by rsFalse

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others about the Monastery: (4)
As of 2023-12-02 05:33 GMT
Find Nodes?
    Voting Booth?
    What's your preferred 'use VERSION' for new CPAN modules in 2023?

    Results (13 votes). Check out past polls.