Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] createCProject vs createNewStyleCProject

I agree that an official API for programmatically creating projects is badly needed, but I don't think fixing the tests should wait for it.

BTW, I have code that creates C++ projects with an external builder that doesn't call any non-API or deprecated methods.


On Thu, Jan 8, 2015 at 7:36 PM, Doug Schaefer <dschaefer@xxxxxxx> wrote:
Yes. And we really need an official API for programmatically creating projects. I have copies of random code with lots of yellow underlines all over the place to do it.

Sent from my BlackBerry 10 smartphone on the Rogers network.
From: Sergey Prigogin
Sent: Thursday, January 8, 2015 7:42 PM
To: CDT General developers list.
Reply To: CDT General developers list.
Subject: [cdt-dev] createCProject vs createNewStyleCProject

I've just noticed that most tests use CProjectHelper.createCProject as opposed to CProjectHelper.createNewStyleCProject. In fact createNewStyleCProject methods don't even seem to support creation of C++ projects. This situation looks dangerous since the tests may not catch failures that happen only with the new style projects. Should we convert all tests to run on the new-style projects?


cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top