in reply to Re^3: Geo Package files
in thread Geo Package files
As I've reached the point I've got to, my gut feeling is that it is worth continuing. Perhaps not for this project, but certainly for what I am learning in the process of doing this. Previously, the only use I've made of unpack is to split up an authentication string.
I think knowing more about pack and unpack would be beneficial to me. Thanks to soonix and Marshall my understanding of these two functions in improving. That alone makes continuing worthwhile.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^5: Geo Package files
by Fletch (Bishop) on Mar 05, 2022 at 22:56 UTC | |
Certainly a good learning opportunity and from the (cursory) read over the linked docs it looks like those should well serve. Having something “tangible” to use for practical samples is great; I’d just rather (for $work purposes) defer to off the shelf and play with things on the back burner.
The cake is a lie. | [reply] |
|
Re^5: Geo Package files
by Marshall (Canon) on Mar 08, 2022 at 03:35 UTC | |
I don't want to get into the idea of "real" vs "fake" OS. Windows is certainly "real". I've worked with several variants of MS O/S's and several variants of Unix, one IBM mainframe OS and several real time O/S's. They are all "real" and have their own jobs. Your question is interesting and a little bit different than what I normally deal with. Worst case, I believe that I can write an inline C subroutine that will do what you want (as long as we are both on 64 bit little endian architecture). Although I don't think that is necessary. | [reply] |
by Bod (Parson) on Mar 11, 2022 at 20:09 UTC | |
I still would like binary dump as I request in here. Sorry - I thought I'd given you this in Re^4: Geo Package files Here you go, this is hex dump of the entirety of $geo from this script...the lengths are vastly different. I added the random order to see how varied the data actually is.
| [reply] [d/l] [select] |
by pryrt (Abbot) on Mar 11, 2022 at 20:49 UTC | |
I get a decoding of the first 8 bites plus envelope of: And the minx,miny are smaller than maxx,maxy -- so whether that's a good thing or not, I don't know. The main takeaways of my input is that you need to use the < for litte-endian and > for big-endian, and that way you won't be guessing in the future whether your system and/or perl have native big- or little-endianness. (Also, even if you'll always be on the same processor, having those directions explicit in the code will make future development/maintenance so much easier.) | [reply] [d/l] [select] |