This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/11168] public inline methods should be kept in .o file
- From: "bangerth at dealii dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Jun 2003 13:20:53 -0000
- Subject: [Bug c++/11168] public inline methods should be kept in .o file
- References: <20030612031111.11168.wfbrodie@smug.adelaide.edu.au>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11168
bangerth@dealii.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |INVALID
------- Additional Comments From bangerth@dealii.org 2003-06-12 13:20 -------
No, inline means inline. You can't put inline methods into implementation
files and expect them to be exported. Because then they are no longer inline
for the rest of the world. inline is and should also be independent of
whether a function is public or not. After all, you can also call
protected functions from outside.
W.