[cdt-dev] Documenting broken APIs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-dev] Documenting broken APIs

From: Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>
Date: Wed, 21 Oct 2015 17:10:29 +0000
Accept-language: en-CA, en-US
Delivered-to: cdt-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/cdt-dev>
List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: AdEMI2LePHRFooIJR9q9HeDhU5gUYQ==
Thread-topic: Documenting broken APIs

Hi,

with the CDT 9.0 release allowing to modify APIs, some non-backwards compatible changes have already gone in to master. That is fine.

Is it of value to document those changes in detail in the N&N page?
I feel it is something important to help people deal with compilation errors due to those API changes. However if people feel like they can manage easily without that info, let's not spend time on it.

Is a list of API changes something important for extenders?

Thanks

Marc

Prev by Date: Re: [cdt-dev] FW: New topic in forum C / C++ IDE (CDT), called Why can't it "just work"?, by Rob Lewis
Next by Date: Re: [cdt-dev] Documenting broken APIs
Previous by thread: [cdt-dev] FW: New topic in forum C / C++ IDE (CDT), called Why can't it "just work"?, by Rob Lewis
Next by thread: Re: [cdt-dev] Documenting broken APIs
Index(es):
- Date
- Thread

Breadcrumbs