bug-commoncpp
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: sha.cpp compiler warnings


From: Chad Yates
Subject: RE: sha.cpp compiler warnings
Date: Thu, 12 Dec 2002 09:39:22 -0800

just noticed that socket.h has a #pragma that disables C4275 warnings, so
should I'm assuming it must be ok, and that sha.cpp should have the same
directive.

from socket.h:

/*
:\projects\libraries\cplusplus\commonc++\win32\socket.h(357) : warning
C4275: non dll-interface class 'streambuf' used as base for dll-interface
class 'TCPStream'
        c:\program files\microsoft visual studio\vc98\include\streamb.h(69)
: see declaration of 'streambuf'
c:\projects\libraries\cplusplus\commonc++\win32\socket.h(358) : warning
C4275: non dll-interface class 'iostream' used as base for dll-interface
class 'TCPStream'
        c:\program files\microsoft visual studio\vc98\include\iostream.h(66)
: see declaration of 'iostream'
*/

#ifdef _MSC_VER
#pragma warning(disable:4275) // disable C4275 warning
#endif

,Chad


-----Original Message-----
From: Chad Yates [mailto:address@hidden
Sent: Thursday, December 12, 2002 9:33 AM
To: address@hidden
Subject: sha.cpp compiler warnings


When compiling sha.cpp under under MS Visual Studio 6.0 I recieve the
following Level 2 warnings:

sha.cpp
..\include\cc++/digest.h(406) : warning C4275: non dll-interface class
'ost::SHA64DigestHelper' used as base for dll-interface class
'ost::SHA1Digest'
        ..\include\cc++/digest.h(381) : see declaration of
'SHA64DigestHelper'

..\include\cc++/digest.h(424) : warning C4275: non dll-interface class
'ost::SHA64DigestHelper' used as base for dll-interface class
'ost::SHA256Digest'
        ..\include\cc++/digest.h(381) : see declaration of
'SHA64DigestHelper'

..\include\cc++/digest.h(424) : warning C4275: non dll-interface class
'ost::SHAConstant' used as base for dll-interface class 'ost::SHA256Digest'
        ..\include\cc++/digest.h(320) : see declaration of 'SHAConstant'

I don't know if this will negatively affect the dll or if it is just a
meaningless microsoft warning.

Since I'm not an expert on dlls and object-oriented programming, could
someone make a call on this.  I'd be interested to know if it is an issue or
not.

,chad




reply via email to

[Prev in Thread] Current Thread [Next in Thread]