Bee wrote:
>
> open FH, ">1.txt";
> binmode FH;
> binmode STDOUT;
> print FH "123m,zxnc,mzxnc,mzncm,zxc";
> close FH;
>
> Why the output still a text file ?
Other posters are right. What is your test, that you find
your output to be a text file?
Rob
--
To unsubscribe, e-mail: [EMAIL PROTECTE
> Bee wrote:
> > open FH, ">1.txt";
> > binmode FH;
> > binmode STDOUT;
> > print FH "123m,zxnc,mzxnc,mzncm,zxc";
> > close FH;
> >
> > Why the output still a text file ?
>
Thanks everybody, the way I tried to make files to binary
format is just because I want to learn how to sysread and
syswrit
Bee wrote:
> open FH, ">1.txt";
> binmode FH;
> binmode STDOUT;
> print FH "123m,zxnc,mzxnc,mzncm,zxc";
> close FH;
>
> Why the output still a text file ?
A file's a file. Terms like "text" and "binary" are just conventions. To the
OS, a file's just a collection of bytes.
What were you expecting
Bee wrote:
> open FH, ">1.txt";
> binmode FH;
> binmode STDOUT;
> print FH "123m,zxnc,mzxnc,mzncm,zxc";
> close FH;
>
> Why the output still a text file ?
Only thing binmode gives you is that what you put in will not be in any way
translated as part of the print and/or write. If you wan
> Why the output still a text file ?
This is a stab in the dark, but the binary equivalent of the characters in the string
are characters, correct? Have you tried seeing what happens when you output hex
values?
-Dan
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
open FH, ">1.txt";
binmode FH;
binmode STDOUT;
print FH "123m,zxnc,mzxnc,mzncm,zxc";
close FH;
Why the output still a text file ?
