From 37f3bd506f1623719a87897d10c7d4ed5169fcc0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Rombauts?= Date: Sat, 7 Apr 2012 08:58:53 +0200 Subject: [PATCH] sqdbpp review --- wrappers.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/wrappers.md b/wrappers.md index 11567d6..172316f 100644 --- a/wrappers.md +++ b/wrappers.md @@ -3,7 +3,6 @@ http://stackoverflow.com/questions/120295/what-is-a-good-oo-c-wrapper-for-sqlite http://stackoverflow.com/questions/818155/sqlite-alternatives-for-c - - **sqdbcpp**: RAII design, no depandencies, UTF-8/UTF-16, new BSD license (http://code.google.com/p/sqdbcpp/) - **sqlite3pp**: uses boost, MIT License (http://code.google.com/p/sqlite3pp/) - **SQLite++**: uses boost build system, Boost License 1.0 (http://sqlitepp.berlios.de/) - **CppSQLite**: famous Code Project but old design, BSD License (http://www.codeproject.com/Articles/6343/CppSQLite-C-Wrapper-for-SQLite/) @@ -15,6 +14,7 @@ http://stackoverflow.com/questions/818155/sqlite-alternatives-for-c - (++) very well documented, in code and with a very good informal presentation - (+) is maintained (recent), initial release is 0.1.0, January 2012 (started in 2010) - (+/-) uses boost (some more dependancies...) +- (-) uses boost coding style (I tend to prefer CamelCaps or Java coding style) - (-) a bit complicated : offer many way to do the same thing where I would prefer a clean choice - (-) thus it does not impose RAII, as it is still possible to open or close a database outside constructor/destructor - (---) LPGPL : for me, this is a stopper as I would like to be able to use it in commercial products @@ -25,3 +25,13 @@ http://stackoverflow.com/questions/818155/sqlite-alternatives-for-c - comment on returning error code instead of exception that shall not be thrown when exepected (!?) - explain the noncopyable property for RAII design + **sqdbcpp**: + - (++) new BSD license (http://code.google.com/p/sqdbcpp/) + - (+) CamelCaps + - (+) STL is the only depandancy + - (+) RAII design, with some good ideas, + - (-) but with some unnecessary complexity, and some unused code (RefCount...) + - (-) UTF-8/UTF-16 : the second is not portable + - (--) Not documented + - (---) Not maintained/not finished : contact author !? +