There've been a couple parallel libpnds where other people have pulled it, changed it and used their version, then submitted patches upstream, and I've rearranged their patches so as struct changes go to the end; but if you used someone elses interim libpnd, it could have run into member location changes.
Or perhaps something slipped through the fcracks.. I'm pretty anal about such things, but if a member got injected into the middle, please let me know which so I can examine the history.
(Also note, you might want to use struct member getter functions to avoid a problem in the future, though I agree, they're cumbersome and I tend not to use them either
So let me know more information (I just popped into thread, will go read..), so I can fix up any problems or we can find the source troublemaker
Hmm, taking a look at current.. I notice package_ stuff is at the end:
88 char *package_version_major;
89 char *package_version_minor;
90 char *package_version_release;
91 char *package_version_build;
But up at the top, package-id got injected:
61 char *package_id;
If thats a new one, that coudl be a problem shuffling the whole struct down a few bytes; is that the one? I'll have to check back and figure out what to do if so .. bump it to the end and risk breaking others, but being 'correct'...
I wonder if this was the patch in question:
If thats the culprit, twas back in May. Do I bump the package_id to bottom, risking a few apps, or just leave it at this point?
lindpnd structs have never changed, beyond adding memebrs to the 'end'; ie: if your'e assujming struct size, and packing them in an array, it could possible be a problem; however, libpnd includes alloc/dealloc type functions for such purposes, as well as lists, so shoudlnt' be a problem.