HDTenEightyP/NetNews huggingface dataset:
From: brossard@sic.epfl.ch (Alain Brossard EPFL-SIC/SII)
Newsgroups: comp.lang.perl
Subject: Why is <...> going to stdout?
Date: 7 Nov 92 14:34:09 GMT


	I have the following piece of code which somehow outputs to
stdout and I can't figure out why!  I'm it didn't use to do this before
some extensive changes to other parts of my script.

print STDERR "Before\n";
    foreach $f ( <$ftp_dir/${patch_ID}*>,
             <${loc412}/${patch_ID}*>,
             <${loc413}/${patch_ID}*> ) {
	next if $f =~ /\*$/;
        next if $f =~ /$patch_id/o;
        next if $f =~ /$patch_ID-$prev_rev/o;
        unlink $f;
    }
print STDERR "\nAfter\n";


	What I get on stdout (or stderr?) is:

Before
/u/ftp/pub/sun-patches/100483-02.README/u/ftp/pub/sun-patches/100483-02.tar.Z/export/mnt/4.1.2/100483-02/export/mnt/4.1.2/4.1.3/100483*
After


   I'm sure it is coming from this piece of code because I put a print
before and after to bracket the problem.

	This occur on sunOS 4.1.3 using perl 4.019 and perl 4.035.


					Alain Brossard
					brossard@sic
From: lwall@netlabs.com (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: Implicit close of piped file handles
Date: 7 Nov 92 00:36:38 GMT
Organization: NetLabs, Inc.

In article <MEISSNER.92Oct28222939@curley.osf.org> meissner@osf.org (Michael Meissner) writes:
: Naively, I expected that perl would wait for the child to terminate
: when closing the pipe in the exit.  Obviously, a simple work around is
: to put:
: 
: 	close (STDERR);
: 	close (STDOUT);
: 
: just before the exit, but I think that perl's exit should do it
: automatically.

If I did that, how would you get the other behavior when you wanted it?

: You are in a twisty little passage of standards, all conflicting.

    You are in a twisty little passage of standards, all on someone
    else's bookshelf.

Larry
From: merlyn@ora.com (Randal L. Schwartz)
Newsgroups: comp.lang.perl
Subject: Re: UUDECODE and perl ...
Date: 11 Nov 92 17:43:29 GMT
Article-I.D.: romulus.MERLYN.92Nov11094326
	<1992Nov11.134119.15928@porthos.cc.bellcore.com>
	<1992Nov11.150851.10057@news.eng.convex.com>
Organization: Stonehenge Consulting Services; Portland, Oregon, USA

In article <1992Nov11.150851.10057@news.eng.convex.com> tchrist@convex.COM (Tom Christiansen) writes:
   You shouldn't have to open a pipe to uudecode.  unpack('u', $datum)
   should suffice.

In fact, here's my program that uudecodes, ignoring anything that's
not a legal part of the uudecode.  I call it "uumerge".  There are
*many* broken uuencoders out there on the net, which is why it goes
through all these gyrations to figure out what the legal uu-lines are.
Ugh.

#!/local/usr/bin/perl

## Version 1.09 on 92/02/25
## Written by Randal L. Schwartz, Stonehenge Consulting Services, Portland, OR
## uudecodes the arguments (or stdin), ignoring non-uuencoded lines

shift,$debug++ if $ARGV[0] =~ /^-d/; # show lines being skipped
while (<>) {
	last if ($mode,$file) = /^begin\s*(\d*)\s*(\S*)/;
}
die "missing begin" unless $_;
open(OUT,"> $file") if $file ne "";
while (<>) {
	last if /^end/;
	$u = unpack("u",$_);
	$p = pack("u",$u);
	$p =~ s/`*\n//; # toss trailing open quotes and newline
	# $p now has the shortest line that might appear in the file
	$lp = length($p);
	if (
		(!/^--/) && # hack for not a cut line
		(!/^#/) && # hack for not a shar tag line blech
		(!/^CREATED BY/) && # hack for a stoopid losing uusplitter
		($lp < length) &&
		(substr($_,0,$lp) =~ /^[\020-\140]+$/) &&
		(substr($_,$lp) =~ /^[` ]*.?.?$/) # two garbage chars ok
	) {
		print OUT $u;
		print "$_","=" x $lp, "\n" if $debug;
	} else {
		print "skipping: $_" if $debug;
	}
}
die "missing end" unless $_;
chmod oct($mode), $file;
exit 0;

