1175 Rate this article:
No rating

The command line and the Workbench

Mark Alonzo
There are two primary ways of using IDL: the command line (CLI*) and the Workbench (WB). The CLI allows direct access to the IDL interpreter. The WB is a separate program that sits on top of IDL and provides a slew of organizing, editing and debugging tools for working with IDL.

I <3 XKCD

What are the pros and cons of these two ways of using IDL? Here's how I see it. CLI Pros:
  1. Lightweight.
  2. Fast. The CLI provides direct access to the IDL interpreter.
Cons:
  1. Limited shell-like support; e.g., no color syntaxing, command completion or keybinding definition. (However, see rIDL.)
  2. An external editor is needed to develop and debug code. (For many, this may not be a negative.)
WB Pros:
  1. Integrated editor with command completion, color syntaxing, code formatting and code templates.
  2. Projects for organizing files and controlling IDL’s path.
  3. A consistent interface across platforms supported by IDL (Windows, Mac OS X, Linux).
Cons:
  1. The WB is built on Eclipse, which is a big, complex Java application. As the size and complexity of an application grows, the likelihood of bugs grows, as well.
It’s part of my job to use the WB, so I’m clearly biased, but there are several features that I miss when I go back to Emacs + the CLI, among them:
  • projects for file operations and path management,
  • the Outline view for jumping between programs in a file, and
  • the Open Resource dialog for opening files.
I’d like to demonstrate these in a set of subsequent posts, as well as other WB features that I find useful. How do you prefer to use IDL?

Please login or register to post comments.