[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] pdom extensions?
|
Hi Elena,
we cannot easily open up the index for storing information that is not generated by the indexer. If you need to store information that is created at a later point, I think it is easier to store it else-where.
Also when storing information per function you need to decide whether to store it with the binding (represents an entity with potentially multiple declarations, definitions or reference) or with a specific occurrence of the function (a declaration, defintion or reference). Either way there is a challenge: In the former case it is unclear, when a property has to be changed (e.g. you have multiple definitions for a function, one returning null, the other not). For the latter case a there is a size issue. There are lots of occurrences and their representation should not grow beyond what we have now.
Markus.
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Alena Laskavaia
> Sent: Mittwoch, 08. Dezember 2010 02:48
> To: CDT General developers list.
> Subject: [cdt-dev] pdom extensions?
> Importance: Low
>
> I think I need to create a framework not only for checker for also for
> extended semantic information that can
> be used by other checker. For example I can keep the information that
> function may return null (or never returns null).
> This info need to be kept per function (per global variable,
> type, class, etc).
>
> The question is where do I keep this information.
> a) extend PDOM with specific semantic attributes?
> b) use some sort of generic extensions that can be attached
> to PDOM nodes?
> c) create totally different db?
>
> Ideas?
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>