You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Ivan Pechorin <iv...@gmail.com> on 2010/01/26 15:46:29 UTC
ActiveMQ C++: warning "deletion of pointer to incomplete type"
Hello
The latest version of ActiveMQ C++ client (3.1.0) gives the following
warning (multiple times) when compiling it with Visual C++ 2008 SP1 on
Win32:
1>SimpleLogger.cpp
1>c:\dev_vc9\activemq\activemq-cpp\src\main\decaf/lang/Pointer.h(357) :
warning C4150: deletion of pointer to incomplete type
'decaf::lang::ThreadProperties'; no destructor called
1> c:\dev_vc9\activemq\activemq-cpp\src\main\decaf/lang/Thread.h(39)
: see declaration of 'decaf::lang::ThreadProperties'
1>
c:\dev_vc9\activemq\activemq-cpp\src\main\decaf/lang/Pointer.h(356) : while
compiling class template member function 'void
decaf::lang::Pointer<T>::onDeleteFunc(T *)'
1> with
1> [
1> T=decaf::lang::ThreadProperties
1> ]
1> c:\dev_vc9\activemq\activemq-cpp\src\main\decaf/lang/Thread.h(73)
: see reference to class template instantiation 'decaf::lang::Pointer<T>'
being compiled
1> with
1> [
1> T=decaf::lang::ThreadProperties
1> ]
Could this be dangerous?
I created project and solution files for VC2008 using standard convertion
procedure from VC2005 files shipped with the source distribution. In
addition to that, I disabled built-in wchar_t, but this change couldn't be
the reason of the warning.
Thanks
--
View this message in context: http://old.nabble.com/ActiveMQ-C%2B%2B%3A-warning-%22deletion-of-pointer-to-incomplete-type%22-tp27323723p27323723.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ C++: warning "deletion of pointer to incomplete type"
Posted by Timothy Bish <ta...@gmail.com>.
On Tue, 2010-01-26 at 06:59 -0800, Ivan Pechorin wrote:
> By the way, is it the right place for such questions, or is it better to open
> JIRA issue?
Sure, its fine to ask here. I do encourage our users to open issues as
well though, since things can sometimes get lost or missed on the
mailing list. Once its in Jira its hard to forget about it.
Regards
Tim.
--
Tim Bish
http://fusesource.com
http://timbish.blogspot.com/
Re: ActiveMQ C++: warning "deletion of pointer to incomplete type"
Posted by Ivan Pechorin <iv...@gmail.com>.
By the way, is it the right place for such questions, or is it better to open
JIRA issue?
--
View this message in context: http://old.nabble.com/ActiveMQ-C%2B%2B%3A-warning-%22deletion-of-pointer-to-incomplete-type%22-tp27323723p27323921.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ C++: warning "deletion of pointer to incomplete type"
Posted by jkirby <jk...@gmail.com>.
I saw this too with Visual Studio 2005 but only when I compiled the 'Dll'
configurations (debug and release show this).
Timothy Bish wrote:
>
>
> I haven't seen that particular warning in my recent compiles on Windows,
> and nobody else has reported it. I made several fixes this weekend in
> trunk for some memory leak problems so you might want to grab the latest
> trunk code before you start working on it.
>
> Regards
> Tim.
>
>
>
>
>
>
>
--
View this message in context: http://old.nabble.com/ActiveMQ-C%2B%2B%3A-warning-%22deletion-of-pointer-to-incomplete-type%22-tp27323723p27757362.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ C++: warning "deletion of pointer to incomplete type"
Posted by Timothy Bish <ta...@gmail.com>.
On Tue, 2010-01-26 at 07:01 -0800, Ivan Pechorin wrote:
> > Its possible it could cause an issue. You are welcome to open a new
> > Jira issue and submit a patch to fix the problem.
>
> Thanks, Tim.
> I'll try to fix it.
> Just wanted to check if anybody else already done that :)
I haven't seen that particular warning in my recent compiles on Windows,
and nobody else has reported it. I made several fixes this weekend in
trunk for some memory leak problems so you might want to grab the latest
trunk code before you start working on it.
Regards
Tim.
--
Tim Bish
http://fusesource.com
http://timbish.blogspot.com/
Re: ActiveMQ C++: warning "deletion of pointer to incomplete type"
Posted by Ivan Pechorin <iv...@gmail.com>.
> Its possible it could cause an issue. You are welcome to open a new
> Jira issue and submit a patch to fix the problem.
Thanks, Tim.
I'll try to fix it.
Just wanted to check if anybody else already done that :)
--
View this message in context: http://old.nabble.com/ActiveMQ-C%2B%2B%3A-warning-%22deletion-of-pointer-to-incomplete-type%22-tp27323723p27323938.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ C++: warning "deletion of pointer to incomplete type"
Posted by Timothy Bish <ta...@gmail.com>.
On Tue, 2010-01-26 at 06:46 -0800, Ivan Pechorin wrote:
> Hello
>
> The latest version of ActiveMQ C++ client (3.1.0) gives the following
> warning (multiple times) when compiling it with Visual C++ 2008 SP1 on
> Win32:
>
Its possible it could cause an issue. You are welcome to open a new
Jira issue and submit a patch to fix the problem.
Regards
Tim.
> 1>SimpleLogger.cpp
> 1>c:\dev_vc9\activemq\activemq-cpp\src\main\decaf/lang/Pointer.h(357) :
> warning C4150: deletion of pointer to incomplete type
> 'decaf::lang::ThreadProperties'; no destructor called
> 1> c:\dev_vc9\activemq\activemq-cpp\src\main\decaf/lang/Thread.h(39)
> : see declaration of 'decaf::lang::ThreadProperties'
> 1>
> c:\dev_vc9\activemq\activemq-cpp\src\main\decaf/lang/Pointer.h(356) : while
> compiling class template member function 'void
> decaf::lang::Pointer<T>::onDeleteFunc(T *)'
> 1> with
> 1> [
> 1> T=decaf::lang::ThreadProperties
> 1> ]
> 1> c:\dev_vc9\activemq\activemq-cpp\src\main\decaf/lang/Thread.h(73)
> : see reference to class template instantiation 'decaf::lang::Pointer<T>'
> being compiled
> 1> with
> 1> [
> 1> T=decaf::lang::ThreadProperties
> 1> ]
>
> Could this be dangerous?
>
> I created project and solution files for VC2008 using standard convertion
> procedure from VC2005 files shipped with the source distribution. In
> addition to that, I disabled built-in wchar_t, but this change couldn't be
> the reason of the warning.
>
> Thanks