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

Home » Public Forums » archive » Re: variables in common blocks
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: variables in common blocks [message #53862 is a reply to message #53861] Fri, 04 May 2007 09:40 Go to previous messageGo to previous message
Christopher Thom is currently offline  Christopher Thom
Messages: 66
Registered: October 2006
Member
Quoth Lasse Clausen:

> Ok. I'll describe what I am using common blocks for: Whatever day
> during the week, I am doing one of the following:
> 1) read data
> 2) process data
> 3) plot data
> Since there are many different ways to process or plot data, it is
> nice to read the data into common blocks, so that when I decide to
> process or plot the data differently, I do not have to read it in
> again.
>
> If you have an easy solution on how to avoid common blocks, shoot. And
> why are common blocks bad? Is it the same reason "goto" statements are
> bad?

Well...I tend to store all my reduced data in IDL .sav files, then read
them whenever I want to run a routine. So which is more evil...sav files
or common blocks? *ducks* :-)

On the GOTO side of things, I often use them as a get-out-of-jail-free
statement inside several layers of nesting, when I take user input. I put
in a "quit now and I really mean it" option for myself, then jump to a
cleanup section at the end, so I don't leave a mangled plotting window and
file handles lying around.

cheers
chris
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: limited angle CT
Next Topic: IDL number output format problem?

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

Current Time: Sat Nov 29 09:38:35 PST 2025

Total time taken to generate the page: 0.40054 seconds