On Feb 16, 4:18 pm, maye <kmichael....@[EMAIL PROTECTED]
> wrote:
> On Feb 16, 11:05 pm, Spon <christoph.b...@[EMAIL PROTECTED]
> wrote:
>
> > On Feb 16, 6: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
>
> > You should add your library directory to your !PATH -
File->Preferences->Path.
>
> > Then you can call every procedure/function in the library without ever
> > having to compile it first. In fact, any directory that has any .pro
> > file in it is probably better off in !PATH. Top level directories,
> > anyway - thankfully IDL searches recursively.
>
> > Take care,
> > Chris
>
> Thanks so much for your fast answers, and I'm very sorry, I was too
> imprecise with my question, silly me.
> I am actually looking for a way to group similar procedures into one
> file to reduce the amount of library files, it's just harder to
> maintain.
> Is there a way to keep things still self-compilable when I put several
> procedures into one file?
>
> Cheers,
> Michael
I started out putting several procedures in on file and found it
harder to maintain that way. With each file a separate procedure I
know exactly where to look. That said, of course it makes sense to
group procedures and functions in one file, if they are only used by
the "main" function (the one with the same name as the file). If they
are going to be used by themselves, then I break them out as separate
files.
|
