Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hplabs!hpcc01!weisberg
From: weisberg@hpcc01.HP.COM (Len Weisberg)
Newsgroups: comp.lang.perl
Subject: program, __END__, data  all in one file
Message-ID: <12150001@hpcc01.HP.COM>
Date: 23 Jul 90 23:00:40 GMT
Organization: HP Corporate Computing & Services
Lines: 37

Larry wrote in another string:
>
> after the next patch you'll be able to
> run this article through perl -x and it will print out "howdy".
>
> #!/usr/bin/perl
> $_ = <STDIN>;
> print;
> __END__
> howdy
>
> Think a little about the possible implications of that.

Well, you could write a ksh script like:

{ cat <<END_OF_PERL_PROGRAM
  ...
  ...  perl code goes here ...
  ...   (for a filter using <STDIN>  and <STDOUT> )
  ...
__END__
END_OF_PERL_PROGRAM

shell | commands | and | stuff | to produce | input to perl program
}  |  perl -x \ 
| other | commands | to process | output from perl program


Now perhaps I should do it all in perl, but then again, maybe not.
It's nice to have the option of having a perl filter in a self-contained
ksh script without the dreaded -e stuff.

Larry, was this prompted by my question to you in Mountain View the other day?

Thanks, 

- Len Weisberg - HP Corp Computing & Services - weisberg@corp.HP.COM