Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] can the scanner discovery API be extended?

My private opinion is that having less interfaces is better and makes the code easier to understand. I think there are already a lot of xxx2 and xxx3 interfaces in CDT. However, I can't tell how many people have indeed implemented the config builder interfaces.
As far as I am concerned, I am not implementing any of these interfaces, I am just using IScannerConfigBuilderInfo2. So the impact on my code would be small, if the interfaces were extended or fused.
Best regards,

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sennikovsky, Mikhail
Sent: Donnerstag, 01. März 2007 12:54
To: CDT General developers list.
Subject: [cdt-dev] can the scanner discovery API be extended?

Hi all,


I’m currently investigating at how to better fit the ScannerDiscoveryProfile functionality with the New Project Model. The thing I want to achieve is to avoid functionality duplication, i.e. I’d like to reuse the reversed back Scanner Discovery functionality of the make.core plug-in in the new CDT Build System instead of duplicating this functionality.

I have a question regarding extending the Scanner Discovery API.

I noticed that to extend e.g. the IScannerConfigBuilderInfo interface the new IScannerConfigBuilderInfo2 interface was created instead of extending the IScannerConfigBuilderInfo directly although, as I understand, the IScannerConfigBuilderInfo is not supposed to have custom implementations.

Is there any reason for doing this? And in case I want to add some new methods to e.g. the IScannerConfigBuilderInfo2, or ScannerConfigInfoFactory2, should I create the new xxx3 interfaces or can just extend the existing xxx2 interfaces?




Back to the top