This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Ways to use special overloaded functions
- From: corey taylor <corey dot taylor at gmail dot com>
- To: nathan at codesourcery dot com, eljay at adobe dot com, lionelbuk at yahoo dot co dot uk, gcc-help at gcc dot gnu dot org
- Date: Mon, 24 Jan 2005 19:50:22 -0600
- Subject: Re: Ways to use special overloaded functions
- References: <2e393d080501221111d73e035@mail.gmail.com>
- Reply-to: corey taylor <corey dot taylor at gmail dot com>
I would like to thank everyone for their involvement in helping me
pin-point the issue. I would like to especially thanks Eljay for his
in-depth involvement and emails. I believe that I can make-do with a
solution now without major shifts in our library.
Corey
On Sat, 22 Jan 2005 13:11:22 -0600, corey taylor <corey.taylor@gmail.com> wrote:
> Thanks you all for replying to my question.
>
> It seems my source for testing had issues getting to you, and it did
> have extra stuff that probably didn't need to be there.
>
> I was hoping one of you could suggest a way for use to get around the
> problem 3.4's apparant two-pass system provides.
>
> We provided templated utility classes, such as G3D::Table for doing hash maps.
>
> This class relies on an overloaded function, currently, to provide the
> hash'ed key of the class or typename in question.
>
> --
>
> The reason we have the issue is because we want to be able to use
> classes hidden in .cpp files, and not in the general header. Also, we
> want users to be able to provide their own hashcode functions for
> their own classes.
>
> G++ 3.4, however, seems to want to know everything in Table.h before
> it can be used. We cannot provide the class and then the overloaded
> function in a separate .cpp file before we use it. or g++ gives us a
> "cannot find overloaded function" error.
>
> Corey
>