| Re: Another IDL 6.2 Project Problem [message #45349] |
Tue, 06 September 2005 12:44 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
JD Smith writes:
> No really... I wasn't trying to be cheeky, just expressing ignorance. Are
> projects more than collections of files easily called up at once? What
> are their advantages?
In theory, I think projects are designed so that you can
leave programs in library directories and add them to
your project without moving them. Then, when you "build"
the project, you get one file with all the executable
code.
In practice, I don't think too many people ship executable
files. I think they ship source code too. Then the whole
project idea breaks down completely because IDL doesn't
store the build order with the project. So you have to
dump all the damn program files in a single directory to
make it work on someone else's machine anyway.
So, come to think of it, there probably isn't a single
good reason for *using* projects, except that I find it
a reasonably good interface for organizing and finding
source files as I am working on something. Paltry, I know,
but Windows users are used to grasping at straws. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: Another IDL 6.2 Project Problem [message #45350 is a reply to message #45349] |
Tue, 06 September 2005 12:18  |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Tue, 06 Sep 2005 12:30:08 -0600, David Fanning wrote:
> JD Smith writes:
>
>> Here's a project for you:
>>
>> % mkdir my_project
>> % cd my_project
>>
>> ... add routine files to the "project" aka directory.
>>
>> ... later that day, continue work on the "project":
>> % emacs my_project/*.pro
>>
>> What am I missing here? A single file included in more than one
>> project? Doesn't this encourage sloppy path/naming conventions (and
>> is nothing "ln -s" couldn't handle)?
>
> Alright, so there is *nothing* to feel superior about.
> Let's just say that doesn't exactly improve my current
> disposition. :-(
No really... I wasn't trying to be cheeky, just expressing ignorance. Are
projects more than collections of files easily called up at once? What
are their advantages?
JD
|
|
|
|
| Re: Another IDL 6.2 Project Problem [message #45352 is a reply to message #45350] |
Tue, 06 September 2005 11:30 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
JD Smith writes:
> Here's a project for you:
>
> % mkdir my_project
> % cd my_project
>
> ... add routine files to the "project" aka directory.
>
> ... later that day, continue work on the "project":
> % emacs my_project/*.pro
>
> What am I missing here? A single file included in more than one
> project? Doesn't this encourage sloppy path/naming conventions (and
> is nothing "ln -s" couldn't handle)?
Alright, so there is *nothing* to feel superior about.
Let's just say that doesn't exactly improve my current
disposition. :-(
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: Another IDL 6.2 Project Problem [message #45353 is a reply to message #45352] |
Tue, 06 September 2005 10:40 |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Tue, 06 Sep 2005 09:12:53 -0600, David Fanning wrote:
> Michael Wallace writes:
>
>> Oh, you know you love IDL 6.2. Just don't use the IDLDE. :-)
>
> Uh, well, this is the *Windows* version, so I don't have much
> choice in the IDLDE matter. And, besides, projects are the
> one and only thing I can still lord-over the EMACS guys. It's
> hard to feel superior though, when the only thing you have that
> works better than their stuff does, doesn't work. :-(
Here's a project for you:
% mkdir my_project
% cd my_project
... add routine files to the "project" aka directory.
... later that day, continue work on the "project":
% emacs my_project/*.pro
What am I missing here? A single file included in more than one
project? Doesn't this encourage sloppy path/naming conventions (and
is nothing "ln -s" couldn't handle)?
JD
|
|
|
|
| Re: Another IDL 6.2 Project Problem [message #45354 is a reply to message #45353] |
Tue, 06 September 2005 08:12 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Michael Wallace writes:
> Oh, you know you love IDL 6.2. Just don't use the IDLDE. :-)
Uh, well, this is the *Windows* version, so I don't have much
choice in the IDLDE matter. And, besides, projects are the
one and only thing I can still lord-over the EMACS guys. It's
hard to feel superior though, when the only thing you have that
works better than their stuff does, doesn't work. :-(
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: Another IDL 6.2 Project Problem [message #45356 is a reply to message #45354] |
Tue, 06 September 2005 07:11 |
Michael Wallace
Messages: 409
Registered: December 2003
|
Senior Member |
|
|
> I'm retreating to IDL 6.1. There is really nothing in IDL 6.2
> I'm interested in anyway. This is the first time in a long time
> that I've thought a new release has gone backwards.
Oh, you know you love IDL 6.2. Just don't use the IDLDE. :-)
-Mike
|
|
|
|
| Re: Another IDL 6.2 Project Problem [message #45357 is a reply to message #45356] |
Tue, 06 September 2005 06:49 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
David Fanning writes:
> Some of you may remember my struggles trying to get a breakpoint
> set in an IDL 6.2 project. I eventually discovered a way around
> that problem and got things working correctly.
>
> Now I've run into *another* problem. It seems I can't add
> another file to the project! :-(
OK, I guess I've found a work-around for this, too. It seems
if I rename my project, then I can add a file to it. Sheesh.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
