% perldoc -f binmode
-David Boyce
At 02:26 AM 1/26/00 +0000, Christian Goetze wrote:
>On Tue, 25 Jan 2000, Marilyn Sander wrote:
>
> >
> >
> > | Date: Wed, 26 Jan 2000 01:34:15 +0000 (GMT)
> > | From: Christian Goetze <cg@digisle.net>
> > | To: cciug@Rational.Com
> > | Subject: [cciug] <CR><LF> from ccperl in triggers.
> > |
> > | I'm having some baffeling behaviour from ccperl.
> > |
> > | Is there any way to positively enforce that only a newline character is
> > | spit out by ccperl?
> > |
> > | It would seem that running ccperl naivly on NT will produce lines ending
> > ^^^^^^
> > natively? naively? :-)
> ^^^^^^^
> >
> > | in <CR><LF>. Is there any way to turn this off.
> >
> > Where are the newlines coming from, and what would you like instead?
> > If they're coming from print " ..... \n"; and you want
> > the UNIX-style line endings, then I would suggest
> > defining a variable $NL that contains just a hex 0A, and use that
> > in place of \n in your print statements.
>
>Nope - doesn't work. Perl seems to scan for those and replace them with
>CR/LF.
>
>My suspicion is that perl decides depending on how you open the file. If
>the file contains forward slashes in the pathname, it treats it UNIX
>style, if not it's NT style.
>--
>cg
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:37 EDT