yeah that def worked because i can byte reverse the file, then after the while loop i can write it to disk/hdd. i can also seek and read it ;) which is what i was after lol.
here is the final working code:
open ( my $in_file, '<', "file" );
binmode( $in_file );
my $mem_file;
binmode( $mem_file );
my ( $buf, $data, $n, $bytes );
while (( $n = read $in_file, $data, 4096 ) != 0){
$mem_file .= pack( "v*", unpack("n*", $data ));
$bytes+=$n;
}
open ( my $otherMem_file, '<', \$mem_file );
binmode( $otherMem_file );
seek $otherMem_file, 0x00, 0;
read $otherMem_file, my $temp, 0x1200;
open my $out_file, '>', "reversed";
syswrite( $out_file, $temp);
and it give me all expected results byte for byte. :)
also i should add that i am parsing the file using its hexadecimal representaion of a binary file and i honestly dont think you would even need to binmode any of these files and it doesnt need file::slurp. completely independant code teehee
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.