| Re: large source trees and networked paths in 7.0 [message #57249 is a reply to message #57235] |
Wed, 05 December 2007 15:29   |
Doug Edmundson
Messages: 58
Registered: November 2005
|
Member |
|
|
Rick Towler wrote:
> b_gom wrote:
>
>> Also, this will effectively force all users
>> to setup a workspace and juggle projects for all the libraries, which
>> means I can't just tell new users who just write simple programs to
>> ignore the projects\workspace features.
>
> That's not how I read Doug's email (Re: IDL 7 on LINUX Question dated
> 11/30 @5:55 PST). He states that you can turn off the "Update IDL Path
> Preference" property which will allow IDL 7 to behave like earlier
> versions. I would guess (I haven't installed it yet) that you can unset
> this property, set the path appropriately, never use the projects, and
> write simple programs as before.
>
> -Rick
>
When the "Update IDL Path Preference" property is turned off, the IDL
Workbench won't add/remove projects to your path, but it will still try
and parse all your PRO code in !path, open projects, open editors and
current directory. Path management and construction of the PRO code
database are distinct. The former can be turned off via that project
property; the latter can't.
The only way I can see to minimize this is what I think already has been
suggested. Namely, have the IDL Workbench manage your path (at least
with respect to the large libraries) and close those large library
projects that are not being used. Closed projects are not parsed.
Unfortunately this may not be a practical option, but it's something to
consider.
Suffice it to say the IDL Workbench needs to do a smarter job with the
parsing. There is a plan to improve that module.
Doug
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
