[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Indexing conf call - summary
|
Hi Markus,
I agree that we need to use the resource plugin to make relocatable PDOMs
possible. However, I think the dependency does not necessarily need to be
enforced at the IWritableIndex level. In particular, I am referring to
addFile(IPath), and getFile(IPath). If we use Strings instead of IPaths,
we could use IPath.toPortableString() to preserve all the information in
the IPath, and Path(portableString) to reconstruct the original.
As for the indexer, I agree it would be impossible to decouple the fast or
the full indexer as-is. However we would like, at the very least, to be
able to manually populate an IWritableIndex or an IWritableIndexFragment
(backed by the PDOM) from an AST (e.g. using
IWritableIndex.addName/Macro/Include).
Jason Montojo
IBM CDT Team
IBM Toronto Lab
905-413-5228
jmontojo@xxxxxxxxxx
"Schorn, Markus"
<Markus.Schorn@wi
ndriver.com> To
Sent by: "CDT General developers list."
cdt-dev-bounces@e <cdt-dev@xxxxxxxxxxx>
clipse.org cc
Subject
25/10/2006 05:11 RE: [cdt-dev] Indexing conf call -
AM summary
Please respond to
"CDT General
developers list."
<cdt-dev@eclipse.
org>
Hi Jason,
it will be fairly easy, at least possible to isolate the parser + dom,
it is harder up to impossible to do the same for the index + indexer.
I have created https://bugs.eclipse.org/bugs/show_bug.cgi?id=162172
which should give some insight, why indexing needs the resources plugin.
Markus.
