wrong. "C" style api's are the standard, even in C++ applications.
Its the established practice. Sorry if your experience is different. Modern C++ is losing its pull around here. (Silicon Valley) Very few projects use it any more. By modern, I mean Boost style and heavy templates. Most of my recent projects have consisted of ripping out templated code and replacing it with "C" friendly "API's". I still prefer C++ for most tasks. However, I like to wrap them in "C" api's so others can use them. Using stream operators or std::string in a public API is a absolutly horrible thing to do around here. Those C++ developers that develop in isolation probably have not experienced this push back. I understand. I sympothize. It just doesnt make any sense to write a utility library for general purpose use that only addresses the needs of boost style C++ developers. The core of the library needs to be written in a way that all C/C++ developers can use it. Fine, if you want to write a wrapper around the core with some fancy C++ technique go for it. On Sun, Mar 14, 2010 at 1:24 PM, joel falcou <joel.falcou@lri.fr> wrote:
Tom Brinkman wrote:
Just plain wrong.
What about arguments then ?
wrong. "C" style api's are the standard, even in C++ applications.
Which comittee decided that ? When I do C++, I do C++. If I need C API, then I write C
C++ developers need to write their api's in a way that is also "C"
friendly. Thats even more true for utility librarie
Except sometimes we can't because C lack type safety and tons of proper, strongly typed language feature.
-- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost