From: Warren Young Date: May 19 2011 3:45am Subject: Re: SSQLS: Number of colomns in a table List-Archive: http://lists.mysql.com/plusplus/9353 Message-Id: MIME-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On May 18, 2011, at 9:27 PM, Adrian Cornish wrote: > Index: lib/ssqls.pl > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- lib/ssqls.pl (revision 2690) > +++ lib/ssqls.pl (working copy) > @@ -499,8 +499,9 @@ > sql_compare_define_##CMP(NAME, $parmC) > sql_construct_define_##CONTR(NAME, $parmC) > static const char* names[]; > + static const size_t field_count =3D NAME##_NULL; Instead of defining the new one in terms of the old, why not just make = this the new constant, and replace all the other ones? ssqls_NULL isn't = nearly as C++ish as ssqls::field_count. > - const char* const table() const > + const char* table() const I guess it makes sense that the second const can have no useful effect. = It would be different if it were returning a reference to the internal C = string pointer.