Re: [cdt-dev] API use of some classes (e.g. MapEntrySourceContainer, CSo

[Doug Schaefer <dschaefer@xxxxxxx>]

Indeed. This is our chance to clean those things up. I¹m not sure when
we¹ll want to do another major release.

But we¹ll definitely need help. We have a lot of things we want to do for
Neon and things like API management has a tendency to fall off the list.

Thanks!
Doug 

On 2015-09-15, 12:10 PM, "cdt-dev-bounces@xxxxxxxxxxx on behalf of Jonah
Graham" <cdt-dev-bounces@xxxxxxxxxxx on behalf of jonah@xxxxxxxxxxxxxxxx>
wrote:

>Thanks, from the age of it I will just use it and assume that it isn't
>likely going anywhere (too far).
>
>That said, is this the kind of thing that we should be cleaning up for
>CDT 9.0, (a perhaps timely question based on the discussions of API
>versioning on the cross-project-issues-dev list).
>
>Thanks
>Jonah
>~~~
>Jonah Graham
>Kichwa Coders Ltd.
>www.kichwacoders.com
>
>
>
>On 15 September 2015 at 16:57, Doug Schaefer <dschaefer@xxxxxxx> wrote:
>> 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 :).
>>
>> Doug.
>>
>> 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.
>>
>> e.g.
>> 
>>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.addMapEntr
>>y(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
>>
>> ~~~
>> Jonah Graham
>> Kichwa Coders Ltd.
>> www.kichwacoders.com
>>
>>
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>>from
>> this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>To change your delivery options, retrieve your password, or unsubscribe
>from this list, visit
>https://dev.eclipse.org/mailman/listinfo/cdt-dev