-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BF: reading stata files - unpack read value describing stored byte order #7272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Otherwise comparison would always result in "low endian"
whoosh! thanks seems simple enough |
BF: reading stata files - unpack read value describing stored byte order
thanks @yarikoptic |
you are welcome Never give up -- never give in! ;) On Thu, 29 May 2014, jreback wrote:
Yaroslav O. Halchenko, Ph.D. |
That was a simple fix. In principle someone should probably test the .dta files created on a big endian platform in Stata. I have tested the files created in the test suite in Stata, but only on LE. |
Hard since most commodity hardware is using x86 which is little endian. Sparc I think is only on specific sun systems which are not feasible for any of us to purchase. That said sometimes these builds do find bugs. |
yep the debian guys run all of the builds on lots of hardware |
On Fri, 30 May 2014, Phillip Cloud wrote:
FWIW: used sparcs are actually more than affordable. companies simply get rid look at Yaroslav O. Halchenko, Ph.D. |
Interesting. Thanks @yarikoptic |
I am sorry for ruining your dream @cpcloud that you had a very wealthy cyber-friend -- my sparcs are recycled 2000 and 2005 boxes too ;) |
You must use Raid for debugging those :) |
Yaroslav O. Halchenko, Ph.D. |
Otherwise comparison would always result in "low endian" . Seems to resolve all the gory stata files reading tests on sparc at least
closes #5781