«

I need to print a text to file from within the script. The printed text must
be the same as the script text.
I do not want to escape every single character of the text, it should be
"pass through". So far nothing worked.
A small script that expose the problem, any help is wellcome.

open FILE, '>test.txt' or die "$^E\n";
print FILE q~
\
\\
\\\
~;
close FILE;

open FILE, '>test.txt' or die "$^E\n";
print FILE <<'F';
\
\\
\\\
F
close FILE;

not good

At linux it is ok. At windows does not behave as should ...

On Mon, 04 Feb 2013 18:02:45 +0000, Henry Law <>
wrote:

>On 04/02/13 15:18, George Mpouras wrote:
>> At linux it is ok. At windows does not behave as should ...
>
>Again, forgive me George: you've much more experience than I, but I
>moved my test program to a Windows image and got this:
>
>C:\WIP>type tryout.pl
>use strict;
>use warnings;
>use 5.010;
>
>use Data:umper;
>
>open FILE, '>test.txt' or die "$^E\n"
>print FILE <<'F';
>\
>\\
>\\\
>F
>close FILE;
>
>C:\WIP>type test.txt
>\
>\\
>\\\
>
>C:\WIP>
>
>I was initially suspicious of the apparent extra return at the end of
>the file but I looked at test.txt with an editor (inside Win) and there
>is only one. The Win shell "type" command seems to add another. So the
>output is the same as the Linux version.
>
>What am I missing?

ANother thing you could try is printing with FORMATs. The output will
be EXACTLY as described on the format. I've used this technique to
create fixed format files for transferral to dependent agencies with
excellent results. Runs the same on *nix or *doze.

there is a strange behaviour of activestate petl (5.16) at windows

print FILE q~
\
\\
\\\
~;

prints


\
\
\\



print FILE<<stop_printing;
\
\\
\\\
stop_printing

prints

\
\

"George Mpouras"
< m.com.nospam>
writes:
> there is a strange behaviour of activestate petl (5.16) at windows
>
> print FILE q~
> \
> \\
> \\\
> ~;
>
> prints
>
>
> \
> \
> \\
>
>
>
> print FILE<<stop_printing;
> \
> \\
> \\\
> stop_printing
>
> prints
>
> \
> \

This is not really strange: A here-document whose delimiter is not quoted is
essentially a "-quoted string. The first \ escapes the newline right
after it. The \\-sequence in the seond line cause a \ to be
printed. The third line results in another \ because of the \\ and the
trailing newline is again escaped (which is a no-op).

if so why windows behaviour is completely different than linux ?

"George Mpouras" < om>
writes:
> if so why windows behaviour is completely different than linux ?

When running your two code examples on 'Linux', I get the exact same
output you posted.

try to run them on a windows box and compare the results between windows and
linux