You really should enable warnings in your code...

Your first example: $/ = m/\d..../;.
What this really means: $/ = ($_ =~ m/\d..../);.
That is: you are first doing a match on $_ with the regex m/\d.../ and then assign the result of the match to $/.

Your second example: $/ == m/\d.../;.
What this really means: my $foo = ($_ =~ m/\d..../);$/ == $foo;.
That is: That is: you are first doing a match on $_ with the regex m/\d.../ and then comparing the result of the match with $/ in a void context. (=> useless comparison)

What you want to do is not possible with $/. $/ has to be a string (or a reference to a integer). It can not be a regex.

What you could do is set $/ to undef; then read from the file and then use: while ($data =~ m/\d.../g) { ... }

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.