print unpack(u,q|92G5S="!A;F]T:&5R(%!E<FP@:&%C:V5R+```|)
--
Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
merlyn@ora.com (semi-permanent) merlyn@reed.edu (for newsreading only)
factoid: "Portland, Oregon, home of the California Raisins and Lone-Star Beer!"
Newsgroups: comp.lang.perl
From: weingart@inf.ethz.ch (Tobias Weingartner)
Subject: Remote Perl
Followup-To: comp.lang.perl
Keywords: remote, in.perld
Reply-To: weingart@inf.ethz.ch
Organization: ETH - Switzerland
Date: Fri, 13 Nov 1992 14:34:50 GMT


Hello.

Perl is great, Perl is cool, but remote it's just no tool...

Well, something like that anyways.  I have run into a small
problem.  When my perl scripts want to execute some 'thing'
(make that a perl subroutine) on another machine, things are
not very rosy.  Frist of all, the rsh method leaves many
things to be desired, security not withstanding.

Going on my usual long trip home, I was thinking to myself.
Why not use RPC?  Well, why not?  Of course, after thinking
about it at length, and drawing out some pictures, I found
that this is quite unuseable.

Here is how far I have gotten:

Make another subroutine in perl:

remote ;
remote EXPR ;
remote( EXPR );

Where EXPR would be ($machine, $subroutine, @args).  Of course,
remote would return whatever $subroutine @ $machine happened to
return.

First problem.  Which *&^@#$* script would the RPC routine
execute?  Well, I was hashing with this for a while, until I
thought of:

Why not make the in.perld (or whatever) require ~/.perldrc,
and the do eval "\&$subroutine(\@args)";?

Each user could then have their own ~/.perldrc, which could
require needed files, do things, etc...


While we are on the topic, how about a gethostname call?
I really hate to put:

chop($host = `hostname`);

into every script that I write.


Well, enough talk.  If anyone is interested in this, tell
me, and I'll see what I can do in the way of source code.

--Toby.

-- 

***************************************************************
* Tobias Weingartner  * Not every man is willing to die...    *                
* c/o Bruno Opprecht  * Some have to be PUSHED out the window *
* Oberdierikoner st.7 * ------------------------------------- *                
* 6030 Ebikon Luzern  *      ...This space for rent...        *
* SWITZERLAND         *      ...This space for rent...        *                
***************************************************************
* +41'041'33'25'40    * ..Midnight the fading, blue Wizrd..   *
***************************************************************
SYSTEM-F-ANARCHISM, the operating system has been overthrown                  

PGP2.0 Public Key available at 'finger weingart@tau.inf.ethz.ch'

Newsgroups: comp.lang.perl
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Executing required files
Originator: tchrist@pixel.convex.com
Date: Wed, 11 Nov 1992 14:59:49 GMT
Distribution: comp.lang.perl
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: Convex Computer Corporation, Colorado Springs, CO
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of mcook@fendahl.dev.cdx.mot.com (Michael Cook):
:jgd@acl.lanl.gov (Jerry G. DeLapp) writes:
:
:>I still like the idea of __REQUIRED__ to armor plate me from idiots setting $0
:>though. Any chance of this appearing in 5.0?
:
:What's wrong with setting $0?  At the risk of declaring myself an idiot, I do
:this pretty-much as a matter of course: $0 =~ s%^.*/%%;

You lose your visible arguments to ps.  Better this way:

    $0 =~ s%^.*/%%;  # clobbered visible @ARGV
    $0 .= " @ARGV";  # restore


--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist

    Some are born to perl, some achieve perl, and some have perl
    thrust upon them.
From: jfriedl+@CS.CMU.EDU (Jeffrey Friedl)
Newsgroups: comp.lang.perl
Subject: multibyte characters / 5.0?
Date: 7 Nov 92 05:44:45 GMT
Article-I.D.: cs.BxBzyM.BGz.1
Reply-To: jfriedl@cs.cmu.edu
Organization: Carnegie Mellon / Omron Corporation

Does anyone happen to have a perl whose regex stuff supports
multibyte characters?  Will 5.0 support them?

	*jeff*
From: mark@coombs.anu.edu.au (Mark)
Newsgroups: comp.lang.perl
Subject: Re: nslookup in perl
Date: 12 Nov 92 02:12:16 GMT
Organization: Australian National University
NNTP-Posting-Host: 150.203.76.2
Organisation: Wassat?!

drich@sandman.lerc.nasa.gov (Daniel Rich) writes:
>I am using a call to nslookup in one of my perl scripts, but someone
>pointed out that nslookup behaves differently on different systems (of
>course :-).  Has anyone implemented an nslookup perl library?  I am
>thinking of doing it myself, but I wanted to check and make sure I
>wasn't repeating anyone else's work.

Check out bind.pl on coombs.anu.edu.au /pub/perl/scripts....

README file from /pub/perl on coombs.anu.edu.au[150.203.76.2]

-=-=-=-=-=-=-=-=-=-=-=-
Australian Perl Archive
-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-
Please Note  Please restrict ftp times to outside normal business hours for
-=-=-=-=-=-  this site:
                          8:30am -  6:00pm AEDT -- Aussie
                          1:30pm - 11:00am PDT  \
                          3:30pm -  1:00am CDT   >-- USA
                          4:30pm -  2:00am EDT  /
                         10:30pm -  8:00am GMT  -- Europe

This archive is maintained by mark@coombs.anu.edu.au

Scripts are currently obtained from:

archive.cis.ohio-state.edu   /pub/perl
convex.com                   /pub/perl
sra.co.jp                    /pub/lang/perl
comp.lang.perl.

Note: mirror planned for *.uk. Watch this space.

See the file INDEX for a description of each script.
Please deposit any scripts in the 'incoming' directory

Share and enjoy.

Mark.
mark@coombs.anu.edu.au
mark@gnu.ai.mit.edu
markm@rmit.edu.au
Newsgroups: comp.lang.perl
From: sherwood@space.ualberta.ca (Sherwood Botsford)
Subject: Re: Marpa, prototype of a Hacker's Parser for Perl
Organization: University Of Alberta, Edmonton Canada
Date: Fri, 6 Nov 1992 21:54:40 GMT

Jeffrey Kegler writes

>This interface didn't come out very "perl-ish", and that may be due to
>my habits of thought.  I would like an interface that seemed more
>"perl-ish".

Perl-ish!
Perlish?

I think the adjectival form should be pearlescent 

perl es cent \,per-'les-ent\ adj
(1936)
:having a perly luster. e.g. "a perlescent lacquer"
  perl es cence \-en(t)s\ n 

(With apolgies to Mr. Webster...)
Newsgroups: comp.lang.perl
From: blah@tu-graz.ac.at (blahowsky)
Subject: Re: Where to find the documentation for using perl.
Organization: Technical University of Graz, Austria
X-Newsreader: TIN [version 1.1 PL6]
Date: Mon, 9 Nov 92 11:26:41 GMT

Subject: Perl documentation
From Peter Blahowsky

One of the most complete documentations on Perl is found in the Perl book 
in the Nutshel Handbook Series on Unix tool from O'Reilly & Associates INC.

                            Cheers Peter


C--------------------------------------------------------
C      Blahowsky Peter
C      Technical University Graz
C      A - 8010 Graz /Ausria-Europe
C      jrp@fmechsg01.tu-graz.ac.at
C--------------------------------------------------------
From: starkg@argon.gas.uug.arizona.edu (Gavin E Stark )
Newsgroups: comp.lang.perl
Subject: Help with reading to and writing from program.
Date: 5 Nov 92 05:06:00 GMT
Organization: University of Arizona - Tucson, Arizona


I'd like to be able to send input to a program and read the output from it.
Unfortunately this doesn't seem to work:

open(BLAH,"| someprogram |");

I'd like to be able to send a single line to the BLAH handle and then loop
and read lines coming from it.   Is this possible?


--


Gavin Stark
starkg@gas.uug.arizona.edu
Newsgroups: comp.lang.perl
From: mab@wdl39.wdl.loral.com (Mark A Biggar)
Subject: Re: Bug or feature ?
Organization: Loral Western Development Labs
Distribution: comp
Date: Mon, 9 Nov 1992 18:47:24 GMT

In article <CONS.92Nov9103421@mercury.cern.ch> cons@mercury.cern.ch (Lionel Cons) writes:
>I want to read the first two bytes of STDIN and then exec another
>process that uses the remaining chars from STDIN. According to the man
>pages the following script should work (if STDIN does not have the
>close-on-exec flag set):
>#!/usr/local/bin/perl
>$c1 = getc(STDIN);
>$c2 = getc(STDIN);
>print "First chars: '$c1' and '$c2'\n";
>exec('/bin/wc', '-c');
>It does not work (wc reply is 0), why ?

BUFFERING

getc uses stdio, so when you did the first getc, stdio slurped in at least
the whole first line into the buffer maybe more.  You are going to have to use
sysread to do what you want. E.G.

#!/usr/local/perl
sysread(STDIN,$c1,1);
sysread(STDIN,$c2,1);
print "First chars: '$c1' and '$c2'\n";
exec('/bin/wc', '-c');

--
Perl's Maternal Uncle
Mark Biggar
mab@wdl1.wdl.loral.com



Newsgroups: comp.lang.perl
From: forrie@morwyn.uucp (Forrest Aldrich)
Subject: Encryption USUBS
Organization: Vision Graphics
			  Dover, NH
			  USA
Date: Sat, 7 Nov 1992 16:52:18 GMT

Someone (a while back, I believe) posted some usubs that could be
used with the perl encryption mechanism.  I've misplaced them,
and wondered if someone out there would be kind enough to send me
a copy (or of something similar).  

Thanks ...

-- 
	   -----------	      Forrest Aldrich	      -----------
	   -------     morwyn!forrie@unhtel.unh.edu	  -------
	   ----						     ----
	   --	     VISION GRAPHICS --	Dover, NH - USA	       --
	   ------------------------------------------------------
From: "G.W.Bultman" <bultman@dgw.rws.nl>
Subject: NGetOpt interface - how to use it
Reply-To: bultman@dgw.rws.nl
Organization: The Internet
Date: Mon, 9 Nov 1992 13:29:45 GMT

Hi,

I'd like to use the NGetOpt interface, but I'm not sure how to 
check if an option is set or not.

Can anyone help?


|    #!/usr/local/bin/perl
|    require "newgetopt.pl";
|    do NGetOpt('gridsize=f','intervals=i','expparts=i');
|    
|    if ( option -gridsize is set )
|         {
|         $gridsize = $opt_gridsize;
|         }
|    else
|         {
|         $gridsize = default value;
|         }

--

    o                                                                o   
  / | \    Gert Bultman <bultman@dgw.rws.nl>   Koningskade 4       / | \  
 o--o--o   Tidal Waters Division               2596 AA The Hague  o--o--o 
  \ | /    Rijkswaterstaat                     The Netherlands     \ | /  
    o                                                                o
From: mark@coombs.anu.edu.au (Mark)
Newsgroups: comp.lang.perl
Subject: Re: Wanted .. a Perl based Disk Usage script
Date: 5 Nov 92 06:19:52 GMT
Organization: Australian National University
NNTP-Posting-Host: 150.203.76.2
Organisation: Wassat?!

bshaw@spdc.ti.com (Bob Shaw) writes:


>A while back, I saw a perl based disk usage script but didn't grab it.

>I think the particular one was written by Johan Vromans.  

>Thanks in advance for any info on this.

>Bob
>bshaw@spdc.ti.com

Check it out on coombs.anu..edu.au /pub/perl/scripts
I'll be posting the INDEX file when it's finished so you can decide if you
need a script or not.


README file from /pub/perl on coombs.anu.edu.au[150.203.76.2]

-=-=-=-=-=-=-=-=-=-=-=-
Australian Perl Archive
-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-
Please Note  Please restrict ftp times to outside normal business hours for
-=-=-=-=-=-  this site:
                          8:30am -  6:00pm AEDT -- Aussie
                          1:30pm - 11:00am PDT  \
                          3:30pm -  1:00am CDT   >-- USA
                          4:30pm -  2:00am EDT  /
                         10:30pm -  8:00am GMT  -- Europe

This archive is maintained mark@coombs.anu.edu.au

Scripts are currently obtained from:

archive.cis.ohio-state.edu   /pub/perl
convex.com                   /pub/perl
sra.co.jp                    /pub/lang/perl
comp.lang.perl.

Note: mirror planned for *.uk. Watch this space.

See the file INDEX for a description of each script.
Please deposit any scripts in the 'incoming' directory

Share and enjoy.

Mark.
mark@coombs.anu.edu.au
mark@gnu.ai.mit.edu
markm@rmit.edu.au
Newsgroups: comp.lang.perl
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: UUDECODE and perl ...
Originator: tchrist@pixel.convex.com
Date: Wed, 11 Nov 1992 15:08:51 GMT
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: Convex Computer Corporation, Colorado Springs, CO
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

You shouldn't have to open a pipe to uudecode.  unpack('u', $datum)
should suffice.

--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist

Perle, plesaunte to prynces paye/ To clanly clos in golde so clere,
Oute of oryent, I hardyly saye/ Ne proued I neuer her precios pere.
From: lynch@hpcc01.corp.hp.com (Howard Lynch)
Date: Tue, 10 Nov 1992 01:12:37 GMT
Subject: Re: require "did not return a true value" ???
Organization: OCD IC MFG
Newsgroups: comp.lang.perl

Thanks for all the responses!  This is indeed a generous group of users!

Hey, Larry, how about putting a note in the next edition of the book about
the requirement for a require'd file to have a statement in it that causes
a 'true' to be returned?  Seems like a good thing to be in the book for us
novices.

Thanks again to all!

Howard Lynch
HP OCD IC Manufacturing
hl@hpocia.sj.hp.com
Newsgroups: comp.lang.perl
From: cons@mercury.cern.ch (Lionel Cons)
Subject: Bug or feature ?
Organization: CERN, European Research Center for Particle Physics
Distribution: comp
Date: Mon, 9 Nov 1992 09:34:21 GMT

I want to read the first two bytes of STDIN and then exec another
process that uses the remaining chars from STDIN. According to the man
pages the following script should work (if STDIN does not have the
close-on-exec flag set):

#!/usr/local/bin/perl
$c1 = getc(STDIN);
$c2 = getc(STDIN);
print "First chars: '$c1' and '$c2'\n";
exec('/bin/wc', '-c');

It does not work (wc reply is 0), why ?
--

Lionel Cons

+------- CERN - European Laboratory for Particle Physics -------+
| E-mail: cons@dxcern.cern.ch                                   |
| Earth-mail: CN/SW/WS, CERN, CH-1211 GENEVE 23, Switzerland    |
| Phone: +41 22 767 49 13              Fax: +41 22 767 71 55    |
+---------------------------------------------------------------+
Newsgroups: comp.lang.perl
From: krab@iesd.auc.dk (Kresten Krab Thorup)
Subject: Re: Help with quotes
Organization: Mathematics and Computer Science, Aalborg University
	<1992Nov6.190530.20726@netlabs.com>
Distribution: comp
Date: 7 Nov 92 18:18:15

>>>>> On 6 Nov 92 19:05:30 GMT, lwall@netlabs.com (Larry Wall) said:
:> Nntp-Posting-Host: scalpel.netlabs.com

:> In article <FILO.92Nov4211406@pegasus.Stanford.EDU> filo@pegasus.stanford.edu writes:
:> : I'm having a bit of a problem with quoting.
:> : 
:> : This works as expected.  It replaces the first character with a double-
:> : quote.
:> : 
:> : $ perl -pe 's/./sprintf ("\\"")/e; print "<$@>" if $@'
:> : help
:> : "elp
:> : $
:> : 
:> : Below is the same thing except $& has been added to the sprintf.  In
:> : this case the evaluation of the replacement string fails.  I have not
:> : been able to find a way to properly escape the double-quote to be
:> : printed.
:> : 
:> : $ perl -pe 's/./sprintf ("$&\\"")/e; print "<$@>" if $@'
:> : help
:> : <EOF in string at (eval) line 1, <> line 1.
:> : >elp
:> : $
:> : 
:> : I know I could just changes quote characters, but I need a way to
:> : include the quote character inside the quoted string.

:> Admittedly it's probably a bug, but changing the inner quote characters
:> is not your only option.  You can also change the outer quote characters,
:> like this:

:>     perl -pe 's/./sprintf(qq!$&"!)/e; print "<$@>" if $@'

:> The whole idea of q and qq is to get away from the necessity of
:> counting backslashes or parens.  (One of the benefits of having More
:> Than One Way To Do It is that if one of the ways doesn't work out, you
:> can do it a different way, no?)

The problem may be, that you're using bash (the prompt $) could look
like you do :-)  Bash has a lot of troubles expanding quotes right....

