On 7/14/16, Darren Duncan <dar...@darrenduncan.net> wrote: > > My recommendation on this matter is to deprecate but retain the current > include > guards that are in violation of the standard, and ALSO add new, redundant > include guards in a manner that comply with the standard. > > Thoughts on that proposal? >
We change internal-use #defines and other internal-use symbols on just about every release. This has never before caused breakage that we are aware of. Or if it has caused breakage, the developers doing such things are aware that what they are doing is not allowed and have the good sense to not complain. The guard #defines were changed here: https://www.sqlite.org/src/info/5471aca0158851d3 -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
