Re: Self-compiling procedures

On Feb 16, 12:47 pm, maye <kmichael....@[EMAIL PROTECTED]
> wrote:
> Hi!
> In terms of self-compiling I'm a beginner, so please excuse my
> ignorance if this is written somewhere in the manual, I couldn't find
> it easily at least:
> So far I put every procedure I consider to be useful enough for more
> than one task in its extra file, so that if it's called, IDL compiles
> it automatically, having the procedure and file name identical.
> But after a while, the number of files I have keeps growing.
> I wonder if there's another elegant way to keep things auto-compilable
> without me having to compile some kind of library before I start
> working on a task using my "library" of useful procedures.
> Am I missing something simple?
> Thanks for any hints and a nice weekend!
> Best regards,
> Michael

I think you've got it.  Just as long as they are in the path, you can
just:
1- write a new procedure(s) that needs some of the library functions.
2- compile the new procedure(s)
3- resolve_all

I think that's the "most elegant" - the compilation is really fast,
anyways.