| RE: [cdt-dev] SetCProjectDescriptionOperation question |
|
Hi Paul, There are several reasons for using the
workspace root rule. The main two of them are: 1. The setProjectDescription for some project may update other project
referencing the former. 2. The common problem with using the more granular rules for several parts
of the CDT functionality (including setProjectDescription) is that the
functionality is invoking custom callbacks, so the functionality invoking
callbacks does not know for sure the scope of the operations the callback is intended
to perform, e.g. the setProjectDescription can not guarantee that the callbacks
it is calling making modifications the given project only. A simplest example to
illustrate that (I believe we’ve encountered that several times in CDT
when using rules more granular than the root) is when the call-back is fails trying
to acquire the root rule while being called in the project rule context. Regards, Mikhail From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Warren.Paul@xxxxxxxxx The
rule for SetCProjectDescriptionOperation is the workspace root rather than the
project whose description is being saved. There's also some code in
CProjectDescriptionManager that runs (seemingly) project specific operations
under the workspace rule. I'm wondering if this is really necessary, or
if it was just an oversight. Anybody know? Thanks,
-------------------------------------------------------------------- Closed Joint Stock Company Intel A/O Registered legal address: 125252, Moscow, Russian Federation, Chapayevsky Per, 14. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. |