comment on

Windows 7 64-bit perl v5.12.3 I open the file using...

open(IN, $nameoffile) or die "Can't open $!\n";

I have not seen binmode so I am definitely not using that. I have my .pl file on a classified network not connected to the internet so I would have to retype the entire thing. I am almost positive it is not my code though since I can repeat the exact same time thousands of times before this issue pops up at some random point.

EDIT: Looking at binmode, before I open the file, should it be...

binmode STDIN, ":bytes"; open(IN, $nameoffile) or die "Can't open $!\n";

Or should it be...

binmode IN, ":bytes"; open(IN, $nameoffile) or die "Can't open $!\n";

EDITEDIT: I just tried including binmode and the behavior didn't change whatsoever, unless both of my examples above are wrong. As far as I can tell these files contains a single massive block of hex data so I don't think I have to worry about any newlines.

In reply to Re^2: Missing byte using unpack, pack, read(in terms of bytes) by joemaniaci
in thread Missing byte using unpack, pack, read(in terms of bytes) by joemaniaci

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks