Author: wyoung
Date: Sat Mar  4 09:52:07 2006
New Revision: 1222

URL: http://svn.gna.org/viewcvs/mysqlpp?rev=1222&view=rev
Log:
Removed Wishlist item corresponding to previous patch

Modified:
    branches/v2.1-bakefile/Wishlist

Modified: branches/v2.1-bakefile/Wishlist
URL: 
http://svn.gna.org/viewcvs/mysqlpp/branches/v2.1-bakefile/Wishlist?rev=1222&r1=1221&r2=1222&view=diff
==============================================================================
--- branches/v2.1-bakefile/Wishlist (original)
+++ branches/v2.1-bakefile/Wishlist Sat Mar  4 09:52:07 2006
@@ -241,36 +241,6 @@
          object may be able to look up a suitable Connection object
          for the manipulators.
 
-       o SSQLS structures include some static elements (_table and
-         names[]), which are defined within the macro.  If you
-         put an SSQLS declaration in a header file and #include
-         that from multiple locations, you get a multiply-defined
-         symbol warning.  Some ways to separate the definition from
-         the declaration:
-
-                 o Give the SSQLS macros another parameter, to
-                   suppress static definition.
-
-                 o Put statics in a separate macro, which the
-                   user must instantiate once in a .cpp file.
-                   (Similar to the way MFC message maps work.)
-
-                 o Put statics in a sub-macro, conditionally defined,
-                   which SSQLS is implemented in terms of.  Define the
-                       condition macro in one module within your
-                       program.
-
-                 o Redesign the SSQLS mechanism entirely.  Instead of
-                   defining SSQLSes by instantiating macros, you could
-                   declare the structure in, say, an XML format,
-                   which could be tranformed (XSLT?  Perl + a DOM
-                   parser?) into code very much like in the current
-                   SSQLS macros, except that it would generate
-                   separate .cpp and .h files for each structure.
-                   In addition to solving the static member problem,
-                   it would have other advantages, like side-stepping
-                   the Borland C++ macro size limit.
-
        o Deprecate sql_create_basic_* ? They have less functionality
          and they're no easier to use than sql_create and friends,
          so why bother with them?  I suppose the code generated


_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits

Reply via email to