Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] API use of some classes (e.g. MapEntrySourceContainer, CSourceLookupDirector)

Checking the git history I see that code is over 10 years old. I’m not sure we knew how to even spell API back then :).


From: <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Tuesday, September 15, 2015 at 11:03 AM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: [cdt-dev] API use of some classes (e.g. MapEntrySourceContainer, CSourceLookupDirector)

A number of places in CDT have API methods receiving or returning non-API types.

org.eclipse.cdt.debug.core.CDebugCorePlugin.getCommonSourceLookupDirector() returns non-API org.eclipse.cdt.debug.internal.core.sourcelookup.CSourceLookupDirector

org.eclipse.cdt.debug.core.sourcelookup.MappingSourceContainer.addMapEntry(MapEntrySourceContainer) receives non-API org.eclipse.cdt.debug.internal.core.sourcelookup.MapEntrySourceContainer

As a consumer of these APIs, what is the intention of such APIs? Obviously these Internals have not changed in a long time and it is hard to impossible to use the public APIs without also using internal APIs. 

It it helps, what I am trying to do is add an additional common source lookup container automatically. My customer's product ships with pre-built code that was pre-built in  /build/engineering/foo/bar.c and I want to map that to where foo/bar.c is on the user's machine. I am planning to do this by adding a path mapping (MappingSourceContainer) to the common source lookup director's container. 

Thanks for your input,

Jonah Graham
Kichwa Coders Ltd.

Back to the top