SCTP Discussions

Text archives Help


Re: [SCTP-Discussion] New to sctplib / impl. without glib?


Chronological Thread 
  • From: Carsten Fuchs <CarstenFuchs AT T-Online.de>
  • To: Thomas Dreibholz <dreibh AT iem.uni-due.de>
  • Cc: sctp-discussion AT sctp.de
  • Subject: Re: [SCTP-Discussion] New to sctplib / impl. without glib?
  • Date: Tue, 05 Feb 2008 16:42:19 +0100
  • List-archive: <http://lists.franken.de/pipermail/sctp-discussion>
  • List-id: SCTP Discussions <sctp-discussion.sctp.de>

Thomas Dreibholz wrote:
Compiling as C++ is not a big problem. I have added the type casts and created a test package. You can find it here:
http://www.exp-math.uni-essen.de/~dreibh/temp/sctplib-1.0.8beta2.tar.gz

Thanks!

Just FYI, here are a few minor points that I encountered when compiling sctplib with VC(++) 8 and 9, which are both a lot more standards conforming than the older VC(++) 6, and thus possibly more picky. VC++ 6 is btw. the only Windows compiler for which precompiled glib binaries are available...

Anyways, these points might be related to compiler version issues or something else, I just noted them for completeness:

a) The Microsoft compilers predefine the _WIN32, but not the WIN32 macro, so the code should probably test for _WIN32, not WIN32.

b) The types gint32_t and uint32_t are totally unknown even to the glib. Although the fix is easy (add "typedef int gint32_t; typedef unsigned int uint32_t;" to globals.hpp), I think they shouldn't be used at all.

c) With 1.0.7 I had some problems wrt. #inlude <sys/time.h> vs. #include <time.h>. No problems with 1.0.8beta2 though -- thanks! :-)

d) There are several warnings about comparisons between signed/unsigned at the highest warning level (which I compile all my code with...). Any interest in a detailed report?

Best,
Carsten



--
Ca3D - Engine http://www.Ca3D-Engine.de
Carsten Fuchs http://www.Ca3D-Engine.de/c_Carsten.php




Archive powered by MHonArc 2.6.19+.

Top of page