🚀 go-pugleaf

In article fsf@pil.idt.unit.no, erikoest@idt.unit.no (Erik Oestlyngen) writes:
>
>When i define two different structs with the same name in two
>different files, my compiler don't complain. I can then use the struct
>as input parameter for a function in one file, and from the other send
>the different struct into the function. The function will then get
>an other input type than it expects.

>What does the ansi-C++ standard say about this?

The One-Definition Rule says in part that two types with the same name
in the same scope must have the same definition.

Your code violates the One-Definition Rule, and has undefined behavior.
The compiler is not required to diagnose the error.

---
Steve Clamage, stephen.clamage@eng.sun.com


[ To submit articles: Try just posting with your newsreader.
		      If that fails, use mailto:std-c++@ncar.ucar.edu
  FAQ:    http://reality.sgi.com/employees/austern_mti/std-c++/faq.html
  Policy: http://reality.sgi.com/employees/austern_mti/std-c++/policy.html
  Comments? mailto:std-c++-request@ncar.ucar.edu
]