comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: porting IDL code to OS X
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Re: porting IDL code to OS X [message #34619] Thu, 10 April 2003 09:58
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
M. Katz (MKatz843@onebox.com) writes:

> For other IDL binary files, like variables saved with the "SAVE" and
> brought back with "RESTORE" commands, you will notice a byteshift
> going from Intel/AMD to Motorola. For those files, I often have to
> test the different byte-swapping keywords until one of them works.
> Fortunately, once you guess the right one, you know it forevermore.

Ah, the ol' empirical method. I know it well. :-)

Cheers,

David
--
David W. Fanning, Ph.D.
Fanning Software Consulting, Inc.
Phone: 970-221-0438, E-mail: david@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
Re: porting IDL code to OS X [message #34621 is a reply to message #34619] Thu, 10 April 2003 09:46 Go to previous message
MKatz843 is currently offline  MKatz843
Messages: 98
Registered: March 2002
Member
> Greetings,
>
> I dumped my Windows workstation in favor of an OS X box

First of all, congratulations, and welcome.

> and now I am
> attempting to bring custom written code from IDL on Windows to IDL on
> OS X. Most of the code appears to come over just fine, however, I am
> getting errors reading graphics files within the program. Are there
> any fundamental issues I am missing here with graphics file
> compatibilities on Windows versus *nix OS's? Big vs. little endian?
> Anything else?

In my experience with GIF (IDL pre 5.5) PNG, JPG, TIFF, EPS, I've had
no problems Mac/Linux/Windows. Make sure if you're using an older FTP
program, to transfer the files with "binary" on. "sftp" from the OS X
command line seems to either always use binary or never have a problem
interpreting which is which.

For other IDL binary files, like variables saved with the "SAVE" and
brought back with "RESTORE" commands, you will notice a byteshift
going from Intel/AMD to Motorola. For those files, I often have to
test the different byte-swapping keywords until one of them works.
Fortunately, once you guess the right one, you know it forevermore.

M. Katz
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Re: Where is the trick in objects
Next Topic: Re: Whither Object

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 18:38:37 PDT 2025

Total time taken to generate the page: 0.00711 seconds