Srinivas,
I could think of problems in performance...maintenance... etc.
consider the 1000 line config spec and the fact that they are evaluated
top down for every element to be displayed in a directory (or mercy the
build).. CC checks each rule from top to a match for each so every time you
step in to a directory it must evaluate the rules (in fact more often than
that- but lets keep is simple for now)... If you have 1000 lines that
means that some files use the 1000th rule (otherwise why have it).. now
lets say you cd to a directory where the "average" element in it matches on
one of the first 4 rules... you would see different performance than it you
cd in to a directory where the "average" element matched on the 1000th
rule... Imagine large directories that match on average the 1000th rule...
imagine complies... Such config specs effect compiles, directory
navigation, speed of GUI, speed of other tools... etc... NOT TO MENTION the
upkeep of such a file....
Are you sure that you could not use another method.. labeling, branching..
etc..
How did and why are the config specs so verbose....
-Charles
At 10:01 AM 2/9/00 -0600, Srinivas Saraswatula (EUS) wrote:
>Hi all:
>
>I am trying to find out if there is any limitation on the number of lines in
>a config spec.
>Are there any known problems caused by very large config specs (1000+
>lines)?
>
>Any info appreciated.
>
>Thanks
>
>Srinivas
>_________________________________________________________
>Srinivas Saraswatula
>ClearCase CM
>
>
>
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:23:07 EDT