Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-lcc!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!agate!bionet!csd4.milw.wisc.edu!leah!itsgw!rpi!sun.soe.clarkson.edu!batcomputer!cornell!rochester!pt.cs.cmu.edu!k.gp.cs.cmu.edu!jgm From: jgm@k.gp.cs.cmu.edu (John Myers) Newsgroups: comp.std.c Subject: -DFOO Message-ID: <4089@pt.cs.cmu.edu> Date: 22 Jan 89 02:41:46 GMT References: <9422@smoke.BRL.MIL> <9445@smoke.BRL.MIL> <9436@smoke.BRL.MIL> <12570003@hpclsue.HP.COM> <915@sfmin.UUCP> Organization: Carnegie-Mellon University, CS/RI Lines: 21 In article <915@sfmin.UUCP> dfp@attunix.att.com (Dave Prosser) writes: >As a related issue, the cc command's -D and -U options do not render a >compilation system nonconforming. They are taken to be the equivalent >series of #defines followed by a series of #undefs inserted just before >the first line of the named source file(s). They are explicitly provided >by the application writer, and as such are not actually predefined macros. One could similarly claim that a compilation system by default prepends a #include to all source files, unless the "-nopollution" was given. Therefore, compilation system with namespace pollution could still be conforming. One really can't distinguish between explicit action by the user and explicit inaction. -- _.John G. Myers Internet: John.Myers@cs.cmu.edu (412) 268-5655 LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up "The datefield parameter is a six byte, null-terminated string encoding the UNIX date in base 64." -- Andrew Message System documentation. --