Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!oliveb!orc!mipos3!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.lang.perl
Subject: <STDIN> =~ /pattern/ (was Re: any chance of real multi-dimensional arrays?)
Message-ID: <1990Feb21.205125.21961@iwarp.intel.com>
Date: 21 Feb 90 20:51:25 GMT
References: <1990Feb20.225434.2045@athena.mit.edu> <7125@jpl-devvax.JPL.NASA.GOV>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Distribution: usa
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 24
In-Reply-To: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall)

In article <7125@jpl-devvax.JPL.NASA.GOV>, lwall@jpl-devvax (Larry Wall) writes:
| However, you should know that I'm strongly considering letting you do
| pattern matching against the input symbol:
| 
| 	<STDIN> =~ /^pattern/;
| 
| If you do this currently it will just read one line and pattern match on
| it.  I'm considering making it read any extra lines it needs to satisfy the
| pattern match.  Except that this could break existing scripts...

What's wrong with

	($_ = <STDIN>) =~ /^pattern/

?  In fact, I think I've already used it a few times...

Maybe you should turn Perl into Icon.  Then we'd have *everything*. :-)

echo Just another Perl hacker,|perl -e 'print$1if($_=<STDIN>)=~/^(.*)/;'
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Welcome to Portland, Oregon, home of the California Raisins!"=/