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

Home » Public Forums » archive » Re: large source trees and networked paths in 7.0
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: large source trees and networked paths in 7.0 [message #57223 is a reply to message #57196] Wed, 05 December 2007 18:33 Go to previous messageGo to previous message
Vince Hradil is currently offline  Vince Hradil
Messages: 574
Registered: December 1999
Senior Member
On Dec 5, 7:11 pm, "R.G. Stockwell" <noem...@please.com> wrote:
> <b_...@hotmail.com> wrote in message
>
> news:4d495e40-e358-411c-8b1f-628008b93be2@e6g2000prf.googleg roups.com...
>
>> On Dec 5, 3:57 pm, Rick Towler <rick.tow...@nomail.noaa.gov> wrote:
> ...
>> Presumably the Workbench is parsing every file in my (probably too
>> large) IDL source path, and examining files much more thouroughly than
>> previous versions of IDL did which only resolved the path for
>> each .pro file. This will add up to a large burden on my file server,
>> so apparently new users will have to configure the path more
>> restrictively, or set up projects for the specific libraries they want
>> to use. Unless I'm still missing something.
>
> Something like this is a killer for me because of two things.
> 1) I like to use a couple routines from Coyote, a couple from
> the astro lib, a couple from another library (for instance).
> So I will almost always require to have all of my projects open,
> with their hundreds of files that will be processed.
>
> 2) my 'trail of bread crumbs' development is going to be horrible.
> As an example, when I get a new data set, i start with an exploratory main
> routine that simply reads the data, and plots it out. I call it
> "look1.pro'.
> Then I will save it as 'look2.pro' and add some functionality now
> that I can actually see the data. Then 'look3.pro' adds some basic
> error checking, 'look4.pro' puts in some data bounds checking,
> look5.pro will allow keyword based functionality, then i finalize
> it as 'read_QWERTYData.pro'. I put all the old look*.pro routines
> in a ../devel folder so I can dig back into it if i ever need to.
> So a great deal of my code is development - not intended for final
> use, but explicitly stored with the final code so I can find it.
>
> With this setup, I guess I will have to cheat and try to fool IDL7
> into skipping the programs (like renaming them look*.pro_devel or
> something).
>
> Cheers,
> bob

Not to be rude, but I think you should look into CVS or SVN... ;^)
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Pointers problem - Unable to dereference NULL pointer
Next Topic: Re: eclipse ridiculously slow over ssh

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

Current Time: Sat Oct 11 21:25:25 PDT 2025

Total time taken to generate the page: 0.56454 seconds