🚀 go-pugleaf

There is a bug in gcc-2.2.2 with defining functions which return a template object
Foo<type> where Foo<type> has not yet been seen by the compiler.  Consider the
following program:

---------------------------------------------------------------------------------

template <class T> class Foo
  {
public:
   Foo() { }
   ~Foo() { }
  };

#ifdef THIS_WORKS_OK
Foo<int> Bar();
#endif

#ifdef THIS_ALSO_WORKS_OK
Foo<int> global_foo;
#endif

Foo<int> Bar() { Foo<int> b; return(b); }

---------------------------------------------------------------------------------

picard [473]% g++ -c -Wall -v junk.c
Reading specs from /cse/grad/skohn/lib/gcc-lib/sparc-sun-sunos4.1/2.2.2/specs
gcc version 2.2.2
 /cse/grad/skohn/lib/gcc-lib/sparc-sun-sunos4.1/2.2.2/cpp -lang-c++ -v -undef -D__GNUC__=2 -D__GNUG__=2 -D__cplusplus -Dsparc -Dsun -Dunix -D__sparc__ -D__sun__ -D__unix__ -D__sparc -D__sun -D__unix -Wall junk.c /usr/tmp/cca11751.i
GNU CPP version 2.2.2 (sparc)
 /cse/grad/skohn/lib/gcc-lib/sparc-sun-sunos4.1/2.2.2/cc1plus /usr/tmp/cca11751.i -quiet -dumpbase junk.cc -Wall -version -o /usr/tmp/cca11751.s
GNU C++ version 2.2.2 (sparc) compiled by GNU C version 2.2.2.
junk.c:16: semicolon missing after declaration of `Foo<int>'
junk.c: In function `int  Bar ()':
junk.c:16: aggregate value used where an integer was expected

However, if we define either of the two #ifdef macros, everything works OK.
So, you can work around the problem by declaring the function before the
actual definition.  Sigh.

-- Scott