From taraben.a@wige-data.de Wed Dec 04 04:16:30 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18JVdt-0003pL-00
	for bug-commoncpp@gnu.org; Wed, 04 Dec 2002 04:16:29 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18JVdn-0003Va-00
	for bug-commoncpp@gnu.org; Wed, 04 Dec 2002 04:16:26 -0500
Received: from ns2.envia-tel.net ([193.98.112.146])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18JVdl-0003C8-00
	for bug-commoncpp@gnu.org; Wed, 04 Dec 2002 04:16:21 -0500
Received: from mailserver.wige-data.de (gw1.wige-data.de [80.243.44.1])
	by ns2.envia-tel.net (8.12.4/8.12.4) with ESMTP id gB49GFAH002681
	for <bug-commoncpp@gnu.org>; Wed, 4 Dec 2002 10:16:15 +0100
Received: by mailserver.wige-data.de with Internet Mail Service (5.5.2653.19)
	id <W7K7LSZL>; Wed, 4 Dec 2002 10:16:09 +0100
Received: from wige-data.de (taraben_a.wigemic.lpz [10.1.11.14]) by mailserver.wige-data.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W7K7LSZK; Wed, 4 Dec 2002 10:16:07 +0100
From: taraben.a@wige-data.de
To: bug-commoncpp@gnu.org
Message-ID: <3DEDC7D4.6090907@wige-data.de>
Date: Wed, 04 Dec 2002 10:16:04 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
Subject: subscribe
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

How to subscibe ???

Adib.
-- 
WIGE DATA GmbH
Wiesenring 11, D-04159 Leipzig, Germany 	

Adib Taraben
Electronic Engineer

PHONE           +49 (0)341 - 46 21 222
FAX             +49 (0)341 - 46 21 400
E-MAIL          taraben.a@wige-data.de
INTERNET        www.wige-data.de



From als@solvo.ru Wed Dec 04 05:24:37 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18JWho-00056f-00
	for bug-commoncpp@gnu.org; Wed, 04 Dec 2002 05:24:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18JWhn-00056N-00
	for bug-commoncpp@gnu.org; Wed, 04 Dec 2002 05:24:36 -0500
Received: from alin.solvo.ru ([195.201.44.102])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18JWhi-0004lM-00
	for bug-commoncpp@gnu.org; Wed, 04 Dec 2002 05:24:32 -0500
Received: from solvo.ru (IDENT:als@localhost.localdomain [127.0.0.1])
	by alin.solvo.ru (8.11.6/8.11.6) with ESMTP id gB4ANxA01395
	for <bug-commoncpp@gnu.org>; Wed, 4 Dec 2002 13:23:59 +0300
Message-ID: <3DEDD7BE.B6EB33B6@solvo.ru>
Date: Wed, 04 Dec 2002 13:23:58 +0300
From: "Andrew L. Shwaika" <als@solvo.ru>
Organization: Solvo
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.19-p i686)
X-Accept-Language: en, ru
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
Subject: Few issues for ThreadFile.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hello,

I've found few issues for ThreadFile class.

ThreadFile::Error ThreadFile::open(const char *path)
file.cpp:413
        fd = ::open(pathname, O_RDWR);
        if(fd < 0)
        {
                flags.initial = true;
                fd = creat(pathname, (int)attrPrivate);
        }

In this case if file does not exists it will be created by 'creat'
function, but man pages for 'creat' function says:
...
       creat  is  equivalent  to  open  with   flags   equal   to
       O_CREAT|O_WRONLY|O_TRUNC.
...
So, file will be opened for writing only and any (p)read function fails
with 'Bad file descriptor' error.
I suppose to change 'creat' to:

    ::open(pathname, O_CREAT|O_RDWR|O_TRUNC, (int)attrPrivate)

It conforms to SVr4, SVID, POSIX, X/OPEN,  BSD  4.3 according man pages.

At least this change works fine on RedHat Linux 7.3 kernel 2.4.19.


ThreadFile::Error ThreadFile::fetch(caddr_t address, ccxx_size_t len,
off_t pos)
file.cpp :493
        io = ::read(fd, fcb->address, fcb->len);

'io' not declared if HAVE_PREAD_PWRITE not defined, fix:
       int io = ::read(fd, fcb->address, fcb->len);

file.cpp:497
        if((size_t) io == len)

Failed if you try to use 'same size', fix:
        if((size_t) io == fcb->len)


ThreadFile::Error ThreadFile::update(caddr_t address, ccxx_size_t len,
off_t pos)
file.cpp :554
        io = ::write(fd, fcb->address, fcb->len);

'io' not declared if HAVE_PREAD_PWRITE not defined, fix:
       int io = ::write(fd, fcb->address, fcb->len);

file.cpp:558
        if((size_t) io == len)

Failed if you try to use 'same size', fix:
        if((size_t) io == fcb->len)


ThreadFile::Error ThreadFile::append(caddr_t address, ccxx_size_t len)
file.cpp:611
        if((size_t) io == len)

Failed if you try to use 'same size', fix:
        if((size_t) io == fcb->len)


Exactly the same issues are for SharedFile.

And one question: Is it possible to add method to truncate file to the
given length?
For example, on unix systems it can be done by using 'ftruncate( int fd,
off_t len)' function.

Sincerely yours,
Andrew





From a2574@dis.ulpgc.es Thu Dec 05 06:07:36 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Jtqx-0000K0-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 06:07:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Jtqu-0000Az-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 06:07:34 -0500
Received: from serdis.dis.ulpgc.es ([193.145.145.17])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Jtqt-00082t-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 06:07:31 -0500
Received: from siglo21.dis.ulpgc.es (IDENT:root@siglo21.dis.ulpgc.es [193.145.145.16])
	by serdis.dis.ulpgc.es (8.10.2/8.9.2) with ESMTP id gB5BGi795571
	for <bug-commoncpp@gnu.org>; Thu, 5 Dec 2002 11:16:45 GMT
Received: (from nobody@localhost)
	by siglo21.dis.ulpgc.es (8.11.6/8.9.3) id gB5C4XA05174;
	Thu, 5 Dec 2002 12:04:33 GMT
Date: Thu, 5 Dec 2002 12:04:33 GMT
Message-Id: <200212051204.gB5C4XA05174@siglo21.dis.ulpgc.es>
X-Authentication-Warning: siglo21.dis.ulpgc.es: nobody set sender to a2574@dis.ulpgc.es using -f
From: a2574@dis.ulpgc.es
To: bug-commoncpp@gnu.org
Reply-To: a2574@dis.ulpgc.es
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP3 Imap webMail Program 2.0.11
Subject: Segmentation fault when using exception handling and ttystream
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hello!

Fisrt of all, Im not an advanced C++ programmer... not even close. So
maybe the answer is just in front of me but I havent see it yet.

Im using commoncpp2-1.0.7. I use the serial interface for connecting to
 a device (a Laser). The problem is that when I use it without exception
handling everything goes right, but if I switch it on
(this->setError(true)) it makes a segmentation fault when an error
occurs. I traced the code and apparently (or so the debugger says) the
error is when the method Serial::error throws the object (itself) 

throw((Serial*)this)

My code is this: (I inerhit from ttystream)
 
class SerialInterface: public ost::ttystream{
public:
SerialInterface(const char *device);
}

// and implementation is:

SerialInterface::SerialInterface(const char *device){
    this->setError(true);
     try{
         open(device);   // The method for openning the device
                         // I call it with a wrong argument \"/dev/jdss\"
     }catch (...){       // I have tried also (Serial *e) and so on ;(
         std::cout:: << getErrorNumber(); 
     }
}


Well, Is been two days now and Im starting to fed up... Two days and no
code written, thats not what I call productivity.. he.

Hoping you could help me...

PS: By the way... to install was a nightmare (as well hehe), the debian
package does not seem to work (but I guess it does not correspond to any
of you) and /usr/include/time.h conflicts with
/usr/include/cc++/cc+2/config.h its definition of nanosleep does not
throw any exception, so I changed it, but I guess this is not the reason....

By again.

Jose.


 



From dyfet@ostel.com Thu Dec 05 09:17:08 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18JwoO-00072a-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 09:17:08 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18JwoM-00072P-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 09:17:07 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18JwoL-00070T-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 09:17:05 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gB5EjgT12702;
	Thu, 5 Dec 2002 09:45:42 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Thu, 5 Dec 2002 09:45:42 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Fred Leeflang <fredl@dutchie.org>
cc: Federico Montesino Pouzols <fedemp@altern.org>,
   bayonne <bayonne-devel@lists.sourceforge.net>, <bug-commoncpp@gnu.org>
Subject: Re: [Bayonne-devel]commonc++
In-Reply-To: <1038608437.2561.49.camel@flare.dutchie.org>
Message-ID: <Pine.LNX.4.44.0212050943050.12686-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

autoconf only checks the aclocal directory for the prefix it itself is 
installed in.  Hence, it only checks /usr/share/aclocal, and never checks 
/usr/local/share/aclocal, at least on a typical GNU system where autoconf 
is installed under /usr.  I always felt autoconf should check both, 
especially if installed as /usr, since many packages are built and install 
as /usr/local.  You need to move the /usr/local/share/aclocal/ost_check.m4
to /usr/share/aclocal, and everything should be fine, or configure and 
install Common C++ with --prefix=/usr.

On 29 Nov 2002, Fred Leeflang wrote:

> I just checked out commoncpp2 from CVS. Should I have 
> CVSROOT=fleeflang@subversions.gnu.org:/cvsroot/commoncpp
> and then cvs co commoncpp2?
> 
> commoncpp2 compiles without a problem if I do it the above way,
> yet ccaudio still complaints: 
> ./configure: line 5727: syntax error near unexpected token `$REQUIRES'
> ./configure: line 5727: `OST_CCXX2_VERSION($REQUIRES)'
> 
> I have Debian unstable, gcc version 2.95.4 20011002 (Debian prerelease)
> kernel 2.4.19
> 
> I noticed a  /usr/local/share/aclocal/ost_check.m4 gets installed
> 
> I have the ccgnu2-config script
> 
> 
> On Fri, 2002-11-29 at 14:12, Federico Montesino Pouzols wrote:
> 
> > 	What is your common c++ version, compiler, system config.,
> > etc? Anyway, I think that line can be safely removed. However, it is
> > strange that only that line makes the compiler complain, since
> > equivalent statements are used in the same file as well as in other
> > files.
> > 
> > On Fri, Nov 29, 2002 at 01:57:11PM -0800, Fred Leeflang wrote:
> > > Commenting out line 572, a result of freddy77's 'merge' fixes the
> > > compile problem.
> > > 
> > > On Fri, 2002-11-29 at 13:35, Fred Leeflang wrote:
> > > 
> > > > Just checked out commoncpp from CVS, ran reconfig, configure and make:
> > > > 
> > > > fredl@orion:~/commoncpp$ make
> > > > Making all in src
> > > > make[1]: Entering directory `/home/fredl/commoncpp/src'
> > > > /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.
> > > > -I../src -I/usr/include/libxml2/libxml -I/usr/include/libxml2   
> > > > -I../src  -g -O2 -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -c
> > > > inaddr.cpp
> > > > rm -f .libs/inaddr.lo
> > > > c++ -DHAVE_CONFIG_H -I. -I. -I. -I../src -I/usr/include/libxml2/libxml
> > > > -I/usr/include/libxml2 -I../src -g -O2 -D_GNU_SOURCE -D_REENTRANT
> > > > -D_THREAD_SAFE -Wp,-MD,.deps/inaddr.pp -c inaddr.cpp  -fPIC -DPIC -o
> > > > .libs/inaddr.lo
> > > > In file included from inaddr.cpp:46:
> > > > socket.h:572: type specifier omitted for parameter
> > > > socket.h:572: parse error before `)'
> > > > make[1]: *** [inaddr.lo] Error 1
> > > > make[1]: Leaving directory `/home/fredl/commoncpp/src'
> > > > make: *** [all-recursive] Error 1
> > > > 
> > > > 
> > > > -- 
> > > > Fred Leeflang <fredl@dutchie.org>
> > > 
> > > -- 
> > > Fred Leeflang <fredl@dutchie.org>
> > > 
> 
> 




From fedemp@wanadoo.es Thu Dec 05 15:19:24 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18K2Sx-0006P6-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 15:19:23 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18K2SS-0006Fk-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 15:19:23 -0500
Received: from [62.37.236.138] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18K2SS-0004o9-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 15:18:52 -0500
Received: from risitas ([80.103.114.143])
	by smtp.wanadoo.es (8.12.6/8.12.6) with ESMTP id gB5KBJeI019364;
	Thu, 5 Dec 2002 21:11:20 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18K2Tc-0000Pd-00; Thu, 05 Dec 2002 21:20:04 +0100
Date: Thu, 5 Dec 2002 21:20:03 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: taraben.a@wige-data.de
Cc: bug-commoncpp@gnu.org
Subject: Re: subscribe
Message-ID: <20021205202003.GB607@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: taraben.a@wige-data.de, bug-commoncpp@gnu.org
References: <3DEDC7D4.6090907@wige-data.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DEDC7D4.6090907@wige-data.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Hi, You can subscribe sending a mail with subject 'subscribe'
to bug-commoncpp-request@gnu.org, or through the web interface:
http://mail.gnu.org/mailman/listinfo/bug-commoncpp.

	Umm, the savannah main page for cc++ should show a pointer to
the mailing list web interface in its public areas...

On Wed, Dec 04, 2002 at 10:16:04AM +0100, taraben.a@wige-data.de wrote:
> How to subscibe ???
> 
> Adib.
> -- 
> WIGE DATA GmbH
> Wiesenring 11, D-04159 Leipzig, Germany 	
> 
> Adib Taraben
> Electronic Engineer
> 
> PHONE           +49 (0)341 - 46 21 222
> FAX             +49 (0)341 - 46 21 400
> E-MAIL          taraben.a@wige-data.de
> INTERNET        www.wige-data.de
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fedemp@wanadoo.es Thu Dec 05 16:22:36 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18K3S8-0001Rh-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:22:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18K3RX-0000Fz-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:22:31 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18K3RW-0000Fd-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:21:58 -0500
Received: from risitas ([80.103.114.143])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gB5LID207738;
	Thu, 5 Dec 2002 22:18:13 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18K3Ty-0000qP-00; Thu, 05 Dec 2002 22:24:30 +0100
Date: Thu, 5 Dec 2002 22:24:29 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Andrew L. Shwaika" <als@solvo.ru>
Cc: bug-commoncpp@gnu.org
Subject: Re: Few issues for ThreadFile.
Message-ID: <20021205212429.GC607@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: "Andrew L. Shwaika" <als@solvo.ru>, bug-commoncpp@gnu.org
References: <3DEDD7BE.B6EB33B6@solvo.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DEDD7BE.B6EB33B6@solvo.ru>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Hi, ...

On Wed, Dec 04, 2002 at 01:23:58PM +0300, Andrew L. Shwaika wrote:
> Hello,
> 
> I've found few issues for ThreadFile class.
> 
> ThreadFile::Error ThreadFile::open(const char *path)
> file.cpp:413
>         fd = ::open(pathname, O_RDWR);
>         if(fd < 0)
>         {
>                 flags.initial = true;
>                 fd = creat(pathname, (int)attrPrivate);
>         }
> 
> In this case if file does not exists it will be created by 'creat'
> function, but man pages for 'creat' function says:
> ...
>        creat  is  equivalent  to  open  with   flags   equal   to
>        O_CREAT|O_WRONLY|O_TRUNC.
> ...
> So, file will be opened for writing only and any (p)read function fails
> with 'Bad file descriptor' error.
> I suppose to change 'creat' to:
> 
>     ::open(pathname, O_CREAT|O_RDWR|O_TRUNC, (int)attrPrivate)
> 
> It conforms to SVr4, SVID, POSIX, X/OPEN,  BSD  4.3 according man pages.
> 
> At least this change works fine on RedHat Linux 7.3 kernel 2.4.19.
> 

	Yes, your suggestion looks better. Fixed in CVS for
ThreadFile, SharedFile and MappedFile.

> 
> ThreadFile::Error ThreadFile::fetch(caddr_t address, ccxx_size_t len,
> off_t pos)
> file.cpp :493
>         io = ::read(fd, fcb->address, fcb->len);
> 
> 'io' not declared if HAVE_PREAD_PWRITE not defined, fix:
>        int io = ::read(fd, fcb->address, fcb->len);
> 
> file.cpp:497
>         if((size_t) io == len)
> 
> Failed if you try to use 'same size', fix:
>         if((size_t) io == fcb->len)
> 
> 
> ThreadFile::Error ThreadFile::update(caddr_t address, ccxx_size_t len,
> off_t pos)
> file.cpp :554
>         io = ::write(fd, fcb->address, fcb->len);
> 
> 'io' not declared if HAVE_PREAD_PWRITE not defined, fix:
>        int io = ::write(fd, fcb->address, fcb->len);
> 
> file.cpp:558
>         if((size_t) io == len)
> 
> Failed if you try to use 'same size', fix:
>         if((size_t) io == fcb->len)
> 
> 
> ThreadFile::Error ThreadFile::append(caddr_t address, ccxx_size_t len)
> file.cpp:611
>         if((size_t) io == len)
> 
> Failed if you try to use 'same size', fix:
>         if((size_t) io == fcb->len)
> 
> 
> Exactly the same issues are for SharedFile.

	All these are now fixed.

> 
> And one question: Is it possible to add method to truncate file to the
> given length?
> For example, on unix systems it can be done by using 'ftruncate( int fd,
> off_t len)' function.
> 

	It would be a useful method, and I do not see any reason to
not include it. Patches are welcome :).

	Bye!

> Sincerely yours,
> Andrew
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Thu Dec 05 16:27:00 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18K3WO-00065s-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:27:00 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18K3Vs-0005bp-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:26:59 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18K3Vr-0005XF-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:26:27 -0500
Received: from home.sys (IDENT:xasSOvGpAnvzgq9eSDYtPp/e73Z1Kpnh@home.sys [172.16.1.254])
	by home.sys (8.11.6/8.11.6) with ESMTP id gB5Lt3312632;
	Thu, 5 Dec 2002 16:55:04 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: a2574@dis.ulpgc.es, bug-commoncpp@gnu.org
Subject: Re: Segmentation fault when using exception handling and ttystream
Date: Thu, 5 Dec 2002 16:55:03 -0500
User-Agent: KMail/1.4.3
References: <200212051204.gB5C4XA05174@siglo21.dis.ulpgc.es>
In-Reply-To: <200212051204.gB5C4XA05174@siglo21.dis.ulpgc.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212051655.03424.dyfet@ostel.com>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Generally a catch handler should catch this, but there have been changes =
in=20
the abi which may make self thrown objects have strange behavior.  I woul=
d=20
suggest trying setException(Thread::throwException);

On Thursday 05 December 2002 07:04, a2574@dis.ulpgc.es wrote:
> Hello!
>
> Fisrt of all, Im not an advanced C++ programmer... not even close. So
> maybe the answer is just in front of me but I havent see it yet.
>
> Im using commoncpp2-1.0.7. I use the serial interface for connecting to
>  a device (a Laser). The problem is that when I use it without exceptio=
n
> handling everything goes right, but if I switch it on
> (this->setError(true)) it makes a segmentation fault when an error
> occurs. I traced the code and apparently (or so the debugger says) the
> error is when the method Serial::error throws the object (itself)
>
> throw((Serial*)this)
>
> My code is this: (I inerhit from ttystream)
>
> class SerialInterface: public ost::ttystream{
> public:
> SerialInterface(const char *device);
> }
>
> // and implementation is:
>
> SerialInterface::SerialInterface(const char *device){
>     this->setError(true);
>      try{
>          open(device);   // The method for openning the device
>                          // I call it with a wrong argument \"/dev/jdss=
\"
>      }catch (...){       // I have tried also (Serial *e) and so on ;(
>          std::cout:: << getErrorNumber();
>      }
> }
>
>
> Well, Is been two days now and Im starting to fed up... Two days and no
> code written, thats not what I call productivity.. he.
>
> Hoping you could help me...
>
> PS: By the way... to install was a nightmare (as well hehe), the debian
> package does not seem to work (but I guess it does not correspond to an=
y
> of you) and /usr/include/time.h conflicts with
> /usr/include/cc++/cc+2/config.h its definition of nanosleep does not
> throw any exception, so I changed it, but I guess this is not the
> reason....
>
> By again.
>
> Jose.
>
>
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From fedemp@wanadoo.es Thu Dec 05 16:34:08 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18K3dH-0004QA-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:34:07 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18K3ck-0003WT-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:34:05 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18K3cj-0003UV-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:33:33 -0500
Received: from risitas ([80.103.114.143])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gB5K9J221355;
	Thu, 5 Dec 2002 21:09:20 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18K2PI-0000PQ-00; Thu, 05 Dec 2002 21:15:36 +0100
Date: Thu, 5 Dec 2002 21:15:36 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Lokesh Johri <ljohri@sbcglobal.net>
Cc: bug-commoncpp@gnu.org
Subject: Re: What is the licensing term for Common C++
Message-ID: <20021205201536.GA607@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Lokesh Johri <ljohri@sbcglobal.net>,
	bug-commoncpp@gnu.org
References: <KMEGIIBLMCKDDHMEHHABKEKBDAAA.ljohri@sbcglobal.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <KMEGIIBLMCKDDHMEHHABKEKBDAAA.ljohri@sbcglobal.net>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Well, it is licensed under the GPL + a linking exception. See
the files COPYING and COPYING.addendum, or the 'Distribution' chapter
in the manual. I would suggest you not to look at sourceforge, but at
Savannah (http://savannah.gnu.org/projects/commoncpp/), which is
currently preferred for the development of cc++.

On Thu, Nov 28, 2002 at 11:44:43AM -0800, Lokesh Johri wrote:
> Hello,
> Could you please tell me what is the licensing term for Common C++- is it
> GPL or LGPL.
> Source forge labels it as LGPL , Common C++ home page labels it as GPL. The
> copyright notice with the package is GPL while the readme mentions it as
> LGPL.
> 
> Could you please clarify.
> Thanks,
> Lokesh
> ________________________________________________________
> 
> Lokesh Johri
> 
> Software Engineering, Probe Systems, NP Test Inc.
> 
> 150, Baytech Drive                 Work: (408) 586 6482
> 
> San Jose CA 95132                Mobile: (408) 887-7338
> 
>                                                   Fax: (408) 586-4662
> 
>                                                   ljohri@nptest.com
> 
> 
> 
> 



From dyfet@ostel.com Thu Dec 05 16:34:53 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18K3e1-0005Xl-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:34:53 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18K3bX-0002J6-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:32:51 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18K3bW-0002Hv-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:32:18 -0500
Received: from home.sys (IDENT:XL1hnbsh18G6o/IqAqGRucYRN9IzJl25@home.sys [172.16.1.254])
	by home.sys (8.11.6/8.11.6) with ESMTP id gB5M15312689;
	Thu, 5 Dec 2002 17:01:05 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: "Andrew L. Shwaika" <als@solvo.ru>, bug-commoncpp@gnu.org
Subject: Re: Few issues for ThreadFile.
Date: Thu, 5 Dec 2002 17:01:03 -0500
User-Agent: KMail/1.4.3
References: <3DEDD7BE.B6EB33B6@solvo.ru>
In-Reply-To: <3DEDD7BE.B6EB33B6@solvo.ru>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212051701.03842.dyfet@ostel.com>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

I am not sure how widely portable ftruncate is, and there is no easy way =
to=20
simulate it's behavior on systems that lack it.  However, these other=20
suggestions and changes do look very worthwhile.  I think you are right t=
hat=20
it is better to use open rather than creat.

On Wednesday 04 December 2002 05:23, Andrew L. Shwaika wrote:
> Hello,
>
> I've found few issues for ThreadFile class.
>
> ThreadFile::Error ThreadFile::open(const char *path)
> file.cpp:413
>         fd =3D ::open(pathname, O_RDWR);
>         if(fd < 0)
>         {
>                 flags.initial =3D true;
>                 fd =3D creat(pathname, (int)attrPrivate);
>         }
>
> In this case if file does not exists it will be created by 'creat'
> function, but man pages for 'creat' function says:
> ...
>        creat  is  equivalent  to  open  with   flags   equal   to
>        O_CREAT|O_WRONLY|O_TRUNC.
> ...
> So, file will be opened for writing only and any (p)read function fails
> with 'Bad file descriptor' error.
>
> I suppose to change 'creat' to:
>     ::open(pathname, O_CREAT|O_RDWR|O_TRUNC, (int)attrPrivate)
>
> It conforms to SVr4, SVID, POSIX, X/OPEN,  BSD  4.3 according man pages=
=2E
>
> At least this change works fine on RedHat Linux 7.3 kernel 2.4.19.
>
>
> ThreadFile::Error ThreadFile::fetch(caddr_t address, ccxx_size_t len,
> off_t pos)
> file.cpp :493
>         io =3D ::read(fd, fcb->address, fcb->len);
>
> 'io' not declared if HAVE_PREAD_PWRITE not defined, fix:
>        int io =3D ::read(fd, fcb->address, fcb->len);
>
> file.cpp:497
>         if((size_t) io =3D=3D len)
>
> Failed if you try to use 'same size', fix:
>         if((size_t) io =3D=3D fcb->len)
>
>
> ThreadFile::Error ThreadFile::update(caddr_t address, ccxx_size_t len,
> off_t pos)
> file.cpp :554
>         io =3D ::write(fd, fcb->address, fcb->len);
>
> 'io' not declared if HAVE_PREAD_PWRITE not defined, fix:
>        int io =3D ::write(fd, fcb->address, fcb->len);
>
> file.cpp:558
>         if((size_t) io =3D=3D len)
>
> Failed if you try to use 'same size', fix:
>         if((size_t) io =3D=3D fcb->len)
>
>
> ThreadFile::Error ThreadFile::append(caddr_t address, ccxx_size_t len)
> file.cpp:611
>         if((size_t) io =3D=3D len)
>
> Failed if you try to use 'same size', fix:
>         if((size_t) io =3D=3D fcb->len)
>
>
> Exactly the same issues are for SharedFile.
>
> And one question: Is it possible to add method to truncate file to the
> given length?
> For example, on unix systems it can be done by using 'ftruncate( int fd=
,
> off_t len)' function.
>
> Sincerely yours,
> Andrew
>
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From fedemp@wanadoo.es Thu Dec 05 16:57:15 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18K3zf-0003Mk-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:57:15 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18K3z9-0003I4-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:57:14 -0500
Received: from [62.37.236.138] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18K3z9-0003Ht-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 16:56:43 -0500
Received: from risitas ([80.103.114.143])
	by smtp.wanadoo.es (8.12.6/8.12.6) with ESMTP id gB5LoSeI002039;
	Thu, 5 Dec 2002 22:50:29 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18K41a-0000rn-00; Thu, 05 Dec 2002 22:59:14 +0100
Date: Thu, 5 Dec 2002 22:59:14 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: a2574@dis.ulpgc.es
Cc: bug-commoncpp@gnu.org
Subject: Re: Segmentation fault when using exception handling and ttystream
Message-ID: <20021205215914.GD607@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: a2574@dis.ulpgc.es, bug-commoncpp@gnu.org
References: <200212051204.gB5C4XA05174@siglo21.dis.ulpgc.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200212051204.gB5C4XA05174@siglo21.dis.ulpgc.es>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

On Thu, Dec 05, 2002 at 12:04:33PM +0000, a2574@dis.ulpgc.es wrote:
> PS: By the way... to install was a nightmare (as well hehe), the debian
> package does not seem to work (but I guess it does not correspond to any
> of you) 

	The Debian packages usually work well. What problems did you
found?

> and /usr/include/time.h conflicts with
> /usr/include/cc++/cc+2/config.h its definition of nanosleep does not
> throw any exception, so I changed it, but I guess this is not the reason....

	Do you mean something like...

../include/cc++/config.h:524: declaration of `int nanosleep (const
timespec *, timespec *)' throws different exceptions
/usr/include/time.h:284: than previous declaration `int nanosleep
(const timespec *, timespec *) throw ()'

	if so, this seems to be a bug and should be fixed soon. In the
meantime you can safely remove the declaration in config.h.

	Bye!
> 
> By again.
> 
> Jose.
> 
> 
>  
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fedemp@wanadoo.es Thu Dec 05 17:06:45 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18K48r-0000Cf-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 17:06:45 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18K48L-00005T-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 17:06:44 -0500
Received: from [62.37.236.137] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18K48L-00005J-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 17:06:13 -0500
Received: from risitas ([80.103.114.143])
	by smtp.wanadoo.es (8.11.3/8.11.3) with ESMTP id gB5LF6g07405;
	Thu, 5 Dec 2002 22:15:07 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18K4Ac-0000xj-00; Thu, 05 Dec 2002 23:08:34 +0100
Date: Thu, 5 Dec 2002 23:08:33 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Cc: bug-commoncpp@gnu.org
Subject: Re: Fwd: [Bayonne-devel]timespec *, timespec *)' throws different exceptions (compiling commoncpp 1.0.7)
Message-ID: <20021205220833.GE607@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org
References: <200212051651.01757.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200212051651.01757.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Oh, I had not had this problem yet, but I have just read a
mail posted to bug-commoncpp whose author seems to complain about the
same issue. The problem comes from the following lines in config.h:

#ifdef HAVE_PTHREAD_NANOSLEEP
#ifndef HAVE_PTHREAD_DELAY
#define HAVE_PTHREAD_DELAY
extern "C" int nanosleep(const struct timespec *rqtp, struct timespec *rmtp);
#define pthread_delay(x) nanosleep(x, NULL)

	I recall we recently added the declaration of nanosleep
because it is missing (or requires the definition of some weird posix
version related symbols) in FreeBSD. However, this declaration is
conflicting with the one in time.h, which difers because of the 'throw
()'. I guess we will have to make an AC_TRY_COMPILE with nanosleep to
see if it is already declared, and declare nanosleep in config.h only
when strictly necessary.

On Thu, Dec 05, 2002 at 04:51:01PM -0500, David Sugar wrote:
> Here's a curious problem I had not seen before...nanosleep is defined in at 
> least some glibc releases under time.h...
> 
> ----------  Forwarded Message  ----------
> 
> Subject: [Bayonne-devel]timespec *, timespec *)' throws different exceptions 
> (compiling commoncpp 1.0.7)
> Date: 05 Dec 2002 15:57:11 -0500
> From: Erik Enge <eenge@prium.net>
> To: bayonne-devel@lists.sourceforge.net
> 
> Hi.
> 
> I'm getting this when trying to compile CommonCPP version 1.0.7:
> 
> make[1]: Entering directory `/share/pak/commoncpp2/commoncpp2-1.0.7/src'
> /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I../include   
>   -I../src -DCCXX_EXPORT_LIBRARY  -I/usr/local/include -D_GNU_SOURCE 
>  -I/usr/include/libxml -I/usr/include -I../include -c thread.cpp rm -f
>  .libs/thread.lo
> c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
>  -I/usr/local/include -D_GNU_SOURCE -I/usr/include/libxml -I/usr/include
>  -I../include -c thread.cpp  -fPIC -DPIC -o .libs/thread.lo In file included
>  from thread.cpp:41:
> ../include/cc++/config.h:524: declaration of `int nanosleep (const
> timespec *, timespec *)' throws different exceptions
> /usr/include/time.h:284: than previous declaration `int nanosleep
> (const timespec *, timespec *) throw ()'
> make[1]: *** [thread.lo] Error 1
> make[1]: Leaving directory `/share/pak/commoncpp2/commoncpp2-1.0.7/src'
> make: *** [install-recursive] Error 1
> 
> Is there anything I can do to make it go away?  I'm getting this error
> when I try to compile 1.0.6 also - which previously compiled just fine.
> I don't think I changed anything between the compiles.  Confusing.
> 
> (Couple of unrelated comments; bayonne.sf.net and
> gnu.org/software/bayonne differ greatly in content but not in design and
> the FAQ page (http://bayonne.myip.org/cgi-bin/bayonne.faq) seems to be
> down).
> 
> Thanks,
> 
> Erik.
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Bayonne-devel mailing list
> Bayonne-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bayonne-devel
> 
> -------------------------------------------------------
> 



From dyfet@ostel.com Thu Dec 05 18:28:36 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18K5Q3-0005mI-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 18:28:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18K5PX-0005Vy-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 18:28:34 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18K5PW-0005VG-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 18:28:02 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gB5NupN13936;
	Thu, 5 Dec 2002 18:56:51 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Thu, 5 Dec 2002 18:56:51 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org, <bayonne-devel@lists.sourceforge.net>
Subject: Re: Fwd: [Bayonne-devel]timespec *, timespec *)' throws different
 exceptions (compiling commoncpp 1.0.7)
In-Reply-To: <20021205220833.GE607@risitas>
Message-ID: <Pine.LNX.4.44.0212051853500.13903-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

I think we will have to add a AC_TRY_COMPILE for it...I don't have any
issue with this on any of the systems I normally test with, but I am
gathering it is an issue at least on some older rh (pre 7.3, and,
similarly pre debian r3) systems.  If we added it in initially for
FreeBSD, maybe we should for the moment just have a "#ifdef __FreeBSD__"  
around it...

On Thu, 5 Dec 2002, Federico Montesino Pouzols wrote:

> 
> 	Oh, I had not had this problem yet, but I have just read a
> mail posted to bug-commoncpp whose author seems to complain about the
> same issue. The problem comes from the following lines in config.h:
> 
> #ifdef HAVE_PTHREAD_NANOSLEEP
> #ifndef HAVE_PTHREAD_DELAY
> #define HAVE_PTHREAD_DELAY
> extern "C" int nanosleep(const struct timespec *rqtp, struct timespec *rmtp);
> #define pthread_delay(x) nanosleep(x, NULL)
> 
> 	I recall we recently added the declaration of nanosleep
> because it is missing (or requires the definition of some weird posix
> version related symbols) in FreeBSD. However, this declaration is
> conflicting with the one in time.h, which difers because of the 'throw
> ()'. I guess we will have to make an AC_TRY_COMPILE with nanosleep to
> see if it is already declared, and declare nanosleep in config.h only
> when strictly necessary.
> 
> On Thu, Dec 05, 2002 at 04:51:01PM -0500, David Sugar wrote:
> > Here's a curious problem I had not seen before...nanosleep is defined in at 
> > least some glibc releases under time.h...
> > 
> > ----------  Forwarded Message  ----------
> > 
> > Subject: [Bayonne-devel]timespec *, timespec *)' throws different exceptions 
> > (compiling commoncpp 1.0.7)
> > Date: 05 Dec 2002 15:57:11 -0500
> > From: Erik Enge <eenge@prium.net>
> > To: bayonne-devel@lists.sourceforge.net
> > 
> > Hi.
> > 
> > I'm getting this when trying to compile CommonCPP version 1.0.7:
> > 
> > make[1]: Entering directory `/share/pak/commoncpp2/commoncpp2-1.0.7/src'
> > /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I../include   
> >   -I../src -DCCXX_EXPORT_LIBRARY  -I/usr/local/include -D_GNU_SOURCE 
> >  -I/usr/include/libxml -I/usr/include -I../include -c thread.cpp rm -f
> >  .libs/thread.lo
> > c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
> >  -I/usr/local/include -D_GNU_SOURCE -I/usr/include/libxml -I/usr/include
> >  -I../include -c thread.cpp  -fPIC -DPIC -o .libs/thread.lo In file included
> >  from thread.cpp:41:
> > ../include/cc++/config.h:524: declaration of `int nanosleep (const
> > timespec *, timespec *)' throws different exceptions
> > /usr/include/time.h:284: than previous declaration `int nanosleep
> > (const timespec *, timespec *) throw ()'
> > make[1]: *** [thread.lo] Error 1
> > make[1]: Leaving directory `/share/pak/commoncpp2/commoncpp2-1.0.7/src'
> > make: *** [install-recursive] Error 1
> > 
> > Is there anything I can do to make it go away?  I'm getting this error
> > when I try to compile 1.0.6 also - which previously compiled just fine.
> > I don't think I changed anything between the compiles.  Confusing.
> > 
> > (Couple of unrelated comments; bayonne.sf.net and
> > gnu.org/software/bayonne differ greatly in content but not in design and
> > the FAQ page (http://bayonne.myip.org/cgi-bin/bayonne.faq) seems to be
> > down).
> > 
> > Thanks,
> > 
> > Erik.
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Bayonne-devel mailing list
> > Bayonne-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bayonne-devel
> > 
> > -------------------------------------------------------
> > 
> 




From scove@occl.com Thu Dec 05 21:24:16 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18K8A3-0006vu-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 21:24:15 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18K89S-0005Ix-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 21:24:10 -0500
Received: from b0i255jzy48f9.bc.hsia.telus.net ([64.180.47.141] helo=host.occl.com)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18K89S-0005BC-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 21:23:38 -0500
Received: (qmail 19514 invoked from network); 6 Dec 2002 02:12:24 -0000
Received: from unknown (HELO jedi.occl.net) (192.168.1.12)
  by 0 with SMTP; 6 Dec 2002 02:12:24 -0000
Subject: Re: Few issues for ThreadFile.
From: Skye Cove <scove@occl.com>
To: bug-commoncpp@gnu.org
In-Reply-To: <200212051701.03842.dyfet@ostel.com>
References: <3DEDD7BE.B6EB33B6@solvo.ru>
	 <200212051701.03842.dyfet@ostel.com>
Content-Type: text/plain; charset=UTF-8
Organization: 
Message-Id: <1039141574.1390.274.camel@jedi.occl.net>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.0 
Date: 05 Dec 2002 18:26:14 -0800
Content-Transfer-Encoding: 8bit
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

On Thu, 2002-12-05 at 14:01, David Sugar wrote:
> I am not sure how widely portable ftruncate is,

For what it's worth:

Aaccording to `man ftruncate` (on a Linux 2.4.18 system):
"4.4BSD, SVr4 (these function calls first appeared in BSD  4.2). POSIX
1003.1‐1996  has ftruncate. POSIX 1003.1‐2001 also has truncate, as an
XSI extension."

I verified that it is also supported on FreeBSD 4.5, Solaris 8 and HP-UX
11 (though I didn't compile any tests). 

Does the win32 API offer anything similar?

-sc





From lst1017@bellsouth.net Thu Dec 05 21:50:34 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18K8ZW-0008Iq-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 21:50:34 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18K8Z0-0008Cd-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 21:50:33 -0500
Received: from mail104.mail.bellsouth.net ([205.152.58.44] helo=imf04bis.bellsouth.net)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18K8Yz-0008CS-00
	for bug-commoncpp@gnu.org; Thu, 05 Dec 2002 21:50:01 -0500
Received: from phoenix ([67.33.159.35]) by imf04bis.bellsouth.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP
          id <20021206025149.PDVC6569.imf04bis.bellsouth.net@phoenix>;
          Thu, 5 Dec 2002 21:51:49 -0500
From: "Leonard Thornton" <lst1017@bellsouth.net>
To: "'Skye Cove'" <scove@occl.com>,
	<bug-commoncpp@gnu.org>
Subject: RE: Few issues for ThreadFile.
Date: Thu, 5 Dec 2002 21:49:36 -0500
Organization: Intelis, Inc
Message-ID: <!~!AAAAACtOcTp7wTJEkIAsu8pFESKESyEA@bellsouth.net>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0005_01C29CA8.379A67E0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <1039141574.1390.274.camel@jedi.occl.net>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MS-TNEF-Correlator: 000000002B4E713A7BC1324490802CBBCA451122C44B2100
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01C29CA8.379A67E0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit

Sorry, but no ftruncate in win32.....closest would be "open(....O_TRUNC)..."


Leonard Thornton
Intelis, Inc
leonardt@intelis-inc.com
 
+1 770.825.0032 x 203


-----Original Message-----
From: bug-commoncpp-admin@gnu.org [mailto:bug-commoncpp-admin@gnu.org] On
Behalf Of Skye Cove
Sent: Thursday, December 05, 2002 9:26 PM
To: bug-commoncpp@gnu.org
Subject: Re: Few issues for ThreadFile.


On Thu, 2002-12-05 at 14:01, David Sugar wrote:
> I am not sure how widely portable ftruncate is,

For what it's worth:

Aaccording to `man ftruncate` (on a Linux 2.4.18 system): "4.4BSD, SVr4
(these function calls first appeared in BSD  4.2). POSIX 1003.1$B!>(J1996  has
ftruncate. POSIX 1003.1$B!>(J2001 also has truncate, as an XSI extension."

I verified that it is also supported on FreeBSD 4.5, Solaris 8 and HP-UX 11
(though I didn't compile any tests). 

Does the win32 API offer anything similar?

-sc




_______________________________________________
Bug-commoncpp mailing list
Bug-commoncpp@gnu.org http://mail.gnu.org/mailman/listinfo/bug-commoncpp

------=_NextPart_000_0005_01C29CA8.379A67E0
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="winmail.dat"

eJ8+IikCAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGAAcAAQAAAAAAAAEGgAMADgAAANIHDAAF
ABUAMQAAAAQANAEBA5AGACAJAAAtAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAAD
AC4AAAAAAAIBMQABAAAAGAAAAAAAAAArTnE6e8EyRJCALLvKRREihEshAAMANgAAAAAAHgBwAAEA
AAAbAAAARmV3IGlzc3VlcyBmb3IgVGhyZWFkRmlsZS4AAAIBcQABAAAAFgAAAAHCnNIU6JYjNDrq
i0jdoNm5OoanDY4AAAIBHQwBAAAAGwAAAFNNVFA6TFNUMTAxN0BCRUxMU09VVEguTkVUAAALAAEO
AAAAAEAABg4A9lYH0pzCAQIBCg4BAAAAGAAAAAAAAAArTnE6e8EyRJCALLvKRREiwoAAAAMAFA4A
AAAACwAfDgEAAAAeACgOAQAAAC0AAAAwMDAwMDAwNAFsc3QxMDE3QGJlbGxzb3V0aC5uZXQBYmVs
bHNvdXRoLm5ldAAAAAAeACkOAQAAAC0AAAAwMDAwMDAwNAFsc3QxMDE3QGJlbGxzb3V0aC5uZXQB
YmVsbHNvdXRoLm5ldAAAAAACAQkQAQAAAAoEAAAGBAAAOAYAAExaRnV0A7ioAwAKAHJjcGcxMjXi
MgNDdGV4BUEBAwH3TwqAAqQD4wIAY2gKwHPwZXQwIAcTAoAP8wBQfwRWCFUHshHFDlEDARDHMncG
AAbDEcUzBEYQyRLfZhY0EF4OIDgF0lBHb3x0aA3gAoAR0wjvCfc72xsfDjA1EcIMYGMAUAsJeQFk
MzYRUAumBgAFsHIgeSwgYnUFQG5vgiABgHJ1bmNhDrAKIAuAIAPwbjMyLq0h8mMasBEgcwVAdwhg
jGxkIFAhUCJvcAnwAigh8k9fVFJVTnRDKSHxIgqiCoQk9kzGZQIgCxEgVGgFsAIwywIgJLRJAjBl
bAQAIECXJzAA4CTDbCXkdEALgPUnUy0LgGMiMANwJLQK4wEKgCsxIDc3MC4iOA4wLjAwIdAgeK4g
AdAV0CTPLS0STwUQHmcLgAdABdAHkHNhZ1ZlLRMr9EYDYTogUWcOLSmhBGAhEHBwLWEEZG0LgEBn
bnUucQWwZyBbAMADECagOiMvfzCIXSBPA6BCZRkQ8GxmM3A0AFNrefMhUAhQdmUr9AZgAjAvUKMm
UAhwc2RhIDFEBZBmZQbQEyEwNSBAAdAwoRTgOToyNhmgTSv0HlQxkC9sMKY05XViatMFkDVxUmUv
UEYH0QQBfwpQBCACEAXAJlAbIDBQRukDEGUuK/8KM4E1oTb0Ki0OIC020CAhMCAxEDQ6MDE2IWF2
aWsjADogZwrBdwNgDrA67TyUPiewPtBtIJEFQDtQPRsgICZgB+AD8AEAbHn8IHAawQGgKFAgyieQ
PJoaRgWxdxDwBUBpdCc3BCAiwAAgaECVPJVodPxtbAAhGAUMAUblEVEA0J0FoWQLgDEQJqAgYAOC
MSDXYCAoAiA+0CBMhQuAdSuhLjQuMRlgrHN5IpA2cCkvUCJLQBA0QlNEIEBTVnI+NEpQGeAHkEMh
IQF0adNKcSEgbGw7gWkREAVAPmEwIDwQGyEhYkxhICANS0AyJGAZoE9TSVhHPwArUUtQXCc4UOE1
sGQxOTk3kEHwYTuBvyDmUB9RIzcRKrAHQHMgsF9R0iDmIEBR4QORWFLgIH8OwQnwAJACICSRRuUC
sX3/R+g8mkEgNMAGgQiQIwAZ4P9FMzshVEQ7UDAgGsFPIUpx/y8QCeBPgktANuEf8AtgBRAPBCAZ
YABwIwBIUC1Vz1BxKrBNAQhgZ2hBEUjg2GRuJwVAKaFwPFFVoTdCkA6wIpBzUAE8mkRvrweRTREh
lBFgUEEgbwEgfxMhX0EZ4UkBAJAwcFxhP+8sWwTwPJ8lC19mP2dPaBp1ZRRCMcogMUJI8idxdA9p
LzkoQfACQHA6Ly/dMUIuMLVtQwOBL2riC4AtAhAvMbtlFH1wcAAAHgBCEAEAAAAqAAAAPDEwMzkx
NDE1NzQuMTM5MC4yNzQuY2FtZWxAamVkaS5vY2NsLm5ldD4AAAADAJIQAAAAAAIBFDoBAAAAEAAA
AKZiK3jBDkhNmI34o1woV/oDAN4/LMQAAAMACVkBAAAAAwBAZQAAAAALABOACCAGAAAAAADAAAAA
AAAARgAAAAADhQAAAAAAAAMAFYAIIAYAAAAAAMAAAAAAAABGAAAAABCFAAAAAAAAAwAbgAggBgAA
AAAAwAAAAAAAAEYAAAAAUoUAAFmUAQADACKACCAGAAAAAADAAAAAAAAARgAAAAABhQAAAAAAAB4A
PoAIIAYAAAAAAMAAAAAAAABGAAAAAFSFAAABAAAABQAAADEwLjAAAAAACwA/gAggBgAAAAAAwAAA
AAAAAEYAAAAABoUAAAAAAAALAEOACCAGAAAAAADAAAAAAAAARgAAAAAOhQAAAAAAAAMARoAIIAYA
AAAAAMAAAAAAAABGAAAAABiFAAAAAAAACwBbgAggBgAAAAAAwAAAAAAAAEYAAAAAgoUAAAEAAAAC
AfgPAQAAABAAAAArTnE6e8EyRJCALLvKRREiAgH6DwEAAAAQAAAAK05xOnvBMkSQgCy7ykURIgIB
+w8BAAAAlQAAAAAAAAA4obsQBeUQGqG7CAArKlbCAABtc3BzdC5kbGwAAAAAAE5JVEH5v7gBAKoA
N9luAAAAQzpcRG9jdW1lbnRzIGFuZCBTZXR0aW5nc1xsc3QxMDE3XExvY2FsIFNldHRpbmdzXEFw
cGxpY2F0aW9uIERhdGFcTWljcm9zb2Z0XE91dGxvb2tcT3V0bG9vay5wc3QAAAAAAwD+DwUAAAAD
AA00/TcCAAIBFDQBAAAAEAAAAE5JVEH5v7gBAKoAN9luAAACAX8AAQAAADEAAAAwMDAwMDAwMDJC
NEU3MTNBN0JDMTMyNDQ5MDgwMkNCQkNBNDUxMTIyQzQ0QjIxMDAAAAAAAwAGEDjvMl4DAAcQKgMA
AAMAEBAAAAAAAwAREAAAAAAeAAgQAQAAAGUAAABTT1JSWSxCVVROT0ZUUlVOQ0FURUlOV0lOMzJD
TE9TRVNUV09VTERCRSJPUEVOKE9UUlVOQykiTEVPTkFSRFRIT1JOVE9OSU5URUxJUyxJTkNMRU9O
QVJEVEBJTlRFTElTLUlOAAAAACo2

------=_NextPart_000_0005_01C29CA8.379A67E0--





From dyfet@ostel.com Fri Dec 06 12:12:54 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18KM1c-0002py-00
	for bug-commoncpp@gnu.org; Fri, 06 Dec 2002 12:12:28 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18KM1Q-0002b7-00
	for bug-commoncpp@gnu.org; Fri, 06 Dec 2002 12:12:25 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18KM1P-0002XE-00
	for bug-commoncpp@gnu.org; Fri, 06 Dec 2002 12:12:15 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by gnudist.gnu.org with esmtp (Exim 4.10.13)
	id 18KLHa-0001z4-00
	for bug-commoncpp@gnu.org; Fri, 06 Dec 2002 11:24:54 -0500
Received: from home.sys (IDENT:IAE1qRqtmpFQaU6kW0wZ+bmo1bMTUebV@home.sys [172.16.1.254])
	by home.sys (8.11.6/8.11.6) with ESMTP id gB6Gr9323220;
	Fri, 6 Dec 2002 11:53:09 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>,
   Lokesh Johri <ljohri@sbcglobal.net>
Subject: Re: What is the licensing term for Common C++
Date: Fri, 6 Dec 2002 11:53:08 -0500
User-Agent: KMail/1.4.3
Cc: bug-commoncpp@gnu.org, cplusplus-devel@lists.sourceforge.net
References: <KMEGIIBLMCKDDHMEHHABKEKBDAAA.ljohri@sbcglobal.net> <20021205201536.GA607@risitas>
In-Reply-To: <20021205201536.GA607@risitas>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212061153.08945.dyfet@ostel.com>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

It is probably worth commenting on this a bit further.  The one problem I=
=20
recall immediately with the LGPL as it applies to C++ class frameworks is=
 the=20
way it defines and refers to "linking" vs "derived works".  In concept, a=
 C++=20
header with inline members or template is not "linked" in the same sense =
as=20
one might presume the meaning in traditional C library, and what does one=
=20
make of a class who's base class is defined in a header in a LGPL protect=
ed=20
library?  Is creating a derived C++ class purely a linking operation or=20
creating a derived/composite work?

At the time it seemed simpler to take the language of the GPL and provide=
 an=20
appropriate priviledges to allow Common C++ to be used in ways that achie=
ve=20
the same goals of the LGPL, but without using the sane choice of language=
 for=20
this that is found in the LGPL.  We actually looked at the Guile license,=
=20
which also faced many of these questions, and choose to use their methodo=
ligy=20
for creating a special priviledge in this regard.  Of course, this was a=20
number of years ago, and the language of the LGPL (and GPL) has evolved o=
ver=20
time to better address the needs of object oriented frameworks.  If the=20
language of the current LGPL were close enough to resolving these goals, =
I=20
think we would likely switch to it, as that would resolve some confusion =
over=20
the exact license status.  I have found it simpler to explain it as a=20
LGPL-like license since we were trying for much the same effect within th=
e=20
context of a C++ framework, and most people basically understand what the=
=20
LGPL is.

On Thursday 05 December 2002 15:15, Federico Montesino Pouzols wrote:
> Well, it is licensed under the GPL + a linking exception. See
> the files COPYING and COPYING.addendum, or the 'Distribution' chapter
> in the manual. I would suggest you not to look at sourceforge, but at
> Savannah (http://savannah.gnu.org/projects/commoncpp/), which is
> currently preferred for the development of cc++.
>
> On Thu, Nov 28, 2002 at 11:44:43AM -0800, Lokesh Johri wrote:
> > Hello,
> > Could you please tell me what is the licensing term for Common C++- i=
s it
> > GPL or LGPL.
> > Source forge labels it as LGPL , Common C++ home page labels it as GP=
L.
> > The copyright notice with the package is GPL while the readme mention=
s it
> > as LGPL.
> >
> > Could you please clarify.
> > Thanks,
> > Lokesh
> > ________________________________________________________
> >
> > Lokesh Johri
> >
> > Software Engineering, Probe Systems, NP Test Inc.
> >
> > 150, Baytech Drive                 Work: (408) 586 6482
> >
> > San Jose CA 95132                Mobile: (408) 887-7338
> >
> >                                                   Fax: (408) 586-4662
> >
> >                                                   ljohri@nptest.com
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From cproch@seculogix.de Fri Dec 06 17:35:59 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18KR4h-0001wF-00
	for bug-commoncpp@gnu.org; Fri, 06 Dec 2002 17:35:59 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18KR4d-0001vv-00
	for bug-commoncpp@gnu.org; Fri, 06 Dec 2002 17:35:58 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18KR4c-0001vr-00
	for bug-commoncpp@gnu.org; Fri, 06 Dec 2002 17:35:55 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP
	id 56E7013AF8; Fri,  6 Dec 2002 22:36:09 +0100 (CET)
Content-Type: text/plain;
  charset="iso-2022-jp"
From: "Prochnow, Christian" <cproch@seculogix.de>
Reply-To: cproch@seculogix.de
To: "Leonard Thornton" <lst1017@bellsouth.net>,
	"'Skye Cove'" <scove@occl.com>, <bug-commoncpp@gnu.org>
Subject: Re: Few issues for ThreadFile.
Date: Fri, 6 Dec 2002 23:35:53 +0100
User-Agent: KMail/1.4.3
References: <!~!AAAAACtOcTp7wTJEkIAsu8pFESKESyEA@bellsouth.net>
In-Reply-To: <!~!AAAAACtOcTp7wTJEkIAsu8pFESKESyEA@bellsouth.net>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212062335.53848.cproch@seculogix.de>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Am Freitag 06 Dezember 2002 03:49 schrieb Leonard Thornton:
> Sorry, but no ftruncate in win32.....closest would be
> "open(....O_TRUNC)..."
>

This is not true.=20
It can be emulated with  SetFilePointer() and SetEndOfFile() functions of=
 the=20
win32 API.

Greetings,
Christian Prochnow


>
> Leonard Thornton
> Intelis, Inc
> leonardt@intelis-inc.com
>
> +1 770.825.0032 x 203
>
>
> -----Original Message-----
> From: bug-commoncpp-admin@gnu.org [mailto:bug-commoncpp-admin@gnu.org] =
On
> Behalf Of Skye Cove
> Sent: Thursday, December 05, 2002 9:26 PM
> To: bug-commoncpp@gnu.org
> Subject: Re: Few issues for ThreadFile.
>
> On Thu, 2002-12-05 at 14:01, David Sugar wrote:
> > I am not sure how widely portable ftruncate is,
>
> For what it's worth:
>
> Aaccording to `man ftruncate` (on a Linux 2.4.18 system): "4.4BSD, SVr4
> (these function calls first appeared in BSD  4.2). POSIX 1003.1=1B$B!>=1B=
(B1996  has
> ftruncate. POSIX 1003.1=1B$B!>=1B(B2001 also has truncate, as an XSI ex=
tension."
>
> I verified that it is also supported on FreeBSD 4.5, Solaris 8 and HP-U=
X 11
> (though I didn't compile any tests).
>
> Does the win32 API offer anything similar?
>
> -sc
>
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org http://mail.gnu.org/mailman/listinfo/bug-commoncp=
p




From ariston@cs.und.edu Sat Dec 07 10:40:31 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Kh4B-000158-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 10:40:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Kh48-00014F-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 10:40:30 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Kh48-00013i-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 10:40:28 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by gnudist.gnu.org with esmtp (Exim 4.10.13)
	id 18Kgnw-0006gg-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 10:23:45 -0500
Received: from penguin.cs.und.nodak.edu (penguin.cs.und.nodak.edu
	[134.129.212.25])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gB7FNgqf015643
	for <bug-commoncpp@gnu.org>; Sat, 7 Dec 2002 09:23:42 -0600
Date: Sat, 7 Dec 2002 09:19:14 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
X-X-Sender: <ariston@localhost.localdomain>
To: <bug-commoncpp@gnu.org>
Message-ID: <Pine.LNX.4.33.0212070913510.2861-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Autoconf check for XML support?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://monty-python.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 07 Dec 2002 15:40:32 -0000


I see that there is an OST_CCXX2_DYNLOADER check among the autoconf macros
defined by ost_check2.m4, but no such way to determine if XML support is
built in.  I'm at the point in my project where I need to make the
decision to move to a more portable autoconf/automake build environment,
and that means that I'll need my configure script to check for an
appropriate version of CommonC++ as well as for built-in XML support.
As to incremental XML parsing, I'll just have to assume that people use
the CVS version until an incremented release number exists for the next
release, when I do OST_CCXX2_VERSION.

Would it overclutter things to include an OST_CCXX2_XML check, or is there
perhaps a better way to accomplish this?  Thanks.

Ari Johnson




From dyfet@ostel.com Sat Dec 07 13:51:49 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Kk3I-00082V-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 13:51:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Kk3G-000825-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 13:51:48 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Kk3G-00081P-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 13:51:46 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gB7JKnF05419;
	Sat, 7 Dec 2002 14:20:49 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sat, 7 Dec 2002 14:20:49 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Ari Johnson <ariston@cs.und.edu>
In-Reply-To: <Pine.LNX.4.33.0212070913510.2861-100000@localhost.localdomain>
Message-ID: <Pine.LNX.4.44.0212071417250.5398-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bug-commoncpp@gnu.org
Subject: Re: Autoconf check for XML support?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://monty-python.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 07 Dec 2002 18:51:49 -0000

I thought the incremental XML parsing patch had made it into the current
distributions.  Let me review that.  The cc++/config.h file provides
compile time info on if xml support was built.  Perhaps you can create a
simple macro which examines it.  I think having a OST_CCXX2_XML check 
might be a useful addition to ost_check2.m4.

On Sat, 7 Dec 2002, Ari Johnson wrote:

> 
> I see that there is an OST_CCXX2_DYNLOADER check among the autoconf macros
> defined by ost_check2.m4, but no such way to determine if XML support is
> built in.  I'm at the point in my project where I need to make the
> decision to move to a more portable autoconf/automake build environment,
> and that means that I'll need my configure script to check for an
> appropriate version of CommonC++ as well as for built-in XML support.
> As to incremental XML parsing, I'll just have to assume that people use
> the CVS version until an incremented release number exists for the next
> release, when I do OST_CCXX2_VERSION.
> 
> Would it overclutter things to include an OST_CCXX2_XML check, or is there
> perhaps a better way to accomplish this?  Thanks.
> 
> Ari Johnson
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 



From fedemp@bulbasaur.rediris.es Sat Dec 07 17:46:52 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Knim-00068K-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 17:46:52 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Knij-000682-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 17:46:51 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Knij-00067o-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 17:46:49 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18Kni6-0002Ep-00; Sat, 07 Dec 2002 23:46:10 +0100
Date: Sat, 7 Dec 2002 23:46:09 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20021207224609.GA8391@bulbasaur.rediris.es>
Mail-Followup-To: David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org,
	bayonne-devel@lists.sourceforge.net
References: <20021205220833.GE607@risitas>
	<Pine.LNX.4.44.0212051853500.13903-100000@home.sys>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0212051853500.13903-100000@home.sys>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
cc: bayonne-devel@lists.sourceforge.net
Subject: Re: Fwd: [Bayonne-devel]timespec *, timespec *)' throws different
 exceptions (compiling commoncpp 1.0.7)
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://monty-python.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 07 Dec 2002 22:46:52 -0000


	I have been trying to add the AC_TRY_COMPILE, but I have found
that it will not work in FreeBSD due to some funny #defines related to
posix versions. So I have just added the "#ifdef __freeBSD__" you
suggested around the declaration in config.h (that way, those RH and
Debian should not complain too).

	When the AC_TRY_COMPILE check runs under FreeBSD, it reports
that the declaration of nanosleep is there, and any simple program
that #includes time.h or sys/time.h and uses nanosleep will compile
and work well. However, nanosleep is defined in time.h only if
_P1003_1B_VISIBLE_HISTORICALLY is defined (in sys/_posix.h). It seems
that the order in which CC++ includes some system headers implies that
the HISTORICALLY symbol is not defined because some posix version
symbols it depends on are affected.

On Thu, Dec 05, 2002 at 06:56:51PM -0500, David Sugar wrote:
> I think we will have to add a AC_TRY_COMPILE for it...I don't have any
> issue with this on any of the systems I normally test with, but I am
> gathering it is an issue at least on some older rh (pre 7.3, and,
> similarly pre debian r3) systems.  If we added it in initially for
> FreeBSD, maybe we should for the moment just have a "#ifdef __FreeBSD__"  
> around it...
> 
> On Thu, 5 Dec 2002, Federico Montesino Pouzols wrote:
> 
> > 
> > 	Oh, I had not had this problem yet, but I have just read a
> > mail posted to bug-commoncpp whose author seems to complain about the
> > same issue. The problem comes from the following lines in config.h:
> > 
> > #ifdef HAVE_PTHREAD_NANOSLEEP
> > #ifndef HAVE_PTHREAD_DELAY
> > #define HAVE_PTHREAD_DELAY
> > extern "C" int nanosleep(const struct timespec *rqtp, struct timespec *rmtp);
> > #define pthread_delay(x) nanosleep(x, NULL)
> > 
> > 	I recall we recently added the declaration of nanosleep
> > because it is missing (or requires the definition of some weird posix
> > version related symbols) in FreeBSD. However, this declaration is
> > conflicting with the one in time.h, which difers because of the 'throw
> > ()'. I guess we will have to make an AC_TRY_COMPILE with nanosleep to
> > see if it is already declared, and declare nanosleep in config.h only
> > when strictly necessary.
> > 
> > On Thu, Dec 05, 2002 at 04:51:01PM -0500, David Sugar wrote:
> > > Here's a curious problem I had not seen before...nanosleep is defined in at 
> > > least some glibc releases under time.h...
> > > 
> > > ----------  Forwarded Message  ----------
> > > 
> > > Subject: [Bayonne-devel]timespec *, timespec *)' throws different exceptions 
> > > (compiling commoncpp 1.0.7)
> > > Date: 05 Dec 2002 15:57:11 -0500
> > > From: Erik Enge <eenge@prium.net>
> > > To: bayonne-devel@lists.sourceforge.net
> > > 
> > > Hi.
> > > 
> > > I'm getting this when trying to compile CommonCPP version 1.0.7:
> > > 
> > > make[1]: Entering directory `/share/pak/commoncpp2/commoncpp2-1.0.7/src'
> > > /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I../include   
> > >   -I../src -DCCXX_EXPORT_LIBRARY  -I/usr/local/include -D_GNU_SOURCE 
> > >  -I/usr/include/libxml -I/usr/include -I../include -c thread.cpp rm -f
> > >  .libs/thread.lo
> > > c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
> > >  -I/usr/local/include -D_GNU_SOURCE -I/usr/include/libxml -I/usr/include
> > >  -I../include -c thread.cpp  -fPIC -DPIC -o .libs/thread.lo In file included
> > >  from thread.cpp:41:
> > > ../include/cc++/config.h:524: declaration of `int nanosleep (const
> > > timespec *, timespec *)' throws different exceptions
> > > /usr/include/time.h:284: than previous declaration `int nanosleep
> > > (const timespec *, timespec *) throw ()'
> > > make[1]: *** [thread.lo] Error 1
> > > make[1]: Leaving directory `/share/pak/commoncpp2/commoncpp2-1.0.7/src'
> > > make: *** [install-recursive] Error 1
> > > 
> > > Is there anything I can do to make it go away?  I'm getting this error
> > > when I try to compile 1.0.6 also - which previously compiled just fine.
> > > I don't think I changed anything between the compiles.  Confusing.
> > > 
> > > (Couple of unrelated comments; bayonne.sf.net and
> > > gnu.org/software/bayonne differ greatly in content but not in design and
> > > the FAQ page (http://bayonne.myip.org/cgi-bin/bayonne.faq) seems to be
> > > down).
> > > 
> > > Thanks,
> > > 
> > > Erik.
> > > 
> > > 
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > Bayonne-devel mailing list
> > > Bayonne-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/bayonne-devel
> > > 
> > > -------------------------------------------------------
> > > 
> > 
> 


From fedemp@bulbasaur.rediris.es Sat Dec 07 18:13:30 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Ko8Y-0001ss-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 18:13:30 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Ko8W-0001sh-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 18:13:30 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Ko8W-0001sc-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 18:13:28 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18Ko81-0002Fh-00; Sun, 08 Dec 2002 00:12:57 +0100
Date: Sun, 8 Dec 2002 00:12:57 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ari Johnson <ariston@cs.und.edu>
Message-ID: <20021207231257.GB8391@bulbasaur.rediris.es>
Mail-Followup-To: Ari Johnson <ariston@cs.und.edu>, bug-commoncpp@gnu.org
References: <Pine.LNX.4.33.0212070913510.2861-100000@localhost.localdomain>
	<Pine.LNX.4.44.0212071417250.5398-100000@home.sys>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0212071417250.5398-100000@home.sys>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Autoconf check for XML support?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://monty-python.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 07 Dec 2002 23:13:31 -0000


	I have just checked that the incremental code in the stable
branch, does it fail somehow?

	As for the check for xml, COMMON_XML_PARSING is defined in
cc++/config.h if xml support is built in.

On Sat, Dec 07, 2002 at 02:20:49PM -0500, David Sugar wrote:
> I thought the incremental XML parsing patch had made it into the current
> distributions.  Let me review that.  The cc++/config.h file provides
> compile time info on if xml support was built.  Perhaps you can create a
> simple macro which examines it.  I think having a OST_CCXX2_XML check 
> might be a useful addition to ost_check2.m4.
> 
> On Sat, 7 Dec 2002, Ari Johnson wrote:
> 
> > 
> > I see that there is an OST_CCXX2_DYNLOADER check among the autoconf macros
> > defined by ost_check2.m4, but no such way to determine if XML support is
> > built in.  I'm at the point in my project where I need to make the
> > decision to move to a more portable autoconf/automake build environment,
> > and that means that I'll need my configure script to check for an
> > appropriate version of CommonC++ as well as for built-in XML support.
> > As to incremental XML parsing, I'll just have to assume that people use
> > the CVS version until an incremented release number exists for the next
> > release, when I do OST_CCXX2_VERSION.
> > 
> > Would it overclutter things to include an OST_CCXX2_XML check, or is there
> > perhaps a better way to accomplish this?  Thanks.
> > 
> > Ari Johnson
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


From ariston@cs.und.edu Sat Dec 07 23:27:25 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Kt2L-0004lU-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 23:27:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Kt2J-0004l5-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 23:27:24 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Kt2I-0004l0-00
	for bug-commoncpp@gnu.org; Sat, 07 Dec 2002 23:27:22 -0500
Received: from penguin.cs.und.nodak.edu (penguin.cs.und.nodak.edu
	[134.129.212.25])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gB84RKqf020468;
	Sat, 7 Dec 2002 22:27:21 -0600
Date: Sat, 7 Dec 2002 22:22:51 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
X-X-Sender: <ariston@localhost.localdomain>
To: Federico Montesino Pouzols <fedemp@altern.org>
In-Reply-To: <20021207231257.GB8391@bulbasaur.rediris.es>
Message-ID: <Pine.LNX.4.33.0212072218370.24534-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bug-commoncpp@gnu.org
Subject: Re: Autoconf check for XML support?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://monty-python.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 08 Dec 2002 04:27:25 -0000


I want to check for XML support at ./configure time of my project, but
that won't be hard to set up a check for.  As to the incremental code,
I've just been tracking the CVS version so I don't know what's in or out
of the stable branch.  Thanks for confirming that it is.  I'll send a
patch here if I get a chance to write the autoconf check.

Ari Johnson

On Sun, 8 Dec 2002, Federico Montesino Pouzols wrote:

>
> 	I have just checked that the incremental code in the stable
> branch, does it fail somehow?
>
> 	As for the check for xml, COMMON_XML_PARSING is defined in
> cc++/config.h if xml support is built in.
>
> On Sat, Dec 07, 2002 at 02:20:49PM -0500, David Sugar wrote:
> > I thought the incremental XML parsing patch had made it into the current
> > distributions.  Let me review that.  The cc++/config.h file provides
> > compile time info on if xml support was built.  Perhaps you can create a
> > simple macro which examines it.  I think having a OST_CCXX2_XML check
> > might be a useful addition to ost_check2.m4.
> >
> > On Sat, 7 Dec 2002, Ari Johnson wrote:
> >
> > >
> > > I see that there is an OST_CCXX2_DYNLOADER check among the autoconf macros
> > > defined by ost_check2.m4, but no such way to determine if XML support is
> > > built in.  I'm at the point in my project where I need to make the
> > > decision to move to a more portable autoconf/automake build environment,
> > > and that means that I'll need my configure script to check for an
> > > appropriate version of CommonC++ as well as for built-in XML support.
> > > As to incremental XML parsing, I'll just have to assume that people use
> > > the CVS version until an incremented release number exists for the next
> > > release, when I do OST_CCXX2_VERSION.
> > >
> > > Would it overclutter things to include an OST_CCXX2_XML check, or is there
> > > perhaps a better way to accomplish this?  Thanks.
> > >
> > > Ari Johnson
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Bug-commoncpp mailing list
> > > Bug-commoncpp@gnu.org
> > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > >
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>



From ariston@cs.und.edu Sun Dec 08 12:05:37 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18L4s5-0007kD-00
	for bug-commoncpp@gnu.org; Sun, 08 Dec 2002 12:05:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18L4s3-0007jW-00
	for bug-commoncpp@gnu.org; Sun, 08 Dec 2002 12:05:36 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18L4s2-0007iM-00
	for bug-commoncpp@gnu.org; Sun, 08 Dec 2002 12:05:34 -0500
Received: from penguin.cs.und.nodak.edu (penguin.cs.und.nodak.edu
	[134.129.212.25])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gB8H5Xqf022463
	for <bug-commoncpp@gnu.org>; Sun, 8 Dec 2002 11:05:33 -0600
Date: Sun, 8 Dec 2002 11:01:02 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
X-X-Sender: <ariston@localhost.localdomain>
To: <bug-commoncpp@gnu.org>
In-Reply-To: <Pine.LNX.4.33.0212072218370.24534-100000@localhost.localdomain>
Message-ID: <Pine.LNX.4.33.0212081059030.14458-200000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-110666773-1039366862=:14458"
Subject: Re: Autoconf check for XML support?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 08 Dec 2002 17:05:37 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--8323328-110666773-1039366862=:14458
Content-Type: TEXT/PLAIN; charset=US-ASCII


Attached please find a patch against src/ost_check2.m4 to add the
following check:
  OST_CCXX2_XML([ACTION-IF-TRUE[,ACTION-IF-FALSE]])

On a side note, I've found that I have to set LIBS=-lgettextlib while
running a ./configure that calls OST_CCXX2_VERSION, because ccgnu2_config
doesn't include that library but it is required on my system for
getopt_long().

Ari Johnson

On Sat, 7 Dec 2002, Ari Johnson wrote:

>
> I want to check for XML support at ./configure time of my project, but
> that won't be hard to set up a check for.  As to the incremental code,
> I've just been tracking the CVS version so I don't know what's in or out
> of the stable branch.  Thanks for confirming that it is.  I'll send a
> patch here if I get a chance to write the autoconf check.
>
> Ari Johnson
>
> On Sun, 8 Dec 2002, Federico Montesino Pouzols wrote:
>
> >
> > 	I have just checked that the incremental code in the stable
> > branch, does it fail somehow?
> >
> > 	As for the check for xml, COMMON_XML_PARSING is defined in
> > cc++/config.h if xml support is built in.
> >
> > On Sat, Dec 07, 2002 at 02:20:49PM -0500, David Sugar wrote:
> > > I thought the incremental XML parsing patch had made it into the current
> > > distributions.  Let me review that.  The cc++/config.h file provides
> > > compile time info on if xml support was built.  Perhaps you can create a
> > > simple macro which examines it.  I think having a OST_CCXX2_XML check
> > > might be a useful addition to ost_check2.m4.
> > >
> > > On Sat, 7 Dec 2002, Ari Johnson wrote:
> > >
> > > >
> > > > I see that there is an OST_CCXX2_DYNLOADER check among the autoconf macros
> > > > defined by ost_check2.m4, but no such way to determine if XML support is
> > > > built in.  I'm at the point in my project where I need to make the
> > > > decision to move to a more portable autoconf/automake build environment,
> > > > and that means that I'll need my configure script to check for an
> > > > appropriate version of CommonC++ as well as for built-in XML support.
> > > > As to incremental XML parsing, I'll just have to assume that people use
> > > > the CVS version until an incremented release number exists for the next
> > > > release, when I do OST_CCXX2_VERSION.
> > > >
> > > > Would it overclutter things to include an OST_CCXX2_XML check, or is there
> > > > perhaps a better way to accomplish this?  Thanks.
> > > >
> > > > Ari Johnson
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Bug-commoncpp mailing list
> > > > Bug-commoncpp@gnu.org
> > > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Bug-commoncpp mailing list
> > > Bug-commoncpp@gnu.org
> > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> >
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>

--8323328-110666773-1039366862=:14458
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="ccxx_autoconf_xml.patch"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.4.33.0212081101020.14458@localhost.localdomain>
Content-Description: 
Content-Disposition: attachment; filename="ccxx_autoconf_xml.patch"

SW5kZXg6IHNyYy9vc3RfY2hlY2syLm00DQo9PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09DQpSQ1MgZmlsZTogL2N2c3Jvb3QvY29tbW9uY3BwL2NvbW1vbmNwcDIv
c3JjL29zdF9jaGVjazIubTQsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjEu
MS4xDQpkaWZmIC1yMS4xLjEuMSBvc3RfY2hlY2syLm00DQoxMDlhMTEwLDEz
NA0KPiBBQ19ERUZVTihPU1RfQ0NYWDJfWE1MLA0KPiBbDQo+ICAgQUNfTVNH
X0NIRUNLSU5HKGZvciBjb21tb25jcHAyIHhtbCBwYXJzaW5nKQ0KPiAgIEFD
X0xBTkdfUFVTSChDKyspDQo+ICAgQUNfUkVRVUlSRV9DUFANCj4gICBBQ19U
UllfUlVOKFsNCj4gI2luY2x1ZGUgPGNjKysvY29uZmlnLmg+DQo+ICNpZm5k
ZWYgQ09NTU9OX1hNTF9QQVJTSU5HDQo+ICNlcnJvciAiIg0KPiAjZW5kaWYN
Cj4gaW50IG1haW4oKSB7DQo+ICAgcmV0dXJuIDA7DQo+IH0NCj4gXSwgb3N0
X2N2X2NjeHhfeG1sPXllcywgb3N0X2N2X2NjeHhfeG1sPW5vKQ0KPiAgIEFD
X0xBTkdfUE9QKEMrKykNCj4gICBpZiB0ZXN0ICJ4JG9zdF9jdl9jY3h4X3ht
bCIgPSAieHllcyIgOyB0aGVuDQo+ICAgICBBQ19NU0dfUkVTVUxUKHllcykN
Cj4gICAgIEFDX0RFRklORShIQVZFX09TVF9DQ1hYMl9YTUxfUEFSU0lORykN
Cj4gICAgIGlmZWxzZShbJDFdLCAsIDosIFskMV0pDQo+ICAgZWxzZQ0KPiAg
ICAgQUNfTVNHX1JFU1VMVChubykNCj4gICAgIGlmZWxzZShbJDJdLCAsIDos
IFskMl0pDQo+ICAgZmkNCj4gXSkNCj4gDQo=
--8323328-110666773-1039366862=:14458--


From ariston@cs.und.edu Sun Dec 08 20:41:51 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18LCvf-0003cC-00
	for bug-commoncpp@gnu.org; Sun, 08 Dec 2002 20:41:51 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18LCvd-0003c0-00
	for bug-commoncpp@gnu.org; Sun, 08 Dec 2002 20:41:50 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18LCvc-0003br-00
	for bug-commoncpp@gnu.org; Sun, 08 Dec 2002 20:41:49 -0500
Received: from penguin.cs.und.nodak.edu (penguin.cs.und.nodak.edu
	[134.129.212.25])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gB91fkqf019255
	for <bug-commoncpp@gnu.org>; Sun, 8 Dec 2002 19:41:46 -0600
Date: Sun, 8 Dec 2002 19:37:14 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
X-X-Sender: <ariston@localhost.localdomain>
To: <bug-commoncpp@gnu.org>
In-Reply-To: <Pine.LNX.4.33.0212081059030.14458-200000@localhost.localdomain>
Message-ID: <Pine.LNX.4.33.0212081936080.28595-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: Autoconf check for XML support?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 09 Dec 2002 01:41:52 -0000


I made a mistake in the patch, causing autoheader to fail on my system.
In the AC_DEFINE() call, it should read:
  AC_DEFINE(HAVE_OST_CCXX2_XML_PARSING, 1, [Define this if the CommonC++ library was compiled with XML parsing support])

On Sun, 8 Dec 2002, Ari Johnson wrote:

>
> Attached please find a patch against src/ost_check2.m4 to add the
> following check:
>   OST_CCXX2_XML([ACTION-IF-TRUE[,ACTION-IF-FALSE]])
>
> On a side note, I've found that I have to set LIBS=-lgettextlib while
> running a ./configure that calls OST_CCXX2_VERSION, because ccgnu2_config
> doesn't include that library but it is required on my system for
> getopt_long().
>
> Ari Johnson
>
> On Sat, 7 Dec 2002, Ari Johnson wrote:
>
> >
> > I want to check for XML support at ./configure time of my project, but
> > that won't be hard to set up a check for.  As to the incremental code,
> > I've just been tracking the CVS version so I don't know what's in or out
> > of the stable branch.  Thanks for confirming that it is.  I'll send a
> > patch here if I get a chance to write the autoconf check.
> >
> > Ari Johnson
> >
> > On Sun, 8 Dec 2002, Federico Montesino Pouzols wrote:
> >
> > >
> > > 	I have just checked that the incremental code in the stable
> > > branch, does it fail somehow?
> > >
> > > 	As for the check for xml, COMMON_XML_PARSING is defined in
> > > cc++/config.h if xml support is built in.
> > >
> > > On Sat, Dec 07, 2002 at 02:20:49PM -0500, David Sugar wrote:
> > > > I thought the incremental XML parsing patch had made it into the current
> > > > distributions.  Let me review that.  The cc++/config.h file provides
> > > > compile time info on if xml support was built.  Perhaps you can create a
> > > > simple macro which examines it.  I think having a OST_CCXX2_XML check
> > > > might be a useful addition to ost_check2.m4.
> > > >
> > > > On Sat, 7 Dec 2002, Ari Johnson wrote:
> > > >
> > > > >
> > > > > I see that there is an OST_CCXX2_DYNLOADER check among the autoconf macros
> > > > > defined by ost_check2.m4, but no such way to determine if XML support is
> > > > > built in.  I'm at the point in my project where I need to make the
> > > > > decision to move to a more portable autoconf/automake build environment,
> > > > > and that means that I'll need my configure script to check for an
> > > > > appropriate version of CommonC++ as well as for built-in XML support.
> > > > > As to incremental XML parsing, I'll just have to assume that people use
> > > > > the CVS version until an incremented release number exists for the next
> > > > > release, when I do OST_CCXX2_VERSION.
> > > > >
> > > > > Would it overclutter things to include an OST_CCXX2_XML check, or is there
> > > > > perhaps a better way to accomplish this?  Thanks.
> > > > >
> > > > > Ari Johnson
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Bug-commoncpp mailing list
> > > > > Bug-commoncpp@gnu.org
> > > > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Bug-commoncpp mailing list
> > > > Bug-commoncpp@gnu.org
> > > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > >
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> >
>



From a2574@dis.ulpgc.es Mon Dec 09 19:15:19 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18LY3T-0007k2-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 19:15:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18LY3P-0007jH-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 19:15:17 -0500
Received: from serdis.dis.ulpgc.es ([193.145.145.17])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18LY3O-0007iQ-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 19:15:14 -0500
Received: from siglo21.dis.ulpgc.es (IDENT:root@siglo21.dis.ulpgc.es
	[193.145.145.16])
	by serdis.dis.ulpgc.es (8.10.2/8.9.2) with ESMTP id gBA0Ok7170190
	for <bug-commoncpp@gnu.org>; Tue, 10 Dec 2002 00:24:46 GMT
Received: (from nobody@localhost)
	by siglo21.dis.ulpgc.es (8.11.6/8.9.3) id gBA1CQg14957;
	Tue, 10 Dec 2002 01:12:26 GMT
Date: Tue, 10 Dec 2002 01:12:26 GMT
Message-Id: <200212100112.gBA1CQg14957@siglo21.dis.ulpgc.es>
X-Authentication-Warning: siglo21.dis.ulpgc.es: nobody set sender to
	a2574@dis.ulpgc.es using -f
From: a2574@dis.ulpgc.es
To: bug-commoncpp@gnu.org
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP3 Imap webMail Program 2.0.11
Sender: a2574@dis.ulpgc.es
Subject: Re: Segmentation fault when using exception handling and ttystream
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: a2574@dis.ulpgc.es
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 10 Dec 2002 00:15:20 -0000

Mensaje citado por: David Sugar <dyfet@ostel.com>:

> Generally a catch handler should catch this, but there have been 
changes > in 
> the abi which may make self thrown objects have strange behavior.  I 
woul> d 
> suggest trying setException(Thread::throwException);

I tried but it did not work. In fact, whenever you trhow any kind of 
exceptions (i.e. and int) the program crashes. And is not a \\\"Program 
Aborted\\\" message but a \\\"Segmentation Fault\\\".

I dont know what to do. I finally thought that it was a program 
related with my compiler, but I upgraded and tested code that uses 
exceptions and worked right. 

I will try to isolate the code I need, to see if it was a problem of 
the thread library or something... dont really know.

So if any of you have an idea... 

Thanks in advance (or however it is said) , Jose Fernandez.

> On Thursday 05 December 2002 07:04, a2574@dis.ulpgc.es wrote:
> > Hello!
> >
> > Fisrt of all, Im not an advanced C++ programmer... not even close. 
So
> > maybe the answer is just in front of me but I havent see it yet.
> >
> > Im using commoncpp2-1.0.7. I use the serial interface for 
connecting to
> >  a device (a Laser). The problem is that when I use it without 
exceptio> n
> > handling everything goes right, but if I switch it on
> > (this->setError(true)) it makes a segmentation fault when an error
> > occurs. I traced the code and apparently (or so the debugger says) 
the
> > error is when the method Serial::error throws the object (itself)
> >
> > throw((Serial*)this)
> >
> > My code is this: (I inerhit from ttystream)
> >
> > class SerialInterface: public ost::ttystream{
> > public:
> > SerialInterface(const char *device);
> > }
> >
> > // and implementation is:
> >
> > SerialInterface::SerialInterface(const char *device){
> >     this->setError(true);
> >      try{
> >          open(device);   // The method for openning the device
> >                          // I call it with a wrong argument 
\\\\\\\"/dev/jdss> \\\\\\\"
> >      }catch (...){       // I have tried also (Serial *e) and so 
on ;(
> >          std::cout:: << getErrorNumber();
> >      }
> > }
> >
> >
> > Well, Is been two days now and Im starting to fed up... Two days 
and no
> > code written, thats not what I call productivity.. he.
> >
> > Hoping you could help me...
> >
> > PS: By the way... to install was a nightmare (as well hehe), the 
debian
> > package does not seem to work (but I guess it does not correspond 
to an> y
> > of you) and /usr/include/time.h conflicts with
> > /usr/include/cc++/cc+2/config.h its definition of nanosleep does 
not
> > throw any exception, so I changed it, but I guess this is not the
> > reason....
> >
> > By again.
> >
> > Jose.
> >
> >
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 


From lgandhi@peerless.com Mon Dec 09 22:26:08 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Lb27-0001mR-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 22:26:07 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Lb24-0001kF-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 22:26:07 -0500
Received: from [209.225.56.192] (helo=str1sowa001.iad.hostedmail.net)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Lb24-0001jF-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 22:26:04 -0500
Received: from STR1VEXC002.CTHES.COM ([209.225.56.57]) by
	str1sowa001.iad.hostedmail.net with Microsoft SMTPSVC(5.0.2195.2966);
	Mon, 9 Dec 2002 22:25:52 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C29FFB.D7563DC8"
Date: Mon, 9 Dec 2002 22:25:51 -0500
Message-ID: <4A798B3E3B58794FB40A47DFCE728BA808902C@STR1VEXC002.CTHES.COM>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Incorrect code generation when returning class by value
Thread-Index: AcKf+2a0zWuzuh5gTnuKsyYsasGrqQ==
From: "Lakhbir Gandhi" <lgandhi@peerless.com>
To: <bug-commoncpp@gnu.org>
X-OriginalArrivalTime: 10 Dec 2002 03:25:52.0802 (UTC)
	FILETIME=[D7ECC020:01C29FFB]
cc: "Burk, Jimm" <jburk@peerless.com>
cc: "Whealon, Lynetta" <lwhealon@peerless.com>
cc: "Garcia, Ivan" <igarcia@peerless.com>
cc: "Tang, Ivan" <itang@peerless.com>
Subject: Incorrect code generation when returning class by value
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 10 Dec 2002 03:26:08 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C29FFB.D7563DC8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,
=20
I want to report a bug wherein if a method returns a class by value,
incorrect code is generated.
It manifests itself when copy constructors are not available, in my case
I had my copy constructor declared 'explicit' to prevent the compiler
from generating expensive temporary objects.
=20
The environment is as follows:
Compiler#1: gcc 2.95.3 with DaveK's modifications for VxWorksPPC.
Compiler#2: cygwin 2.95.3-5
Host: PIII MS Windows 2000
Shell: Cmd
Compile command: c++<ppc> test.cpp -g -c -o test.o
Disassembly command: objdump<ppc> -d -r -S test.o=20
=20
Both compilers produce the same result so I don't think DaveK's
modifications have anything to do with it.
=20
The test code is as follows:
=20
    class A  {
=20

    };
=20
class B  {
    public :
       =20
            B(int  init);
            B(A  init);
explicit  B(const B & init);
=20
         operator A();
       =20
    };
=20
    class C  {
   =20
        public :
         operator B();
       =20
   =20
    };
   =20
     C::operator B() {
        return B(12345);
    }
   =20
=20
The setup is described so:
=20
class B contains conversion constructor and operator for class A.
class B also has a conversion constructor from int.
class C defines a conversion operator to class B.
The copy constructor for class B is declared explicit to prevent the
compiler from generating temporary B objects.
C's conversion operator returns a B object by value, not as a reference
or pointer.=20
=20
The implementation of C::operator B() elects to return an object B which
is initialized by the integer 12345.
Because class B has a conversion constructor from int, all we should see
in the assembly code generated is a call to B::B(int).
=20
However I get the following:
=20

MiscTest.ppc.o:     file format elf32-powerpc
=20
Disassembly of section .text:
=20
00000000 <C::operator B(void)>:
       =20
   =20
    };
   =20
     C::operator B() {
   0: 94 21 ff c0  stwu r1,-64(r1)
   4: 7c 08 02 a6  mflr r0
   8: 93 61 00 2c  stw r27,44(r1)
   c: 93 81 00 30  stw r28,48(r1)
  10: 93 a1 00 34  stw r29,52(r1)
  14: 93 c1 00 38  stw r30,56(r1)
  18: 93 e1 00 3c  stw r31,60(r1)
  1c: 90 01 00 44  stw r0,68(r1)
  20: 7c 3f 0b 78  mr r31,r1
  24: 7c 7d 1b 78  mr r29,r3
  28: 7c 9c 23 78  mr r28,r4
        return B(12345);
  2c: 3b 7f 00 09  addi r27,r31,9
  30: 38 1f 00 18  addi r0,r31,24
  34: 7c 03 03 78  mr r3,r0
  38: 38 80 30 39  li r4,12345
  3c: 48 00 00 01  bl 3c <C::operator B(void)+0x3c>
   3c: R_PPC_REL24 B::B(int)
  40: 7c 60 1b 78  mr r0,r3
  44: 39 3f 00 18  addi r9,r31,24
  48: 7f 63 db 78  mr r3,r27
  4c: 7d 24 4b 78  mr r4,r9
  50: 4c c6 31 82  crclr 4*cr1+eq
  54: 48 00 00 01  bl 54 <C::operator B(void)+0x54>
   54: R_PPC_REL24 B::operator A(void)
  58: 88 1f 00 09  lbz r0,9(r31)
  5c: 39 20 00 00  li r9,0
  60: 99 3f 00 08  stb r9,8(r31)
  64: 7f a3 eb 78  mr r3,r29
  68: 38 9f 00 08  addi r4,r31,8
  6c: 48 00 00 01  bl 6c <C::operator B(void)+0x6c>
   6c: R_PPC_REL24 B::B(A)
  70: 7c 60 1b 78  mr r0,r3
  74: 48 00 00 0c  b 80 <C::operator B(void)+0x80>
  78: 48 00 00 08  b 80 <C::operator B(void)+0x80>
  7c: 48 00 00 04  b 80 <C::operator B(void)+0x80>
    }
  80: 7f a3 eb 78  mr r3,r29
  84: 81 61 00 00  lwz r11,0(r1)
  88: 80 0b 00 04  lwz r0,4(r11)
  8c: 7c 08 03 a6  mtlr r0
  90: 83 6b ff ec  lwz r27,-20(r11)
  94: 83 8b ff f0  lwz r28,-16(r11)
  98: 83 ab ff f4  lwz r29,-12(r11)
  9c: 83 cb ff f8  lwz r30,-8(r11)
  a0: 83 eb ff fc  lwz r31,-4(r11)
  a4: 7d 61 5b 78  mr r1,r11
  a8: 4e 80 00 20  blr

=20
At offset 3c above, the correct call to B::B(int) is generated.
But at offset 54, there is a call to B::operator A !!!!!=20
To add insult to injury, this returned A is used to call B::B(A) at
offset 6c !
This causes C::operator B() to return the B object created above, which
is initialized by an A instead of an int which was the intent.
=20
This is incorrect behavior on two accounts:
1) ISO/IEC 14882:1998 in section 12.3.4 specifies that "At most one
user-defined conversion (constructor or conversion function) is
implictely applied to a single value", and here we see two such
conversions, from B to A and then back to B.
2) The B object created by B::B(A) at offset 6c is returned instead of
the the B object created by B::B(int) at offset 3c.
=20
I have examined the rtl and it contains the incorrect return semantic
described above, so rtl to asm conversion is not the issue.
Either the bug is in gcc/cp/parse.y or tree generation is incorrect or
the resolution of candidate functions is incorrect or has the wrong data
or the code in gcc/cp/typeck.c between line 7449 and line 7453 in
function c_expand_return does not implement  the correct semantics.
Please be aware this is just a conjecture.
=20

Now if I do not declare B::B(B&) explicit, the correct code gets
generated at offset 30 as shown below.
=20
=20
MiscTest.ppc.o:     file format elf32-powerpc
=20
Disassembly of section .text:
=20
00000000 <C::operator B(void)>:
       =20
   =20
    };
   =20
     C::operator B() {
   0: 94 21 ff e0  stwu r1,-32(r1)
   4: 7c 08 02 a6  mflr r0
   8: 93 81 00 10  stw r28,16(r1)
   c: 93 a1 00 14  stw r29,20(r1)
  10: 93 c1 00 18  stw r30,24(r1)
  14: 93 e1 00 1c  stw r31,28(r1)
  18: 90 01 00 24  stw r0,36(r1)
  1c: 7c 3f 0b 78  mr r31,r1
  20: 7c 7d 1b 78  mr r29,r3
  24: 7c 9c 23 78  mr r28,r4
        return B(12345);
  28: 7f a3 eb 78  mr r3,r29
  2c: 38 80 30 39  li r4,12345
  30: 48 00 00 01  bl 30 <C::operator B(void)+0x30>
   30: R_PPC_REL24 B::B(int)
  34: 7c 60 1b 78  mr r0,r3
  38: 48 00 00 0c  b 44 <C::operator B(void)+0x44>
  3c: 48 00 00 08  b 44 <C::operator B(void)+0x44>
  40: 48 00 00 04  b 44 <C::operator B(void)+0x44>
    }
  44: 7f a3 eb 78  mr r3,r29
  48: 81 61 00 00  lwz r11,0(r1)
  4c: 80 0b 00 04  lwz r0,4(r11)
  50: 7c 08 03 a6  mtlr r0
  54: 83 8b ff f0  lwz r28,-16(r11)
  58: 83 ab ff f4  lwz r29,-12(r11)
  5c: 83 cb ff f8  lwz r30,-8(r11)
  60: 83 eb ff fc  lwz r31,-4(r11)
  64: 7d 61 5b 78  mr r1,r11
  68: 4e 80 00 20  blr

This code should have been generated for the explicit copy constructor
case because as you can see there is no mention of B::B(B&)  here!
I think it is a definite bug.
=20
I have tried commenting out the conversion operator B::operator A() and
the conversion constructor B::B(A) one at a time, the compiler then
generates the error messages shown below.
=20
Change#1:
//        B::B(A  init);

result#1:
=20
MiscTest.cpp: In method `C::operator B()':
MiscTest.cpp:29: no matching function for call to `B::B (B)'
MiscTest.cpp:11: candidates are: B::B(int)

=20
change#2:
//         B::operator A();

resullt#2:
MiscTest.cpp: In method `C::operator B()':
MiscTest.cpp:29: no matching function for call to `B::B (B)'
MiscTest.cpp:11: candidates are: B::B(int)
MiscTest.cpp:14:                 B::B(A)

I am a newbie to gcc innards, so I may be way off the mark. Sorry I
don't have more details yet, I just ran into this problem last friday.
=20
VisualC++ however does not display this behaviour and generates correct
code.

Regards,=20

Lakhbir Gandhi=20
Consulting Engineer=20
lgandhi@peerless.com=20
253-395-8890 x13.=20

=20

------_=_NextPart_001_01C29FFB.D7563DC8
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002>Hello,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>I want =
to report a=20
bug wherein if a method returns a class by value, incorrect code is=20
generated.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>It =
manifests itself=20
when copy constructors are not available, in my case I had&nbsp;my copy=20
constructor declared 'explicit' to prevent the compiler from generating=20
expensive temporary objects.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>The =
environment is=20
as follows:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>Compiler#1:=20
gcc</SPAN></FONT><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002> 2.95.3=20
with DaveK's modifications for VxWorksPPC.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002><FONT =
face=3DArial=20
size=3D2><SPAN =
class=3D553084001-10122002>Compiler#2:&nbsp;</SPAN></FONT>cygwin=20
2.95.3-5</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>Host: =
PIII MS=20
Windows 2000</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>Shell: =

Cmd</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>Compile command:=20
c++&lt;ppc&gt; test.cpp -g -c -o test.o</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>Disassembly command:=20
objdump&lt;ppc&gt; -d -r -S test.o </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>Both =
compilers=20
produce the same result so I don't think DaveK's modifications have =
anything to=20
do with it.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>The =
test code is as=20
follows:</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>&nbsp;&nbsp;&nbsp;=20
class A&nbsp; {</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002><BR>&nbsp;&nbsp;&nbsp; };</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>class =
B&nbsp;=20
{<BR>&nbsp;&nbsp;&nbsp; public=20
:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
B(int&nbsp; init);<BR><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=20
B(A&nbsp; init);<BR></SPAN></FONT>explicit&nbsp;&nbsp;B(const B &amp;=20
init);</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
operator A();<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp; };</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>&nbsp;&nbsp;&nbsp;=20
class C&nbsp; {<BR>&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; public=20
:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; operator=20
B();<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<BR>&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp; };<BR>&nbsp;&nbsp;&nbsp; =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
C::operator B() {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return=20
B(12345);<BR>&nbsp;&nbsp;&nbsp; }<BR>&nbsp;&nbsp;&nbsp; =
</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>The =
setup is=20
described so:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>class =
B contains=20
conversion constructor and operator for class A.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>class =
B also has a=20
conversion constructor from int.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>class =
C defines a=20
conversion operator to class B.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>The =
copy constructor=20
for class B is declared explicit to prevent the compiler from generating =

temporary B objects.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>C's =
conversion=20
operator returns a B object by value, not as a reference or pointer.=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>The =
implementation=20
of C::operator B() elects to return an object B which is initialized by =
the=20
integer 12345.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>Because class B has=20
a conversion constructor from int, all we should see in the assembly =
code=20
generated is a call to B::B(int).</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>However I get the=20
following:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002><BR>MiscTest.ppc.o:&nbsp;&nbsp;&nbsp;&nbsp; =
file format=20
elf32-powerpc</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>Disassembly of=20
section .text:</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>00000000=20
&lt;C::operator =
B(void)&gt;:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp; <BR>&nbsp;&nbsp;&nbsp; };<BR>&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp; C::operator B() {<BR>&nbsp;&nbsp; =
0:&nbsp;94 21 ff=20
c0 &nbsp;stwu&nbsp;r1,-64(r1)<BR>&nbsp;&nbsp; 4:&nbsp;7c 08 02 a6=20
&nbsp;mflr&nbsp;r0<BR>&nbsp;&nbsp; 8:&nbsp;93 61 00 2c=20
&nbsp;stw&nbsp;r27,44(r1)<BR>&nbsp;&nbsp; c:&nbsp;93 81 00 30=20
&nbsp;stw&nbsp;r28,48(r1)<BR>&nbsp; 10:&nbsp;93 a1 00 34=20
&nbsp;stw&nbsp;r29,52(r1)<BR>&nbsp; 14:&nbsp;93 c1 00 38=20
&nbsp;stw&nbsp;r30,56(r1)<BR>&nbsp; 18:&nbsp;93 e1 00 3c=20
&nbsp;stw&nbsp;r31,60(r1)<BR>&nbsp; 1c:&nbsp;90 01 00 44=20
&nbsp;stw&nbsp;r0,68(r1)<BR>&nbsp; 20:&nbsp;7c 3f 0b 78=20
&nbsp;mr&nbsp;r31,r1<BR>&nbsp; 24:&nbsp;7c 7d 1b 78=20
&nbsp;mr&nbsp;r29,r3<BR>&nbsp; 28:&nbsp;7c 9c 23 78=20
&nbsp;mr&nbsp;r28,r4<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
return=20
B(12345);<BR>&nbsp; 2c:&nbsp;3b 7f 00 09 =
&nbsp;addi&nbsp;r27,r31,9<BR>&nbsp;=20
30:&nbsp;38 1f 00 18 &nbsp;addi&nbsp;r0,r31,24<BR>&nbsp; 34:&nbsp;7c 03 =
03 78=20
&nbsp;mr&nbsp;r3,r0<BR>&nbsp; 38:&nbsp;38 80 30 39=20
&nbsp;li&nbsp;r4,12345<BR>&nbsp; 3c:&nbsp;48 00 00 01 &nbsp;bl&nbsp;3c=20
&lt;C::operator B(void)+0x3c&gt;<BR>&nbsp;&nbsp;&nbsp;3c:=20
R_PPC_REL24&nbsp;B::B(int)<BR>&nbsp; 40:&nbsp;7c 60 1b 78=20
&nbsp;mr&nbsp;r0,r3<BR>&nbsp; 44:&nbsp;39 3f 00 18=20
&nbsp;addi&nbsp;r9,r31,24<BR>&nbsp; 48:&nbsp;7f 63 db 78=20
&nbsp;mr&nbsp;r3,r27<BR>&nbsp; 4c:&nbsp;7d 24 4b 78=20
&nbsp;mr&nbsp;r4,r9<BR>&nbsp; 50:&nbsp;4c c6 31 82=20
&nbsp;crclr&nbsp;4*cr1+eq<BR>&nbsp; 54:&nbsp;48 00 00 01 =
&nbsp;bl&nbsp;54=20
&lt;C::operator B(void)+0x54&gt;<BR>&nbsp;&nbsp;&nbsp;54:=20
R_PPC_REL24&nbsp;B::operator A(void)<BR>&nbsp; 58:&nbsp;88 1f 00 09=20
&nbsp;lbz&nbsp;r0,9(r31)<BR>&nbsp; 5c:&nbsp;39 20 00 00=20
&nbsp;li&nbsp;r9,0<BR>&nbsp; 60:&nbsp;99 3f 00 08=20
&nbsp;stb&nbsp;r9,8(r31)<BR>&nbsp; 64:&nbsp;7f a3 eb 78=20
&nbsp;mr&nbsp;r3,r29<BR>&nbsp; 68:&nbsp;38 9f 00 08=20
&nbsp;addi&nbsp;r4,r31,8<BR>&nbsp; 6c:&nbsp;48 00 00 01 &nbsp;bl&nbsp;6c =

&lt;C::operator B(void)+0x6c&gt;<BR>&nbsp;&nbsp;&nbsp;6c:=20
R_PPC_REL24&nbsp;B::B(A)<BR>&nbsp; 70:&nbsp;7c 60 1b 78=20
&nbsp;mr&nbsp;r0,r3<BR>&nbsp; 74:&nbsp;48 00 00 0c &nbsp;b&nbsp;80=20
&lt;C::operator B(void)+0x80&gt;<BR>&nbsp; 78:&nbsp;48 00 00 08 =
&nbsp;b&nbsp;80=20
&lt;C::operator B(void)+0x80&gt;<BR>&nbsp; 7c:&nbsp;48 00 00 04 =
&nbsp;b&nbsp;80=20
&lt;C::operator B(void)+0x80&gt;<BR>&nbsp;&nbsp;&nbsp; }<BR>&nbsp; =
80:&nbsp;7f=20
a3 eb 78 &nbsp;mr&nbsp;r3,r29<BR>&nbsp; 84:&nbsp;81 61 00 00=20
&nbsp;lwz&nbsp;r11,0(r1)<BR>&nbsp; 88:&nbsp;80 0b 00 04=20
&nbsp;lwz&nbsp;r0,4(r11)<BR>&nbsp; 8c:&nbsp;7c 08 03 a6=20
&nbsp;mtlr&nbsp;r0<BR>&nbsp; 90:&nbsp;83 6b ff ec=20
&nbsp;lwz&nbsp;r27,-20(r11)<BR>&nbsp; 94:&nbsp;83 8b ff f0=20
&nbsp;lwz&nbsp;r28,-16(r11)<BR>&nbsp; 98:&nbsp;83 ab ff f4=20
&nbsp;lwz&nbsp;r29,-12(r11)<BR>&nbsp; 9c:&nbsp;83 cb ff f8=20
&nbsp;lwz&nbsp;r30,-8(r11)<BR>&nbsp; a0:&nbsp;83 eb ff fc=20
&nbsp;lwz&nbsp;r31,-4(r11)<BR>&nbsp; a4:&nbsp;7d 61 5b 78=20
&nbsp;mr&nbsp;r1,r11<BR>&nbsp; a8:&nbsp;4e 80 00 20=20
&nbsp;blr<BR></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002>&nbsp;</DIV></SPAN></FONT>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>At =
offset 3c above,=20
the correct call to B::B(int) is generated.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>But at =
offset 54,=20
there is a call to B::operator A !!!!! </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>To add =
insult to=20
injury, this returned A is used to call B::B(A) at offset 6c=20
!</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>This =
causes=20
C::operator B() to return&nbsp;the B object created above, which is =
initialized=20
by an A instead of an int which was the intent.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>This =
is incorrect=20
behavior on&nbsp;two accounts:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>1) =
ISO/IEC=20
14882:1998 in section 12.3.4 specifies that "At most one user-defined =
conversion=20
(constructor or conversion function) is implictely applied to a single =
value",=20
and here we see two such conversions, from B to A and then back to=20
B.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>2) The =
B object=20
created by B::B(A) at offset 6c is returned instead of the the B object=20
created&nbsp;by B::B(int) at offset 3c.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>I have =
examined the=20
rtl and it&nbsp;contains the incorrect return semantic described above, =
so rtl=20
to asm conversion is not the issue.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>Either&nbsp;the bug=20
is in gcc/cp/parse.y&nbsp;or tree generation is incorrect or the=20
resolution&nbsp;of candidate functions is incorrect or has the wrong =
data or the=20
code in gcc/cp/typeck.c between line 7449 and line 7453 in function=20
c_expand_return does not implement&nbsp; the correct semantics. Please =
be aware=20
this is just a conjecture.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV><BR>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>Now if =
I do not=20
declare B::B(B&amp;) explicit, the correct code gets generated&nbsp;at =
offset 30=20
as shown below.</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>MiscTest.ppc.o:&nbsp;&nbsp;&nbsp;&nbsp; file format=20
elf32-powerpc</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>Disassembly of=20
section .text:</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>00000000=20
&lt;C::operator =
B(void)&gt;:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp; <BR>&nbsp;&nbsp;&nbsp; };<BR>&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp; C::operator B() {<BR>&nbsp;&nbsp; =
0:&nbsp;94 21 ff=20
e0 &nbsp;stwu&nbsp;r1,-32(r1)<BR>&nbsp;&nbsp; 4:&nbsp;7c 08 02 a6=20
&nbsp;mflr&nbsp;r0<BR>&nbsp;&nbsp; 8:&nbsp;93 81 00 10=20
&nbsp;stw&nbsp;r28,16(r1)<BR>&nbsp;&nbsp; c:&nbsp;93 a1 00 14=20
&nbsp;stw&nbsp;r29,20(r1)<BR>&nbsp; 10:&nbsp;93 c1 00 18=20
&nbsp;stw&nbsp;r30,24(r1)<BR>&nbsp; 14:&nbsp;93 e1 00 1c=20
&nbsp;stw&nbsp;r31,28(r1)<BR>&nbsp; 18:&nbsp;90 01 00 24=20
&nbsp;stw&nbsp;r0,36(r1)<BR>&nbsp; 1c:&nbsp;7c 3f 0b 78=20
&nbsp;mr&nbsp;r31,r1<BR>&nbsp; 20:&nbsp;7c 7d 1b 78=20
&nbsp;mr&nbsp;r29,r3<BR>&nbsp; 24:&nbsp;7c 9c 23 78=20
&nbsp;mr&nbsp;r28,r4<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
return=20
B(12345);<BR>&nbsp; 28:&nbsp;7f a3 eb 78 &nbsp;mr&nbsp;r3,r29<BR>&nbsp;=20
2c:&nbsp;38 80 30 39 &nbsp;li&nbsp;r4,12345<BR>&nbsp; 30:&nbsp;48 00 00 =
01=20
&nbsp;bl&nbsp;30 &lt;C::operator =
B(void)+0x30&gt;<BR>&nbsp;&nbsp;&nbsp;30:=20
R_PPC_REL24&nbsp;B::B(int)<BR>&nbsp; 34:&nbsp;7c 60 1b 78=20
&nbsp;mr&nbsp;r0,r3<BR>&nbsp; 38:&nbsp;48 00 00 0c &nbsp;b&nbsp;44=20
&lt;C::operator B(void)+0x44&gt;<BR>&nbsp; 3c:&nbsp;48 00 00 08 =
&nbsp;b&nbsp;44=20
&lt;C::operator B(void)+0x44&gt;<BR>&nbsp; 40:&nbsp;48 00 00 04 =
&nbsp;b&nbsp;44=20
&lt;C::operator B(void)+0x44&gt;<BR>&nbsp;&nbsp;&nbsp; }<BR>&nbsp; =
44:&nbsp;7f=20
a3 eb 78 &nbsp;mr&nbsp;r3,r29<BR>&nbsp; 48:&nbsp;81 61 00 00=20
&nbsp;lwz&nbsp;r11,0(r1)<BR>&nbsp; 4c:&nbsp;80 0b 00 04=20
&nbsp;lwz&nbsp;r0,4(r11)<BR>&nbsp; 50:&nbsp;7c 08 03 a6=20
&nbsp;mtlr&nbsp;r0<BR>&nbsp; 54:&nbsp;83 8b ff f0=20
&nbsp;lwz&nbsp;r28,-16(r11)<BR>&nbsp; 58:&nbsp;83 ab ff f4=20
&nbsp;lwz&nbsp;r29,-12(r11)<BR>&nbsp; 5c:&nbsp;83 cb ff f8=20
&nbsp;lwz&nbsp;r30,-8(r11)<BR>&nbsp; 60:&nbsp;83 eb ff fc=20
&nbsp;lwz&nbsp;r31,-4(r11)<BR>&nbsp; 64:&nbsp;7d 61 5b 78=20
&nbsp;mr&nbsp;r1,r11<BR>&nbsp; 68:&nbsp;4e 80 00 20=20
&nbsp;blr<BR></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>This =
code should=20
have been generated for the explicit copy constructor case because as =
you can=20
see there is no mention of B::B(B&amp;)&nbsp; here!</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>I =
think it is a=20
definite bug.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002>&nbsp;</DIV></SPAN></FONT>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>I have =
tried=20
commenting out the conversion operator B::operator A() and the =
conversion=20
constructor B::B(A) one at a time, the compiler then generates the error =

messages shown below.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002>Change#1:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002>//&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
B::B(A&nbsp; init);<BR></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002>result#1:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>MiscTest.cpp: In=20
method `C::operator B()':<BR>MiscTest.cpp:29: no matching function for =
call to=20
`B::B (B)'<BR>MiscTest.cpp:11: candidates are: =
B::B(int)<BR></DIV></SPAN></FONT>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002>change#2:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002>//&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
B::operator A();<BR></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002>resullt#2:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>MiscTest.cpp: In=20
method `C::operator B()':<BR>MiscTest.cpp:29: no matching function for =
call to=20
`B::B (B)'<BR>MiscTest.cpp:11: candidates are:=20
B::B(int)<BR>MiscTest.cpp:14:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
B::B(A)<BR></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553084001-10122002>I am a =
newbie to gcc=20
innards, so I may be way off the mark. Sorry&nbsp;I don't have more =
details yet,=20
I just ran into this problem last friday.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553084001-10122002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553084001-10122002>VisualC++ however=20
does not display this behaviour and generates correct =
code.</SPAN></FONT></DIV>
<P><FONT face=3D"Comic Sans MS" size=3D2>Regards,</FONT> </P>
<P><FONT face=3D"Comic Sans MS" size=3D2>Lakhbir Gandhi</FONT> <BR><FONT =

face=3D"Comic Sans MS" size=3D2>Consulting Engineer</FONT> <BR><FONT=20
face=3D"Comic Sans MS" size=3D2>lgandhi@peerless.com</FONT> <BR><FONT=20
face=3D"Comic Sans MS" size=3D2>253-395-8890 x13.</FONT> </P>
<DIV>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C29FFB.D7563DC8--


From adani@primposta.com Mon Dec 09 03:03:41 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18LItB-0001u2-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 03:03:41 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18LIt7-0001q5-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 03:03:40 -0500
Received: from heat.prim.hu ([195.228.75.76])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18LIt7-0001cl-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 03:03:37 -0500
Received: from armada.prim.hu [195.228.75.74] 
	by heat.prim.hu with esmtp (Exim 3.32 #1 (Debian))
	id 18LIpR-0001bo-00
	for <bug-commoncpp@gnu.org>; Mon, 09 Dec 2002 08:59:49 +0100
Received: from www-data by armada.prim.hu with local (Exim 3.34 #1 (Debian))
	id 18LIsO-0002MI-00
	for <bug-commoncpp@gnu.org>; Mon, 09 Dec 2002 09:02:52 +0100
From: "dani attila" <adani@primposta.com>
To: bug-commoncpp@gnu.org
Errors-To: adani@primposta.com
X-Sender: adani@primposta.com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 8bit
X-Mailer: PrimPosta
Sender: adani@primposta.com
Message-Id: <E18LIsO-0002MI-00@armada.prim.hu>
Date: Mon, 09 Dec 2002 09:02:52 +0100
X-Mailman-Approved-At: Tue, 10 Dec 2002 08:39:47 -0500
Subject: non-blocking socket
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: dani attila <adani@primposta.com>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 09 Dec 2002 08:03:42 -0000

Hi,

I don't know if the following things are features or a bugs, so
I am sorry if I misunderstood something.
I wanted to use TCPStream (or tcpstream) in a non-blocking
mode, so I turned it on by stream.setCompletion(false). After
I found it difficult to recognize if the stream was still 
connected or an error happend. 
If the remote host closes the connection isActive() and 
isConnected() still say the stream is OK. Maybe the error() 
function should modify the state member variable in an error 
condition!
In the case of a reading from a non-blocking socket it can happen that
there is not as many bytes as I want to read. Then, getErrorNumber()
says errInput and stream.fail() = true. This ok but the result is
the same if the socket was closed. Maybe getErr...() should
return errNotConnected? Also, getErr..() should return errSuccess 
if a successful reading follows a bad one, becase now errid is 
never reseted.
The folowing modification in TCPStream::underflow() maybe would
solve the problem (same in readLine):

int TCPStream::underflow()
{
	......

	if(!gptr())
		return EOF;

	if(gptr() < egptr())
		return (unsigned char)*gptr();

	rlen = (gbuf + bufsize) - eback();
	if(Socket::state == STREAM)
		rlen = ::read(so, (char *)eback(), rlen);
	else if(timeout && !Socket::isPending(pendingInput, timeout))
	{
		clear(ios::failbit | rdstate());
		error(errTimeout);
		return EOF;
	}
	else
		rlen = ::recv(so, (char *)eback(), rlen, 0);
	if(rlen < 1)
	{
		if(rlen < 0)
		{
			clear(ios::failbit | rdstate());
			error(errInput);
		}
                //!
                else {
                        clear(ios::failbit | rdstate());
                        error(errNotConnected);
                }
                //!
		return EOF;
	}
        //!
        error(errSuccess);
        //!
	setg(eback(), eback(), eback() + rlen);
	return (unsigned char) *gptr();
}


regards,
Attila Dani

ps.: I can detect correctly if a socket is closed with
isPending() etc. , but maybe this would be more consistent 


From gernot@hillier.de Mon Dec 09 05:39:42 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18LLKA-000716-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 05:39:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18LLK8-00070S-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 05:39:41 -0500
Received: from mail08a.verio.de ([213.198.55.86])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18LLK7-00070F-00
	for bug-commoncpp@gnu.org; Mon, 09 Dec 2002 05:39:39 -0500
Received: from www.hillier.de (213.198.5.214)
	by mail08a.verio.de (RS ver 1.0.63s) with SMTP id 0108820219
	for <bug-commoncpp@gnu.org>; Mon,  9 Dec 2002 11:11:21 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by gernot.hillier.de (Postfix) with ESMTP id 1A64877767
	for <bug-commoncpp@gnu.org>; Mon,  9 Dec 2002 11:12:46 +0100 (CET)
Received: by gernot.hillier.de (Postfix, from userid 501)
	id DF60B776A7; Mon,  9 Dec 2002 11:12:44 +0100 (CET)
From: Gernot Hillier <gernot@hillier.de>
To: bug-commoncpp@gnu.org
Date: Mon, 9 Dec 2002 11:12:40 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="------------Boundary-00=_4DKUK8QHOH6BJCC47PXQ"
Message-Id: <200212091112.44257.gernot@hillier.de>
X-Virus-Scanned: by AMaViS 0.3.12pre8
X-Loop-Detect: 1
X-Mailman-Approved-At: Tue, 10 Dec 2002 08:39:47 -0500
Subject: Thread: memory leak when using not detached thread?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 09 Dec 2002 10:39:43 -0000


--------------Boundary-00=_4DKUK8QHOH6BJCC47PXQ
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

I'm no pthread guru, so perhaps I've misunderstood something. Please excu=
se=20
this ;-)

I narrowed my problem down to a very small test application. See attached=
=20
test.cpp file.

This program produces a memory leak - i.e. a finishing thread doesn't fre=
e its=20
resources.

I had a small look on the sources and the problem seems to be in=20
Thread::terminate():

        if(pthread_self() !=3D priv->_tid)
        {
                printf("grbml\n");
                // in suspend thread cannot be cancelled or signaled
                // ??? rigth
                // ccxx_resume(priv->_tid);

                // assure thread has ran before we try to cancel...
                if(_start)
                        _start->post();

                pthread_cancel(priv->_tid);
                pthread_join(priv->_tid,NULL);
        }

This doesn't get called as pthread_self() seems to be the same thread whi=
ch=20
deletes this. So pthread_join isn't called and the resources aren't freed=
=2E

Now I thought Thread::final() won't run in the same thread context as my =
new=20
thread? So why doesn't this work?

Do I have to use Thread::detach() instead of Thread::start() when I want =
to=20
"delete this"?=20

Could you elaborate on the cited glibc bug mentioned in the Thread::detac=
h()=20
docu? I asked a glibc developer and he told me that it's my fault if I do=
n't=20
run pthread_join - no glibc bug.

I've seeked the archives a  little bit but found no mail responding my=20
question. Sorry if this is a FAQ.

- --=20
Ciao,

Gernot
"Der Horizont vieler Menschen ist ein Kreis mit Radius Null - und das nen=
nen=20
sie ihren Standpunkt." (A. Einstein)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE99Gyak997/GGeSeIRAl21AJ9ZsCP5I7ucAtdTkrmRHWH2FRUaigCgjsYA
g7ujTDi4IQHkJpU3WTgm06c=3D
=3DNjMu
-----END PGP SIGNATURE-----

--------------Boundary-00=_4DKUK8QHOH6BJCC47PXQ
Content-Type: text/x-c++src;
  charset="us-ascii";
  name="test.cpp"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="test.cpp"

#include <iostream>
#include <cc++/thread.h>

using namespace std;

class A : public ost::Thread
{
	public:
		A(){}

		void run()
		{
			cout << "hi" << endl;
		}

		void final()
		{
			delete this;
		}
		
};

int main()
{
	while (true) {
		int a;
		cin >> a;
		(new A())->start();
	}
}

  

--------------Boundary-00=_4DKUK8QHOH6BJCC47PXQ--


From dyfet@ostel.com Tue Dec 10 08:50:11 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Lkm2-0004QI-00
	for bug-commoncpp@gnu.org; Tue, 10 Dec 2002 08:50:10 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Lkly-0004MX-00
	for bug-commoncpp@gnu.org; Tue, 10 Dec 2002 08:50:09 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Lkly-0004MG-00
	for bug-commoncpp@gnu.org; Tue, 10 Dec 2002 08:50:06 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gBAEJZj24442;
	Tue, 10 Dec 2002 09:19:35 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Tue, 10 Dec 2002 09:19:35 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Gernot Hillier <gernot@hillier.de>
In-Reply-To: <200212091112.44257.gernot@hillier.de>
Message-ID: <Pine.LNX.4.44.0212100917280.24421-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bug-commoncpp@gnu.org
Subject: Re: Thread: memory leak when using not detached thread?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 10 Dec 2002 13:50:13 -0000


A thread cannot delete it's own context or join itself.  To make a thread
that is a self running object that self-deletes, one has to detach the
thread.  However, there is very definately a known bug in at least some
glibc releases that when a detached thread exits, it will not clean up
it's stack frame allocations because that code only existed in the 
pthread_join implimentation, and, of course, one cannot self join...

On Mon, 9 Dec 2002, Gernot Hillier wrote:

> --[PinePGP]--------------------------------------------------[begin]--
> Hi!
> 
> I'm no pthread guru, so perhaps I've misunderstood something. Please excuse
> this ;-)
> 
> I narrowed my problem down to a very small test application. See attached
> test.cpp file.
> 
> This program produces a memory leak - i.e. a finishing thread doesn't free its
> resources.
> 
> I had a small look on the sources and the problem seems to be in
> Thread::terminate():
> 
>         if(pthread_self() != priv->_tid)
>         {
>                 printf("grbml\n");
>                 // in suspend thread cannot be cancelled or signaled
>                 // ??? rigth
>                 // ccxx_resume(priv->_tid);
> 
>                 // assure thread has ran before we try to cancel...
>                 if(_start)
>                         _start->post();
> 
>                 pthread_cancel(priv->_tid);
>                 pthread_join(priv->_tid,NULL);
>         }
> 
> This doesn't get called as pthread_self() seems to be the same thread which
> deletes this. So pthread_join isn't called and the resources aren't freed.
> 
> Now I thought Thread::final() won't run in the same thread context as my new
> thread? So why doesn't this work?
> 
> Do I have to use Thread::detach() instead of Thread::start() when I want to
> "delete this"?
> 
> Could you elaborate on the cited glibc bug mentioned in the Thread::detach()
> docu? I asked a glibc developer and he told me that it's my fault if I don't
> run pthread_join - no glibc bug.
> 
> I've seeked the archives a  little bit but found no mail responding my
> question. Sorry if this is a FAQ.
> 
> --
> Ciao,
> 
> Gernot
> "Der Horizont vieler Menschen ist ein Kreis mit Radius Null - und das nennen
> sie ihren Standpunkt." (A. Einstein)
> --[PinePGP]-----------------------------------------------------------
> gpg: Warning: using insecure memory!
> gpg: Signature made Mon 09 Dec 2002 05:12:42 AM EST using DSA key ID 619E49E2
> gpg: Can't check signature: public key not found
> PinePGP: Encryption backend encountered error.
> --[PinePGP]----------------------------------------------------[end]--
> 



From vass@virgosystems.hu Tue Dec 10 09:22:29 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18LlHJ-0000Iu-00
	for bug-commoncpp@gnu.org; Tue, 10 Dec 2002 09:22:29 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18LlHG-0000Hr-00
	for bug-commoncpp@gnu.org; Tue, 10 Dec 2002 09:22:28 -0500
Received: from www.wiw.hu ([195.228.254.53] helo=virgosystems.hu)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18LlHD-0000GQ-00
	for bug-commoncpp@gnu.org; Tue, 10 Dec 2002 09:22:24 -0500
Received: (qmail 18411 invoked by uid 64014); 10 Dec 2002 14:15:35 -0000
Received: from vass@virgosystems.hu by kozoslo by uid 64011 with
	qmail-scanner-1.12 (F-PROT: 3.12. Clear:. Processed in 0.271417 secs); 10 Dec
	2002 14:15:35 -0000
Received: from unknown (HELO marilyn) (10.0.0.200)
  by 192.168.131.1 with SMTP; 10 Dec 2002 14:15:34 -0000
Message-ID: <005f01c2a056$ab43e3e0$c800000a@marilyn>
From: "Vass Andras" <vass@virgosystems.hu>
To: "David Sugar" <dyfet@ostel.com>,
	"Gernot Hillier" <gernot@hillier.de>
References: <Pine.LNX.4.44.0212100917280.24421-100000@home.sys>
Date: Tue, 10 Dec 2002 15:16:00 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
cc: bug-commoncpp@gnu.org
Subject: Re: Thread: memory leak when using not detached thread?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 10 Dec 2002 14:22:30 -0000

Thread are created joinable by default - at least in commoncpp2-1.0.7.
>From the libc info pages:
"When a joinable thread terminates, its memory resources (thread
     descriptor and stack) are not deallocated until another thread
     performs `pthread_join' on it. Therefore, `pthread_join' must be
     called once for each joinable thread created to avoid memory leaks."
The problem can be solved if you detach the thread in the Thread::~Thread
destructor,
right before calling terminate (See below)

ps: has anynone taken a look at the bug report on savannah.gnu.org?

Thread::~Thread()
{
#ifdef WIN32
  terminate();

  if (isThread())
  {
    priv->_tid = 0;
    _self.setKey(DUMMY_INVALID_THREAD);
  }
  if (priv->_hThread) CloseHandle(priv->_hThread);
  if (priv->_cancellation) CloseHandle(priv->_cancellation);

#else
  detach();
  if(this != &_mainthread){
    terminate();
  }
#endif // WIN32
}

----- Original Message -----
From: "David Sugar" <dyfet@ostel.com>
To: "Gernot Hillier" <gernot@hillier.de>
Cc: <bug-commoncpp@gnu.org>
Sent: Tuesday, December 10, 2002 3:19 PM
Subject: Re: Thread: memory leak when using not detached thread?


>
> A thread cannot delete it's own context or join itself.  To make a thread
> that is a self running object that self-deletes, one has to detach the
> thread.  However, there is very definately a known bug in at least some
> glibc releases that when a detached thread exits, it will not clean up
> it's stack frame allocations because that code only existed in the
> pthread_join implimentation, and, of course, one cannot self join...
>
> On Mon, 9 Dec 2002, Gernot Hillier wrote:
>
> > --[PinePGP]--------------------------------------------------[begin]--
> > Hi!
> >
> > I'm no pthread guru, so perhaps I've misunderstood something. Please
excuse
> > this ;-)
> >
> > I narrowed my problem down to a very small test application. See
attached
> > test.cpp file.
> >
> > This program produces a memory leak - i.e. a finishing thread doesn't
free its
> > resources.
> >
> > I had a small look on the sources and the problem seems to be in
> > Thread::terminate():
> >
> >         if(pthread_self() != priv->_tid)
> >         {
> >                 printf("grbml\n");
> >                 // in suspend thread cannot be cancelled or signaled
> >                 // ??? rigth
> >                 // ccxx_resume(priv->_tid);
> >
> >                 // assure thread has ran before we try to cancel...
> >                 if(_start)
> >                         _start->post();
> >
> >                 pthread_cancel(priv->_tid);
> >                 pthread_join(priv->_tid,NULL);
> >         }
> >
> > This doesn't get called as pthread_self() seems to be the same thread
which
> > deletes this. So pthread_join isn't called and the resources aren't
freed.
> >
> > Now I thought Thread::final() won't run in the same thread context as my
new
> > thread? So why doesn't this work?
> >
> > Do I have to use Thread::detach() instead of Thread::start() when I want
to
> > "delete this"?
> >
> > Could you elaborate on the cited glibc bug mentioned in the
Thread::detach()
> > docu? I asked a glibc developer and he told me that it's my fault if I
don't
> > run pthread_join - no glibc bug.
> >
> > I've seeked the archives a  little bit but found no mail responding my
> > question. Sorry if this is a FAQ.
> >
> > --
> > Ciao,
> >
> > Gernot
> > "Der Horizont vieler Menschen ist ein Kreis mit Radius Null - und das
nennen
> > sie ihren Standpunkt." (A. Einstein)
> > --[PinePGP]-----------------------------------------------------------
> > gpg: Warning: using insecure memory!
> > gpg: Signature made Mon 09 Dec 2002 05:12:42 AM EST using DSA key ID
619E49E2
> > gpg: Can't check signature: public key not found
> > PinePGP: Encryption backend encountered error.
> > --[PinePGP]----------------------------------------------------[end]--
> >
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>



From dyfet@ostel.com Tue Dec 10 09:23:50 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18LlIc-0000ZU-00
	for bug-commoncpp@gnu.org; Tue, 10 Dec 2002 09:23:50 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18LlIY-0000Z3-00
	for bug-commoncpp@gnu.org; Tue, 10 Dec 2002 09:23:49 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18LlIY-0000Yt-00
	for bug-commoncpp@gnu.org; Tue, 10 Dec 2002 09:23:46 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gBAErDF24805;
	Tue, 10 Dec 2002 09:53:13 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Tue, 10 Dec 2002 09:53:13 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Vass Andras <vass@virgosystems.hu>
In-Reply-To: <005f01c2a056$ab43e3e0$c800000a@marilyn>
Message-ID: <Pine.LNX.4.44.0212100950510.24772-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bug-commoncpp@gnu.org
Subject: Re: Thread: memory leak when using not detached thread?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 10 Dec 2002 14:23:50 -0000


First, you should not detach in the destructor unless it is in it's own
context.  If anything, perhaps detach() vs terminate() should be called
depending on the circumstances, on whether it is being deleted by self or
by another thread, which, I think would be valid, otherwise, if another
thread calls detelete xxx, it will suddenly detach itself :).  Also, as
noted earlier, some glibc releases definately had a bug where a detached
thread that terminates never released resources, which is why I tended to
avoid them.

On Tue, 10 Dec 2002, Vass Andras wrote:

> Thread are created joinable by default - at least in commoncpp2-1.0.7.
> >From the libc info pages:
> "When a joinable thread terminates, its memory resources (thread
>      descriptor and stack) are not deallocated until another thread
>      performs `pthread_join' on it. Therefore, `pthread_join' must be
>      called once for each joinable thread created to avoid memory leaks."
> The problem can be solved if you detach the thread in the Thread::~Thread
> destructor,
> right before calling terminate (See below)
> 
> ps: has anynone taken a look at the bug report on savannah.gnu.org?
> 
> Thread::~Thread()
> {
> #ifdef WIN32
>   terminate();
> 
>   if (isThread())
>   {
>     priv->_tid = 0;
>     _self.setKey(DUMMY_INVALID_THREAD);
>   }
>   if (priv->_hThread) CloseHandle(priv->_hThread);
>   if (priv->_cancellation) CloseHandle(priv->_cancellation);
> 
> #else
>   detach();
>   if(this != &_mainthread){
>     terminate();
>   }
> #endif // WIN32
> }
> 
> ----- Original Message -----
> From: "David Sugar" <dyfet@ostel.com>
> To: "Gernot Hillier" <gernot@hillier.de>
> Cc: <bug-commoncpp@gnu.org>
> Sent: Tuesday, December 10, 2002 3:19 PM
> Subject: Re: Thread: memory leak when using not detached thread?
> 
> 
> >
> > A thread cannot delete it's own context or join itself.  To make a thread
> > that is a self running object that self-deletes, one has to detach the
> > thread.  However, there is very definately a known bug in at least some
> > glibc releases that when a detached thread exits, it will not clean up
> > it's stack frame allocations because that code only existed in the
> > pthread_join implimentation, and, of course, one cannot self join...
> >
> > On Mon, 9 Dec 2002, Gernot Hillier wrote:
> >
> > > --[PinePGP]--------------------------------------------------[begin]--
> > > Hi!
> > >
> > > I'm no pthread guru, so perhaps I've misunderstood something. Please
> excuse
> > > this ;-)
> > >
> > > I narrowed my problem down to a very small test application. See
> attached
> > > test.cpp file.
> > >
> > > This program produces a memory leak - i.e. a finishing thread doesn't
> free its
> > > resources.
> > >
> > > I had a small look on the sources and the problem seems to be in
> > > Thread::terminate():
> > >
> > >         if(pthread_self() != priv->_tid)
> > >         {
> > >                 printf("grbml\n");
> > >                 // in suspend thread cannot be cancelled or signaled
> > >                 // ??? rigth
> > >                 // ccxx_resume(priv->_tid);
> > >
> > >                 // assure thread has ran before we try to cancel...
> > >                 if(_start)
> > >                         _start->post();
> > >
> > >                 pthread_cancel(priv->_tid);
> > >                 pthread_join(priv->_tid,NULL);
> > >         }
> > >
> > > This doesn't get called as pthread_self() seems to be the same thread
> which
> > > deletes this. So pthread_join isn't called and the resources aren't
> freed.
> > >
> > > Now I thought Thread::final() won't run in the same thread context as my
> new
> > > thread? So why doesn't this work?
> > >
> > > Do I have to use Thread::detach() instead of Thread::start() when I want
> to
> > > "delete this"?
> > >
> > > Could you elaborate on the cited glibc bug mentioned in the
> Thread::detach()
> > > docu? I asked a glibc developer and he told me that it's my fault if I
> don't
> > > run pthread_join - no glibc bug.
> > >
> > > I've seeked the archives a  little bit but found no mail responding my
> > > question. Sorry if this is a FAQ.
> > >
> > > --
> > > Ciao,
> > >
> > > Gernot
> > > "Der Horizont vieler Menschen ist ein Kreis mit Radius Null - und das
> nennen
> > > sie ihren Standpunkt." (A. Einstein)
> > > --[PinePGP]-----------------------------------------------------------
> > > gpg: Warning: using insecure memory!
> > > gpg: Signature made Mon 09 Dec 2002 05:12:42 AM EST using DSA key ID
> 619E49E2
> > > gpg: Can't check signature: public key not found
> > > PinePGP: Encryption backend encountered error.
> > > --[PinePGP]----------------------------------------------------[end]--
> > >
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> >
> 
> 



From gernot@hillier.de Wed Dec 11 03:27:10 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18M2D0-00005F-00
	for bug-commoncpp@gnu.org; Wed, 11 Dec 2002 03:27:10 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18M2Cw-0008W1-00
	for bug-commoncpp@gnu.org; Wed, 11 Dec 2002 03:27:08 -0500
Received: from mail08b.verio.de ([213.198.55.87])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18M2Cv-0008V1-00
	for bug-commoncpp@gnu.org; Wed, 11 Dec 2002 03:27:06 -0500
Received: from www.hillier.de (213.198.5.214)
	by mail08b.verio.de (RS ver 1.0.63s) with SMTP id 0110685621;
	Wed, 11 Dec 2002 09:29:29 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by gernot.hillier.de (Postfix) with ESMTP
	id 06D3077B6C; Wed, 11 Dec 2002 09:26:53 +0100 (CET)
Received: by gernot.hillier.de (Postfix, from userid 501)
	id BEFA177B69; Wed, 11 Dec 2002 09:26:51 +0100 (CET)
From: Gernot Hillier <gernot@hillier.de>
To: David Sugar <dyfet@ostel.com>
Date: Wed, 11 Dec 2002 09:26:51 +0100
User-Agent: KMail/1.4.3
References: <Pine.LNX.4.44.0212100917280.24421-100000@home.sys>
In-Reply-To: <Pine.LNX.4.44.0212100917280.24421-100000@home.sys>
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="------------Boundary-00=_RS4Y7T13GQO04BZFU3U3"
Message-Id: <200212110926.51230.gernot@hillier.de>
X-Virus-Scanned: by AMaViS 0.3.12pre8
X-Loop-Detect: 1
cc: bug-commoncpp@gnu.org
Subject: Re: Thread: memory leak when using not detached thread?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 11 Dec 2002 08:27:11 -0000


--------------Boundary-00=_RS4Y7T13GQO04BZFU3U3
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi!

On Tuesday 10 December 2002 15:19, David Sugar wrote:
> A thread cannot delete it's own context or join itself.  To make a thre=
ad
> that is a self running object that self-deletes, one has to detach the
> thread. =20

Ok, hope I understood it now. Thx!

Could you add a comment like (slightly modified)

"Note: A thread cannot delete it's own context or join itself.  To make a=
=20
thread that is a self running object that self-deletes, one has to detach=
 the
thread by using detach() instead of run()."

to the explanation of=20

virtual void ost::Thread::final(void)?

Would be great and help others to avoid the pitfall I stepped in. Thx!

I prepared a small patch for this. See attachment.

> However, there is very definately a known bug in at least some
> glibc releases that when a detached thread exits, it will not clean up
> it's stack frame allocations because that code only existed in the
> pthread_join implimentation, and, of course, one cannot self join...

With using detach() instead of start() and "delete this" in final(), the=20
resources get deleted here. I use glibc-2.2.5 (SuSE package -164), so I t=
hink=20
it's fixed in the meanwhile.

--=20
Bye,

Gernot
"Der Horizont vieler Menschen ist ein Kreis mit Radius Null - und das nen=
nen=20
sie ihren Standpunkt." (A. Einstein)
--------------Boundary-00=_RS4Y7T13GQO04BZFU3U3
Content-Type: text/x-diff;
  charset="iso-8859-1";
  name="note.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="note.diff"

diff -u -3 -p -r1.15 thread.h
--- include/cc++/thread.h	5 Nov 2002 11:24:09 -0000	1.15
+++ include/cc++/thread.h	11 Dec 2002 08:25:54 -0000
@@ -1111,6 +1111,10 @@ protected:
 	 * 
 	 * You can safe delete thread ("delete this") class on final, but 
 	 * you should exit ASAP (or do not try to call CommonC++ methods...)
+	 *
+	 * NOTE: A thread cannot delete it's own context or join itself.  
+	 * To make a thread that is a self running object that self-deletes, 
+	 * one has to detach the thread by using detach() instead of start().
 	 * 
 	 * @see #exit
 	 * @see #run

--------------Boundary-00=_RS4Y7T13GQO04BZFU3U3--


From vass@virgosystems.hu Wed Dec 11 05:04:54 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18M3jZ-0000oZ-00
	for bug-commoncpp@gnu.org; Wed, 11 Dec 2002 05:04:53 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18M3jW-0000nX-00
	for bug-commoncpp@gnu.org; Wed, 11 Dec 2002 05:04:52 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18M3bi-0006dn-00
	for bug-commoncpp@gnu.org; Wed, 11 Dec 2002 04:56:46 -0500
Received: from mx2.datanet.hu ([194.149.13.163])
	by gnudist.gnu.org with esmtp (Exim 4.10.13)
	id 18M306-000605-00
	for bug-commoncpp@gnu.org; Wed, 11 Dec 2002 04:17:54 -0500
Received: from busybox (nilus-1572.adsl.datanet.hu [195.56.94.48])
	by mx2.datanet.hu (DataNet) with SMTP
	id 9CB6D5AEA; Wed, 11 Dec 2002 10:17:51 +0100 (CET)
Message-ID: <001601c2a0f6$3e4d2f80$1600a8c0@busybox>
From: "Andras Vass" <vass@virgosystems.hu>
To: "Gernot Hillier" <gernot@hillier.de>,
	"David Sugar" <dyfet@ostel.com>
References: <Pine.LNX.4.44.0212100917280.24421-100000@home.sys>
	<200212110926.51230.gernot@hillier.de>
Date: Wed, 11 Dec 2002 10:18:18 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
cc: bug-commoncpp@gnu.org
Subject: Re: Thread: memory leak when using not detached thread?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 11 Dec 2002 10:04:54 -0000

If this holds true, tcpthread.cpp in the examples is incorrect, since every
myTCPSession is started as a joinable thread and deletes itself without
detaching first.
The same notice should be added to TCPSession::final().

Andras Vass

----- Original Message -----
From: "Gernot Hillier" <gernot@hillier.de>
To: "David Sugar" <dyfet@ostel.com>
Cc: <bug-commoncpp@gnu.org>
Sent: Wednesday, December 11, 2002 9:26 AM
Subject: Re: Thread: memory leak when using not detached thread?


Hi!

On Tuesday 10 December 2002 15:19, David Sugar wrote:
> A thread cannot delete it's own context or join itself.  To make a thread
> that is a self running object that self-deletes, one has to detach the
> thread.

Ok, hope I understood it now. Thx!

Could you add a comment like (slightly modified)

"Note: A thread cannot delete it's own context or join itself.  To make a
thread that is a self running object that self-deletes, one has to detach
the
thread by using detach() instead of run()."

to the explanation of

virtual void ost::Thread::final(void)?

Would be great and help others to avoid the pitfall I stepped in. Thx!

I prepared a small patch for this. See attachment.

> However, there is very definately a known bug in at least some
> glibc releases that when a detached thread exits, it will not clean up
> it's stack frame allocations because that code only existed in the
> pthread_join implimentation, and, of course, one cannot self join...

With using detach() instead of start() and "delete this" in final(), the
resources get deleted here. I use glibc-2.2.5 (SuSE package -164), so I
think
it's fixed in the meanwhile.

--
Bye,

Gernot
"Der Horizont vieler Menschen ist ein Kreis mit Radius Null - und das nennen
sie ihren Standpunkt." (A. Einstein)


----------------------------------------------------------------------------
----


> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>



From lakeshore_s@sina.com Thu Dec 12 04:12:24 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MPNy-0002Sc-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 04:12:02 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MPNZ-0001r2-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 04:11:41 -0500
Received: from [202.106.187.156] (helo=sina.com)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18MPNH-00088j-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 04:11:21 -0500
Received: (qmail 69297 invoked from network); 12 Dec 2002 08:48:27 -0000
Received: from unknown (HELO team2) (61.170.157.30)
  by 202.106.187.156 with SMTP; 12 Dec 2002 08:48:27 -0000
Message-ID: <000a01c2a1bc$251ce750$4f13a8c0@dvnchina.com>
From: "lake" <lakeshore_s@sina.com>
To: "bug- commoncpp" <bug-commoncpp@gnu.org>
Date: Thu, 12 Dec 2002 16:54:34 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C2A1FF.25CED6C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: Serious memory leaks with TCPSession class
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 09:12:24 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C2A1FF.25CED6C0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

hi all,

I'm using TCPSession in a multithread app under Redhat 7.1,
and found the class derived from TCPSession had the problem
of memory leak.so i made a test like below,it's modified from the
tcpthread.cpp in demo.

i'm using CommonCPP2-1.0.5,as you can see from the code,
in the main(),the program listens to a specified port 4096,
whenever a client attempts to connect to it,it creates a new =
myTCPSession class,
then the myTCPSession class accepts the connection,and sends sth. to the =
client
,print sth. in the screen and wait for 5 seconds to return from its =
run().

the result is:
----------------------------------
[root@xu test]# ./tcp
testing addr: 255.255.255.255:4096
binding for: (null):4096                    <----------a:    begin to =
listen to the port  4096
before create                                <----------b:    process =
the 1st client's connection
accepting from: team-2:2268
creating session client object
after create
enter thread 1
ending session                            <-----------c:    quit from =
the 1st myTCPSession object
before create                                <-----------d:    process =
the 2nd client's connection
accepting from: team-2:2310
creating session client object
after create
enter thread 2
ending session                            <------------e:    quit from =
the 2nd myTCPSession object
----------------------------------

the usage of memory acquired from top is:
----------------------------------
a:
  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 2798 root       9   0  1224 1224  1024 S     0.0  0.4   0:00 tcp
b:
  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 2798 root      15   0  1260 1260  1040 S     0.1  0.4   0:00 tcp
c:
  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 2798 root       9   0  1264 1264  1044 S     0.0  0.4   0:00 tcp
d:
  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 2798 root       9   0  1272 1272  1044 S     0.0  0.4   0:00 tcp
e:
  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 2798 root       9   0  1272 1272  1044 S     0.0  0.4   0:00 tcp
----------------------------------
The total amount of physical memory used by tcp continiously increased =
and it never
decreased!!
and then everytime the client connected to it,the RSS increased 8k,the =
amount is fixed!
i don't know whether it's a bug of TCPSession class,who can help me??? =
:(


the modified code is:
-------------------------------------8<----------------------------------=
--------------------

#include <cc++/socket.h>
#include <cstdlib>

#ifdef CCXX_NAMESPACES
using namespace std;
using namespace ost;
#endif

class myTCPSocket : public TCPSocket
{
protected:
 bool onAccept(const InetHostAddress &ia, tpport_t port);

public:
 myTCPSocket(InetAddress &ia);
};

class myTCPSession : public TCPSession
{
private:
 static Mutex mutex;
 void run(void);
 void final(void);

public:
 myTCPSession(TCPSocket &server);
 static volatile int count;
};

myTCPSocket::myTCPSocket(InetAddress &ia) : TCPSocket(ia, 4096) {};

bool myTCPSocket::onAccept(const InetHostAddress &ia, tpport_t port)
{
 cout << "accepting from: " << ia.getHostname() << ":" << port << endl;;
 return true;
}

volatile int myTCPSession::count =3D 0;

Mutex myTCPSession::mutex;

myTCPSession::myTCPSession(TCPSocket &server) :
TCPSession(server)
{
 cout << "creating session client object" << endl;
 mutex.enterMutex();
 ++count;
 mutex.leaveMutex();
 // unsetf(ios::binary);
}

void myTCPSession::run(void)
{
 InetAddress addr =3D getLocal();
 *tcp() << "welcome to " << addr.getHostname() << " from socket " << so =
<< endl;
 mutex.enterMutex();
 *tcp() << "called from thread " << count << endl;
 cout << "enter thread " << count << endl;
 mutex.leaveMutex();
 sleep(5000);
 *tcp() << "ending session" << endl;
 cout << "ending session" << endl;
}

void myTCPSession::final(void)
{
 delete this;
}

int main()
{
 myTCPSession *tcp;
 BroadcastAddress addr;
 addr =3D "255.255.255.255";
 cout << "testing addr: " << addr.getHostname() << ":" << 4096 << endl;
 addr =3D "*";
 cout << "binding for: " << addr.getHostname() << ":" << 4096 << endl;

 try
 {
  myTCPSocket server(addr);
 =20
  while(1)
  {

   if(server.isPendingConnection(1000))
   {
    cout << "before create" << endl;
    tcp =3D new myTCPSession(server);
    cout << "after create" << endl;
    tcp->start();
   }
  }
 }
 catch(Socket *socket)
 {
  tpport_t port;
  int err =3D socket->getErrorNumber();
  InetAddress saddr =3D (InetAddress)socket->getPeer(&port);
  cerr << "socket error " << saddr.getHostname() << ":" << port << " =3D =
" << err << endl;=20
  if(err =3D=3D Socket::errBindingFailed)
  {
   cerr << "bind failed; port busy" << endl;
   ::exit(-1);
  }
  else
   cerr << "client socket failed" << endl;
 }
 cout << "timeout after 30 seconds inactivity, exiting" << endl;
 return 0;
}

---------------------------------------------------->8-------------------=
-----------------------------------------------

------=_NextPart_000_0007_01C2A1FF.25CED6C0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>hi all,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I'm using TCPSession in a multithread =
app under=20
Redhat 7.1,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and found the class derived from =
TCPSession had the=20
problem</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>of memory leak.so i made a test like =
below,it's=20
modified from the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>tcpthread.cpp in demo.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>i'm using CommonCPP2-1.0.5,</FONT><FONT =
face=3DArial=20
size=3D2>as you can see from the code,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in the main(),the program listens to a =
specified=20
port 4096,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>whenever a&nbsp;client&nbsp;attempts to =
connect to=20
it,it creates a new myTCPSession class,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>then the myTCPSession class accepts the =

connection,and sends sth. to the client</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>,print sth. in the screen and wait for =
5 seconds to=20
return from its run().</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>the result is:</FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2>----------------------------------</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>[root@xu test]# ./tcp</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>testing addr: =
255.255.255.255:4096<BR>binding for:=20
(null):4096&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &lt;----------a:&nbsp;&nbsp;&nbsp; =
begin=20
to listen to the port&nbsp; 4096</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>before create&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &lt;----------b:&nbsp;&nbsp;&nbsp; =
process=20
the 1st client's connection<BR>accepting from: team-2:2268<BR>creating =
session=20
client object<BR>after create<BR>enter thread 1<BR>ending=20
session&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&lt;-----------c:&nbsp;&nbsp;&nbsp; quit from the 1st myTCPSession=20
object<BR>before create&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &lt;-----------d:&nbsp;&nbsp;&nbsp; process =
the&nbsp;2nd=20
client's connection<BR>accepting from: team-2:2310<BR>creating session =
client=20
object<BR>after create<BR>enter thread 2<BR>ending =
session&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&lt;------------e:&nbsp;&nbsp;&nbsp; quit=20
from the 2nd myTCPSession object</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial =
size=3D2>----------------------------------</FONT></DIV>
<DIV>&nbsp;</DIV></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the usage of memory acquired from top=20
is:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial =
size=3D2>----------------------------------</FONT></DIV>
<DIV>a:</DIV>
<DIV>&nbsp; PID USER&nbsp;&nbsp;&nbsp;&nbsp; PRI&nbsp; NI&nbsp; =
SIZE&nbsp; RSS=20
SHARE STAT %CPU %MEM&nbsp;&nbsp; TIME COMMAND<BR>&nbsp;2798=20
root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 9&nbsp;&nbsp; 0&nbsp; 1224 =
1224&nbsp;=20
1024 S&nbsp;&nbsp;&nbsp;&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp; 0:00 tcp</DIV>
<DIV>b:</DIV>
<DIV>&nbsp; PID USER&nbsp;&nbsp;&nbsp;&nbsp; PRI&nbsp; NI&nbsp; =
SIZE&nbsp; RSS=20
SHARE STAT %CPU %MEM&nbsp;&nbsp; TIME COMMAND<BR>&nbsp;2798=20
root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 15&nbsp;&nbsp; 0&nbsp; 1260 =
1260&nbsp; 1040=20
S&nbsp;&nbsp;&nbsp;&nbsp; 0.1&nbsp; 0.4&nbsp;&nbsp; 0:00 tcp</DIV>
<DIV>c:</DIV>
<DIV>&nbsp; PID USER&nbsp;&nbsp;&nbsp;&nbsp; PRI&nbsp; NI&nbsp; =
SIZE&nbsp; RSS=20
SHARE STAT %CPU %MEM&nbsp;&nbsp; TIME COMMAND<BR>&nbsp;2798=20
root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 9&nbsp;&nbsp; 0&nbsp; 1264 =
1264&nbsp;=20
1044 S&nbsp;&nbsp;&nbsp;&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp; 0:00 tcp</DIV>
<DIV>d:</DIV>
<DIV>&nbsp; PID USER&nbsp;&nbsp;&nbsp;&nbsp; PRI&nbsp; NI&nbsp; =
SIZE&nbsp; RSS=20
SHARE STAT %CPU %MEM&nbsp;&nbsp; TIME COMMAND<BR>&nbsp;2798=20
root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 9&nbsp;&nbsp; 0&nbsp; 1272 =
1272&nbsp;=20
1044 S&nbsp;&nbsp;&nbsp;&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp; 0:00 tcp</DIV>
<DIV>e:</DIV>
<DIV>&nbsp; PID USER&nbsp;&nbsp;&nbsp;&nbsp; PRI&nbsp; NI&nbsp; =
SIZE&nbsp; RSS=20
SHARE STAT %CPU %MEM&nbsp;&nbsp; TIME COMMAND<BR>&nbsp;2798=20
root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 9&nbsp;&nbsp; 0&nbsp; 1272 =
1272&nbsp;=20
1044 S&nbsp;&nbsp;&nbsp;&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp; 0:00 tcp</DIV>
<DIV>
<DIV><FONT face=3DArial=20
size=3D2>----------------------------------</FONT></DIV></DIV></FONT></DI=
V>
<DIV><FONT face=3DArial size=3D2>The total amount of physical memory =
used by tcp=20
continiously increased and it never</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>decreased!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and then everytime the client connected =
to it,the=20
RSS increased 8k,the amount is fixed!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>i don't know whether it's a bug of =
TCPSession=20
class,who can help me??? :(</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>the modified code is:</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>-------------------------------------8&lt;----------------------=
--------------------------------</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>#include =
&lt;cc++/socket.h&gt;<BR>#include=20
&lt;cstdlib&gt;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>#ifdef&nbsp;CCXX_NAMESPACES<BR>using =
namespace=20
std;<BR>using namespace ost;<BR>#endif</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>class myTCPSocket : public=20
TCPSocket<BR>{<BR>protected:<BR>&nbsp;bool onAccept(const =
InetHostAddress=20
&amp;ia, tpport_t port);</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>public:<BR>&nbsp;myTCPSocket(InetAddress=20
&amp;ia);<BR>};</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>class myTCPSession : public=20
TCPSession<BR>{<BR>private:<BR>&nbsp;static Mutex mutex;<BR>&nbsp;void=20
run(void);<BR>&nbsp;void final(void);</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>public:<BR>&nbsp;myTCPSession(TCPSocket =

&amp;server);<BR>&nbsp;static volatile int count;<BR>};</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>myTCPSocket::myTCPSocket(InetAddress =
&amp;ia) :=20
TCPSocket(ia, 4096) {};</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>bool myTCPSocket::onAccept(const =
InetHostAddress=20
&amp;ia, tpport_t port)<BR>{<BR>&nbsp;cout &lt;&lt; "accepting from: " =
&lt;&lt;=20
ia.getHostname() &lt;&lt; ":" &lt;&lt; port &lt;&lt; =
endl;;<BR>&nbsp;return=20
true;<BR>}</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>volatile int myTCPSession::count =3D =
0;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Mutex myTCPSession::mutex;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>myTCPSession::myTCPSession(TCPSocket =
&amp;server)=20
:<BR>TCPSession(server)<BR>{<BR>&nbsp;cout &lt;&lt; "creating session =
client=20
object" &lt;&lt;=20
endl;<BR>&nbsp;mutex.enterMutex();<BR>&nbsp;++count;<BR>&nbsp;mutex.leave=
Mutex();<BR>&nbsp;//=20
unsetf(ios::binary);<BR>}</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>void=20
myTCPSession::run(void)<BR>{<BR>&nbsp;InetAddress addr =3D=20
getLocal();<BR>&nbsp;*tcp() &lt;&lt; "welcome to " &lt;&lt; =
addr.getHostname()=20
&lt;&lt; " from socket " &lt;&lt; so &lt;&lt;=20
endl;<BR>&nbsp;mutex.enterMutex();<BR>&nbsp;*tcp() &lt;&lt; "called from =
thread=20
" &lt;&lt; count &lt;&lt; endl;<BR>&nbsp;cout &lt;&lt; "enter thread " =
&lt;&lt;=20
count &lt;&lt;=20
endl;<BR>&nbsp;mutex.leaveMutex();<BR>&nbsp;sleep(5000);<BR>&nbsp;*tcp() =

&lt;&lt; "ending session" &lt;&lt; endl;<BR>&nbsp;cout &lt;&lt; "ending =
session"=20
&lt;&lt; endl;<BR>}</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>void =
myTCPSession::final(void)<BR>{<BR>&nbsp;delete=20
this;<BR>}</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>int main()<BR>{<BR>&nbsp;myTCPSession=20
*tcp;<BR>&nbsp;BroadcastAddress addr;<BR>&nbsp;addr =3D=20
"255.255.255.255";<BR>&nbsp;cout &lt;&lt; "testing addr: " &lt;&lt;=20
addr.getHostname() &lt;&lt; ":" &lt;&lt; 4096 &lt;&lt; =
endl;<BR>&nbsp;addr =3D=20
"*";<BR>&nbsp;cout &lt;&lt; "binding for: " &lt;&lt; addr.getHostname() =
&lt;&lt;=20
":" &lt;&lt; 4096 &lt;&lt; endl;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>&nbsp;try<BR>&nbsp;{<BR>&nbsp;&nbsp;myTCPSocket=20
server(addr);<BR>&nbsp;&nbsp;<BR>&nbsp;&nbsp;while(1)<BR>&nbsp;&nbsp;{</F=
ONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;if(server.isPendingConnection(1000))<BR>&nbsp;=
&nbsp;&nbsp;{<BR>&nbsp;&nbsp;&nbsp;&nbsp;cout=20
&lt;&lt; "before create" &lt;&lt; endl;<BR>&nbsp;&nbsp;&nbsp;&nbsp;tcp =
=3D new=20
myTCPSession(server);<BR>&nbsp;&nbsp;&nbsp;&nbsp;cout &lt;&lt; "after =
create"=20
&lt;&lt;=20
endl;<BR>&nbsp;&nbsp;&nbsp;&nbsp;tcp-&gt;start();<BR>&nbsp;&nbsp;&nbsp;}<=
BR>&nbsp;&nbsp;}<BR>&nbsp;}<BR>&nbsp;catch(Socket=20
*socket)<BR>&nbsp;{<BR>&nbsp;&nbsp;tpport_t port;<BR>&nbsp;&nbsp;int err =
=3D=20
socket-&gt;getErrorNumber();<BR>&nbsp;&nbsp;InetAddress saddr =3D=20
(InetAddress)socket-&gt;getPeer(&amp;port);<BR>&nbsp;&nbsp;cerr &lt;&lt; =
"socket=20
error " &lt;&lt; saddr.getHostname() &lt;&lt; ":" &lt;&lt; port &lt;&lt; =
" =3D "=20
&lt;&lt; err &lt;&lt; endl; <BR>&nbsp;&nbsp;if(err =3D=3D=20
Socket::errBindingFailed)<BR>&nbsp;&nbsp;{<BR>&nbsp;&nbsp;&nbsp;cerr =
&lt;&lt;=20
"bind failed; port busy" &lt;&lt;=20
endl;<BR>&nbsp;&nbsp;&nbsp;::exit(-1);<BR>&nbsp;&nbsp;}<BR>&nbsp;&nbsp;el=
se<BR>&nbsp;&nbsp;&nbsp;cerr=20
&lt;&lt; "client socket failed" &lt;&lt; endl;<BR>&nbsp;}<BR>&nbsp;cout =
&lt;&lt;=20
"timeout after 30 seconds inactivity, exiting" &lt;&lt; =
endl;<BR>&nbsp;return=20
0;<BR>}</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>----------------------------------------------------&gt;8-------=
-----------------------------------------------------------</FONT></DIV><=
/BODY></HTML>

------=_NextPart_000_0007_01C2A1FF.25CED6C0--




From lakeshore_s@sina.com Thu Dec 12 04:14:02 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MPPu-00036h-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 04:14:02 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MPPr-00035q-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 04:14:01 -0500
Received: from [202.106.187.156] (helo=sina.com)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18MPPo-0002yf-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 04:13:57 -0500
Received: (qmail 3052 invoked from network); 12 Dec 2002 09:01:52 -0000
Received: from unknown (HELO team2) (61.170.157.30)
  by 202.106.187.156 with SMTP; 12 Dec 2002 09:01:52 -0000
Message-ID: <001901c2a1be$05155ee0$4f13a8c0@dvnchina.com>
From: "lake" <lakeshore_s@sina.com>
To: "bug- commoncpp" <bug-commoncpp@gnu.org>
Date: Thu, 12 Dec 2002 17:08:19 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0016_01C2A201.11839BE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: Serious memory leaks with TCPSession class(continued)
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 09:14:03 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0016_01C2A201.11839BE0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

hi all.

haha,just now i've read the article post by Andras Vass on yesterday :)
use the detach() to replace the start() under linux,then the problem i =
mentioned
before can be solved!=20

thank you, Vass,Gernot Hillier and David Sugar!!

best regards




------=_NextPart_000_0016_01C2A201.11839BE0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>hi all.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>haha,just now i've read the article =
post by <FONT=20
size=3D3>Andras Vass </FONT><FONT size=3D2>on yesterday =
:)</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2>use the detach() to replace the =
start()=20
under<FONT size=3D3> </FONT><FONT size=3D2>linux,then the problem i=20
mentioned</FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>before can be solved! </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>thank you, <FONT =
size=3D3>Vass</FONT>,<FONT=20
size=3D3>Gernot Hillier <FONT size=3D2>and</FONT> David =
Sugar</FONT>!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>best regards</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0016_01C2A201.11839BE0--




From dyfet@ostel.com Thu Dec 12 08:04:35 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MT0P-00052R-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 08:03:57 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MSyE-0003W8-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 08:01:43 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18MSv6-0002Qx-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 07:58:29 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gBCDS1a25410;
	Thu, 12 Dec 2002 08:28:03 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Thu, 12 Dec 2002 08:28:01 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: lake <lakeshore_s@sina.com>
In-Reply-To: <001901c2a1be$05155ee0$4f13a8c0@dvnchina.com>
Message-ID: <Pine.LNX.4.44.0212120827340.24146-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bug- commoncpp <bug-commoncpp@gnu.org>
Subject: Re: Serious memory leaks with TCPSession class(continued)
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 13:04:35 -0000


Yes, it seems best to replace start with detach in tcpthread.cpp in case 
it is used as a design model by others...

On Thu, 12 Dec 2002, lake wrote:

> hi all.
> 
> haha,just now i've read the article post by Andras Vass on yesterday :)
> use the detach() to replace the start() under linux,then the problem i mentioned
> before can be solved! 
> 
> thank you, Vass,Gernot Hillier and David Sugar!!
> 
> best regards
> 
> 
> 
> 



From dyfet@ostel.com Thu Dec 12 09:53:58 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MUis-0006Et-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 09:53:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MUel-0004gp-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 09:49:46 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18MUeG-000499-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 09:49:13 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gBCFIxh27231
	for <bug-commoncpp@gnu.org>; Thu, 12 Dec 2002 10:18:59 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Thu, 12 Dec 2002 10:18:59 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: bug-commoncpp@gnu.org
In-Reply-To: <E18MP4m-0007UG-00@sc8-sf-web1.sourceforge.net>
Message-ID: <Pine.LNX.4.44.0212121016590.27223-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [ cplusplus-Bugs-652548 ] Compilation of network.cpp fails
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 14:53:59 -0000


This seems to be the only item I have left holding up the 1.0.8 release.  
It does seem FreeBSD does not have a ifr_netmask in ifreq.

On Thu, 12 Dec 2002 noreply@sourceforge.net wrote:

> Bugs item #652548, was opened at 2002-12-12 09:52
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=101523&aid=652548&group_id=1523
> 
> Category: Bug Reporter
> Group: None
> Status: Open
> Resolution: None
> Priority: 5
> Submitted By: Norbert Koch (nkoch)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: Compilation of network.cpp fails
> 
> Initial Comment:
> Hello.
> I tried the latest cvs sources under FreeBSD 4.7.
> Compilation fails in network.cpp because
> the structure element ifr_netmask does not exist
> under FreeBSD. As I understand the kernel
> sources it should be replaced by ifr_addr.
> See the enclosed diff file. It compiles but
> I did not test so far if it works.
> 
> ----------------------------------------------------------------------
> 
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=101523&aid=652548&group_id=1523
> 



From cproch@seculogix.de Thu Dec 12 11:56:47 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MWdj-0005k9-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 11:56:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MWdc-0005eU-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 11:56:45 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18MWdc-0005eE-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 11:56:40 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP
	id 601F413AEF; Thu, 12 Dec 2002 16:56:07 +0100 (CET)
Content-Type: text/plain;
  charset="iso-8859-1"
From: "Prochnow, Christian" <cproch@seculogix.de>
To: bug-commoncpp@gnu.org
Date: Thu, 12 Dec 2002 17:56:37 +0100
User-Agent: KMail/1.4.3
References: <Pine.LNX.4.44.0212121016590.27223-100000@home.sys>
In-Reply-To: <Pine.LNX.4.44.0212121016590.27223-100000@home.sys>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212121756.37360.cproch@seculogix.de>
cc: dyfet@ostel.com
Subject: Re: [ cplusplus-Bugs-652548 ] Compilation of network.cpp fails
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: cproch@seculogix.de
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 16:56:47 -0000

Hi,

i'm the author of network.cpp - but i dont have access to a FreeBSD machi=
ne at=20
all :(. The solution sounds ok, cause all the ifreq-members are in an uni=
on=20
(except ifr_name) and the returned values depend on the SIO* ioctl call.
I will have a look on some BSD man pages on the net to clarify.

Regards,

Christian Prochnow


Am Donnerstag 12 Dezember 2002 16:18 schrieb David Sugar:
> This seems to be the only item I have left holding up the 1.0.8 release=
=2E
> It does seem FreeBSD does not have a ifr_netmask in ifreq.
>
> On Thu, 12 Dec 2002 noreply@sourceforge.net wrote:
> > Bugs item #652548, was opened at 2002-12-12 09:52
> > You can respond by visiting:
> > https://sourceforge.net/tracker/?func=3Ddetail&atid=3D101523&aid=3D65=
2548&group
> >_id=3D1523
> >
> > Category: Bug Reporter
> > Group: None
> > Status: Open
> > Resolution: None
> > Priority: 5
> > Submitted By: Norbert Koch (nkoch)
> > Assigned to: Nobody/Anonymous (nobody)
> > Summary: Compilation of network.cpp fails
> >
> > Initial Comment:
> > Hello.
> > I tried the latest cvs sources under FreeBSD 4.7.
> > Compilation fails in network.cpp because
> > the structure element ifr_netmask does not exist
> > under FreeBSD. As I understand the kernel
> > sources it should be replaced by ifr_addr.
> > See the enclosed diff file. It compiles but
> > I did not test so far if it works.
> >
> > ---------------------------------------------------------------------=
-
> >
> > You can respond by visiting:
> > https://sourceforge.net/tracker/?func=3Ddetail&atid=3D101523&aid=3D65=
2548&group
> >_id=3D1523
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From cyates@uidaho.edu Thu Dec 12 12:37:38 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MXHG-0004sZ-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 12:37:38 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MXDk-0003aA-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 12:34:03 -0500
Received: from maila.its.uidaho.edu ([129.101.155.252] helo=rain)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18MXCw-000337-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 12:33:10 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H7000GBWOR8AI@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 12 Dec 2002 09:33:08 -0800 (PST)
Date: Thu, 12 Dec 2002 09:33:08 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp@gnu.org
Message-id: <NBBBJJODBJBNJFNIDDCNGEIODDAA.cyates@uidaho.edu>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Subject: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 17:37:38 -0000

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



From cyates@uidaho.edu Thu Dec 12 12:45:57 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MXMl-0007N7-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 12:43:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MXL1-0006RK-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 12:41:32 -0500
Received: from maila.its.uidaho.edu ([129.101.155.252] helo=rain)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18MXIx-0005b6-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 12:39:23 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H7000GSRP1MAI@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 12 Dec 2002 09:39:22 -0800 (PST)
Date: Thu, 12 Dec 2002 09:39:22 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <NBBBJJODBJBNJFNIDDCNGEIODDAA.cyates@uidaho.edu>
To: bug-commoncpp@gnu.org
Message-id: <NBBBJJODBJBNJFNIDDCNOEIODDAA.cyates@uidaho.edu>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Subject: RE: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 17:45:57 -0000

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:cyates@uidaho.edu]
Sent: Thursday, December 12, 2002 9:33 AM
To: bug-commoncpp@gnu.org
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



From lizzy@soggytrousers.net Thu Dec 12 13:00:29 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MXdK-000770-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 13:00:26 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MXdB-0006mg-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 13:00:20 -0500
Received: from 66-190-65-189.ftwrth.tx.charter.com ([66.190.65.189]
	helo=liliwhite.renaissance.oasis)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18MXdA-0006hX-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 13:00:16 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1
	(Debian))	id 18MXcv-000425-00; Thu, 12 Dec 2002 12:00:01 -0600
To: Chad Yates <cyates@uidaho.edu>
References: <NBBBJJODBJBNJFNIDDCNGEIODDAA.cyates@uidaho.edu>
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 12 Dec 2002 12:00:00 -0600
In-Reply-To: Chad Yates's message of "Thu, 12 Dec 2002 09:33:08 -0800"
Message-ID: <87k7if3yov.fsf@liliwhite.renaissance.oasis>
Lines: 46
X-Mailer: Gnus v5.7/Emacs 20.7
Sender: Elizabeth Barham <lizzy@soggytrousers.net>
cc: bug-commoncpp@gnu.org
Subject: Re: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 18:00:29 -0000

Chad Yates <cyates@uidaho.edu> writes:

> 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.

Perhaps SHA64DigestHelper needs to be exported.

If you modify the beginning of digest.h so that it appears like this
(adding SHA64DigestHelper), do the warnings go away?

#ifdef WIN32
class CCXX_CLASS_EXPORT Digest;
class CCXX_CLASS_EXPORT ChecksumDigest;
class CCXX_CLASS_EXPORT CRC16Digest;
class CCXX_CLASS_EXPORT CRC32Digest;
class CCXX_CLASS_EXPORT MD5Digest;
class CCXX_CLASS_EXPORT SHA64DigestHelper; // new
class CCXX_CLASS_EXPORT SHA1Digest;
class CCXX_CLASS_EXPORT SHA256Digest;
#endif

Elizabeth


From cyates@uidaho.edu Thu Dec 12 13:38:23 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MYE1-0003G3-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 13:38:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MYDE-00024m-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 13:37:34 -0500
Received: from maila.its.uidaho.edu ([129.101.155.252] helo=rain)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18MYCV-0000ke-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 13:36:48 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H7000GJWRP9AI@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 12 Dec 2002 10:36:45 -0800 (PST)
Date: Thu, 12 Dec 2002 10:36:45 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <87k7if3yov.fsf@liliwhite.renaissance.oasis>
To: Elizabeth Barham <lizzy@soggytrousers.net>
Message-id: <NBBBJJODBJBNJFNIDDCNGEJADDAA.cyates@uidaho.edu>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
cc: bug-commoncpp@gnu.org
Subject: RE: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 18:38:24 -0000

looks like that solves 1 problem, but exposes others.  with your change I
get the following warnings (I've left out one that I mention a bit later):

sha.cpp
..\include\cc++/digest.h(382) : warning C4275: non dll-interface class
'ost::SHADigest<unsigned __int64,64>' used as base for dll-interface class
'ost::SHA64DigestHelper'
        ..\include\cc++/digest.h(382) : see declaration of
'SHA64DigestHelper'

..\include\cc++/digest.h(384) : warning C4251: 'h' : class
'ost::SHATumbler<unsigned __int32>' needs to have dll-interface to be used
by clients of class 'ost::SHA64DigestHelper'

..\include\cc++/digest.h(385) : warning C4251: 'a' : class
'ost::SHATumbler<unsigned __int32>' needs to have dll-interface to be used
by clients of class 'ost::SHA64DigestHelper'

since these are templated classes I tried to reference the template in the
export area like so:

class CCXX_CLASS_EXPORT SHADigest<unsigned __int64,64>; // new

but that gives the following errros:

sha.cpp
..\include\cc++/digest.h(72) : error C2143: syntax error : missing ';'
before '<'
..\include\cc++/digest.h(72) : error C2059: syntax error : '<'
..\include\cc++/digest.h(372) : error C2989: 'SHADigest' : template class
has already been defined as a non-template class
        ..\include\cc++/digest.h(72) : see declaration of 'SHADigest'
..\include\cc++/digest.h(384) : error C2143: syntax error : missing ','
before '<'
..\include\cc++/digest.h(384) : error C2059: syntax error : '<'
..\include\cc++/digest.h(384) : fatal error C1903: unable to recover from
previous error(s); stopping compilation

so I gather that you can't export templated classes?  Any Ideas?

now about the warning I left out above. Following your lead, the final
warning on ost::SHAConstant (from the first batch) can be eliminated with a
another line added to the same WIN32 section:

> ..\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'

#ifdef WIN32
class CCXX_CLASS_EXPORT Digest;
class CCXX_CLASS_EXPORT ChecksumDigest;
class CCXX_CLASS_EXPORT CRC16Digest;
class CCXX_CLASS_EXPORT CRC32Digest;
class CCXX_CLASS_EXPORT MD5Digest;
class CCXX_CLASS_EXPORT SHA64DigestHelper; // new
class CCXX_CLASS_EXPORT SHAConstant; // even newer
class CCXX_CLASS_EXPORT SHA1Digest;
class CCXX_CLASS_EXPORT SHA256Digest;
#endif


-----Original Message-----
From: bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org
[mailto:bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org]On Behalf Of
Elizabeth Barham
Sent: Thursday, December 12, 2002 10:00 AM
To: Chad Yates
Cc: bug-commoncpp@gnu.org
Subject: Re: sha.cpp compiler warnings


Chad Yates <cyates@uidaho.edu> writes:

> 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.

Perhaps SHA64DigestHelper needs to be exported.

If you modify the beginning of digest.h so that it appears like this
(adding SHA64DigestHelper), do the warnings go away?

#ifdef WIN32
class CCXX_CLASS_EXPORT Digest;
class CCXX_CLASS_EXPORT ChecksumDigest;
class CCXX_CLASS_EXPORT CRC16Digest;
class CCXX_CLASS_EXPORT CRC32Digest;
class CCXX_CLASS_EXPORT MD5Digest;
class CCXX_CLASS_EXPORT SHA64DigestHelper; // new
class CCXX_CLASS_EXPORT SHA1Digest;
class CCXX_CLASS_EXPORT SHA256Digest;
#endif

Elizabeth


_______________________________________________
Bug-commoncpp mailing list
Bug-commoncpp@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From lizzy@soggytrousers.net Thu Dec 12 14:08:46 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MYhS-0001yL-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 14:08:46 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MYdA-0000TE-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 14:04:22 -0500
Received: from 66-190-65-189.ftwrth.tx.charter.com ([66.190.65.189]
	helo=liliwhite.renaissance.oasis)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18MYYm-0007Rg-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 13:59:48 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1
	(Debian))	id 18MYYi-0005e6-00; Thu, 12 Dec 2002 12:59:44 -0600
To: Chad Yates <cyates@uidaho.edu>
References: <NBBBJJODBJBNJFNIDDCNGEJADDAA.cyates@uidaho.edu>
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 12 Dec 2002 12:59:44 -0600
In-Reply-To: Chad Yates's message of "Thu, 12 Dec 2002 10:36:45 -0800"
Message-ID: <87bs3r3vxb.fsf@liliwhite.renaissance.oasis>
Lines: 79
X-Mailer: Gnus v5.7/Emacs 20.7
Sender: Elizabeth Barham <lizzy@soggytrousers.net>
cc: bug-commoncpp@gnu.org
Subject: Re: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 19:08:47 -0000

Chad Yates <cyates@uidaho.edu> writes:

> ..\include\cc++/digest.h(384) : warning C4251: 'h' : class
> 'ost::SHATumbler<unsigned __int32>' needs to have dll-interface to be used
> by clients of class 'ost::SHA64DigestHelper'

   The thing here is that SHATumbler is not needed by clients of
SHA64DigestHelper. Originally, I was of the impression that only those
classes that needed to be used by the clients needed to be exported,
which are SHA1Digest and SHA256Digest.

> ..\include\cc++/digest.h(385) : warning C4251: 'a' : class
> 'ost::SHATumbler<unsigned __int32>' needs to have dll-interface to be used
> by clients of class 'ost::SHA64DigestHelper'

> so I gather that you can't export templated classes?  Any Ideas?
> 
> now about the warning I left out above. Following your lead, the final
> warning on ost::SHAConstant (from the first batch) can be eliminated with a
> another line added to the same WIN32 section:
> 
> > ..\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'
> 
> #ifdef WIN32
> class CCXX_CLASS_EXPORT Digest;
> class CCXX_CLASS_EXPORT ChecksumDigest;
> class CCXX_CLASS_EXPORT CRC16Digest;
> class CCXX_CLASS_EXPORT CRC32Digest;
> class CCXX_CLASS_EXPORT MD5Digest;
> class CCXX_CLASS_EXPORT SHA64DigestHelper; // new
> class CCXX_CLASS_EXPORT SHAConstant; // even newer
> class CCXX_CLASS_EXPORT SHA1Digest;
> class CCXX_CLASS_EXPORT SHA256Digest;
> #endif


   If you build the library with it the way it was originally, that
is, with the warnings and all, and only SHA1Digest and SHA256Digest
defined as CCXX_CLASS_EXPORT, does it work?

   To find out, you can write a simple program that, for instance,
provides the SHA256 hash of a file:

#include <cc++/digest.h>
#include <cstdio>

#define BUFF_SIZE 1024

int main(int argc, char * argv[])
{
	unsigned char buff[1024];
	ost::SHA256Digest d256;
	unsigned length;

	for(int i = 1 ; i < argc; i++) {
		FILE * fp = fopen(argv[i], "rb");
		d256.initDigest();

		if(fp) {
			while(length = 
			      fread(buff, sizeof(unsigned char), BUFF_SIZE, fp)) {
				d256.putDigest(buff, length);
			}
			
			std::cout << d256 << "  " << argv[i] << std::endl;
			
			fclose(fp);
		}
	}
}

Does it work (never mind the exact result at the moment; does it
compile and run)?

Elizabeth



From cyates@uidaho.edu Thu Dec 12 17:44:36 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Mc4F-0008JN-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 17:44:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Mc3q-0007u9-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 17:44:10 -0500
Received: from mailb.its.uidaho.edu ([129.101.155.251] helo=snow)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Mc2z-0007Eb-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 17:43:13 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H7100K1Z33W9J@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 12 Dec 2002 14:43:09 -0800 (PST)
Date: Thu, 12 Dec 2002 14:43:09 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <87bs3r3vxb.fsf@liliwhite.renaissance.oasis>
To: Elizabeth Barham <lizzy@soggytrousers.net>
Message-id: <NBBBJJODBJBNJFNIDDCNKEJDDDAA.cyates@uidaho.edu>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
cc: bug-commoncpp@gnu.org
Subject: RE: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 22:44:39 -0000

(snip)
>    If you build the library with it the way it was originally, that
> is, with the warnings and all, and only SHA1Digest and SHA256Digest
> defined as CCXX_CLASS_EXPORT, does it work?
>
>    To find out, you can write a simple program that, for instance,
> provides the SHA256 hash of a file:
>
(snip)
>
> Does it work (never mind the exact result at the moment; does it
> compile and run)?
>
> Elizabeth
>

compiling the original library without our header mods, I get the three
warnings again of course, and a link error that the test program you
provided:

--------------------Configuration: digesttest - Win32
Debug--------------------
Compiling...
digesttest.cpp
e:\projects\c\commoncpp2\include\cc++\digest.h(414) : warning C4275: non
dll-interface class 'ost::SHA64DigestHelper' used as base for dll-interface
class 'ost::SHA1Digest'
        e:\projects\c\commoncpp2\include\cc++\digest.h(389) : see
declaration of 'SHA64DigestHelper'
e:\projects\c\commoncpp2\include\cc++\digest.h(432) : warning C4275: non
dll-interface class 'ost::SHA64DigestHelper' used as base for dll-interface
class 'ost::SHA256Digest'
        e:\projects\c\commoncpp2\include\cc++\digest.h(389) : see
declaration of 'SHA64DigestHelper'
e:\projects\c\commoncpp2\include\cc++\digest.h(432) : warning C4275: non
dll-interface class 'ost::SHAConstant' used as base for dll-interface class
'ost::SHA256Digest'
        e:\projects\c\commoncpp2\include\cc++\digest.h(328) : see
declaration of 'SHAConstant'
Linking...
digesttest.obj : error LNK2001: unresolved external symbol "public: virtual
void __thiscall ost::SHADigest<unsigned __int64,64>::putDigest(unsigned char
const *,unsigned int)" (?putDigest@?$SHADigest@_K$0EA@@ost@@UAEXPBEI@Z)
Debug/digesttest.exe : fatal error LNK1120: 1 unresolved externals
Error executing link.exe.

digesttest.exe - 2 error(s), 3 warning(s)

looks like the unresolved external relates to one of the warnings generated
after we added SHA64DigestHelper and SHAConstant to the dll export.

..\include\cc++/digest.h(382) : warning C4275: non dll-interface class
'ost::SHADigest<unsigned __int64,64>' used as base for dll-interface class
'ost::SHA64DigestHelper'
        ..\include\cc++/digest.h(382) : see declaration of
'SHA64DigestHelper'

what's so special about SHADigest<unsigned __int64,64>

,Chad



From cyates@uidaho.edu Thu Dec 12 17:48:04 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Mc6X-0003IP-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 17:46:53 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Mc62-0001qj-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 17:46:25 -0500
Received: from maila.its.uidaho.edu ([129.101.155.252] helo=rain)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Mc5D-000129-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 17:45:31 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H7100BN937T7O@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 12 Dec 2002 14:45:30 -0800 (PST)
Date: Thu, 12 Dec 2002 14:45:29 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <87bs3r3vxb.fsf@liliwhite.renaissance.oasis>
To: Elizabeth Barham <lizzy@soggytrousers.net>
Message-id: <NBBBJJODBJBNJFNIDDCNOEJDDDAA.cyates@uidaho.edu>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
cc: bug-commoncpp@gnu.org
Subject: RE: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 12 Dec 2002 22:48:05 -0000



> > ..\include\cc++/digest.h(384) : warning C4251: 'h' : class
> > 'ost::SHATumbler<unsigned __int32>' needs to have dll-interface
> to be used
> > by clients of class 'ost::SHA64DigestHelper'
>
>    The thing here is that SHATumbler is not needed by clients of
> SHA64DigestHelper. Originally, I was of the impression that only those
> classes that needed to be used by the clients needed to be exported,
> which are SHA1Digest and SHA256Digest.

I would think so too. perhaps the warning can be suppressed, but we'll have
to see what the soluation to the C4275 warnings and link error are first.

,chad



From lizzy@soggytrousers.net Thu Dec 12 19:08:35 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MdMG-0006my-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 19:07:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MdLj-0006Uo-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 19:06:43 -0500
Received: from 66-190-65-189.ftwrth.tx.charter.com ([66.190.65.189]
	helo=liliwhite.renaissance.oasis)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18MdJT-0005vW-00
	for bug-commoncpp@gnu.org; Thu, 12 Dec 2002 19:04:20 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1
	(Debian))	id 18MdJM-0005uK-00; Thu, 12 Dec 2002 18:04:12 -0600
To: Chad Yates <cyates@uidaho.edu>
References: <NBBBJJODBJBNJFNIDDCNKEJDDDAA.cyates@uidaho.edu>
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 12 Dec 2002 18:04:12 -0600
In-Reply-To: Chad Yates's message of "Thu, 12 Dec 2002 14:43:09 -0800"
Message-ID: <87pts63htv.fsf@liliwhite.renaissance.oasis>
Lines: 38
X-Mailer: Gnus v5.7/Emacs 20.7
Sender: Elizabeth Barham <lizzy@soggytrousers.net>
cc: bug-commoncpp@gnu.org
Subject: Re: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 13 Dec 2002 00:08:36 -0000

The answer may be provided here:

<http://216.239.53.100/search?q=cache:MtxlQUBvZr0C:www.experts-exchange.com/Programming/Programming_Languages/Cplusplus/Q_20263546.html+exporting+template+visual+c%2B%2B+dll&hl=en&ie=UTF-8>

According to the above, any template instances that are used need to
instantiated and dll'exported prior to use, a'la what you did earlier:

extern template class __declspec(dllexport) CBase<long>;
extern template class __declspec(dllexport) CArray<long>;

Perhaps instead of:

class CCXX_CLASS_EXPORT SHADigest<unsigned __int64,64>; // new

if we were to try:

extern template class CCXX_CLASS_EXPORT SHADigest<unsigned __int64,64>;

(or just "template class..."), assuming of course that
CCXX_CLASS_EXPORT expands to "__declspec(dllexport)", it may work.

> Linking...
> digesttest.obj : error LNK2001: unresolved external symbol "public: virtual
> void __thiscall ost::SHADigest<unsigned __int64,64>::putDigest(unsigned char
> const *,unsigned int)" (?putDigest@?$SHADigest@_K$0EA@@ost@@UAEXPBEI@Z)
> Debug/digesttest.exe : fatal error LNK1120: 1 unresolved externals
> Error executing link.exe.

This is similar to gcc in that gcc requires an instantiation of a
template if the template is defined in another file (or something like
that).

Anyway, perhaps by defining it as special with the "extern template"
directive it may work.

Thank you for all your help, btw.

Elizabeth


From cproch@seculogix.de Fri Dec 13 04:12:24 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Mlrp-0007rz-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 04:12:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Mlrd-0007Kt-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 04:12:13 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Mlrc-0007DE-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 04:12:08 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP
	id A3F6513AEF; Fri, 13 Dec 2002 09:11:28 +0100 (CET)
Content-Type: text/plain;
  charset="utf-8"
From: "Prochnow, Christian" <cproch@seculogix.de>
To: Elizabeth Barham <lizzy@soggytrousers.net>
Date: Fri, 13 Dec 2002 10:12:04 +0100
User-Agent: KMail/1.4.3
References: <NBBBJJODBJBNJFNIDDCNKEJDDDAA.cyates@uidaho.edu>
	<87pts63htv.fsf@liliwhite.renaissance.oasis>
In-Reply-To: <87pts63htv.fsf@liliwhite.renaissance.oasis>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212131012.04428.cproch@seculogix.de>
cc: bug-commoncpp@gnu.org
Subject: Re: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: cproch@seculogix.de
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 13 Dec 2002 09:12:27 -0000

Am Freitag 13 Dezember 2002 01:04 schrieb Elizabeth Barham:
> The answer may be provided here:
>
snip
>
> Perhaps instead of:
>
> class CCXX_CLASS_EXPORT SHADigest<unsigned __int64,64>; // new
>
> if we were to try:
>
> extern template class CCXX_CLASS_EXPORT SHADigest<unsigned __int64,64>;


you should add CCXX_CLASS_EXPORT in front of the template class declarati=
on:

template <class uint_type, unsigned blockSizeInBytes>
class CCXX_CLASS_EXPORT SHADigest {
         ^^^^^^^^^^^^^^^^^^^^^^^^

this works. tried it with VC 6 and VC.NET.
you don't need "extern template" declaration or something else.

Regards,=20
Christian Prochnow

>
> (or just "template class..."), assuming of course that
> CCXX_CLASS_EXPORT expands to "__declspec(dllexport)", it may work.
>
> > Linking...
> > digesttest.obj : error LNK2001: unresolved external symbol "public:
> > virtual void __thiscall ost::SHADigest<unsigned
> > __int64,64>::putDigest(unsigned char const *,unsigned int)"
> > (?putDigest@?$SHADigest@_K$0EA@@ost@@UAEXPBEI@Z) Debug/digesttest.exe=
 :
> > fatal error LNK1120: 1 unresolved externals Error executing link.exe.
>
> This is similar to gcc in that gcc requires an instantiation of a
> template if the template is defined in another file (or something like
> that).
>
> Anyway, perhaps by defining it as special with the "extern template"
> directive it may work.
>
> Thank you for all your help, btw.
>
> Elizabeth
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fedemp@bulbasaur.rediris.es Fri Dec 13 05:26:48 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Mn1s-0004zI-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 05:26:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Mn0e-0004Dx-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 05:25:33 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18MmyJ-0003b6-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 05:23:08 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18Mmxn-0000Yh-00; Fri, 13 Dec 2002 11:22:35 +0100
Date: Fri, 13 Dec 2002 11:22:35 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20021213102235.GA247@bulbasaur.rediris.es>
Mail-Followup-To: David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org,
	cplusplus-devel@lists.sourceforge.net
References: <KMEGIIBLMCKDDHMEHHABKEKBDAAA.ljohri@sbcglobal.net>
	<20021205201536.GA607@risitas> <200212061153.08945.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200212061153.08945.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
cc: cplusplus-devel@lists.sourceforge.net
Subject: Re: What is the licensing term for Common C++
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 13 Dec 2002 10:26:49 -0000


	I think it is alwo worth adding this commentary to the docs...

On Fri, Dec 06, 2002 at 11:53:08AM -0500, David Sugar wrote:
> It is probably worth commenting on this a bit further.  The one
> problem I recall immediately with the LGPL as it applies to C++
> class frameworks is the way it defines and refers to "linking" vs
> "derived works".  In concept, a C++
...


From fedemp@bulbasaur.rediris.es Fri Dec 13 05:31:13 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Mn5a-0000ZN-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 05:30:38 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Mn2x-0005s6-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 05:27:57 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Mn0D-00043R-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 05:25:05 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18Mmzz-0000ZK-00
	for <bug-commoncpp@gnu.org>; Fri, 13 Dec 2002 11:24:51 +0100
Date: Fri, 13 Dec 2002 11:24:51 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Message-ID: <20021213102451.GB247@bulbasaur.rediris.es>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <!~!AAAAACtOcTp7wTJEkIAsu8pFESKESyEA@bellsouth.net>
	<200212062335.53848.cproch@seculogix.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200212062335.53848.cproch@seculogix.de>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
Subject: Re: Few issues for ThreadFile.
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 13 Dec 2002 10:31:14 -0000


	So it seems it is possible to add this method in a portable
manner. Is there interest?

On Fri, Dec 06, 2002 at 11:35:53PM +0100, Prochnow, Christian wrote:
> Am Freitag 06 Dezember 2002 03:49 schrieb Leonard Thornton:
> > Sorry, but no ftruncate in win32.....closest would be
> > "open(....O_TRUNC)..."
> >
> 
> This is not true. 
> It can be emulated with  SetFilePointer() and SetEndOfFile() functions of the 
> win32 API.
> 
> Greetings,
> Christian Prochnow
> 
> 
> >
> > Leonard Thornton
> > Intelis, Inc
> > leonardt@intelis-inc.com
> >
> > +1 770.825.0032 x 203
> >
> >
> > -----Original Message-----
> > From: bug-commoncpp-admin@gnu.org [mailto:bug-commoncpp-admin@gnu.org] On
> > Behalf Of Skye Cove
> > Sent: Thursday, December 05, 2002 9:26 PM
> > To: bug-commoncpp@gnu.org
> > Subject: Re: Few issues for ThreadFile.
> >
> > On Thu, 2002-12-05 at 14:01, David Sugar wrote:
> > > I am not sure how widely portable ftruncate is,
> >
> > For what it's worth:
> >
> > Aaccording to `man ftruncate` (on a Linux 2.4.18 system): "4.4BSD, SVr4
> > (these function calls first appeared in BSD  4.2). POSIX 1003.1?$B!>1996  has
> > ftruncate. POSIX 1003.1?$B!>2001 also has truncate, as an XSI extension."
> >
> > I verified that it is also supported on FreeBSD 4.5, Solaris 8 and HP-UX 11
> > (though I didn't compile any tests).
> >
> > Does the win32 API offer anything similar?
> >
> > -sc
> >
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


From fedemp@bulbasaur.rediris.es Fri Dec 13 06:07:05 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Mner-00083p-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 06:07:05 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Mneo-00081u-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 06:07:03 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Mnc4-0005o0-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 06:04:12 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18Mnbj-0002EU-00; Fri, 13 Dec 2002 12:03:51 +0100
Date: Fri, 13 Dec 2002 12:03:51 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ari Johnson <ariston@cs.und.edu>
Message-ID: <20021213110351.GC247@bulbasaur.rediris.es>
Mail-Followup-To: Ari Johnson <ariston@cs.und.edu>, bug-commoncpp@gnu.org
References: <Pine.LNX.4.33.0212081059030.14458-200000@localhost.localdomain>
	<Pine.LNX.4.33.0212081936080.28595-100000@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.33.0212081936080.28595-100000@localhost.localdomain>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Autoconf check for XML support?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 13 Dec 2002 11:07:06 -0000


	It is in CVS. I have also added some documentation about it to
the manual.

On Sun, Dec 08, 2002 at 07:37:14PM -0600, Ari Johnson wrote:
> 
> I made a mistake in the patch, causing autoheader to fail on my system.
> In the AC_DEFINE() call, it should read:
>   AC_DEFINE(HAVE_OST_CCXX2_XML_PARSING, 1, [Define this if the CommonC++ library was compiled with XML parsing support])
> 
> On Sun, 8 Dec 2002, Ari Johnson wrote:
> 
> >
> > Attached please find a patch against src/ost_check2.m4 to add the
> > following check:
> >   OST_CCXX2_XML([ACTION-IF-TRUE[,ACTION-IF-FALSE]])
> >
> > On a side note, I've found that I have to set LIBS=-lgettextlib while
> > running a ./configure that calls OST_CCXX2_VERSION, because ccgnu2_config
> > doesn't include that library but it is required on my system for
> > getopt_long().
> >
> > Ari Johnson
> >
> > On Sat, 7 Dec 2002, Ari Johnson wrote:
> >
> > >
> > > I want to check for XML support at ./configure time of my project, but
> > > that won't be hard to set up a check for.  As to the incremental code,
> > > I've just been tracking the CVS version so I don't know what's in or out
> > > of the stable branch.  Thanks for confirming that it is.  I'll send a
> > > patch here if I get a chance to write the autoconf check.
> > >
> > > Ari Johnson
> > >
> > > On Sun, 8 Dec 2002, Federico Montesino Pouzols wrote:
> > >
> > > >
> > > > 	I have just checked that the incremental code in the stable
> > > > branch, does it fail somehow?
> > > >
> > > > 	As for the check for xml, COMMON_XML_PARSING is defined in
> > > > cc++/config.h if xml support is built in.
> > > >
> > > > On Sat, Dec 07, 2002 at 02:20:49PM -0500, David Sugar wrote:
> > > > > I thought the incremental XML parsing patch had made it into the current
> > > > > distributions.  Let me review that.  The cc++/config.h file provides
> > > > > compile time info on if xml support was built.  Perhaps you can create a
> > > > > simple macro which examines it.  I think having a OST_CCXX2_XML check
> > > > > might be a useful addition to ost_check2.m4.
> > > > >
> > > > > On Sat, 7 Dec 2002, Ari Johnson wrote:
> > > > >
> > > > > >
> > > > > > I see that there is an OST_CCXX2_DYNLOADER check among the autoconf macros
> > > > > > defined by ost_check2.m4, but no such way to determine if XML support is
> > > > > > built in.  I'm at the point in my project where I need to make the
> > > > > > decision to move to a more portable autoconf/automake build environment,
> > > > > > and that means that I'll need my configure script to check for an
> > > > > > appropriate version of CommonC++ as well as for built-in XML support.
> > > > > > As to incremental XML parsing, I'll just have to assume that people use
> > > > > > the CVS version until an incremented release number exists for the next
> > > > > > release, when I do OST_CCXX2_VERSION.
> > > > > >
> > > > > > Would it overclutter things to include an OST_CCXX2_XML check, or is there
> > > > > > perhaps a better way to accomplish this?  Thanks.
> > > > > >
> > > > > > Ari Johnson
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Bug-commoncpp mailing list
> > > > > > Bug-commoncpp@gnu.org
> > > > > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Bug-commoncpp mailing list
> > > > > Bug-commoncpp@gnu.org
> > > > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Bug-commoncpp mailing list
> > > Bug-commoncpp@gnu.org
> > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > >
> >
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


From fedemp@bulbasaur.rediris.es Fri Dec 13 06:16:46 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MnlO-0001go-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 06:13:50 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Mnko-0000Xw-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 06:13:18 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Mnkn-0000UA-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 06:13:13 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18MnkP-0002FD-00; Fri, 13 Dec 2002 12:12:49 +0100
Date: Fri, 13 Dec 2002 12:12:49 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: dani attila <adani@primposta.com>
Message-ID: <20021213111249.GE247@bulbasaur.rediris.es>
Mail-Followup-To: dani attila <adani@primposta.com>, bug-commoncpp@gnu.org
References: <E18LIsO-0002MI-00@armada.prim.hu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E18LIsO-0002MI-00@armada.prim.hu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: non-blocking socket
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 13 Dec 2002 11:16:50 -0000


	Yes, I think that replacing errInput with errNotConnected when
(rlen < 0) makes sense.

On Mon, Dec 09, 2002 at 09:02:52AM +0100, dani attila wrote:
> Hi,
> 
> I don't know if the following things are features or a bugs, so
> I am sorry if I misunderstood something.
> I wanted to use TCPStream (or tcpstream) in a non-blocking
> mode, so I turned it on by stream.setCompletion(false). After
> I found it difficult to recognize if the stream was still 
> connected or an error happend. 
> If the remote host closes the connection isActive() and 
> isConnected() still say the stream is OK. Maybe the error() 
> function should modify the state member variable in an error 
> condition!
> In the case of a reading from a non-blocking socket it can happen that
> there is not as many bytes as I want to read. Then, getErrorNumber()
> says errInput and stream.fail() = true. This ok but the result is
> the same if the socket was closed. Maybe getErr...() should
> return errNotConnected? Also, getErr..() should return errSuccess 
> if a successful reading follows a bad one, becase now errid is 
> never reseted.
> The folowing modification in TCPStream::underflow() maybe would
> solve the problem (same in readLine):
> 
> int TCPStream::underflow()
> {
> 	......
> 
> 	if(!gptr())
> 		return EOF;
> 
> 	if(gptr() < egptr())
> 		return (unsigned char)*gptr();
> 
> 	rlen = (gbuf + bufsize) - eback();
> 	if(Socket::state == STREAM)
> 		rlen = ::read(so, (char *)eback(), rlen);
> 	else if(timeout && !Socket::isPending(pendingInput, timeout))
> 	{
> 		clear(ios::failbit | rdstate());
> 		error(errTimeout);
> 		return EOF;
> 	}
> 	else
> 		rlen = ::recv(so, (char *)eback(), rlen, 0);
> 	if(rlen < 1)
> 	{
> 		if(rlen < 0)
> 		{
> 			clear(ios::failbit | rdstate());
> 			error(errInput);
> 		}
>                 //!
>                 else {
>                         clear(ios::failbit | rdstate());
>                         error(errNotConnected);
>                 }
>                 //!
> 		return EOF;
> 	}
>         //!
>         error(errSuccess);
>         //!
> 	setg(eback(), eback(), eback() + rlen);
> 	return (unsigned char) *gptr();
> }
> 
> 
> regards,
> Attila Dani
> 
> ps.: I can detect correctly if a socket is closed with
> isPending() etc. , but maybe this would be more consistent 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


From fedemp@bulbasaur.rediris.es Fri Dec 13 06:27:23 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Mny2-0003WK-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 06:26:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Mnxt-0003Gz-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 06:26:48 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Mnxe-0002pJ-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 06:26:30 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18MnxL-0002G4-00; Fri, 13 Dec 2002 12:26:11 +0100
Date: Fri, 13 Dec 2002 12:26:11 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Gernot Hillier <gernot@hillier.de>
Message-ID: <20021213112611.GF247@bulbasaur.rediris.es>
Mail-Followup-To: Gernot Hillier <gernot@hillier.de>,
	David Sugar <dyfet@ostel.com>, Andras Vass <vass@virgosystems.hu>,
	bug-commoncpp@gnu.org
References: <Pine.LNX.4.44.0212100917280.24421-100000@home.sys>
	<200212110926.51230.gernot@hillier.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200212110926.51230.gernot@hillier.de>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
cc: David Sugar <dyfet@ostel.com>
Subject: Re: Thread: memory leak when using not detached thread?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 13 Dec 2002 11:27:24 -0000

On Wed, Dec 11, 2002 at 09:26:51AM +0100, Gernot Hillier wrote:
> 
> Could you add a comment like (slightly modified)
> 
> "Note: A thread cannot delete it's own context or join itself.  To make a 
> thread that is a self running object that self-deletes, one has to detach the
> thread by using detach() instead of run()."
> 
> to the explanation of 
> 
> virtual void ost::Thread::final(void)?
> 

	It is in CVS. As suggested by Andras Vass, I have also added a
similar note to TCPSession::final.


From fedemp@bulbasaur.rediris.es Fri Dec 13 07:03:55 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18MoWZ-0005GN-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 07:02:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Mo6I-0007P2-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 06:35:28 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Mo5T-00076A-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 06:34:35 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18Mo5C-0002GL-00; Fri, 13 Dec 2002 12:34:18 +0100
Date: Fri, 13 Dec 2002 12:34:18 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Vass Andras <vass@virgosystems.hu>
Message-ID: <20021213113418.GG247@bulbasaur.rediris.es>
Mail-Followup-To: Vass Andras <vass@virgosystems.hu>, bug-commoncpp@gnu.org
References: <Pine.LNX.4.44.0212100917280.24421-100000@home.sys>
	<005f01c2a056$ab43e3e0$c800000a@marilyn>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <005f01c2a056$ab43e3e0$c800000a@marilyn>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Thread: memory leak when using not detached thread?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 13 Dec 2002 12:03:55 -0000

On Tue, Dec 10, 2002 at 03:16:00PM +0100, Vass Andras wrote:
> ps: has anynone taken a look at the bug report on savannah.gnu.org?
> 
	Does this problem disappear if you replace start with detach?


From lizzy@soggytrousers.net Fri Dec 13 08:19:06 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Mpic-0006xy-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 08:19:06 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Mpia-0006wt-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 08:19:05 -0500
Received: from 66-190-65-189.ftwrth.tx.charter.com ([66.190.65.189]
	helo=liliwhite.renaissance.oasis)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18Mpia-0006wh-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 08:19:04 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1
	(Debian))	id 18MpiN-0000YW-00; Fri, 13 Dec 2002 07:18:51 -0600
To: cproch@seculogix.de
References: <NBBBJJODBJBNJFNIDDCNKEJDDDAA.cyates@uidaho.edu>
	<87pts63htv.fsf@liliwhite.renaissance.oasis>
	<200212131012.04428.cproch@seculogix.de>
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 13 Dec 2002 07:18:51 -0600
In-Reply-To: "Prochnow, Christian"'s message of "Fri, 13 Dec 2002 10:12:04
	+0100"
Message-ID: <87k7ie2h1g.fsf@liliwhite.renaissance.oasis>
Lines: 3
X-Mailer: Gnus v5.7/Emacs 20.7
Sender: Elizabeth Barham <lizzy@soggytrousers.net>
cc: bug-commoncpp@gnu.org
Subject: Re: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 13 Dec 2002 13:19:07 -0000

Thank you Christian and Chad. The header file has been modified.

Elizabeth


From a2574@dis.ulpgc.es Fri Dec 13 08:40:44 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Mq3Y-0001e6-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 08:40:44 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Mq3U-0001V6-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 08:40:41 -0500
Received: from serdis.dis.ulpgc.es ([193.145.145.17])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Mq3T-00016w-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 08:40:39 -0500
Received: from siglo21.dis.ulpgc.es (IDENT:root@siglo21.dis.ulpgc.es
	[193.145.145.16])
	by serdis.dis.ulpgc.es (8.10.2/8.9.2) with ESMTP id gBDDo67275546
	for <bug-commoncpp@gnu.org>; Fri, 13 Dec 2002 13:50:07 GMT
Received: (from nobody@localhost)
	by siglo21.dis.ulpgc.es (8.11.6/8.9.3) id gBDEbdA20290;
	Fri, 13 Dec 2002 14:37:39 GMT
Date: Fri, 13 Dec 2002 14:37:39 GMT
Message-Id: <200212131437.gBDEbdA20290@siglo21.dis.ulpgc.es>
X-Authentication-Warning: siglo21.dis.ulpgc.es: nobody set sender to
	a2574@dis.ulpgc.es using -f
From: a2574@dis.ulpgc.es
To: bug-commoncpp@gnu.org
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP3 Imap webMail Program 2.0.11
Sender: a2574@dis.ulpgc.es
Subject: Problems with serial device
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: a2574@dis.ulpgc.es
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 13 Dec 2002 13:40:45 -0000

Hi!  I wrote a message a week ago cause I could use the ttystream()
class with exception handling. The program used to crash. I found the
solution (not actually a solution) I compiled my code with serial.cpp
and didnt link the whole library... This way it worked but I have more
problems now.

Im trying to communicate to a Laser device, This kind of device has not
an end of telegram packet so I have to use it by reading byte by byte. 

The problem is that when I set a Timeout it throws an Input error
whenever I try to read something.

This is the code: (I inerhit from ttystream for changing some staff)
---------------------------------------------------------

#ifndef _SERIAL_INTERFACE_H
#define _SERIAL_INTERFACE_H

#include<cc++/common.h>
#include<string>
#include<iostream>

class SerialInterface: public ost::ttystream{
 private:
 public:
  SerialInterface():ttystream(){
    this->setError(true);
    setPacketInput(1,1000);
  }

};


#endif  // _SERIAL_INTERFACE_H

-------------------------------------------------------
int main(){

unsigned char p;

SerialInterface *comm = new SerialInterafe(\"...\");

comm->setTimeout(10000);


*comm >> p;  // the program chrashes here with errInput (why??)
}


If I dont set the timeout it works right, but I need it for checking
whether the device is there. I guess this is the last chance... tyhe
library is not why I call a final release... since I downloaded the code
I have nothing but problems... If you could help me. I would be nice..

Thanks, Jose Fernandez


From cyates@uidaho.edu Fri Dec 13 13:57:51 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Mv0Q-0007qu-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 13:57:50 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18MupZ-000443-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 13:46:38 -0500
Received: from mailb.its.uidaho.edu ([129.101.155.251] helo=snow)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Munx-00038b-00
	for bug-commoncpp@gnu.org; Fri, 13 Dec 2002 13:44:57 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H72008LOMQE7T@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Fri, 13 Dec 2002 10:44:38 -0800 (PST)
Date: Fri, 13 Dec 2002 10:44:38 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <200212131012.04428.cproch@seculogix.de>
To: cproch@seculogix.de, Elizabeth Barham <lizzy@soggytrousers.net>
Message-id: <NBBBJJODBJBNJFNIDDCNKEJIDDAA.cyates@uidaho.edu>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
cc: bug-commoncpp@gnu.org
Subject: RE: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 13 Dec 2002 18:57:51 -0000

Chris wrote:
> you should add CCXX_CLASS_EXPORT in front of the template class 
> declaration:
> 
> template <class uint_type, unsigned blockSizeInBytes>
> class CCXX_CLASS_EXPORT SHADigest {
>          ^^^^^^^^^^^^^^^^^^^^^^^^
> 
> this works. tried it with VC 6 and VC.NET.
> you don't need "extern template" declaration or something else.
> 
> Regards, 
> Christian Prochnow

chris,

no offense, but did you "actually" try it on the sha digest class and the test program Elizabeth provided.  I've updated my source from cvs with the changes you mentioned, and still get the following when compiling/linking digest.cpp and the test program. Am I doing something wrong?

Compiling...
digest.cpp
e:\projects\c\commoncpp2\include\cc++\digest.h(383) : warning C4275: non dll-interface class 'ost::SHADigest<unsigned __int64,64>' used as base for dll-interface class 'ost::SHA64DigestHelper'
        e:\projects\c\commoncpp2\include\cc++\digest.h(383) : see declaration of 'SHA64DigestHelper'
e:\projects\c\commoncpp2\include\cc++\digest.h(385) : warning C4251: 'h' : class 'ost::SHATumbler<unsigned __int32>' needs to have dll-interface to be used by clients of class 'ost::SHA64DigestHelper'
e:\projects\c\commoncpp2\include\cc++\digest.h(386) : warning C4251: 'a' : class 'ost::SHATumbler<unsigned __int32>' needs to have dll-interface to be used by clients of class 'ost::SHA64DigestHelper'
Skipping... (no relevant changes detected)
md5.cpp
sha.cpp
Linking...
--------------------Configuration: digesttest - Win32 Debug--------------------
Compiling...
digesttest.cpp
e:\projects\c\commoncpp2\include\cc++\digest.h(385) : warning C4251: 'h' : class 'ost::SHATumbler<unsigned __int32>' needs to have dll-interface to be used by clients of class 'ost::SHA64DigestHelper'
e:\projects\c\commoncpp2\include\cc++\digest.h(386) : warning C4251: 'a' : class 'ost::SHATumbler<unsigned __int32>' needs to have dll-interface to be used by clients of class 'ost::SHA64DigestHelper'
Linking...
digesttest.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall ost::SHADigest<unsigned __int64,64>::putDigest(unsigned char const *,unsigned int)" (?putDigest@?$SHADigest@_K$0EA@@ost@@UAEXPBEI@Z)
Debug/digesttest.exe : fatal error LNK1120: 1 unresolved externals
Error executing link.exe.

???

I was able to get rid of all warnings (and subsequent warnings) last night (using the link Elizabeth provided as a starting place), but to do so I had to move the template class implementations into the class declaration itself in the .h file, and add dummy implementations for any abstract methods so the msvc++ could instantiate them explicitly for export.  I noticed that there are no other commoncpp2 classes like this (that use templates in this manner), perhaps they have been avoided for the reasons we are finding out.  if someone wants to look at the code, I can send it to them, but it's pretty ugly as it was a cut and paste marathon.  If I didn't get the link error, I would just say bag it, but the warnings seem to really be more than warnings.  maybe I'm just naive, but if I am I'd like to understand the problem/solution so I can use templated classes in a dll in the future and have it be cross-platform compatible.

Any thoughts?

,chad




From cproch@seculogix.de Sat Dec 14 11:35:54 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18NFGb-0000GA-00
	for bug-commoncpp@gnu.org; Sat, 14 Dec 2002 11:35:53 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18NFGY-00006w-00
	for bug-commoncpp@gnu.org; Sat, 14 Dec 2002 11:35:52 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18NFGX-0008S7-00
	for bug-commoncpp@gnu.org; Sat, 14 Dec 2002 11:35:50 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP
	id 61D5513A68; Sat, 14 Dec 2002 16:35:00 +0100 (CET)
Content-Type: text/plain;
  charset="utf-8"
From: "Prochnow, Christian" <cproch@seculogix.de>
To: Chad Yates <cyates@uidaho.edu>
Date: Sat, 14 Dec 2002 17:35:46 +0100
User-Agent: KMail/1.4.3
References: <NBBBJJODBJBNJFNIDDCNKEJIDDAA.cyates@uidaho.edu>
In-Reply-To: <NBBBJJODBJBNJFNIDDCNKEJIDDAA.cyates@uidaho.edu>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212141735.46715.cproch@seculogix.de>
cc: bug-commoncpp@gnu.org
Subject: Re: sha.cpp compiler warnings
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: cproch@seculogix.de
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 14 Dec 2002 16:35:54 -0000

Ok,

i missed to interpret a new warning that comes up :(
i also forget to mention two additional lines needed (after their class=20
declaration):

#ifdef WIN32
template class CCXX_CLASS_EXPORT SHADigest<uint64, 64>;
template class CCXX_CLASS_EXPORT SHATumbler<uint32>;
#endif

but adding this leads to more weird Warnings :(
They're all related to the template implementation that actually resides =
in =20
the .cpp file.=20
Seems that M$ compilers (tried it with VC 6 and VC.NET) does'nt like this=
=2E
I think simpliest and portable solution would be to move the template-cla=
ss=20
implementations into the header file.

Regards, Christian



Am Freitag 13 Dezember 2002 19:44 schrieben Sie:
> Chris wrote:
> > you should add CCXX_CLASS_EXPORT in front of the template class
> > declaration:
> >
> > template <class uint_type, unsigned blockSizeInBytes>
> > class CCXX_CLASS_EXPORT SHADigest {
> >          ^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > this works. tried it with VC 6 and VC.NET.
> > you don't need "extern template" declaration or something else.
> >
> > Regards,
> > Christian Prochnow
>
> chris,
>
> no offense, but did you "actually" try it on the sha digest class and t=
he
> test program Elizabeth provided.  I've updated my source from cvs with =
the
> changes you mentioned, and still get the following when compiling/linki=
ng
> digest.cpp and the test program. Am I doing something wrong?
>
> Compiling...
> digest.cpp
> e:\projects\c\commoncpp2\include\cc++\digest.h(383) : warning C4275: no=
n
> dll-interface class 'ost::SHADigest<unsigned __int64,64>' used as base =
for
> dll-interface class 'ost::SHA64DigestHelper'
> e:\projects\c\commoncpp2\include\cc++\digest.h(383) : see declaration o=
f
> 'SHA64DigestHelper' e:\projects\c\commoncpp2\include\cc++\digest.h(385)=
 :
> warning C4251: 'h' : class 'ost::SHATumbler<unsigned __int32>' needs to
> have dll-interface to be used by clients of class 'ost::SHA64DigestHelp=
er'
> e:\projects\c\commoncpp2\include\cc++\digest.h(386) : warning C4251: 'a=
' :
> class 'ost::SHATumbler<unsigned __int32>' needs to have dll-interface t=
o be
> used by clients of class 'ost::SHA64DigestHelper' Skipping... (no relev=
ant
> changes detected)
> md5.cpp
> sha.cpp
> Linking...
> --------------------Configuration: digesttest - Win32
> Debug-------------------- Compiling...
> digesttest.cpp
> e:\projects\c\commoncpp2\include\cc++\digest.h(385) : warning C4251: 'h=
' :
> class 'ost::SHATumbler<unsigned __int32>' needs to have dll-interface t=
o be
> used by clients of class 'ost::SHA64DigestHelper'
> e:\projects\c\commoncpp2\include\cc++\digest.h(386) : warning C4251: 'a=
' :
> class 'ost::SHATumbler<unsigned __int32>' needs to have dll-interface t=
o be
> used by clients of class 'ost::SHA64DigestHelper' Linking...
> digesttest.obj : error LNK2001: unresolved external symbol "public: vir=
tual
> void __thiscall ost::SHADigest<unsigned __int64,64>::putDigest(unsigned
> char const *,unsigned int)"
> (?putDigest@?$SHADigest@_K$0EA@@ost@@UAEXPBEI@Z) Debug/digesttest.exe :
> fatal error LNK1120: 1 unresolved externals Error executing link.exe.
>
> ???
>
> I was able to get rid of all warnings (and subsequent warnings) last ni=
ght
> (using the link Elizabeth provided as a starting place), but to do so I=
 had
> to move the template class implementations into the class declaration
> itself in the .h file, and add dummy implementations for any abstract
> methods so the msvc++ could instantiate them explicitly for export.  I
> noticed that there are no other commoncpp2 classes like this (that use
> templates in this manner), perhaps they have been avoided for the reaso=
ns
> we are finding out.  if someone wants to look at the code, I can send i=
t to
> them, but it's pretty ugly as it was a cut and paste marathon.  If I di=
dn't
> get the link error, I would just say bag it, but the warnings seem to
> really be more than warnings.  maybe I'm just naive, but if I am I'd li=
ke
> to understand the problem/solution so I can use templated classes in a =
dll
> in the future and have it be cross-platform compatible.
>
> Any thoughts?
>
> ,chad



From vass@virgosystems.hu Sat Dec 14 18:09:31 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18NLPQ-0007kf-00
	for bug-commoncpp@gnu.org; Sat, 14 Dec 2002 18:09:24 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18NLPN-0007eK-00
	for bug-commoncpp@gnu.org; Sat, 14 Dec 2002 18:09:22 -0500
Received: from mxpool.datanet.hu ([194.149.13.160] helo=mx3.datanet.hu)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18NLOs-0006vs-00
	for bug-commoncpp@gnu.org; Sat, 14 Dec 2002 18:08:50 -0500
Received: from busybox (nilus-2879.adsl.datanet.hu [195.56.227.85])
	by mx3.datanet.hu (DataNet) with SMTP
	id 6E12B1EA84A; Sun, 15 Dec 2002 00:08:47 +0100 (CET)
Message-ID: <004201c2a3c5$d3693f10$1600a8c0@busybox>
From: "Anrdas Vass" <vass@virgosystems.hu>
To: "Federico Montesino Pouzols" <fedemp@altern.org>
References: <Pine.LNX.4.44.0212100917280.24421-100000@home.sys>
	<005f01c2a056$ab43e3e0$c800000a@marilyn>
	<20021213113418.GG247@bulbasaur.rediris.es>
Date: Sun, 15 Dec 2002 00:09:16 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
cc: bug-commoncpp@gnu.org
Subject: Re: Thread: memory leak when using not detached thread?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 14 Dec 2002 23:09:32 -0000

Yes, but SIGSEGV remains....
A backtrace shows that calling pthread_detach() quickly after
pthread_create() /quickly means less than 10 ms/ dumps core in certain
cases. (glibc-2.2.5)
This small patch seems to help if detach() is called instead of start(). I
don't know what would be the Right Thing (tm) to do, if someone wants to
call detach() to detach a joinable thread.
Perhaps an ost::Thread::sleep(10) call before pthread_detach()?


Index: src/thread.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/thread.cpp,v
retrieving revision 1.19
diff -r1.19 thread.cpp
708,716c708,709
<   _start = start;
<   rtn = pthread_create(&priv->_tid, &priv->_attr,
exec_t(&ccxx_exec_handler), this);
<   if(!rtn && priv->_tid)
<   {
<     pthread_detach(priv->_tid);
<     return 0;
<   }
<   else
<     return -1;
---
>   pthread_attr_setdetachstate(&priv->_attr, PTHREAD_CREATE_DETACHED);
>   return this->start(start);

----- Original Message -----
From: "Federico Montesino Pouzols" <fedemp@altern.org>
To: "Vass Andras" <vass@virgosystems.hu>
Cc: <bug-commoncpp@gnu.org>
Sent: Friday, December 13, 2002 12:34 PM
Subject: Re: Thread: memory leak when using not detached thread?


> On Tue, Dec 10, 2002 at 03:16:00PM +0100, Vass Andras wrote:
> > ps: has anynone taken a look at the bug report on savannah.gnu.org?
> >
> Does this problem disappear if you replace start with detach?
>



From ariston@cs.und.edu Sun Dec 15 23:28:34 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Nmrq-00055X-00
	for bug-commoncpp@gnu.org; Sun, 15 Dec 2002 23:28:34 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Nmrn-00050r-00
	for bug-commoncpp@gnu.org; Sun, 15 Dec 2002 23:28:33 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Nmrn-0004s6-00
	for bug-commoncpp@gnu.org; Sun, 15 Dec 2002 23:28:31 -0500
Received: from penguin.cs.und.nodak.edu (penguin.cs.und.nodak.edu
	[134.129.212.25])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gBG4SGqf014267;
	Sun, 15 Dec 2002 22:28:21 -0600
Date: Sun, 15 Dec 2002 22:23:28 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
X-X-Sender: <ariston@localhost.localdomain>
To: "Prochnow, Christian" <cproch@seculogix.de>
In-Reply-To: <200212121756.37360.cproch@seculogix.de>
Message-ID: <Pine.LNX.4.33.0212152222030.9405-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bug-commoncpp@gnu.org
cc: dyfet@ostel.com
Subject: Re: [ cplusplus-Bugs-652548 ] Compilation of network.cpp fails
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 16 Dec 2002 04:28:35 -0000


I am running FreeBSD 4.7-STABLE and have no problem compiling network.cpp
at all, using the default installed version of gcc (2.95.4).  Of course, I
still can't compile almost any part of CommonC++ with gcc 3.x on FreeBSD,
but with 2.95.4 it goes just fine (I think I have all ./configure options
other than --with-piostreams enabled.).

Ari Johnson

On Thu, 12 Dec 2002, Prochnow, Christian wrote:

> Hi,
>
> i'm the author of network.cpp - but i dont have access to a FreeBSD machine at
> all :(. The solution sounds ok, cause all the ifreq-members are in an union
> (except ifr_name) and the returned values depend on the SIO* ioctl call.
> I will have a look on some BSD man pages on the net to clarify.
>
> Regards,
>
> Christian Prochnow
>
>
> Am Donnerstag 12 Dezember 2002 16:18 schrieb David Sugar:
> > This seems to be the only item I have left holding up the 1.0.8 release.
> > It does seem FreeBSD does not have a ifr_netmask in ifreq.
> >
> > On Thu, 12 Dec 2002 noreply@sourceforge.net wrote:
> > > Bugs item #652548, was opened at 2002-12-12 09:52
> > > You can respond by visiting:
> > > https://sourceforge.net/tracker/?func=detail&atid=101523&aid=652548&group
> > >_id=1523
> > >
> > > Category: Bug Reporter
> > > Group: None
> > > Status: Open
> > > Resolution: None
> > > Priority: 5
> > > Submitted By: Norbert Koch (nkoch)
> > > Assigned to: Nobody/Anonymous (nobody)
> > > Summary: Compilation of network.cpp fails
> > >
> > > Initial Comment:
> > > Hello.
> > > I tried the latest cvs sources under FreeBSD 4.7.
> > > Compilation fails in network.cpp because
> > > the structure element ifr_netmask does not exist
> > > under FreeBSD. As I understand the kernel
> > > sources it should be replaced by ifr_addr.
> > > See the enclosed diff file. It compiles but
> > > I did not test so far if it works.
> > >
> > > ----------------------------------------------------------------------
> > >
> > > You can respond by visiting:
> > > https://sourceforge.net/tracker/?func=detail&atid=101523&aid=652548&group
> > >_id=1523
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>



From mark@purcell.homeip.net Sun Dec 15 04:07:47 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18NUkV-0005EC-00
	for bug-commoncpp@gnu.org; Sun, 15 Dec 2002 04:07:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18NUkS-00059J-00
	for bug-commoncpp@gnu.org; Sun, 15 Dec 2002 04:07:46 -0500
Received: from cpe-203-51-32-155.nsw.bigpond.net.au ([203.51.32.155]
	helo=purcell.homeip.net)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18NUkR-0004s4-00
	for bug-commoncpp@gnu.org; Sun, 15 Dec 2002 04:07:44 -0500
Received: from [192.168.2.128] (helo=htpc.purcell.homeip.net ident=mail)
	by purcell.homeip.net with esmtp (Exim 3.35 #1 (Debian))
	id 18NUkJ-0003oN-00; Sun, 15 Dec 2002 20:07:35 +1100
Received: from msp by htpc.purcell.homeip.net with local (Exim 3.36 #1
	(Debian))	id 18NUkD-0002DL-00; Sun, 15 Dec 2002 20:07:29 +1100
Content-Type: text/plain;
  charset="us-ascii"
From: Mark Purcell <msp@debian.org>
To: bug-commoncpp@gnu.org
Date: Sun, 15 Dec 2002 20:07:19 +1100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200212152007.28784.msp@debian.org>
Sender: Mark Purcell <msp@htpc.purcell.homeip.net>
X-Mailman-Approved-At: Mon, 16 Dec 2002 23:51:15 -0500
cc: 173081-forwarded@bugs.debian.org
Subject: Things have gone wrong with commoncpp2-1.0.7
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 15 Dec 2002 09:07:47 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David, (and others),

The Debian GNU/Linux binary packages of commoncpp2 have gone a little off 
track with the release of version 1.0.7.

Version 1.0.5 of commoncpp2 would build fine for all supported architectures, 
but Version 1.0.7 fails for the following architectures:

s390, powerpc, hppa, sparc, mips & m68k.

The full details are available at:

http://buildd.debian.org/build.php?&pkg=libcommoncpp2

Any assistance you can provide to bring the binary packages back online would 
be appreciated.

Mark

>    ost::enumNetworkDevices(std::vector<ost::NetworkDeviceInfo, 
>    std::allocator<ost::NetworkDeviceInfo> >&)':
> network.cpp:112: ambiguous overload for `ost::InetAddress& = in_addr_t' 
>    operator
> ../include/cc++/socket.h:299: candidates are: ost::InetAddress& 
>    ost::InetAddress::operator=(const char*)
> ../include/cc++/socket.h:301:                 ost::InetAddress& 
>    ost::InetAddress::operator=(const ost::InetAddress&) <near match>
> ../include/cc++/socket.h:307:                 ost::InetAddress& 
>    ost::InetAddress::operator=(long unsigned int)
> make[2]: *** [network.lo] Error 1
> make[2]: Leaving directory `/build/buildd/libcommoncpp2-1.0.7/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/build/buildd/libcommoncpp2-1.0.7'
> make: *** [build-stamp] Error 2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE9/EZMoCzanz0IthIRAquyAJ9qztDTUwLn9zu1V5pS63SLGThgBACfUZ8d
pK0k9//DR+kKXucYTJOwOT8=
=bOqq
-----END PGP SIGNATURE-----


From phreed@netarx.com Mon Dec 16 21:51:05 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18O7od-0007oH-00
	for bug-commoncpp@gnu.org; Mon, 16 Dec 2002 21:50:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18O7oA-0007dW-00
	for bug-commoncpp@gnu.org; Mon, 16 Dec 2002 21:50:11 -0500
Received: from [66.147.137.4] (helo=exchange.netarx.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18O7o3-0007XT-00
	for bug-commoncpp@gnu.org; Mon, 16 Dec 2002 21:50:03 -0500
Received: from netarx.com ([10.0.0.222]) by exchange.netarx.com with Microsoft
	SMTPSVC(5.0.2195.3779);	 Mon, 16 Dec 2002 21:49:52 -0500
Message-ID: <3DFE90CF.60805@netarx.com>
Date: Mon, 16 Dec 2002 21:49:51 -0500
From: Fredrick Paul Eisele <phreed@netarx.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.2.1) Gecko/20021210 Debian/1.2.1-3
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Dec 2002 02:49:52.0216 (UTC)
	FILETIME=[F901BD80:01C2A576]
X-Mailman-Approved-At: Mon, 16 Dec 2002 23:51:15 -0500
Subject: TelnetStream similar to URLStream
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 17 Dec 2002 02:51:05 -0000

I have a need to communicate to cisco devices.
I have started developing a couple classes.
My plan is to use URLStream as a model and the api from Perl
modules Net::Telnet and Net::Telnet::Cisco for the methods.

Is this a reasonable thing to do.
If so, would you be interested in my contributing the result.



From fedemp@bulbasaur.rediris.es Tue Dec 17 03:53:00 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ODTI-0007Gk-00
	for bug-commoncpp@gnu.org; Tue, 17 Dec 2002 03:53:00 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ODTG-0007GQ-00
	for bug-commoncpp@gnu.org; Tue, 17 Dec 2002 03:52:59 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ODTF-0007FM-00
	for bug-commoncpp@gnu.org; Tue, 17 Dec 2002 03:52:57 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ODSu-00006O-00; Tue, 17 Dec 2002 09:52:36 +0100
Date: Tue, 17 Dec 2002 09:52:36 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Mark Purcell <msp@debian.org>
Message-ID: <20021217085236.GA256@bulbasaur.rediris.es>
Mail-Followup-To: Mark Purcell <msp@debian.org>, bug-commoncpp@gnu.org,
	173081-forwarded@bugs.debian.org
References: <200212152007.28784.msp@debian.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200212152007.28784.msp@debian.org>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
cc: 173081-forwarded@bugs.debian.org
Subject: Re: Things have gone wrong with commoncpp2-1.0.7
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 17 Dec 2002 08:53:00 -0000


	Hi, these logs seem to indicate that in_addr_t is not defined
as anything compatible/assignable to 'long unsigned int' on those
platforms. This could be solved with a typecast or adding/modifying
the assignment operators of InetAddress. Could you tell us how
in_addr_t is defined on those platforms? It may be a 32/64 bits issue.

On Sun, Dec 15, 2002 at 08:07:19PM +1100, Mark Purcell wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> David, (and others),
> 
> The Debian GNU/Linux binary packages of commoncpp2 have gone a little off 
> track with the release of version 1.0.7.
> 
> Version 1.0.5 of commoncpp2 would build fine for all supported architectures, 
> but Version 1.0.7 fails for the following architectures:
> 
> s390, powerpc, hppa, sparc, mips & m68k.
> 
> The full details are available at:
> 
> http://buildd.debian.org/build.php?&pkg=libcommoncpp2
> 
> Any assistance you can provide to bring the binary packages back online would 
> be appreciated.
> 
> Mark
> 
> >    ost::enumNetworkDevices(std::vector<ost::NetworkDeviceInfo, 
> >    std::allocator<ost::NetworkDeviceInfo> >&)':
> > network.cpp:112: ambiguous overload for `ost::InetAddress& = in_addr_t' 
> >    operator
> > ../include/cc++/socket.h:299: candidates are: ost::InetAddress& 
> >    ost::InetAddress::operator=(const char*)
> > ../include/cc++/socket.h:301:                 ost::InetAddress& 
> >    ost::InetAddress::operator=(const ost::InetAddress&) <near match>
> > ../include/cc++/socket.h:307:                 ost::InetAddress& 
> >    ost::InetAddress::operator=(long unsigned int)
> > make[2]: *** [network.lo] Error 1
> > make[2]: Leaving directory `/build/buildd/libcommoncpp2-1.0.7/src'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/build/buildd/libcommoncpp2-1.0.7'
> > make: *** [build-stamp] Error 2
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> 
> iD8DBQE9/EZMoCzanz0IthIRAquyAJ9qztDTUwLn9zu1V5pS63SLGThgBACfUZ8d
> pK0k9//DR+kKXucYTJOwOT8=
> =bOqq
> -----END PGP SIGNATURE-----
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


From fedemp@bulbasaur.rediris.es Tue Dec 17 05:25:09 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18OEuR-0007dt-00
	for bug-commoncpp@gnu.org; Tue, 17 Dec 2002 05:25:07 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18OEuH-0007Lk-00
	for bug-commoncpp@gnu.org; Tue, 17 Dec 2002 05:24:58 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18OEu0-0006vc-00
	for bug-commoncpp@gnu.org; Tue, 17 Dec 2002 05:24:40 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18OEtS-000095-00; Tue, 17 Dec 2002 11:24:06 +0100
Date: Tue, 17 Dec 2002 11:23:59 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Fredrick Paul Eisele <phreed@netarx.com>
Message-ID: <20021217102357.GB256@bulbasaur.rediris.es>
Mail-Followup-To: Fredrick Paul Eisele <phreed@netarx.com>,
	bug-commoncpp@gnu.org
References: <3DFE90CF.60805@netarx.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DFE90CF.60805@netarx.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: TelnetStream similar to URLStream
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 17 Dec 2002 10:25:09 -0000


	Yes, I think this is very reasonable and would be a good
addition to cc++. You may also want to have a look at FTPSocket,
ifstpstream and oftpstream in ftp.h.

On Mon, Dec 16, 2002 at 09:49:51PM -0500, Fredrick Paul Eisele wrote:
> I have a need to communicate to cisco devices.
> I have started developing a couple classes.
> My plan is to use URLStream as a model and the api from Perl
> modules Net::Telnet and Net::Telnet::Cisco for the methods.
> 
> Is this a reasonable thing to do.
> If so, would you be interested in my contributing the result.
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


From dyfet@ostel.com Sat Dec 21 12:52:42 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Pnnm-0007CY-00
	for bug-commoncpp@gnu.org; Sat, 21 Dec 2002 12:52:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Pnnj-0007As-00
	for bug-commoncpp@gnu.org; Sat, 21 Dec 2002 12:52:41 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Pnni-000791-00
	for bug-commoncpp@gnu.org; Sat, 21 Dec 2002 12:52:38 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id gBLINiX12450;
	Sat, 21 Dec 2002 13:23:44 -0500
Content-Type: text/plain;
  charset="utf-8"
From: David Sugar <dyfet@ostel.com>
Date: Sat, 21 Dec 2002 12:53:58 -0500
User-Agent: KMail/1.4.3
To: bug-commoncpp@gnu.org, cplusplus-devel@lists.sourceforge.net
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212211253.58792.dyfet@ostel.com>
Subject: Fwd: [ cplusplus-Bugs-657258 ] Implicit declaration of snprintf
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 21 Dec 2002 17:52:43 -0000

process.cpp does include cstdio, which should define snprintf...does it n=
ot on=20
Solaris?

----------  Forwarded Message  ----------

Subject: [ cplusplus-Bugs-657258 ] Implicit declaration of snprintf
Date: Sat, 21 Dec 2002 09:40:12 -0800
From: noreply@sourceforge.net
To: noreply@sourceforge.net

Bugs item #657258, was opened at 2002-12-21 17:40
You can respond by visiting:
https://sourceforge.net/tracker/?func=3Ddetail&atid=3D101523&aid=3D657258=
&group_id=3D
1523

Category: Bug Reporter
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Rob O'Leary (raoleary)
Assigned to: Nobody/Anonymous (nobody)
Summary: Implicit declaration of snprintf

Initial Comment:
In process.cpp, stdio.h is only included on win32. and
so, on Solaris 8 at least, there is no declaration of
snprintf and the compiler exits with a status of 1,
stopping the make process.

Moving the #include <stdio.h> down a line fixes the
problem.


----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=3Ddetail&atid=3D101523&aid=3D657258=
&group_id=3D
1523

-------------------------------------------------------



From ariston@cs.und.edu Sat Dec 21 15:29:25 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18PqFR-0001Ct-00
	for bug-commoncpp@gnu.org; Sat, 21 Dec 2002 15:29:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18PqFM-00010v-00
	for bug-commoncpp@gnu.org; Sat, 21 Dec 2002 15:29:23 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18PqFM-0000vF-00
	for bug-commoncpp@gnu.org; Sat, 21 Dec 2002 15:29:20 -0500
Received: from penguin.cs.und.nodak.edu (penguin.cs.und.nodak.edu
	[134.129.212.25])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gBLKTIqf023704;
	Sat, 21 Dec 2002 14:29:18 -0600
Date: Sat, 21 Dec 2002 14:24:17 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
X-X-Sender: <ariston@localhost.localdomain>
To: David Sugar <dyfet@ostel.com>
In-Reply-To: <200212211253.58792.dyfet@ostel.com>
Message-ID: <Pine.LNX.4.33.0212211421320.8073-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bug-commoncpp@gnu.org
Subject: Re: Fwd: [ cplusplus-Bugs-657258 ] Implicit declaration of snprintf
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 21 Dec 2002 20:29:26 -0000


snprintf is a terribly unportable function.  I've found that at least
Solaris and Irix, each in relatively recent versions, do not include it.
One solution is to include a custom snprintf with the project, and compile
it in if configure can't find snprintf.  GtkYahoo should still come with
an snprintf.c that, I believe, is freely redistributable.  But make sure
it only gets compiled in if it is needed, since it tends to break
compatibility with systems that DO have snprintf.

Ari Johnson

On Sat, 21 Dec 2002, David Sugar wrote:

> process.cpp does include cstdio, which should define snprintf...does it not on
> Solaris?
>
> ----------  Forwarded Message  ----------
>
> Subject: [ cplusplus-Bugs-657258 ] Implicit declaration of snprintf
> Date: Sat, 21 Dec 2002 09:40:12 -0800
> From: noreply@sourceforge.net
> To: noreply@sourceforge.net
>
> Bugs item #657258, was opened at 2002-12-21 17:40
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=101523&aid=657258&group_id=
> 1523
>
> Category: Bug Reporter
> Group: None
> Status: Open
> Resolution: None
> Priority: 5
> Submitted By: Rob O'Leary (raoleary)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: Implicit declaration of snprintf
>
> Initial Comment:
> In process.cpp, stdio.h is only included on win32. and
> so, on Solaris 8 at least, there is no declaration of
> snprintf and the compiler exits with a status of 1,
> stopping the make process.
>
> Moving the #include <stdio.h> down a line fixes the
> problem.
>
>
> ----------------------------------------------------------------------
>
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=101523&aid=657258&group_id=
> 1523
>
> -------------------------------------------------------
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>



From fedemp@bulbasaur.rediris.es Mon Dec 23 04:41:41 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18QP5h-0007YC-00
	for bug-commoncpp@gnu.org; Mon, 23 Dec 2002 04:41:41 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18QP5e-0007UE-00
	for bug-commoncpp@gnu.org; Mon, 23 Dec 2002 04:41:40 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18QP5e-0007Tn-00
	for bug-commoncpp@gnu.org; Mon, 23 Dec 2002 04:41:38 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18QP5l-0000Aq-00
	for <bug-commoncpp@gnu.org>; Mon, 23 Dec 2002 10:41:45 +0100
Date: Mon, 23 Dec 2002 10:41:45 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Message-ID: <20021223094145.GB242@bulbasaur.rediris.es>
Mail-Followup-To: bug-commoncpp@gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
Subject: patch for join and periodic timers from Jakob Scov-Pedersen
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 23 Dec 2002 09:41:41 -0000


	Hi, Jakob Skov-Pedersen has recently submitted thrugh savannah
the patch included below. It adds a new method (Thread::join) and a
bool parameter for setTimer, which allows for setting a periodic
timer.

	Since there has been a discussion about threads, some people
may have comments about this patch. I would apply it for both the next
1.0 release and the 1.1 release, just adding a comment stating that
the periodic timer will be available only where itimer is available,
and adding the 'false' default value for the bool parameter of
setTimer.

-----------

diff -rc2P commoncpp2-1.0.7/ChangeLog commoncpp2-1.0.7-jasp2/ChangeLog
*** commoncpp2-1.0.7/ChangeLog	Mon Nov 25 20:38:32 2002
--- commoncpp2-1.0.7-jasp2/ChangeLog	Thu Dec  5 19:50:35 2002
***************
*** 1,2 ****
--- 1,4 ----
+ From 1.0.7 to 1.0.7-jasp
+ - timer in PosixThread can now be periodic, I think
  From Common C++ 2 1.0.6 to 1.0.7
  - socketport attach() stuff.
diff -rc2P commoncpp2-1.0.7/include/cc++/thread.h commoncpp2-1.0.7-jasp2/include/cc++/thread.h
*** commoncpp2-1.0.7/include/cc++/thread.h	Sun Nov 10 05:19:36 2002
--- commoncpp2-1.0.7-jasp2/include/cc++/thread.h	Thu Dec  5 20:18:51 2002
***************
*** 1069,1072 ****
--- 1069,1073 ----
  	friend class Slog;
  
+ 	Semaphore joinSem;
  	static Thread* _main;
  
***************
*** 1341,1344 ****
--- 1342,1350 ----
  
  	/**
+ 	 * Blocking call which unlucks when thread terminates
+ 	 */
+ 	void join(void);
+ 	
+ 	/**
  	 * Get exception mode of the current thread.
  	 *
***************
*** 1475,1480 ****
  	 * 
  	 * @param timer timeout in milliseconds.
  	 */
! 	void setTimer(timeout_t timer);
  	
  	/**
--- 1481,1487 ----
  	 * 
  	 * @param timer timeout in milliseconds.
+ 	 * @param recuring should the timer be periodic
  	 */
! 	void setTimer(timeout_t timer, bool periodic);
  	
  	/**
diff -rc2P commoncpp2-1.0.7/src/thread.cpp commoncpp2-1.0.7-jasp2/src/thread.cpp
*** commoncpp2-1.0.7/src/thread.cpp	Sun Nov 10 05:19:37 2002
--- commoncpp2-1.0.7-jasp2/src/thread.cpp	Thu Dec  5 20:25:10 2002
***************
*** 276,279 ****
--- 276,283 ----
  }
  
+ void Thread::join(void) {
+ 	joinSem.wait();
+ }
+ 
  /*
   * End Suspend/Resume stuff
***************
*** 825,828 ****
--- 829,833 ----
  		priv->_tid = 0;
  	}
+ 	joinSem.post();
  }
  
***************
*** 1253,1257 ****
  }
  
! void	PosixThread::setTimer(timeout_t timer)
  {
  	sigset_t sigs;
--- 1258,1262 ----
  }
  
! void	PosixThread::setTimer(timeout_t timer, bool periodic)
  {
  	sigset_t sigs;
***************
*** 1263,1266 ****
--- 1268,1275 ----
  	itimer.it_value.tv_usec = (timer * 1000) % 1000000;
  	itimer.it_value.tv_sec = timer / 1000;
+ 	if (periodic) {
+ 		itimer.it_interval.tv_usec = itimer.it_value.tv_usec;
+ 		itimer.it_interval.tv_sec = itimer.it_value.tv_sec;
+ 	}
  #else
  	timer /= 1000;



From dyfet@ostel.com Mon Dec 23 07:55:20 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18QS76-0005w3-00
	for bug-commoncpp@gnu.org; Mon, 23 Dec 2002 07:55:20 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18QS73-0005tq-00
	for bug-commoncpp@gnu.org; Mon, 23 Dec 2002 07:55:18 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18QS72-0005s3-00
	for bug-commoncpp@gnu.org; Mon, 23 Dec 2002 07:55:16 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id gBNDQXi03830;
	Mon, 23 Dec 2002 08:26:33 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>, bug-commoncpp@gnu.org
Date: Mon, 23 Dec 2002 07:57:17 -0500
User-Agent: KMail/1.4.3
References: <20021223094145.GB242@bulbasaur.rediris.es>
In-Reply-To: <20021223094145.GB242@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212230757.18197.dyfet@ostel.com>
Subject: Re: patch for join and periodic timers from Jakob Scov-Pedersen
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 23 Dec 2002 12:55:20 -0000

I think this is a good patch and that makes some degree of sense.  We don=
't=20
make much use of timers in Common C++ since they are not very portable bu=
t=20
where they do work, this is useful.

On Monday 23 December 2002 04:41, Federico Montesino Pouzols wrote:
> Hi, Jakob Skov-Pedersen has recently submitted thrugh savannah
> the patch included below. It adds a new method (Thread::join) and a
> bool parameter for setTimer, which allows for setting a periodic
> timer.
>
> =09Since there has been a discussion about threads, some people
> may have comments about this patch. I would apply it for both the next
> 1.0 release and the 1.1 release, just adding a comment stating that
> the periodic timer will be available only where itimer is available,
> and adding the 'false' default value for the bool parameter of
> setTimer.
>
> -----------
>
> diff -rc2P commoncpp2-1.0.7/ChangeLog commoncpp2-1.0.7-jasp2/ChangeLog
> *** commoncpp2-1.0.7/ChangeLog=09Mon Nov 25 20:38:32 2002
> --- commoncpp2-1.0.7-jasp2/ChangeLog=09Thu Dec  5 19:50:35 2002
> ***************
> *** 1,2 ****
> --- 1,4 ----
> + From 1.0.7 to 1.0.7-jasp
> + - timer in PosixThread can now be periodic, I think
>   From Common C++ 2 1.0.6 to 1.0.7
>   - socketport attach() stuff.
> diff -rc2P commoncpp2-1.0.7/include/cc++/thread.h
> commoncpp2-1.0.7-jasp2/include/cc++/thread.h ***
> commoncpp2-1.0.7/include/cc++/thread.h=09Sun Nov 10 05:19:36 2002 ---
> commoncpp2-1.0.7-jasp2/include/cc++/thread.h=09Thu Dec  5 20:18:51 2002
> ***************
> *** 1069,1072 ****
> --- 1069,1073 ----
>   =09friend class Slog;
>
> + =09Semaphore joinSem;
>   =09static Thread* _main;
>
> ***************
> *** 1341,1344 ****
> --- 1342,1350 ----
>
>   =09/**
> + =09 * Blocking call which unlucks when thread terminates
> + =09 */
> + =09void join(void);
> +
> + =09/**
>   =09 * Get exception mode of the current thread.
>   =09 *
> ***************
> *** 1475,1480 ****
>   =09 *
>   =09 * @param timer timeout in milliseconds.
>   =09 */
> ! =09void setTimer(timeout_t timer);
>
>   =09/**
> --- 1481,1487 ----
>   =09 *
>   =09 * @param timer timeout in milliseconds.
> + =09 * @param recuring should the timer be periodic
>   =09 */
> ! =09void setTimer(timeout_t timer, bool periodic);
>
>   =09/**
> diff -rc2P commoncpp2-1.0.7/src/thread.cpp
> commoncpp2-1.0.7-jasp2/src/thread.cpp ***
> commoncpp2-1.0.7/src/thread.cpp=09Sun Nov 10 05:19:37 2002
> --- commoncpp2-1.0.7-jasp2/src/thread.cpp=09Thu Dec  5 20:25:10 2002
> ***************
> *** 276,279 ****
> --- 276,283 ----
>   }
>
> + void Thread::join(void) {
> + =09joinSem.wait();
> + }
> +
>   /*
>    * End Suspend/Resume stuff
> ***************
> *** 825,828 ****
> --- 829,833 ----
>   =09=09priv->_tid =3D 0;
>   =09}
> + =09joinSem.post();
>   }
>
> ***************
> *** 1253,1257 ****
>   }
>
> ! void=09PosixThread::setTimer(timeout_t timer)
>   {
>   =09sigset_t sigs;
> --- 1258,1262 ----
>   }
>
> ! void=09PosixThread::setTimer(timeout_t timer, bool periodic)
>   {
>   =09sigset_t sigs;
> ***************
> *** 1263,1266 ****
> --- 1268,1275 ----
>   =09itimer.it_value.tv_usec =3D (timer * 1000) % 1000000;
>   =09itimer.it_value.tv_sec =3D timer / 1000;
> + =09if (periodic) {
> + =09=09itimer.it_interval.tv_usec =3D itimer.it_value.tv_usec;
> + =09=09itimer.it_interval.tv_sec =3D itimer.it_value.tv_sec;
> + =09}
>   #else
>   =09timer /=3D 1000;
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From funt@alarit.com Mon Dec 23 10:26:28 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18QUTM-0002EF-00
	for bug-commoncpp@gnu.org; Mon, 23 Dec 2002 10:26:28 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18QUTK-0002Cd-00
	for bug-commoncpp@gnu.org; Mon, 23 Dec 2002 10:26:27 -0500
Received: from gw2.alarit.com ([193.201.100.1] helo=alarit.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18QUTJ-00026S-00
	for bug-commoncpp@gnu.org; Mon, 23 Dec 2002 10:26:25 -0500
Received: from funt.alarit.com (funt.alarit.com [193.201.100.66])
	by alarit.com (8.12.6/8.11.6) with ESMTP id gBNFPZH7077800
	for <bug-commoncpp@gnu.org>; Mon, 23 Dec 2002 17:25:36 +0200 (EET)
	(envelope-from funt@alarit.com)
Content-Type: text/plain;
  charset="us-ascii"
From: funtik <funt@alarit.com>
To: bug-commoncpp@gnu.org
Date: Mon, 23 Dec 2002 17:32:03 +0200
X-Mailer: KMail [version 1.4]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212231732.03056.funt@alarit.com>
X-Mailman-Approved-At: Thu, 26 Dec 2002 08:29:55 -0500
Subject: bug in commoncpp
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 23 Dec 2002 15:26:29 -0000

Hello.

I am use Commoncpp2-1.0.7
OS - FreeBSD 4.7(stable)
glib 1.2
=20
I am compile and receive this message:

c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY=20
-I/usr/local/include -D_GNU_SOURCE -D_THREAD_SAFE=20
-I/usr/local/include/libxml2 -I/usr/local/include -I../include -c network=
=2Ecpp =20
-fPIC -DPIC -o .libs/network.lo
network.cpp: In function `bool=20
ost::enumNetworkDevices(vector<ost::NetworkDeviceInfo,allocator<ost::Netw=
orkDeviceInfo>=20
> &)':
network.cpp:119: `struct ifreq' has no member named `ifr_netmask'
*** Error code 1

In FreeBSD stucture ifreq don`t have member ifr_netmask.


From dyfet@ostel.com Thu Dec 26 08:39:36 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18RYEO-00060K-00
	for bug-commoncpp@gnu.org; Thu, 26 Dec 2002 08:39:24 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18RYCa-0004Zr-00
	for bug-commoncpp@gnu.org; Thu, 26 Dec 2002 08:37:34 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18RYA7-0003kK-00
	for bug-commoncpp@gnu.org; Thu, 26 Dec 2002 08:34:59 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id gBQE6Xe09829;
	Thu, 26 Dec 2002 09:06:33 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: funtik <funt@alarit.com>, bug-commoncpp@gnu.org
Date: Thu, 26 Dec 2002 08:35:20 -0500
User-Agent: KMail/1.4.3
References: <200212231732.03056.funt@alarit.com>
In-Reply-To: <200212231732.03056.funt@alarit.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212260835.21048.dyfet@ostel.com>
Subject: Re: bug in commoncpp
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 26 Dec 2002 13:39:39 -0000

This problem is fixed in cvs and will be fixed in the 1.0.8 release when =
it is=20
made available.

On Monday 23 December 2002 10:32, funtik wrote:
> Hello.
>
> I am use Commoncpp2-1.0.7
> OS - FreeBSD 4.7(stable)
> glib 1.2
>
> I am compile and receive this message:
>
> c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
> -I/usr/local/include -D_GNU_SOURCE -D_THREAD_SAFE
> -I/usr/local/include/libxml2 -I/usr/local/include -I../include -c
> network.cpp -fPIC -DPIC -o .libs/network.lo
> network.cpp: In function `bool
> ost::enumNetworkDevices(vector<ost::NetworkDeviceInfo,allocator<ost::Ne=
twor
>kDeviceInfo>
>
> > &)':
>
> network.cpp:119: `struct ifreq' has no member named `ifr_netmask'
> *** Error code 1
>
> In FreeBSD stucture ifreq don`t have member ifr_netmask.
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From cproch@seculogix.de Thu Dec 26 08:42:25 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18RYH2-0001sG-00
	for bug-commoncpp@gnu.org; Thu, 26 Dec 2002 08:42:08 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18RYGu-0001X1-00
	for bug-commoncpp@gnu.org; Thu, 26 Dec 2002 08:42:02 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18RYGn-00017A-00
	for bug-commoncpp@gnu.org; Thu, 26 Dec 2002 08:41:53 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP
	id D8E5113B3F; Thu, 26 Dec 2002 13:39:26 +0100 (CET)
Content-Type: text/plain;
  charset="iso-8859-1"
From: "Prochnow, Christian" <cproch@seculogix.de>
To: funtik <funt@alarit.com>
Date: Thu, 26 Dec 2002 14:41:50 +0100
User-Agent: KMail/1.4.3
References: <200212231732.03056.funt@alarit.com>
In-Reply-To: <200212231732.03056.funt@alarit.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212261441.50832.cproch@seculogix.de>
cc: bug-commoncpp@gnu.org
Subject: Re: bug in commoncpp
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: cproch@seculogix.de
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 26 Dec 2002 13:42:27 -0000

Hi,=20

this is a known issue, could you try this:
change the member ifr_netmask to ifr_addr and check the demo program if i=
t=20
still prints you the right netmasks for your network devices?

If this works we're going to change it to "ifr_addr" cause there seem to =
be a=20
header-file problem with some BSD versions. It's weird because another pe=
ople=20
did compile network.cpp withour errors - also on FreeBSD 4.7-STABLE.

Regards,
Christian Prochnow


> Hello.
>
> I am use Commoncpp2-1.0.7
> OS - FreeBSD 4.7(stable)
> glib 1.2
>
> I am compile and receive this message:
>
> c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
> -I/usr/local/include -D_GNU_SOURCE -D_THREAD_SAFE
> -I/usr/local/include/libxml2 -I/usr/local/include -I../include -c
> network.cpp -fPIC -DPIC -o .libs/network.lo
> network.cpp: In function `bool
> ost::enumNetworkDevices(vector<ost::NetworkDeviceInfo,allocator<ost::Ne=
twor
>kDeviceInfo>
>
> > &)':
>
> network.cpp:119: `struct ifreq' has no member named `ifr_netmask'
> *** Error code 1
>
> In FreeBSD stucture ifreq don`t have member ifr_netmask.
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Thu Dec 26 08:53:56 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18RYSS-0005sE-00
	for bug-commoncpp@gnu.org; Thu, 26 Dec 2002 08:53:56 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18RYSP-0005lb-00
	for bug-commoncpp@gnu.org; Thu, 26 Dec 2002 08:53:55 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18RYSO-0005kI-00
	for bug-commoncpp@gnu.org; Thu, 26 Dec 2002 08:53:53 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id gBQEPZe09965;
	Thu, 26 Dec 2002 09:25:35 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: cproch@seculogix.de, funtik <funt@alarit.com>
Date: Thu, 26 Dec 2002 08:54:23 -0500
User-Agent: KMail/1.4.3
References: <200212231732.03056.funt@alarit.com>
	<200212261441.50832.cproch@seculogix.de>
In-Reply-To: <200212261441.50832.cproch@seculogix.de>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212260854.23642.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
cc: Federico Montesino Pouzols <fedemp@altern.org>
Subject: Re: bug in commoncpp
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 26 Dec 2002 13:53:56 -0000

It seems ifr_addr and ifr_netmask are typically defined in a union and of=
 the=20
same type, so yes, they generally are interchangable.  I am not sure if t=
here=20
are any platforms this is not true for, however.

There are a few small issues left in 1.0.8 that need to be resolved.  I h=
ope=20
we can clarify them by the 1st to do a release then.  I think it is proba=
bly=20
about time to do a new ccrtp release as well, as I think there is only a=20
question about dropped packets still being investigated there...

On Thursday 26 December 2002 08:41, Prochnow, Christian wrote:
> Hi,
>
> this is a known issue, could you try this:
> change the member ifr_netmask to ifr_addr and check the demo program if=
 it
> still prints you the right netmasks for your network devices?
>
> If this works we're going to change it to "ifr_addr" cause there seem t=
o be
> a header-file problem with some BSD versions. It's weird because anothe=
r
> people did compile network.cpp withour errors - also on FreeBSD 4.7-STA=
BLE.
>
> Regards,
> Christian Prochnow
>
> > Hello.
> >
> > I am use Commoncpp2-1.0.7
> > OS - FreeBSD 4.7(stable)
> > glib 1.2
> >
> > I am compile and receive this message:
> >
> > c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRA=
RY
> > -I/usr/local/include -D_GNU_SOURCE -D_THREAD_SAFE
> > -I/usr/local/include/libxml2 -I/usr/local/include -I../include -c
> > network.cpp -fPIC -DPIC -o .libs/network.lo
> > network.cpp: In function `bool
> > ost::enumNetworkDevices(vector<ost::NetworkDeviceInfo,allocator<ost::=
Netw
> >or kDeviceInfo>
> >
> > > &)':
> >
> > network.cpp:119: `struct ifreq' has no member named `ifr_netmask'
> > *** Error code 1
> >
> > In FreeBSD stucture ifreq don`t have member ifr_netmask.
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fullung@dogbert.sdsl.sun.ac.za Sun Dec 29 04:59:04 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18SaDo-0001ci-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 04:59:04 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18SaDm-0001br-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 04:59:03 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18SaDm-0001bn-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 04:59:02 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18SaDj-0002LA-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 11:58:59 +0200
Received: (qmail 16662 invoked from network); 29 Dec 2002 09:58:59 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 29 Dec 2002 09:58:59 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18SaDh-0006kP-00
	for <bug-commoncpp@gnu.org>; Sun, 29 Dec 2002 11:58:57 +0200
Date: Sun, 29 Dec 2002 11:58:57 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20021229095856.GD420@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18SaDj-0002LA-00*h7.bYZE6mTw*
Subject: autoconf/automake questions
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 29 Dec 2002 09:59:06 -0000

Hello,

I have some questions regarding the autoconf and automake configuration 
of the Common C++ project, specifically the commoncpp2 CVS module.

Firstly, it seems that whenever one runs ./configure, everything is 
rebuilt the next time you run make. This is probably a good policy in 
general, but when one is working on files related to the build system 
and you know that the configure options haven't changed, you might want 
to turn this off. Which macro do I hack? :-)

Secondly, changes to Makefile.am doesn't seem to automatically trigger 
the "rebuilding" of Makefile.in and Makefile, instead requiring that one 
does a ./reconfig && ./configure, causing a complete rebuild as 
described above.

This is quite annoying when you are adding files to a specific _SOURCES 
target, and just want to rebuild just this one target with the 
additional sources. How do I change this behaviour?

Happy holidays and all that. :-)

Cheers,

Albert


From fullung@dogbert.sdsl.sun.ac.za Sun Dec 29 06:15:36 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18SbPs-0005Q8-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 06:15:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18SbPq-0005Ll-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 06:15:35 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18SbPp-0005KK-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 06:15:33 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18SbPk-0001wn-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 13:15:28 +0200
Received: (qmail 27472 invoked from network); 29 Dec 2002 11:15:28 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 29 Dec 2002 11:15:28 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18SbPi-0005rx-00
	for <bug-commoncpp@gnu.org>; Sun, 29 Dec 2002 13:15:26 +0200
Date: Sun, 29 Dec 2002 13:15:26 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20021229111525.GI420@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="FEz7ebHBGB6b2e8X"
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18SbPk-0001wn-00*dXrDXoMR3qc*
Subject: Compiler warnings; minor thread.h patch
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 29 Dec 2002 11:15:36 -0000


--FEz7ebHBGB6b2e8X
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hello,

Attached is a patch to remove the extra qualification of getThreadID() 
in thread.h on line 1352.

This warning shows up when compiling Common C++ with the -Wall, -ansi, 
and -pedantic flags. I think this should be made the default for the 
project?

Another interesting issue that shows up is the extensive use of long 
long constants in sha.cpp, which is apparently forbidden by ANSI C++.

Cheers,

Albert

--FEz7ebHBGB6b2e8X
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="threadqual.diff"

--- commoncpp2.orig/include/cc++/thread.h	2002-12-13 13:24:56.000000000 +0200
+++ commoncpp2/include/cc++/thread.h	2002-12-29 13:05:31.000000000 +0200
@@ -1349,7 +1349,7 @@
 	 *
 	 * @return numeric identifier of this thread.
 	 */
-	cctid_t Thread::getThreadID() const;
+	cctid_t getThreadID() const;
 
 	/**
 	 * Get exception mode of the current thread.

--FEz7ebHBGB6b2e8X--


From fedemp@bulbasaur.rediris.es Sun Dec 29 08:29:10 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18SdV8-00058e-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 08:29:10 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18SdV5-00056K-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 08:29:09 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18SdU2-0004eB-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 08:28:02 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18SdU9-0002Ld-00; Sun, 29 Dec 2002 14:28:09 +0100
Date: Sun, 29 Dec 2002 14:28:08 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-ID: <20021229132808.GA9017@bulbasaur.rediris.es>
Mail-Followup-To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20021229095856.GD420@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021229095856.GD420@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: autoconf/automake questions
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 29 Dec 2002 13:29:11 -0000


        I have found that newer releases of autoconf and automake
(from 2.5x and 1.6 on) handle dependencies (including .am and .in
files) more strictly, so the two problems you mention disappear when
using these autotools releases. With classic releases I would say it
is more reliable to use reconfig and configure. Anyway, if you just
want to do a quick compilation of an additional SOURCE, one can always
edit the Makefile :)

On Sun, Dec 29, 2002 at 11:58:57AM +0200, Albert Strasheim wrote:
> Hello,
> 
> I have some questions regarding the autoconf and automake configuration 
> of the Common C++ project, specifically the commoncpp2 CVS module.
> 
> Firstly, it seems that whenever one runs ./configure, everything is 
> rebuilt the next time you run make. This is probably a good policy in 
> general, but when one is working on files related to the build system 
> and you know that the configure options haven't changed, you might want 
> to turn this off. Which macro do I hack? :-)
> 
> Secondly, changes to Makefile.am doesn't seem to automatically trigger 
> the "rebuilding" of Makefile.in and Makefile, instead requiring that one 
> does a ./reconfig && ./configure, causing a complete rebuild as 
> described above.
> 
> This is quite annoying when you are adding files to a specific _SOURCES 
> target, and just want to rebuild just this one target with the 
> additional sources. How do I change this behaviour?
> 
> Happy holidays and all that. :-)
> 
> Cheers,
> 
> Albert
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


From fedemp@bulbasaur.rediris.es Sun Dec 29 08:55:40 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Sdum-0001qg-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 08:55:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Sduk-0001m5-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 08:55:39 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Sduk-0001kj-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 08:55:38 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18Sdrr-0002Ms-00; Sun, 29 Dec 2002 14:52:39 +0100
Date: Sun, 29 Dec 2002 14:52:39 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-ID: <20021229135238.GB9017@bulbasaur.rediris.es>
Mail-Followup-To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20021229111525.GI420@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021229111525.GI420@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Compiler warnings; minor thread.h patch
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 29 Dec 2002 13:55:41 -0000

On Sun, Dec 29, 2002 at 01:15:26PM +0200, Albert Strasheim wrote:
> Hello,
> 
> Attached is a patch to remove the extra qualification of getThreadID() 
> in thread.h on line 1352.
> 

	Fixed in CVS.

> This warning shows up when compiling Common C++ with the -Wall, -ansi, 
> and -pedantic flags. I think this should be made the default for the 
> project?
> 

	Yes, it has been suggested by other people on this list and I
think it should be done -if is no objection- for the next release. It
would require adding a conditional check for gcc -and fixing a lot of
seemingly inoffensive warnings that show up when these options are
specified.

> Another interesting issue that shows up is the extensive use of long 
> long constants in sha.cpp, which is apparently forbidden by ANSI C++.
> 
> Cheers,
> 
> Albert



From fullung@dogbert.sdsl.sun.ac.za Sun Dec 29 10:33:36 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18SfRY-0003eg-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 10:33:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18SfRV-0003XE-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 10:33:34 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18SfRU-0003Us-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 10:33:32 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18SfRO-0001Bn-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 17:33:26 +0200
Received: (qmail 28700 invoked from network); 29 Dec 2002 15:33:26 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 29 Dec 2002 15:33:26 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18SfRO-0002rf-00; Sun, 29 Dec 2002 17:33:26 +0200
Date: Sun, 29 Dec 2002 17:33:26 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-ID: <20021229153325.GA395@dogbert.sdsl.sun.ac.za>
References: <20021229095856.GD420@dogbert.sdsl.sun.ac.za>
	<20021229132808.GA9017@bulbasaur.rediris.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021229132808.GA9017@bulbasaur.rediris.es>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18SfRO-0001Bn-00*0iF2NSSzr.s*
cc: bug-commoncpp@gnu.org
Subject: Re: autoconf/automake questions
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 29 Dec 2002 15:33:38 -0000

Hello,

On Sun, 29 Dec 2002, Federico Montesino Pouzols wrote:

>         I have found that newer releases of autoconf and automake
> (from 2.5x and 1.6 on) handle dependencies (including .am and .in
> files) more strictly, so the two problems you mention disappear when

I am running automake 1.6.3 and autoconf 2.57.

> using these autotools releases. With classic releases I would say it
> is more reliable to use reconfig and configure. Anyway, if you just
> want to do a quick compilation of an additional SOURCE, one can always
> edit the Makefile :)

Anyway, I've found the solution to the problem. All you have to do is to 
configure with --enable-maintainer-mode, and changes to Makefile.am and 
the like will cause autoconf/automake to rerun the neccesary programs to 
generate the .in files.

Cheers,

Albert


From dyfet@ostel.com Sun Dec 29 10:36:10 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18SfU1-0008Eg-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 10:36:09 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18SfTs-0007sA-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 10:36:03 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18SfTd-00071B-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 10:35:45 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id gBTG7ke23028;
	Sun, 29 Dec 2002 11:07:46 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>,
   Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Date: Sun, 29 Dec 2002 10:37:26 -0500
User-Agent: KMail/1.4.3
References: <20021229111525.GI420@dogbert.sdsl.sun.ac.za>
	<20021229135238.GB9017@bulbasaur.rediris.es>
In-Reply-To: <20021229135238.GB9017@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212291037.26698.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: Compiler warnings; minor thread.h patch
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 29 Dec 2002 15:36:11 -0000

I actually fixed a lot of small code issues recently with -Wall on gcc 2.=
95,=20
so the number of annoying warnings left should already be fairly small an=
d=20
much easier to deal with.

On Sunday 29 December 2002 08:52, Federico Montesino Pouzols wrote:
> On Sun, Dec 29, 2002 at 01:15:26PM +0200, Albert Strasheim wrote:
> > Hello,
> >
> > Attached is a patch to remove the extra qualification of getThreadID(=
)
> > in thread.h on line 1352.
>
> =09Fixed in CVS.
>
> > This warning shows up when compiling Common C++ with the -Wall, -ansi=
,
> > and -pedantic flags. I think this should be made the default for the
> > project?
>
> =09Yes, it has been suggested by other people on this list and I
> think it should be done -if is no objection- for the next release. It
> would require adding a conditional check for gcc -and fixing a lot of
> seemingly inoffensive warnings that show up when these options are
> specified.
>
> > Another interesting issue that shows up is the extensive use of long
> > long constants in sha.cpp, which is apparently forbidden by ANSI C++.
> >
> > Cheers,
> >
> > Albert
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fullung@dogbert.sdsl.sun.ac.za Sun Dec 29 11:37:29 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18SgR7-0007Di-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 11:37:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18SgQx-00075x-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 11:37:07 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18SgQv-00071u-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 11:37:01 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18SgQq-00071a-00
	for bug-commoncpp@gnu.org; Sun, 29 Dec 2002 18:36:56 +0200
Received: (qmail 29175 invoked from network); 29 Dec 2002 16:36:55 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 29 Dec 2002 16:36:55 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18SgQp-0002uQ-00; Sun, 29 Dec 2002 18:36:55 +0200
Date: Sun, 29 Dec 2002 18:36:55 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20021229163655.GB395@dogbert.sdsl.sun.ac.za>
References: <20021229111525.GI420@dogbert.sdsl.sun.ac.za>
	<20021229135238.GB9017@bulbasaur.rediris.es>
	<200212291037.26698.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="bp/iNruPH9dso1Pn"
Content-Disposition: inline
In-Reply-To: <200212291037.26698.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18SgQq-00071a-00*jyqnu45lr.Q*
cc: bug-commoncpp@gnu.org
Subject: Re: Compiler warnings; minor thread.h patch
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 29 Dec 2002 16:37:30 -0000


--bp/iNruPH9dso1Pn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hello,

Attached is a patch to fix all the warnings (when compiling with 
-Wall, -ansi and -pedantic) in src, demos, and tests, with the 
exception of an usused variable in one of the demos and the long long 
integer constant warnings in sha.cpp (not quite sure what needs to be 
done here).

I'll feed cc++ to gcc 3.2 and the Intel C++ compiler when I get back to 
work during the second week in January.

Cheers,

Albert

On Sun, 29 Dec 2002, David Sugar wrote:

> I actually fixed a lot of small code issues recently with -Wall on gcc 2.95, 
> so the number of annoying warnings left should already be fairly small and 
> much easier to deal with.
> 
> On Sunday 29 December 2002 08:52, Federico Montesino Pouzols wrote:
> > On Sun, Dec 29, 2002 at 01:15:26PM +0200, Albert Strasheim wrote:
> > > Hello,
> > >
> > > Attached is a patch to remove the extra qualification of getThreadID()
> > > in thread.h on line 1352.
> >
> > 	Fixed in CVS.
> >
> > > This warning shows up when compiling Common C++ with the -Wall, -ansi,
> > > and -pedantic flags. I think this should be made the default for the
> > > project?
> >
> > 	Yes, it has been suggested by other people on this list and I
> > think it should be done -if is no objection- for the next release. It
> > would require adding a conditional check for gcc -and fixing a lot of
> > seemingly inoffensive warnings that show up when these options are
> > specified.
> >
> > > Another interesting issue that shows up is the extensive use of long
> > > long constants in sha.cpp, which is apparently forbidden by ANSI C++.
> > >
> > > Cheers,
> > >
> > > Albert
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 

--bp/iNruPH9dso1Pn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="warnfix1.patch"

diff -x CVS -uNr commoncpp2.orig/demo/serialecho.cpp commoncpp2.patch/demo/serialecho.cpp
--- commoncpp2.orig/demo/serialecho.cpp	2002-09-27 15:18:16.000000000 +0200
+++ commoncpp2.patch/demo/serialecho.cpp	2002-12-29 18:17:45.000000000 +0200
@@ -105,7 +105,7 @@
 }
 
 void SerialEcho::run() {
-  char b, s[getBufferSize()];
+  char* s = new char[getBufferSize()];
 
   cout << "start monitor" << endl;
 
@@ -117,6 +117,9 @@
   }
 
   cout << "end of monitor" << endl;
+
+  delete [] s;
+  
   exit();
 }
 
diff -x CVS -uNr commoncpp2.orig/demo/serialmain.cpp commoncpp2.patch/demo/serialmain.cpp
--- commoncpp2.orig/demo/serialmain.cpp	2002-05-09 01:18:30.000000000 +0200
+++ commoncpp2.patch/demo/serialmain.cpp	2002-12-29 18:14:03.000000000 +0200
@@ -79,7 +79,7 @@
     ::exit(1);
   }
 
-  char b[ modem->getBufferSize()];
+  char* b = new char[modem->getBufferSize()];
 
   cout << "Modem code:" << modem->start() << endl;
 
@@ -93,6 +93,8 @@
   }
   cout << "fin" << endl;
 
+  delete [] b;
+  
   return 0;
 }
 
diff -x CVS -uNr commoncpp2.orig/demo/shadigest.cpp commoncpp2.patch/demo/shadigest.cpp
--- commoncpp2.orig/demo/shadigest.cpp	2002-11-22 00:14:40.000000000 +0200
+++ commoncpp2.patch/demo/shadigest.cpp	2002-12-29 18:14:34.000000000 +0200
@@ -30,8 +30,8 @@
 		d256.initDigest();
 
 		if(fp) {
-			while(length = 
-			      fread(buff, sizeof(unsigned char), BUFF_SIZE, fp)) {
+			while((length = 
+			      fread(buff, sizeof(unsigned char), BUFF_SIZE, fp))) {
 				d256.putDigest(buff, length);
 			}
 			
diff -x CVS -uNr commoncpp2.orig/demo/tcpservice.cpp commoncpp2.patch/demo/tcpservice.cpp
--- commoncpp2.orig/demo/tcpservice.cpp	2002-05-09 01:18:30.000000000 +0200
+++ commoncpp2.patch/demo/tcpservice.cpp	2002-12-29 18:12:21.000000000 +0200
@@ -71,6 +71,10 @@
     {
     }
 
+    virtual ~ts_list_head()
+    {
+    }
+   
     // This thing knows how to remove and insert items.
     void RemoveListItem( ts_list_item * li );
     void InsertListItem( ts_list_item * li );
diff -x CVS -uNr commoncpp2.orig/demo/xmlfetch.cpp commoncpp2.patch/demo/xmlfetch.cpp
--- commoncpp2.orig/demo/xmlfetch.cpp	2002-02-22 12:12:18.000000000 +0200
+++ commoncpp2.patch/demo/xmlfetch.cpp	2002-12-29 18:18:45.000000000 +0200
@@ -113,9 +113,7 @@
 int main(int argc, char **argv)
 {
 	myXMLParser xml;
-	char cbuf[1024];
 	URLStream::Error status;
-	int len;
 
 //	url.setProxy("home.sys", 8000);
 	try
diff -x CVS -uNr commoncpp2.orig/src/file.cpp commoncpp2.patch/src/file.cpp
--- commoncpp2.orig/src/file.cpp	2002-12-05 23:19:07.000000000 +0200
+++ commoncpp2.patch/src/file.cpp	2002-12-29 18:29:52.000000000 +0200
@@ -321,6 +321,8 @@
 		flag |= O_NDELAY;
 
 	//completionDeferred: ? (hen)
+	default:
+                break;
 	}
 	fcntl(fd, F_SETFL, flag);
 	return errSuccess;
diff -x CVS -uNr commoncpp2.orig/src/socket.cpp commoncpp2.patch/src/socket.cpp
--- commoncpp2.orig/src/socket.cpp	2002-12-20 13:03:56.000000000 +0200
+++ commoncpp2.patch/src/socket.cpp	2002-12-29 17:40:33.000000000 +0200
@@ -345,6 +345,8 @@
 			throw SockException(string(errs), err, systemError);
 		}
 #endif
+	default:
+	        break;
 	}
 	return err;
 }
diff -x CVS -uNr commoncpp2.orig/src/url.cpp commoncpp2.patch/src/url.cpp
--- commoncpp2.orig/src/url.cpp	2002-09-17 23:22:08.000000000 +0200
+++ commoncpp2.patch/src/url.cpp	2002-12-29 17:42:49.000000000 +0200
@@ -311,6 +311,8 @@
 		Socket::state = STREAM;
 		allocate(bufsize);
 		return errSuccess;
+	default:
+	        break;
 	}
 
 
@@ -518,6 +520,8 @@
 		snprintf(reloc, 64, "%s:%s", user, password);
 		b64Encode(reloc, reloc + 64, 128);
 		str << reloc + 64 << "\r\n";
+	default:
+	        break;
 	}
 
         str << "Connection: close\r\n";
diff -x CVS -uNr commoncpp2.orig/tests/url1.cpp commoncpp2.patch/tests/url1.cpp
--- commoncpp2.orig/tests/url1.cpp	2002-03-21 15:09:53.000000000 +0200
+++ commoncpp2.patch/tests/url1.cpp	2002-12-29 18:36:31.000000000 +0200
@@ -76,15 +76,15 @@
 }
 
 // check buffer overflow on string
-void checkStringOverflow(char* s,int len)
+void checkStringOverflow(char* s,unsigned int len)
 {
 	bool execCheck2 = (strlen(s) == len);
-	for(int l1=0;l1<32;++l1)
+	for(unsigned int l1=0;l1<32;++l1)
 	{
 		sprintf(status,"%s %d",s,l1);
 		if (execCheck2)
 			check2(s,l1,l1 >= (len+2)/3*4+1);
-		for(int l2=0;l2<32;++l2)
+		for(unsigned int l2=0;l2<32;++l2)
 			check1((unsigned char*)s,len,l1,l2,
 					(l1 >= (len+2)/3*4+1) 
 					&& (l2 >= len) );

--bp/iNruPH9dso1Pn--


From fullung@dogbert.sdsl.sun.ac.za Mon Dec 30 04:46:41 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18SwVN-0006cM-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 04:46:41 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18SwVJ-0006Rc-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 04:46:40 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18SwVH-0006F3-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 04:46:36 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18SwVA-0003y2-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 11:46:28 +0200
Received: (qmail 4733 invoked from network); 30 Dec 2002 09:46:28 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 30 Dec 2002 09:46:28 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18SwV9-00078t-00
	for <bug-commoncpp@gnu.org>; Mon, 30 Dec 2002 11:46:27 +0200
Date: Mon, 30 Dec 2002 11:46:27 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20021230094627.GA417@dogbert.sdsl.sun.ac.za>
References: <20021229111525.GI420@dogbert.sdsl.sun.ac.za>
	<20021229135238.GB9017@bulbasaur.rediris.es>
	<200212291037.26698.dyfet@ostel.com>
	<20021229163655.GB395@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="FCuugMFkClbJLl1L"
Content-Disposition: inline
In-Reply-To: <20021229163655.GB395@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18SwVA-0003y2-00*g4wUkSLHX5E*
Subject: Re: Compiler warnings; minor thread.h patch
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 30 Dec 2002 09:46:42 -0000


--FCuugMFkClbJLl1L
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hello,

Attached is a slightly modified and extended patch for compiler warnings 
seen with gcc 3.2 (some also seen with gcc 2.96).

On Sun, 29 Dec 2002, Albert Strasheim wrote:

> Attached is a patch to fix all the warnings (when compiling with 
> -Wall, -ansi and -pedantic) in src, demos, and tests, with the 
> exception of an usused variable in one of the demos and the long long 
> integer constant warnings in sha.cpp (not quite sure what needs to be 
> done here).

The new patch lists all possible cases in switches, instead of using a 
default case to suppress the warning. This is probably more correct.
 
> I'll feed cc++ to gcc 3.2 and the Intel C++ compiler when I get back to 
> work during the second week in January.

Compiled with gcc 3.2. Fixed some more warnings.
 
Cheers,

Albert

--FCuugMFkClbJLl1L
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="warnfix2.patch"

diff -uNr commoncpp2.orig/demo/serialecho.cpp commoncpp2.patch/demo/serialecho.cpp
--- commoncpp2.orig/demo/serialecho.cpp	2002-09-27 15:18:16.000000000 +0200
+++ commoncpp2.patch/demo/serialecho.cpp	2002-12-29 18:17:45.000000000 +0200
@@ -105,7 +105,7 @@
 }
 
 void SerialEcho::run() {
-  char b, s[getBufferSize()];
+  char* s = new char[getBufferSize()];
 
   cout << "start monitor" << endl;
 
@@ -117,6 +117,9 @@
   }
 
   cout << "end of monitor" << endl;
+
+  delete [] s;
+  
   exit();
 }
 
diff -uNr commoncpp2.orig/demo/serialmain.cpp commoncpp2.patch/demo/serialmain.cpp
--- commoncpp2.orig/demo/serialmain.cpp	2002-05-09 01:18:30.000000000 +0200
+++ commoncpp2.patch/demo/serialmain.cpp	2002-12-29 18:14:03.000000000 +0200
@@ -79,7 +79,7 @@
     ::exit(1);
   }
 
-  char b[ modem->getBufferSize()];
+  char* b = new char[modem->getBufferSize()];
 
   cout << "Modem code:" << modem->start() << endl;
 
@@ -93,6 +93,8 @@
   }
   cout << "fin" << endl;
 
+  delete [] b;
+  
   return 0;
 }
 
diff -uNr commoncpp2.orig/demo/shadigest.cpp commoncpp2.patch/demo/shadigest.cpp
--- commoncpp2.orig/demo/shadigest.cpp	2002-11-22 00:14:40.000000000 +0200
+++ commoncpp2.patch/demo/shadigest.cpp	2002-12-29 18:14:34.000000000 +0200
@@ -30,8 +30,8 @@
 		d256.initDigest();
 
 		if(fp) {
-			while(length = 
-			      fread(buff, sizeof(unsigned char), BUFF_SIZE, fp)) {
+			while((length = 
+			      fread(buff, sizeof(unsigned char), BUFF_SIZE, fp))) {
 				d256.putDigest(buff, length);
 			}
 			
diff -uNr commoncpp2.orig/demo/tcpservice.cpp commoncpp2.patch/demo/tcpservice.cpp
--- commoncpp2.orig/demo/tcpservice.cpp	2002-05-09 01:18:30.000000000 +0200
+++ commoncpp2.patch/demo/tcpservice.cpp	2002-12-29 18:12:21.000000000 +0200
@@ -71,6 +71,10 @@
     {
     }
 
+    virtual ~ts_list_head()
+    {
+    }
+   
     // This thing knows how to remove and insert items.
     void RemoveListItem( ts_list_item * li );
     void InsertListItem( ts_list_item * li );
diff -uNr commoncpp2.orig/demo/xmlfetch.cpp commoncpp2.patch/demo/xmlfetch.cpp
--- commoncpp2.orig/demo/xmlfetch.cpp	2002-02-22 12:12:18.000000000 +0200
+++ commoncpp2.patch/demo/xmlfetch.cpp	2002-12-29 18:18:45.000000000 +0200
@@ -113,9 +113,7 @@
 int main(int argc, char **argv)
 {
 	myXMLParser xml;
-	char cbuf[1024];
 	URLStream::Error status;
-	int len;
 
 //	url.setProxy("home.sys", 8000);
 	try
diff -uNr commoncpp2.orig/src/file.cpp commoncpp2.patch/src/file.cpp
--- commoncpp2.orig/src/file.cpp	2002-12-05 23:19:07.000000000 +0200
+++ commoncpp2.patch/src/file.cpp	2002-12-30 11:30:30.000000000 +0200
@@ -320,7 +320,8 @@
 	case completionDelayed:
 		flag |= O_NDELAY;
 
-	//completionDeferred: ? (hen)
+	case completionDeferred:
+		break;
 	}
 	fcntl(fd, F_SETFL, flag);
 	return errSuccess;
diff -uNr commoncpp2.orig/src/socket.cpp commoncpp2.patch/src/socket.cpp
--- commoncpp2.orig/src/socket.cpp	2002-12-20 13:03:56.000000000 +0200
+++ commoncpp2.patch/src/socket.cpp	2002-12-30 11:28:06.000000000 +0200
@@ -345,6 +345,8 @@
 			throw SockException(string(errs), err, systemError);
 		}
 #endif
+	case Thread::throwNothing:
+		break;
 	}
 	return err;
 }
@@ -1405,6 +1407,10 @@
 			Socket::state = INITIAL;
 			return -1;
 		}
+	case AVAILABLE:
+	case BOUND:
+	case STREAM:
+		break;
 	}
 	Socket::state = CONNECTED;
 	return 0;
diff -uNr commoncpp2.orig/src/unix.cpp commoncpp2.patch/src/unix.cpp
--- commoncpp2.orig/src/unix.cpp	2002-12-12 06:11:05.000000000 +0200
+++ commoncpp2.patch/src/unix.cpp	2002-12-30 11:25:08.000000000 +0200
@@ -515,6 +515,10 @@
  			Socket::state = INITIAL;
  			return -1;
  		}
+	case AVAILABLE:
+	case BOUND:
+	case STREAM:
+		break;
  	}
  	Socket::state = CONNECTED;
  	return 0;
diff -uNr commoncpp2.orig/src/url.cpp commoncpp2.patch/src/url.cpp
--- commoncpp2.orig/src/url.cpp	2002-09-17 23:22:08.000000000 +0200
+++ commoncpp2.patch/src/url.cpp	2002-12-30 11:40:39.000000000 +0200
@@ -311,6 +311,12 @@
 		Socket::state = STREAM;
 		allocate(bufsize);
 		return errSuccess;
+	case methodHttpPut:
+	case methodHttpPost:
+	case methodFtpGet:
+	case methodFtpPut:
+	case methodFilePut:
+    	        break;
 	}
 
 
@@ -518,6 +524,8 @@
 		snprintf(reloc, 64, "%s:%s", user, password);
 		b64Encode(reloc, reloc + 64, 128);
 		str << reloc + 64 << "\r\n";
+	case authAnonymous:
+	        break;
 	}
 
         str << "Connection: close\r\n";
diff -uNr commoncpp2.orig/src/urlstring.cpp commoncpp2.patch/src/urlstring.cpp
--- commoncpp2.orig/src/urlstring.cpp	2002-08-31 16:20:13.000000000 +0200
+++ commoncpp2.patch/src/urlstring.cpp	2002-12-30 11:14:17.000000000 +0200
@@ -51,7 +51,11 @@
 #ifdef	WIN32
 #include <io.h>
 #endif
+#ifdef HAVE_SSTREAM
+#include <sstream>
+#else
 #include <strstream>
+#endif
 #include <cctype>
 
 #ifdef	CCXX_NAMESPACES
diff -uNr commoncpp2.orig/tests/url1.cpp commoncpp2.patch/tests/url1.cpp
--- commoncpp2.orig/tests/url1.cpp	2002-03-21 15:09:53.000000000 +0200
+++ commoncpp2.patch/tests/url1.cpp	2002-12-29 18:36:31.000000000 +0200
@@ -76,15 +76,15 @@
 }
 
 // check buffer overflow on string
-void checkStringOverflow(char* s,int len)
+void checkStringOverflow(char* s,unsigned int len)
 {
 	bool execCheck2 = (strlen(s) == len);
-	for(int l1=0;l1<32;++l1)
+	for(unsigned int l1=0;l1<32;++l1)
 	{
 		sprintf(status,"%s %d",s,l1);
 		if (execCheck2)
 			check2(s,l1,l1 >= (len+2)/3*4+1);
-		for(int l2=0;l2<32;++l2)
+		for(unsigned int l2=0;l2<32;++l2)
 			check1((unsigned char*)s,len,l1,l2,
 					(l1 >= (len+2)/3*4+1) 
 					&& (l2 >= len) );

--FCuugMFkClbJLl1L--


From fedemp@bulbasaur.rediris.es Mon Dec 30 07:54:12 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18SzQU-0002JH-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 07:53:50 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18SzQM-000278-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 07:53:44 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18SzQK-00022V-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 07:53:40 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18SzHM-0007QB-00; Mon, 30 Dec 2002 13:44:24 +0100
Date: Mon, 30 Dec 2002 13:44:16 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-ID: <20021230124414.GA6010@bulbasaur.rediris.es>
Mail-Followup-To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20021229111525.GI420@dogbert.sdsl.sun.ac.za>
	<20021229135238.GB9017@bulbasaur.rediris.es>
	<200212291037.26698.dyfet@ostel.com>
	<20021229163655.GB395@dogbert.sdsl.sun.ac.za>
	<20021230094627.GA417@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021230094627.GA417@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Compiler warnings; minor thread.h patch
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 30 Dec 2002 12:54:13 -0000


	Ok, the patch has been just committed to CVS. I have added an
AM_CONDITIONAL so that these compiling options are only used when
compiling with GCC.

	For now, these options are not used for the library sources of
the RELEASE1 branch, since we have yet to sort out the issue with long
long. I have also looked at what happens when you specify -W and other
subtle options, and it seems there are more details to fix...

On Mon, Dec 30, 2002 at 11:46:27AM +0200, Albert Strasheim wrote:
> Hello,
> 
> Attached is a slightly modified and extended patch for compiler warnings 
> seen with gcc 3.2 (some also seen with gcc 2.96).
> 
> On Sun, 29 Dec 2002, Albert Strasheim wrote:
> 
> > Attached is a patch to fix all the warnings (when compiling with 
> > -Wall, -ansi and -pedantic) in src, demos, and tests, with the 
> > exception of an usused variable in one of the demos and the long long 
> > integer constant warnings in sha.cpp (not quite sure what needs to be 
> > done here).
> 
> The new patch lists all possible cases in switches, instead of using a 
> default case to suppress the warning. This is probably more correct.
>  
> > I'll feed cc++ to gcc 3.2 and the Intel C++ compiler when I get back to 
> > work during the second week in January.
> 
> Compiled with gcc 3.2. Fixed some more warnings.
>  
> Cheers,
> 
> Albert



From dyfet@ostel.com Mon Dec 30 09:02:27 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18T0Ut-0008OU-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 09:02:27 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18T0Ur-0008Nt-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 09:02:26 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18T0U3-0008CK-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 09:01:35 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id gBUEVwe31205;
	Mon, 30 Dec 2002 09:31:58 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>,
   Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Date: Mon, 30 Dec 2002 08:59:42 -0500
User-Agent: KMail/1.4.3
References: <20021229111525.GI420@dogbert.sdsl.sun.ac.za>
	<20021230094627.GA417@dogbert.sdsl.sun.ac.za>
	<20021230124414.GA6010@bulbasaur.rediris.es>
In-Reply-To: <20021230124414.GA6010@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212300859.42683.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: Compiler warnings; minor thread.h patch
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 30 Dec 2002 14:02:27 -0000

I think we may need to pull sha.cpp from the R1 branch if we cannot come =
up=20
with a fully satisfactory solution with that, or if there are still expor=
t=20
linking issues in it...

David

On Monday 30 December 2002 07:44, Federico Montesino Pouzols wrote:
> Ok, the patch has been just committed to CVS. I have added an
> AM_CONDITIONAL so that these compiling options are only used when
> compiling with GCC.
>
> =09For now, these options are not used for the library sources of
> the RELEASE1 branch, since we have yet to sort out the issue with long
> long. I have also looked at what happens when you specify -W and other
> subtle options, and it seems there are more details to fix...
>
> On Mon, Dec 30, 2002 at 11:46:27AM +0200, Albert Strasheim wrote:
> > Hello,
> >
> > Attached is a slightly modified and extended patch for compiler warni=
ngs
> > seen with gcc 3.2 (some also seen with gcc 2.96).
> >
> > On Sun, 29 Dec 2002, Albert Strasheim wrote:
> > > Attached is a patch to fix all the warnings (when compiling with
> > > -Wall, -ansi and -pedantic) in src, demos, and tests, with the
> > > exception of an usused variable in one of the demos and the long lo=
ng
> > > integer constant warnings in sha.cpp (not quite sure what needs to =
be
> > > done here).
> >
> > The new patch lists all possible cases in switches, instead of using =
a
> > default case to suppress the warning. This is probably more correct.
> >
> > > I'll feed cc++ to gcc 3.2 and the Intel C++ compiler when I get bac=
k to
> > > work during the second week in January.
> >
> > Compiled with gcc 3.2. Fixed some more warnings.
> >
> > Cheers,
> >
> > Albert
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fullung@dogbert.sdsl.sun.ac.za Mon Dec 30 11:04:56 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18T2Nu-0002N3-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 11:03:22 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18T2NA-0001s7-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 11:02:38 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18T2Mg-0001Wt-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 11:02:06 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18T2Ma-0004EI-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 18:02:00 +0200
Received: (qmail 7827 invoked from network); 30 Dec 2002 16:02:00 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 30 Dec 2002 16:02:00 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18T2MZ-0003my-00
	for <bug-commoncpp@gnu.org>; Mon, 30 Dec 2002 18:01:59 +0200
Date: Mon, 30 Dec 2002 18:01:59 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20021230160159.GA409@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18T2Ma-0004EI-00*SLerSLnVT1g*
Subject: Coding standards
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 30 Dec 2002 16:04:57 -0000

Hello,

Are there any hard-and-fast rules with regards to formatting code one 
wants to contribute to Common C++, specifically with regards to 
indentation, capitalization of method names, etc.?

Cheers,

Albert


From fullung@dogbert.sdsl.sun.ac.za Mon Dec 30 11:11:43 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18T2Vz-0006NF-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 11:11:43 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18T2Vv-0006MU-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 11:11:42 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18T2Vu-0006M9-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 11:11:39 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18T2Vs-00071e-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 18:11:37 +0200
Received: (qmail 7991 invoked from network); 30 Dec 2002 16:11:36 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 30 Dec 2002 16:11:36 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18T2Vs-00052r-00; Mon, 30 Dec 2002 18:11:36 +0200
Date: Mon, 30 Dec 2002 18:11:36 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-ID: <20021230161135.GB409@dogbert.sdsl.sun.ac.za>
References: <20021229111525.GI420@dogbert.sdsl.sun.ac.za>
	<20021229135238.GB9017@bulbasaur.rediris.es>
	<200212291037.26698.dyfet@ostel.com>
	<20021229163655.GB395@dogbert.sdsl.sun.ac.za>
	<20021230094627.GA417@dogbert.sdsl.sun.ac.za>
	<20021230124414.GA6010@bulbasaur.rediris.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021230124414.GA6010@bulbasaur.rediris.es>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18T2Vs-00071e-00*.5C1OTgrMzo*
cc: bug-commoncpp@gnu.org
Subject: Re: Compiler warnings; minor thread.h patch
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 30 Dec 2002 16:11:43 -0000

Hello,

On Mon, 30 Dec 2002, Federico Montesino Pouzols wrote:

> 	Ok, the patch has been just committed to CVS. I have added an
> AM_CONDITIONAL so that these compiling options are only used when
> compiling with GCC.

Instead of an AM_CONDITIONAL, might I suggest something like the 
following:

if test $GCC = xyes; then
	WARN_FLAGS = -Wall -ansi -pedantic
else
	WARN_FLAGS =
fi
AC_SUBST(WARN_FLAGS)

Then update the CFLAGS and CXXFLAGS in the various Makefile.am files and 
just add $(WARN_FLAGS).

Cheers,

Albert


From fullung@dogbert.sdsl.sun.ac.za Mon Dec 30 16:02:11 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18T71h-0004M7-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 16:00:45 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18T71W-0004I1-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 16:00:35 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18T70z-0003z0-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 16:00:02 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18T70t-0005Yu-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 22:59:55 +0200
Received: (qmail 10090 invoked from network); 30 Dec 2002 20:59:55 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 30 Dec 2002 20:59:55 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18T70s-000117-00
	for <bug-commoncpp@gnu.org>; Mon, 30 Dec 2002 22:59:54 +0200
Date: Mon, 30 Dec 2002 22:59:54 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20021230205954.GD409@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18T70t-0005Yu-00*zFmRWt.l936*
Subject: Headers and templated classes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 30 Dec 2002 21:02:11 -0000

Hello,

A few questions regarding header files and templated classes in cc++.

Firstly, what are the p[io]* headers for?

Secondly, how does one actually use a header in the template directory 
when building something in the demo directory? You can't exactly 
#include it in the standard way, unless I am mistaken? Seems you 
would have to make install cc++ first -- not always convenient.

IMHO, the reasons given in the README for keeping the templated and 
non-templated code seperate are not entirely valid. It is quite common 
for code that was once "normal" to be extended in future to support 
templating. Should this code then be moved? I think not.

Cheers,

Albert


From fedemp@bulbasaur.rediris.es Mon Dec 30 16:17:00 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18T7HK-0001VV-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 16:16:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18T7H6-000183-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 16:16:42 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18T7GC-0000g2-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 16:15:44 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18T7GL-0008DA-00; Mon, 30 Dec 2002 22:15:53 +0100
Date: Mon, 30 Dec 2002 22:15:52 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-ID: <20021230211550.GA31551@bulbasaur.rediris.es>
Mail-Followup-To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20021230160159.GA409@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021230160159.GA409@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Coding standards
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 30 Dec 2002 21:17:01 -0000


	Yes, there is a short summary of rules, see the "Developer
Documentation" chapter in the info documentation.

On Mon, Dec 30, 2002 at 06:01:59PM +0200, Albert Strasheim wrote:
> Hello,
> 
> Are there any hard-and-fast rules with regards to formatting code one 
> wants to contribute to Common C++, specifically with regards to 
> indentation, capitalization of method names, etc.?
> 
> Cheers,
> 
> Albert
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


From fedemp@bulbasaur.rediris.es Mon Dec 30 16:23:52 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18T7O4-0006uC-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 16:23:52 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18T7NI-0006OO-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 16:23:05 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18T7Mr-00068Q-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 16:22:37 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18T7K3-0008DM-00; Mon, 30 Dec 2002 22:19:43 +0100
Date: Mon, 30 Dec 2002 22:19:43 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-ID: <20021230211942.GB31551@bulbasaur.rediris.es>
Mail-Followup-To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20021229111525.GI420@dogbert.sdsl.sun.ac.za>
	<20021229135238.GB9017@bulbasaur.rediris.es>
	<200212291037.26698.dyfet@ostel.com>
	<20021229163655.GB395@dogbert.sdsl.sun.ac.za>
	<20021230094627.GA417@dogbert.sdsl.sun.ac.za>
	<20021230124414.GA6010@bulbasaur.rediris.es>
	<20021230161135.GB409@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021230161135.GB409@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Compiler warnings; minor thread.h patch
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 30 Dec 2002 21:23:53 -0000


	I agree, I also prefer this solution.

On Mon, Dec 30, 2002 at 06:11:36PM +0200, Albert Strasheim wrote:
> Instead of an AM_CONDITIONAL, might I suggest something like the 
> following:
> 
> if test $GCC = xyes; then
> 	WARN_FLAGS = -Wall -ansi -pedantic
> else
> 	WARN_FLAGS =
> fi
> AC_SUBST(WARN_FLAGS)
> 
> Then update the CFLAGS and CXXFLAGS in the various Makefile.am files and 
> just add $(WARN_FLAGS).
> 
> Cheers,
> 
> Albert
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


From fullung@dogbert.sdsl.sun.ac.za Mon Dec 30 19:16:41 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TA5J-0003A5-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 19:16:41 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TA5G-00039l-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 19:16:40 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TA5F-00038q-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 19:16:37 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18TA5D-0006Pi-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 02:16:35 +0200
Received: (qmail 10735 invoked from network); 31 Dec 2002 00:16:34 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 31 Dec 2002 00:16:34 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18TA5C-0005Zo-00
	for <bug-commoncpp@gnu.org>; Tue, 31 Dec 2002 02:16:34 +0200
Date: Tue, 31 Dec 2002 02:16:34 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20021231001633.GA4188@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="IS0zKkzwUGydFO0o"
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18TA5D-0006Pi-00*iauDpbl5pLE*
Subject: Test framework; new counter class
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 31 Dec 2002 00:16:41 -0000


--IS0zKkzwUGydFO0o
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hello,

Attached is a patch that contains the following:

- some basic code for a test framework for Common C++ based on the 
CppUnit test library,

- a counter class (called UberCounter for now) meant to unify the 
Counter, MutexCounter and AtomicCounter classes,

- minor tweaks to configure.in and some Makefile.am files related to 
gcc compiler flags.

The patch is against commoncpp2 in CVS on Tue Dec 31 02:00:00 GMT+2 2002 
or thereabouts.

Firstly, a few notes about the proposed test framework.

The CppUnit test library seems to be THE way to test any C++ project. 
Since Common C++ doesn't have much in the way of a test suite at the 
moment (which the exception of a few tests and demos), I think it would 
be wise to incorporate this test framework into the project to ensure a 
robust and bug-free library for everyone.

To run the tests, compile Common C++ as usual, and then cd to the tests 
directory. Now run "make check" to build and run the tests.

On Debian unstable, I currently configure Common C++ as follows:

CC=/usr/bin/gcc-3.2 CXX=/usr/bin/g++-3.2 ./configure \
--enable-maintainer-mode --with-cppunit-prefix=/home/fullung/opt

For development purposes, I removed the "default" CppUnit from the 
system, and installed a recompiled (with gcc 3.2) CppUnit in
/home/fullung/opt/{bin,lib,etc.}. This is neccesary due to the 
incompatible ABI changes between gcc 2.9x and gcc 3.2 which prevents 
one from linking code (the tests) compiled with gcc 3.2 against a 
library (default CppUnit) compiled with gcc 2.9x.

This shouldn't be a problem on RedHat 8, which ships with gcc 3.2
compiled libraries by default, or systems that only ship with gcc 
2.9x compiled libraries.

I noticed some weirdness when compiling the UberCounter tests with gcc 
2.95.4, related to the tests for operator!=. If anyone else sees this 
behaviour and/or is able to provide a workaround, I would be most 
interested.

The current tests are by no means complete (or even correct :-)), but it 
should serve as a good example of what can be done. Specifically, I 
still need to spend some time on the Thread tests.

Secondly, some notes about the new counter class, UberCounter.

Common C++ currently has three counter classes,

- a templated Counter<T> class with only a few operators,
- MutexCounter, which is essentially a thread-safe counter, but only 
for the int type,
- AtomicCounter class, a thread-safe counter that utilizes system 
specific support for atomic operations on ints (Linux) or longs (Win32), 
or substitutes a mutex on system with no such features.

There are a few shortcomings with this arrangement, namely, that there 
isn't a templated, thread-safe counter and furthermore, that there is 
much code duplication as regards the various operator methods.

UberCounter is a templated counter class was designed with these 
problems in mind. Using UberCounter as a base class, I have implemented 
UberMutexCounter, which is thread-safe and templated, and 
UberAtomicCounter which makes use of system specific atomic operations 
(Linux code is mostly done, Win32 not).

If you're interested, take a quick look at the patch for an idea of how 
UberCounter works. I still need to write some documentation, but the 
basic design should be easy to understand.

(As an aside, it seems that configure is checking for sys/atomic.h, when 
it should in fact be checking for asm/atomic.h (at least on Linux). I 
added #define HAVE_ATOMIC in the UberCounter code to work around this
problem; this issue should probably be addressed in the configure 
script, as I would imagine that it also affects AtomicCounter.)

So, any chance of me seeing a future version of UberCounter in CVS? :-) 
Comments, suggestions, etc. on improving this class would be much 
appreciated.

Finally, the configure.in tweaks simply fix code related to the compile 
flags for gcc (-Wall, -ansi, and -pedantic), add a check for CppUnit, 
and make corresponding changes to the Makefile.am files.

Phew. That's about it... :-)

Cheers,

Albert

--IS0zKkzwUGydFO0o
Content-Type: application/octet-stream
Content-Disposition: attachment; filename="tstcntcnf1.patch.gz"
Content-Transfer-Encoding: base64

H4sICCDfED4AA3RzdGNudGNuZjEucGF0Y2gA7D1rd9u4jp/rX8F6cuY6seRnMm2dx8R1nNTn
Jk6O7Uzb2/Z4FImOtZUlryTnced2f/sCJPWmHDtJ7+7ZTWbGlkkQBEEABEEKY5iTCVEXbp/o
zmzm2Pp83qg4rnld1R17Yl4vXFox7XilTW8TdQVVVZc2ftWo1RpqvaE2a6T+ptV826r/VqkF
f6Rcg/pCuVxe1kmEo05q9dbOu1atmcFxeEjUN++Ut6QMn/UGOTwskPPhaNz59Gnc734c9/q9
ES8ZnvTGw9HpxfkACgrqL6TtUnJLycIz7WviTyk56V8iPXPTou7vBbV9Nu6c9496o955v31a
Oul04PfZRe+0O1B86vmkuAFlRbJP7qm3WSg/hJH0JgipEI/65GN70B8fn7ZPhoUyf26fngz3
C2VzQhjyO0QOuO+gyS4iswvlV1Gr/aL6UbMsomq2ZxJ1Tg3N9k29WChPzEK53RkPL98PR6Wo
wSYMmvxCRlPTI97UWVgGuaLEtH167Wo+Ncit6U8Z0Q58uCETyWRh677p2B4Ak9l21fH8sX53
V5ltFwj0c9run4yH7T+6bCrqtbfKG1Ku1xvwhXMRUsKa3YyNe9tyNIO6gp7h8DTgEHHm2A8w
vjNuD07GH3ujDyXPsxQS/X1RVaRThWKS+Hu/MGFEzpzaWOUt5nPH9b8pjBW5yAhZju4c0CGB
ETryCn7vIx7xWCxuxgYJJZucD413ym/Ah2ZTqTcZI2JQ79vD7vi09x5ZAFJz6ugwAaQzn1/a
pk8mjsskAGQIqD8bX7RHH8adi4tLkORSvfK2UgNZw3afnQXRNZuJ02JO4Elb+M5M+06Bo7Zh
IjM1C8oNkEiYap/4TrzGukcsV2ykoIAL6FwVoosCOHcdkIyZV2FUxDXhA8x2QJFChCqI3ziu
YREpxPGeX44uLkclz9Wrun5tLxoqV3CCJWdA6QTn/da0m43oJ3A3+gECFzwXiOHEWhl05kS/
TFu3FgbNFuh6uRyVhg8+nc0tYHtUNXEpvfKM6vz7tTq3TM8vEHg07YkTN1LenOohaGoEHdCX
RsXVGUu8iG4mENvbyg4IxM6OwuXBA5VTYbCvi4f+1J27AHp3WHxd3Ah/FV8HAJfDwfhi0D3u
fWIQYfVXEEIGctHu/L190n2NFIyDH7z1H93BEKaNVwU/yB6fh4o/m5MD8TwtEN0glUq1Uimo
8I+Ru0wkWF/RZmkrnq6XLhdpoMcuGUvxAJJGq9mQLhv1ulKvo62C1QNn5Kzd64/gv+6gc9pt
94/B0A/BAIeowfxFolgg3U+jQXt81BuOAGjQbR+ddYk2p56jf68Y3jz2fBvhuNK5dFTuZlZB
BVsfX1UKKswRM9aA8TB4PiQbpdEH7EAYciK1/AWVWh5dEQUAgxmYoB1ZrcuN5ErS63dOL48Y
e9TeRsl35mPQaMN0N6tC7wrk9Kh9dAQAIFCo7ZZ5xU1AxdIi9GgtEPvR5/749Lx91B0A9n+w
YsRt/XOJFEo1XCKNeXBSqcwDFlJVB0UmjWar1mjV36winQ/gY1LaaLS2663tbamUNrZxQWWf
KKSvJv68MiXXrrOYe/AwMz0dvmzq3zrud3xazK6oi1Vz+AIzBk8edU3NwgfLAT1ndgNlk7JK
39WnmlvBxd+lmgEPsBTc4ZeLbUBSEZnr6NTzeCk0gWVCIJqbsLRDwxmBp5lmm3N88Mg8LBYP
FR+Ef26GwLHSrwWV4ZncGqzx2ITFCAxSWVYKLF6A2+KiwSqQ77AojKcUXQoPRAYp0mcGuBK2
x0BxNtgDt3HEMK8pYwq90ylzONgzru/wwGYHx7Wi2IWkLJ33iOAHRS4EfVV/96am1urwLwFp
q9Xg37UFLsIW96UbKL47dam41RT4VVca9R0Ut3K1SjrO/B7InPqk1NkkiEeBjyZpWyBnPhn6
ruZNqTmrMGjCPpmXKRwIAo+4YBLPmfi3mkt3yb3wXFxqoBSYVwuf+SfgqlTB+5k5wP17hggK
FzZMLXNMYSQzjziT0LU+oTZ1wcW5WFxZpk5OTR3cP0o06BtLgCxwcjkibHKMVAwFFeQYeGNo
KAC7hJrM571BjXFs0gg6ERgV4rgMS0nzkXhXuKqbQPE9QTcibMu5IGVCNFYDXWnEPwWHFR4A
Kwz01gSrfoXbBzpZgIOJOACaoOsKjhRp9z/jtmHQ7o8+7zJ33YFaekM5LhMcGhP9eM11YUW4
hzEwFGewnn2ANu33vdPe6DMMhRz3Rv3ucEiOzwekTS7ag1Gvc3naHpCLy8HF+bBbIWRIkTDK
MCxh9YRNl4vemK+ZlhcbPrqnYqMx1W4oTLZOzRsgUAORnd8/PI8Mi2Y54JCKvUnEz10Ca6ft
+Aq5dU0QHvBsszPMEETTrJCerVcUsvOOjND7o+TC0nRKVDJcII5ms6aQ92CsEPSsDXpSR3vf
rL1RyOWwHRta24NBoCcIVjWyIwER+SNS0CaDxWZCBoNhyK5xtoAtyErNCN12kIJQ1n1656MF
AxbbXHhM3wOGWlTzxDABssMMAemUywkhpDEKoU+UNgW5h0pomfZ31kPUFsquXM295zxne0GG
CC2jh0OEGTAWwDbQX3pH9YWvXVkwMjY7hgMwMC2gdUgitSag57j5CETJpd7Cwq1NrC0ivcI9
C6gQU9gHuFgJxMtl+xrGI9CgGEKT7VVtB3ThHrsEtdORxTBCTWc2MVAOZECwWZfwQHcMtkd2
YDRpzY64Go566tyCOrrQ4kazTAN3dWgg+IYaFjsPd9G308gixWjmux1mZ9dnhowqbY72AGTI
tu4D0WTjEXJjxCwra29rszgTwAj0uJQwdWVNJ64zC4fDsHicPaFOiyUjQKKgMWYjkNsPpg++
pwhuxDnKaQKu4kCSI2DzjZSBvnBTCiOHuQaSR0DLjWMa6BgBgQbbRaMdse8dmy0NApHna/6C
aZi30Kd8zUHzyeRcYdhnC9jZGjBOn4oZSzAYaINRcJ4AxllsKgTjuG3iqHWNB1GciVhBbm2m
8nFewSIAPbBqfeoAcobsdkoZx1H3GLvShCD/Ax6xxokeK3GKDIex9BbWRmEJ+PjkY6vgcl4o
/2JOQFLAwOAWsnN+2R91B+MPUA6FYJAy5diCeyGwz0Q3JHAsD7CuWoV97Fm3BT4rsBtDElOq
f2e88O69quY7MxNdWoxbaN4sLIhjjZcfRISwwER7dH7W6wi6Q7L77bPuEHbG3WGhjILuzdH0
g7EvlP8CyHA7lEMd2Mtr8FNx2Z+Z/6RsHYLJAJ6Llbx4BcpQBGvH1y2BRKx/GODCBQmbANng
qDIVtz3/90I5iETs+fdzynRwBEPSLc3zyCW4WB3uwzE6oVefoilrFcoYphpxX3gXapheiWLE
hCOnsBkgZ2BgfPRfsAZwvJrxgjYsQ9f2jNq+EhVesNACrJMuldYcUUkNcDGvEa+StWqLpS5W
dAQ+N1g9G+Ueif0R0L7Lf0sG12GcTY5PD8u6/7nQ0JGKFfUdX1J6AvIJPE4WnsJ+RwomQYCw
rDigPCIsQXxsQksjgvsZcCH2a5ukxWeyJIo2//qB0ohNbkzXB8Tkv+JtJfXM6l1R0CN6zuQM
mMvhou4TsNoEMK0GChtE+5oaJTEfTJCXwnOBN0oRG5a1GYkOgtHFu1GgFlbTBQUu7abHfOU4
VtBZ0DjV5dL2I3JN/T+wtrTJFTIxW6NQY/dLAsvmbraKNYxP7a9ED+ASpUGTcrm0tF5VS9l+
oBEstdlyAJaWl5fQXF5OdAz5EiTqciRsbkImZfCkq1dG9Xo5qtdroNpbimlvdUQHSxEdrEHR
8sHtrTG4g+WoDvJR/WB68tC6BEpK70RDMF98AYpj2xsdKEExrAOtFmvB17H4apVGljaMSZSh
hQwNPjO4gWabtoWegNwYRmsERWys01DTEpYpjiZtJyMs4GDe0AwWzr6IUW3mqCzlFCjwAXdE
4q7W5bA7/tjrNxuhTxNf/4V3k/B5kALuF4198bCL3g1GhlklI5ZYjv59N/J6wtnIQ5kZBVqc
2CRFHBGde9Qv/cqflQAuxqGAx/5Su4/1Gcu9ksWXtsTCtLWPCHepv3DtgHnorgYDiNEtGPnL
rebauGssgjchTns5rNAudLuLq7EuJd8oCLkSHnmpWFAFrz4rXuDSgcx7WdmviFZbsMPB+MJW
9SElCWQxIQ6vUHYqKfUJCMuo0XIa04qVR2KuAi6hMKWaKQrFRKbdaRZrCtUmY6QemEfeMHf2
OD+C3QUIjoEb0nvqR9Rxy5G3bfmxGxeB1BYriPT6us52WbEdzdYW6Z61O0OytQVUbLHzZvDT
NNfEwIPXYoWwZaTgg5bL7JeuwnbG1FVnMgFVbpFtVtq1GaO2qutGxzHEv0qYGuBWj5AD8LPG
yBFfKkrebDWXR8nf1F6i5C9R8pco+UuU/CVK/hIlf4mSv0TJU1HyUaeTEydnNY+LUct35qPU
RrnVWiGotslQs41Veh8QxntgawSw4qcHBk+fllgwL+HhYuSbZELLLb61gvZkn5S4UdmPohKv
rkDfv+9KMAgTL2tfXgVBFEuWoVBXQZGKhSfwlMtB4P2B5mHoO9FcVR9unoqqJ9qz1uXyCu3l
/bP2qppuL3Yp6f1WgF0EgdncizKxbQ5F5Ee+fLKde0ZEV4vdPiymDPsakpo6JEgKCRGCKqSE
yMUke6ggxfJ6VSzidEGK5CAHRwoFHkOIDSufnCSWvRgWAfMwPfkjO1h1ZOHpiBTNXi6aB+Qx
OGR4pEBmDWY2PPRXat/OnBjcNnJvXeNwYxivv1epVA5KuEJskpmmu87vmQg/dLLF9BNcmTFb
S/bjCFKQApkYWLyZevCQtQ50XNo4h59PYl32oCRknsCbXI2yh5CRRX5kx9Jw9tpU6JVICh4g
JknKr7mk4XFPSIeUgNRSk5qRLZy25yEFT5ZWISVcNtYnJX+KxAnWSlOSXv4eLRfieGydThOD
f9xI11WD4DD8iUqQd663JhFr6MASxq/Jg8hjeyoX8g4m1yZjDT5IvRvJ6WeGhqQDlL67sBIn
Hup7NWY8QMhz8eL1I3gRXtp4OjvyjocfQctzcWRvfYawqylPZ0bOCfeaZDwXHw7W50Nwb+fp
rMg5o1+fkmeTikfoSehnP4dsPFVRYsQ8m4Q8gieJO1vPICdPZUuSHilnVjwA/B864ZttV8Xb
opXZdvpkLVEpPctLQDz2AC+JJPni4M5vrR35C3/i1O4tP7QzbIt9kPQ7tl/Oev3e2eWZKt6W
VMiXdgdffVV7x+rx+WX/iHxRSFTUPx/x4m/fvm0KvO3O+Kh7fNkvpZArhfIXnLL4W8nBu7f8
tU4leis5WbF/cfwJ5Iv75xjudKN3hlko3/M1y6IGKfFjN83axPefSexPIBzzl6HGAm9xA3sD
zSgqeRD4Qq+MZIzM59Mdq+XEd6GAzJ9vANjBCqNIgLF3kwFp9J59PjTGbu5I8Pa9jALNvfag
a0kpMCM+/iW9iJsiMYr+Cl6m7pz3j3snZdDQH4wWfNU7QQ78JWGXdVS9Mu1Ab8SL2AIN5gwI
PnMZ8yw8yWHHv4MTqzMBv0HcmeJeDM5PSknMoYCJ9gqxHRZiDDoUp9zjmWnvb9RDfGfDk3Hn
Q7fz917/pMRONTg8UcMz9YN9siHBwrDbzlhUgRTHZyp6+Z7ThykpirZTTDAo1voej40IiW6F
hc15aok/U/gwXD2xtGvvzyQ4vqUrA7bMqwA0NRYZtKj6M7jXFDSZaf/huFFDqk+dDG/Iv8jX
hIXAA7u/edWvpS9fauq7b9+2vm5Wcn9Uv9arf0sRCsz+6b02JL3qrvOTe22yXmU8RjGV94lV
P4vHP7fXPB7/3F5lPA7Q8zdGoPO7uRvvZUMq8OTrQboG6fv6r1Wa7kub/ipvGhf4ZK/BNP38
XvelveY1jekKELyfrsK24SxENlI+H8xW1ouptUQY60F3eHkKDqF8xBX5aCpySr+JQ6jI6qa7
EYuI3Finl6dwXHcbETAOJrU2mxPsEIbQ+KYQhbTAmYXHTVaXXATSq0CxmCpn5r5YTCNuRoib
fJCxJZQnvEli3pTWsUwQhfI35p7BP/kbkHjuGEm6h1S1dBOSgpGkHnm7yjZkCZpGs9VstOo7
8swjDaWOyWAamIAEszpEuUT2E3lyWBquROIclkYJX0lr4O4rkVcEUx/AbhKcZ0wQwR908VCv
6AVyOgoSwOwfwnM8I8zh8mQkao9n8SDqEWvV/YRptHDOBu3B52WJQzCzw+Gns9OxqMd0IQzF
UW+wPJNJuUB+PgVhIpR8GlOpTzpRtpS83Cq/pNKjRLhivRTKK0GR06OwQ/GIPUZTCUwMrrix
4kH3tNsedll6LU23MBJgmC403ygZmq+xHC2inMnidh0TVTXfwCdKIkvTQu/8xtjSxsPzy0GH
EXi1wKh4BSQftHvisIe5OafsIUg5gs+J/BtYgElE8BvTiLBWIisJPlP72rQ5DpGWI0CBt8LY
D5HoBB9nxg779qYax4xZShhF/lw0ZFlExteWc6VZniDSYQ88lYi0KswngmAsKdncNW+QgCnB
C5KYI83Fy4Yiy8gDpimGTWYv4p3lmaYYzGMjJGk08ZvNtdZOPS+XnoiR1BuNl5vNLzebX242
v9xsfrnZ/HKz+eVm8//vm83SV814Oo/HXGCWvWeKr9NlXrJbfoc5fM0zPH3LuRaHgOG9uBov
y1wP/Su6UCm7xsw35rL3WxPvWMduXS55lzRx7zLn3nOiQxD0EutHIRlUT+owcU86OcbF1c/p
MnuvOtEvCFsWVbUqukTTzl4fNVbqJX79OdGLQZ+nl+wt7XU4tGzIy3vMDmytHqXDj/XIb95K
bnzL745Kr46G5+hplV717e1IrdOXu3P0fJlOZy98kxTfSlLOJW+BE/ncSK+Cr4j/9Vr4o0vi
K6I/WAd77v1xKerl18mX3yZflfq1mBO/Z77qGJZ3IPRActN8ZUXILHvL7nXkhxaSOaUlcc8M
gDS8kIGSxD7frRJgWIKIhxjetRpZREHeZZYjXqn/9lyJlw2H0VNBtwbjSPANm+P5wq/4sHW6
0X+rzLTv/wsSLqsrZE5+VErmdDRRghhapAPxz5WkGWbFdvACBzsuH7TPeMzwuo4fDZFYuC6+
GyLYR3x9DluzOoYI65gKf9QdjrBhcH7CprRQZuHuOGIgDCFZknnsJBGnvK4HcTzsOlnVYFUo
g813SpOUm2+VOrsMxEiIweJPjoZVyLiEMVLOJYzWBiz6R/jE2rAM/4nhxDqJDpVMm0ULEWDM
clawFMRl9nsUJGWO/wqhO0E6/wAgKuARUY4ksQIHoEM60+ZTWEezBfG2sYtumIQvPZ71eQOI
N5LHPhG7HrJ/GZ5JrVIaaoklTIM+Nt6agy1jE7ezWcNjYdedNy9R15eo6+Oirv9Xg66J+APX
r+rCrGJMtDoCrRssbFtEI0LAYtyUFjMVgU3N1sTsabYyZjCzlSkTmwVI2NEijgs3OmgpWCoh
zb3WFdxxuVv4fPPlW3SnWNySbLVGMOhLE7+DcROXfQnnlX/yoopmGAhX4km/8LHV8pDppc3Q
202Dcs6sBhvyajXwkHurgSf4uVqTGIexYI8lnUtn1yIHT0AUT1O3KrZC+RXnKjXiOKG18iS8
+VQmWJdCBHsQUuP4qltix7NFxNutM+0eLGE2YVfcomgYiKB3aINvtfvfQxQfMaSKttRDKDDn
HIxlCvOq9I5FedGw4hKkWR4LZoIhm4UYiiDc4CVTo5jNplYJoKqP5nFySGm2xPKDCdzwlX41
thaENv69N+65byF15KReiAxyiQskA3+aGyTFmPy/uSFS+eUY4Qq9qb+4Qi+u0IsrlHaFYklm
cBcszk/ysrLLQWQuFTO+KEBe9QO1wPCeYQ4DL+lXSdK58zynmdU6ynMac148/9i8A0tKI89G
bAMZncPL3qgrWfnDFTAOXWJ71vMwo7oMhmMcd/tHzJKn0z2ypSG5LODCw8636kr03NhNJYPM
UFgK8j/ytqXNeOtSvdGUZoPkn+y0MjGWeIrZYDj/3d6x9rZtJD/rfgVdoCkjvyTKTlvLD7RN
cHcfri1iF3e4LwZj0Y4QSfRJVFwDTX/7zcy+ZpfcXcpSLj5A/dDI5HB2dnY4Oy/O/nB5+eYt
TBq2tNQMRNHpnmicEYTMCBIIaYbd3TU4CbAZrBXQ/r4ZVQyaRbCFwdh0sfVP/1hM5VUrEj1Q
jDHYCyiT7Ol5WOlQKsGkKRUk+CwZ9HqEfEBPiRQT2BILoO1iR3ci7bjPMJskMseBj+qdZIdB
tqM4wwQpk6oaeZnMoMaJywKyucOgWH9d2f/0C33YyGwXO4rmt3EsuJiJZQFvwMCy8Tnm1eAk
C0aa+v2jrX21ta+29pUn1NQUDvrLLu3VTtwDAX/KZzfF5NcS99yXNeNGaz2ZB9k/Hy8wejOe
3TH3Xt9cVPm8Sl17RiFph+MhHyMK2G7wF7rjonhKUo7LipVqMTrviur6rqyusQ4mnzQTW96b
gbCUDkvP2EhjrJW8If5MaJmSe2TTqhzicYtDCx0VGILgiEfxY8/RdZdmDUIjNtsnTVM35Q4t
/KV84hmt+ZPXVK8ZkCPu3eaw+9PijsrZN1Xybl7mI2xVlggAbsaSMS2CMCcni0lR3KfHvZ7C
HZlXazlblcnBxftRTYf3xELxEehUujLVjPEuG3Aon+C1R7LkVdmQh87swL+O2UEbUXAxaA43
C4N6aF0J8c5nEzI1TLBAU7JebiwPeJj58n5VOTs8ZKiALlHwyUS2vSD+8UcSneTh4buyUsfn
ohkwwokBeHTcndQ/8osX3pHN0OPb4Fuk/Uhl+S+qERZggVlxegp7nMzLI4vEQ1/hdQIC7Tfh
dn6zZElPFr0ERksTr1qRkq1AiiPOn6y1QPNAbUj5XT6e+cSxmi+FNBrdZhYNLJCHiOyBM7i2
kvO94ytqRaNA4qqyroKCmvJqPC1G/yR2P5udLjvuraHKwmrk8HBRTosKZg2uDZm9Bwd0Ogj4
AaNiovMeX2hDewZ+cSj1wKDa+8SbSDlwbDV/+CiYbugPtgdeb/3hrT8czTf89MvPr/+Ora+a
cw3W7c3nGbh5fmIdLid0eeMpqbL7MTuETiSn+VagVUc+6dIoSl/DHgBSd13RL1VnQQXpuAtd
g4WwlxhN72YKGL1pfZwcb79MTnT6GhMHU3Fo1R49mwqQPTF62oNfalhpSeM5pGynERfdbIP4
8SenhuUYUM2MZzkmw4fOI2QQiK2qPTxtz4ZxOdFuHRNHc3RPEeuomSVnCZpleIkepW8aJPfl
o80n77HFqW3AznlvAkgDXOMrOvRS5gACQWzJwVqg7yrxf2WZYC36DNhw4SNWnTVXH11Ow5Vf
YiqVIxj6lfuEh53JUouH9/gJobJ6UVFZMR81acVlNROSGM1rJegRhrhI1N/OMgrc2tejqIw0
xzvoLthoYHodnJt67+YKu158vGPYxgeYF9gRzNwD4E/eBQgPjRyTNqah4qUavpkfNcKUAJtH
XCKQPJldUSPXXAvyTDDAhSsKYgFabLq4EA9LYeGnTVqW+xoZWBuPP/vKwp5ukK4OLEJlAWw6
HFOryKnDaofkyXlfpoiTrn5JhjW13VUmu6vaLSalHpUr9GdR/WYpUBMdPUvAhK0RJAREeecC
huvuWkDKHq8q8vnr8sHSF/ozTzUXdcWduovKCW4PnZsqAOpeZ7E19xZzJofPKOenCu/97oWE
iPk0EmwD/ozC5PgyxydHwWMJt77M1pfZ+jItfJl//Hb15l/Nfoy+xb0SFIHZne2owL4Lb9L5
5l0dshpW9nUoYCrolMoeP8RX0eJZ9UJ1O+LOD+mZrjoWWtvQZIaUM+Ur+Y1REKQ0GQ6VFaUi
vJoeFeU1BFHMFwYs74FQO9Kr/7idLBfvedwX8SGN++fu+cNtB8R2aiBzY9xRFsA2WBt7cEBC
WJIwFXR0NfJRWaiGqeI+GJice8QZyS1FbCdIKT1d4w0+1gnQ1vGHNTtyc6d/Dw/l2/2uEOFu
GHcvASsTXqmHQrzzeJ2Iv5APCUlP1VyxvIfxQI+hbu+eJcerrA3axyi1tQWqr0lbMXFNbi3w
ikOP42IyUvm7CbgsoreJyuSAZrorLWvbsgD5G5ryFy+fET/pdcslP/asVy1HAvdoZrVX7dqN
CBhOpYSZYgPi43mFHS4hxpTwUkyAY0xt9K6piv/ICIE1pZjLz10P/Y3JGm6HweF3Et4WN0vY
qz8WAZirh/JKruBTvQO5TEr1WcuuyaSqTxmu8fO02QUQaoGZ/7VghoMhYNTzYFZzaanmWo2E
mi7toC+teCyoRGsPFAWKFpgAUzSbRGqEuhNR7EPsR7U6PzlENX98w0YRukLec99Rz+VVMH82
KvwMNiLHOay3CYph9QR3lVtH7+RCvd0Z9TyafVOpwe0ihH6qkrVf6Zdfhgr3EpHDbH4wUw9m
DQ/KXLzxNVnxgc6ysksNu0sm858wMRWfEL1phbSC9XePPahA5au9xFIez8Dvs7969jtjFlzM
B7SAN+AJ2vgcf/C7k6NXYX9w+1nx1h/c+oPhWk/7615ZC+F8tIqAGLnCJkxPLoXwlWR8vsIJ
qphEw36R3xaTR7Tkl9NCtptTCYNZ+XBBMWZQt4+4HgfCeO97CyaoAgOQ340/6shigoUTZB7o
jwcEBZqTYPIUIywKvSuIl4LUaQFvwMgO+2q+tCqJa64ZXYn6bJPUh4tS7kssE2wlFY3gCyAI
UN2XLMKqiJVf8yKlYkLYBrMqRfoFX3J8SnyMi80ArVpgH6P4CMGql+jEJOXsrF39nchG+RBY
cskgqvF5j7L/rqhA7V/EJ1knwwPunSXi/xTSL6hbIqVWERY28aQViv76KLLYQj4bpfhF5b3v
TOXpSm4TU/G9XCvIXVCkr+aPjkSDL0YJWOWrPFwrP4fGwKCHupTJS8F57BgMjcXVT38l9DqZ
ASIrFaZkjbUyiDehaGOM9FSpm9st2dCM5+ls4BRuaEtoxfXaaN5Hnvqa/FzO/l3My7fFAryS
myJuYA5W0qVH7aCR+syv1vXIbfSVh8B19dVgBX1Vm4qreo/aTcXDvXWncrTOVJhMPYPwSSh1
zqDah042kULn2Jywybcnx5GS4O0nstuwyTZsEk2jX4Li+fVvv7x905xKt25vPk+OmnHlNDnd
17qhS0jop1S/kZJhytkJnR1MjGu07LMpT0WlwMYqB0OFrlY+ijEgdeeV4003n6ipSsXtPTkV
T/Gw2cL+5EPFsoPmMV2Qq3e5pmJccTNSd8qAgFV6BZqYlSSCAlVua+OXRPIUpuOTaFlik26U
pRYVEaYowAhEpZwiXhzQ8cy7Lh6e0taOal5t5fsbk97+xLbNCa9QWZInLrqyw/lrWbxrpIlt
PP40sArUBkBUrCWUTBbLFIBwzPYn55wdddQf+u9lw9qrz+tUPbcCTw38t46GjnRY/F89801z
45lvjU/IJM2v+X7WUBfLZVAHClTysgXMwAPDxzoKwTRPO1qDi2y1rwxqV7LaFV65q4SE/50F
COKpi6FzxwQd3Ts6duPeqHmrw2eU1BW6LpLRNUAxn8RAbsAlYchsj6QPyOrnjjKP5LvB1iHZ
OiRbh8TXHnpawLQf642g5RvH8rriCuvjghGgS/md25OyuptISTAca3Y7cecnvuFgk6NyxXxZ
ldf31fyUNK7c2c5lt55rcOTy5URbgbDR4B7IQVPLrhSPvRZPvfRR34icAluKxuTsTJV8+vH7
g52eAZr47QENr+Am8IdWdwX87ZdyvMD9drTqWsrHPt9iygHiq2lPIMxuF7bdeq43glzR5vba
l0LlMjeZvqnVjbE0GwS+C9CiprH2a3h958sbPB9LVtidgGLX16Q6XzCWg+LVqW2NRlU25zN3
UHGYFlydTOirAUOlevhwPc7VO2nV1O9ycQ9AYEsupzzvoVP109KUmEirDrQ7zKgIoQV8Yun/
j3W6YMNczERX2j4P6hJdzPClDf1Q7kGBtDTyN5F10KiclMP3J1nQwO/3thb+1sLfWvjRlIM8
mawx32DubT7ZwC2m9tkG/A4Av3UrVFcRyxQS+zYpx2AyoSmmLLDu7g5ZjFlcS75OjmWOmIeX
uTPAo8SeSLDfQpRU50j2WcAPcHIPgjhqZIJPpvS8FR1U5NENE86SGQiLIE8KgvZLVM50mgh+
pTIqb5Z4WGouGmFYKNu3ODEmNy4oJjTkbGoJDZlysNbciYYbW2WNUDhD4o9Pa9822skhhIRb
aPFmD9LyCnZyiMTE+Up7mzAYBqzWgcGOIdtC5cpc+54KNTkxbRJMfMGNo7K30X7Etond29q2
fU5hV+uMq4B9ZJ8pGLHLLOANGGc2vloI9jhooWXH32kLrdqaaFsTbWuieUy0334E9oaOpXEA
Yl0VPhYY71i30cKNevHJqKtwuiCkp9Uj6Fr8FB2UYHG1l+i/JfzVuelAh5+8r2oBKjRd8Yub
gfyAOhr9PJk+cqjlDLtK0atRoQYYOcf9tbUVCWf9e19lNqZdAsATw3vYfFiCs4rDr+XoDWal
eBbPUhEg+31Ro/DYeF0ZnfivbIGlMSkyhE2rMBgL95M9m9af+PttXL6iqVko8Wn9ns3+XEzD
tWoJVH6Mj5atIFpZuSP8UF8+aJZItVOQPD1nham8Yx+j7fO07COZS9gyN9uyck4HBtC1a+sv
k3lrnLMK1zB5XUwBmxbnIaKkzY0ABBgdGL/4uZQ/ApCgJecFuhGvC/kjAPzDAsUmAgQYaVRA
SP8GQP8KIgBzxiPun1JhojSPMlPV37WzrRz+rtrYTJ5ghFb1lXjr9LFB4lo/GxytbGJr0q0L
4WIHvvyhE7UE7ubS6mbgekk5zKn+8mpKHAkLEdM15zp5KGAQDZTHHlE/Ce7w8LbErici6r+o
9FEa6kN+si7ubm6S7OD7VxcNmHfUrtFPdjTyIBWZxS8vqYDt+NW31qFV7mapNFJfi1RoSAVs
eaSh4dWznATxHS2m2qZgON2QlYDqUlnHYGx9GN98QBsWUxMXDVSf8u1E7/TZKnPwnJPGaLcA
uftdl826TguJ5+4ukyXv+W9xIVZSA7t8O1H3jKXxgAfph6rTAwv5voCFQiN9XtzCWmHnI7nT
3c7LKbwDYK7+Lk+gBQ3SyIxU84N9JBMa3gOxv59qroW0T3giV/YEQPLcGaAFMwZNzNiPSKxL
+/utRm6WJrPprafktFYhXRE+u5BLiQ+mWcdHUEZUFaOxa5+xGNFtFpBBAvquPelKOcap6ofh
GVECphPQFJat0naFw2RilzBBYZy+yIzxIEdx1GIU1YAzH20TP+trm32M8buOPLRQbj2XnKPY
RPkInjMu2QCvAq8ssyvbrOi5/0xHQ+A5niEZJOq0DZrTCJoMqbEsmsBwfD8PzW41fB44PYkM
JqHXKgZ6boNGnKtopEK4p9aJ6GunGmxsfm9FQF/mt0X12MpdqQf1raF8bggrsqGgIpmxIhom
+pjclWTdlgl9F0ENIIFvGGMrwWq7Bet3oTHATYxayvibatylo+buGfSmRJpNVhPaIdcHXBDp
YI+B22NqDd7vf9vXjhFMT6r4VEKQlFBNl4h4nfIYgIgQ7em17p6rZoXCGpjmvwtqFufHvaTK
P4A5/x8K4unOJniUzXSJbAK7dVGN70CqNK12rEkjA6ozal8mBzvAduvzj0VqQJQ5QuqEd1AU
noUgWEWmrGHGZ71hMj41qOAvsAutbvBy2Pvl4v31u/zmA1awdURbbD9z0heCs3uAL3upw0MK
GeF5yctnvL0qvyIYXaCVUFfOcct+lJ+UG+B8IKw6p/migNIz4GIB/J0U+Wx5ryaBS6IUQHuZ
OTkBiSCrMBmbVrD4H67OWLSr02wq7sYzzKrS9R1zA+aHl3d38QZfrbRLV1hRkYnYZbg/agAW
TMJOPHRimu4n+I0MtsrHpefflRQTW5X5q95VEKfibj6uHr2GlPabbc/OXm1tQtE6i79Y4Ms9
mKzp6cx6Ogs87fhn/4tc3n8Bi9fFcQHwAAA=

--IS0zKkzwUGydFO0o--


From cyates@uidaho.edu Mon Dec 30 20:08:43 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TAs5-00045F-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 20:07:05 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TAqI-0003hQ-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 20:05:16 -0500
Received: from maila.its.uidaho.edu ([129.101.155.252] helo=rain)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TAdL-0007iA-00
	for bug-commoncpp@gnu.org; Mon, 30 Dec 2002 19:51:51 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H7Y00D07L2CZQ@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Mon, 30 Dec 2002 16:51:49 -0800 (PST)
Date: Mon, 30 Dec 2002 16:51:48 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20021231001633.GA4188@dogbert.sdsl.sun.ac.za>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
 bug-commoncpp@gnu.org
Message-id: <NBBBJJODBJBNJFNIDDCNCENJDDAA.cyates@uidaho.edu>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Subject: RE: Test framework; new counter class
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 31 Dec 2002 01:08:43 -0000

Albert,

I had been stewing over what unit testing framework would be best to use for
common c++, and just in the last few days had decided on cppunit.  This
morning I began writing some cppunit tests for common c++ also.  I have felt
that it needed a good suite of tests instead of the makshift shell script
test programs and thought it would be something I could develop/contribute.

I've written test fixtures for the persistent engine, and have started one
for the various digests (which I am having problems with because of the
strDigest function being protected in the digest subclasses).

I'm glad to see someone else that is interested in pursuing this, as I
wasn't sure if it would be welcome or not.  I had planned to convert all
existing tests to the framework and some of my own, and them push for
adoption (with a lot of the work done).  My primary dev environment right
now is MS Visual C++ 6.0 and so you have a leg up on the unix side.

Anyway, glad to hear about this, and maybe we all can discuss it further.

,chad

> -----Original Message-----
> From: bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org
> [mailto:bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org]On Behalf Of
> Albert Strasheim
> Sent: Monday, December 30, 2002 4:17 PM
> To: bug-commoncpp@gnu.org
> Subject: Test framework; new counter class
>
>
> Hello,
>
> Attached is a patch that contains the following:
>
> - some basic code for a test framework for Common C++ based on the
> CppUnit test library,
>
> - a counter class (called UberCounter for now) meant to unify the
> Counter, MutexCounter and AtomicCounter classes,
>
> - minor tweaks to configure.in and some Makefile.am files related to
> gcc compiler flags.
>
> The patch is against commoncpp2 in CVS on Tue Dec 31 02:00:00 GMT+2 2002
> or thereabouts.
>
> Firstly, a few notes about the proposed test framework.
>
> The CppUnit test library seems to be THE way to test any C++ project.
> Since Common C++ doesn't have much in the way of a test suite at the
> moment (which the exception of a few tests and demos), I think it would
> be wise to incorporate this test framework into the project to ensure a
> robust and bug-free library for everyone.
>
> To run the tests, compile Common C++ as usual, and then cd to the tests
> directory. Now run "make check" to build and run the tests.
>
> On Debian unstable, I currently configure Common C++ as follows:
>
> CC=/usr/bin/gcc-3.2 CXX=/usr/bin/g++-3.2 ./configure \
> --enable-maintainer-mode --with-cppunit-prefix=/home/fullung/opt
>
> For development purposes, I removed the "default" CppUnit from the
> system, and installed a recompiled (with gcc 3.2) CppUnit in
> /home/fullung/opt/{bin,lib,etc.}. This is neccesary due to the
> incompatible ABI changes between gcc 2.9x and gcc 3.2 which prevents
> one from linking code (the tests) compiled with gcc 3.2 against a
> library (default CppUnit) compiled with gcc 2.9x.
>
> This shouldn't be a problem on RedHat 8, which ships with gcc 3.2
> compiled libraries by default, or systems that only ship with gcc
> 2.9x compiled libraries.
>
> I noticed some weirdness when compiling the UberCounter tests with gcc
> 2.95.4, related to the tests for operator!=. If anyone else sees this
> behaviour and/or is able to provide a workaround, I would be most
> interested.
>
> The current tests are by no means complete (or even correct :-)), but it
> should serve as a good example of what can be done. Specifically, I
> still need to spend some time on the Thread tests.
>
> Secondly, some notes about the new counter class, UberCounter.
>
(snip)
>
> Cheers,
>
> Albert
>



From fullung@dogbert.sdsl.sun.ac.za Tue Dec 31 06:12:07 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TKJ9-00071g-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 06:11:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TKJ4-0006sw-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 06:11:35 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TKIl-0004xZ-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 06:11:16 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18TKHj-00086G-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 13:10:11 +0200
Received: (qmail 18033 invoked from network); 31 Dec 2002 11:10:10 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 31 Dec 2002 11:10:10 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18TKHi-0000g7-00
	for <bug-commoncpp@gnu.org>; Tue, 31 Dec 2002 13:10:10 +0200
Date: Tue, 31 Dec 2002 13:10:10 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20021231111009.GD22613@dogbert.sdsl.sun.ac.za>
References: <20021231001633.GA4188@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="FFoLq8A0u+X9iRU8"
Content-Disposition: inline
In-Reply-To: <20021231001633.GA4188@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18TKHj-00086G-00*otzBJoHyNqY*
Subject: Re: Test framework; new counter class
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 31 Dec 2002 11:12:07 -0000


--FFoLq8A0u+X9iRU8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hello,

On Tue, 31 Dec 2002, Albert Strasheim wrote:

> Attached is a patch that contains the following:

New patch attached. diff'd against the same CVS snapshot.
 
> - some basic code for a test framework for Common C++ based on the 
> CppUnit test library,
> 
> - a counter class (called UberCounter for now) meant to unify the 
> Counter, MutexCounter and AtomicCounter classes,

I've cleaned this up quite a bit. I've added reasonably complete doxygen 
documentation, and moved a bunch of methods that were public but are 
supposed to be protected.

For some reason, doxygen isn't convinced that UberCounter is in the 
Common C++ namespace, though. Also, some @c's aren't resolving...
 
> - minor tweaks to configure.in and some Makefile.am files related to 
> gcc compiler flags.
> 
> The patch is against commoncpp2 in CVS on Tue Dec 31 02:00:00 GMT+2 2002 
> or thereabouts.

The rest of the stuff is still there. I don't have the energy to split 
up the patch into the various possibilities. :-)

Cheers,

Albert

--FFoLq8A0u+X9iRU8
Content-Type: application/octet-stream
Content-Disposition: attachment; filename="tstcntcnf2.patch.gz"
Content-Transfer-Encoding: base64

H4sICIh5ET4AA3RzdGNudGNuZjIucGF0Y2gA7D1tc9pI0p/Dr5iwrj0cJNlgZ5Pg2GuCsUMd
xi7Am+SSFCtLg9FGSDyS8Mvu5fnt190zekXC4Dh7dVXx7trDvPR093T3dPcMs6Y1HjN13vOY
4U6nrmPMZnXN9ayrLcN1xtbV3OOa5SQbHX6Taiupqrp08JP69nZdrdXVnW1We9HYedmo/aJt
hz+sug3tpWq1umySGEaNbdcaz181tncWYBweMvXFK+Ulq8LvWp0dHpbY2WA4ar1/P+q13406
vc5Q1AxOOqPBsHt+1oeKkvoTa3qc3XA29y3nigUTzk56F4jPzLK592tJbZ6OWme9o86wc9Zr
disnrRZ8Pj3vdNt9JeB+wMobUFdm++yO+5ul6n0QWWeMPRXm84C9a/Z7o+Nu82RQqopys3sy
2C9VrTEj4LcIHGDfwpA9BOaUqk/iUftl9Z1u20zVHd9i6oybuhNYRrlUHVularM1Gly8GQwr
8YBNIJr9xIYTy2f+xJ3bJrvkzHICfuXpATfZjRVMCGkXfnkRE9l47hiB5To+dGbT3S3XD0bG
7a023S0xmKfb7J2MBs3f2rQUte2XygtWrdXq8AfXIsKEhl2PzDvHdnWTexKfwaAbcoi5M5wH
GN8aNfsno3ed4duK79sKi38+qiriqUI1S/28mVtAkTvjDjb589nM9YLPCrGiEBhjy8GdAThE
MAbHnsDnfYQji+XyZoJIqNkUfKi/Un4BPuzsKLUdYkSi15vmoD3qdt4gC0Bquq4BC8Bas9mF
YwVs7HokASBDgP3p6Lw5fDtqnZ9fgCRXatpLbRtkDcd9cOfM0B0Sp/mMQUmfB+5U/8KBo45p
ITN1G+pNkEhY6oAFbrLFvkMol0QpKOAcJlel6KIAzjwXJGPqa4RFUhPewmqHGClMqoL8jHQN
yogh0nt2MTy/GFZ8z9gyjCtnXleFgjOsOQVMx7juN5azU48/AnfjDyBwYbnETDcxyuRTN/5k
OYY9N/lihWFUq3FtVAj4dGYD2+Omscf5pW9uzb5cqTPb8oMSg6LljN2kkfJn3Ii6Zihogb7U
Nc8glvgx3iQQu7vKcxCI588VIQ8+qJwKxD4tHwYTb+ZB19vD8tPyRvSp/DTscDHoj8777ePO
e+oRNX8CIaQu583WP5sn7aeIwSj8IEb/1u4PYNlEU/iBvRbroAXTGTuQ5UmJGSbTtC1NK6nw
j1m4TaRYr+nTrBXPtuduF9lOD90ylsIBIPXGTj1326jVlFoNbRXsHrgip81Obwj/tfutbrvZ
OwZDPwADHIEG8xeLYom13w/7zdFRZzCETv128+i0zfQZ913ji2b6s0T5JoZxaQjp0G6ndkkF
W5/cVUoqrBEZa4B4GJYP2UZl+BYnkIac5Vr+ksptn68IAjqDGRijHVltyo30TtLptboXR8Qe
tbNRCdzZCDTatLzNLal3JdY9ah4dQQcQKNR227oUJkCz9Rg8WguEfvShN+qeNY/afYD+L6pG
2PafS6QwV8NzpLGoX65UFnWWUlUDRWb1ncZ2vVF7sYp03gOPpLReb+zWGru7uVJa38UNlX6j
kD4ZBzNtwq48dz7zoTC1fAP+ODy4cb0vWJpPL7mHTTP4A2YMSj73LN3Ggu2CnpPdQNnk1Bh4
xkT3NNz8Pa6bUICt4Bb/eDgGJBWBea7BfV/UwhDYJiSgmQVbOwycMihNdceaYcFns6haFrQA
hH9mRZ0TtZ9KKsEZ35g0eGTBZgQGqZpXCyyeg9viocEqsS+wKYwmHF0KH0QGMTKmJrgSjk9d
cTWoIGwcM60rTkzhtwYnh4PKuL9DgVYH6VpR7CJUlq57jPC9Ihd1fVJ79WJb3a7BvwykbXsb
/l1b4GJoCV8aLOLz5+BO54rbtgKfasrOL9sobtWtLdZyZ3eA5iRgldYmQzgK/NphTRvkLGCD
wNP9CbemGvVm9Ju8TOlAMCjihsl8dxzc6B7fY3fSc/G4iVJgXc4D8k/AVdkC72fqAvfvCBBU
zh1YWnJMgZKpz9xx5FqfcId74OKczy9ty2BdywD3jzMd5sYaQAucXAEIhxwjFgOJBTsG3pg6
CsAe4xb5vNeoMa7D6uEkEqLCXI+gVPQAkfekq7oJGN8xdCOisYILuUyIaTXRlUb4E3BYoQBQ
gdAbC6z6JYYPfDwHBxNhQG+Gris4UqzZ+4BhQ7/ZG37YI3fdhVZ+zQUsCxwaC/143fNgR7gD
GgjEKexnb2FM802n2xl+AFLYcWfYaw8G7Pisz5rsvNkfdloX3WafnV/0z88GbY2xAUfEOEFY
wuoxLZeH3ligW7afIB/dUxloTPRrDottcOsaENRBZGd3968jQdFtFxxSGZvE/NxjsHc6bqCw
G88C4QHPdnGFCUC8zArrOIamsOev2BC9P87Obd3gTGWDOcLY2dlW2BswVtj1tAlaV0N7v7P9
QmEXg2aCtKYPRKAnCFY1tiMhEsUUKWiTwWKTkAExBOwKVwvYgqzUzchtBymIZD3gtwFaMGCx
I4THCnxgqM11X5IJPVtkCFirWk0JIU9gCHOitCnIPVRC23K+0AzxWKi79HTvTvCcYkEChJbR
RxJhBcw5sA30l99yYx7olzZQRqtjutAHlgW0DlHk9hj0HIOPUJQ87s9tDG0SYxHoJcYsoEKk
sPdwUQvFy6O4hngEGpQAaFGs6rigC3c4JaidgSwGCnWDbGKoHMiAMFjP4YHhmhQju0BNVrNj
rkZUT9wbUEcPRlzrtmViVIcGQgTUsNn5GEXfTGKLlMBZRDtkZ9dnRh5W+gztAciQY9+Fokn0
SLkxE5aVxjv6NMkEMAIdISWkrjR07LnTiByC4gv2RDott4wQiILGmCjItx+kD4GvSG4kOSpw
Aq4iIWkKaL0RM9AXYUqBclhrQHkIuFy7lomOESBoUhSNdsS5cx3aGiQgP9CDOWmYPzcmYs9B
80lyrhD06RwiWxPoDLhcsRSDATegQvAEIE4TSyEZJ2yTAG3oIonijuUOcuOQyid5BZsAzEDN
xsQF4ATsZsKJ46h7xK4sIsj/kEc0ODWjlsTIdImlN7A3Sksg6MunTcPtvFT9yRqDpICBwRCy
dXbRG7b7o7dQD5VgkBbqcYTwQiDORDckdCwPsG1rC+LY03YDfFZgN6YkJtz4Qrzw7/wtPXCn
Frq0mLfQ/WlUkYSarD+IEaHERHN4dtppSbwjtHvN0/YAIuP2oFRFQfdnaPrB2Jeqf0HPKBza
evasVGXP2AU4Ny3hPeGakLELQGQt1FXpVjHD1n1f7t9+lFIgO0MGD+CEXa91cMFhrEYWWQzU
bZ/M6bVlctxRbizUTt25IqMGumld4xCCMwUZcE05GYR/7o0vdgxmgJQCJ/7UI8zQoIX+Ou1V
iLyOO55CsA4NMDEwmJ+BPOnCWACzoVofA65xLfpowiGhhbIhZBDpJAeLBEsHLYHtCZt9fcyv
5rpnSkUVhE85xiMx/TiKRkop6KWkgMjD4VPw9afzqQxnkB+CA4CTbQNJsL1fclJuZI5OZhra
0CCBvni048QsjNgn5H+C0UsSiYHwUwTe0xlCd4kLLgQVwAGaADZgP/g1wv9QnwNMb8EPBumk
mkPTvcK/mm/6tubPHU03tD/1AzEYPCMY1C6QKUJuq1QNRep1cDfjZJ+HMF5IT0JCSYbJ5TUa
MBJ+hBjjzzPWBh6GK0rmjpKZwHVYOaJQC7tuiQJOhorDYSA7FZ1EC0zzRI5qghdz5Uy5Eyhx
5TllpsDN8nhuyxHPaQElLBokmvJGNaWnlKg6gpANVt5Bs4nIfg1x3xOf1+CMEIL7mdOK+sX8
ice2/2+uox+fqOq5QU7tCZhHWMZ0ZRfUN7dbDgDsS9Uh5TFihcS3CBoaBwvkWncMsjoJqYoo
Z1HhEIFCMANxOLq+4V/wduY8dFaNUCZTbEvArQzDgfvbm6whBlRk1eZfX9EMZ5E9QifOvUub
ZYl2doWuLS8AVrD/T86ZhAvbYZ8Hc88Rrkke9loa1JBd8eA37FfZFHYgxdZhZC32gTiCt7m3
2EQDkyT8zIywX5JYoSuYwRZiH4EAaw7uq2eSx+qSp9p0wJ6JjV6JAPwm49jnWl3bNhTWmugz
5Ngr4WeJ/HHCwskwzSOmMD2CA/2EQoVOk3v5BzeCLMNTFIVQq9VKRBswXNJk8gWalsBQ1TQM
YQ7yGJNlNswOfmne4EIMhslpE4MTQJesbnX58iaALwGiLgdy6bp2LE4LcLLNK4N6uhzU0zVA
vV4K6fXqgA6WAjpYA6PlxL1eg7iD5aAOikGBNxZwDEEbsUC2ih0kEgqyRHt5xrC54NhEPug8
sGzrTxE4gj9nTNCblDPF9gFbhJsTNoUOYGjmpIOIAQf8naLBoUg2dA39CJbwdRf93AKjTLFZ
xvsUxjl/l/o7aCWvF53qBH0ZuiJwIX0ip3XJuRPyiJtLaU671g8kGZ3ffIIlESLsEHCySwIo
+wLjMNiNEM5u8MgHYfClbAsMoiC5eJ9P0ew6LcLRrEhPjOA9BumpFV2LdjmUYg7fncrtf11O
xFBW5oQcUYlds4dww5XLXui5LGqgSAxJABm9oUwIckECiaiUAdO6fMGFQvzCnFpWfeRogXhM
gsgAUpxJF4+cP+Slk8StFDnPIkLSbVlgSKTMBQszTGtQSkYVJi09uKgr22A3Ch4LFwdTNY5M
qkYWBeVv2SIlF+ixFokQ/S+tkixmGEQI+YWrRVttWu+zqhQtGi7Z171sOucUExXJnE5BHocW
FjOBmNgDY5MKtDHlIbYPAifXTQCgDJHpr5xfIWiLeZWH5VRWyBakGNAQZ2Qp8l4PD5SwGtzl
RoNGLM8uFIeRyekePZZMAs8GlGmKosgyCtHxT26U2XUNcRwi+C99oLTjQ6mnaMu/z03IugSW
Y2OiMt8LinMIHIERiVEAVLhLXAihidHOdWdy3JU4TZm/Zy7DPevNxKjbHGZaQH1RG5uUvk2n
WOk2IurjvXpZknnMZLoCc9wyhSNSozRDxqeTU/gAUCjztW7ZiRMsMSWevniUlV1wLHMcyqRV
iJxKUF66iidPvzzujuPcZ2csZgvRhaKtG3gSpUTaj5uATLzy6Rz1Woy55LCWlghbBbTe2bDd
oLzyO7yHlkN4JpGLR8UUAwsLFNGtiPNmAQST0xI/P5+XeDQrUpXCCiZOL8NLo7ptBXh2JK+b
4j0LuX3IbTCR7ywlErJtPNXGKxjLFxQnzVtAAmV6+pUvD5ATwhW5hGTfkwmlKLBwkFGhVU2d
flwM2qN3nd5OPTpmiM1rWqJz7SvgcCDMaSIglMcUqcMLUnI8aRYko0EvCBQFU0aBLOzhYQZe
BItAnC7fSzLgRG+0KHvJY5EFq7+uE/q/4T/meSaRuCnyfIxkUeTQIiBxSgrtwCyT7FLYzcQy
JiH47QXDGix1RbF9qTPaWt3tfFi48z08xsdzEVdyDSMmUj4m9GYKdS/Hw2EOv1lwclJKX8jW
0LmhezrrOTqpCTAvmfB14l1XWgGfB5WfRVkJ+yV24dgorJj/xumyme940jBfLObGI95w8sSc
0hr9dKN7DkpPuecG8hsSC/a8/C3M/5t5n/Ez0bIXeprFdvTdRN7e8u98cN/jqyThvrfAI7nN
RZFiBCp1Sht7g6S/ken370kVLO5jEUZX4gaHfRfGpklEFiX/yEW/RMZEuV23QnawsYU+w7Ot
+/zicCtOqesTJFjLeMwhx+UC4J+/hfnzrDP+v8f+Qtd+CfczTn+G+1/3cszAIqm4rQrfE5N1
dIsM45XIWQUO3/GgnFSnohseX/fSvVK3UUITFxgGXUhJXf5g7dNma8BkoIJfzbGjdfIbVDl1
Td5gAIk+Geql7luG6o7HYH0bbJdq2w6l+oHJa14kxtvQq9zohX6rXyaGzo96nRjhJS8U1xq7
Lxq7tWUXiusvflwo/nGh+MeF4h8Xin9cKP5xofjHheIfF4qzF4qHrVbBlWJqedh13vwjkWHm
iKDRWOEkcJNAU74hG6BEF3kgIoa+8qMPBs+YVOiQNxUR4jVVtnCNsiEiahjP9llFGJX9OGXx
5BL0/cteDgRp4vPGV1cBEN+bzAOhrgIic+8zBadaDW+y3DM8uuaZGq6q9w/P3CBNjafR1eoK
4/Pnp/Gqmh0vg8pssCRb44sPtPqyVuZLIiH5WiyhlNJaENIVTz/vFVSCvoasZq60psWESVGV
csLyBWXxCmwulKerQpF3YXOBHBTAyIDAS7PyQFMsThrK6wQU2ed+fIopO1iVsuguby6Y14Vg
7pXI8ALKA0Vy0WguZgb/CjOM8hiHHBkMHYXHrot+I6A4eK1p2kEFd4lNNtUNz/01zrvFkzwj
HQV3ZkT7yX4SQKanBCYJSw5TD+6z2KGe5w4u4Og3sW7xvnDEPAk3vSMtXrpP3HR42MS5dxXX
xsLQYim4B5k0Kj8XooY3hyM8chHIbDeZFXmGy/Y4qOAF5FVQibaO9VEpXiJ5h3mlJclugQ+W
C3n3eZ1JU8Q/jNJ11SD88sc3KkHRpe01kVhDB5Ywfk0exF7bt3Kh6Nb52miswYdc/ybnavsC
DmkXKPtdm5U4cd/cqzHjHkQeixdPH8CL6EtG386Oorv/D8DlsTjyen2G0Fepvp0ZBV9fWBON
x+LDwfp8CL9n9u2sKPgCxvqYPJpUPEBPIk/7MWTjWxUlgcyjScgDeJL6juEjyMm3siWNTy5n
VjwE/C+d8k13t+Tjetp0N3u6lmrMPc9L9XjoIV4aSPqdtee/NJ7nv48mT+5eioM707HpF8s+
SfjxtNPrnF6cqvJxOYV9bLbwpUC1c6wen130jthHhcVVvbOhqP78+fOmhNtsjY7axxe9Sga4
Uqp+xCVLPuIYPlUoLlkp8SOO6Yb98+P3IF/ye4fiO+HhE4uUzvcD8Y2Sijh60+3Nz+G3huSP
BDgSb0eNJNzyBs4GmlFWinrg+4d5KGN2vhjvRKtAvg0V4V2yxyAAJ1iBilQ3esoRgMbPkhb3
xuzNLQsfK83DQPeufJg6pxaYkaR/ySzyklACo7/CtydbZ73jzkkVNPQr4YIvY6bQgZ9032UT
bV1aTqg38t1KCWZMl9fE70LGPApPCtjxd3BidSbgXxB3Utzz/tlJJQ05EjA5XmGOS0nGcEJ5
0j2aWs7+Ri2Cdzo4GbXetlv/7PROKnSyIfozNTpXP9hnGzlQCLrjjmQTSHFypeK3SgV++IJv
2XHLKQYlRt9xuucT36qNhouXeH/PwMOU9djWr/zf093xUcO8zrZ1GXbN0JLXWzb9Ht4mC4dM
9T9cLx7IjYm7wBv2b/YpZSHw0O4f/tanyseP2+qrz5+ffdrUCj9sfapt/SODKDD7u89az5nV
8NzvPOsOzZrHYxTT/Dmx6Xvx+PvOWsTj7ztrHo9D8DMPfUiY/HbmJWfZyBV49ukg24L4ffr3
KkP3c4f+nD80KfDpWcNl+v6z7ufOWjQ0oSuA8H62CcdGqxDbyPz1IFtZK2f2Emms++3BRRcc
wnyKtXxqtHxMP8tjqNjqZqeRm0i+sc5uTxFdtxtxZyQmszdbY5wQSKh/VpjCGuDMQnGT2tKb
QHYXKJcz9WTuy+Us4J0Y8I4gMrGFivfB05A3c9vo4dxS9TO5Z/BPcQCSfGo753XcTHNuEJLp
k/NS88tVwpAlYOo7jZ16o/Y8/6HmulLDt7Pr+F4zPoIbP728n3pWnP6vBal3xunVeXxZqo7R
V+oZZnwpFqJJcJ7xPV1RMGShphkl1h2G72XvH0I5+YD24fK3m9WOePSYqUc0qv0e/68DuGb9
Zv/DsneW8SHcw/en3ZFsx9eVCcRRp7/84edqiX1/DKJ3o4txzLwU3Yofly56ivqnzGvSMazE
LKXqSr1Y9yiaUBZxxngpgYnhNTeq7re77eagTf83At2wMRNgWh4M36iYeqDTk9aynmRxt4bv
+u+8gN8oifSqNb8N6iNbHw3OLvotQvByjllxDSQftHvsUmFmzTgVwheasZx6rhgr8M1l/Iuv
LtMo+Ygzljl+L0rAkK8YhyD+096TLcdxJPcMfUWD4ZWawAAz0wBICmdoRdq7D5I2CDDWsQ4H
oolpDCc4BzwHIYSX++3OzLqyzu45tILt0YM46M7KysqqzsqrsjAzjP6QdaHx56h3Qv/OPpUC
MxZ1JormD7IhFV2+7Q8nH8vhTBI5oR+i8nLwlT4igmB0h8MDHoSfY91kTJLEc3ZTTDiURZlr
RBPDFpIXvLOYaGIwq3pIXDR2ueSiOD0JV+eWPpJu9802u3mb3bzNbt5mN2+zm7fZzdvs5v/f
2c3B42ai+vEqScyhQ8p4GNU7QpfOYzYnoFX0DZ/oBLiOSF3yMkH/2+ROhnKWhQUeOn9sVcpj
CZaJ88JWimUkydnqEFZ0Tv20Mg/VWh1aSdH2GBcff5su/SRqq19YVT6qdlt2iTK8PwbVoteo
F57rbPXSqzbTi5+SvQyHUkNO9+gPbKkeg8NnPYok22B6dzAfVAfH3e+0cbUC9a16OdupD9VP
2M4cZuRBdthZ3FmY4cFU7ob4d5fCb5K8G6K/XAZ7NP87iDqdDp7OBm9K/VLM4XniTceQ7kAv
7kCmeGB1L3UMO+4EsC/LC3goPYCgI8CDCngp/SuPAq6ABKJu1ungPaRF+O4kvFCOLr9sdV9t
6ka53oToOUQFBD0+8C+YsQ+L+eEcjJwvd68OR+XnZ3CT3EGDK+FWumvO9fsFEEML12W+qdvn
YFbGE0y1oMD2+x9+Et69fhf/V2TiYouu/LeQbrlsfvcARlQXnXldvOPz5t31DTZUkQ6a0m/2
yTHNEQNhCEm3Z2Inlkex31UeN+zaflXQK1yDR9+3jrL9ozetLqXtEAkMFv8UaOhFiEvozRRc
Qr+qYtHf9C9qQ1eXWsNhnZjwz2BMfj0EuBX1EvFutX36+0bdNsf/0tA/qntKFYB5IHyXAold
fkeCXlej8uETaCn+A96W1477hGLMHs/yvAHE/2IHaAy76uSfx7OgVHKhEpLQBV3VMxrB5snE
Y/86ROYgPXm99Y9u/aOr+Uf/r7pHLU+B+L7ai0EbvZftG/jq3i/GY+k30IAvuCh94b1QMtV/
w+Sp/5IJTP+lI2J9AEuOvsBxofWCkoJKZpXT/l0LD49M9/D3l//4T5P9K/MZT09vYNAfBviv
Gnc2pX+koiqThQVHwOhHuFwUK8Sfp6czZHr+Umu2LqjgTDNYzatm4Jp7zcAtfjZrwjiMD86p
Nq9bfSy7XAMRL6fbFNs3+zuCq1WP44TWrbXwxqm0WOcgAhtEFVZsmzJY8hzqqHwCSeiXnOIS
RdVdBRn8WD5daRR/RecnytIZQoE4F2BUcGzWrn4lfywKVtyCxJVeosKuxvBCVOGqei/8imJu
Oa4VeGwPyWULK8UlccM/7iHWjvJX/HNz44VuEVTkglpICDKhAoXA11ODghi5KtTFm6E74TQW
qQq97m5Voa0qtFWFXFWIlYRBK1hGOmLXTYZBQiqVvLcRZG37T9UQBO9PWG1gZutVgXsqRWFn
b7c2hZ2Z8jKb/+vgV5CkldFspBlIdF5/+PPNu8DOr3dADp2TzfqLvpwrBCMw3r77+W0eul6I
tgZ7W8CNhyJR3Zb5XZw5hf09CnOsc2ra5i9567xbHHm1To22RnFFayy8Trwazg/X1+/ew6Bh
S8tNR+SJ7ogiF0nIgiCBkDDs/r7BSYBhsEZABwemV9FpUYMtDcaGi4V6uidiKK8akRiBYozB
yj2FZE8nwkqHUgkmVakkwRfZUadDyI+olYgRUU3h7qurXV3wc8dtw3SSmjEexajezXYZZDOK
C4xwslXlkVfIEGg9cUVibe4yKO/6g9/rCCLTXWwvWlzHseDqVCwLeAMKlo3PUa+OToukp6nb
Pd7qV1v9aqtfRVxNIXfQN/u0Vzt+DwT8EcutD/8ywT33pafcaKkn4yAHl4MZem8G4z4z7/XL
2bycznNXn1FImuF4LAeIArYb/GWu35GU47RiTlkdnf1qftufzG8xkaUchomdPJiOMOkNk8RY
T+IGKeLPUFzy9IBsWpZD3G/RttBRKiAsHNEUj2X2bvdo1LBoxGa70jDVNvQ1NfHXssUzmvOV
51TPGZAj3t2XsPvT5PYm4+/m2cfppOxhUbFMAHA1lpRp4YQ5PZ0Nq+ohP+l0FO6acTVeZ8sy
OTl5f1TD4dWrcPkIdCpcmWvGRKcNOFQO8dkTafIq7ydCZ3EYn8fisMlScDFoDocXg2q07gqJ
jmcTa+osw1RKyXq5sTzS1VAPy66zdpuhArpEaiZbss0X4t//ntUOst3+OKH9C+FQDejhwAC8
tt/dPN7zt99GezZdD+6TX5G2I5XmP5v3MKsK1Irzc9jjZFweWSQavcDnBATSb8j1/PDKkpYs
WgmMlhCvGpFSLEGKs5y/WnOB6oHakMp+ORjHluN8uhCr0cg2M2mggTzWrD0wBtcWcrFvfEmp
aARIvaj0RVBSUt4MRlXvr8TuZ7PTFSedNURZWoy023iZ6BxGDaYNqb2Hh3SPG141Ug113ON3
2tCegV2cCj0wqOY28SZCDhybZw8fJ8MN3aOTrT28tYe39nBdvOHHX35++2csUhWONVivNx9n
4Or5qXUHr5Dl3q2RKF1lnWJ2V68ITvOtQIuOcrhHvSh5DXsArLrbOf1SeRaUZY670C1oCK3M
SHo3UsDozf1+Snz9MjvV4WsMHIzE/VAtapsLkJboPe/AL9Wt1KThs9lhO4146EYbxI9/cGpY
jAHFzGBcYjD8zGlCCoHYqprD0/ZsGFcS7dY9fDRG9zKyHTWy7CJDtQwfUVM6lCC5L5uGr89l
k+NtwM6lfAJIA9ziJ3oWpcwBBILYlIO2QCcg8X+TSYZ552Ngw1WMWHUhoN+7HIa7fomplI5g
6FfmE92jJlItHj/hYT+l9d5PprbPRw1acVmNhFaM5rVa6DUMcZGov51pFLi1rUdeGamO76C5
YKOB4e3g2NR3N1XY9eTjG8M23sG0wtpd5h0Af41OQLpr5JjUMQ0VL1X3YX54hKkFbJq4RCB5
MrqievZMC7JM0MGFMwrLAqTYaHYlGsvFImImQjpamvsaEVgbTzz6ytyerpPOBxausgQ27Y7x
MnJ8WG2QrBz3ZYI429MfyZkntveUyu6KdotJeUTkCvlZzT9YAtR4Ry/owk6XILFAlHUuYLjs
9hxSdn/zqpy+nTxa8kIfyFRjUU/cobuoHOf2mfNSOUDd58y35r5ixuTZM4r5qcT7uHkhIeps
Ggm2AXtGYXJsmZOaSwS3tszWltnaMg1smZ8+3Lz797Ado19xqwSXwLhvGyqw78KXdLl5U4e0
hqVtHXKYCjqlsMcj88pbPJ5/q+oSceOH5Myeus5e69CkhkzGylaKK6OwkPLs7ExpUcrDq+lR
Xl5DEPl8ocPJAxBqe3r1H/fDxewT9/siPqTx4NK9xrhph1j4DNbcAHeUWUVXrNudAxLCkqWp
oKvokY9KQzVMFe9BweTcI85Ibilid5KUUmuPN9hsJ0HbTtytuSM3d/q33ZZf90dxDf0M+m1l
oGXCJ/VYiW9eX858JRuJlZ7re5kvLjgPdB/q9f5FdrLM3KB+jKvWmyB/TpouE1fl1gtecehp
UA17Kn43BJNFVCFRkRyQTP2JpW1bGiD/QnP+4ZVj4id9bqXkR8v61EoksEUj8z61W9cjYDiV
E2byDYgT8Qo7PEKMOeElnwDHmNvoXVUV/5EeAmtIdSY/Nz30GZM1zA6DI24kvK/uFrBXf6kS
MDePkxs5g6taB3KalOizpl2TSVmf0l0T52nYBBBigan/njPDwZBQ6rkzK5xaqrnmkeDJ0h20
pRWPBZWo7YGgwKUFKsAI1SYRGqE6QuT7EPuRl+cnu5hPn96xXoSskO/cbzTyeBnMvxkVcQab
Jcc5rLcJ8mF1BHeVWUff5Ex93QVVJxp/N1ed20kI3VwFa1/oj1+6CluZiGGGGxaqYRFoKGPx
xtZkyQc6ysoeBXaXQsY/YWDKPyGqyIrVCtrfA1aLApGv9hJLeDwDu88+9Rw3xiy4OhvQAt6A
JWjjc+zBN6fHr9L24PZY8dYe3NqD6VxP+3SvzIVwDq0iIHqusIrSyqkQsZSM3y5xgjImUbGf
lffV8Ak1+cWokoXhVMBgPHm8Ih8ziNsnnI9Dobx3owkTlIEByPuDL9qzmGHiBKkH+vCAoEBz
ElSeqodJof2KeClIHVXwBfRst6/mS6OUuHDO6FLUF5ukPp2U8jDBNMFGqyIIPgOCANXDhHlY
FbHyNC9SKgaEBSvnExF+wY8cW4nDuFi2z8oFjjGK95DMeqkdmKSc3Yqrz4lslA+JKZcMohyf
T7j2P1ZzEPtX9YP0yYiAR0eJ+L+m5AvKlppUqxoWhnjSCEV3fRRF3UQ+G6H4u673rjOU1YXc
JoYS+7iWWHfJJX0zfXJWNNhiFIBVtsrjrbJzqA90eqhHhXyUHMeuwRBMrl79k9DzZDqomak0
JWvMlUG8CUFbx8hIlrp53ZANYTyrs4FTuKEtoRHXvd6iTVb9TH6ejP9WTSfvqxlYJXdVvYJ5
tJQsPW4GjdQXcbGue24iryIEriuvjpaQV95QXNF73GwoEe6tO5TjdYbC1tQzcJ+kQucMqrnr
ZBMhdI7NcZu8Pj2pSQneHpHduk22bpPaMPo1CJ6//OmX9+/CoXTr9ebj5CgZlw6T03stG/YI
Cf2U4rcmZZhidkJmJwPjGi07NhXJqBTYWOZgKtHVikcxBuTuuEp86cYTNVW5eN2SQ4kkD5st
7B+8q7rooGmmE3L1LhdKxhUva/JOGRCwSs9AiFlZJihQ6bY2fkkkD2E6NoleS2zQwbXUICPC
JAWYBTFXRhFPDtiJjNtfHpHU1h1VqNqK9weD3vHAts2J6KKyVp546K4dzl9L410jTGzjiYeB
laM2AaJ8LalgspimBISjtq8cc3bEUfcs/q448z59nqcaeZVodRR/dXzmrA6L/8tHvmlsPPKt
8Yk1SeMLvy8CebF8DWpHgQpeNoA5isDwvo5TMOFh1+bgIlvtJ0fek8J7wjN31SLhfxcJgnjo
4sx5Y5yO7hvtu3FfeNbq2TMK6gpZVxPRNUB1NomB3IBJwpDZFkkXkPk3hDKL5M3R1iDZGiRb
gyRWHnpUwbCf/ELQ8otjcV3xhNVxQQ/QtTzntlJUdxMhCYZjzWon7vjEGQ42OEpXLBfzye3D
fHpOElfubJeyWs8tGHLlYqi1QNhocA/koLmlV4pmb0WrlzHqg8jJsaVozC4uVMpnHH/c2Rnp
IMTvCGh6BjeBPzW7S+BvPpWDGe63vWXnUjb77SZTdlA/m/YA0ux2YZvN53o9yBkNl9e+FiKX
mcl0plYXxtJsEPiuQIqawtpv4fOdLu7w0iuZYXcKgl0/k+J8xlgOgleHtjUaldlcjt1OP1aY
AQBPh0M6NWCoVI3b63HOr6Tlid/F7AGAQJdcjHjcQ4fqRxOTYiK1OpDuMKIqhRbwian/XyzT
BRumYiQ60/Z5UJfpZIbfW9FPxR4USEMlfxNRB43KCTl8f1okFfxuZ6vhbzX8rYZfG3KQN5MF
4w3m3eaDDVxjah5twHMAeNatUlVFLFVI7NskHJPBhJBPWWDd3z9jPmbxLPtDdiJjxNy9zI0B
7iWOeILjGqKkukSyLxJ2gBN7EMRRIRNsmVN7yzuoyKMXxp0lIxAWQZEQBO2XKJzpNhE8pdKb
3C3wttNSFMKwUDYvcWJUbpxQDGjI0XgBDRlysObc8YYbXWUNVzhDEvdPa9u2tpJDCgnX0OqL
PUjNK1nJocYnzmc6WoTBMGC5Cgy2D9leVO6aa15TwVsnpkyC8S+4flT2NdpNbJ3Yfa112+fk
drXuuEroR/adgjV6mQW8AeXMxue5YE+SGlpx8kZraPOtirZV0bYqWkRF+/BHYG/qWhoHoK6q
wpcK/R3rFlq4Ux8+KXVzHC4s0vP5E8haPIoOQrC6aWX6bwl/c2kq0OGR92U1QIVmT/ziaiC/
oI56v8xGTxxqMcaqUvRpzFEC9Jzr/prqioTTP++r1MZ8jwDwdvAOFh+W4Czj8A+y94BaKdri
XSoC5KArchSegs+V0on/yhJYGpMiQ+i0CoPRcL/ao2l8xD+u4/IZzc1EiaP1LZv9pRiGq9US
qDyMj5qtIFppuT08qC8bmilS5RQkTy9ZYiqv2Mdo+21K9tGay9g0h3VZOaZDA+jqtf7HZL4a
567CNVReF1NCp8VxCC9puBCAAKPL4Wc/T+SPBCRIyWmFZsTbSv5IAP8ww2VTAwQYqVdASP8m
QP8NlgCMGa+zXyXDREkepaaqv727rRz+LlvYTN5ghFr1jfjq9LVB4lm3ODpeWsXWpFsP0skO
fPpTN2oJ3OHU6jCwn1IOY/I/Xk2Js8JSxOyZe50iFDCIAOV1TdRPgmu37ydY9UR4/WdzfZWG
OshP2kX/7i4rDr9/dRXAvKt2jW62q5EnqSgsfkVJBWwnr15bl1a5m6WSSF29pFJdKmDLIk11
r9pyEsQ5Wgy1jUBxuiMtAcWl0o5B2fo8uPuMOiyGJq4CVJ/z7UTv9MUyY4jck8ZotwC5+e2v
TV+mpZbn/j5bS9H73+oXsVo1sMs3W+qRvjQesCDjUD49MJGfKpgoVNKn1T3MFVY+kjvd/XQy
gm8A1NVf5Q20IEGCzMg1P9ghmVT3EYiDg1xzLSV90gO5sQcAK88dAWowA5DEjP2IxHp0cNCo
5/BqMpveekJOSxWSFem7C/kqicGEZXwNyhpRxWjcs+9YrJFtFpBBAvKuOelKONZT1U3DM6IE
zE5CUli6StMZTpOJVcIEhfX01YwYL3IUVy3WojrizEfdJM56b7OvY/y+sx4aCLeOS85x3UB5
D5E7LlkHrxKfLNMrm8zoZfxOR0PgJd4hmSTqvAma8xo0BVJjaTSJ7vh+nhrdcvgicHoQBQxC
z1Ud6KUNWmNc1XoqhHlq3Yi+dqjBxha3VgT0dXlfzZ8amSu+U9/qKmaGsCQbciqSGiu8YaKO
SX9C2u0ko3MRVAAS+IY+tglobfeg/c40BniJXkvpf1OFu7TX3L2D3qRIs8FqQnfI9AETRBrY
A+D2gEqDd7uvu9owguFJEZ9LCFollNMlPF7n3AcgPEQtPdd7l6pYodAGRuWvgprZ5Uknm5ef
QZ3/L3Li6comeJXNaIFsAr11Nh/0YVVpWm1fk0YGVBdUvkx2dojl1qdfqtyAKHWExAmvoCgs
C0Gw8kxZ3QwuOmfZ4Nyggr9AL7SqwctuHxazT7cfy7vPmMG2I8pix5mTfys42wJ8xUvtHlLI
CM9Lnj4TrVX5gmB0glZGVTkHDetRflVmgHNAWFVOi3kBpWXAlwXwd1iV48WDGgROiRIAzdfM
6SmsCNIKs4EpBYv/4ewMRLk6zaaqPxhjVJWe75oXMD58vL+PL/hs5Xv0hCUVGY9dgfujBmDO
JKzEQzem6XqC30lnq2wuLf89STGxVam/6luF5VT1p4P5U1SR0nazbdnZs61VKJpn8RdzfLkX
k4VaF1brItHasc/+GbG8/wH98djf2gQBAA==

--FFoLq8A0u+X9iRU8--


From cyates@uidaho.edu Tue Dec 31 13:35:27 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TREJ-0001cT-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 13:35:07 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TRE9-0001Lh-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 13:34:58 -0500
Received: from mailb.its.uidaho.edu ([129.101.155.251] helo=snow)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TRDx-00011P-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 13:34:45 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H7Z00MC4Y9WK5@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Tue, 31 Dec 2002 10:34:44 -0800 (PST)
Date: Tue, 31 Dec 2002 10:34:44 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp@gnu.org
Message-id: <NBBBJJODBJBNJFNIDDCNIENLDDAA.cyates@uidaho.edu>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Subject: possible bug in sha and crc32 digest classes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 31 Dec 2002 18:35:31 -0000

While building a cppunit test suite for the digest classes I exposed some
possible bugs.  I cannot get correct digests for CRC32 and the two SHA
classes I'm testing (SHA1 & SHA256).  I used a freely available command line
hashing program (fsum) to generate my expected hash values, and have
verified that fsum generates a correct hash for the sha256 reference message
of 'abc' as documented in the sha256 literature.  My other test cases for
Checksum, CRC16, and MD5 test out ok, and I am only testing SHA1 and SHA256
at this time.

here are the failures from my cppunit test suite -- I kept 'pippo' as a
message in honor of the person that wrote the digest test program :)

1) test: DigestTest.testCRC32 (F) line: 111
e:\projects\c\ccgnu2_tests\digesttest.h
expected: df1dc234
but was:  00000000
additional message:
Source Message was 'pippo'

2) test: DigestTest.testSHA1 (F) line: 142
e:\projects\c\ccgnu2_tests\digesttest.h
expected: a9993e364706816aba3e25717850c26c9cd0d89d
but was:
000098440000f81e000014080000f6ec0000b9320000137d000033be0000d7cf0000dcf50000
18a3
additional message:
Source Message was 'pippo'

3) test: DigestTest.testSHA256 (F) line: 157
e:\projects\c\ccgnu2_tests\digesttest.h
expected: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
but was:
00004ea50000c5080000a65600006e7600002405000043f80000feb000006fd4000057770000
7be3000095490000c401000064360000afda000065d20000330e
additional message:
Source Message was 'pippo'

I suspect the error in crc32 may be the stream extract function and not the
actual algorithm.

I'm using M$ Visual C++ 6.0 and would like to see if this problem also
exists on the unix versions before I dig deeper.

,chad




From fullung@dogbert.sdsl.sun.ac.za Tue Dec 31 15:09:38 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TShf-0004V8-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 15:09:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TShQ-000460-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 15:09:17 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TShC-0003LW-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 15:09:03 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18TShA-0005dH-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 22:09:00 +0200
Received: (qmail 21786 invoked from network); 31 Dec 2002 20:08:59 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 31 Dec 2002 20:08:59 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18TSh9-00007P-00
	for <bug-commoncpp@gnu.org>; Tue, 31 Dec 2002 22:08:59 +0200
Date: Tue, 31 Dec 2002 22:08:59 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20021231200859.GB415@dogbert.sdsl.sun.ac.za>
References: <NBBBJJODBJBNJFNIDDCNIENLDDAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNIENLDDAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18TShA-0005dH-00*Uvxv1WDMghg*
Subject: Re: possible bug in sha and crc32 digest classes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 31 Dec 2002 20:09:38 -0000

Hello,

On Tue, 31 Dec 2002, Chad Yates wrote:

> While building a cppunit test suite for the digest classes I exposed some
> possible bugs.  I cannot get correct digests for CRC32 and the two SHA
> classes I'm testing (SHA1 & SHA256).  I used a freely available command line
> hashing program (fsum) to generate my expected hash values, and have
> verified that fsum generates a correct hash for the sha256 reference message
> of 'abc' as documented in the sha256 literature.  My other test cases for
> Checksum, CRC16, and MD5 test out ok, and I am only testing SHA1 and SHA256
> at this time.

<snipped>

I noticed a minor issue with MD5Digest. On any Unixish system you can do 
the following:

fullung@dogbert:~> echo -n "" | md5sum
d41d8cd98f00b204e9800998ecf8427e  -

So the hash value of "nothing" is the value given above. I believe this 
agrees with the example given in the RFC.

I quickly fiddled with MD5Digest, but it doesn't seem as if this is the 
default value of the digest. Inserting "" doesn't seem to work either.

Don't know if anyone is going to get very excited about this (if at 
all; maybe I'm not using MD5Digest correctly), but it should probably 
be fixed.

Cheers,

Albert


From fedemp@bulbasaur.rediris.es Tue Dec 31 16:28:25 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TTvh-0005JE-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 16:28:05 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TTuj-0004mt-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 16:27:09 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TTuO-0004Bm-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 16:26:44 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18TTug-0005ca-00; Tue, 31 Dec 2002 22:27:02 +0100
Date: Tue, 31 Dec 2002 22:27:02 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-ID: <20021231212702.GC32211@bulbasaur.rediris.es>
Mail-Followup-To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20021230205954.GD409@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021230205954.GD409@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Headers and templated classes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 31 Dec 2002 21:28:27 -0000

On Mon, Dec 30, 2002 at 10:59:54PM +0200, Albert Strasheim wrote:
> Hello,
> 
> A few questions regarding header files and templated classes in cc++.
> 
> Firstly, what are the p[io]* headers for?
> 

	The pios* headers are a contribution by Daniel Baumann that
implements thread-safe C++ iostreams.

> Secondly, how does one actually use a header in the template directory 
> when building something in the demo directory? You can't exactly 
> #include it in the standard way, unless I am mistaken? Seems you 
> would have to make install cc++ first -- not always convenient.
> 
> IMHO, the reasons given in the README for keeping the templated and 
> non-templated code seperate are not entirely valid. It is quite common 
> for code that was once "normal" to be extended in future to support 
> templating. Should this code then be moved? I think not.
> 

	I think you are right, I do not see any simple way to use the
templates in demo or tests apps. Probably the reasons why David put
the templates there are no longer valid and we should move them?

> Cheers,
> 
> Albert
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


From fedemp@bulbasaur.rediris.es Tue Dec 31 16:42:32 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TU7F-0003CT-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 16:40:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TU71-0002Yu-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 16:39:54 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TU6n-0001re-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 16:39:33 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18TU79-0005d4-00; Tue, 31 Dec 2002 22:39:55 +0100
Date: Tue, 31 Dec 2002 22:39:55 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-ID: <20021231213955.GD32211@bulbasaur.rediris.es>
Mail-Followup-To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20021231001633.GA4188@dogbert.sdsl.sun.ac.za>
	<20021231111009.GD22613@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021231111009.GD22613@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Test framework; new counter class
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 31 Dec 2002 21:42:33 -0000


	Well, both things -the unified counter template and the
CppUnit tests- are very interesting.

	One point that you should take into account for the atomic
counter stuff is that we removed the use of asm/atomic.h (actually
there should not be any references to it left) a few weeks ago. Look
for a bug report that we received from the debian maintainer of
commoncpp2, at the September and October archives of bug-commoncpp. I
think we should not wait to add the counter template to HEAD, and if
you think the interface is stable, it should also get into RELEASE1.

	If there are no more last minute updates or suggestions for
the CppUnit part of the patch for now, I would add it to CVS. Or do
you, Albert and Chad, prefer to merge or compare your tests before?

On Tue, Dec 31, 2002 at 01:10:10PM +0200, Albert Strasheim wrote:
> Hello,
> 
> On Tue, 31 Dec 2002, Albert Strasheim wrote:
> 
> > Attached is a patch that contains the following:
> 
> New patch attached. diff'd against the same CVS snapshot.
>  
> > - some basic code for a test framework for Common C++ based on the 
> > CppUnit test library,
> > 
> > - a counter class (called UberCounter for now) meant to unify the 
> > Counter, MutexCounter and AtomicCounter classes,
> 
> I've cleaned this up quite a bit. I've added reasonably complete doxygen 
> documentation, and moved a bunch of methods that were public but are 
> supposed to be protected.
> 
> For some reason, doxygen isn't convinced that UberCounter is in the 
> Common C++ namespace, though. Also, some @c's aren't resolving...
>  
> > - minor tweaks to configure.in and some Makefile.am files related to 
> > gcc compiler flags.
> > 
> > The patch is against commoncpp2 in CVS on Tue Dec 31 02:00:00 GMT+2 2002 
> > or thereabouts.
> 
> The rest of the stuff is still there. I don't have the energy to split 
> up the patch into the various possibilities. :-)
> 
> Cheers,
> 
> Albert


> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fullung@dogbert.sdsl.sun.ac.za Tue Dec 31 17:13:20 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TUdQ-0008DI-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 17:13:16 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TUco-0007PM-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 17:12:39 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TUaz-0006RZ-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 17:10:45 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18TUaw-0004k3-00
	for bug-commoncpp@gnu.org; Wed, 01 Jan 2003 00:10:42 +0200
Received: (qmail 23326 invoked from network); 31 Dec 2002 22:10:42 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 31 Dec 2002 22:10:42 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18TUaw-00009F-00; Wed, 01 Jan 2003 00:10:42 +0200
Date: Wed, 1 Jan 2003 00:10:42 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-ID: <20021231221041.GC415@dogbert.sdsl.sun.ac.za>
References: <20021231001633.GA4188@dogbert.sdsl.sun.ac.za>
	<20021231111009.GD22613@dogbert.sdsl.sun.ac.za>
	<20021231213955.GD32211@bulbasaur.rediris.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021231213955.GD32211@bulbasaur.rediris.es>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18TUaw-0004k3-00*1R.4HnVgUH2*
cc: bug-commoncpp@gnu.org
Subject: Re: Test framework; new counter class
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 31 Dec 2002 22:13:21 -0000

Hello,

On Tue, 31 Dec 2002, Federico Montesino Pouzols wrote:

> 	Well, both things -the unified counter template and the
> CppUnit tests- are very interesting.
> 
> 	One point that you should take into account for the atomic
> counter stuff is that we removed the use of asm/atomic.h (actually
> there should not be any references to it left) a few weeks ago. Look
> for a bug report that we received from the debian maintainer of
> commoncpp2, at the September and October archives of bug-commoncpp. I
> think we should not wait to add the counter template to HEAD, and if
> you think the interface is stable, it should also get into RELEASE1.

I'll look at the atomic.h stuff now.

Most of the UberCounter code (with the exception of the atomic stuff on 
Win32) is probably done and has been reasonably well tested.

Furthermore, are the current list of operator methods sufficient? In 
deciding which operators to implement, I basically looked at kind of 
stuff you do to a counter variable in a for(;;) loop. UberCounter 
wasn't intended to be a complete numeric type. Has this been achieved?

One addition might be an operator() method, but I still need to 
investigate how this is utilized by other libraries, specifically the 
STL (used by sort algorithms?). Anyone?

A question: do you intend for UberCounter to replace the existing 
counter classes? If so, I think it should be renamed to Counter, taking 
the place of the existing Counter<T>.

As I understand it, this will be 1.1 release, so we might be justified 
in cleaning up the counters in the library. It should be noted that old 
code will have to be slightly modified to make use of UberCounter if it 
replaces Counter<T>, MutexCounter, and AtomicCounter.

> 	If there are no more last minute updates or suggestions for
> the CppUnit part of the patch for now, I would add it to CVS. Or do
> you, Albert and Chad, prefer to merge or compare your tests before?

I think Chad is preparing some patches that contain his CppUnit work so 
far. I'd like to take a look at what he has done before we decide on a 
final framework for implementing the tests. Chad?

Cheers,

Albert


From fullung@dogbert.sdsl.sun.ac.za Tue Dec 31 18:05:05 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TVRZ-0006u5-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 18:05:05 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TVRX-0006sA-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 18:05:04 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TVRW-0006qg-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 18:05:02 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18TVRR-0007CU-00
	for bug-commoncpp@gnu.org; Wed, 01 Jan 2003 01:04:57 +0200
Received: (qmail 23947 invoked from network); 31 Dec 2002 23:04:57 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 31 Dec 2002 23:04:57 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18TVRQ-0000BM-00
	for <bug-commoncpp@gnu.org>; Wed, 01 Jan 2003 01:04:56 +0200
Date: Wed, 1 Jan 2003 01:04:56 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20021231230456.GD415@dogbert.sdsl.sun.ac.za>
References: <20021231001633.GA4188@dogbert.sdsl.sun.ac.za>
	<20021231111009.GD22613@dogbert.sdsl.sun.ac.za>
	<20021231213955.GD32211@bulbasaur.rediris.es>
	<20021231221041.GC415@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021231221041.GC415@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18TVRR-0007CU-00*Z3McxEqh6pc*
Subject: Re: Test framework; new counter class
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 31 Dec 2002 23:05:12 -0000

Hello,

On Wed, 01 Jan 2003, Albert Strasheim wrote:

<snip>

> > 	One point that you should take into account for the atomic
> > counter stuff is that we removed the use of asm/atomic.h (actually
> > there should not be any references to it left) a few weeks ago. Look
> > for a bug report that we received from the debian maintainer of
> > commoncpp2, at the September and October archives of bug-commoncpp. I
> > think we should not wait to add the counter template to HEAD, and if
> > you think the interface is stable, it should also get into RELEASE1.
> 
> I'll look at the atomic.h stuff now.

I'm confused.

We should be using sys/atomic.h instead of asm/atomic.h, because 
asm/atomic.h is an evil kernel header. Yet I haven't been able to find 
an i386 Linux system on which sys/atomic.h actually exists (checked 
Debian unstable, RedHat 7.1, and recent Mandrake).

Where is it? How do I get at the atomic stuff on i386 without violating 
this policy?

Cheers,

Albert


From lizzy@soggytrousers.net Tue Dec 31 19:13:54 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TWWA-0001mw-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 19:13:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TWW8-0001mh-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 19:13:53 -0500
Received: from c66.190.65.189.ftwrth.tx.charter.com ([66.190.65.189]
	helo=liliwhite.renaissance.oasis)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18TWW8-0001mc-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 19:13:52 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1
	(Debian))	id 18TWW2-0002zF-00; Tue, 31 Dec 2002 18:13:46 -0600
To: Chad Yates <cyates@uidaho.edu>
References: <NBBBJJODBJBNJFNIDDCNIENLDDAA.cyates@uidaho.edu>
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 31 Dec 2002 18:13:46 -0600
In-Reply-To: Chad Yates's message of "Tue, 31 Dec 2002 10:34:44 -0800"
Message-ID: <87el7x4thh.fsf@liliwhite.renaissance.oasis>
Lines: 76
X-Mailer: Gnus v5.7/Emacs 20.7
Sender: Elizabeth Barham <lizzy@soggytrousers.net>
cc: bug-commoncpp@gnu.org
Subject: Re: possible bug in sha and crc32 digest classes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 01 Jan 2003 00:13:55 -0000

Hi Chad,

   The "expected" answers provided in your message for the SHA1Digest
and SHA256Digest are for the message "abc" and are the same in the SHA
specs.

CommonC++ SHA1Digest and SHA156Digest of "abc", respectivly:
a9993e364706816aba3e25717850c26c9cd0d89d
ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad

CommonC++ SHA1Digest and SHA156Digest of "pippo", respectivly:
d012f68144ed0f121d3cc330a17eec528c2e7d59
a2242ead55c94c3deb7cf2340bfef9d5bcaca22dfe66e646745ee4371c633fc8

   How do these answers compare with that of fsum?

   As for the extraneous zeros, though, that must be a VC++ issue. The
test case output is from commoncpp2-1.0.7 using g++.

   Elizabeth


Chad Yates <cyates@uidaho.edu> writes:

> While building a cppunit test suite for the digest classes I exposed some
> possible bugs.  I cannot get correct digests for CRC32 and the two SHA
> classes I'm testing (SHA1 & SHA256).  I used a freely available command line
> hashing program (fsum) to generate my expected hash values, and have
> verified that fsum generates a correct hash for the sha256 reference message
> of 'abc' as documented in the sha256 literature.  My other test cases for
> Checksum, CRC16, and MD5 test out ok, and I am only testing SHA1 and SHA256
> at this time.
> 
> here are the failures from my cppunit test suite -- I kept 'pippo' as a
> message in honor of the person that wrote the digest test program :)
> 
> 1) test: DigestTest.testCRC32 (F) line: 111
> e:\projects\c\ccgnu2_tests\digesttest.h
> expected: df1dc234
> but was:  00000000
> additional message:
> Source Message was 'pippo'
> 
> 2) test: DigestTest.testSHA1 (F) line: 142
> e:\projects\c\ccgnu2_tests\digesttest.h
> expected: a9993e364706816aba3e25717850c26c9cd0d89d
> but was:
> 000098440000f81e000014080000f6ec0000b9320000137d000033be0000d7cf0000dcf50000
> 18a3
> additional message:
> Source Message was 'pippo'
> 
> 3) test: DigestTest.testSHA256 (F) line: 157
> e:\projects\c\ccgnu2_tests\digesttest.h
> expected: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
> but was:
> 00004ea50000c5080000a65600006e7600002405000043f80000feb000006fd4000057770000
> 7be3000095490000c401000064360000afda000065d20000330e
> additional message:
> Source Message was 'pippo'
> 
> I suspect the error in crc32 may be the stream extract function and not the
> actual algorithm.
> 
> I'm using M$ Visual C++ 6.0 and would like to see if this problem also
> exists on the unix versions before I dig deeper.
> 
> ,chad
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


From cyates@uidaho.edu Tue Dec 31 20:53:01 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TY45-000609-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 20:53:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TY42-0005sO-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 20:53:00 -0500
Received: from mailb.its.uidaho.edu ([129.101.155.251] helo=snow)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TY41-0005le-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 20:52:57 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8000N4RIK209@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Tue, 31 Dec 2002 17:52:52 -0800 (PST)
Date: Tue, 31 Dec 2002 17:52:51 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <87el7x4thh.fsf@liliwhite.renaissance.oasis>
To: Elizabeth Barham <lizzy@soggytrousers.net>
Message-id: <NBBBJJODBJBNJFNIDDCNAENPDDAA.cyates@uidaho.edu>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
cc: bug-commoncpp@gnu.org
Subject: RE: possible bug in sha and crc32 digest classes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 01 Jan 2003 01:53:01 -0000

There was some discrepancies between the printed message and the actal test
(the evils of cut and paste), I'm feeling much better now.

your provided SHA1/SHA256 digests match fsum's output.  So I guess the
problem must be in VC 6.0/Win32.  thank goodness.  I'm not very familiar
with the algorithm, but I'll see if I can flush it out in the coming days.
I've almost got a linux installation with commoncpp2 setup on it so I can
test under redhat 8.0 too.

thanks for checking this out.

,Chad

P.S. here is the corrected output from the unit test:

1) test: DigestTest.testCRC32 (F) line: 111
e:\projects\c\ccgnu2_tests\digesttest.h
expected: df1dc234
but was:  00000000
additional message:
Hashed Message was 'pippo'

2) test: DigestTest.testSHA1 (F) line: 142
e:\projects\c\ccgnu2_tests\digesttest.h
expected: d012f68144ed0f121d3cc330a17eec528c2e7d59
but was:
000098440000f81e000014080000f6ec0000b9320000137d000033be0000d7cf0000dcf50000
18a3
additional message:
Hashed Message was 'pippo'

3) test: DigestTest.testSHA256 (F) line: 157
e:\projects\c\ccgnu2_tests\digesttest.h
expected: a2242ead55c94c3deb7cf2340bfef9d5bcaca22dfe66e646745ee4371c633fc8
but was:
00004ea50000c5080000a65600006e7600002405000043f80000feb000006fd4000057770000
7be3000095490000c401000064360000afda000065d20000330e
additional message:
Hashed Message was 'pippo'


> -----Original Message-----
> From: bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org
> [mailto:bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org]On Behalf Of
> Elizabeth Barham
> Sent: Tuesday, December 31, 2002 4:14 PM
> To: Chad Yates
> Cc: bug-commoncpp@gnu.org
> Subject: Re: possible bug in sha and crc32 digest classes
>
>
> Hi Chad,
>
>    The "expected" answers provided in your message for the SHA1Digest
> and SHA256Digest are for the message "abc" and are the same in the SHA
> specs.
>
> CommonC++ SHA1Digest and SHA156Digest of "abc", respectivly:
> a9993e364706816aba3e25717850c26c9cd0d89d
> ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
>
> CommonC++ SHA1Digest and SHA156Digest of "pippo", respectivly:
> d012f68144ed0f121d3cc330a17eec528c2e7d59
> a2242ead55c94c3deb7cf2340bfef9d5bcaca22dfe66e646745ee4371c633fc8
>
>    How do these answers compare with that of fsum?
>
>    As for the extraneous zeros, though, that must be a VC++ issue. The
> test case output is from commoncpp2-1.0.7 using g++.
>
>    Elizabeth
>
>
> Chad Yates <cyates@uidaho.edu> writes:
>
> > While building a cppunit test suite for the digest classes I
> exposed some
> > possible bugs.  I cannot get correct digests for CRC32 and the two SHA
> > classes I'm testing (SHA1 & SHA256).  I used a freely available
> command line
> > hashing program (fsum) to generate my expected hash values, and have
> > verified that fsum generates a correct hash for the sha256
> reference message
> > of 'abc' as documented in the sha256 literature.  My other test
> cases for
> > Checksum, CRC16, and MD5 test out ok, and I am only testing
> SHA1 and SHA256
> > at this time.
> >
> > here are the failures from my cppunit test suite -- I kept 'pippo' as a
> > message in honor of the person that wrote the digest test program :)
> >
> > 1) test: DigestTest.testCRC32 (F) line: 111
> > e:\projects\c\ccgnu2_tests\digesttest.h
> > expected: df1dc234
> > but was:  00000000
> > additional message:
> > Source Message was 'pippo'
> >
> > 2) test: DigestTest.testSHA1 (F) line: 142
> > e:\projects\c\ccgnu2_tests\digesttest.h
> > expected: a9993e364706816aba3e25717850c26c9cd0d89d
> > but was:
> >
> 000098440000f81e000014080000f6ec0000b9320000137d000033be0000d7cf00
> 00dcf50000
> > 18a3
> > additional message:
> > Source Message was 'pippo'
> >
> > 3) test: DigestTest.testSHA256 (F) line: 157
> > e:\projects\c\ccgnu2_tests\digesttest.h
> > expected:
> ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
> > but was:
> >
> 00004ea50000c5080000a65600006e7600002405000043f80000feb000006fd400
> 0057770000
> > 7be3000095490000c401000064360000afda000065d20000330e
> > additional message:
> > Source Message was 'pippo'
> >
> > I suspect the error in crc32 may be the stream extract function
> and not the
> > actual algorithm.
> >
> > I'm using M$ Visual C++ 6.0 and would like to see if this problem also
> > exists on the unix versions before I dig deeper.
> >
> > ,chad
> >
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From lizzy@soggytrousers.net Tue Dec 31 20:56:08 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TY76-0007GU-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 20:56:08 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TY74-0007GJ-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 20:56:07 -0500
Received: from c66.190.65.189.ftwrth.tx.charter.com ([66.190.65.189]
	helo=liliwhite.renaissance.oasis)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18TY74-0007GF-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 20:56:06 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1
	(Debian))	id 18TY70-00036S-00
	for <bug-commoncpp@gnu.org>; Tue, 31 Dec 2002 19:56:02 -0600
To: bug-commoncpp@gnu.org
References: <NBBBJJODBJBNJFNIDDCNIENLDDAA.cyates@uidaho.edu>
	<87el7x4thh.fsf@liliwhite.renaissance.oasis>
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 31 Dec 2002 19:56:02 -0600
In-Reply-To: Elizabeth Barham's message of "31 Dec 2002 18:13:46 -0600"
Message-ID: <87bs314or1.fsf@liliwhite.renaissance.oasis>
Lines: 26
X-Mailer: Gnus v5.7/Emacs 20.7
Sender: Elizabeth Barham <lizzy@soggytrousers.net>
Subject: Re: possible bug in sha and crc32 digest classes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 01 Jan 2003 01:56:08 -0000



> CommonC++ SHA1Digest and SHA156Digest of "pippo", respectivly:
> d012f68144ed0f121d3cc330a17eec528c2e7d59
> a2242ead55c94c3deb7cf2340bfef9d5bcaca22dfe66e646745ee4371c633fc8

That should be SHA256Digest, not SHA156Digest.

   Anyway, I was concerned that maybe the raw digest was in error as
the output above has been massaged into a character representation for
an ostream. Perhaps all those excess zeroes were in memory but were
neatly removed when going out ostream...

(gdb) x/20xb d1_d
0x100ba920:	0xd0	0x12	0xf6	0x81	0x44	0xed	0x0f	0x12
0x100ba928:	0x1d	0x3c	0xc3	0x30	0xa1	0x7e	0xec	0x52
0x100ba930:	0x8c	0x2e	0x7d	0x59
(gdb) x/32xb d256_d
0x100ba938:	0xa2	0x24	0x2e	0xad	0x55	0xc9	0x4c	0x3d
0x100ba940:	0xeb	0x7c	0xf2	0x34	0x0b	0xfe	0xf9	0xd5
0x100ba948:	0xbc	0xac	0xa2	0x2d	0xfe	0x66	0xe6	0x46
0x100ba950:	0x74	0x5e	0xe4	0x37	0x1c	0x63	0x3f	0xc8

   It looks good here.

   Elizabeth


From lizzy@soggytrousers.net Tue Dec 31 21:44:31 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TYrs-0000QJ-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 21:44:28 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TYrU-00089S-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 21:44:06 -0500
Received: from c66.190.65.189.ftwrth.tx.charter.com ([66.190.65.189]
	helo=liliwhite.renaissance.oasis)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18TYrD-0007z0-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 21:43:47 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1
	(Debian))	id 18TYr8-00037t-00; Tue, 31 Dec 2002 20:43:42 -0600
To: Chad Yates <cyates@uidaho.edu>
References: <NBBBJJODBJBNJFNIDDCNAENPDDAA.cyates@uidaho.edu>
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 31 Dec 2002 20:43:42 -0600
In-Reply-To: Chad Yates's message of "Tue, 31 Dec 2002 17:52:51 -0800"
Message-ID: <8765t94mjl.fsf@liliwhite.renaissance.oasis>
Lines: 41
X-Mailer: Gnus v5.7/Emacs 20.7
Sender: Elizabeth Barham <lizzy@soggytrousers.net>
cc: bug-commoncpp@gnu.org
Subject: Re: possible bug in sha and crc32 digest classes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 01 Jan 2003 02:44:32 -0000

Chad, 

   Are you using the CVS version or the regular download version? I
was going over the code on the web viewcvs thing:

template <class int_type>
std::ostream & SHATumbler<int_type>::toString(std::ostream & os)
{
	unsigned i;
 	unsigned long h1, h2;
	for(i = 0 ; i < (unsigned)size ; i++) {
		
#ifdef DEBUG_SHATUMBLER
		if(i != 0)
			os << " ";
#endif

#if defined(WIN32) && !defined(__MINGW32__)
		h1 = h[i] / 0x10000;
		h2 = h[i] % 0x10000;
#else
		h1 = h[i] / 0x10000LL;
		h2 = h[i] % 0x10000LL;
#endif

		os << std::hex << std::setw(sizeof(h1) * 2) << 
			std::setfill('0') << h1;

		os << std::hex << std::setw(sizeof(h2) * 2) << 
			std::setfill('0') << h2;
	}
	return(os);
}

The h1 and h2 are not in the download'd code and I did not use them
originally IIRC.

   Anyway, if you are using the CVS code, this might possibly be where
the extra 0's are showing up.

Elizabeth


From cyates@uidaho.edu Tue Dec 31 22:04:20 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TZB6-0005HS-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 22:04:20 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TZB3-000593-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 22:04:18 -0500
Received: from maila.its.uidaho.edu ([129.101.155.252] helo=rain)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TZB2-000572-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 22:04:16 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8000L7ZLV3JE@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Tue, 31 Dec 2002 19:04:15 -0800 (PST)
Date: Tue, 31 Dec 2002 19:04:15 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <8765t94mjl.fsf@liliwhite.renaissance.oasis>
To: Elizabeth Barham <lizzy@soggytrousers.net>
Message-id: <NBBBJJODBJBNJFNIDDCNGEOADDAA.cyates@uidaho.edu>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
cc: bug-commoncpp@gnu.org
Subject: RE: possible bug in sha and crc32 digest classes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 01 Jan 2003 03:04:20 -0000

cvs, updated this morning.  I'll check it out. thanks

> -----Original Message-----
> From: Elizabeth Barham [mailto:lizzy@soggytrousers.net]
> Sent: Tuesday, December 31, 2002 6:44 PM
> To: Chad Yates
> Cc: bug-commoncpp@gnu.org
> Subject: Re: possible bug in sha and crc32 digest classes
> 
> 
> Chad, 
> 
>    Are you using the CVS version or the regular download version? I
> was going over the code on the web viewcvs thing:
> 
> template <class int_type>
> std::ostream & SHATumbler<int_type>::toString(std::ostream & os)
> {
> 	unsigned i;
>  	unsigned long h1, h2;
> 	for(i = 0 ; i < (unsigned)size ; i++) {
> 		
> #ifdef DEBUG_SHATUMBLER
> 		if(i != 0)
> 			os << " ";
> #endif
> 
> #if defined(WIN32) && !defined(__MINGW32__)
> 		h1 = h[i] / 0x10000;
> 		h2 = h[i] % 0x10000;
> #else
> 		h1 = h[i] / 0x10000LL;
> 		h2 = h[i] % 0x10000LL;
> #endif
> 
> 		os << std::hex << std::setw(sizeof(h1) * 2) << 
> 			std::setfill('0') << h1;
> 
> 		os << std::hex << std::setw(sizeof(h2) * 2) << 
> 			std::setfill('0') << h2;
> 	}
> 	return(os);
> }
> 
> The h1 and h2 are not in the download'd code and I did not use them
> originally IIRC.
> 
>    Anyway, if you are using the CVS code, this might possibly be where
> the extra 0's are showing up.
> 
> Elizabeth


From lizzy@soggytrousers.net Tue Dec 31 22:15:48 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TZLz-0000yP-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 22:15:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TZLu-0000n5-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 22:15:32 -0500
Received: from c66.190.65.189.ftwrth.tx.charter.com ([66.190.65.189]
	helo=liliwhite.renaissance.oasis)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18TZLn-0000Ti-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 22:15:23 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1
	(Debian))	id 18TZLj-00038x-00
	for <bug-commoncpp@gnu.org>; Tue, 31 Dec 2002 21:15:19 -0600
To: bug-commoncpp@gnu.org
References: <NBBBJJODBJBNJFNIDDCNAENPDDAA.cyates@uidaho.edu>
	<8765t94mjl.fsf@liliwhite.renaissance.oasis>
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 31 Dec 2002 21:15:19 -0600
In-Reply-To: Elizabeth Barham's message of "31 Dec 2002 20:43:42 -0600"
Message-ID: <873cod4l2w.fsf@liliwhite.renaissance.oasis>
Lines: 58
X-Mailer: Gnus v5.7/Emacs 20.7
Sender: Elizabeth Barham <lizzy@soggytrousers.net>
Subject: Re: possible bug in sha and crc32 digest classes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 01 Jan 2003 03:15:48 -0000

> template <class int_type>
> std::ostream & SHATumbler<int_type>::toString(std::ostream & os)
> {
> 	unsigned i;
>  	unsigned long h1, h2;

This should *probably* be:

        int_type h1, h2;

> 	for(i = 0 ; i < (unsigned)size ; i++) {
> 		
> #ifdef DEBUG_SHATUMBLER
> 		if(i != 0)
> 			os << " ";
> #endif

This appears to be an effort to split the "tumbler" (a uint32_t and
possibly a uint64_t in the future) into a HIGH part and LOW part.

> #if defined(WIN32) && !defined(__MINGW32__)
> 		h1 = h[i] / 0x10000;
> 		h2 = h[i] % 0x10000;
> #else
> 		h1 = h[i] / 0x10000LL;
> 		h2 = h[i] % 0x10000LL;
> #endif

The above may not work as expected if we modify "unsigned long" to
"int_type" since there is no guarantee on the length of "int_type".

Perhaps something akin to:

                h1 = h[i] / (1 << (sizeof(h[i]) / 2);
	        h2 ...

would work better?

> 
> 		os << std::hex << std::setw(sizeof(h1) * 2) << 
> 			std::setfill('0') << h1;
> 
> 		os << std::hex << std::setw(sizeof(h2) * 2) << 
> 			std::setfill('0') << h2;

and since the tumbler has been split into two halves with the output
in the lower halves, there is no need to have the "* 2" (the sizeof
will return the correct number of characters that will need to be used
to represent one half of the datum).

> 	}
> 	return(os);
> }

Out of curiosity, what prompted the modification to use h1 and h2?

Sincerely,
Elizabeth


From seenutn@cdotb.ernet.in Tue Dec 31 22:54:51 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TZxj-0005qE-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 22:54:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TZxe-0005ht-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 22:54:31 -0500
Received: from [202.41.72.121] (helo=ws9.cdotb.ernet.in)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18TZwE-00051J-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 22:53:44 -0500
Received: from ws9.cdotb.ernet.in ([192.168.51.218])
	by ws9.cdotb.ernet.in (8.9.3/8.9.3) with ESMTP id IAA23673
	for <bug-commoncpp@gnu.org>; Wed, 1 Jan 2003 08:57:59 +0500 (GMT+0500)
Message-ID: <3E1266D7.2030508@ws9.cdotb.ernet.in>
Date: Wed, 01 Jan 2003 09:26:07 +0530
From: "Srinivasa T.N." <seenutn@cdotb.ernet.in>
Organization: C-DOT
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: HNY
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 01 Jan 2003 03:54:51 -0000

Hi,
	Wish you all a Very Happy New Year....

With Luv,
Seenu.
-- 
-----------------------------------------------------------------------------
If not here, you can reach me at seenutn@yahoo.com

C-DOT, 71/1, Sneha Complex, Miller Road, Bangalore - 560 052
Ph: 226 3399 Ext: 268/Direct: 238 3951 (Off)   363 1707 (Resi)
	http://www.geocities.com/seenutn



From cityman@junisphere.net Tue Dec 31 09:44:15 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TNcp-0007lC-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 09:44:11 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TNca-0007IS-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 09:43:58 -0500
Received: from exavns01gb1.netstore.net ([194.79.241.56])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18TNcO-00079i-00
	for bug-commoncpp@gnu.org; Tue, 31 Dec 2002 09:43:44 -0500
Received: from 194.79.241.49 by exavns01gb1.netstore.net (InterScan E-Mail
	VirusWall NT); Tue, 31 Dec 2002 14:43:25 -0000
Received: from EXBENS01GB1.netstore.local ([194.79.241.50]) by
	exfens02gb1.netstore.local with Microsoft SMTPSVC(5.0.2195.5329);
	Tue, 31 Dec 2002 14:43:24 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6334.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-9bc57818-c247-4e7c-9b49-50c5d9bba8ba"
Date: Tue, 31 Dec 2002 14:43:24 -0000
Message-ID: <1AD05C34099CE048B5881A7852C61DE001D1096F@EXBENS01GB1.netstore.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bug in thread code
Thread-Index: AcKw2wBGjxyVuUCMRfaGz3ed4x1wJQ==
From: "Marcel Stadtmann" <cityman@junisphere.net>
To: <bug-commoncpp@gnu.org>
X-OriginalArrivalTime: 31 Dec 2002 14:43:24.0961 (UTC)
	FILETIME=[F92CB110:01C2B0DA]
X-Mailman-Approved-At: Wed, 01 Jan 2003 09:19:52 -0500
Subject: Bug in thread code
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 31 Dec 2002 14:44:15 -0000

This is a multi-part message in MIME format.

------=_NextPartTM-000-9bc57818-c247-4e7c-9b49-50c5d9bba8ba
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2B0DA.F8E422D8"

------_=_NextPart_001_01C2B0DA.F8E422D8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,


I found a bug in the thread code section. (Used Version GNU Common C++ =
'2' 1.0.7)=20
After starting abount 1024 thread's, i got the errorcode 11.

Systeminfo:
SuSE Linux 2.4.10
Used Version GNU Common C++ '2' 1.0.7
complied with gcc Version 2.95.3


It's very easy to get the error:

1. Take the sample code tcpthread.cpp from the demo section:
2. Change timeout on myTCPSession from 20000 to 10
void myTCPSession::run(void)=20
{=20
InetAddress addr =3D getLocal();=20
*tcp() << "welcome to " << addr.getHostname() << " from socket " << so =
<< endl; mutex.enterMutex();=20
*tcp() << "called from thread " << count << endl; mutex.leaveMutex();=20
sleep(20000); <------ Replace this with sleep(10);
*tcp() << "ending session" << endl;=20
}=20

3. Make a quick connecting script like this:
#!/bin/sh


while true; do
        telnet localhost 4096=20
       =20
        done

After about 1024 start's the demo code is hanging.=20
Also my own Programm has the same fault.=20







------_=_NextPart_001_01C2B0DA.F8E422D8
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6336.0">
<TITLE>Bug in thread code</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi All,</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">I found a bug in the thread code =
section. (Used Version<SPAN LANG=3D"de-ch"></SPAN></FONT><SPAN =
LANG=3D"de-ch"></SPAN><SPAN LANG=3D"de-ch"> <FONT FACE=3D"Times New =
Roman">GNU Common C++ '2' 1.0.7)</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"> </SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">After starting =
abount 1024 thread's, i got the errorcode 11.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 =
FACE=3D"Arial">Systeminfo:</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">SuSE Linux =
2.4.10</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Used =
Version</FONT></SPAN><SPAN LANG=3D"de-ch"></SPAN><SPAN =
LANG=3D"de-ch"></SPAN><SPAN LANG=3D"de-ch"> <FONT FACE=3D"Times New =
Roman">GNU Common C++ '2' 1.0.7</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">complied with gcc =
Version 2.95.3</FONT></SPAN>
</P>
<BR>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">It's very easy to get =
the error:</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">1. Take the sample =
code</FONT></SPAN><SPAN LANG=3D"de-ch"></SPAN><SPAN =
LANG=3D"de-ch"></SPAN><SPAN LANG=3D"de-ch"> <FONT FACE=3D"Times New =
Roman">tcpthread.cpp</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial"> from the demo =
section:</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">2. Change timeout =
on</FONT></SPAN><SPAN LANG=3D"de-ch"></SPAN><SPAN =
LANG=3D"de-ch"></SPAN><SPAN LANG=3D"de-ch"> <FONT FACE=3D"Times New =
Roman">myTCPSession from 20000 to 10</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN>

<BR><SPAN LANG=3D"de-ch"><FONT FACE=3D"Times New Roman">void =
myTCPSession::run(void) </FONT></SPAN>

<BR><SPAN LANG=3D"de-ch"><FONT FACE=3D"Times New Roman">{ </FONT></SPAN>

<BR><SPAN LANG=3D"de-ch"><FONT FACE=3D"Times New Roman">InetAddress addr =
=3D getLocal(); </FONT></SPAN>

<BR><SPAN LANG=3D"de-ch"><FONT FACE=3D"Times New Roman">*tcp() &lt;&lt; =
&quot;welcome to &quot; &lt;&lt; addr.getHostname() &lt;&lt; &quot; from =
socket &quot; &lt;&lt; so &lt;&lt; endl; mutex.enterMutex(); =
</FONT></SPAN>

<BR><SPAN LANG=3D"de-ch"><FONT FACE=3D"Times New Roman">*tcp() &lt;&lt; =
&quot;called from thread &quot; &lt;&lt; count &lt;&lt; endl; =
mutex.leaveMutex(); </FONT></SPAN>

<BR><SPAN LANG=3D"de-ch"><FONT COLOR=3D"#FF0000" FACE=3D"Times New =
Roman">sleep(20000); &lt;------ Replace this with =
sleep(10);</FONT></SPAN>

<BR><SPAN LANG=3D"de-ch"><FONT FACE=3D"Times New Roman">*tcp() &lt;&lt; =
&quot;ending session&quot; &lt;&lt; endl; </FONT></SPAN>

<BR><SPAN LANG=3D"de-ch"><FONT FACE=3D"Times New Roman">} </FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">3. Make a quick =
connecting script like this:</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 =
FACE=3D"Arial">#!/bin/sh</FONT></SPAN>
</P>
<BR>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">while true; =
do</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; telnet =
localhost 4096 </FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
done</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">After about 1024 =
start's the demo code is hanging. </FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Also my own Programm =
has the same fault. </FONT></SPAN>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C2B0DA.F8E422D8--

------=_NextPartTM-000-9bc57818-c247-4e7c-9b49-50c5d9bba8ba--



