Any software as large and as sophisticated as IDL has odd behavior from time to time. There are bugs. There are things that don't work exactly the way they are supposed to. There are typos in the documentation. There are people who don't read manuals.

This is a page that is meant to shed light on some of the odd behaviors IDL exhibits from time to time. It is not meant to be a forum for sharing gripes about IDL. Rather, it is a place to get and share information about software that most of us like, and all of us want to get better and better.

No forum like this can be successful without the efforts of a great number of people who are willing to share information with the larger IDL community. I am especially indepted to the people who send me reports of odd IDL behavior and even more so to the people who can explain how and why IDL does what it does. The team of technical support engineers at Research Systems are to be especially commended for their commitment to getting accurate, timely information out to the IDL community.