Thanks. I think so. So the issue is that unpack takes a string as an argument (which I now see on the description in perlfunc), so it's unpack itself that forces the number to be interpreted as a string? Packing it explicitly as an integer gives it an integer to unpack -- though pack, according to perlfunc, also produces a string. I guess I just lack a basic understanding about how Perl stores data. My understanding of data types is essentially C-centric (char or int or short or string).
In reply to Re^2: ActivePerl on Win32 storing integers as strings?
by LonelyPilgrim
in thread ActivePerl on Win32 storing integers as strings?
by LonelyPilgrim
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |