Re: binmode i/o for perl -pi in-place editing

I didn't get this working with the -pi switches, but looks to me like shmem has a solution. If all else fails, what needs to be done without the -pi complication is straightforward:

#!usr/bin/perl
use strict;
use warnings;

open (IN, '<','src.bin') or die $!;
binmode IN;
open (OUT, '>','srcnew.bin') or die $!;
binmode OUT;

my $inbuf = do {local $/; <IN> };
$inbuf =~ s/w/v/;

print OUT $inbuf;

__END__

C:\PROJEC~1\testing>debug src.bin
-d
62 69 6E 0A 00 65 6E 63-6F 64 65 64 00 66 69 6C   bin..encoded.fil
65 00 72 3A 0D 00 6E 3A-0A 00 6E 72 3A 0A 0D 00   e.r:..n:..nr:...
72 6E 3A 0D 0A 00 77 69-74 68 00 45 4F 4C 2D 6C   rn:...with.EOL-l
69 6B 65 00 73 65 71 75-65 6E 63 65 73 00 00 00   ike.sequences...
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   ................
-q


C:\PROJEC~1\testing>debug srcnew.bin
-d
62 69 6E 0A 00 65 6E 63-6F 64 65 64 00 66 69 6C   bin..encoded.fil
65 00 72 3A 0D 00 6E 3A-0A 00 6E 72 3A 0A 0D 00   e.r:..n:..nr:...
72 6E 3A 0D 0A 00 76 69-74 68 00 45 4F 4C 2D 6C   rn:...vith.EOL-l
69 6B 65 00 73 65 71 75-65 6E 63 65 73 00 00 00   ike.sequences...
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   ................
-q
[download]

Update: edited out beginning line info (byte offset, etc) from the debug output in the hopes that the lines will display better on Perl Monks. "debug" is a standard Windows command from the Command Line.

I will also add as a comment that although it is possible to preserve the line endings in a file, I almost always find that this is not desirable. You can wind up with mixed line endings that Perl can deal with, but other programs cannot. Perl will write a line ending appropriate for the platform being used for that "write". So: read the line, print the line is often the best way. That "normalizes" the line endings.

Comment on Re: binmode i/o for perl -pi in-place editing Download Code

Replies are listed 'Best First'.
Re^2: binmode i/o for perl -pi in-place editing by pryrt (Abbot) on Dec 09, 2016 at 15:17 UTC
Yeah, I ended up using something similar to your non`-pi` script to actually do the processing yesterday. (And today, I was able to follow shmem's suggestions to get the `-pi` working) My searches indicate that debug.exe hasn't shipped with Win7^(1,2) (or probably beyond), though it did ship with Windows XP⁽³⁾. Regardless of normal, my Win7 64bit installation doesn't include it. I just used xxd, because it was faster than rolling my own hex dumper in perl -- though I should have, once I was trying to bring fellow Monks to help me. :-) I was just using null-separated text for easy-to-create dummy data. Really, it is a binary data format, which can have the bytes 0x0A and 0x0D anywhere (not really functioning as newlines), but occasionally has embedded strings; I was trying to edit some of those occasional strings (and I couldn't get my GnuWin32 sed.exe to do the changes I wanted -- I was probably not escaping something correctly on the command line -- so I switched to perl, because I thought it would be easier (and I wanted to learn more about the `-pi` options, since I'd never used that combination, I'd normally just rolled my own file loop, like I ended up doing.) Again, everyone, thanks for your help and suggestions. I've learned more, which is always my goal here. ¹ http://superuser.com/questions/510671 /is-there-debug-exe-equivalent-for-windows7: implies it doesn't ship with Win7 ² http://www.computerhope.com/forum/index.php?topic=129058.0: implies it doesn't ship with Win7 ³ https://technet.microsoft.com/en-us/library/bb491040.aspx: did ship with XP	[reply] [d/l] [select]
Re^3: binmode i/o for perl -pi in-place editing by shmem (Chancellor) on Dec 09, 2016 at 16:38 UTC
Really, it is a binary data format, which can have the bytes 0x0A and 0x0D anywhere (not really functioning as newlines), but occasionally has embedded strings; I was trying to edit some of those occasional strings... Something like that was my very first use of `-pi` back in the '90s - monkey-patching a different hostid into a binary bound to a specific Sun workstation, when due to sudden death of one machine they had to be transferred to the other which was not licensed. The only other method would have been manipulating the hostid at the OpenBoot PROM, which was deemed too dangerous (and it changes the MAC Address as well). Then monkey-patching windows dlls containing incomplete translations (making sure that the replacing string is equal or lower in size as the original, of course)... that type of fun stuff. Anyways. I am/was glad I could help ;-) perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'	[reply] [d/l]