Hi there,
We've been toying around with the idea of creating a static API scanner that
would analyze your project and list any known capabilities that your classes
may be invoking.
To comment, please see this post -
http://blogs.s60.com/creatingcarbidecpp/2006/08/platform_security_product_feat.html -
and the linked posts; they contain the mockups for the feature, and should
give a good idea about what we're thinking.
At the same time, we're looking into the needs to do similar scanning
against SDK or device API lists, so that you can easily check whether you're
likely going to run into a BC issue when deploying to a new phone. The use
cases are:
1) you've written an S60 3.0 MR app and want to see if it'll have any
problems if you target 3.0 AND 3.1 (Similar case for UIQ 3.0 --> 3.1)
2) you've written an S60 3.0 app that runs on the 3250. You now want to see
if it'll have any problems with if you target an N93.
More info on the idea here:
http://blogs.s60.com/creatingcarbidecpp/2006/08/binary_compatibility_tool_musi.html
We have limited resources, so please indicate which you think is more
important. Please post your comment to the blog, or send them to me
directly.
//markus
Carbide.c++