| large source trees and networked paths in 7.0 [message #57295] |
Wed, 05 December 2007 11:17 |
b_gom
Messages: 105
Registered: April 2003
|
Senior Member |
|
|
We have a site license with several IDL seats, configured so that all
users share one networked directory tree of source code. In earlier
versions of IDL, searching this rather large path took several seconds
when IDL loaded for the first time, but this worked ok and also
simplified maintenance and backup of all our internal and external IDL
code.
Now, in version 7.0, startup is much faster, but after the workbench
has loaded I get a message at the bottom of the application saying
"Analyzing Code..." which persists for a LONG time (>10s of minutes).
Also, there is an accompanying network usage of 170 KB/s incoming and
outgoing during this time.
What is the workbench doing? Exactly what does 'Analyzing Code' mean?
What is the recommended way to configure the workbench when you have a
huge library of code that you reference often? Am I forced to separate
out individual routines from the many external libraries I use, and
group them into each project or workspace that uses them? Is this
going to save me time in the long run?
Thanks
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
