* Re: Ways to use special overloaded functions
[not found] <2e393d080501221111d73e035@mail.gmail.com>
@ 2005-01-25 2:17 ` corey taylor
0 siblings, 0 replies; only message in thread
From: corey taylor @ 2005-01-25 2:17 UTC (permalink / raw)
To: nathan, eljay, lionelbuk, gcc-help
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
>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-01-25 2:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <2e393d080501221111d73e035@mail.gmail.com>
2005-01-25 2:17 ` Ways to use special overloaded functions corey taylor
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).