From: "Giovanni Bajo" <giovannibajo@libero.it>
To: <e7677215@est.fib.upc.edu>
Cc: <gcc@gcc.gnu.org>
Subject: Re: nurbs cannot be compiled with gcc 3.4
Date: Wed, 24 Nov 2004 12:44:00 -0000 [thread overview]
Message-ID: <25ad01c4d210$782e33a0$2fb82997@bagio> (raw)
In-Reply-To: <1101288663.41a454d70a0dc@webmail.fib.upc.es>
e7677215@est.fib.upc.edu wrote:
> I need to install nurbs++-3.0.11 compiling it with gcc 3.4...., it
> can be compiled with gcc 3.3 but it cannot be compiled with gcc 3.4,
> it returns a lot of errors. I soved some problems of templates, but
> there's one I can't solve :
>
> nurbs.cpp: In member function `BasicList<PLib::Point_nD<T, D> >
> PLib::NurbsCurve<T, N>::tesselate(T, BasicList<T>*) const [with T =
> float, int N = 3]':
> f_nurbs.cpp:56: instantiated from here
> nurbs.cpp:5252: error: no matching function for call to
> `BasicList<PLib::Point_nD<float, 3>
>>>> BasicList(BasicList<PLib::Point_nD<float, 3> >)'
> ../matrix/list.h:128: note: candidates are:
> BasicList<T>::BasicList(BasicList<T>&) [with T =
> PLib::Point_nD<float, 3>] nurbs.cpp: In member function
> `BasicList<PLib::Point_nD<T, D> > PLib::NurbsCurve<T,
> N>::tesselate(T, BasicList<T>*) const [with T = float, int N = 2]':
Looks like you are attemping to bind a temporary to a non-const reference. This
is invalid. More to the point, a copy constructor should always be declared as
A(A const &), not A(A&). BasicList<T>'s copy constructor seems to violate this.
BTW, when upgrading to 3.4, http://gcc.gnu.org/gcc-3.4/changes.html can be very
helpful.
Giovanni Bajo
next prev parent reply other threads:[~2004-11-24 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 10:27 e7677215
2004-11-24 12:44 ` Giovanni Bajo [this message]
2004-11-24 16:30 ` e7677215
2004-11-24 16:34 ` Giovanni Bajo
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='25ad01c4d210$782e33a0$2fb82997@bagio' \
--to=giovannibajo@libero.it \
--cc=e7677215@est.fib.upc.edu \
--cc=gcc@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).