Some comments, as I was doing scientific programming of one kind or another for a number of years..

1. Small scientific programs without fancy output generally don't need objects.

2. Your program, however, is about 80% of its way to using an object.

3. As long as you only wish to display 1 dataset you're fine as you are.

4. Should you ever wish to get fancy with your display, such as embedding a different dataset as an inset view, then you can start encapsulating your data along with their associated screen transformation parameters or drive yourself crazy. And as ELISHEVA has pointed out, it's easier to manage input options with an OO framework.

Update: Clarified some language.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.