🚀 go-pugleaf

In article <4uo8it$ogu@dartvax.dartmouth.edu>, crow@coos.dartmouth.edu
(Preston F. Crow) wrote:

>>>Christopher R Volpe <volpe@ash.crd.ge.com> writes:
>>>>Preston F. Crow wrote:
>>>>> Christopher R Volpe <volpe@ash.crd.ge.com> writes:
>>>>> 
>>>>> >comp.std.c answer: The compiler is allowed to know the semantics of
>>>>> >printf, and should know that the printf function will not modify
>>>>> >flag_pt, despite the fact that other user-defined functions could.
>>>>> 
>>>>> No, the compiler can't assume anything about printf(), as the user
>>>
>>>>Bzzzt. Thanks for playing.

  1/ You should be able to turn this behavior off with

      -fno-builtins

  2/ ANSI says (4.1.2.1)

      ...If the program declares or defines an identifier with the
      same name as an identifier reserved in that context (other than
      allowed by 4.1.6) the behavior is undefined.

     The 'that context' refers to reserved identifiers declared in the
     library header files.

So, my interpretation is that:

   a. RTFM (or RTF info-files, in the case of gcc), and you can
      dumb-down the compiler.

   b. ANSI allows a compiler to do strange and wonderous things to
      recognize those names provided by the standard library header
      files.

-- Al Lehotsky

-- 
                    Quality Software Management
                  (617)862-5418 (617)674-1096 FAX
                        lehotsky@tiac.net
                 http://www.tiac.net/users/lehotsky
                   Software Process Improvement
                      Management Consulting