| Re: Self-compiling procedures [message #58727 is a reply to message #58722] |
Sat, 16 February 2008 15:50   |
maye
Messages: 29
Registered: June 2006
|
Junior Member |
|
|
On Feb 16, 11:30 pm, Spon <christoph.b...@gmail.com> wrote:
> On Feb 16, 10:18 pm, maye <kmichael....@googlemail.com> wrote:
>
>
>
>> On Feb 16, 11:05 pm, Spon <christoph.b...@gmail.com> wrote:
>
>>> On Feb 16, 6:47 pm, maye <kmichael....@googlemail.com> 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
>
> Short answer - no.
>
> Here, have a read of this, particularly the second half:
>
> http://www.dfanning.com/tips/namefiles.html
>
> Good luck,
> Chris
Thx will do.
And I got an idea: I could at least sort things by subfolders. As IDL
parses recursively - as it was mentioned before - I can put related
procedures together.
Thanks for your hints.
Cheers,
Michael
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
