Request for opinions on C++ API for new third-party libraries

[bjonni]

The company I work at are planning to port one of our products, an SDK, from Windows to Symbian OS 9+. Since we do not have to worry about backwards compatibility with earlier versions of the Symbian OS we can use a more modern C++ design to handle errors and resources, since stack-unwinding in the presence of exceptions now works, but we should be able to "hide" our internal design behind a public API that more closely resembles the current Symbian OS API:s with traps/leaves etc. if you want us to.

Do you have any strong feelings about what kind of C++ API you would prefer to work with? Would you prefer one that resembles the current Symbian OS API:s with traps/leaves, cleanup and the naming convention it implies or would you prefer a more modern C++ API? Both so you can choose?

Please I'm not here to debate design choices made in the Symbian OS API. I'm looking for opinions on what kind of C++ API:s you as developers on the Symbian platform would like to work with in the future.

Kind regards,
Patrik

[skumar_rao]

What we now a days do while porting from Unix or Windows Native C++ Code to Symbian is as follows.

1. we use the OpenC to Post the Native Desktop Code to Symbian. Then
2. We try to Improve the Speed by Introducing the Native symbian APIs.
3. When all looks fine we go ahead and port the Code to Symbian API one module at a time.

[lenclud]

I found Symbian style APIs are definitely easier and more natural to use when coding using Symbian C++.

[Venky.Dadge]

Symbian style API will be the natural choice,,