/Kresten
--
Kresten Krab Thorup, DAT3, D2-117 |       /   | E-mail : krab@iesd.auc.dk
Institute of Electronic Systems   |   ,-'/(   | S-mail : Sigrid Undsetsvej 234A
Aalborg University                |  /  |  \  |          9220 Aalborg \O
Fr. Bajers vej 7, 9220 Aalb. \O   |  A  U  C  |          98 15 18 44
-------------------------------------------------------------------------------
           Member of the LPF - The League for Programming Freedom
From: roy%cybrspc@cs.umn.edu (Roy M. Silvernail)
Newsgroups: comp.lang.perl
Subject: Re: UUDECODE and perl ...
Date: Thu, 12 Nov 92 18:05:04 CST
Organization: Villa CyberSpace, Minneapolis, MN

rdm2@donner.uucp (24337-mcburnett) writes:

> Hi All,
> 
> Here is what I use to "auto decode" articles.
[...]
> 
> ================cut here================
> #! /usr/local/bin/perl -S
> #extract will scan for uuendcoded stuff and feed it to uudecode
> open(_uud,"|uudecode");

But why?  That's built in....

| #!/usr/bin/perl
| $_ = <> until ($mode,$file) = /^begin\s*(\d*)\s*(\S*)/;
| open(OUT,"> $file") if $file ne "";
| while (<>) {
|     last if /^end/;
|     next if /[a-z]/;
|     next unless int((((ord() - 32) & 077) + 2) / 3) == int(length() / 4);
|     print OUT unpack("u", $_);
| }
| chmod oct($mode), $file;

