On 7/9/16 11:47 PM, J Decker wrote:
Okay if this should change, I would recommand a new standard for all
libraries; and since standards are so important maybe make them know about
it too...
do ... ORG_DOMAIN_APPLICATION_LIBRARY_MODULE_SOURCE_INCLUDED
where each piece becomes unqiqe so there's no collision. I'd expect
compilers these days would support more than 32 characters required by the
standard (goodbye Borland BCC 3.1).
#ifndef ORG_SQLITE_SQLITE_SQLITE_INCLUDED
and copY and paste one other time...
I mean what editor doesnt' support double click to mark a word (the above
is within the genaral defitition of a 'word' ) to copy and click somewhere
to paste?
I mean ; how many times have I had a symbol in a header that collided with
sqlite? or ffmpeg? or zlib? or... wait like never.
someone probably just never considered deprecation of reservation as a
'law' and at least demote to 'recommended practice' because some obscure
compiler somewhere would start failing?
Try to write a fully standard compliant standard library without using
any of the reserved namespace!!!
By the standard, a header defined by the standard is only allow to
define the symbols it is EXPLICITLY defined to, and the symbols in the
appropriate reserved namespaces. ANY other symbol is allowed to be
used/defined by the user.
Your suggest has a couple of problems. First, it handles the include
guard, but not a bunch of other things that need symbols. The second,
what is to be used by a programmer who doesn't own a domain? Owning a
domain is not a requirement for writing software.
--
Richard Damon
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
