Hello all. I have MacOSX at home and Windows at the office. I compiled it++3.9.1 against ATLAS 3.6.0 under cygwin at the office and against vecLib on MacOSX at home. When I compile and run the same program under the two environments all looks well until I write to a file. In Windows the file is written properly and I can read the file using itload under octave. However the reading fails under MacOSX. If I do a binary comparison between the files I can clearly see they are different but I have no clues why. Did anyone run into this problem? Thank you and regards.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could you please give us more information on the problem occured? We are not fortune-tellers, and your description is not sufficent to narrow down the problem...
1) Is it possible to read the content of the file under MacOS X in IT++?
2) What is the content of the written file?
3) Can you test this problem using something very simple, e.g. writing an int or a double variable to a file?
/ediap
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I guess that the problem is caused by different endianities of your Windows and MacOS X platforms.
Could you confirm that? What endianity (big or little) uses your MacOS X?
I am not an author of the it_file classes, so I can not say if it is a bug in file reading/writing functions or a bug/problem in Matlab/Octave scripts...
Anyway, thanks for your help with this bug. It would be great if you could post an official bug-report to the Bugs section with a short, clear description of the problem.
/ediap
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry if I were not explicit. Answers to your questions:
1) Yes but in a byte to byte comparison between the one in Windows and the one in MacOSX they are different;
2) The content seems to be valid. It is possible to see the names and types of the variables but it seems the binary value of the variables is incorrect;
3) I tested with writing an integer with the value of 1 and when reading the variable it reads 16777216. I also tried writing a double with the value of 2.0 and reading in octave I get 3.1620e-322
/ojl1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello all. I have MacOSX at home and Windows at the office. I compiled it++3.9.1 against ATLAS 3.6.0 under cygwin at the office and against vecLib on MacOSX at home. When I compile and run the same program under the two environments all looks well until I write to a file. In Windows the file is written properly and I can read the file using itload under octave. However the reading fails under MacOSX. If I do a binary comparison between the files I can clearly see they are different but I have no clues why. Did anyone run into this problem? Thank you and regards.
Could you please give us more information on the problem occured? We are not fortune-tellers, and your description is not sufficent to narrow down the problem...
1) Is it possible to read the content of the file under MacOS X in IT++?
2) What is the content of the written file?
3) Can you test this problem using something very simple, e.g. writing an int or a double variable to a file?
/ediap
I guess that the problem is caused by different endianities of your Windows and MacOS X platforms.
Could you confirm that? What endianity (big or little) uses your MacOS X?
I am not an author of the it_file classes, so I can not say if it is a bug in file reading/writing functions or a bug/problem in Matlab/Octave scripts...
Anyway, thanks for your help with this bug. It would be great if you could post an official bug-report to the Bugs section with a short, clear description of the problem.
/ediap
Sorry if I were not explicit. Answers to your questions:
1) Yes but in a byte to byte comparison between the one in Windows and the one in MacOSX they are different;
2) The content seems to be valid. It is possible to see the names and types of the variables but it seems the binary value of the variables is incorrect;
3) I tested with writing an integer with the value of 1 and when reading the variable it reads 16777216. I also tried writing a double with the value of 2.0 and reading in octave I get 3.1620e-322
/ojl1