Inline member functions

[kelvSYC]

I'm not sure if it violates standards or if it's just one of gcc's
quirks, but on gcc with Mac OS X (at least with my installation), for
some reason inline member functions that are not part of the class
declaration always produce linker errors.

For example, take a piece of my code:

// random access iterator for Cocoa Foundation's NSArray
// technically obj-c++, but only the c++ part that is relevant
class NSArrayIterator : std::iterator<...> {
// template arguments above not really relevant
unsigned int index;

public:
NSArrayIterator& operator++() { index++; return *this; }
};

The above compiles and links fine, but the one below gives out a linker
error

(NSArrayIterator.h)
class NSArrayIterator : std::iterator<...> {
unsigned int index;

//...
public:
NSArrayIterator& operator++();
};

(NSArrayIterator.mm)
inline NSArrayIterator& NSArrayIterator::operator++() {
index++;
return *this;
}

Is this supposed to be standard behavior (that it compiles but doesn't
link), a gcc quirk, or some other quirk? Is this issue similar to that
export and templates? If it's a gcc or linker thing, what should I set
in order for the second one to properly link?

--
I am only a mirage.

[Jack Klein]

On Mon, 06 Jun 2005 06:51:04 GMT, kelvSYC <ke*****@no.email.shaw.ca>
wrote in comp.lang.c++:

I'm not sure if it violates standards or if it's just one of gcc's
quirks, but on gcc with Mac OS X (at least with my installation), for
some reason inline member functions that are not part of the class
declaration always produce linker errors.

For example, take a piece of my code:

// random access iterator for Cocoa Foundation's NSArray
// technically obj-c++, but only the c++ part that is relevant
class NSArrayIterator : std::iterator<...> {
// template arguments above not really relevant
unsigned int index;

public:
NSArrayIterator& operator++() { index++; return *this; }
};

The above compiles and links fine, but the one below gives out a linker
error

(NSArrayIterator.h)
class NSArrayIterator : std::iterator<...> {
unsigned int index;

//...
public:
NSArrayIterator& operator++();
};

(NSArrayIterator.mm)
inline NSArrayIterator& NSArrayIterator::operator++() {
index++;
return *this;
}

Is this supposed to be standard behavior (that it compiles but doesn't
link), a gcc quirk, or some other quirk? Is this issue similar to that
export and templates? If it's a gcc or linker thing, what should I set
in order for the second one to properly link?

This is not similar to export for templates. The inline keyword
requests that the compiler substitute the executable code for the
function body in place of the call. It can do this if and only if it
has the source of the function in scope, to generate the code.

If you want the compiler to have the option of honoring your request
to inline the member functions, they need to be in the header.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html