cated to
this flag, i.e. release+_SECURE_SCL=0 and release+_SECURE_SCL=1.
Another, approach is to always use _SECURE_SCL=0 and document it. In this
case, users that concerned about buffer overruns and ready to sacrifice
performance, will be explicitly overriding it in their environment.
--
View this
On Thu, 2011-12-15 at 10:11 +0400, Ivan Pechorin wrote:
> 2011/12/14 mikmela :
> > I'm having a lot of issues passing std::strings into ActiveMQ-CPP
> > interfaces,
> > i.e. Connection, Session, Message and etc.
> > Even though I'm using MS VS2010 to build both activemq-cpp dll and my
> > applicat
2011/12/14 mikmela :
> I'm having a lot of issues passing std::strings into ActiveMQ-CPP interfaces,
> i.e. Connection, Session, Message and etc.
> Even though I'm using MS VS2010 to build both activemq-cpp dll and my
> application with the same version of multithreaded c-runtime dll
> MSVCP100.dll
erytime, you move
to build an app with newer compiler you need to rebuild activemq-cpp as
well?
Wouldn't it be better to stick to primitive const char* instead?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-using-ActiveMQ-CPP-interfaces-where-std-stri
