> Again, it compiles for me (g++ main.cpp -Wall). What does gcc -v
> give you? Same as me:
> gcc version egcs-2.91.60 19981201 (egcs-1.1.1 release)
i have:
  gcc version egcs-2.91.60 19981201 (egcs-1.1.1 release)


> and indeed, a grep for "binary" on apvector* returns nothing, so the error
> message seems correct.
oops, sorry, that was the member function i had to write for my assignment, just comment out that line :)

> I did get rid of
> #include "apvector.cpp"
> from apvector.h before doing that though, and it compiled cleanly with no
> mention of assert.h.
why would i remove that? if i need to compile an application that uses the apvector class, I can just do an #include "apvector.h", and have it take care of the apvector.cpp for me... 

>Do you have
> /usr/include/assert.h:
>      $NetBSD: assert.h,v 1.7 1998/11/14 16:30:07 christos Exp $
i have:
       $NetBSD: assert.h,v 1.7 1998/11/14 16:30:07 christos Exp $
 

> This was on NetBSD 1.4. What port do you run? (/usr/include/machine points
> to the port)
sparc.

this is really weird. thanks for your help though... I'd really like to get c++ working on my sparcstation, because I can't wait to ditch my wintel box.
-- 


-----ethan.bakshy---------
ethan@enteract.com
http://ethan.home.dhs.org
--------------------------