(uudecode.pl courtesy of Randal Schwartz)
--
Roy M. Silvernail --  roy%cybrspc@cs.umn.edu - OR-  cybrspc!roy@cs.umn.edu
                         "I'm a model citizen."
                                      -- Warren Zevon
Newsgroups: comp.lang.perl
From: jja@fnbc.com (Joseph Alotta)
Subject: Re: i need help with tar and tapes drives.
Keywords: tar,gnutar,tapes
Organization: First National Bank Of Chicago, Chicago IL, USA
Date: Mon, 9 Nov 92 16:49:53 GMT

i am trying to tar backup files to tape. 
 
i can:

tar cvf /dev/rst0 /data/*
tar tvf /dev/rst0
tar xvf /devrst0  filenames.

without much problem.

but since my tape is not filled up, i'd like to append new files to
the end of it.

 
i tried "tar rvf /dev/rst0"  but it didn't work.  seems the r option
is unsupported on my machine.  

i ftp'd gnutar and tried "gnutar -Avf /dev/rst0"  but that didn't work.
i got cannot backspace errors.
 
people say i should use "mt -f /dev/nrst0 -fsf 99" to get to the end of  
thetape and then "tar cvf /dev/nrst0 *", but i don't like having to  
remember what segments i've used on the tape and what is in each segment.

can anyone help me to get gnutar to append?
 
btw, i am using a archive dat tape and a nextstation 3.0. and perl as a
wrapper for all these commands.

 
thanks in advance,

joe.

==============================================================
! joe alotta                                    jja@fnbc.com !                                               
!                                             (312) 732-3439 !
!                                                            !
! "The main thing is to keep the main thing the main thing." !
! Dr. George Sweeney                                         !
==============================================================
From: lmjm@doc.ic.ac.uk (Lee M J McLoughlin)
Newsgroups: comp.lang.perl
Subject: Wanted: file descriptor management
Date: 13 Nov 92 20:42:26
Organization: Dept. of Computing, Imperial College, London. U.K.
Distribution: comp
NNTP-Posting-Host: swan.doc.ic.ac.uk

I'm writing a program that needs to process input lines a bit like
cpp.  In particular I need to be able to implement a #include -like
mechanism.  So I'm looking for a library that I can use to mangage
file descriptors so that when I switch file, on an include, I can
switch back to my original file when I'm done.

If anyone has such a library or can point me at something I can turn
into such a library I'd be most greatful.
	Lee
--
--
Lee McLoughlin.                          Phone: +44 71 589 5111 X 5085
Dept of Computing, Imperial College,     Fax: +44 71 581 8024
180 Queens Gate, London, SW7 2BZ, UK.    Email: L.McLoughlin@doc.ic.ac.uk
Newsgroups: comp.lang.perl