From: "Aleksei Andevis" <aleksei@andevis.ee>
To: <gcc-help@gcc.gnu.org>
Subject: gcc linker error
Date: Wed, 18 Feb 2004 13:09:00 -0000 [thread overview]
Message-ID: <01e001c3f620$780425f0$6f0015ac@corp.fusionone.com> (raw)
Hello All ,
I use MinGW32 with 3.3.1 gcc
and build Win32 DLL
What you think about this construction:
Class MyVariant have got:
- MyVariant& MyVariant::operator=(const MyVariant& var)
exist some another class , where MyVariant is - father (teplated classes)
template<enumFieldType typeID>
class TMyVariant : public MyVariant
....
...
typedef TMyVariant<eFieldType_Float> CMyFloatVariant
All this stuff compiler,builded and resides in some DLL
----------------------------------------------------------------------------
-------------------------------------
and question:
Why contruction
MyVariant myvar(....);
myvar = CMyFloatVariant(tag, poleVar->fltVal);
compiled ,BUT causing Linker error
undefined reference to `MyVariant::operator=(MyVariant const&)
when I build this DLL with DLL , where is defined MyVariant and operator's
Best Regards
next reply other threads:[~2004-02-18 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 13:09 Aleksei Andevis [this message]
2006-06-29 12:26 rtariq
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01e001c3f620$780425f0$6f0015ac@corp.fusionone.com' \
--to=aleksei@andevis.ee \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).