comment on

The \G anchor does no harm, but is not necessary in the OPed example case (/g modifier causes match position to be preserved in void/boolean/scalar context):

Win8 Strawberry 5.8.9.5 (32) Thu 12/17/2020 23:11:18
C:\@Work\Perl\monks
>perl -Mstrict -Mwarnings
my $string = " info

                    info


                100 - 2000


                  Kent";
my $word = "info";

$string =~ /$word\s*?(\S+)/g;
my $next_word = $1;     my $nwo = $-[1];  # offset of start of capture
$string =~ /\s*?(\S+)/g;
my $next_word_2 = $1;   my $nwo_2 = $-[1];

print "The next word after $word is $next_word @ $nwo \n";
print "The next word or number after $next_word is $next_word_2 @ $nwo
+_2 \n";
^Z
The next word after info is info @ 27
The next word or number after info is 100 @ 50
[download]

(Repeated words are also handled properly with/without \G.)

Give a man a fish: <%-{-{-{-<

In reply to Re^2: getting next word or number after another by AnomalousMonk
in thread getting next word or number after another by bigup401

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.


Clear questions and runnable code get the best and fastest answer
	PerlMonks