From: Bastiaan B. <Bas...@li...> - 2002-02-04 10:01:01
|
> -----Original Message----- > From: hel...@ed...=20 > [mailto:hel...@ed...] > Sent: Friday, February 01, 2002 9:08 PM > To: Bastiaan Bakker; log...@li... > Subject: RE: [Log4cpp-devel] Compiling with sun CC >=20 >=20 > Yeah, that seems to do the trick! >=20 > Perhaps this could go down into a FAQ or something for > other people to take advantage of? >=20 Yes, it definitely should, but I've been to busy/lazy to write one. > First test ran OK, but the second came up with: >=20 > CC -DHAVE_CONFIG_H -I. -I. -I../include -I../include -g -c=20 > Clock.cpp > "Clock.cpp", line 47: Error: endl is not defined. > 1 Error(s) detected. >=20 > some std:: missing, perhaps. >=20 Hmm, you're right. I thought I got rid of all of them... > We are thinking about using this library in our software. Has > anyone run purify on this code to check for memory leaks? Any > routine on that before you ship new releases? >=20 Well, I don't have access to Purify myself, so it's not part of the = release routine. Incidentally other people have checked with Purify, = BoundsChecker or similar tools. If you like to see this happen within = the release regime, please volunteer to run Purify and report on the = release candidates so any leaks can be fixed before the final release... =20 > How about connection to the Lumbermill GUI/Log server? I see > that it's missing a SocketAppender class, so this probably=20 > haven't been tested? Should be easy to add such a class, though? >=20 AFAIK this has not been tried. However most of the work here is not in = the socket related stuff (for *nix machines you can already send logs = through a socket using FileAppender and a socket file descriptor), but = in writing the data conformant to the Java serialization API. But maybe = it turns out to be a very simple format, or maybe someone has created a = nice library to do it for us, I dunno. You're very welcome to contribute = :-) > Best regards, > Helge Fredriksen Cheers, Bastiaan Bakker |