BIND 10 #2357: Use of reserved identifiers

BIND 10 Development do-not-reply at isc.org
Mon Oct 15 09:43:23 UTC 2012


#2357: Use of reserved identifiers
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  Unclassified  |  Sprint-Proposed
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 According to the C++ (and C) standard, everything that:
  * Begins with and underscore and then there's an upper case letter
  * Contains double underscore (two underscores following each other)
 are reserved for the implementation of compiler.

 What I understand is the authors of compilers are free to use such names
 for their crazy internal macros and functions as they wish and if they
 clash with our such names, it's our problem. In other words, such code
 using them has undefined behaviour.

 I noticed we have some such names through the code (usually the #ifndef
 __HEADER_NAME__ guards). We should replace them by something less
 dangerous.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2357>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list