Difference between revisions of "CDT/calls/Indexing23102006"

Revision as of 12:29, 23 October 2006

Do we need to co-ordinate unit test writing?
Performance testing
74433 (offline/composite indexes) update
Discussion of index model (IndexFactory)
- Should an indexer attached to project A write to other projects
- Do we want to model static functions, unnamed namespaces in the index?
How to present elements from the index in the UI.
Proposal: Use String instead of IPath in IIndex and IIndexFragment to reduce dependencies for remote clients

Co-ordination of unit tests
- We're happy for duplication to happen - more tests is better than fewer
Performance testing
- Andrew to try to get this working locally
74433 update
- proof on concept is working, by having new PDOMBinding records used instead of placeholders
- work has begun on an CIndexProvider extension point. Proposed draft patch to follow
- a IPDOMVisitor impementation for traversing multiple pdom has been tested, we might not need this
static functions
- Markus to comment in bugzilla
anonymous namespaces
- Markus to remove them from index (they go in under the empty name)
Finding the enclosing function for a reference - this is not currently stored in the index
- Suggestion of storing additional location information in a special definition class
- Markus to raise a bugzilla
Standardization of displaying objects from the index in a UI
- Lifecycle issue - objects returned from index queries can expire
- Markus suggests using ICElements to store information
IBM propose using String rather than IPath in index API
- Discussion of whether IIndexFragment can be public long term
- We need to support EFS also - which uses URI (part of the JDK - so may benefit IBM)

@@ Line 41: / Line 41: @@
 *IBM propose using String rather than IPath in index API
 **Discussion of whether IIndexFragment can be public long term
+**We need to support EFS also - which uses URI (part of the JDK - so may benefit IBM)