From fullung@dogbert.sdsl.sun.ac.za Wed Jan 01 10:45:36 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Tl3n-0005pe-00
	for bug-commoncpp@gnu.org; Wed, 01 Jan 2003 10:45:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Tl3k-0005gr-00
	for bug-commoncpp@gnu.org; Wed, 01 Jan 2003 10:45:34 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Tl3k-0003Mc-00
	for bug-commoncpp@gnu.org; Wed, 01 Jan 2003 10:45:32 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18Tl2h-0002Uz-00
	for bug-commoncpp@gnu.org; Wed, 01 Jan 2003 17:44:27 +0200
Received: (qmail 26879 invoked from network); 1 Jan 2003 15:44:27 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 1 Jan 2003 15:44:27 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18Tl2g-0000Vz-00; Wed, 01 Jan 2003 17:44:26 +0200
Date: Wed, 1 Jan 2003 17:44:26 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: Marcel Stadtmann <cityman@junisphere.net>
Message-ID: <20030101154426.GG415@dogbert.sdsl.sun.ac.za>
References: <1AD05C34099CE048B5881A7852C61DE001D1096F@EXBENS01GB1.netstore.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1AD05C34099CE048B5881A7852C61DE001D1096F@EXBENS01GB1.netstore.local>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18Tl2h-0002Uz-00*RGv7wP4nLbo*
cc: bug-commoncpp@gnu.org
Subject: Re: 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: Wed, 01 Jan 2003 15:45:36 -0000

Hello,

On Tue, 31 Dec 2002, Marcel Stadtmann wrote:

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

Error 11 seems be EAGAIN. It is returned by pthread_create when not 
enough system resources to create a process for the new thread are 
available, or more than PTHREAD_THREADS_MAX (16384 on my system) 
threads are already active.

I am not surprised that starting 1024 threads causes this error. To 
compare, my system is currently only running about 66 processes in 
total.

It might be possible to start this many threads using the new pthreads 
implementation that the RedHat folks are working on (also requires a 
recent 2.5.x kernel), but any design requiring 1024 threads probably 
still requires some rethinking.

Cheers,

Albert


From fullung@dogbert.sdsl.sun.ac.za Wed Jan 01 16:21:52 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TqJE-0007ow-00
	for bug-commoncpp@gnu.org; Wed, 01 Jan 2003 16:21:52 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Tq7A-0003E9-00
	for bug-commoncpp@gnu.org; Wed, 01 Jan 2003 16:09:30 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Tq6H-0002ws-00
	for bug-commoncpp@gnu.org; Wed, 01 Jan 2003 16:08:29 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18Tq6E-0000fp-00
	for bug-commoncpp@gnu.org; Wed, 01 Jan 2003 23:08:26 +0200
Received: (qmail 29484 invoked from network); 1 Jan 2003 21:08:26 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 1 Jan 2003 21:08:26 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18Tq6D-0000o8-00
	for <bug-commoncpp@gnu.org>; Wed, 01 Jan 2003 23:08:25 +0200
Date: Wed, 1 Jan 2003 23:08:25 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20030101210824.GH415@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/)
	*18Tq6E-0000fp-00*fCu7PVN5NxQ*
Subject: Signalling a condition
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 21:21:52 -0000

Hello,

I have a question about Conditional::signal().

According to the glibc manual (describing pthread_cond_wait),

"Unlocking the mutex and suspending on the condition variable is done 
atomically. Thus, if all threads always acquire the mutex before 
signaling the condition, this guarantees that the condition cannot be 
signaled (and thus ignored) between the time a thread locks the mutex 
and the time it waits on the condition variable."

The current code:

void ost::Conditional::signal(bool broadcast) 
{
  if(broadcast)
    pthread_cond_broadcast(&_cond);
  else
    pthread_cond_signal(&_cond);
}

But according to the glibc manual, "... if all threads always acquire 
the mutex before signaling the condition ...".

The new signal method would then read:

void ost::Conditional::signal(bool broadcast) 
{
  enterMutex();
  if(broadcast)
    pthread_cond_broadcast(&_cond);
  else
    pthread_cond_signal(&_cond);
  leaveMutex();
}

What will happen now is that all the threads that called
pthread_cond_wait will start waking up, and one will acquire the mutex. 
It will then possibly do something, and then unlock the mutex and go 
about its business, allowing the next thread to complete its
pthread_cond_wait call and so forth.

Comments? Am I even correct? :-)

Cheers,

Albert


From fullung@dogbert.sdsl.sun.ac.za Thu Jan 02 06:43:43 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U3lG-00082r-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 06:43:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U3hb-0005ow-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 06:39:57 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18U3h0-0005jf-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 06:39:19 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18U3gy-0004m8-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 13:39:16 +0200
Received: (qmail 1990 invoked from network); 2 Jan 2003 11:39:16 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 2 Jan 2003 11:39:16 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18U3gz-0002Lf-00; Thu, 02 Jan 2003 13:39:18 +0200
Date: Thu, 2 Jan 2003 13:39:17 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: Marcel Stadtmann <cityman@junisphere.net>
Message-ID: <20030102113917.GA17347@dogbert.sdsl.sun.ac.za>
References: <1AD05C34099CE048B5881A7852C61DE001D10970@EXBENS01GB1.netstore.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1AD05C34099CE048B5881A7852C61DE001D10970@EXBENS01GB1.netstore.local>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18U3gy-0004m8-00*XRlxV6b7iac*
cc: bug-commoncpp@gnu.org
Subject: Re: 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: Thu, 02 Jan 2003 11:43:44 -0000

Hello,

On Thu, 02 Jan 2003, Marcel Stadtmann wrote:

> Thanks for your help. But i think this is not the real problem. 
> Maybe my discribtion was not correct. On the sample, the thread will start,
> do his job, and then terminate. For me means this, the resource of 
> this thread should be free after termination. Is this not correct ?? 
> Are there still resources allocated ??

It seems as if final() in myTCPSession is being called, so the "delete 
this" probably happens. This starts destructing the thread object, which 
hopefully calls a terminate() somewhere down the line, which stops the 
thread and cleans up the other bits and pieces.

The obvious scenario related to threads where you could possibly run 
out of resources is when you start a bunch of joinable threads, but 
never join on them again, meaning their resources stick around until the 
parent process terminates.

I ran your test, and on my system (using commoncpp2 from CVS) I had 
completed about 20000 connections before tcpthread segfaulted.

While you wait for someone with a proper clue (i.e. not me :-)) to help 
you, you might want to try commoncpp2 from CVS and see if your problems 
persist. You can find instructions for doing a checkout here:

http://savannah.gnu.org/cvs/?group=commoncpp

I'll poke around the threads code some more today. Good luck!

Cheers,

Albert


From fullung@dogbert.sdsl.sun.ac.za Thu Jan 02 07:11:25 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U4Bo-000621-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 07:11:08 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U4A7-0005GV-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 07:09:24 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18U49v-0005Eh-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 07:09:11 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18U49p-00033F-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 14:09:05 +0200
Received: (qmail 2085 invoked from network); 2 Jan 2003 12:09:05 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 2 Jan 2003 12:09:05 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18U49r-0002NB-00
	for <bug-commoncpp@gnu.org>; Thu, 02 Jan 2003 14:09:07 +0200
Date: Thu, 2 Jan 2003 14:09:07 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20030102120906.GB17347@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>
	<20021231230456.GD415@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="OXfL5xGRrasGEqWY"
Content-Disposition: inline
In-Reply-To: <20021231230456.GD415@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/)
	*18U49p-00033F-00*hzXbgcZNyjY*
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: Thu, 02 Jan 2003 12:11:27 -0000


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

Hello,

Attached is a patch that contains the latest version of UberCounter and 
friends, the proposed test framework, and some minor other bits and 
pieces.

I've cleaned up the UberCounter, UberMutexCounter, and UberAtomicCounter 
documentation since the previous patch.

On the test framework front, I've added a custom TestListener class that 
will allow us to customize the output of the CppUnit test program.

Finally, there are some minor updates to the MAINTAINERCLEANFILES lists 
in some of the Makefile.am files.

Cheers,

Albert

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

H4sICF8cFD4AA3RzdGNudG1pc2MucGF0Y2gA7D37d9pGsz+Hv2Lj5rTYIMzDbhoc+wshOOHU
r2Nwm54kl09IC6gRElcSfrTN/dvvzOxKWgkJA3H69dxrNzWLdnd2Xjszuztam9ZoxLS5d8a0
W+Zzz9JtLN1YTqOOhfYvPWa406nrGLNZveJ61nj3VP/MR5bNK/pUrXP4jVpV0DRtWdcn9Wq1
rlVfaLUXrF5t1p43q3uVavjDSlWoL5RKpSVDIIiGVq3BP1arNxs/NRuNBRCvXjGtvld+zkr0
+9WrAjttdc/68H/nsn3SaZ0dd086PXYIAzkjazz3ONMN2zV0uzLdY7Y1DFzXZtGwlhOV2ccC
eyJ67YqPynjOfZ8ln/nzYfjEcvxAt23Nn6h97UAUWPR9qltOBRrJB1PL9y0nqp9+lnBMy/MB
kPZk9nlsOSOXtYlX7VKp4s+4USjlVLDuWa/fOjkpsAJ70+31B72r12+6l8gE3zOk9IF40zWY
yacuC/h0ZusBh4If+MxyDHtucub7doFZI/Zr96xRL5gb6FLEc+RrStJqXaY2qQ0SulBr7jWa
jf1V1CkXRqNZrzf3F1US9alWa6BCiQ/UqFYbWdjrF10/GBjXA/POsV3d5N42svg71uud4MAz
VBp3FlguEAR9WpdvB792+++KwMgyi38+aNqNFUw0eMwSP6/nlm0CBO5glT+fzVwv+FQulJYB
Y2w5uHMAhwjG4NgT+H6IcGRxa2tbIRKebAs+NPbKtQYwAj7rVeKE0ux1q9cZnHRfIw9K37ET
mFKgQe3Z7MqxAjZyPdIm0GtA/3Rw0eq/G7QvLq7Ouv1irfJTpbpdKGG/39w5M3QHNCpg8xmD
kj4P3CnMQZwPpoXcBE3THZPNfc4AdOCqNfYdQhkSqSD2OQyuzWk64fBs5rljT5/6FcKifX72
ptvvnp+1TorvWr90QozKovHWM/kd6eptIYZI7/lV/+KqX4S5s2sYY2de1+SExieRtaCJEH8F
9sZfpntRuYDTLq7B+Rd/kzNv8YFhlErx06gQTty4auRxPvTNXbAM2sy2/KDAQiOhTA2yEmHT
FAXt9vv39QrYCTIGCt5Kf+Bq4JLyg3kg1mkjomsSTG0wgya/rWCRHbBgwmE2PLF9qp/qTmN3
p9IwDPYXiNxkGmc/+M3/iuqa8FuWfoAmY4/PmHYNMjdddnS0SF1JgXwf9M1GYN+FQxBFCcBN
f6J7fBcrY+4g3ExAIws4RhNr70V5H+bV/o/lBk0rCdJ/uvUqmHgzDzh++2rr6daz6NvW07DB
Ve9ycHHZOe6+pxZRNXocanLRav/cett5ioIchF9E7186lz3QflEVfmEvpScLpjN2JMsTkLfJ
KpXdSqWgwX+bWP+0NmdEFBlNMn1BRjsZYdS1eh3DA4wQ6qu4hBxQaqSx19yrZnuGankP5FYF
6UlreNU/P2393BmcX6BZQRfruJrJweaa3DEsDpoDstdQT0TpD2tWYLFDxold0Drv+5etAfrq
KFCpTNAvfmRnLgOsbcuBuCVgAJa5I0YTspTbq5QTAqlRjtr+a4SbsExLJJxut1TM6cZC1rUa
zBxWbzSrIO7n68g6C54q8OfN2os8gT8ngT//OoEnRLUDs0tbGqVCgzwZhg2yhAkTGHE0jNtb
STmEkIfPivGXbWJFXTBEWqNU+PxkFMwA/Nhz5zMfChCdGvDh8ODG9T5jaT4dcg+rZvABJEJJ
KA0WbBeRQ2Pku8ZnTpWBZwA7oATmjOsmFMBN3+KHh31up/gbfIoB0bV4Cl3AhUtAMwviLug4
ZVACy23NsOCzWfRYFioBWP6ZFTVWnlIYDZ1GNyZ1HlgQKCCbs54CP+dOwD2lBDCQtZ/B1A8m
HGM/H4RBUf7UhJjP8akxal9lEgvJtMacGMRvDU6RIZUxEIMCiQ9p/OoJqCKcPwOiVvdPvqjp
k9qL51U5VWDeVavwb+2pF0OLJh4Z7X2YyNkxeLUM32rlxj5Z2tLuLqxxZneA5iRgxfY2Q4NQ
RmCsZYM2BqwXeLo/4da0Qq0Z/e5PLD8MARkU0Skz3x0FN+C2D9idjD09jjPVs4bzgCJMCDZ3
IX6duiCXOwIED+cwwT0MZyDg8aY+mmH88vbsir3lDvdAZBfzoW0Z7MQyIIIHew1j4xNAy2RD
AQi7HCMWPYkFOwbemDqqxgHjEMfDINc4r1yH1cNBJMQycz2CUgRXAMh7crWxDRjfMQwEo76C
C5lMiGk1Ib4k+BNYc0ABoAKhN5ZtsyHHcHs0hzUCwoDWDFcfEAqz1tlv7NfW5WXrrP/bAcOl
hwu1/JoLWBaEpBaABuI83QnugAYCcQqG7B30ab3unnT7vwEp7LjbP+v0euz4/JK12EXrst9t
X520LtnF1eXFea9TYazHETFOEJawekTi8jCeDnTL9hXycYHhA4qwPpjo1xyEbXDrGhDUQWVn
d/fLkaDotgtLCiQWWsf8PMAA2HGDMrvxLFxAuxkSJgCxmMus6xiVMtt/wfoYv3N2YesGZxrr
zRFGo1Ets9dg0rDpaQtmXQ09X6P6vMyuei2FtJYPRGAsj/YisjAhEvkUldFy064DtAZiCNgY
pQVsQVbqZrTwAi2IdD3gtwHaNmCxI5THCnxgqM11X5IJLcVmBMPdCFUJuYIhjInaVkbu4SSE
8OYzjRD3xa0ZT/fuBM9dnBcECG2mjySCBMw5sA3mL7/lxjzQhzZQRtIxXWgDYoFZhyhyewTz
HJePoSp53J/buDhV+iLQIa46YQrRhL2Hi5VQvTxamRKPMESLAVq4lwJ4wFy4wyFh2hnIYqBQ
N8gmhpMDGUBr1mweGK6Ja0FAENxTambHXI2onrg3MB096HGt25aJ63I0EMREwEP3XcdnN5PY
Iik4i/Uq2dn1mZGFlT5DewA65Nh3oWoSPVJvTMWyUn9Hn6pMACPQFVpC05W6jjx3GpFDUHzB
nmhOS5cRAimjMSYKsu0HzYfAL0tuqBwVOAFXkZAkBSRvxAzmizClQDnIGlDuAy7XrmVi+AQI
mrQPgnbEuXMdcg0SkB/owZxmmD83JsLnoPkkPS8T9OkcFtgm0BlwKbEEgwE3oELwBCBOFVFI
xgnbJEAbZINoQOFBbhya8iqvwAnACFRtTFwATsBuJpw4jnOP2JVGBPkf8og6J0asqBjBWhtZ
egO+UVoCQV82bRV054XSd9YINAUMDK5e2+dXZ/3O5eAdPIeHuD5KP8cecivzJYUhYfh5JKFF
wM5ap50eLJU7vUIJ1c+foUF2cX/hT2gJsb01wj67OzuFEtthVxBytEVMg5wiExSAIlk4g2Sw
wwxb933pVf1oq4ZmP5khgBM2vdYh5IO+FbKToqNu+2Tkri2To52/sXDO6M6YTA3MGOsauxCc
KUjGNeVgum27N76w48wA3XGn1h96hBmamTDWJg+CyOvoh8oEa8ihJz8HEZPcitu096aPAE/1
IcZNIkgwUd42BPtik87BIkHSQXPBZWC1r4/4eK57ppw8guwpx5VETD32op6v9DkQ5C3Edli5
WyiFvHwZ3MG6C81FH0Qq2KaIhoRHEZjRhJ7wI+SHPzusA+sYSY6YfbQ9CtQA0nrgeqiwoumu
KOBgqDEcOrJT0UjUwDBPZK8WONWxM+VOUI4fXtAeDXh9j2fWvOEZNaB9eZ1EVVavlnTcyqM3
sLYAG+7gLEZkv4S4H4jva3AG97h1737mtKN2MX/ivp3/nusYViqPztwg4+lbmK0gxuTDE9Db
zGYZALAtPQ4pjxHLJb5N0HBW0CmMY9B0U7QqopxFhVcIFGJrWDxiJBZ+gvOd8zB2MkKdTLBN
gVvshx0Pq9usKToU5aPtP7+g/Ukj+wZjCvcuaY8k2mkJXVteAKxg/6OOqcIF63zJg7nnCE+Z
hX0lCarPxjz4BduhQQAbHyTY2sejDOL2IRBH8LYPFquoo0rC98wI26nEirmCW+JC7SMQYMYg
mvJMCqBcCpxaDngO4XfKEYBf5LJqv1KvVI0ya0/0GXLshXD7szz4cvkQwfGIS2DeoIOYWaEz
d4e/cyNIcz5BWgi0VCouIdLk35bIRfjfhEhNi4kE9ZKGK0uEabUA9kBAl9U5gzXpzjCs0lkB
ukQPS8sVUQG+BIi2HMgQj5ojxY/hJOZOulEmwPweT1cB+3RtsC9XgPpyXaBHKwA9WhvTVRjw
cm0GHK0C9ug+sHhwxnEN2IwVu50fDZFyke09yDb/MgiUAWAUbM4Dy7b+EOs2Y4IxY2TwY0sh
/KRSQ/GbYtFFJIjBPnxO0fDQKjIMAv0IkohoF6PZHA9E66LFMFNwDh1S7EL+RmopwsXgWaEw
RVkELKRQ7CgNOXdCLnFzKdWLYfSmRBuAaSbJkhCxxAhpTwoG0PYF1uFyM0I6HdMgL4TVD/0E
IRAtU/NDmwTdrtMmLM2iDD4J3vbX0Z2S6FqEy860dvHdqQx31mVDDGVlNsgexTgUFazYQBNc
KfrccC2iOwKSNWVoFwJZIDtHJMpV5bpMQSEhXuF+VnryyN4C4Rh1sftG60lxovX73DFoDSJ3
XeNxFhGS0Qo2ksUEP6IZvdDz443uOYjpG7kjQVsl8e6OONmLDIEK3KdtJglnIXhE65ITbMnd
kEw16aemszpdykx6IFggrOgP3FBF83UEd20cub8amTchmkVdUfXkoXSFEPwHKYtEyI+1JSUj
cvkp65OazpGoYtf/5SC9g3SKuyPqNlLO1hHt9eCWIO7wJfY3cJMF9IwAVcTGq+hK21Gmv+Jm
DgFa3MT5z23gJDjTFKdohkr6y/5ROXwM64Jmk3os3/DJX9mrwz348l4Fnl7jJymKFvvRrgl+
ZC78T0A8YpkuJCRDtWR8xvQ4eov2HXNjmbRFshxKOlkWrKm7Ow6mRup+8DJNMxC2c1TEfd1t
7YjjE6qNFoa5Du+KlFClMjNEywjB4i3W7DBgGanZEdr6lNoc8FqgdNEItHB71khuJsPilY/R
DNxrDgqp3egKbrD7dz5MsHDfTmwE0yipyFYO4wNQYUqudctWTtHEsHgC5NEedDq2XoypI4uk
xNVgPKQHwcMrxI+Ah9hB0dYNPPyCiJz6C1mj45F7y3w6F9nJ2G/IQeCWWPQLLn6k1D3cOP+V
8iUWaU3tVeMJNfljYfciUsvimFsAwd13iaOfzT48ESaHtyMsr3JoOpLeSLetAANVPHweckr8
kC5LulwxcJqWDp6lW6N7JIhDZkmMAJmePvblqbWiUVEgnPYlsbd3kE0KWfLsfIhHg7fcpLPj
iT7zhafVMZXHdf61quWPbXxS8TONPGB9JGy6smyW5zaUvtvqn5922/FSWsCkzeic5bRg4yCQ
hQM83bF9HoM4Xe7xUuCm8tQ09kHkRA/UQ6NchFXftGIg/38pFi/Lcz5SbxEqR0CWx9FldjOx
jEkIvvqfjerzg3rQ36XhPNYvDejbqwfvmy1gv0X8/XAB90qBdsTEONQO5969oSCm1i5EgwnD
lMvQMAqklKf1IsLEALhTnR8UogVcDAuzLMoTadl8HhS/F+VyCHdb4UkUUi6zoyueAyHq6ROg
OFIKTxAEXnjyHiKmBESxmUzLqCtGlMFMlNsS+sQFfyhdoFz5WvHuZOKIOg4mSf8jI++vaG4j
yyITGcRCSx1aydnAvaoEVnqQiEtB77wgZG0Y1ommC/sDq4ThYYJEUjGQ7koq8E5pA378DRKQ
y8p/lAxkRv2KErhndbBEAKn1QEoAYl2Ql5LyJRVPJJJalAxlkdeiZquwzmmr3WNyvYHvaNkR
Y/2mCLfBKzYZvoZAGSnaUPctQ3NHI7AkTbZHTzsOHVgAKx4sUxmTsldJGcbE65WzlaHxg+Yr
I7zkW4P7z5t7SzOW68+rjxnLjxnLjxnLjxnLjxnLjxnLjxnLjxnLqYzlfrudk7NMNZtlJmef
qPRTJwzN5gqni9sEmtbf6fVGlPAEaztoK7/6YPCMSZGOsRNHFwYa2YXE2KZYG0J/dsiKwqgc
xhlVT4Yw3z8fZECQJj6rf2kVAHEmbBYIbRUQqUzeBJxSKczUuad7lLib6K5p93dP5QQn+lPv
UmmF/tnjU39NS/eXq8P0wkfWxnkdJH35VK78IyX5kq+htMWzoKRrna3eq640xhoam0pVTioL
kwortYVlq8tianMmlKerQpE5zplAjnJgpEBgMrTcChMiSkJ5qUCRbe7HJ5+yo1Upi3K0M8G8
zAVzr16GiTYbKuai6Vzc6foz3DE77r4/7TRFOIMLSBG360w5LKxUKvJskE11w3P/Fe8HKseH
4YHCgLzKIUudNi4eNB4kziGom3Z0n90OZ3tm5xyOfhXrFvPAI+ZJuEm/tPgyRWybNxw4My9z
bSyMSqwF9yCTROX7XNQwETzCIxOBlNNJSWQHxfYwqGC69iqoRA5kfVTyRSQzvlcSSdoRbqwX
MlN8nUETxG9G6brTIHyp5ysnQV6K+5pIrDEHljB+TR7EsdvXciEvR39tNNbgQ2aUk/siwAIm
yXAo/SbVSvy4D4MlaevrovNQfFl4k2FlRKLXyb6eNcvflNgAo4fiTvqFjJVRoRfovp4xS1/2
WBOZh+JJ+n2SldEI3zT8erYsfV1lfXweTFs2nktRfP4QOvMwk0lB6cE0Z2P+JN4+fQD9eRgW
JbHK5NKKh43/uNPE6d5uxbjGkBxPT1KneInKzHPDRIv0HXK1ZuOnVQ4LF4Co94rCv5zb48ov
6IQQzwe175ikYMzhAy8GqNBVeyy+cFG54aug7VS82RQ/At2rjP/A0uzzGD/wgjFNXvK4KUeX
XOCWrM3jac5lbbUfm/s/NfdWuqt1EYp6RVujubd4vZ+8ou3HNa9oS93H9qx4ure9yqV5CP10
D57hPbB4noZXCNOdsLe3YXEmL5kIv7q+FdVhJoU15fj1Y0HsseBjvA44iNqAWoi7iembuEMt
/CZuRZPf0Kj4AtaGUpf3pSKMRVnElXkyj1tseuieBJKSeL25l30pnzxp/0kctJuOTb9Y+pbZ
D6fds+7p1akmL7ossw+tNmqE1j3Wjs+vzt6wD2UWPzo774vHnz592pZwW+3Bm87x1VkxBbxc
KH1Ao6hezBvePivyA8vxxbzJisOL4/cgePmi980ElhPRrbl0/EZ3P3OTFcVRuW5vfwpfY5Q/
EuBAXDM3kHC3nuFo4IG2ynkt8ErbLJTxNC0fb6VWIN+BB2Ea5EMQgAOsQEWiGd3OC0DDC2hv
n+W3xn3W2/Au2lIWBro39mHojKfADJX+JaNsSdAxRn+G1wm3z8GcvC2BD/xCuOBlxwl04CfZ
dtlAu0PLCeeNvIpYghlR8qX4ncuYB+FJDjv+Dk6szgT8BHWniXtxef62mIQcKZjsXwY/QccB
4YAyM2UwtZzDZ7UI3mnv7aD9rtP+uXv2tkgnkaI906I8mCPwKhlQCLrjDmQVaLEqqfj6aYHf
FniaLcfdSjBI6X3HKcUuzl+Puh+ftN72Dv+dgodHTCNbH/v/TjbHy66zGtvWMGyaoiWrtaz6
d5jLGXaZ6r+7XtyRGxN3gTfsL3BiqoXAQ/Yf/N2PxQ8fqtqLT592Pm5Xcr/sfqzt/pBCFJj9
zUetZ4xqeO43HrVBo2bxGNU0e0ys+lY8/raj5vH4246axeMQPMR9sFaDwW9nnjrKs0yFZx+P
0jWI38e/Vul6mNn1++yuqsInRw3F9O1HPcwcNa+rMlcA4cN0FfaNpBDbyGx5kK2sbaV8iTTW
l53e1QkEhNkUV7KpqWRj+kkeGMdWNz2MdCLZxjrtniK6bp/FjZGYlG+2RjggkFD/VGZl1oRg
ForbVJd0AmkvsLWVek7mfmsrDbgRA24IIhUXKv7kQxLydmYdQoeaTxSewX+bLE3Uv6uQsSJN
VWcuT1JtMv5+yI+rLFCWgaE/SVOtZS5RGj/iopR+46IUPKlh8NugPrD1Qe/86rJNS8vhHE8T
KjAa8HrkUmFmzTgVwmu2sZy4Zxof4MXZ+IlXZ1MveRM3ljm+7iVgyOunQxCYV0df5OXeWJya
+/TpT3QBGW/mJoyCmexIN2cPxrY71G1fIulSQVyfnVkVvSqCzeivpMzwcoIAL7zGFFN8I9HD
dE15m/bGiqKMkyU9FY08RVHabLqSTYNRFWW/Wdtr7i9dy9bqLx6zxh+zxh+zxh+zxh+zxh+z
xh+zxv9/Z41nvuC3+bXVWa/64ru7Cy8jL88Pj9+0vjflFptGuYbVzfPEs15qjrO0oxFy3jFe
KZVc9gXVLhLkMlMhbDxEMtk8pGM+fNBBMtLRJQhQoQSE3V05CNpqOng018tT/9/2nrS5bR3J
z86voD1v8mhL1kHbScZnMrFn36vK8cp2ambf1paLkWhHFR0eSY7jqcn89u1uHGyAAEgd2XF2
9SWRiWaj0QAafbEh8XazhfCGEth9g/eMaK4k95I+7NF9l0R4Hf+3t96MhQ7+l/PeXaxbOA3e
iXTBrHgnTl+SvCdLvhTf4WwkVh77wnnzbmq/exp94bApySt5LNkkeE2nP53EbHX7DwyQud0H
JpZiRok790F6D8QdWQ2M1zyp6fyRGs9cqG01+in9O1+OCL/O1OWSM5u9nHKlibTohujWi/2k
mkuuiMa8u7FVTOFBXr1Aj9wLmSXyB6eVX1fKKlWUmEr1byrsgn56X/QCICaHI2AuJwDeo1sl
B2WWKwifRG8u1UWfRy/hN7/5E/jw5pRcuYDipfz5Mvopzt/ZjLaV2UuPz8+ArIuzTecEmxfG
LuB1DSN6vr/7woWIkoGSejuBLQH/qSs6jVSf87NXp2/PQC2nLvAObvyB/8Os3t5NG1Ow/L90
njUG6ecnEfBKs0f9Rv5c/oJ4roQXPHoJy+ed+OPlk+1f371+8+GUZm3715/i6ej2ajLu0NWL
Uq1/UiuHgU5sZzvM1avTU3il0SBvI/mU8TZi2Ng5TeR+hz9P//Pd1Zv3r07PzuHN3+kx9tb/
B7JkOMIkDQqJn796KzzRN238J4lE+lJb/p9IF3I07dyCWd9Gx3MbF+rl2cUlXUcpYyTEzye1
zqes85kjBsIQkq5Sxk4M7/dNW3mHsWuzKaEm8qXv1Xei2s6LelvcQY0kMFj8U6ChBheX0PMu
uPS3t280i37Xv+gdusfaGA7rJA8c9YbkaUaAK1F3FS9wrNHfl+p6S/6Xhn6tLq1WAPkD4WcX
SMzyUxL0Ihukt5/gaCg+4O/ySpASkD/CWio1e5CzMwx6+8mM9+Q8nOdsEdu9wGKnULChAoLI
Bp33bPZgs0TSn/b33KEgla32YuXgXzn453Pw/1/17xuuLrG/mne9Jrrfm5ew687vhkPp+CoC
IsAbWAFZGOScPOAegPd06E9tBBtcum8UGpSYL7YwEV9sZDK82GhJ/SKAIdp586G6HZncg6K+
6mu69Q2H/xvOL5iKilN5oVWZsrm/zxlZrKDtRxV76lSTO5hK2+FbsdHPFh1K+Ytrk2kXPR+w
7w4PqW37+CabvksH+Jk1PKJ2UGzRzDSBN2JEKPU22Dd0611jc8N+i1m5jL602/0L7K+7cSa/
tzDIlE3R02vxw0fwhmxHdFnX1zXrFhqKTIm2QkzZiM9kibp8uPYwPR2LqnLoN8JTiypNpuOb
Th2/bRxv4e8v//XfuTOXEfV1+qEniBN7MBrTfwdla0LIE3hwoIYtXmygVJ2+TYfpDS6cBvBL
L6PoqXop2rRfAzjilyjLiz/39ycoXWB1aG+EBSq2ZzVYvWGrgestXA3c2NTVXmHbHB8cUmFh
uyJodLwAIqNieUVssCYFV7Muxwlv1xfC66fSYJ2F6A9wVsmav828KqSswTBIH+DILxaY5ken
utcAlI379OFEo/grhqlQaZggFOgtAoxqZ06a2VeKnKEGgbqWuJ9TlJzXGDZELUqUBYXymHZB
yTl4bA7JZgsrKSlxw3/xxkY9ugZiMWY8xsgD/WG58lrKOf1Y/HJC6XYaRE713AUZsA1c4IvZ
B06Mpm9qt7W/8zxkIzxvr2yElY2wshFsG4EVUUNvkoxh+26AdoO41H95aTPI5uYvWR8E9Vus
zDOxjYXC1dFCyS6c7h7d+i+9ryBjs1zNkp4TovPiw6+XZw5NQZ+YHDomHfC9/FR44oQRGK/O
3p1SFMe+cJCOEvMYwYOKcgza9fx3cmDZAQUKY6xVnr9LN+rpt+N2slMwDywV3BgLMybW1HBe
XVycncOg4QiM844o6NgSkawgZEKQQIgbtlbLcRKgG6wS0PZ23qvoNCnBFgZjw8XSdu09MZRn
lUj0QDHGYK27RLKn5WGlRakEk6pXkOCjaKfVIuQ79FZEOQJUT7797GRd37ixZr/DdJiSMe74
qF6P1hlkNYoTTFFhq6pAXiJzWMqJSwJrc51BsQL4svL3owuMMq3G9FP7tR8Drkz5MoCXoHqZ
+GZUvNrt3ZXmtdK8VpqXxzvr8m4+qdEpbnlQEPA13qbS/22Ep/FmQe3R8lBGGrePexN0MvWG
N8xRoBvJkRjbmo5CUg3HfdpDFHAQ4a/8IjxJOU4r5hGX0XmTTa9uRqpEg5vY0W3eESY6Y2Iw
60nc8kj86dM0RbfIplk5xD0gTQMdpX/DwhGv4ifT3astGjUsGnEMzzVMdUB9C038hXzjEc35
3HOq5wzIEW3SbwIc746GP0+jj+NR2sXSnJEA4AouqdnCnbO/P+ln2W2812op3CXjqrzOZmVy
cPL+rIbDa0Di8hHoVEJArBnjnTbgUNrHZw+k42NGaIDOpOGfx6RRZSnYGDSH3YtBvbToCvGO
Zxlr6iDC9HnJenmw3Kef4bi8nXWdNZsMFdAl0vHZkq2+EP/5z6h0kM3mxxGdXwiHakAXBwbg
pf2ux/6enz719px33bsO7iJtYSqbwIyzqMwXZJF4qRDQ0RaAe2VJGxftB0aLi1eVSElmIMVa
zt+MuUD1QB1I6U3aG/qWIzqIaTXmsi2fNNBA7kvWHpiJCws53x6fUSrmAqRcVBZFUFBSXvYG
WfevxO5Hc9Ile60FRFlYjDSbeO03Vq4C04bU3kaDbj8FO6Cb9XUE5d90oD1qizkUrmBQ1a3l
ZYQpOLZZLeWdvZWlvLKUV5ZyWYzi9ft3p79ifrY7PmE0Lz82wRV3HZVgUr5wqzLKXcdlxhQA
54eEFh1pf4t6UZIcTgdYdVdT+qUSRegLJDyfrkB3qEf5GWBHFxi9cbGfFJs3o30dIsdgw0Dc
pVind2MBUhe9xy34pbqVOjZsmzV2BomH7gSmf3FqWFwCxUxvmGLA3ZncIw6x6vB0cOeMS4n2
oxbDQGO07+5cUyOLjiiij4/oVfq+TXJfvuq+hZ5NTuFoti5xFUAa4Aq36IGXMgsQCGJTDnoE
fQ+P/4xGEX7HNAQ2nPiIVRfIFnuXw7DXLzEVUx4YB5VhRRePinSO+0/46bfSh69HY9MbpAat
uKxGQitG81ot9BKG2EjU39Y0CtzaCiR/jVTU19CQMNHA8NZwbGrfjRV2PfnYkrONdzDOsOJe
3gbA37wTEO4aOSa1z5yKTdW9mx8FwtQCzl+xiUDyZERG9VwwOshmQdcXzigsC5Big8mJeFku
FhFnkemRXKdfIGpr4vFHbJlD1HbfFYGFEy2ATTtqClk/RVhtqswdK2aCONrSm+SgILa3lDJv
i3aDSeGc0Wz6wRCgud/0iG7qtgkSC0TZ7QKGy+6Cq8rsb5ql49PRvSEv9Of5aizqiT10G5Xl
9j6wGpVr1H7OvG52EzMzD36IOKH6HMZveEiIMmtHgi3B0lGYVlbOyspZWTnLt3Lefrg8+5vb
wtFN3F4RFcxNEwZOZNhJzu8zFjOCSJ+Y2QoiJ6ugUx4DWFpFeZiH06eqsh03i0jObJGWyU0f
UlBGQ2VF+dVUWEhxdHCg9CvlFdb06C8kNEHkJ4YOR7dAqOdrgOv+3eQT9xUjPqRx+9hSzCp3
CDu3A2uuh2fNBNgGc2N2DkgISxSmAlUh4qPSXXOminZQPTn3iDOSW4rYtSCl9HaBN/jaWoC2
Nb8rdE0e+/R/syl398dMuMih33oE+idsqftM7Hl8TsSfyJfESo/VWDFZiPFA96Gaa0fR3ixz
g5ozrtrCBBXnpOoysZVxveAVhx56Wb+rYn59MGZEtSoV/QHJdDMy9HBDN+Q7NOYbLx0SP2m7
pZIfdWOrpUhgnUZW2GpXtq8g51RMmMlrIMqsKOzwCDHGhJe8BRxjbKK3lVj8T/oOjCGVOQO4
UaK/cFnAIMlx+M2H86xzB2f1lywAc3k/upQzOK/dIKdJiT5j2jWZlEMqHTl+nrqNAyEWmGFQ
cHNYGALqPndzuRNVNdcKJBRkKdVEUjwWVKK2B4IClxaoAANUm0Q4herNkVdEnEeFrEHZxXT8
cMZ6EbJCttl71PN4FszfjQo/g/MlxzmsjwnybrUEd5XBR3tyonZ3QlXshj9PVedm4kI7VgHe
Db35pRNRfBiTU21nPKhwrONF/S2NskJZwoKOzLJHjtMlkTFTGJjyXIiq0GK1gvZ3i1UFQeSr
s8QQHo/aIjSrFPjNNAOuzDo0gJdgI5r4ZrYUn68sxZWluLIUg5mj5qfvMrPC+pgWAdHbhfX7
5k6s8CV4fL80DMq/RJV/kl5n/QfU8e8GmSwtqoIMw9H9CfmlQRA/4Hw0hFrf9qZfUD4HIL/p
fdHeyAjTMEhx0B8pCAo0J0EZyrqYYnqTES8FqYMMdkDXdBVrvlRKsHNnoM5EfbJM6sMpLrcj
TDqstCqc4BMgCFDdjphXVhErvzJGSsWAsOTxdCRCNrjJ8S3xkTAWfjUyi32M4j0Ec2hKByYp
ZzfV6+9RlsqHwJRLBlHG0Cdc+x8zLLBxUj7IIhkecO8oEf+3kHxB2VKSuFXCQhdPKqFoL44i
KZvIRyMU/63rvW0NZX4ht4yh+DbXDOsuuKQvxw/WigYrjYK2yoq5v1IWEPWB7hD1KJGPguNY
zzE4U7Xn3xJ6nvIOSmYqTMkCc5UjXoagLWOkJ+c9b67IBjee+dnAKVzSkVCJ64XevK/Mu03e
jYa/Z+PReTYBq6STlSuYOzPJ0t1q0Eh94hfruucq8spD4KLyamcGeVUYii16d6sNxcO9RYey
u8hQ2Jp61I6VULidQVV3qiwj7M6xzexQWX2Ku3KorBwqpaH3CxBJv/3y/vzMHX43mpcfW0eZ
OXNondq1bNgiJPRTCuaSBGSK8wlpHgyma7Ts8yxPfqbAxvIQQ2mzRgyLMSC2x5Viox2D1FTF
orkuh+JJRc4Pt3/xrsoiivlrOr1Xn3+u1F7RWJLFyoCAVXoGXMyKIkGBSt418UsiedjTslb0
WmKDdq6lClkUeSJBviCmylziCQVrnnEXl4cnUVZfqWDkCDgD5f5guMkJ76IyVp54aK8dzl9D
F14gtGzi8YeOlQs3AKK8MKEAtJimAISl0M8dp7bEUfvA35YcFLY+z3r1NAXe2vE37R5Yq8Pg
/+zRchobj5ZrfGJN0vjc7Ykjy5avQe1CUAHPCjA7Hhje124Ixj3s0oxeZKv5ZKfwJCk84XnA
apHwv5MAQTyocWC15O5Iu0V7deyGgh178EMEgoUULIkC50Bl1koOuQRjhSGb0VZ5sbMyVVam
yspU8dV0H2Qw7IdiZXW541gsWDxhlWTQa3Qhv6ebKxK8jDAGw7FgvRV7fOJbETY4Sn5M76aj
q9vp+JBksTzzjmW9oCsw8dK7vtYP4QjC05GDxobGKV47FW9t+qh3IidnmKIxOjpSCaR+/H4H
qacDF789oOEZXAb+0OzOgL/6VPYmeBJ3Z51L+dr3m0zZQflsmgMIs9uGrTafi/UgZ9RdKvxC
iFxmQNO3u7o0l2aDwHcCUjQvEn4K23d818F7GWW+3j4Idv1MivMJYzkIXh0O12hUnnQ6tDsV
1znC036fvkHIqVQvNxfjXLGWV0H83k3wNjG8O2PAYyU6vD8Y5WkpUqsD6Q4jykJoAZ+Y+h9Y
pgs2jMVIdN7u46Au0gkQj9cECMUrFEhF9X8ZkQqNatYwRWul+690/5XuXxqmkPcSOmMUedvy
AxRcl6oeocDvDfCbukzVNTGUJHGik9gMBiBcfmiBtVY7YH5p8Sz6Y7QnI87cJc3NBO5Z9niP
/bqjpDpFso8CFoIVrxDEUSkVfDOm9w2PoiKPGnIXmIxaGAR5whZ0kqJwpjtT8GuY7qhzh7d2
p6IUh4GyepGVXBnHCcUgiBxNIQgiwxTGnFse9FyLWcB9zpD4fdra6i2tJRFCwnW38nITUicL
1pIo8aPzmfaWgcgZMFsNCNPvbC4qe81Vr+pQWCd5oYbc82D7XtluNF8xtWW7WWu9P4ar1rxD
1K85GXBlGpsBvAS1zcRX9XZgqbslyTOtu01XyttKeVspbx7l7cOfgb2ha3YsgLK6Dl8y9JEs
WuqhozY+qXtTHC4s0sPpA0hh/BgexGN2WY/03xL+8jivjocf3c+qGyo0W+IXVxD5BX3U+3E0
eOBQd0OseEVbY4oSoKvLR8ymRRLO4hfHSqGMtwhgMzoGbfLpUwXOMhv/KHt3KJziXbwbRoBs
t0XGw4PzuVJH8X9ZnktjUmQIbVdhyHXfb+ZoKhcZ8Gu/fEbjfKLEx/11k/2pGIat7xKoLAeA
Oq8gWum/XSwVIF/Mp0gVdJA8PWYJsLyaIKPt+5QTpDUXsWl2a7lyTI0c0NZ4i5sp3zXWXY0L
KMM2poC2i+MQnlV3KQIBdvb3u7Q/eTeSPwKQICXHGRoYp5n8EQB+NcFlUwIEGKlXQEj/B0D/
A5YAjPmNuup0Rj1bSR6lwKq/C3d1WfydteiavJEJ9e1Lsev0NUjiWTvZ2Z1Z+dakGw/CqRN8
+kM3hAnc7hRuN3AxdR3GVNy8mhJrhYWI2crvqfJQwCAclJe9on4SXLMpbj4WkYLJVF8AokoJ
kHZx0+lESeNPz04cmNfVqdGO1jXyIBWJwS8vqYBt79lz4xIu+7BUEqmtl1SoSwVs2Kqh7tW7
nATxvS6G5wagOHVIS0BxqbRjULY+9zqfUYfFcMaJg+pDfpzokz6ZZQyee98Y7QYgN8yLa7Mo
00LLs1Zja8l7n135IlarBk75akvd05fGAxakH6pID0zkpwwmCpX0cXYNc4W1l+RJdz0eDWAP
gLr6Vd7ACxLEyYxY84N9jBPq3gOxvR1rroWkT3ggl+YAYOXZI0ANpgeSmLEfkRiPtrcr9exe
Tfmht5iQ01KFZEX4Lka+SnwwbhlfgrJEVDEat8w7I0tkmwGUIwF5V510JRzLqWqH4RlRAmYt
ICkMXaXqDIfJxDplgsJy+kpGjBdTiqsjS1HtcOajbuJnfeGwL2N8zVoPFYRbyyZnt2ygvAfP
nZ2sg2eBLcv0yiozeuy/ozIn8BjvxAwSdVgFzWEJmgSpMTSaQHf8PA+NbjZ8Hjg9iAQGoeeq
DPTYBC0xrko9FcI8NW6EXzgIYWLzWysC+iK9zqYPlcyVorvf6MpnhrDEHHIqkhorvGGiXsrN
iLTbUURfWVAJSuAb+thGoLVdg/Y70RigEb2W0v+mSodpf3rDSqHJE67ZYLmn3kxc5G7naaez
8UM584Hgih51gJzFoQ/gS3bpI8YZnfrPklU+xsqlP59LP/r/6tO/fP26zKtPIEFBKNK4Zzrc
WHagcUQI53ldQ8oSJ4ZshhNuTTl9h3BSCN9nDw7CHt0o0W4/Vw4yhUcq4LEEUmcZJeqKkMQh
d9LaVGwdq3q28sVmc5B+FVRNjvda0TT9nE2iv9Ok6CpXeEna4A6PsuEXGETvBpjD6TZDAhof
jCBpyX5krw28tGP8JYtzqDwTsUO6Hy+4K9xAgngBRZEEo7/eUQtW5GGOEP4C6VyIu08at3eT
T1cf087nWHrmxSULfm7FTwW364AxoUxljYvQbNoJkt8cmTZmaUzd7IizSN+LNbXAl36WDu9u
FWMkQ9VarD71+/swq2R9R7286DdytCeKkurBZTe9Iea00PP1vAH0A3xcq2ED43C8RQ9Yrqfy
s9bQlpeNzFePBdXoGk1dMPZnGcvKnapbjEh9CaTwLyhlCOY/uwEh9GBqdKaxqn2TeXUS84pK
baJSfW3xFwss2NdVehAkBoIkgODb99e1ak/+B2jscrUwFQEA

--OXfL5xGRrasGEqWY--


From cityman@junisphere.net Thu Jan 02 06:10:14 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U3Er-0001LW-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 06:10:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U3En-0001GK-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 06:10:11 -0500
Received: from exavns01gb1.netstore.net ([194.79.241.56])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18U3Em-0001D3-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 06:10:08 -0500
Received: from 194.79.241.49 by exavns01gb1.netstore.net (InterScan E-Mail
	VirusWall NT); Thu, 02 Jan 2003 11:09:56 -0000
Received: from EXBENS01GB1.netstore.local ([194.79.241.50]) by
	exfens02gb1.netstore.local with Microsoft SMTPSVC(5.0.2195.5329);
	Thu, 2 Jan 2003 11:09:55 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6334.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Jan 2003 11:09:55 -0000
Message-ID: <1AD05C34099CE048B5881A7852C61DE001D10970@EXBENS01GB1.netstore.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bug in thread code
Thread-Index: AcKxrLELbYPucDa9TayMxQbE5paNdwAoT45w
From: "Marcel Stadtmann" <cityman@junisphere.net>
To: "Albert Strasheim" <fullung-ccpp@dogbert.sdsl.sun.ac.za>
X-OriginalArrivalTime: 02 Jan 2003 11:09:55.0992 (UTC)
	FILETIME=[7B42A180:01C2B24F]
X-Mailman-Approved-At: Thu, 02 Jan 2003 07:58:37 -0500
cc: bug-commoncpp@gnu.org
Subject: AW: 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: Thu, 02 Jan 2003 11:10:15 -0000

Hello Albert,

Thanks for your help. But i think this is not the real problem.=20
Maybe my discribtion was not correct. On the sample, the thread will =
start,
do his job, and then terminate. For me means this, the resource of this =
thread should be
free after termination. Is this not correct ?? Are there still resources =
allocated ??


Happy New YEAR=20
Marcel





-----Urspr=FCngliche Nachricht-----
Von: Albert Strasheim [mailto:fullung-ccpp@dogbert.sdsl.sun.ac.za]
Gesendet: Mittwoch, 1. Januar 2003 16:44
An: Marcel Stadtmann
Cc: bug-commoncpp@gnu.org
Betreff: Re: Bug in thread code


Hello,

On Tue, 31 Dec 2002, Marcel Stadtmann wrote:

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

Error 11 seems be EAGAIN. It is returned by pthread_create when not=20
enough system resources to create a process for the new thread are=20
available, or more than PTHREAD_THREADS_MAX (16384 on my system)=20
threads are already active.

I am not surprised that starting 1024 threads causes this error. To=20
compare, my system is currently only running about 66 processes in=20
total.

It might be possible to start this many threads using the new pthreads=20
implementation that the RedHat folks are working on (also requires a=20
recent 2.5.x kernel), but any design requiring 1024 threads probably=20
still requires some rethinking.

Cheers,

Albert


From cityman@junisphere.net Thu Jan 02 07:27:50 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U4Ry-0007yF-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 07:27:50 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U4Rw-0007xR-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 07:27:49 -0500
Received: from exavns01gb1.netstore.net ([194.79.241.56])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18U4PM-00078G-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 07:25:08 -0500
Received: from 194.79.241.48 by exavns01gb1.netstore.net (InterScan E-Mail
	VirusWall NT); Thu, 02 Jan 2003 12:25:07 -0000
Received: from EXBENS01GB1.netstore.local ([194.79.241.50]) by
	exfens01gb1.netstore.local with Microsoft SMTPSVC(5.0.2195.5329);
	Thu, 2 Jan 2003 12:25:07 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6334.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Jan 2003 12:25:06 -0000
Message-ID: <1AD05C34099CE048B5881A7852C61DE001D10975@EXBENS01GB1.netstore.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bug in thread code
Thread-Index: AcKyU5sK0LgHYmWQTLixE8XfZNLwOQAA9Diw
From: "Marcel Stadtmann" <cityman@junisphere.net>
To: "Albert Strasheim" <fullung-ccpp@dogbert.sdsl.sun.ac.za>
X-OriginalArrivalTime: 02 Jan 2003 12:25:07.0296 (UTC)
	FILETIME=[FC34FE00:01C2B259]
X-Mailman-Approved-At: Thu, 02 Jan 2003 07:58:37 -0500
cc: bug-commoncpp@gnu.org
Subject: AW: 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: Thu, 02 Jan 2003 12:27:51 -0000

Hello,

-----Urspr=FCngliche Nachricht-----
Von: Albert Strasheim [mailto:fullung-ccpp@dogbert.sdsl.sun.ac.za]
Gesendet: Donnerstag, 2. Januar 2003 12:39
An: Marcel Stadtmann
Cc: bug-commoncpp@gnu.org
Betreff: Re: Bug in thread code


Hello,

On Thu, 02 Jan 2003, Marcel Stadtmann wrote:

> Thanks for your help. But i think this is not the real problem.=20
> Maybe my discribtion was not correct. On the sample, the thread will =
start,
> do his job, and then terminate. For me means this, the resource of=20
> this thread should be free after termination. Is this not correct ??=20
> Are there still resources allocated ??

It seems as if final() in myTCPSession is being called, so the "delete=20
this" probably happens. This starts destructing the thread object, which =

hopefully calls a terminate() somewhere down the line, which stops the=20
thread and cleans up the other bits and pieces.

The obvious scenario related to threads where you could possibly run=20
out of resources is when you start a bunch of joinable threads, but=20
never join on them again, meaning their resources stick around until the =

parent process terminates.

I ran your test, and on my system (using commoncpp2 from CVS) I had=20
completed about 20000 connections before tcpthread segfaulted.

While you wait for someone with a proper clue (i.e. not me :-)) to help=20
you, you might want to try commoncpp2 from CVS and see if your problems=20
persist. You can find instructions for doing a checkout here:

http://savannah.gnu.org/cvs/?group=3Dcommoncpp

I'll poke around the threads code some more today. Good luck!

Cheers,

Albert


Thanks Albert for the fast answer.=20
I have testet this allready with the newest Code from CVS. Still the =
same problem.
But your explanation with the resources seems as its true.

It's is maybe a problem with the thread cleanup code part in commoncpp.
I try to make some additional test's, to give more input.

cheers
Marcel




=20




From dyfet@ostel.com Thu Jan 02 08:01:15 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U4y2-0006oB-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:00:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U4xe-0006Ta-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:00:38 -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 18U4xZ-0006Fx-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:00:29 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h02DX8e27210;
	Thu, 2 Jan 2003 08:33:08 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
   bug-commoncpp@gnu.org
Date: Thu, 2 Jan 2003 08:01:42 -0500
User-Agent: KMail/1.4.3
References: <20021231001633.GA4188@dogbert.sdsl.sun.ac.za>
	<20021231230456.GD415@dogbert.sdsl.sun.ac.za>
	<20030102120906.GB17347@dogbert.sdsl.sun.ac.za>
In-Reply-To: <20030102120906.GB17347@dogbert.sdsl.sun.ac.za>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301020801.42629.dyfet@ostel.com>
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: Thu, 02 Jan 2003 13:01:16 -0000

In the 1.1 release, would it just make more sense to call this Counter an=
d use=20
it in place of what we have in current 1.0.x dists?=20

On Thursday 02 January 2003 07:09, Albert Strasheim wrote:
> Hello,
>
> Attached is a patch that contains the latest version of UberCounter and
> friends, the proposed test framework, and some minor other bits and
> pieces.
>
> I've cleaned up the UberCounter, UberMutexCounter, and UberAtomicCounte=
r
> documentation since the previous patch.
>
> On the test framework front, I've added a custom TestListener class tha=
t
> will allow us to customize the output of the CppUnit test program.
>
> Finally, there are some minor updates to the MAINTAINERCLEANFILES lists
> in some of the Makefile.am files.
>
> Cheers,
>
> Albert



From dyfet@ostel.com Thu Jan 02 08:02:54 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U4zu-0007wp-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:02:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U4zn-0007sz-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:02: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 18U4zZ-0007iy-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:02:33 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h02DZIe27233;
	Thu, 2 Jan 2003 08:35:18 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
   Marcel Stadtmann <cityman@junisphere.net>
Date: Thu, 2 Jan 2003 08:03:53 -0500
User-Agent: KMail/1.4.3
References:
	<1AD05C34099CE048B5881A7852C61DE001D10970@EXBENS01GB1.netstore.local>
	<20030102113917.GA17347@dogbert.sdsl.sun.ac.za>
In-Reply-To: <20030102113917.GA17347@dogbert.sdsl.sun.ac.za>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301020803.53427.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: 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: Thu, 02 Jan 2003 13:02:55 -0000

A self deleting thread never uses join, and hence terminate is meaningles=
s for=20
this scenareo.  So long as the thread is started with detach() rather tha=
n=20
with start(), it should execute in effect as a co-routine and clean itsel=
f=20
when when it exits by deleting itself.

On Thursday 02 January 2003 06:39, Albert Strasheim wrote:
> Hello,
>
> On Thu, 02 Jan 2003, Marcel Stadtmann wrote:
> > Thanks for your help. But i think this is not the real problem.
> > Maybe my discribtion was not correct. On the sample, the thread will
> > start, do his job, and then terminate. For me means this, the resourc=
e of
> > this thread should be free after termination. Is this not correct ?? =
Are
> > there still resources allocated ??
>
> It seems as if final() in myTCPSession is being called, so the "delete
> this" probably happens. This starts destructing the thread object, whic=
h
> hopefully calls a terminate() somewhere down the line, which stops the
> thread and cleans up the other bits and pieces.
>
> The obvious scenario related to threads where you could possibly run
> out of resources is when you start a bunch of joinable threads, but
> never join on them again, meaning their resources stick around until th=
e
> parent process terminates.
>
> I ran your test, and on my system (using commoncpp2 from CVS) I had
> completed about 20000 connections before tcpthread segfaulted.
>
> While you wait for someone with a proper clue (i.e. not me :-)) to help
> you, you might want to try commoncpp2 from CVS and see if your problems
> persist. You can find instructions for doing a checkout here:
>
> http://savannah.gnu.org/cvs/?group=3Dcommoncpp
>
> I'll poke around the threads code some more today. Good luck!
>
> Cheers,
>
> Albert
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Thu Jan 02 08:23:51 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U5JQ-0001Dc-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:23:04 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U5I6-0000CM-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:21:44 -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 18U5GQ-00086q-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:19:58 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h02Dqfe27355;
	Thu, 2 Jan 2003 08:52:42 -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: Thu, 2 Jan 2003 08:21:15 -0500
User-Agent: KMail/1.4.3
References: <20021231001633.GA4188@dogbert.sdsl.sun.ac.za>
	<20021231111009.GD22613@dogbert.sdsl.sun.ac.za>
	<20021231213955.GD32211@bulbasaur.rediris.es>
In-Reply-To: <20021231213955.GD32211@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301020821.15959.dyfet@ostel.com>
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: Thu, 02 Jan 2003 13:23:52 -0000

I am a little hesitent in the idea of putting something new or different =
into=20
the r1 branch, especially since I think this new ubercounter should actua=
lly=20
depreciate the existing counter stuff.  I do not know if anyone uses exis=
ting=20
counters but unless it were a true drop in replacement, there is concern =
will=20
break behavior or interfaces existing apps depend on, and I do not want=20
people to start coding for "ubercounter" if later we make "ubercounter"=20
simply "counter".

On Tuesday 31 December 2002 16:39, Federico Montesino Pouzols wrote:
> Well, both things -the unified counter template and the
> CppUnit tests- are very interesting.
>
> =09One 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.
>
> =09If 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 doxy=
gen
> > 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 t=
o
> > > 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 spli=
t
> > 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
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Thu Jan 02 08:35:32 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U5VG-0004lG-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:35:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U5Uf-0004Ro-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:34: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 18U5Ll-0002Oq-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:25:30 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h02DwFe27391;
	Thu, 2 Jan 2003 08:58:15 -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: Thu, 2 Jan 2003 08:26:50 -0500
User-Agent: KMail/1.4.3
References: <20021230205954.GD409@dogbert.sdsl.sun.ac.za>
	<20021231212702.GC32211@bulbasaur.rediris.es>
In-Reply-To: <20021231212702.GC32211@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301020826.50022.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: 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: Thu, 02 Jan 2003 13:35:41 -0000

The reason they were in a seperate directory originally was that they cam=
e=20
about late in the development of Common C++ and so idea of having a Commo=
n=20
C++ template library was new.  However, the throught at the time was also=
=20
that there were still many C++ compilers in production use that generate=20
template code poorly or incorrectly, and so I thought it was best to make=
 it=20
easy to isolate any template classes from the rest of the library if one=20
simply did not want to make use templates at all or had poor or broken=20
compilers.  Even today, none of the core libccgnu2 classes make use of an=
y=20
template code, although templates are found in some things in libccext2.

On Tuesday 31 December 2002 16:27, Federico Montesino Pouzols wrote:
> 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?
>
> =09The 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 director=
y
> > 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 commo=
n
> > for code that was once "normal" to be extended in future to support
> > templating. Should this code then be moved? I think not.
>
> =09I 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
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Thu Jan 02 08:38:33 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U5YG-0005iK-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:38:24 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U5TR-00043k-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:33:28 -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 18U5Ry-0003my-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:31:54 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h02E4de27458;
	Thu, 2 Jan 2003 09:04:39 -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: Thu, 2 Jan 2003 08:33:14 -0500
User-Agent: KMail/1.4.3
References: <20021229111525.GI420@dogbert.sdsl.sun.ac.za>
	<20021230161135.GB409@dogbert.sdsl.sun.ac.za>
	<20021230211942.GB31551@bulbasaur.rediris.es>
In-Reply-To: <20021230211942.GB31551@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301020833.14844.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: Thu, 02 Jan 2003 13:38:35 -0000

Yes, this is the better way.  I will probably do this for the other Commo=
n C++=20
related libraries (ccScript, ccAudio, and ccRTP) as well...

On Monday 30 December 2002 16:19, Federico Montesino Pouzols wrote:
> 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 =3D xyes; then
> > =09WARN_FLAGS =3D -Wall -ansi -pedantic
> > else
> > =09WARN_FLAGS =3D
> > 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
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Thu Jan 02 08:47:28 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U5ZX-0006F5-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:39:43 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U5Yd-0005x2-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:38: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 18U5XV-0005PU-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 08:37:37 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h02EAPe27510;
	Thu, 2 Jan 2003 09:10:25 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
   bug-commoncpp@gnu.org
Date: Thu, 2 Jan 2003 08:38:59 -0500
User-Agent: KMail/1.4.3
References: <20021229095856.GD420@dogbert.sdsl.sun.ac.za>
In-Reply-To: <20021229095856.GD420@dogbert.sdsl.sun.ac.za>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301020838.59986.dyfet@ostel.com>
Subject: Re: autoconf/automake questions,  use --without-unsafe
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, 02 Jan 2003 13:47:29 -0000

I should have added, as a standard practice, one should build distributio=
n=20
packages with configure "--without-unsafe", which disables all experiment=
al=20
or incomplete drivers.  This (and rather than --without-openh323) should =
be=20
done in the debian master package.

On Sunday 29 December 2002 04:58, 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 on=
e
> 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 fullung@dogbert.sdsl.sun.ac.za Thu Jan 02 10:12:29 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U6fq-0006Lh-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 09:50:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U6Z2-0004WS-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 09:43:20 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18U6Js-0000Tw-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 09:27:37 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18U6Jn-0001WH-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 16:27:31 +0200
Received: (qmail 2512 invoked from network); 2 Jan 2003 14:27:31 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 2 Jan 2003 14:27:31 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18U6Jo-0002O6-00; Thu, 02 Jan 2003 16:27:32 +0200
Date: Thu, 2 Jan 2003 16:27:32 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20030102142732.GF17347@dogbert.sdsl.sun.ac.za>
References: <20021229095856.GD420@dogbert.sdsl.sun.ac.za>
	<200301020838.59986.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301020838.59986.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18U6Jn-0001WH-00*qcE8aUiiZPU*
cc: bug-commoncpp@gnu.org
Subject: Re: autoconf/automake questions,  use --without-unsafe
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, 02 Jan 2003 15:12:30 -0000

Hello,

On Thu, 02 Jan 2003, David Sugar wrote:

> I should have added, as a standard practice, one should build distribution 
> packages with configure "--without-unsafe", which disables all experimental 
> or incomplete drivers.  This (and rather than --without-openh323) should be 
> done in the debian master package.

By the way, I've seen other projects include their "debian" directory 
in CVS. Perhaps you want to invite the Debian maintainer for Common C++ 
to submit a patch to this effect?

Cheers,

Albert


From fullung@dogbert.sdsl.sun.ac.za Thu Jan 02 09:35:55 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U6NZ-0001Nt-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 09:31:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U6Kp-0000ka-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 09:28:39 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18U6Ho-00005N-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 09:25:28 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18U6Hj-0000uX-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 16:25:23 +0200
Received: (qmail 2508 invoked from network); 2 Jan 2003 14:25:22 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 2 Jan 2003 14:25:22 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18U6Hk-0002O2-00; Thu, 02 Jan 2003 16:25:24 +0200
Date: Thu, 2 Jan 2003 16:25:24 +0200
From: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20030102142524.GE17347@dogbert.sdsl.sun.ac.za>
References: <20021230205954.GD409@dogbert.sdsl.sun.ac.za>
	<20021231212702.GC32211@bulbasaur.rediris.es>
	<200301020826.50022.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301020826.50022.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18U6Hj-0000uX-00*d44rSZcDTsw*
X-Mailman-Approved-At: Thu, 02 Jan 2003 11:02:41 -0500
cc: bug-commoncpp@gnu.org
Subject: Re: 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: Thu, 02 Jan 2003 14:35:58 -0000

Hello,

On Thu, 02 Jan 2003, David Sugar wrote:

> The reason they were in a seperate directory originally was that they came 
> about late in the development of Common C++ and so idea of having a Common 
> C++ template library was new.  However, the throught at the time was also 
> that there were still many C++ compilers in production use that generate 
> template code poorly or incorrectly, and so I thought it was best to make it 
> easy to isolate any template classes from the rest of the library if one 
> simply did not want to make use templates at all or had poor or broken 
> compilers.  Even today, none of the core libccgnu2 classes make use of any 
> template code, although templates are found in some things in libccext2.

I was wondering about the distinction between libccgnu2 and libccext2. 
Would it be safe to assume that templated code is okay for libccext2, 
but not for libccgnu2? Are there any other distinctions?

How many commercial compilers are still out there that handle templates 
poorly? I came across an interesting article, C++ portability guide, 
from mozilla.org,

http://www.mozilla.org/hacking/portable-cpp.html

They say to avoid templates. But also to avoid exceptions. (This was 
in 1998.) So I don't know where you draw the line. Personally, if 
you're not using gcc 3.2, you deserve to suffer, but I guess my 
philosophy doesn't work too well for an open source project. :-)

It seems C++ templates have been around since 1995. So one has to ask 
the question: if your compiler doesn't support it after more than 8 
years, is it ever going to support it?

As an aside, is there a reason that the SSL code is also now being 
compiled to another library?

The current layout of the libraries seems to be economizing on headers 
and "spending" on libraries. I'm used to it being the other way round. 
How receptive are you to suggestions for restructuring the headers?

Cheers,

Albert


From fullung@dogbert.sdsl.sun.ac.za Thu Jan 02 09:45:26 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U6P1-0001rV-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 09:32:55 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U6Lq-00014y-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 09:29:43 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18U61z-0005fq-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 09:09:07 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18U61t-0005hC-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 16:09:01 +0200
Received: (qmail 2435 invoked from network); 2 Jan 2003 14:09:01 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 2 Jan 2003 14:09:01 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18U61v-0002Ns-00; Thu, 02 Jan 2003 16:09:03 +0200
Date: Thu, 2 Jan 2003 16:09:03 +0200
From: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20030102140902.GD17347@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>
	<200301020821.15959.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301020821.15959.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18U61t-0005hC-00*XGr9CyVWJI2*
X-Mailman-Approved-At: Thu, 02 Jan 2003 11:02:41 -0500
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: Thu, 02 Jan 2003 14:45:28 -0000

Hello,

On Thu, 02 Jan 2003, David Sugar wrote:

> I am a little hesitent in the idea of putting something new or different into 
> the r1 branch, especially since I think this new ubercounter should actually 

I'm a bit new to the Common C++ scene -- is the r1 branch going to be 
shipping as a 1.0.x release or a 1.1.0 release? If it's a 1.0.x, leave 
UberCounter out of the branch.

> depreciate the existing counter stuff.  I do not know if anyone uses existing 
> counters but unless it were a true drop in replacement, there is concern will 
> break behavior or interfaces existing apps depend on, and I do not want 
> people to start coding for "ubercounter" if later we make "ubercounter" 
> simply "counter".

The reason I didn't design it to be a drop-in replacement is because the 
existing couters were perhaps a bit mmm... random in what they could and 
couldn't do.

I agree that we don't want to rename UberCounter at a later stage.

Cheers,

Albert


From fullung@dogbert.sdsl.sun.ac.za Thu Jan 02 10:14:01 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U6wM-0002Iu-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 10:07:22 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U6rz-0000q2-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 10:02:54 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18U5z3-00052z-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 09:06:05 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18U5yx-000529-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 16:05:59 +0200
Received: (qmail 2431 invoked from network); 2 Jan 2003 14:05:59 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 2 Jan 2003 14:05:59 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18U5yz-0002Nk-00; Thu, 02 Jan 2003 16:06:01 +0200
Date: Thu, 2 Jan 2003 16:06:01 +0200
From: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20030102140600.GC17347@dogbert.sdsl.sun.ac.za>
References: <20021231001633.GA4188@dogbert.sdsl.sun.ac.za>
	<20021231230456.GD415@dogbert.sdsl.sun.ac.za>
	<20030102120906.GB17347@dogbert.sdsl.sun.ac.za>
	<200301020801.42629.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301020801.42629.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18U5yx-000529-00*5HxiQ3tqKRc*
X-Mailman-Approved-At: Thu, 02 Jan 2003 11:02:41 -0500
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: Thu, 02 Jan 2003 15:14:03 -0000

Hello,

I think UberCounter (renamed to Counter) should go into 1.1. Depending 
on how seamless you want the upgrade to be, one might consider renaming 
the existing counters to something like Old[CounterName], marking 
them as deprecated, and keeping them a while longer.

I guess interface changes are painful, but that's the price you have to 
pay sometimes.

Let me know how you want me to proceed.

Cheers,

Albert

On Thu, 02 Jan 2003, David Sugar wrote:

> In the 1.1 release, would it just make more sense to call this Counter and use 
> it in place of what we have in current 1.0.x dists? 
> 
> On Thursday 02 January 2003 07:09, Albert Strasheim wrote:
> > Hello,
> >
> > Attached is a patch that contains the latest version of UberCounter and
> > friends, the proposed test framework, and some minor other bits and
> > pieces.
> >
> > I've cleaned up the UberCounter, UberMutexCounter, and UberAtomicCounter
> > documentation since the previous patch.
> >
> > On the test framework front, I've added a custom TestListener class that
> > will allow us to customize the output of the CppUnit test program.
> >
> > Finally, there are some minor updates to the MAINTAINERCLEANFILES lists
> > in some of the Makefile.am files.
> >
> > Cheers,
> >
> > Albert


From dyfet@ostel.com Thu Jan 02 11:29:40 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U81q-0002gx-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:17:06 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U7yy-0001xI-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:14:10 -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 18U7vE-0001BQ-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:10:16 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h02Gh4e09068;
	Thu, 2 Jan 2003 11:43:05 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Date: Thu, 2 Jan 2003 11:11:41 -0500
User-Agent: KMail/1.4.3
References: <20021229095856.GD420@dogbert.sdsl.sun.ac.za>
	<200301020838.59986.dyfet@ostel.com>
	<20030102142732.GF17347@dogbert.sdsl.sun.ac.za>
In-Reply-To: <20030102142732.GF17347@dogbert.sdsl.sun.ac.za>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301021111.41717.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: autoconf/automake questions,  use --without-unsafe
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, 02 Jan 2003 16:29:44 -0000

We could do this.  I recall there was a reason that originally they wante=
d to=20
keep the debian builds in a seperate cvs, but I do not recall what it was=
 at=20
the time...

On Thursday 02 January 2003 09:27, Albert Strasheim wrote:
> Hello,
>
> On Thu, 02 Jan 2003, David Sugar wrote:
> > I should have added, as a standard practice, one should build
> > distribution packages with configure "--without-unsafe", which disabl=
es
> > all experimental or incomplete drivers.  This (and rather than
> > --without-openh323) should be done in the debian master package.
>
> By the way, I've seen other projects include their "debian" directory
> in CVS. Perhaps you want to invite the Debian maintainer for Common C++
> to submit a patch to this effect?
>
> Cheers,
>
> Albert
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Thu Jan 02 11:52:12 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U8W1-0002Lw-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:48:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U8Vc-0002B9-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:47: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 18U7wU-0001J6-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:11:34 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h02GiNe09074;
	Thu, 2 Jan 2003 11:44:23 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>
Date: Thu, 2 Jan 2003 11:12:59 -0500
User-Agent: KMail/1.4.3
References: <20021231001633.GA4188@dogbert.sdsl.sun.ac.za>
	<200301020821.15959.dyfet@ostel.com>
	<20030102140902.GD17347@dogbert.sdsl.sun.ac.za>
In-Reply-To: <20030102140902.GD17347@dogbert.sdsl.sun.ac.za>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301021112.59894.dyfet@ostel.com>
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: Thu, 02 Jan 2003 16:52:14 -0000

r1 is the 1.0.x tree.  Yes, I tend to agree, to keep uber out of that, an=
d=20
make it the default counter class in -HEAD (for 1.1).

On Thursday 02 January 2003 09:09, Albert Strasheim wrote:
> Hello,
>
> On Thu, 02 Jan 2003, David Sugar wrote:
> > I am a little hesitent in the idea of putting something new or differ=
ent
> > into the r1 branch, especially since I think this new ubercounter sho=
uld
> > actually
>
> I'm a bit new to the Common C++ scene -- is the r1 branch going to be
> shipping as a 1.0.x release or a 1.1.0 release? If it's a 1.0.x, leave
> UberCounter out of the branch.
>
> > depreciate the existing counter stuff.  I do not know if anyone uses
> > existing counters but unless it were a true drop in replacement, ther=
e is
> > concern will break behavior or interfaces existing apps depend on, an=
d I
> > do not want people to start coding for "ubercounter" if later we make
> > "ubercounter" simply "counter".
>
> The reason I didn't design it to be a drop-in replacement is because th=
e
> existing couters were perhaps a bit mmm... random in what they could an=
d
> couldn't do.
>
> I agree that we don't want to rename UberCounter at a later stage.
>
> Cheers,
>
> Albert
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From jjn@kriln.com Thu Jan 02 11:54:56 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U8W6-0002Pi-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:48:22 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U8CR-0005Nz-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:28:34 -0500
Received: from malkav.cac.washington.edu ([140.142.107.26])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18U8Bo-0005Ci-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:27:24 -0500
Received: from nosferatu.kriln.com
	(evrtwa1-ar1-4-47-235-208.evrtwa1.dsl-verizon.net [4.47.235.208])
	by malkav.cac.washington.edu (Postfix) with ESMTP id 110F8CF305
	for <bug-commoncpp@gnu.org>; Thu,  2 Jan 2003 01:20:55 -0800 (PST)
Received: by nosferatu.kriln.com (Postfix, from userid 1000)
	id 904F758F3; Thu,  2 Jan 2003 16:30:46 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by nosferatu.kriln.com (Postfix) with ESMTP id 8B8125507
	for <bug-commoncpp@gnu.org>; Thu,  2 Jan 2003 16:30:46 +0000 (GMT)
Date: Thu, 2 Jan 2003 16:30:46 +0000 (GMT)
From: Jeremy Noetzelman <jjn@kriln.com>
To: bug-commoncpp@gnu.org
Message-ID: <20030102162845.K180-100000@nosferatu.kriln.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Non Threaded use of TCPSocket with select/poll?
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, 02 Jan 2003 16:54:58 -0000

Is there an easy (ie preexisting) way of using the TCPSocket/TCPStream
classes with select or poll without using the threads interface?  It seems
to me at a glance that there's not, and if I want to have a 'real' server
which handles lots of sockets I have to use Threads (SocketService, etc)

Can someone enlighten me?



From dyfet@ostel.com Thu Jan 02 12:07:59 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U8GU-0006Yc-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:32:14 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U82d-0002zH-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:17: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 18U7u7-00010E-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 11:09:07 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h02Gfte09050;
	Thu, 2 Jan 2003 11:41:55 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>
Date: Thu, 2 Jan 2003 11:10:32 -0500
User-Agent: KMail/1.4.3
References: <20021230205954.GD409@dogbert.sdsl.sun.ac.za>
	<200301020826.50022.dyfet@ostel.com>
	<20030102142524.GE17347@dogbert.sdsl.sun.ac.za>
In-Reply-To: <20030102142524.GE17347@dogbert.sdsl.sun.ac.za>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301021110.32274.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: 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: Thu, 02 Jan 2003 17:08:01 -0000

Templating is not the only issue that distinguishes ccext and ccgnu.  Thi=
ngs=20
that require or induce new library link requirements also are in ccext. =20
Hence, for example, if you do not wish to use XML parsing in your=20
application, why create an unused library dependency for libxml2?  The id=
ea=20
being that one can, if one needs to, use only "core" features found in=20
libccgnu2 and then create very compact executables with very few addition=
al=20
library dependencies.   This also is the reason that ccssl is seperate. =20
Since "openssl" is already a very large library image in itself, it seeme=
d=20
best to use a seperate libccssl to isolate that dependency, since I expec=
t=20
ssl will be far less commonly used in most Common C++ applications than X=
ML=20
parsing or other things already commonly found in ccext2.

On Thursday 02 January 2003 09:25, Albert Strasheim wrote:
> Hello,
>
> On Thu, 02 Jan 2003, David Sugar wrote:
> > The reason they were in a seperate directory originally was that they
> > came about late in the development of Common C++ and so idea of havin=
g a
> > Common C++ template library was new.  However, the throught at the ti=
me
> > was also that there were still many C++ compilers in production use t=
hat
> > generate template code poorly or incorrectly, and so I thought it was
> > best to make it easy to isolate any template classes from the rest of=
 the
> > library if one simply did not want to make use templates at all or ha=
d
> > poor or broken compilers.  Even today, none of the core libccgnu2 cla=
sses
> > make use of any template code, although templates are found in some
> > things in libccext2.
>
> I was wondering about the distinction between libccgnu2 and libccext2.
> Would it be safe to assume that templated code is okay for libccext2,
> but not for libccgnu2? Are there any other distinctions?
>
> How many commercial compilers are still out there that handle templates
> poorly? I came across an interesting article, C++ portability guide,
> from mozilla.org,
>
> http://www.mozilla.org/hacking/portable-cpp.html
>
> They say to avoid templates. But also to avoid exceptions. (This was
> in 1998.) So I don't know where you draw the line. Personally, if
> you're not using gcc 3.2, you deserve to suffer, but I guess my
> philosophy doesn't work too well for an open source project. :-)
>
> It seems C++ templates have been around since 1995. So one has to ask
> the question: if your compiler doesn't support it after more than 8
> years, is it ever going to support it?
>
> As an aside, is there a reason that the SSL code is also now being
> compiled to another library?
>
> The current layout of the libraries seems to be economizing on headers
> and "spending" on libraries. I'm used to it being the other way round.
> How receptive are you to suggestions for restructuring the headers?
>
> Cheers,
>
> Albert



From fullung@dogbert.sdsl.sun.ac.za Thu Jan 02 12:34:46 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U9EB-0004bV-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 12:33:55 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U9Du-0004Wq-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 12:33:40 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18U9AQ-0002iW-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 12:30:02 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18U9AI-0003IL-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 19:29:54 +0200
Received: (qmail 3291 invoked from network); 2 Jan 2003 17:29:54 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 2 Jan 2003 17:29:54 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18U9AJ-0002PQ-00
	for <bug-commoncpp@gnu.org>; Thu, 02 Jan 2003 19:29:55 +0200
Date: Thu, 2 Jan 2003 19:29:55 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20030102172955.GG17347@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/)
	*18U9AI-0003IL-00*NmzYZ6Ln4WY*
Subject: Some issues with the codebase
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, 02 Jan 2003 17:34:51 -0000

Hello,

While looking at some of the code in Common C++, I've noticed a few 
general issues that we might want to address.

Firstly, identifier names. Here's an important quote from the C++ 
standard via mozilla.org's C++ portability guide, available at
http://www.mozilla.org/hacking/portable-cpp.html,

"Certain sets of names and function signatures are always reserved to 
the implementation:

    * Each name that contains a double underscore (__) or begins with an 
underscore followed by an uppercase letter (2.11) is reserved to the 
implemenation for any use.
    * Each name that begins with an underscore is reserved to the
implementaiton for use as a name in the global namespace."

I've seen many member variables whose names start with an underscore. As 
far as I understand, this is Very, Very Evil(TM). If you really want an 
underscore in your identifier name, stick it on the end.

Secondly, what's up with the Common C++ namespace being called "ost"? I 
assume this stands for Open Source Telecom? If another company were to 
contribute code to this project, are we going to start seeing "acme" and 
other namespaces too? :-)

I think Common C++ deserves a vendor-neutral namespace, say... mmm... 
"ccxx"? :-)

To provide backward compatability for a while, I think following 
declaration sprinkled through some of the headers will do the trick:

#ifdef CCXX_NAMESPACES
/**
 * Old Common C++ namesspace (DEPRECATED).
 */
namespace ost
{
  using namespace ccxx;
}
#endif

Don't know exactly how one convinces doxygen to add a description for a 
namespace, but anyway.

Comments?

Cheers,

Albert


From cyates@uidaho.edu Thu Jan 02 20:59:42 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UH7e-0002Nx-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 20:59:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UH7b-0002KT-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 20:59:41 -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 18UH7b-0002K3-00
	for bug-commoncpp@gnu.org; Thu, 02 Jan 2003 20:59:39 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H84002TT87DGY@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 02 Jan 2003 17:59:38 -0800 (PST)
Date: Thu, 02 Jan 2003 17:59:38 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp@gnu.org
Message-id: <NBBBJJODBJBNJFNIDDCNCEOHDDAA.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: bugs in CRC32
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, 03 Jan 2003 01:59:43 -0000

I have discovered and fixed some bugs in the CRC32Digest class while
developing test cases for the digest classes.

1) the virtual function overflow was not being called (at least on win32) so
I changed the argument and return type to int (as in the other digest
classes)...

2) the lookup table was not using "reflection" during its initialization
(apparently this is a part of the CRC32 standard implementation) so I added
a reflect function and changed (replaced) the lookup code to use it. I
commented out the old code so you can see it in the diff.

3) I moved the crc32 = 0 from the constructor to the initDigest method so it
is reset both during construction and reseting.

4) I removed the crc32 = ~crc_reg in the overload method and moved it to
both the getDigest and strDigest methods as a minor performance improvement
(won't be re-computed for every octet in the stream)

finally, I checked the output agains two programs available on the net, and
it matches both, however the existing CRC32 demo program now reports all
failures.  I suspect that the tests were not valid to begin with, but if
anyone would like to verify this (or comment) please do so.

,chad

Index: digest.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/digest.h,v
retrieving revision 1.10
diff -r1.10 digest.h
204c204
<    unsigned char overflow(unsigned char octet);
---
>    int overflow(int octet);
207c207,209
<
---
>
>    unsigned long reflect(unsigned long ref, unsigned char ch);
>

Index: digest.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/digest.cpp,v
retrieving revision 1.4
diff -r1.4 digest.cpp
145d144
<    crc32 = 0;
161,172c160,182
<    for (i = 0; i < 256; i++)
<    {
<       crc = ( (unsigned long) i << 24 );
<       for (j = 0; j < 8; j++)
<       {
<          if (crc & 0x80000000)
<             crc = (crc << 1) ^ POLYNOMIAL;
<          else
<             crc <<= 1;
<       }
<       crc_table[i] = crc;
<    }
---
>   for(i = 0; i <= 0xFF; i++)
>   {
>     crc=reflect(i, 8) << 24;
>     for (j = 0; j < 8; j++)
>       crc = (crc << 1) ^ (crc & (1 << 31) ? POLYNOMIAL : 0);
>     crc_table[i] = reflect(crc, 32);
>   }
>   /* old loop without reflection
>   for (i = 0; i < 256; i++)
>   {
>     crc = ( (unsigned long) i << 24 );
>     for (j = 0; j < 8; j++)
>     {
>       if (crc & 0x80000000)
>         crc = (crc << 1) ^ POLYNOMIAL;
>       else
>         crc <<= 1;
>     }
>     crc_table[i] = crc;
>   }
>   */
>
>    crc32 = 0;
175c185,201
< unsigned char CRC32Digest::overflow(unsigned char octet)
---
> unsigned long CRC32Digest::reflect(unsigned long ref, unsigned char ch)
> {
>   unsigned long value = 0;
>
>   // Swap bit 0 for bit 7
>   // bit 1 for bit 6, etc.
>   for(int i = 1; i < (ch + 1); i++)
>   {
>     if(ref & 1)
>       value |= 1 << (ch - i);
>     ref >>= 1;
>   }
>
>   return value;
> }
>
> int CRC32Digest::overflow(int octet)
177,179c203,206
<    crc_reg = crc_table[((crc_reg >> 24) ^ octet) & 0xFF] ^ (crc_reg << 8);
<    crc32 = ~crc_reg;
<
---
>    //crc_reg = crc_table[((crc_reg >> 24) ^ octet) & 0xFF] ^ (crc_reg <<
8);
>        crc_reg = (crc_reg >> 8) ^ crc_table[(crc_reg & 0xFF) ^ octet];
>    //crc32 = ~crc_reg; deferred calculation until later rather than for
every
byte
>
184a212
>    crc32 = ~crc_reg; // finalize crc32 before exporting
198a227
>    crc32 = ~crc_reg;  // finalize crc32 before exporting



From cyates@uidaho.edu Fri Jan 03 01:28:55 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ULKB-0007WT-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 01:28:55 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ULK7-0007UK-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 01:28:54 -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 18ULK6-0007T0-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 01:28:50 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H84002D6KNWGY@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 02 Jan 2003 22:28:45 -0800 (PST)
Date: Thu, 02 Jan 2003 22:28:44 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp@gnu.org
Message-id: <NBBBJJODBJBNJFNIDDCNEEOIDDAA.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: Small bug in MD5Digest
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, 03 Jan 2003 06:28:55 -0000

I have isolated the bug in the MD5Digest class as pointed out by Albert.  It
appears that if you use a MD5Digest, and then .initDigest and then export
the digest, the last value is reported.  I have attributed it to code in
initDigest that sets updated equal to false which apparently keeps it from
updating the internal digest.  changing this seems to fix it without
breaking my other test cases (Construction, Empty Message, Small Message,
Re-Initialization, Large Message, Piecewise Message, and Typical Usage).

If someone that is an expert on the md5 class and the algorithm (I know very
little about the internals of the md5 algorithm), can they let me know if
this sounds right.

thanks,

Chad

P.S if this is correct we should also be able to remove the updated = true
line in the constructor after the call to initDigest.

Index: md5.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/md5.cpp,v
retrieving revision 1.2
diff -r1.2 md5.cpp
142c142,143
<       updated = false;
---
>       //updated = false;
>       updated = true; // CCY Added



From cyates@uidaho.edu Fri Jan 03 01:38:00 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ULSy-0007Sv-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 01:38:00 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ULSu-0007Sk-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 01:37:59 -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 18ULSu-0007Ly-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 01:37:56 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8400J1LL34YV@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 02 Jan 2003 22:37:52 -0800 (PST)
Date: Thu, 02 Jan 2003 22:37:52 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20030102142524.GE17347@dogbert.sdsl.sun.ac.za>
To: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>,
 David Sugar <dyfet@ostel.com>
Message-id: <NBBBJJODBJBNJFNIDDCNMEOIDDAA.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
cc: bug-commoncpp@gnu.org
Subject: RE: 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: Fri, 03 Jan 2003 06:38:00 -0000

I also read that portable-cpp file a while ago and was actually appauled by
it.  It's my opinion that if compilers should be updated to the standard
(expected) functionality or new compilers should be found/used.  they pretty
much said not to use any of C++'s nice features, they may as well have said
just don't use C++.  Please don't let common c++ go that direction.

my 2 cents

,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: Thursday, January 02, 2003 6:25 AM
> To: David Sugar
> Cc: bug-commoncpp@gnu.org
> Subject: Re: Headers and templated classes
>
(snip)
> How many commercial compilers are still out there that handle templates
> poorly? I came across an interesting article, C++ portability guide,
> from mozilla.org,
>
> http://www.mozilla.org/hacking/portable-cpp.html
>
> They say to avoid templates. But also to avoid exceptions. (This was
> in 1998.) So I don't know where you draw the line. Personally, if
> you're not using gcc 3.2, you deserve to suffer, but I guess my
> philosophy doesn't work too well for an open source project. :-)
>
> It seems C++ templates have been around since 1995. So one has to ask
> the question: if your compiler doesn't support it after more than 8
> years, is it ever going to support it?
(snip)



From cyates@uidaho.edu Fri Jan 03 01:38:51 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ULTn-0007iR-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 01:38:51 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ULTj-0007hv-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 01:38:50 -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 18ULTi-0007hl-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 01:38:47 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8400J3WL4KYV@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 02 Jan 2003 22:38:44 -0800 (PST)
Date: Thu, 02 Jan 2003 22:38:44 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20021231213955.GD32211@bulbasaur.rediris.es>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-id: <NBBBJJODBJBNJFNIDDCNOEOIDDAA.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
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: Fri, 03 Jan 2003 06:38:51 -0000

I have sent what I have done so far to Albert to compare with his so we can
see how they will integrate.  I imagine after he reviews it we can decide
how best to integrate it into the library and/or build process.  I wouldn't
think we need to rush it into a release, but integrate it progressively
stomping any bugs we find along the way.

,chad

> -----Original Message-----
> From: bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org
> [mailto:bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org]On Behalf Of
> Federico Montesino Pouzols
> Sent: Tuesday, December 31, 2002 1:40 PM
> To: Albert Strasheim
> Cc: bug-commoncpp@gnu.org
> Subject: Re: Test framework; new counter class
>
>
>
> 	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
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Fri Jan 03 02:35:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UMMA-00026u-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 02:35:02 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UMHL-0006SN-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 02:30:03 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UMHE-0006Rr-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 02:30:02 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UMHD-0006Rj-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 02:29:55 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18UMHB-0002Vg-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:29:53 +0200
Received: (qmail 5536 invoked from network); 3 Jan 2003 07:29:52 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 3 Jan 2003 07:29:52 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18UMH7-0000ag-00; Fri, 03 Jan 2003 09:29:49 +0200
Date: Fri, 3 Jan 2003 09:29:49 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030103072949.GC887@dogbert.sdsl.sun.ac.za>
References: <20021231213955.GD32211@bulbasaur.rediris.es>
	<NBBBJJODBJBNJFNIDDCNOEOIDDAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNOEOIDDAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18UMHB-0002Vg-00*RqU2PWjvoPQ*
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: Fri, 03 Jan 2003 07:30:04 -0000

Hello,

On Thu, 02 Jan 2003, Chad Yates wrote:

> I have sent what I have done so far to Albert to compare with his so we can
> see how they will integrate.  I imagine after he reviews it we can decide
> how best to integrate it into the library and/or build process.  I wouldn't
> think we need to rush it into a release, but integrate it progressively
> stomping any bugs we find along the way.

I've looked over Chad's stuff. Sweet.

I'll have to look my own code over and make sure it plays nice with the 
test factory stuff. I'll do this today.

One thing that needs to get done is to improve the test "driver" 
program. I think the custom TestListener I coded is a step in the right 
direction (gone are the .'s in strange places in the test output). 
Furthermore, we need to add support for a few command line options -- 
stuff to run specific tests, skip specific tests, and some other bits 
like outputting "compiler output" for MSVC so that the IDE can send you 
directly to the line where the test failed.

This is probably a good test for CommandOption and friends. I'll take 
this on if no-one else is particularly interested.

Also, we need to decide on a naming convention for the test files. I 
suggest the following:

1. Move demo/* and test/* to a new "examples" directory.

Reasons: old tests are probably deprecated, but could still serve as 
examples (or be removed once we've integrated them); probably don't want 
_examples_ in the "demo" directory; when I think "demo", I think a big 
monolithic piece of code; CppUnit project put their examples in the 
"examples" directory.

As an aside, the CppUnit source tree is, for me, an example of good 
organisation. I think the Common C++ project should look to emulate 
their source tree layout as far as possible, although we are similar in 
many respects already.

2. Put the tests in tests/test_<ClassName>.{cpp,h,tcc}.

Reasons: the name is reasonably unambigious, easily grepable, etc.

In the case where you can use a class (templated or not) to test derived 
classes, we could probably add tests for the derived classes to 
test_<BaseClass>.{cpp,h,tcc}, like I did with the UberCounter tests.

A good guideline would probably be: one library header, one set of test 
files, but this breaks down for thread.h and others, since it has about 
10 classes in there (which should be split up, IMHO).

Comments?

Cheers,

Albert



From MAILER-DAEMON Fri Jan 03 08:10:04 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18URaN-0004QU-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:10:03 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UMuO-0006Ke-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 03:10:24 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UMuK-0006Ij-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 03:10:23 -0500
Received: from mxout3.netvision.net.il ([194.90.9.24])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UMuJ-0006HA-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 03:10:19 -0500
Received: from localhost.localdomain ([62.0.180.144])
 by mxout3.netvision.net.il
 (iPlanet Messaging Server 5.2 HotFix 1.08 (built Dec  6 2002))
 with ESMTP id <0H840003APCYF3@mxout3.netvision.net.il> for
 bug-commoncpp@gnu.org; Fri, 03 Jan 2003 10:10:12 +0200 (IST)
Date: Fri, 03 Jan 2003 10:10:17 +0200
From: Roee Friedman <roee_fr@netvision.net.il>
To: bug-commoncpp@gnu.org
Message-id: <200301031010.17837.roee_fr@netvision.net.il>
MIME-version: 1.0
X-Mailer: KMail [version 1.4]
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Mailman-Approved-At: Fri, 03 Jan 2003 08:10:01 -0500
Subject: Included files order
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, 03 Jan 2003 08:10:25 -0000

Hello!
I have seen the problem discussed about a year ago, but it still not fixed.
I am using CC++ 2 (1.0.7).
It seems that still the inclusion of <fstream> or <iostream> before 
<cc++/socket.h> breaks the compilation with error:

In file included from /usr/local/include/cc++/socket.h:54,
                 from MailServer.h:3,
                 from mailclin.h:10,
                 from mailclin.cpp:1:
/usr/local/include/cc++/thread.h:320: syntax error before `;'

the order of inclusion is:

#include <fstream>
#include <iostream>
#include <cstdio>
#include <new>

#include "MailServer.h"  // <-- This file includes <cc++/socket.h>

In order to compile the project, I either have to move the last include to be 
the first or include <cc++/socket.h> first.

Roee




From MAILER-DAEMON Fri Jan 03 08:13:56 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18URe7-00073G-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:13:55 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18URe4-0006qt-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:13:52 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18URdu-0006MI-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:13: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 18URdt-0006G4-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:13:41 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h03Dkfe23066;
	Fri, 3 Jan 2003 08:46:41 -0500
From: David Sugar <dyfet@ostel.com>
Date: Fri, 3 Jan 2003 08:15:32 -0500
User-Agent: KMail/1.4.3
To: bug-commoncpp@gnu.org
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="------------Boundary-00=_WH35KXT5I525L2GYRLIR"
Message-Id: <200301030815.32759.dyfet@ostel.com>
cc: Ying-Chieh Liao <ijliao@csie.nctu.edu.tw>
Subject: Fwd: FreeBSD ports : 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: Fri, 03 Jan 2003 13:13:53 -0000


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

Let's see what the list thinks of it, since we do want to make sure the n=
ext=20
point release is bsd clean...

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

Subject: FreeBSD ports : commoncpp
Date: Fri, 3 Jan 2003 15:51:38 +0800
From: Ying-Chieh Liao <ijliao@csie.nctu.edu.tw>
To: dyfet@gnu.org
Cc: Ying-Chieh Liao <ijliao@csie.nctu.edu.tw>

what do you think about pr/44205 ?

http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/44205
--
char*p=3D"char*p=3D%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,=
p,34);}
=09=09=09=09=09-- Anonymous

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


--------------Boundary-00=_WH35KXT5I525L2GYRLIR
Content-Type: application/pgp-signature;
  charset="us-ascii";
  name="Attachment: 1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)

iD8DBQE+FUEKrMYBZRHAI4IRAm+iAKC+mRibUxANITcCRKoY8lorhe0OSgCgo+YR
ishRsqTyvnx5ZURjPA4gnYs=
=JqBB
-----END PGP SIGNATURE-----

--------------Boundary-00=_WH35KXT5I525L2GYRLIR--




From MAILER-DAEMON Fri Jan 03 08:20:22 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18URkM-0006Cg-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:20:22 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18URkJ-0006BG-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:20:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18URkH-0006AX-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:20: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 18URkG-00069j-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:20:16 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h03Dr4e23109;
	Fri, 3 Jan 2003 08:53:04 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
   Chad Yates <cyates@uidaho.edu>
Date: Fri, 3 Jan 2003 08:21:56 -0500
User-Agent: KMail/1.4.3
References: <20021231213955.GD32211@bulbasaur.rediris.es>
	<NBBBJJODBJBNJFNIDDCNOEOIDDAA.cyates@uidaho.edu>
	<20030103072949.GC887@dogbert.sdsl.sun.ac.za>
In-Reply-To: <20030103072949.GC887@dogbert.sdsl.sun.ac.za>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301030821.56347.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: Test framework; and what should be in 1.1.0
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, 03 Jan 2003 13:20:19 -0000

At this point, it seems destined for the 1.1 release, and no date has bee=
n set=20
yet for when that will be made available.  So, no, there is no immediate =
rush=20
:).

It might be worth asserting what things remain to be done for a 1.1 relea=
se to=20
occur, and for that I would like to suggest the following:

* from the threading perspective, support for pth based ng Linux threadin=
g,=20
and alternate compile option that can compile for systems that use the pt=
h=20
library.

* completion (by me) of ccssl...

* integration of new counter code

* addition of IP6Address classes and ip6 socket support.  (this may actua=
lly=20
be fairly easy to add...)

* new testing framework

Any comments on this?

On Friday 03 January 2003 02:29, Albert Strasheim wrote:
> Hello,
>
> On Thu, 02 Jan 2003, Chad Yates wrote:
> > I have sent what I have done so far to Albert to compare with his so =
we
> > can see how they will integrate.  I imagine after he reviews it we ca=
n
> > decide how best to integrate it into the library and/or build process=
=2E  I
> > wouldn't think we need to rush it into a release, but integrate it
> > progressively stomping any bugs we find along the way.
>
> I've looked over Chad's stuff. Sweet.
>
> I'll have to look my own code over and make sure it plays nice with the
> test factory stuff. I'll do this today.
>
> One thing that needs to get done is to improve the test "driver"
> program. I think the custom TestListener I coded is a step in the right
> direction (gone are the .'s in strange places in the test output).
> Furthermore, we need to add support for a few command line options --
> stuff to run specific tests, skip specific tests, and some other bits
> like outputting "compiler output" for MSVC so that the IDE can send you
> directly to the line where the test failed.
>
> This is probably a good test for CommandOption and friends. I'll take
> this on if no-one else is particularly interested.
>
> Also, we need to decide on a naming convention for the test files. I
> suggest the following:
>
> 1. Move demo/* and test/* to a new "examples" directory.
>
> Reasons: old tests are probably deprecated, but could still serve as
> examples (or be removed once we've integrated them); probably don't wan=
t
> _examples_ in the "demo" directory; when I think "demo", I think a big
> monolithic piece of code; CppUnit project put their examples in the
> "examples" directory.
>
> As an aside, the CppUnit source tree is, for me, an example of good
> organisation. I think the Common C++ project should look to emulate
> their source tree layout as far as possible, although we are similar in
> many respects already.
>
> 2. Put the tests in tests/test_<ClassName>.{cpp,h,tcc}.
>
> Reasons: the name is reasonably unambigious, easily grepable, etc.
>
> In the case where you can use a class (templated or not) to test derive=
d
> classes, we could probably add tests for the derived classes to
> test_<BaseClass>.{cpp,h,tcc}, like I did with the UberCounter tests.
>
> A good guideline would probably be: one library header, one set of test
> files, but this breaks down for thread.h and others, since it has about
> 10 classes in there (which should be split up, IMHO).
>
> Comments?
>
> Cheers,
>
> Albert
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Fri Jan 03 08:35:09 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18URyb-0003IW-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:35:05 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18URy7-0002eV-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:34:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18URtI-0000ti-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:29:38 -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 18URt9-0000p9-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 08:29:27 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h03E2Je23185;
	Fri, 3 Jan 2003 09:02:19 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Chad Yates <cyates@uidaho.edu>,
   Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>
Date: Fri, 3 Jan 2003 08:31:10 -0500
User-Agent: KMail/1.4.3
References: <NBBBJJODBJBNJFNIDDCNMEOIDDAA.cyates@uidaho.edu>
In-Reply-To: <NBBBJJODBJBNJFNIDDCNMEOIDDAA.cyates@uidaho.edu>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301030831.10927.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: 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: Fri, 03 Jan 2003 13:35:04 -0000

Ah yes, the mozilla c++ recommendations...

We may choose to keep the ccgnu2 half very clean in large part to enable =
one=20
to build very compact applications with Common C++, but I do not think we=
=20
ever got that anal even in that.  If anything, as practices and compilers=
=20
improve, we will continue to make greater use of the C++ language standar=
d in=20
full.  However, the reality is that many broken compilers and poor std=20
library/stl implimentations still remain in everyday use so we do have to=
=20
pick and choose what language features we will make use of extensivily an=
d=20
which we will not.  I much prefer isolating language features with=20
troublesome implimention history rather than excluding them, which is why=
 we=20
had the templates library segregated, for example, or extensive facilitie=
s to=20
built with or without exception handling.=20

On Friday 03 January 2003 01:37, Chad Yates wrote:
> I also read that portable-cpp file a while ago and was actually appaule=
d by
> it.  It's my opinion that if compilers should be updated to the standar=
d
> (expected) functionality or new compilers should be found/used.  they
> pretty much said not to use any of C++'s nice features, they may as wel=
l
> have said just don't use C++.  Please don't let common c++ go that
> direction.
>
> my 2 cents
>
> ,Chad
>
> > -----Original Message-----
> > From: bug-commoncpp-bounces+cyates=3Duidaho.edu@gnu.org
> > [mailto:bug-commoncpp-bounces+cyates=3Duidaho.edu@gnu.org]On Behalf O=
f
> > Albert Strasheim
> > Sent: Thursday, January 02, 2003 6:25 AM
> > To: David Sugar
> > Cc: bug-commoncpp@gnu.org
> > Subject: Re: Headers and templated classes
>
> (snip)
>
> > How many commercial compilers are still out there that handle templat=
es
> > poorly? I came across an interesting article, C++ portability guide,
> > from mozilla.org,
> >
> > http://www.mozilla.org/hacking/portable-cpp.html
> >
> > They say to avoid templates. But also to avoid exceptions. (This was
> > in 1998.) So I don't know where you draw the line. Personally, if
> > you're not using gcc 3.2, you deserve to suffer, but I guess my
> > philosophy doesn't work too well for an open source project. :-)
> >
> > It seems C++ templates have been around since 1995. So one has to ask
> > the question: if your compiler doesn't support it after more than 8
> > years, is it ever going to support it?
>
> (snip)
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Fri Jan 03 09:37:49 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18USxJ-0006HG-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:37:49 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18USxG-0006Dc-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:37:46 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18USxE-0006C3-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:37:46 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18USxD-0006Bq-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:37:43 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18USxA-0007TV-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 16:37:40 +0200
Received: (qmail 6253 invoked from network); 3 Jan 2003 14:37:40 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 3 Jan 2003 14:37:40 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18USx7-0001Jt-00; Fri, 03 Jan 2003 16:37:37 +0200
Date: Fri, 3 Jan 2003 16:37:37 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20030103143737.GG887@dogbert.sdsl.sun.ac.za>
References: <20021231213955.GD32211@bulbasaur.rediris.es>
	<NBBBJJODBJBNJFNIDDCNOEOIDDAA.cyates@uidaho.edu>
	<20030103072949.GC887@dogbert.sdsl.sun.ac.za>
	<200301030821.56347.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301030821.56347.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18USxA-0007TV-00*2ZhAc2zpc2E*
cc: bug-commoncpp@gnu.org
Subject: Re: Test framework; and what should be in 1.1.0
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, 03 Jan 2003 14:37:47 -0000

Hello,

On Fri, 03 Jan 2003, David Sugar wrote:

> At this point, it seems destined for the 1.1 release, and no date has been set 
> yet for when that will be made available.  So, no, there is no immediate rush 
> :).

Still, I think Chad and I will be able to prepare a nice patch in the 
next week or two which should go into CVS; then other people can start 
writing tests too.
 
> It might be worth asserting what things remain to be done for a 1.1 release to 
> occur, and for that I would like to suggest the following:
> 
> * from the threading perspective, support for pth based ng Linux threading, 
> and alternate compile option that can compile for systems that use the pth 
> library.

Seems Pth is licensed under the LGPL. Cool.

As I understand, Pth provides a layer on top of POSIX-conformant thread 
implementations on Unix platforms. Is this correct?

Seems you want to provide a Thread class implemented on top of Pth? 
Isn't the pthread_* code always going to be inferior to this 
implementation?

> * completion (by me) of ccssl...
> 
> * integration of new counter code

I will make a final patch for this once we've merged the test framework 
code.
 
> * addition of IP6Address classes and ip6 socket support.  (this may actually 
> be fairly easy to add...)
> 
> * new testing framework

I'd say we will probably be ready to submit something for inclusion into 
CVS by this time next week. Chad?

By the way, I've noticed something rather interesting with regards to 
licensing of the various libraries out there. As I see it, the Thread 
class in Common C++ is competing directly with the QThread part of Qt, 
which is licensed under the GPL (no linking exception). Qt is licensed 
under the GPL to force people who don't want to pay for Qt, but still 
want all its features, to write GPLed code.

QThread probably isn't the most impressive part of Qt, but I find it 
amusing that the GNU project is supporting a project (Common C++) that 
is developing code that provides people with a way of not GPLing their 
code, while still getting the benefits of a nice thread abstraction 
layer. I wonder what RMS has to say about this... :-)

Cheers,

Albert



From MAILER-DAEMON Fri Jan 03 09:46:05 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UT5J-0001vf-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:46:05 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UT3G-0001iD-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:43:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UT2g-0001LZ-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:43:39 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UT2N-0001AU-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:43:03 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18UT2L-0000ZH-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 16:43:01 +0200
Received: (qmail 6274 invoked from network); 3 Jan 2003 14:43:01 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 3 Jan 2003 14:43:01 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18UT2I-0001Kn-00
	for <bug-commoncpp@gnu.org>; Fri, 03 Jan 2003 16:42:58 +0200
Date: Fri, 3 Jan 2003 16:42:58 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20030103144258.GH887@dogbert.sdsl.sun.ac.za>
References: <20021231213955.GD32211@bulbasaur.rediris.es>
	<NBBBJJODBJBNJFNIDDCNOEOIDDAA.cyates@uidaho.edu>
	<20030103072949.GC887@dogbert.sdsl.sun.ac.za>
	<200301030821.56347.dyfet@ostel.com>
	<20030103143737.GG887@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030103143737.GG887@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/)
	*18UT2L-0000ZH-00*dojsN4cjfrw*
Subject: Re: Test framework; and what should be in 1.1.0
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, 03 Jan 2003 14:46:03 -0000

Hello,

On Fri, 03 Jan 2003, Albert Strasheim wrote:

> Seems you want to provide a Thread class implemented on top of Pth? 
> Isn't the pthread_* code always going to be inferior to this 
> implementation?

I am a bit mistaken here. Seems Pth uses the exact same function names, 
etc., so the existing code remains unmodified? And you can decide if you 
want to link against Pth, or just straight glibc (at least on Linux).

And then on platforms with some weird thread library, you now get 
existing code to compile by using Pth. Sweet.

Cheers,

Albert



From MAILER-DAEMON Fri Jan 03 09:59:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UTID-0000VZ-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:59:25 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UTI1-0000MC-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:59:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UTHv-0000Iw-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:59:12 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UTHv-0000HH-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 09:59:07 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18UTHs-000580-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 16:59:04 +0200
Received: (qmail 6313 invoked from network); 3 Jan 2003 14:59:04 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 3 Jan 2003 14:59:04 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18UTHp-0001Nf-00
	for <bug-commoncpp@gnu.org>; Fri, 03 Jan 2003 16:59:01 +0200
Date: Fri, 3 Jan 2003 16:59:01 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20030103145901.GI887@dogbert.sdsl.sun.ac.za>
References: <20021231213955.GD32211@bulbasaur.rediris.es>
	<NBBBJJODBJBNJFNIDDCNOEOIDDAA.cyates@uidaho.edu>
	<20030103072949.GC887@dogbert.sdsl.sun.ac.za>
	<200301030821.56347.dyfet@ostel.com>
	<20030103143737.GG887@dogbert.sdsl.sun.ac.za>
	<20030103144258.GH887@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030103144258.GH887@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/)
	*18UTHs-000580-00*yZDheGLLvVQ*
Subject: Re: Test framework; and what should be in 1.1.0
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, 03 Jan 2003 14:59:14 -0000

Hello,

On Fri, 03 Jan 2003, Albert Strasheim wrote:

> > Seems you want to provide a Thread class implemented on top of Pth? 
> > Isn't the pthread_* code always going to be inferior to this 
> > implementation?
> 
> I am a bit mistaken here. Seems Pth uses the exact same function names, 
> etc., so the existing code remains unmodified? And you can decide if you 
> want to link against Pth, or just straight glibc (at least on Linux).

You can get the exact same function names, if you use the backward 
compatible headers. The "normal" Pth functions are called pth_*.
 
> And then on platforms with some weird thread library, you now get 
> existing code to compile by using Pth. Sweet.

Generally you don't want to link against Pth on Linux? Pth doesn't 
contain any platform specific code, so it also doesn't support SMP and 
other nice bits and pieces. When the new thread code in glibc 2.3 and 
Linux 2.5/2.6 hits town, you'll probably definately want to be linking 
against that instead of against Pth. But on other platforms you probably 
have no choice.

Cheers,

Albert



From MAILER-DAEMON Fri Jan 03 10:55:49 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UUAO-0000HF-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 10:55:24 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UU8i-0006cH-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 10:53:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UU8f-0006bB-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 10:53:39 -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 18UU8e-0006aE-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 10:53:36 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h03GQXe24066;
	Fri, 3 Jan 2003 11:26:33 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
   bug-commoncpp@gnu.org
Date: Fri, 3 Jan 2003 10:55:27 -0500
User-Agent: KMail/1.4.3
References: <20021231213955.GD32211@bulbasaur.rediris.es>
	<20030103144258.GH887@dogbert.sdsl.sun.ac.za>
	<20030103145901.GI887@dogbert.sdsl.sun.ac.za>
In-Reply-To: <20030103145901.GI887@dogbert.sdsl.sun.ac.za>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301031055.27225.dyfet@ostel.com>
Subject: Re: Test framework; and what should be in 1.1.0
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, 03 Jan 2003 15:53:42 -0000

There are cases when even on GNU/Linux systems that you might want to use=
 pth=20
rather than native threading, depending on your applications actual needs=
, so=20
I thought it might be useful to do both together and select at link time=20
(hence, the idea of ccpth2 as an alternate link to ccgnu2).    But yes, p=
th=20
offers threading "emulation" on many platforms which do not have threadin=
g,=20
and so would provide a foundation for using Common C++ for common applica=
tion=20
designs that then still port to those systems.  Whether we support pth an=
d=20
native threading together on one platform is however less important than =
that=20
we at least support pth as an option (along with current posix and win32)=
 in=20
general for porting to those other platforms.

On Friday 03 January 2003 09:59, Albert Strasheim wrote:
> Hello,
>
> On Fri, 03 Jan 2003, Albert Strasheim wrote:
> > > Seems you want to provide a Thread class implemented on top of Pth?
> > > Isn't the pthread_* code always going to be inferior to this
> > > implementation?
> >
> > I am a bit mistaken here. Seems Pth uses the exact same function name=
s,
> > etc., so the existing code remains unmodified? And you can decide if =
you
> > want to link against Pth, or just straight glibc (at least on Linux).
>
> You can get the exact same function names, if you use the backward
> compatible headers. The "normal" Pth functions are called pth_*.
>
> > And then on platforms with some weird thread library, you now get
> > existing code to compile by using Pth. Sweet.
>
> Generally you don't want to link against Pth on Linux? Pth doesn't
> contain any platform specific code, so it also doesn't support SMP and
> other nice bits and pieces. When the new thread code in glibc 2.3 and
> Linux 2.5/2.6 hits town, you'll probably definately want to be linking
> against that instead of against Pth. But on other platforms you probabl=
y
> have no choice.
>
> Cheers,
>
> Albert
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Fri Jan 03 11:06:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UUJm-0006EM-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 11:05:06 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UUIc-00059y-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 11:03:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UUIa-00058a-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 11:03:53 -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 18UUIS-000504-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 11:03:44 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h03Gafe24125;
	Fri, 3 Jan 2003 11:36:41 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Date: Fri, 3 Jan 2003 11:05:35 -0500
User-Agent: KMail/1.4.3
References: <20021231213955.GD32211@bulbasaur.rediris.es>
	<200301030821.56347.dyfet@ostel.com>
	<20030103143737.GG887@dogbert.sdsl.sun.ac.za>
In-Reply-To: <20030103143737.GG887@dogbert.sdsl.sun.ac.za>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301031105.35463.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: Test framework; and what should be in 1.1.0
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, 03 Jan 2003 16:03:55 -0000

Glibc is under the LGPL, as are some other libraries in the GNU system. =20
Generally we primarly use the GPL for libraries primarly when there is no=
=20
non-free implimentation or non-free similar library already in existance=20
(readline being the most often sited example) and the possibility of help=
ing=20
further proprietary development exists if we use the LGPL as a result.  =20
There are many frameworks under various proprietary and free licenses, so=
=20
there is no benefit taken away from proprietary developers by restricting=
 GNU=20
Common C++ only for linking with free applications, just as there is no r=
eal=20
benefit derived for the GNU system as a whole by having glibc under a pur=
e=20
GPL since what would happen is that other existing libc's (BSD comes to=20
mind..) would have then been placed on GNU systems by others instead. =20

On Friday 03 January 2003 09:37, Albert Strasheim wrote:
> Hello,
>
> On Fri, 03 Jan 2003, David Sugar wrote:
> > At this point, it seems destined for the 1.1 release, and no date has
> > been set yet for when that will be made available.  So, no, there is =
no
> > immediate rush
> >
> > :).
>
> Still, I think Chad and I will be able to prepare a nice patch in the
> next week or two which should go into CVS; then other people can start
> writing tests too.
>
> > It might be worth asserting what things remain to be done for a 1.1
> > release to occur, and for that I would like to suggest the following:
> >
> > * from the threading perspective, support for pth based ng Linux
> > threading, and alternate compile option that can compile for systems =
that
> > use the pth library.
>
> Seems Pth is licensed under the LGPL. Cool.
>
> As I understand, Pth provides a layer on top of POSIX-conformant thread
> implementations on Unix platforms. Is this correct?
>
> Seems you want to provide a Thread class implemented on top of Pth?
> Isn't the pthread_* code always going to be inferior to this
> implementation?
>
> > * completion (by me) of ccssl...
> >
> > * integration of new counter code
>
> I will make a final patch for this once we've merged the test framework
> code.
>
> > * addition of IP6Address classes and ip6 socket support.  (this may
> > actually be fairly easy to add...)
> >
> > * new testing framework
>
> I'd say we will probably be ready to submit something for inclusion int=
o
> CVS by this time next week. Chad?
>
> By the way, I've noticed something rather interesting with regards to
> licensing of the various libraries out there. As I see it, the Thread
> class in Common C++ is competing directly with the QThread part of Qt,
> which is licensed under the GPL (no linking exception). Qt is licensed
> under the GPL to force people who don't want to pay for Qt, but still
> want all its features, to write GPLed code.
>
> QThread probably isn't the most impressive part of Qt, but I find it
> amusing that the GNU project is supporting a project (Common C++) that
> is developing code that provides people with a way of not GPLing their
> code, while still getting the benefits of a nice thread abstraction
> layer. I wonder what RMS has to say about this... :-)
>
> Cheers,
>
> Albert
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Fri Jan 03 11:22:33 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UUXz-0006Tj-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 11:19:47 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UUX5-0005hG-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 11:18:51 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UUUj-0004zU-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 11:16:26 -0500
Received: from acate.com.br ([200.215.17.89] helo=srv001.brasmap)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UUQr-0003nT-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 11:12:26 -0500
Received: from brasmap.com.br (localhost.localdomain [127.0.0.1])
	by srv001.brasmap (Postfix) with SMTP id 6831A107407
	for <bug-commoncpp@gnu.org>; Fri,  3 Jan 2003 14:11:06 -0200 (BRST)
Date: Fri, 3 Jan 2003 14:11:06 -0200
From: Marcelo Dalmas <mad@brasmap.com.br>
To: ccxx <bug-commoncpp@gnu.org>
Message-Id: <20030103141106.1c9909a6.mad@brasmap.com.br>
Organization: BRASMAP Sistemas
X-Mailer: Sylpheed version 0.8.5 (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="Multipart_Fri__3_Jan_2003_14:11:06_-0200_081ede30"
Subject: Date::fromJulian 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: Fri, 03 Jan 2003 16:18:52 -0000

This is a multi-part message in MIME format.

--Multipart_Fri__3_Jan_2003_14:11:06_-0200_081ede30
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit


Hi,

I am sending a patch for date.cpp with Henry F. Fliegel and Thomas C. Van
Flandern algorithm. It's same from Commoncpp2 0.99.7 with a correction:

year = 100 * (n - 49) + i + 1;

The last "1" isn't a 1, it is a "l", :)

In current release, Date isn't working. Date return 2002-01-03 for today year.

by

-- 
Marcelo Dalmas
BRASMAP Sistemas
www.brasmap.com.br
Fone/Fax: (48) 333-2218 ramal 2114

Linux user #114373 http://counter.li.org/


--Multipart_Fri__3_Jan_2003_14:11:06_-0200_081ede30
Content-Type: application/octet-stream;
 name="date.patch"
Content-Disposition: attachment;
 filename="date.patch"
Content-Transfer-Encoding: base64

SW5kZXg6IHNyYy9kYXRlLmNwcAo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJDUyBmaWxlOiAvY3Zzcm9vdC9jb21tb25j
cHAvY29tbW9uY3BwMi9zcmMvZGF0ZS5jcHAsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEuNC4yLjQK
ZGlmZiAtdSAtcjEuNC4yLjQgZGF0ZS5jcHAKLS0tIHNyYy9kYXRlLmNwcAk1IE5vdiAyMDAyIDA5
OjE1OjIxIC0wMDAwCTEuNC4yLjQKKysrIHNyYy9kYXRlLmNwcAkzIEphbiAyMDAzIDE0OjIzOjMz
IC0wMDAwCkBAIC00NCw2ICs0NCw3IEBACiAjaW5jbHVkZSA8Y3N0ZGxpYj4KICNpbmNsdWRlIDxj
c3RkaW8+CiAjaW5jbHVkZSA8Y3RpbWU+CisjaW5jbHVkZSA8Y21hdGg+CiAKICNpZmRlZglXSU4z
MgogI2luY2x1ZGUgInRpbWUuaCIKQEAgLTI4MywyNyArMjg0LDI5IEBACiAKIHZvaWQgRGF0ZTo6
ZnJvbUp1bGlhbihjaGFyICpidWZmZXIpCiB7CisvLyBUaGUgZm9sbG93aW5nIGNvbnZlcnNpb24g
YWxnb3JpdGhtIGlzIGR1ZSB0byAKKy8vIEhlbnJ5IEYuIEZsaWVnZWwgYW5kIFRob21hcyBDLiBW
YW4gRmxhbmRlcm46CisKIAlaTnVtYmVyIG55ZWFyKGJ1ZmZlciwgNCk7CiAJWk51bWJlciBubW9u
dGgoYnVmZmVyICsgNCwgMik7CiAJWk51bWJlciBuZGF5KGJ1ZmZlciArIDYsIDIpOwogCi0JbG9u
ZyB0MSwgdDIsIG1vbnRoLCB5ZWFyOwotCi0JdDEgPSBqdWxpYW4gKyAzMjA3NTsKLQl5ZWFyID0g
NCAqIHQxIC8gMTQ2MTsKLQl0MSA9IHQxIC0gMTQ2MSAqIHllYXIgLyA0OwotCXQyID0gMyAqICh5
ZWFyICsgMTAwKSAvIDQwMDsKLQl0MSA9IHQxICsgdDI7Ci0JbW9udGggPSAxMiAqIHQxIC8gMzY3
OwotCXQyID0gbW9udGggLyAxMTsKLQluZGF5ID0gdDEgLSAzNjcgKiBtb250aCAvIDEyOwotCW5t
b250aCA9IG1vbnRoICsgMiAtIDEyICogdDI7Ci0JeWVhciA9IHllYXIgLSA0ODAwOworCWRvdWJs
ZSBpLCBqLCBrLCBsLCBuOwogCi0JaWYoeWVhciA8PSAwKQotCQktLXllYXI7Ci0KLQlueWVhciA9
IHllYXI7CisJbCA9IGp1bGlhbiArIDY4NTY5LjA7CisJbiA9IGludCggNCAqIGwgLyAxNDYwOTcu
MCk7CisJbCA9IGwgLSBpbnQoICgxNDYwOTcuMCAqIG4gKyAzKS8gNCApOworCWkgPSBpbnQoIDQw
MDAuMCAqIChsKzEpLzE0NjEwMDEuMCk7CisJbCA9IGwgLSBpbnQoMTQ2MS4wKmkvNC4wKSArIDMx
LjA7CisJaiA9IGludCggODAgKiBsLzI0NDcuMCk7CisJayA9IGwgLSBpbnQoIDI0NDcuMCAqIGog
LyA4MC4wKTsKKwlsID0gaW50KGovMTEpOworCWogPSBqKzItMTIqbDsKKwlpID0gMTAwKihuIC0g
NDkpICsgaSArIGw7CisJbnllYXIgPSBpbnQodHJ1bmMoaSkpOworCW5tb250aCA9IGludCh0cnVu
YyhqKSk7CisJbmRheSA9IGludCh0cnVuYyhrKSk7CisJCiAJYnVmZmVyWzhdID0gJ1wwJzsKIH0K
IAo=

--Multipart_Fri__3_Jan_2003_14:11:06_-0200_081ede30--



From MAILER-DAEMON Fri Jan 03 13:47:31 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UWqw-0007z7-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 13:47:30 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UWqu-0007xa-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 13:47:28 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UWpp-0007Y7-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 13:46:24 -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 18UWpd-0007Be-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 13:46:09 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8500IPHISW3P@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Fri, 03 Jan 2003 10:46:08 -0800 (PST)
Date: Fri, 03 Jan 2003 10:46:08 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20030103072949.GC887@dogbert.sdsl.sun.ac.za>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-id: <NBBBJJODBJBNJFNIDDCNOEONDDAA.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
cc: bug-commoncpp@gnu.org
Subject: RE: Test framework
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, 03 Jan 2003 18:47:28 -0000

> I've looked over Chad's stuff. Sweet.
>
> I'll have to look my own code over and make sure it plays nice with the
> test factory stuff. I'll do this today.
>
> One thing that needs to get done is to improve the test "driver"
> program. I think the custom TestListener I coded is a step in the right
> direction (gone are the .'s in strange places in the test output).
> Furthermore, we need to add support for a few command line options --
> stuff to run specific tests, skip specific tests, and some other bits
> like outputting "compiler output" for MSVC so that the IDE can send you
> directly to the line where the test failed.

sounds good, go get em.  my driver was just the basics from a cppunit
example, but the CompilerOutputter was a pretty cool "nicety". if you do
clone the cppunit CompilerOutputter class, have it indent the lines after
the compiler line error.  it would make it more readable since a failed test
generates multiple lines 4+ if assert messages, actual, and expected values
are used.

> This is probably a good test for CommandOption and friends. I'll take
> this on if no-one else is particularly interested.

it's all yours (I'm available for testing if you need it)

> Also, we need to decide on a naming convention for the test files. I
> suggest the following:
>
> 1. Move demo/* and test/* to a new "examples" directory.
>
> Reasons: old tests are probably deprecated, but could still serve as
> examples (or be removed once we've integrated them); probably don't want
> _examples_ in the "demo" directory; when I think "demo", I think a big
> monolithic piece of code; CppUnit project put their examples in the
> "examples" directory.

sounds like a good move.

> As an aside, the CppUnit source tree is, for me, an example of good
> organisation. I think the Common C++ project should look to emulate
> their source tree layout as far as possible, although we are similar in
> many respects already.
>
> 2. Put the tests in tests/test_<ClassName>.{cpp,h,tcc}.
>
> Reasons: the name is reasonably unambigious, easily grepable, etc.
>
> In the case where you can use a class (templated or not) to test derived
> classes, we could probably add tests for the derived classes to
> test_<BaseClass>.{cpp,h,tcc}, like I did with the UberCounter tests.

I would have to agree the cppunit tree was pretty organized.  I have no
opinion on the naming for the test files, just as long as the word test is
in there somewhere, and that they are consistent.  I've used <Class>Test for
what I've done, but will gladly change to test_<class> if that is the
direction we want to go. cppunit has a contrib directory, is that
conceptually the same thing as common c++'s patches directory?

> A good guideline would probably be: one library header, one set of test
> files, but this breaks down for thread.h and others, since it has about
> 10 classes in there (which should be split up, IMHO).

I think some of the headers have become bogged down, and should be broken
down.  I'm of the opinion that for most tests a single class will be
exercised, and so should have it's own file where it makes sense (a unit).
in the cases where your testing the way multiple classes interface that
standard may have to be brushed aside as you'd be testing a composite.  on a
side note, I am willing to re-org the persist.h, engine.cpp, persist.cpp,
digest.h digest.cpp md5.cpp, and sha.cpp files to better break them down
closer to the 1 class equals 1 each of .h/.cpp/.tcc (.tcc is for templates?)
files as appropriate.  the timing would just need to be decided on so I
don't cause trouble for a merge back into cvs (since the contents of the
files would be exploded over multiple other files).  I'm sure other areas
could also benefit also, but these are ones I've become the most familiar
with.

Comments?

,Chad




From MAILER-DAEMON Fri Jan 03 14:03:21 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UX6G-00071T-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 14:03:20 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UX6E-000713-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 14:03:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UX6B-0006zS-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 14:03:17 -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 18UX6A-0006yP-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 14:03:14 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8500IF2JLE3P@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Fri, 03 Jan 2003 11:03:14 -0800 (PST)
Date: Fri, 03 Jan 2003 11:03:14 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20030103143737.GG887@dogbert.sdsl.sun.ac.za>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-id: <NBBBJJODBJBNJFNIDDCNKEOODDAA.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
cc: bug-commoncpp@gnu.org
Subject: RE: Test framework; and what should be in 1.1.0
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, 03 Jan 2003 19:03:18 -0000

> > * new testing framework
>
> I'd say we will probably be ready to submit something for inclusion into
> CVS by this time next week. Chad?

I think so.  things related to digest and persistence should come to closure
pretty soon.  I'm going to see if I can't use some "magic" that albert and I
discussed to give the digests a simple extensible base that can be used to
run all current (and future with very small additions) digest sub-classes
through a common test suite.  hopefully the technique will be useful (if it
works out) in other class hieararchies that enforce a basic common
interface.

also, I just remembered something.  albert, you may want to take a look at
the Orthodox.h file in cppunit-1.8.0/include/cppunit/extensions.  Last night
while lie in bed sleepless (brain in overdrive), I remembered stumbling onto
it while perusing the doxygen docs.  I think I might find some useful bits
applicable to the above "magic."  it runs a class through the standard C++
opperators.  from the header comments:

 * Orthodox performs a simple set of tests on an arbitary
 * class to make sure that it supports at least the
 * following operations:
 *
 *      default construction    - constructor
 *      equality/inequality     - operator== && operator!=
 *      assignment              - operator=
 *      negation                - operator!
 *      safe passage            - copy construction
 *
 * If operations for each of these are not declared
 * the template will not instantiate.  If it does
 * instantiate, tests are performed to make sure
 * that the operations have correct semantics.

Check out the doxygen docs for more info on it's usage.  I'll be
investigating as I play with the digest tests in the next few days.

,chad




From MAILER-DAEMON Fri Jan 03 14:11:27 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UXE7-0005uc-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 14:11:27 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UXE5-0005sn-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 14:11:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UXE3-0005sU-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 14:11:24 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UXE1-0005qj-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 14:11:22 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18UXDw-0001e3-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 21:11:16 +0200
Received: (qmail 6830 invoked from network); 3 Jan 2003 19:11:16 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 3 Jan 2003 19:11:16 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18UXDt-0001c1-00; Fri, 03 Jan 2003 21:11:13 +0200
Date: Fri, 3 Jan 2003 21:11:13 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030103191113.GM887@dogbert.sdsl.sun.ac.za>
References: <20030103143737.GG887@dogbert.sdsl.sun.ac.za>
	<NBBBJJODBJBNJFNIDDCNKEOODDAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNKEOODDAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18UXDw-0001e3-00*Yra8me04CvM*
cc: bug-commoncpp@gnu.org
Subject: Re: Test framework; and what should be in 1.1.0
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, 03 Jan 2003 19:11:25 -0000

Hello,

On Fri, 03 Jan 2003, Chad Yates wrote:

> > > * new testing framework
> >
> > I'd say we will probably be ready to submit something for inclusion into
> > CVS by this time next week. Chad?
> 
> I think so.  things related to digest and persistence should come to closure
> pretty soon.  I'm going to see if I can't use some "magic" that albert and I
> discussed to give the digests a simple extensible base that can be used to
> run all current (and future with very small additions) digest sub-classes
> through a common test suite.  hopefully the technique will be useful (if it
> works out) in other class hieararchies that enforce a basic common
> interface.
> 
> also, I just remembered something.  albert, you may want to take a look at
> the Orthodox.h file in cppunit-1.8.0/include/cppunit/extensions.  Last night
> while lie in bed sleepless (brain in overdrive), I remembered stumbling onto
> it while perusing the doxygen docs.  I think I might find some useful bits
> applicable to the above "magic."  it runs a class through the standard C++
> opperators.  from the header comments:
> 
>  * Orthodox performs a simple set of tests on an arbitary
>  * class to make sure that it supports at least the
>  * following operations:
>  *
>  *      default construction    - constructor
>  *      equality/inequality     - operator== && operator!=
>  *      assignment              - operator=
>  *      negation                - operator!

I am quite surprised by this. I was looking over some of the Common C++ 
documentation, and I couldn't figure out why everyone was including 
operator! methods. To me negation doesn't mean much, except in specific 
cases, and even then negating the return value of a "get" method would 
probably be clearer in meaning. Or should negation generally return true 
if something is "wrong" with the object?

Does someone know of an article or a reference describing what operator! 
is generally supposed to do?

>  *      safe passage            - copy construction

The C++ portability guide has some insightful comments on this subject: 
declare a private copy constructor and operator=(T&) if you don't intend 
for your class to be copy constructed. Has this been adhered to in the 
Common C++ classes? This test will help us find this kind of stuff.

>  *
>  * If operations for each of these are not declared
>  * the template will not instantiate.  If it does
>  * instantiate, tests are performed to make sure
>  * that the operations have correct semantics.
> 
> Check out the doxygen docs for more info on it's usage.  I'll be
> investigating as I play with the digest tests in the next few days.

Sweet.

Cheers,

Albert



From MAILER-DAEMON Fri Jan 03 15:14:59 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UYDb-0000M3-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:14:59 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UYDZ-0000L9-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:14:57 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UYDW-0000Go-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:14:56 -0500
Received: from malkav.cac.washington.edu ([140.142.107.26])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UYDW-0000Ds-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:14:54 -0500
Received: from nosferatu.kriln.com
	(evrtwa1-ar1-4-47-235-208.evrtwa1.dsl-verizon.net [4.47.235.208])
	by malkav.cac.washington.edu (Postfix) with ESMTP id BBBF0CF305
	for <bug-commoncpp@gnu.org>; Fri,  3 Jan 2003 05:08:20 -0800 (PST)
Received: by nosferatu.kriln.com (Postfix, from userid 1000)
	id E580058F5; Fri,  3 Jan 2003 20:18:32 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by nosferatu.kriln.com (Postfix) with ESMTP id E39975507
	for <bug-commoncpp@gnu.org>; Fri,  3 Jan 2003 20:18:32 +0000 (GMT)
Date: Fri, 3 Jan 2003 20:18:32 +0000 (GMT)
From: Jeremy Noetzelman <jjn@kriln.com>
To: bug-commoncpp@gnu.org
In-Reply-To: <20030102162845.K180-100000@nosferatu.kriln.com>
Message-ID: <20030103201811.D180-100000@nosferatu.kriln.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: Non Threaded use of TCPSocket with select/poll?
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, 03 Jan 2003 20:14:57 -0000

Shall I take the lack of response as a "No, you can't, roll it yourself."?

:)

J

On Thu, 2 Jan 2003, Jeremy Noetzelman wrote:

> Is there an easy (ie preexisting) way of using the TCPSocket/TCPStream
> classes with select or poll without using the threads interface?  It seems
> to me at a glance that there's not, and if I want to have a 'real' server
> which handles lots of sockets I have to use Threads (SocketService, etc)
>
> Can someone enlighten me?
>
>




From MAILER-DAEMON Fri Jan 03 15:18:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UYGu-0002gD-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:18:24 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UYGs-0002fz-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:18:22 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UYGq-0002es-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:18:21 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UYGN-0002RR-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:17:52 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18UYGK-000334-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 22:17:48 +0200
Received: (qmail 6968 invoked from network); 3 Jan 2003 20:17:47 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 3 Jan 2003 20:17:47 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18UYGG-0001eM-00; Fri, 03 Jan 2003 22:17:44 +0200
Date: Fri, 3 Jan 2003 22:17:44 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: Jeremy Noetzelman <jjn@kriln.com>
Message-ID: <20030103201744.GN887@dogbert.sdsl.sun.ac.za>
References: <20030102162845.K180-100000@nosferatu.kriln.com>
	<20030103201811.D180-100000@nosferatu.kriln.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030103201811.D180-100000@nosferatu.kriln.com>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18UYGK-000334-00*Ypd7J1cDcQU*
cc: bug-commoncpp@gnu.org
Subject: Re: Non Threaded use of TCPSocket with select/poll?
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, 03 Jan 2003 20:18:23 -0000

Hello,

>From the Common C++ documentation for tcpstream (not TCPStream):

A more natural C++ "tcpstream" class for use by non-threaded 
applications. C++ "fstream" style tcpstream class. 

I don't know if this is what you want?

Cheers,

Albert



From MAILER-DAEMON Fri Jan 03 15:23:46 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UYLp-0007y7-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:23:29 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UYLl-0007nL-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:23:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UYLe-0007Tm-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:23:20 -0500
Received: from malkav.cac.washington.edu ([140.142.107.26])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UYKu-0006dU-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 15:22:32 -0500
Received: from nosferatu.kriln.com
	(evrtwa1-ar1-4-47-235-208.evrtwa1.dsl-verizon.net [4.47.235.208])
	by malkav.cac.washington.edu (Postfix) with ESMTP
	id 7B279CF305; Fri,  3 Jan 2003 05:16:00 -0800 (PST)
Received: by nosferatu.kriln.com (Postfix, from userid 1000)
	id 6625A58F5; Fri,  3 Jan 2003 20:26:11 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by nosferatu.kriln.com (Postfix) with ESMTP
	id 613DB5507; Fri,  3 Jan 2003 20:26:11 +0000 (GMT)
Date: Fri, 3 Jan 2003 20:26:11 +0000 (GMT)
From: Jeremy Noetzelman <jjn@kriln.com>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
In-Reply-To: <20030103201744.GN887@dogbert.sdsl.sun.ac.za>
Message-ID: <20030103202530.S180-100000@nosferatu.kriln.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bug-commoncpp@gnu.org
Subject: Re: Non Threaded use of TCPSocket with select/poll?
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, 03 Jan 2003 20:23:27 -0000

I'm more concerned about having a proper select polling loop for the
server socket ... I'm less concerned about the client connection sockets.

On Fri, 3 Jan 2003, Albert Strasheim wrote:

> Hello,
>
> >From the Common C++ documentation for tcpstream (not TCPStream):
>
> A more natural C++ "tcpstream" class for use by non-threaded
> applications. C++ "fstream" style tcpstream class.
>
> I don't know if this is what you want?
>
> Cheers,
>
> Albert
>




From MAILER-DAEMON Fri Jan 03 16:46:51 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UZeU-0003VK-00
	for mharc-bug-commoncpp@gnu.org; Fri, 03 Jan 2003 16:46:50 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UZeS-0003To-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 16:46:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UZeQ-0003Sq-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 16:46:47 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UZdD-00039N-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 16:45:32 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18UZd8-00016M-00
	for bug-commoncpp@gnu.org; Fri, 03 Jan 2003 23:45:26 +0200
Received: (qmail 7137 invoked from network); 3 Jan 2003 21:45:26 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 3 Jan 2003 21:45:26 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18UZd5-0004Hq-00
	for <bug-commoncpp@gnu.org>; Fri, 03 Jan 2003 23:45:23 +0200
Date: Fri, 3 Jan 2003 23:45:23 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: bug-commoncpp@gnu.org
Message-ID: <20030103214523.GP887@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/)
	*18UZd8-00016M-00*VO8bVVisJrk*
Subject: doxygen @short directive in comments
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, 03 Jan 2003 21:46:49 -0000

Hello,

All the classes in Common C++ are documented as follows (MutexCounter 
in thread.h used as example):

/**
 * The Mutex Counter is a counter variable which can safely be incremented
 * or decremented by multiple threads.  A Mutex is used to protect access
 * to the counter variable (an integer).  An initial value can be specified 
 * for the counter, and it can be manipulated with the ++ and -- operators.
 * 
 * @author David Sugar <dyfet@ostel.com>
 * @short Thread protected integer counter.
 */
class CCXX_CLASS_EXPORT MutexCounter : public Mutex
{
...
};

This is wrong. The problem is the position of the @short directive. 
@short should be at the top of the class description, not the bottom, 
e.g.:

/**
 * @short Empty class.
 *
 * Class A is an empty class. Be happy.
 *
 * @author Albert Strasheim
 */

This generates the proper HTML in doxygen -- you'll see that all the 
current class descriptions currently don't read too well, since the 
first sentence of the description, and the @short sentence are being 
used for the description of the class that is placed at the top of the 
generated page.

Cheers,

Albert



From MAILER-DAEMON Sat Jan 04 08:17:43 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UoBL-0004di-00
	for mharc-bug-commoncpp@gnu.org; Sat, 04 Jan 2003 08:17:43 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UmYq-0007G7-00
	for bug-commoncpp@gnu.org; Sat, 04 Jan 2003 06:33:52 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UmYW-0006iQ-00
	for bug-commoncpp@gnu.org; Sat, 04 Jan 2003 06:33:33 -0500
Received: from ns.suse.de ([213.95.15.193] helo=Cantor.suse.de)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UmYV-0006fU-00
	for bug-commoncpp@gnu.org; Sat, 04 Jan 2003 06:33:31 -0500
Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136])
	by Cantor.suse.de (Postfix) with ESMTP id 94BF11444D
	for <bug-commoncpp@gnu.org>; Sat,  4 Jan 2003 12:33:30 +0100 (MET)
From: Gernot Hillier <ghillie@suse.de>
To: <bug-commoncpp@gnu.org>
Date: Sat, 4 Jan 2003 12:33:27 +0100
User-Agent: KMail/1.4.3
Organization: SuSE Linux AG
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="------------Boundary-00=_RFT6YVKQOROXMZXCUAHG"
Message-Id: <200301041233.27796.ghillie@suse.de>
X-Mailman-Approved-At: Sat, 04 Jan 2003 08:17:42 -0500
Subject: [BUG] [PATCH] Buffer Overflow in Keydata::loadPrefix()
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, 04 Jan 2003 11:33:56 -0000


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

Hi!

I stumbled over a very dangerous code part in CommonC++ in the KeyData=20
implementation:

void Keydata::loadPrefix(const char *pre, const char *keypath, const char=
=20
*environment)
{
[...]
        if(*keypath =3D=3D '~')
        {
                prefix =3D getenv("HOME");
                strcpy(path, prefix);=20
                strcat(path, "/.");
                ++keypath;
        }
[...]

This is a classical buffer overflow (use a environment variable, rely on =
its=20
length and copy it to an internal buffer).

I tried to fix it for the time being - but I don't actually know the clas=
s as=20
I don't use it. Please triple-check my fixes - they're untested and I don=
't=20
have read the complete code of keydata.cpp!=20

So please see my patch just as a suggestion. I'll attach it...

--=20
Bye,

Gernot

--------------Boundary-00=_RFT6YVKQOROXMZXCUAHG
Content-Type: text/x-diff;
  charset="us-ascii";
  name="commonc++-bo.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="commonc++-bo.patch"

diff -uNr commoncpp2-orig/src/keydata.cpp commoncpp2/src/keydata.cpp
--- commoncpp2-orig/src/keydata.cpp	2003-01-04 12:30:26.000000000 +0100
+++ commoncpp2/src/keydata.cpp	2003-01-04 12:27:56.000000000 +0100
@@ -283,7 +283,7 @@
 	if(*keypath == '~')
 	{
 		prefix = getenv("HOME");
-		strcpy(path, prefix);
+		strncpy(path, prefix, 507); // 512 - "/." - "rc" - '\0'
 		strcat(path, "/.");
 		++keypath;
 	}
@@ -293,7 +293,7 @@
 		prefix = getenv(environment);
 		if(!prefix)
 			prefix = ETC_PREFIX;
-		strcpy(path, prefix);
+		strncpy(path, prefix, 506); // 512 - ".conf" - '\0'
 		prefix = NULL;
 	}
 

--------------Boundary-00=_RFT6YVKQOROXMZXCUAHG--




From MAILER-DAEMON Tue Jan 07 14:58:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Vwtv-0005sT-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:48:27 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VZi2-00044D-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:02:38 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VZXZ-0002WC-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 10:51:50 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VZXE-0002Tc-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 10:51:28 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18VZXk-0002IW-00; Mon, 06 Jan 2003 16:52:00 +0100
Date: Mon, 6 Jan 2003 16:51:59 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Marcel Stadtmann <cityman@junisphere.net>
Message-ID: <20030106155159.GC4098@bulbasaur.rediris.es>
Mail-Followup-To: Marcel Stadtmann <cityman@junisphere.net>,
	Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <1AD05C34099CE048B5881A7852C61DE001D10975@EXBENS01GB1.netstore.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1AD05C34099CE048B5881A7852C61DE001D10975@EXBENS01GB1.netstore.local>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Bug in thread code
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, 06 Jan 2003 16:04:25 -0000


	A bug in the tcpthread demo has been recently fixed. Does the
code you are testing start threads with tcp->start() or does it call
tcp->detach()?  As long as it uses detach(), it should free the thread
system resources. If it is not the case, we should look at this issue
again.

On Thu, Jan 02, 2003 at 12:25:06PM -0000, Marcel Stadtmann wrote:
> Hello,
> 
> -----Ursprüngliche Nachricht-----
> Von: Albert Strasheim [mailto:fullung-ccpp@dogbert.sdsl.sun.ac.za]
> Gesendet: Donnerstag, 2. Januar 2003 12:39
> An: Marcel Stadtmann
> Cc: bug-commoncpp@gnu.org
> Betreff: Re: Bug in thread code
> 
> 
> Hello,
> 
> On Thu, 02 Jan 2003, Marcel Stadtmann wrote:
> 
> > Thanks for your help. But i think this is not the real problem. 
> > Maybe my discribtion was not correct. On the sample, the thread will start,
> > do his job, and then terminate. For me means this, the resource of 
> > this thread should be free after termination. Is this not correct ?? 
> > Are there still resources allocated ??
> 
> It seems as if final() in myTCPSession is being called, so the "delete 
> this" probably happens. This starts destructing the thread object, which 
> hopefully calls a terminate() somewhere down the line, which stops the 
> thread and cleans up the other bits and pieces.
> 
> The obvious scenario related to threads where you could possibly run 
> out of resources is when you start a bunch of joinable threads, but 
> never join on them again, meaning their resources stick around until the 
> parent process terminates.
> 
> I ran your test, and on my system (using commoncpp2 from CVS) I had 
> completed about 20000 connections before tcpthread segfaulted.
> 
> While you wait for someone with a proper clue (i.e. not me :-)) to help 
> you, you might want to try commoncpp2 from CVS and see if your problems 
> persist. You can find instructions for doing a checkout here:
> 
> http://savannah.gnu.org/cvs/?group=commoncpp
> 
> I'll poke around the threads code some more today. Good luck!
> 
> Cheers,
> 
> Albert
> 
> 
> Thanks Albert for the fast answer. 
> I have testet this allready with the newest Code from CVS. Still the same problem.
> But your explanation with the resources seems as its true.
> 
> It's is maybe a problem with the thread cleanup code part in commoncpp.
> I try to make some additional test's, to give more input.
> 
> cheers
> Marcel
> 
> 
> 
> 
>  
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Tue Jan 07 16:44:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18W1Sv-00088f-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 16:40:53 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VlpK-0006Rc-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 23:58:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VlpI-0006RO-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 23:58:57 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VlpI-0006ON-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 23:58:56 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18Vlp9-000151-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 06:58:47 +0200
Received: (qmail 19079 invoked from network); 7 Jan 2003 04:58:47 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 7 Jan 2003 04:58:47 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18W7hm-00007h-00; Wed, 08 Jan 2003 06:20:38 +0200
Date: Wed, 8 Jan 2003 06:20:38 +0200
From: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-ID: <20030108042038.GA434@dogbert.sdsl.sun.ac.za>
References: <20030101210824.GH415@dogbert.sdsl.sun.ac.za>
	<20030106160857.GD4098@bulbasaur.rediris.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030106160857.GD4098@bulbasaur.rediris.es>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18Vlp9-000151-00*smqLAWC4G/A*
X-Mailman-Approved-At: Tue, 07 Jan 2003 16:40:40 -0500
cc: bug-commoncpp@gnu.org
Subject: Re: Signalling a condition
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, 07 Jan 2003 04:58:59 -0000

Hello,

Sorry, I missed the paragraph in the doxygen docs discussing this. Maybe 
you want to add \warning? :-)

Cheers,

Albert

On Mon, 06 Jan 2003, Federico Montesino Pouzols wrote:

> 	Hi, I guess you are considering that Conditional handles the
> mutex as well as the condition variable. However, Conditional is meant
> to allow the user to independently perform operantions on both
> things. You may find interesting a mail in the arhives from November,
> "[ Patch #623 ] ost::Conditional is broken with posix threads". There
> is also a discussion on this on the savannah patch manager (you may
> need to browse the 'closed' patches).



From MAILER-DAEMON Tue Jan 07 16:47:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18W1Sv-00088g-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 16:40:53 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VqG5-0004vG-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 04:42:53 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VqG1-0004mf-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 04:42:53 -0500
Received: from exavns02gb1.netstore.net ([194.79.241.57])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18VqG1-0004mV-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 04:42:49 -0500
Received: from 194.79.241.49 by exavns02gb1.netstore.net (InterScan E-Mail
	VirusWall NT); Tue, 07 Jan 2003 09:42:27 -0000
Received: from EXBENS01GB1.netstore.local ([194.79.241.50]) by
	exfens02gb1.netstore.local with Microsoft SMTPSVC(5.0.2195.5329);
	Tue, 7 Jan 2003 09:42:27 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6334.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 7 Jan 2003 09:42:26 -0000
Message-ID: <1AD05C34099CE048B5881A7852C61DE001D10979@EXBENS01GB1.netstore.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bug in thread code
Thread-Index: AcK1m3ih0bEo7MSUTVGIGyPTF4Oi1AAk/QdQ
From: "Marcel Stadtmann" <cityman@junisphere.net>
To: "Federico Montesino Pouzols" <fedemp@altern.org>
X-OriginalArrivalTime: 07 Jan 2003 09:42:27.0144 (UTC)
	FILETIME=[16C4BC80:01C2B631]
X-Mailman-Approved-At: Tue, 07 Jan 2003 16:40:40 -0500
cc: bug-commoncpp@gnu.org
Subject: AW: 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, 07 Jan 2003 09:42:54 -0000

Hi Federico,

In the sample code the thread is started with tcp->start().
I have tested now both the sample code, and my code with tcp->detach(). =
It's great !!!!
The code is working. It doesn't matter for my if a start with ->start or =
->detach !
The main point is that the code is running.
Thank's very much Federico, and all other peoples for the professional =
and fast help !

All the best for the new Year
Marcel


-----Urspr=FCngliche Nachricht-----
Von: Federico Montesino Pouzols [mailto:fedemp@altern.org]
Gesendet: Montag, 6. Januar 2003 16:52
An: Marcel Stadtmann
Cc: Albert Strasheim; bug-commoncpp@gnu.org
Betreff: Re: Bug in thread code



	A bug in the tcpthread demo has been recently fixed. Does the
code you are testing start threads with tcp->start() or does it call
tcp->detach()?  As long as it uses detach(), it should free the thread
system resources. If it is not the case, we should look at this issue
again.

On Thu, Jan 02, 2003 at 12:25:06PM -0000, Marcel Stadtmann wrote:
> Hello,
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: Albert Strasheim [mailto:fullung-ccpp@dogbert.sdsl.sun.ac.za]
> Gesendet: Donnerstag, 2. Januar 2003 12:39
> An: Marcel Stadtmann
> Cc: bug-commoncpp@gnu.org
> Betreff: Re: Bug in thread code
>=20
>=20
> Hello,
>=20
> On Thu, 02 Jan 2003, Marcel Stadtmann wrote:
>=20
> > Thanks for your help. But i think this is not the real problem.=20
> > Maybe my discribtion was not correct. On the sample, the thread will =
start,
> > do his job, and then terminate. For me means this, the resource of=20
> > this thread should be free after termination. Is this not correct ?? =

> > Are there still resources allocated ??
>=20
> It seems as if final() in myTCPSession is being called, so the "delete =

> this" probably happens. This starts destructing the thread object, =
which=20
> hopefully calls a terminate() somewhere down the line, which stops the =

> thread and cleans up the other bits and pieces.
>=20
> The obvious scenario related to threads where you could possibly run=20
> out of resources is when you start a bunch of joinable threads, but=20
> never join on them again, meaning their resources stick around until =
the=20
> parent process terminates.
>=20
> I ran your test, and on my system (using commoncpp2 from CVS) I had=20
> completed about 20000 connections before tcpthread segfaulted.
>=20
> While you wait for someone with a proper clue (i.e. not me :-)) to =
help=20
> you, you might want to try commoncpp2 from CVS and see if your =
problems=20
> persist. You can find instructions for doing a checkout here:
>=20
> http://savannah.gnu.org/cvs/?group=3Dcommoncpp
>=20
> I'll poke around the threads code some more today. Good luck!
>=20
> Cheers,
>=20
> Albert
>=20
>=20
> Thanks Albert for the fast answer.=20
> I have testet this allready with the newest Code from CVS. Still the =
same problem.
> But your explanation with the resources seems as its true.
>=20
> It's is maybe a problem with the thread cleanup code part in =
commoncpp.
> I try to make some additional test's, to give more input.
>=20
> cheers
> Marcel
>=20
>=20
>=20
>=20
> =20
>=20
>=20
>=20
>=20
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Tue Jan 07 16:59:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18W1Su-00088c-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 16:40:52 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VYK2-0001L2-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 09:33:46 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VYJx-0001IT-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 09:33:43 -0500
Received: from mx1.magmacom.com ([206.191.0.217])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VYBp-0000B1-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 09:25:17 -0500
Received: from mail4.magma.ca (mail4.magma.ca [206.191.0.222])
	by mx1.magmacom.com (Magma's Mail Server) with ESMTP id h06EPFRw005012
	for <bug-commoncpp@gnu.org>; Mon, 6 Jan 2003 09:25:15 -0500 (EST)
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail4.magma.ca (Magma's Mail Server) with ESMTP id h06EPFnH002384
	for <bug-commoncpp@gnu.org>; Mon, 6 Jan 2003 09:25:15 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: <bug-commoncpp@gnu.org>
Date: Mon, 6 Jan 2003 09:25:14 -0500
Message-ID: <!~!AAAAAEHQcWKgHmRJlScZOL5O6CYkTiEA@gridiron-networks.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0000_01C2B565.857273B0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MS-TNEF-Correlator: 0000000041D07162A01E644995271938BE4EE826844E2100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailman-Approved-At: Tue, 07 Jan 2003 16:40:40 -0500
Subject: Process class is not exported under Win32
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, 06 Jan 2003 14:36:33 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01C2B565.857273B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

cc++ version 1.07
 
It would seem that the Process.h is missing 
 
  class CCXX_CLASS_EXPORT Process;

so that the Process class is visible in the windows import library.
 
Symptoms are that any program that uses any of the Win32 supported methods
such as spawn fails to link due to an unresolved reference.

------=_NextPart_000_0000_01C2B565.857273B0
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="winmail.dat"

eJ8+Ig8OAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGAAcAAQAAAAAAAAEGgAMADgAAANMHAQAG
AAkAGQAAAAEABAEBA5AGAJwJAAAqAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAAC
ATEAAQAAABgAAAAAAAAAQdBxYqAeZEmVJxk4vk7oJiROIQADADYAAAAAAB4AcAABAAAAKgAAAFBy
b2Nlc3MgY2xhc3MgaXMgbm90IGV4cG9ydGVkIHVuZGVyIFdpbjMyAAAAAgFxAAEAAAAWAAAAAcKz
/zk9LPpvuIK9SO2OZE3FOLarPQAAAgEdDAEAAAAiAAAAU01UUDpJR09VR0hAR1JJRElST04tTkVU
V09SS1MuQ09NAAAACwABDgAAAABAAAYOAIYLZY+1wgECAQoOAQAAABgAAAAAAAAAQdBxYqAeZEmV
Jxk4vk7oJsKAAAADABQOAAAAAAsAHw4BAAAAAgEJEAEAAAD0BAAA8AQAAGESAABMWkZ1jPZBogMA
CgByY3BnMTI1gjIDQ2h0bWwxAzA/AQMB9wqAAqQD4wIAY2jBCsBzZXQwIAcTAoD/EAMAUARWCFUH
shHVDlEDAd0Q1zIGAAbDEdUzBEYQ2fkS72Y0EG8RdhHjCO8J97Y7Gr8OMDUR0gxgYwBQMwsJAWQz
NhFgC6U0IFkQAipcDrIBkGcfYDMAIDwhRE9DVFkAUEUgSFRNTCAAUFVCTElDICJALS8vVzNDIiBE
JFREITQ0LhFgVHI5AHJ0aQIgB0AiIEVOfCI+EeMf1yCACqMkjDE+OSCQIUIkfh9wJuBFQSJEJH0x
NzcgkFRJuFRMRSR9H2AO8E0HkEpzIEBlJd04NSCQL18p7yaCJX8uLyZGNg7wPOBNRVRBIAWgAjAJ
8Fh0PSIF4CFDNiMwMCguMjgysTEOIDYiJiAj8AeAPUckQEVS8EFUT1IkfSsxLPAobxcgQS+/IDE1
EWA8Qk8cRFkkfR7hNx9nOTZxIJBESVYkcB/jACEgzwAAO5URYB+5NjQ7fzyCCSXsNDggkEZPTlRc
IGYA0DPABxMgAJB6/TPAMjtrGDADsgHQAzA+X4UgEzgoMVNQQU4xgJsLYAQQPT1wMQAwMzMwYDQt
MDQwDiAysDMDO288c2NjKysgdr8EkACQAiAfjEJBOdMxIzD+NzosFPAs8ERyRklGVz7O+jU7AS9A
AktvPH4BwEZX/wqiTBgKgCXsRcAs4Ts8TB//OT86TztfTz89f1RfP59Ar/9Bv1ovQ90Ko0TPRd9a
D0pfH1NfY49Nj2WfX10mbmKMc3ACgGKXXCdhAUD/WB9QH1EvUj9TT2kPVW9Wf/9iv1ifdD9av1vP
XN9d73cvr0QvYW9z/3UDSQVAdwhgjGxkeYAJ4G0gdBEA7wVASH9ycoEQZSGAA2B5AJEEEC5oIAQA
IG0EAf0LgGdjz2TfcL9m/4Wva///bQ9uH28viK9xT3Jfc290f/91j3afd694v3nPet9772BP/32/
fs+ZL4T/jf+HH4gvoD//ad9q74mPip+Lr4y/on+O3/+P75D/kg+TH50/lT+WT5df/5hvo598/5vv
sJ+2L6SvpbsHt4SBX6yjQ0NYWF8AQ0xBU1NfRVjuUDRQswCC9Tsl7DDwOFHrNGG76GwLgGUKgbnv
np//qn+gv6HPiQ+mz6ffqO+p///F36wfrS+5H69PsF/OH7J/f7OPtJ/T77a/t8+439HHc35vgQSC
ub2/z2O9ZIORdn0EAGkCYILQC4DdowPwbkhkb3fgAW1wGmEgxcKwYiNwcnkuw7/Ez//YX8bv5C/J
D8ofyy/MP+cv/85fz2/Qf9GP0p/Tr9S/1c//1t/X79j/mp/az+//96/jf//sf+Wf5q/+v7r/vA/o
D+kf/+ov6z8A/+1f7m/vf/CP8Z//+7/zv/TP9d/27/f/2g/6b4kPH1N54dB0b23hoB/5cILQgR9J
NyOAeSBw7d4AZyNwgPV1gMAZURthVm8NMIKyV+FQM/1gc3R1cOHiZYCgM7AZsG/2ZOGgHcBjg3AW
IBIw+WDmd+DgEZBpbOGgGSAZ/8MLE8KxayBkdRmR3UDbI4AcUG4ZgN0wbEfwgKDdGYBmSAAx0BGw
LgjfDdH/I+8EzwXfBu8H/yVfNhwRAn/9lSuPAFY3bCxyOH82wTdRNYJUTUw0fTMK9X0BMwACARQ6
AQAAABAAAADzFKkwS0PAQZbDOjP6E3ZqAwDeP59OAAADAAJZAAAWAAMACVkCAAAAAwBAZQAAAAAL
ABOACCAGAAAAAADAAAAAAAAARgAAAAADhQAAAAAAAAMAFYAIIAYAAAAAAMAAAAAAAABGAAAAABCF
AAAAAAAAAwAbgAggBgAAAAAAwAAAAAAAAEYAAAAAUoUAAOOQAQADACKACCAGAAAAAADAAAAAAAAA
RgAAAAABhQAAAAAAAB4ANIAIIAYAAAAAAMAAAAAAAABGAAAAAFSFAAABAAAABQAAADEwLjAAAAAA
CwA1gAggBgAAAAAAwAAAAAAAAEYAAAAABoUAAAAAAAALADmACCAGAAAAAADAAAAAAAAARgAAAAAO
hQAAAAAAAAMAPIAIIAYAAAAAAMAAAAAAAABGAAAAABiFAAAAAAAACwBTgAggBgAAAAAAwAAAAAAA
AEYAAAAAgoUAAAEAAAAeAFSACCAGAAAAAADAAAAAAAAARgAAAACDhQAAAQAAABMAAAA2NDYxMDMx
MTQtMDQwMTIwMDMAAAIB+A8BAAAAEAAAAEHQcWKgHmRJlScZOL5O6CYCAfoPAQAAABAAAABB0HFi
oB5kSZUnGTi+TugmAgH7DwEAAACUAAAAAAAAADihuxAF5RAaobsIACsqVsIAAG1zcHN0LmRsbAAA
AAAATklUQfm/uAEAqgA32W4AAABDOlxEb2N1bWVudHMgYW5kIFNldHRpbmdzXGlnb3VnaFxMb2Nh
bCBTZXR0aW5nc1xBcHBsaWNhdGlvbiBEYXRhXE1pY3Jvc29mdFxPdXRsb29rXE91dGxvb2sucHN0
AAMA/g8FAAAAAwANNP03AgACARQ0AQAAABAAAABOSVRB+b+4AQCqADfZbgAAAgF/AAEAAAAxAAAA
MDAwMDAwMDA0MUQwNzE2MkEwMUU2NDQ5OTUyNzE5MzhCRTRFRTgyNjg0NEUyMTAwAAAAAAMABhCy
ZY64AwAHEPIAAAADABAQAAAAAAMAERABAAAAHgAIEAEAAABlAAAAQ0MrK1ZFUlNJT04xMDdJVFdP
VUxEU0VFTVRIQVRUSEVQUk9DRVNTSElTTUlTU0lOR0NMQVNTQ0NYWENMQVNTRVhQT1JUUFJPQ0VT
UztTT1RIQVRUSEVQUk9DRVNTQ0xBU1NJUwAAAADb6A==

------=_NextPart_000_0000_01C2B565.857273B0--




From MAILER-DAEMON Tue Jan 07 18:38:53 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18W2mu-0005tO-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 18:05:36 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18W1BO-0004Vc-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 16:22:46 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18W0I0-0000T4-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 15:26: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 18W0I0-0000Si-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 15:25:32 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8D00FPW22J6I@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Tue, 07 Jan 2003 12:25:31 -0800 (PST)
Date: Tue, 07 Jan 2003 12:25:31 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp@gnu.org
Message-id: <NBBBJJODBJBNJFNIDDCNIEPNDDAA.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: multipart/mixed; boundary="Boundary_(ID_AhTxg/r/7JAItajIZS221g)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Subject: commconcpp2 changes to date.cpp (copy)
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, 07 Jan 2003 23:05:34 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_AhTxg/r/7JAItajIZS221g)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

I just started recieving list messages again today.  It appears that my
previous messages were lost, so I'm forwarding them again...

The recent changes to date.cpp broke the library under MSVC 6.0 on the
following:

  nyear = int(trunc(i));
  nmonth = int(trunc(j));
  nday = int(trunc(k));

I removed the trunc() function, and wondered if it was redundant anyway?
since the int() should suffice.

I also wrote a test suite for the date class (figured what better way to
determine if trunc() was necessary, and it needed to be done anyway) The
following are the test cases, and I'll save the code fore release with the
test suite:

  DateTest.testSimpleGets ...
  DateTest.testSimpleSets ...
  DateTest.testIsValid ...
  DateTest.testGetDate_String ...
  DateTest.testGetDate_time_t ...
  DateTest.testGeteDate_struct_tm ...
  DateTest.testOperations ...

and implemented a functions that were defined in the class but not
implemented (linker errors).  I also re-arranged some of the related methods
to avoid duplicate code.  I've attached diffs showing what was changed. here
is a summary:

date.cpp
- added test fixture for the Date class and fixed/enhanced.
- implemented missing tm* Date::getDate(tm*) function declared in
  class but not in implementation. took the liberty to make it
  also return a time_t instead of tm* in addition to filling the
  provided tm structure.
- simplified time_t Date::getDate(void) to use the above function.
- changed setDate parameter to const and placed (char*) in calls to Number.
setDate's use of Number seems to guarantee constness, but I don't know if
Number itself does. hopefully these casts can be removed someday.

email me with questions and comments.

,Chad

--Boundary_(ID_AhTxg/r/7JAItajIZS221g)
Content-type: application/octet-stream; name=date_cpp.diff
Content-transfer-encoding: 7bit
Content-disposition: attachment; filename=date_cpp.diff

Index: date.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/date.cpp,v
retrieving revision 1.4.2.5
diff -u -r1.4.2.5 date.cpp
--- date.cpp	6 Jan 2003 15:04:32 -0000	1.4.2.5
+++ date.cpp	7 Jan 2003 00:32:38 -0000
@@ -86,12 +86,12 @@
 	setDate(str, size);
 }
 
-void Date::setDate(char *str, size_t size)
+void Date::setDate(const char *str, size_t size)
 {
 	time_t now;
 	struct tm *dt;
 	int year;
-	char *md;
+	const char *md;
 
 	if(!size)
 		size = strlen(str);
@@ -107,18 +107,18 @@
 	{
 		time(&now);
 		dt = localtime(&now);
-		Number nyear(str, 2);
+		Number nyear((char*)str, 2);
 		year = ((dt->tm_year + 1900) / 100) * 100 + nyear();
 		md = str + 2;
 	}
 	else
 	{
-		Number nyear(str, 4);
+		Number nyear((char*)str, 4);
 		year = nyear();
 		md = str + 4;
 	}
-	Number nmonth(md, 2);
-	Number nday(md + 2, 2);
+	Number nmonth((char*)md, 2);
+	Number nday((char*)md + 2, 2);
 	toJulian(year, nmonth(), nday());
 }
 
@@ -140,20 +140,26 @@
 	return buf;
 }
 
-time_t Date::getDate(void)
+time_t Date::getDate(tm* dt)
 {
 	char buf[9];
-	struct tm dt;
-	memset(&dt, 0, sizeof(dt));
+	memset(dt, 0, sizeof(tm));
 	fromJulian(buf);
 	Number nyear(buf, 4);
 	Number nmonth(buf + 4, 2);
 	Number nday(buf + 6, 2);
 	
-	dt.tm_year = nyear() - 1900;
-	dt.tm_mon = nmonth() - 1;
-	dt.tm_mday = nday();
-	return mktime(&dt);
+	dt->tm_year = nyear() - 1900;
+	dt->tm_mon = nmonth() - 1;
+	dt->tm_mday = nday();
+
+	return mktime(dt); // to fill in day of week etc.
+}
+
+time_t Date::getDate(void)
+{
+	struct tm dt;
+	return getDate(&dt);
 }
 
 int Date::getYear(void)
@@ -303,9 +309,9 @@
 	l = int(j/11);
 	j = j+2-12*l;
 	i = 100*(n - 49) + i + l;
-	nyear = int(trunc(i));
-	nmonth = int(trunc(j));
-	nday = int(trunc(k));
+	nyear = int(i);
+	nmonth = int(j);
+	nday = int(k);
 	
 	buffer[8] = '\0';
 }

--Boundary_(ID_AhTxg/r/7JAItajIZS221g)
Content-type: application/octet-stream; name=numbers_h.diff
Content-transfer-encoding: 7bit
Content-disposition: attachment; filename=numbers_h.diff

Index: numbers.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/numbers.h,v
retrieving revision 1.2.2.4
diff -u -r1.2.2.4 numbers.h
--- numbers.h	18 Nov 2002 20:18:38 -0000	1.2.2.4
+++ numbers.h	7 Jan 2003 00:34:16 -0000
@@ -156,7 +156,7 @@
 	Date(time_t tm);
 	Date(tm *dt);
 	Date(char *str, size_t size = 0);
-	Date(int year, unsigned month, unsigned day);	
+	Date(int year, unsigned month, unsigned day);
 	Date();
 
 	int getYear(void);
@@ -165,9 +165,9 @@
 	unsigned getDayOfWeek(void);
 	char *getDate(char *buffer);
 	time_t getDate(void);
+	time_t getDate(tm *buf);
 	long getValue(void);
-	tm *getDate(tm *buf);
-	void setDate(char *str, size_t size = 0);
+	void setDate(const char *str, size_t size = 0);
 	bool isValid(void);
 
 	friend Date operator+(Date &date, long val);

--Boundary_(ID_AhTxg/r/7JAItajIZS221g)--



From MAILER-DAEMON Tue Jan 07 20:39:28 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18W1v6-0005cZ-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 17:10:00 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18W1AB-0004IA-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 16:21:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18W18w-0004Cm-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 16:20:45 -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 18W0kh-0007GG-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 15:55:11 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8D007JK3FYFV@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Tue, 07 Jan 2003 12:55:10 -0800 (PST)
Date: Tue, 07 Jan 2003 12:55:10 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp <bug-commoncpp@gnu.org>
Message-id: <NBBBJJODBJBNJFNIDDCNIEPODDAA.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: multipart/mixed; boundary="Boundary_(ID_ZJrlIYMyBOJFj5dbSy7fUw)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Subject: base 64 encode/decode test
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, 07 Jan 2003 22:09:58 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_ZJrlIYMyBOJFj5dbSy7fUw)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Here is the test program I promised.  On my win32 system and vc++ 6.0 the
second two tests (testPadding1Short, testPadding2Short) fail unless I change
part of the b64Decode function like so:

if (c == '=')
{
  if (bits & 0x40000)
  {
    if (dstsize < 2) break;
    *(pdst++) = (bits >> 10);  // changed from '(bits >> 16)'
    *(pdst++) = (bits >> 2) & 0xff;  // changed from '(bits >> 8) & 0xff'
    break;
  }
  if (bits & 0x1000 && dstsize)
    *(pdst++) = (bits >> 4);  // changed from '(bits >> 10)'
  break;
}

What I want to know if this is system specific (endian related?) or an
actual bug.

thanks,

Chad

--Boundary_(ID_ZJrlIYMyBOJFj5dbSy7fUw)
Content-type: application/octet-stream; name=b64test.cpp
Content-transfer-encoding: quoted-printable
Content-disposition: attachment; filename=b64test.cpp

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

using namespace ost;

void testPaddingPerfect()
{
  const char inputChars[] =3D "aaabbb123";
  char actualEncodedChars[1000];
  char actualDecodedChars[1000];

  std::cout << "Input Text: '" << inputChars << "'" << std::endl;

  b64Encode((const unsigned char *)inputChars, strlen(inputChars), =
actualEncodedChars, sizeof(actualEncodedChars));
  std::cout << "   Encoded: '" << actualEncodedChars << "'" << =
std::endl;

  int size =3D b64Decode(actualEncodedChars, (unsigned char =
*)actualDecodedChars, sizeof(actualDecodedChars));
  actualDecodedChars[size] =3D '\0';
  std::cout << "   Decoded: '" << actualDecodedChars << "'" << =
std::endl;

  if (std::string(inputChars) =3D=3D std::string(actualDecodedChars))
    std::cout << "  Test: PASSED" << std::endl;
  else
    std::cout << "  Test: FAILED" << std::endl;
}

void testPadding1Short()
{
  const char inputChars[] =3D "aaabbb12";
  char actualEncodedChars[1000];
  char actualDecodedChars[1000];

  std::cout << "Input Text: '" << inputChars << "'" << std::endl;

  b64Encode((const unsigned char *)inputChars, strlen(inputChars), =
actualEncodedChars, sizeof(actualEncodedChars));
  std::cout << "   Encoded: '" << actualEncodedChars << "'" << =
std::endl;

  int size =3D b64Decode(actualEncodedChars, (unsigned char =
*)actualDecodedChars, sizeof(actualDecodedChars));
  actualDecodedChars[size] =3D '\0';
  std::cout << "   Decoded: '" << actualDecodedChars << "'" << =
std::endl;

  if (std::string(inputChars) =3D=3D std::string(actualDecodedChars))
    std::cout << "  Test: PASSED" << std::endl;
  else
    std::cout << "  Test: FAILED" << std::endl;
}

void testPadding2Short()
{
  const char inputChars[] =3D "aaabbb1";
  char actualEncodedChars[1000];
  char actualDecodedChars[1000];

  std::cout << "Input Text: '" << inputChars << "'" << std::endl;

  b64Encode((const unsigned char *)inputChars, strlen(inputChars), =
actualEncodedChars, sizeof(actualEncodedChars));
  std::cout << "   Encoded: '" << actualEncodedChars << "'" << =
std::endl;

  int size =3D b64Decode(actualEncodedChars, (unsigned char =
*)actualDecodedChars, sizeof(actualDecodedChars));
  actualDecodedChars[size] =3D '\0';
  std::cout << "   Decoded: '" << actualDecodedChars << "'" << =
std::endl;

  if (std::string(inputChars) =3D=3D std::string(actualDecodedChars))
    std::cout << "  Test: PASSED" << std::endl;
  else
    std::cout << "  Test: FAILED" << std::endl;
}

int main(int argc, char* argv[])
{
  /*
  const char inputChars[] =3D "aaabbb12";
  char actualEncodedChars[1000];
  char actualDecodedChars[1000];

  std::cout << "Input Text: '" << inputChars << "'" << std::endl;

  b64Encode((const unsigned char *)inputChars, strlen(inputChars), =
actualEncodedChars, sizeof(actualEncodedChars));
  std::cout << "   Encoded: '" << actualEncodedChars << "'" << =
std::endl;

  int size =3D b64Decode(actualEncodedChars, (unsigned char =
*)actualDecodedChars, sizeof(actualDecodedChars));
  actualDecodedChars[size] =3D '\0';
  std::cout << "   Decoded: '" << actualDecodedChars << "'" << =
std::endl;

  if (std::string(inputChars) =3D=3D std::string(actualDecodedChars))
    std::cout << "PASSED" << std::endl;
  else
    std::cout << "FAILED" << std::endl;
  */
  testPaddingPerfect();
  testPadding1Short();
  testPadding2Short();

  return 0;
}


--Boundary_(ID_ZJrlIYMyBOJFj5dbSy7fUw)--



From MAILER-DAEMON Tue Jan 07 21:10:51 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Vwv0-0005vL-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:49:34 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VZye-0000k1-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:19:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VZqx-0006lO-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:11:53 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VYvu-0005jz-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 10:12:55 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18VYvl-0002Gm-00; Mon, 06 Jan 2003 16:12:45 +0100
Date: Mon, 6 Jan 2003 16:12:45 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Marcelo Dalmas <mad@brasmap.com.br>
Message-ID: <20030106151244.GA4098@bulbasaur.rediris.es>
Mail-Followup-To: Marcelo Dalmas <mad@brasmap.com.br>,
	ccxx <bug-commoncpp@gnu.org>
References: <20030103141106.1c9909a6.mad@brasmap.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030103141106.1c9909a6.mad@brasmap.com.br>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: ccxx <bug-commoncpp@gnu.org>
Subject: Re: Date::fromJulian 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, 06 Jan 2003 16:20:50 -0000


	Fixed in CVS.

On Fri, Jan 03, 2003 at 02:11:06PM -0200, Marcelo Dalmas wrote:
> 
> Hi,
> 
> I am sending a patch for date.cpp with Henry F. Fliegel and Thomas C. Van
> Flandern algorithm. It's same from Commoncpp2 0.99.7 with a correction:
> 
> year = 100 * (n - 49) + i + 1;
> 
> The last "1" isn't a 1, it is a "l", :)
> 
> In current release, Date isn't working. Date return 2002-01-03 for today year.
> 
> by
> 
> -- 
> Marcelo Dalmas
> BRASMAP Sistemas
> www.brasmap.com.br
> Fone/Fax: (48) 333-2218 ramal 2114
> 
> Linux user #114373 http://counter.li.org/
> 


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




From MAILER-DAEMON Tue Jan 07 21:33:43 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18W56n-0000eL-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 20:34:17 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18W1b6-0001J0-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 16:49:20 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18W1GB-0005hs-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 16:28:14 -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 18W0MC-0001IP-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 15:29:52 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8D00FH129R6I@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Tue, 07 Jan 2003 12:29:52 -0800 (PST)
Date: Tue, 07 Jan 2003 12:29:51 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp@gnu.org
Message-id: <NBBBJJODBJBNJFNIDDCNCEPODDAA.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: urlstring testing/enhancement (copy)
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, 08 Jan 2003 01:34:10 -0000

I just started recieving list messages again today.  It appears that my
previous messages were lost, so I'm forwarding them again...

I built urlstring testcases this weekend. Here are the test cases performed:
  URLStringTest.testBinaryBase64EncodeDecode ...
  URLStringTest.testStringVersion ...
  URLStringTest.testTypicalUrlEncodeDecode ...
  URLStringTest.testTypicalTextBase64EncodeDecode ...
  URLStringTest.testSimpleTextBase64EncodeDecode ...
  URLStringTest.testComplexTextBase64EncodeDecode ...
  URLStringTest.testPaddingPerfect ...
  URLStringTest.testPadding1Short ...
  URLStringTest.testPadding2Short ...

I have some issues to resolve with the b64Decode function, as it appears to
not work correctly when the base 64 output is padded to a multiple of 3.  I
have patched my version, but wonder if it is just a problem on my system.
I'll upload some test code if someone is willing to try it.

I also added Base64 functions that take std::string arguments for the encode
output and the decode input.  I don't know where the line is supposed to be
relating to std::string usage as I see most of common c++ is char* based,
but there seems to be std::string usage in some classes.  personally I like
having it as an overloaded version.  I can post diffs showing the new
functions if they are wanted.

,Chad




From MAILER-DAEMON Tue Jan 07 22:50:38 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwuY-0005u0-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:49:06 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VZqv-0006ja-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:11:49 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VZpk-0006M2-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:10:37 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VZnV-0005f8-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:08:17 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18VZoA-0002JA-00; Mon, 06 Jan 2003 17:08:58 +0100
Date: Mon, 6 Jan 2003 17:08:57 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-ID: <20030106160857.GD4098@bulbasaur.rediris.es>
Mail-Followup-To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20030101210824.GH415@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030101210824.GH415@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: Signalling a condition
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, 06 Jan 2003 16:12:47 -0000


	Hi, I guess you are considering that Conditional handles the
mutex as well as the condition variable. However, Conditional is meant
to allow the user to independently perform operantions on both
things. You may find interesting a mail in the arhives from November,
"[ Patch #623 ] ost::Conditional is broken with posix threads". There
is also a discussion on this on the savannah patch manager (you may
need to browse the 'closed' patches).

On Wed, Jan 01, 2003 at 11:08:25PM +0200, Albert Strasheim wrote:
> Hello,
> 
> I have a question about Conditional::signal().
> 
> According to the glibc manual (describing pthread_cond_wait),
> 
> "Unlocking the mutex and suspending on the condition variable is done 
> atomically. Thus, if all threads always acquire the mutex before 
> signaling the condition, this guarantees that the condition cannot be 
> signaled (and thus ignored) between the time a thread locks the mutex 
> and the time it waits on the condition variable."
> 
> The current code:
> 
> void ost::Conditional::signal(bool broadcast) 
> {
>   if(broadcast)
>     pthread_cond_broadcast(&_cond);
>   else
>     pthread_cond_signal(&_cond);
> }
> 
> But according to the glibc manual, "... if all threads always acquire 
> the mutex before signaling the condition ...".
> 
> The new signal method would then read:
> 
> void ost::Conditional::signal(bool broadcast) 
> {
>   enterMutex();
>   if(broadcast)
>     pthread_cond_broadcast(&_cond);
>   else
>     pthread_cond_signal(&_cond);
>   leaveMutex();
> }
> 
> What will happen now is that all the threads that called
> pthread_cond_wait will start waking up, and one will acquire the mutex. 
> It will then possibly do something, and then unlock the mutex and go 
> about its business, allowing the next thread to complete its
> pthread_cond_wait call and so forth.
> 
> Comments? Am I even correct? :-)
> 
> Cheers,
> 
> Albert
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Tue Jan 07 23:06:53 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18W7DU-0005Sd-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 22:49:20 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18W1D4-0004xO-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 16:24:30 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18W0I0-0000TF-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 15:26:04 -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 18W0I0-0000Si-01
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 15:25:32 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8D00FPW22J6I@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Tue, 07 Jan 2003 12:25:31 -0800 (PST)
Date: Tue, 07 Jan 2003 12:25:31 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp@gnu.org
Message-id: <NBBBJJODBJBNJFNIDDCNKEPNDDAA.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: bugs in CRC32 (copy)
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, 08 Jan 2003 03:49:19 -0000

I just started recieving list messages again today.  It appears that my
previous messages were lost, so I'm forwarding them again...

I did a little research -- I'm not an expert on CRC algorithms, allthough I
might be after all this ;)

I did a myriad of searches on google to see if I could find out how many
different versions of crc32 there are.  I had hoped to find a definite
answer, however, that doesn't seem to be the case.  I found a document that
discusses this problem
(http://ce.sharif.edu/~cheraghchi/science/cs/crc_algorithm.htm if
interestd).

it appears that the most common CRC32 version is the one for ethernet, and
according to the above, is also "reportedly used in PKZip, AUTODIN II,
Ethernet, and FDDI."  I'm not familiar with ATM, so don't know if it uses a
different version.

anyway, according to the docs above this version has these distinguishing
attributes. (The Check: value is the result of running it against
'123456789').

   Name   : "CRC-32"
   Width  : 32
   Poly   : 04C11DB7
   Init   : FFFFFFFF
   RefIn  : True
   RefOut : True
   XorOut : FFFFFFFF
   Check  : CBF43926

The fsum program I've been using to validate some of my tests also generates
that number:

  ; SlavaSoft Optimizing Checksum Utility fsum 2.0 <www.slavasoft.com>
  ; Generated on 01/06/03 at 14:19:17
  cbf43926 ?CRC32*check.txt

So, it should be pretty safe to assume that it is implementing the same
version of the algorithm.  the changes I made bring it into check with that
version.  It's really a shame that there is the possiblilyt of multiple
versions masquerading as "CRC32"  we may need to create 2 or more versions
if we want to cover both the old and new versions.  perhaps the code could
be templatized (using template values) and be instantiated into digest.cpp
for CRC, CRC16, CRC32_Ethernet, CRC32_ATM, etc... or , if those weren't
enough they could just use the template directly like so:

  CRC<32, 0x04C11DB7, 0xFFFFFFFF, true, true, 0xFFFFFFFF>

Its an idea anyway :)  I might even be willing to pursue it if it sounds
useful (for educational reasons)

another idea may be to copy the code from the above doc (it says the code is
public domain) and then have the commoncpp2 classes call it with the right
parms.  I don't know if it's fast or not.  the current CRC32 creates tables
everytime it's called, so I'd say it's not exactly efficient either (maybe
the initialization should be moved to a class initializer?)

thoughts?

,Chad


> 	As for the algorithm results, either the cc++ implementation
> or the two programs appear to be wrong. However, the three tests of
> the crc32 demo are the official examples of the ATM standard. Do those
> two programs you mention provide the result expected in the demo for
> the three tests?  They may be using a different generator polynomial.
>
> On Thu, Jan 02, 2003 at 05:59:38PM -0800, Chad Yates wrote:
> > I have discovered and fixed some bugs in the CRC32Digest class while
> > developing test cases for the digest classes.
> >
> > 1) the virtual function overflow was not being called (at least
> on win32) so
> > I changed the argument and return type to int (as in the other digest
> > classes)...
> >
> > 2) the lookup table was not using "reflection" during its initialization
> > (apparently this is a part of the CRC32 standard
> implementation) so I added
> > a reflect function and changed (replaced) the lookup code to use it. I
> > commented out the old code so you can see it in the diff.
> >
> > 3) I moved the crc32 = 0 from the constructor to the initDigest
> method so it
> > is reset both during construction and reseting.
> >
> > 4) I removed the crc32 = ~crc_reg in the overload method and moved it to
> > both the getDigest and strDigest methods as a minor performance
> improvement
> > (won't be re-computed for every octet in the stream)
> >
> > finally, I checked the output agains two programs available on
> the net, and
> > it matches both, however the existing CRC32 demo program now reports all
> > failures.  I suspect that the tests were not valid to begin with, but if
> > anyone would like to verify this (or comment) please do so.
> >
> > ,chad
> >
> > Index: digest.h
> > ===================================================================
> > RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/digest.h,v
> > retrieving revision 1.10
> > diff -r1.10 digest.h
> > 204c204
> > <    unsigned char overflow(unsigned char octet);
> > ---
> > >    int overflow(int octet);
> > 207c207,209
> > <
> > ---
> > >
> > >    unsigned long reflect(unsigned long ref, unsigned char ch);
> > >
> >
> > Index: digest.cpp
> > ===================================================================
> > RCS file: /cvsroot/commoncpp/commoncpp2/src/digest.cpp,v
> > retrieving revision 1.4
> > diff -r1.4 digest.cpp
> > 145d144
> > <    crc32 = 0;
> > 161,172c160,182
> > <    for (i = 0; i < 256; i++)
> > <    {
> > <       crc = ( (unsigned long) i << 24 );
> > <       for (j = 0; j < 8; j++)
> > <       {
> > <          if (crc & 0x80000000)
> > <             crc = (crc << 1) ^ POLYNOMIAL;
> > <          else
> > <             crc <<= 1;
> > <       }
> > <       crc_table[i] = crc;
> > <    }
> > ---
> > >   for(i = 0; i <= 0xFF; i++)
> > >   {
> > >     crc=reflect(i, 8) << 24;
> > >     for (j = 0; j < 8; j++)
> > >       crc = (crc << 1) ^ (crc & (1 << 31) ? POLYNOMIAL : 0);
> > >     crc_table[i] = reflect(crc, 32);
> > >   }
> > >   /* old loop without reflection
> > >   for (i = 0; i < 256; i++)
> > >   {
> > >     crc = ( (unsigned long) i << 24 );
> > >     for (j = 0; j < 8; j++)
> > >     {
> > >       if (crc & 0x80000000)
> > >         crc = (crc << 1) ^ POLYNOMIAL;
> > >       else
> > >         crc <<= 1;
> > >     }
> > >     crc_table[i] = crc;
> > >   }
> > >   */
> > >
> > >    crc32 = 0;
> > 175c185,201
> > < unsigned char CRC32Digest::overflow(unsigned char octet)
> > ---
> > > unsigned long CRC32Digest::reflect(unsigned long ref,
> unsigned char ch)
> > > {
> > >   unsigned long value = 0;
> > >
> > >   // Swap bit 0 for bit 7
> > >   // bit 1 for bit 6, etc.
> > >   for(int i = 1; i < (ch + 1); i++)
> > >   {
> > >     if(ref & 1)
> > >       value |= 1 << (ch - i);
> > >     ref >>= 1;
> > >   }
> > >
> > >   return value;
> > > }
> > >
> > > int CRC32Digest::overflow(int octet)
> > 177,179c203,206
> > <    crc_reg = crc_table[((crc_reg >> 24) ^ octet) & 0xFF] ^
> (crc_reg << 8);
> > <    crc32 = ~crc_reg;
> > <
> > ---
> > >    //crc_reg = crc_table[((crc_reg >> 24) ^ octet) & 0xFF] ^
> (crc_reg <<
> > 8);
> > >        crc_reg = (crc_reg >> 8) ^ crc_table[(crc_reg & 0xFF) ^ octet];
> > >    //crc32 = ~crc_reg; deferred calculation until later
> rather than for
> > every
> > byte
> > >
> > 184a212
> > >    crc32 = ~crc_reg; // finalize crc32 before exporting
> > 198a227
> > >    crc32 = ~crc_reg;  // finalize crc32 before exporting
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Tue Jan 07 23:34:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwzB-0006Ea-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:53:53 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VrtL-0001yH-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 06:27:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Vrsp-0001Hu-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 06:27:30 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Vrso-00012S-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 06:26:58 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18VrtA-0000cC-00; Tue, 07 Jan 2003 12:27:20 +0100
Date: Tue, 7 Jan 2003 12:27:19 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Jeremy Noetzelman <jjn@kriln.com>
Message-ID: <20030107112717.GA308@bulbasaur.rediris.es>
Mail-Followup-To: Jeremy Noetzelman <jjn@kriln.com>,
	Federico Montesino Pouzols <fedemp@altern.org>,
	Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20030106161441.GE4098@bulbasaur.rediris.es>
	<20030106163305.X180-100000@nosferatu.kriln.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030106163305.X180-100000@nosferatu.kriln.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: Non Threaded use of TCPSocket with select/poll?
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, 07 Jan 2003 11:27:32 -0000


	Yes, I would say that with CC++ you need to create at least one
additional thread.

On Mon, Jan 06, 2003 at 04:33:49PM +0000, Jeremy Noetzelman wrote:
> My point is I want a single thread for the entire application.  Not two,
> not more than two.  One.  It doesn't seem that CommonC++ supports such an
> application without a fair amount of work.  Please correct me if I'm wrong
> though.
> 
> J
> 
> On Mon, 6 Jan 2003, Federico Montesino Pouzols wrote:
> 
> >
> > 	If you only want a limited number of threads and to simulate
> > concurrency through select/poll, I think the SocketPort and
> > SocketService classes are the most adequate classes in Common
> > C++. There is a tcpservice demo that shows how to use them.
> >
> > On Fri, Jan 03, 2003 at 08:26:11PM +0000, Jeremy Noetzelman wrote:
> > > I'm more concerned about having a proper select polling loop for the
> > > server socket ... I'm less concerned about the client connection sockets.
> > >
> > > On Fri, 3 Jan 2003, Albert Strasheim wrote:
> > >
> > > > Hello,
> > > >
> > > > >From the Common C++ documentation for tcpstream (not TCPStream):
> > > >
> > > > A more natural C++ "tcpstream" class for use by non-threaded
> > > > applications. C++ "fstream" style tcpstream class.
> > > >
> > > > I don't know if this is what you want?
> > > >
> > > > Cheers,
> > > >
> > > > Albert
> > > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Bug-commoncpp mailing list
> > > Bug-commoncpp@gnu.org
> > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> >
> 



From MAILER-DAEMON Tue Jan 07 23:44:15 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwxC-000658-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:51:50 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Vg0i-0000av-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 17:46:20 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Vg0B-0008Fc-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 17:46:19 -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 18Vg0B-0008DJ-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 17:45:47 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8B00M5KDW8QI@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Mon, 06 Jan 2003 14:45:44 -0800 (PST)
Date: Mon, 06 Jan 2003 14:45:44 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20030106200308.GJ4098@bulbasaur.rediris.es>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-id: <NBBBJJODBJBNJFNIDDCNEEPGDDAA.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
cc: bug-commoncpp@gnu.org
Subject: RE: bugs in CRC32
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, 06 Jan 2003 22:46:21 -0000

I did a little research -- I'm not an expert on CRC algorithms, allthough I
might be after all this ;)

I did a myriad of searches on google to see if I could find out how many
different versions of crc32 there are.  I had hoped to find a definite
answer, however, that doesn't seem to be the case.  I found a document that
discusses this problem
(http://ce.sharif.edu/~cheraghchi/science/cs/crc_algorithm.htm if
interestd).

it appears that the most common CRC32 version is the one for ethernet, and
according to the above, is also "reportedly used in PKZip, AUTODIN II,
Ethernet, and FDDI."  I'm not familiar with ATM, so don't know if it uses a
different version.

anyway, according to the docs above this version has these distinguishing
attributes. (The Check: value is the result of running it against
'123456789').

   Name   : "CRC-32"
   Width  : 32
   Poly   : 04C11DB7
   Init   : FFFFFFFF
   RefIn  : True
   RefOut : True
   XorOut : FFFFFFFF
   Check  : CBF43926

The fsum program I've been using to validate some of my tests also generates
that number:

  ; SlavaSoft Optimizing Checksum Utility fsum 2.0 <www.slavasoft.com>
  ; Generated on 01/06/03 at 14:19:17
  cbf43926 ?CRC32*check.txt

So, it should be pretty safe to assume that it is implementing the same
version of the algorithm.  the changes I made bring it into check with that
version.  It's really a shame that there is the possiblilyt of multiple
versions masquerading as "CRC32"  we may need to create 2 or more versions
if we want to cover both the old and new versions.  perhaps the code could
be templatized (using template values) and be instantiated into digest.cpp
for CRC, CRC16, CRC32_Ethernet, CRC32_ATM, etc... or , if those weren't
enough they could just use the template directly like so:

  CRC<32, 0x04C11DB7, 0xFFFFFFFF, true, true, 0xFFFFFFFF>

Its an idea anyway :)  I might even be willing to pursue it if it sounds
useful (for educational reasons)

another idea may be to copy the code from the above doc (it says the code is
public domain) and then have the commoncpp2 classes call it with the right
parms.  I don't know if it's fast or not.  the current CRC32 creates tables
everytime it's called, so I'd say it's not exactly efficient either (maybe
the initialization should be moved to a class initializer?)

thoughts?

,Chad


> 	As for the algorithm results, either the cc++ implementation
> or the two programs appear to be wrong. However, the three tests of
> the crc32 demo are the official examples of the ATM standard. Do those
> two programs you mention provide the result expected in the demo for
> the three tests?  They may be using a different generator polynomial.
>
> On Thu, Jan 02, 2003 at 05:59:38PM -0800, Chad Yates wrote:
> > I have discovered and fixed some bugs in the CRC32Digest class while
> > developing test cases for the digest classes.
> >
> > 1) the virtual function overflow was not being called (at least
> on win32) so
> > I changed the argument and return type to int (as in the other digest
> > classes)...
> >
> > 2) the lookup table was not using "reflection" during its initialization
> > (apparently this is a part of the CRC32 standard
> implementation) so I added
> > a reflect function and changed (replaced) the lookup code to use it. I
> > commented out the old code so you can see it in the diff.
> >
> > 3) I moved the crc32 = 0 from the constructor to the initDigest
> method so it
> > is reset both during construction and reseting.
> >
> > 4) I removed the crc32 = ~crc_reg in the overload method and moved it to
> > both the getDigest and strDigest methods as a minor performance
> improvement
> > (won't be re-computed for every octet in the stream)
> >
> > finally, I checked the output agains two programs available on
> the net, and
> > it matches both, however the existing CRC32 demo program now reports all
> > failures.  I suspect that the tests were not valid to begin with, but if
> > anyone would like to verify this (or comment) please do so.
> >
> > ,chad
> >
> > Index: digest.h
> > ===================================================================
> > RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/digest.h,v
> > retrieving revision 1.10
> > diff -r1.10 digest.h
> > 204c204
> > <    unsigned char overflow(unsigned char octet);
> > ---
> > >    int overflow(int octet);
> > 207c207,209
> > <
> > ---
> > >
> > >    unsigned long reflect(unsigned long ref, unsigned char ch);
> > >
> >
> > Index: digest.cpp
> > ===================================================================
> > RCS file: /cvsroot/commoncpp/commoncpp2/src/digest.cpp,v
> > retrieving revision 1.4
> > diff -r1.4 digest.cpp
> > 145d144
> > <    crc32 = 0;
> > 161,172c160,182
> > <    for (i = 0; i < 256; i++)
> > <    {
> > <       crc = ( (unsigned long) i << 24 );
> > <       for (j = 0; j < 8; j++)
> > <       {
> > <          if (crc & 0x80000000)
> > <             crc = (crc << 1) ^ POLYNOMIAL;
> > <          else
> > <             crc <<= 1;
> > <       }
> > <       crc_table[i] = crc;
> > <    }
> > ---
> > >   for(i = 0; i <= 0xFF; i++)
> > >   {
> > >     crc=reflect(i, 8) << 24;
> > >     for (j = 0; j < 8; j++)
> > >       crc = (crc << 1) ^ (crc & (1 << 31) ? POLYNOMIAL : 0);
> > >     crc_table[i] = reflect(crc, 32);
> > >   }
> > >   /* old loop without reflection
> > >   for (i = 0; i < 256; i++)
> > >   {
> > >     crc = ( (unsigned long) i << 24 );
> > >     for (j = 0; j < 8; j++)
> > >     {
> > >       if (crc & 0x80000000)
> > >         crc = (crc << 1) ^ POLYNOMIAL;
> > >       else
> > >         crc <<= 1;
> > >     }
> > >     crc_table[i] = crc;
> > >   }
> > >   */
> > >
> > >    crc32 = 0;
> > 175c185,201
> > < unsigned char CRC32Digest::overflow(unsigned char octet)
> > ---
> > > unsigned long CRC32Digest::reflect(unsigned long ref,
> unsigned char ch)
> > > {
> > >   unsigned long value = 0;
> > >
> > >   // Swap bit 0 for bit 7
> > >   // bit 1 for bit 6, etc.
> > >   for(int i = 1; i < (ch + 1); i++)
> > >   {
> > >     if(ref & 1)
> > >       value |= 1 << (ch - i);
> > >     ref >>= 1;
> > >   }
> > >
> > >   return value;
> > > }
> > >
> > > int CRC32Digest::overflow(int octet)
> > 177,179c203,206
> > <    crc_reg = crc_table[((crc_reg >> 24) ^ octet) & 0xFF] ^
> (crc_reg << 8);
> > <    crc32 = ~crc_reg;
> > <
> > ---
> > >    //crc_reg = crc_table[((crc_reg >> 24) ^ octet) & 0xFF] ^
> (crc_reg <<
> > 8);
> > >        crc_reg = (crc_reg >> 8) ^ crc_table[(crc_reg & 0xFF) ^ octet];
> > >    //crc32 = ~crc_reg; deferred calculation until later
> rather than for
> > every
> > byte
> > >
> > 184a212
> > >    crc32 = ~crc_reg; // finalize crc32 before exporting
> > 198a227
> > >    crc32 = ~crc_reg;  // finalize crc32 before exporting
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Tue Jan 07 23:48:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18W88Y-0005UA-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 23:48:18 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18W857-0004lq-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 23:44:45 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18W6p6-0008PU-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 22:24:39 -0500
Received: from ns.istop.com ([66.11.168.199])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18W63i-0006M8-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 21:35:10 -0500
Received: from Pokey (unknown [66.11.172.25])
	by ns.istop.com (Postfix) with SMTP id 14E2E1702E
	for <bug-commoncpp@gnu.org>; Tue,  7 Jan 2003 21:35:04 -0500 (EST)
From: "Ian Gough" <igough@istop.com>
To: <bug-commoncpp@gnu.org>
Date: Tue, 7 Jan 2003 21:35:09 -0500
Message-ID: <NDBBIOGMDMIANEEKGGEGKEGODLAA.igough@istop.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0000_01C2B694.A7232AB0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: Process class is not exported under Win32
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, 08 Jan 2003 04:48:16 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01C2B694.A7232AB0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Please forgive if this problem has already been reported.

cc++ version 1.07

It would seem that the Process.h is missing the statement:

  class CCXX_CLASS_EXPORT Process;

so that the Process class is visible in the windows import library.

Symptoms are that any program that uses any of the Win32 supported methods
such as spawn fails to link due to an unresolved reference.

------=_NextPart_000_0000_01C2B694.A7232AB0
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=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D646103114-04012003><SPAN=20
class=3D234403002-08012003>Please forgive if this problem has already =
been=20
reported.</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D646103114-04012003><SPAN=20
class=3D234403002-08012003></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D646103114-04012003>cc++ =
version=20
1.07</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D646103114-04012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D646103114-04012003>It =
would seem that=20
the Process.h is missing<SPAN class=3D234403002-08012003> the=20
statement</SPAN><SPAN class=3D234403002-08012003>:</SPAN> =
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D646103114-04012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D646103114-04012003>&nbsp; =
class=20
CCXX_CLASS_EXPORT Process;</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D646103114-04012003><BR></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
class=3D646103114-04012003>so that the Process class is visible in the =
windows=20
import library.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D646103114-04012003></SPAN></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D646103114-04012003><FONT face=3DArial =
size=3D2>Symptoms are that=20
any program that uses any of&nbsp;<SPAN class=3D234403002-08012003>the=20
</SPAN>Win32 supported methods&nbsp;such as spawn fails to link due to =
an=20
unresolved reference.</FONT></DIV></SPAN></DIV></BODY></HTML>

------=_NextPart_000_0000_01C2B694.A7232AB0--




From MAILER-DAEMON Wed Jan 08 00:39:21 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18W8Lp-0000x9-00
	for mharc-bug-commoncpp@gnu.org; Wed, 08 Jan 2003 00:02:01 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18W6dw-0006As-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 22:12:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18W69q-0007Io-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 21:42:01 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VxpW-0002Y7-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 12:47:58 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18VxpT-00078L-00
	for bug-commoncpp@gnu.org; Tue, 07 Jan 2003 19:47:55 +0200
Received: (qmail 20216 invoked from network); 7 Jan 2003 17:47:55 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 7 Jan 2003 17:47:55 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18WIi6-0000OM-00; Wed, 08 Jan 2003 18:05:42 +0200
Date: Wed, 8 Jan 2003 18:05:42 +0200
From: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-ID: <20030108160541.GB434@dogbert.sdsl.sun.ac.za>
References: <20030103214523.GP887@dogbert.sdsl.sun.ac.za>
	<20030106163246.GG4098@bulbasaur.rediris.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030106163246.GG4098@bulbasaur.rediris.es>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18VxpT-00078L-00*/FzMU/x5kL6*
X-Mailman-Approved-At: Wed, 08 Jan 2003 00:01:59 -0500
cc: bug-commoncpp@gnu.org
Subject: Re: doxygen @short directive in comments
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, 08 Jan 2003 03:13:59 -0000

Hello,

On Mon, 06 Jan 2003, Federico Montesino Pouzols wrote:

> 	Um, yes this should be fixed. Another pending issue with the
> doxygen doc is that, as reported sometime ago, ost::Exception does not
> appear in it. This is because there is a specific doc/cc++/config.h
> for doxygen which only defines a few configuration constants. Should
> not we remove this file and simply use the config.h generated by
> configure?

Sounds like a plan. Don't know why this hasn't been done all along. I 
wouldn't want my docs to reflect some other system.

Here's a more general question: how is any autoconf/automake project 
supposed to use the config.h file?

It seems to be as if the right way to go about things is to have 
autoconf generate a config.h header which you include with your 
installed headers (which seems to be what Common C++ does), and always 
include if you need configuration info in your other headers.

BTW, with autoconf 2.57, reconfig prints the following warning message 
when you generate the files for the build system:

fullung@dogbert:~/work/commoncpp2> ./reconfig
Putting files in AC_CONFIG_AUX_DIR, `config'.
WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
WARNING: and `config.h.top', to define templates for `config.h.in'
WARNING: is deprecated and discouraged.

WARNING: Using the third argument of `AC_DEFINE' and
WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
WARNING: `acconfig.h':

WARNING:   AC_DEFINE([NEED_MAIN], 1,
WARNING:             [Define if a function `main' is needed.])

WARNING: More sophisticated templates can also be produced, see the
WARNING: documentation.

Cheers,

Albert



From MAILER-DAEMON Wed Jan 08 00:50:23 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Vwxb-00067W-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:52:15 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Vhrs-0005h1-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 19:45:20 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Vhrl-0005YQ-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 19:45:15 -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 18Vhrd-0005Sx-01
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 19:45:05 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8B00ECXJF34L@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Mon, 06 Jan 2003 16:45:04 -0800 (PST)
Date: Mon, 06 Jan 2003 16:45:04 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp@gnu.org
Message-id: <NBBBJJODBJBNJFNIDDCNAEPIDDAA.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: urlstring testing/enhancement
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, 07 Jan 2003 00:45:29 -0000

I built urlstring testcases this weekend. Here are the test cases performed:
  URLStringTest.testBinaryBase64EncodeDecode ...
  URLStringTest.testStringVersion ...
  URLStringTest.testTypicalUrlEncodeDecode ...
  URLStringTest.testTypicalTextBase64EncodeDecode ...
  URLStringTest.testSimpleTextBase64EncodeDecode ...
  URLStringTest.testComplexTextBase64EncodeDecode ...
  URLStringTest.testPaddingPerfect ...
  URLStringTest.testPadding1Short ...
  URLStringTest.testPadding2Short ...

I also added Base64 functions that take std::string arguments for the encode
output and the decode input.  I don't know where the line is supposed to be
relating to string usage as I see most of common c++ is char* based, but
there seems to be std::string usage in some classes.  personally I like
having it as an overload option.  I can post diffs showing the new functions
if they are wanted.

,Chad




From MAILER-DAEMON Wed Jan 08 01:13:36 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwvL-0005wE-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:49:55 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Va8C-0006xz-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:29:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Va8B-0006xU-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:29:40 -0500
Received: from malkav.cac.washington.edu ([140.142.107.26])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Va8A-0006wF-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:29:38 -0500
Received: from nosferatu.kriln.com
	(evrtwa1-ar1-4-47-235-208.evrtwa1.dsl-verizon.net [4.47.235.208])
	by malkav.cac.washington.edu (Postfix) with ESMTP
	id 8D021CF305; Mon,  6 Jan 2003 01:22:53 -0800 (PST)
Received: by nosferatu.kriln.com (Postfix, from userid 1000)
	id A021E58F5; Mon,  6 Jan 2003 16:33:49 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by nosferatu.kriln.com (Postfix) with ESMTP
	id 9AD7D5507; Mon,  6 Jan 2003 16:33:49 +0000 (GMT)
Date: Mon, 6 Jan 2003 16:33:49 +0000 (GMT)
From: Jeremy Noetzelman <jjn@kriln.com>
To: Federico Montesino Pouzols <fedemp@altern.org>
In-Reply-To: <20030106161441.GE4098@bulbasaur.rediris.es>
Message-ID: <20030106163305.X180-100000@nosferatu.kriln.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bug-commoncpp@gnu.org
Subject: Re: Non Threaded use of TCPSocket with select/poll?
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, 06 Jan 2003 16:29:41 -0000

My point is I want a single thread for the entire application.  Not two,
not more than two.  One.  It doesn't seem that CommonC++ supports such an
application without a fair amount of work.  Please correct me if I'm wrong
though.

J

On Mon, 6 Jan 2003, Federico Montesino Pouzols wrote:

>
> 	If you only want a limited number of threads and to simulate
> concurrency through select/poll, I think the SocketPort and
> SocketService classes are the most adequate classes in Common
> C++. There is a tcpservice demo that shows how to use them.
>
> On Fri, Jan 03, 2003 at 08:26:11PM +0000, Jeremy Noetzelman wrote:
> > I'm more concerned about having a proper select polling loop for the
> > server socket ... I'm less concerned about the client connection sockets.
> >
> > On Fri, 3 Jan 2003, Albert Strasheim wrote:
> >
> > > Hello,
> > >
> > > >From the Common C++ documentation for tcpstream (not TCPStream):
> > >
> > > A more natural C++ "tcpstream" class for use by non-threaded
> > > applications. C++ "fstream" style tcpstream class.
> > >
> > > I don't know if this is what you want?
> > >
> > > Cheers,
> > >
> > > Albert
> > >
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>




From MAILER-DAEMON Wed Jan 08 01:13:41 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwvL-0005wF-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:49:55 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VaAe-0001XK-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:32:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VaAa-0001Lv-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:32:10 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VaAa-0001KO-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:32:08 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18VaBD-0002KS-00; Mon, 06 Jan 2003 17:32:47 +0100
Date: Mon, 6 Jan 2003 17:32:47 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20030106163246.GG4098@bulbasaur.rediris.es>
Mail-Followup-To: David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org,
	Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
References: <20030103214523.GP887@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030103214523.GP887@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: doxygen @short directive in comments
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, 06 Jan 2003 16:32:13 -0000


	Um, yes this should be fixed. Another pending issue with the
doxygen doc is that, as reported sometime ago, ost::Exception does not
appear in it. This is because there is a specific doc/cc++/config.h
for doxygen which only defines a few configuration constants. Should
not we remove this file and simply use the config.h generated by
configure?

On Fri, Jan 03, 2003 at 11:45:23PM +0200, Albert Strasheim wrote:
> Hello,
> 
> All the classes in Common C++ are documented as follows (MutexCounter 
> in thread.h used as example):
> 
> /**
>  * The Mutex Counter is a counter variable which can safely be incremented
>  * or decremented by multiple threads.  A Mutex is used to protect access
>  * to the counter variable (an integer).  An initial value can be specified 
>  * for the counter, and it can be manipulated with the ++ and -- operators.
>  * 
>  * @author David Sugar <dyfet@ostel.com>
>  * @short Thread protected integer counter.
>  */
> class CCXX_CLASS_EXPORT MutexCounter : public Mutex
> {
> ...
> };
> 
> This is wrong. The problem is the position of the @short directive. 
> @short should be at the top of the class description, not the bottom, 
> e.g.:
> 
> /**
>  * @short Empty class.
>  *
>  * Class A is an empty class. Be happy.
>  *
>  * @author Albert Strasheim
>  */
> 
> This generates the proper HTML in doxygen -- you'll see that all the 
> current class descriptions currently don't read too well, since the 
> first sentence of the description, and the @short sentence are being 
> used for the description of the class that is placed at the top of the 
> generated page.
> 
> Cheers,
> 
> Albert
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Wed Jan 08 01:14:42 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Vwxb-00067V-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:52:15 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Vhry-0005op-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 19:45:26 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Vhri-0005X1-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 19:45:13 -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 18Vhrd-0005Sx-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 19:45:05 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8B00ECXJF34L@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Mon, 06 Jan 2003 16:45:04 -0800 (PST)
Date: Mon, 06 Jan 2003 16:45:04 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp@gnu.org
Message-id: <NBBBJJODBJBNJFNIDDCNOEPHDDAA.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: multipart/mixed; boundary="Boundary_(ID_hqJKFSV3GZPtjK01TvKVMw)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Subject: commconcpp2 changes to date.cpp
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, 07 Jan 2003 00:45:27 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_hqJKFSV3GZPtjK01TvKVMw)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

The recent changes to date.cpp broke the library under MSVC 6.0 on the
following:

  nyear = int(trunc(i));
  nmonth = int(trunc(j));
  nday = int(trunc(k));

I removed the trunc() function, and wondered if it was redundant anyway?
since the int() should suffice.

I also wrote a test suite for the date class (figured what better way to
determine if trunc() was necessary, and it needed to be done anyway) The
following are the test cases, and I'll save the code fore release with the
test suite:

  DateTest.testSimpleGets ...
  DateTest.testSimpleSets ...
  DateTest.testIsValid ...
  DateTest.testGetDate_String ...
  DateTest.testGetDate_time_t ...
  DateTest.testGeteDate_struct_tm ...
  DateTest.testOperations ...

and implemented a functions that were defined in the class but not
implemented (linker errors).  I also re-arranged some of the related methods
to avoid duplicate code.  I've attached diffs showing what was changed. here
is a summary:

date.cpp
- added test fixture for the Date class and fixed/enhanced.
- implemented missing tm* Date::getDate(tm*) function declared in
  class but not in implementation. took the liberty to make it
  also return a time_t instead of tm* in addition to filling the
  provided tm structure.
- simplified time_t Date::getDate(void) to use the above function.
- changed setDate parameter to const and placed (char*) in calls to Number.
setDate's use of Number seems to guarantee constness, but I don't know if
Number itself does. hopefully these casts can be removed someday.

email me with questions and comments.

,Chad

--Boundary_(ID_hqJKFSV3GZPtjK01TvKVMw)
Content-type: application/octet-stream; name=date_cpp.diff
Content-transfer-encoding: 7bit
Content-disposition: attachment; filename=date_cpp.diff

Index: date.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/date.cpp,v
retrieving revision 1.4.2.5
diff -u -r1.4.2.5 date.cpp
--- date.cpp	6 Jan 2003 15:04:32 -0000	1.4.2.5
+++ date.cpp	7 Jan 2003 00:32:38 -0000
@@ -86,12 +86,12 @@
 	setDate(str, size);
 }
 
-void Date::setDate(char *str, size_t size)
+void Date::setDate(const char *str, size_t size)
 {
 	time_t now;
 	struct tm *dt;
 	int year;
-	char *md;
+	const char *md;
 
 	if(!size)
 		size = strlen(str);
@@ -107,18 +107,18 @@
 	{
 		time(&now);
 		dt = localtime(&now);
-		Number nyear(str, 2);
+		Number nyear((char*)str, 2);
 		year = ((dt->tm_year + 1900) / 100) * 100 + nyear();
 		md = str + 2;
 	}
 	else
 	{
-		Number nyear(str, 4);
+		Number nyear((char*)str, 4);
 		year = nyear();
 		md = str + 4;
 	}
-	Number nmonth(md, 2);
-	Number nday(md + 2, 2);
+	Number nmonth((char*)md, 2);
+	Number nday((char*)md + 2, 2);
 	toJulian(year, nmonth(), nday());
 }
 
@@ -140,20 +140,26 @@
 	return buf;
 }
 
-time_t Date::getDate(void)
+time_t Date::getDate(tm* dt)
 {
 	char buf[9];
-	struct tm dt;
-	memset(&dt, 0, sizeof(dt));
+	memset(dt, 0, sizeof(tm));
 	fromJulian(buf);
 	Number nyear(buf, 4);
 	Number nmonth(buf + 4, 2);
 	Number nday(buf + 6, 2);
 	
-	dt.tm_year = nyear() - 1900;
-	dt.tm_mon = nmonth() - 1;
-	dt.tm_mday = nday();
-	return mktime(&dt);
+	dt->tm_year = nyear() - 1900;
+	dt->tm_mon = nmonth() - 1;
+	dt->tm_mday = nday();
+
+	return mktime(dt); // to fill in day of week etc.
+}
+
+time_t Date::getDate(void)
+{
+	struct tm dt;
+	return getDate(&dt);
 }
 
 int Date::getYear(void)
@@ -303,9 +309,9 @@
 	l = int(j/11);
 	j = j+2-12*l;
 	i = 100*(n - 49) + i + l;
-	nyear = int(trunc(i));
-	nmonth = int(trunc(j));
-	nday = int(trunc(k));
+	nyear = int(i);
+	nmonth = int(j);
+	nday = int(k);
 	
 	buffer[8] = '\0';
 }

--Boundary_(ID_hqJKFSV3GZPtjK01TvKVMw)
Content-type: application/octet-stream; name=numbers_h.diff
Content-transfer-encoding: 7bit
Content-disposition: attachment; filename=numbers_h.diff

Index: numbers.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/numbers.h,v
retrieving revision 1.2.2.4
diff -u -r1.2.2.4 numbers.h
--- numbers.h	18 Nov 2002 20:18:38 -0000	1.2.2.4
+++ numbers.h	7 Jan 2003 00:34:16 -0000
@@ -156,7 +156,7 @@
 	Date(time_t tm);
 	Date(tm *dt);
 	Date(char *str, size_t size = 0);
-	Date(int year, unsigned month, unsigned day);	
+	Date(int year, unsigned month, unsigned day);
 	Date();
 
 	int getYear(void);
@@ -165,9 +165,9 @@
 	unsigned getDayOfWeek(void);
 	char *getDate(char *buffer);
 	time_t getDate(void);
+	time_t getDate(tm *buf);
 	long getValue(void);
-	tm *getDate(tm *buf);
-	void setDate(char *str, size_t size = 0);
+	void setDate(const char *str, size_t size = 0);
 	bool isValid(void);
 
 	friend Date operator+(Date &date, long val);

--Boundary_(ID_hqJKFSV3GZPtjK01TvKVMw)--



From MAILER-DAEMON Wed Jan 08 01:50:51 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwvD-0005vv-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:49:47 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Va17-0001s4-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:22:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VZtm-0007PC-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:14:47 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VZtY-0007My-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:14:32 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18VZuA-0002Jd-00; Mon, 06 Jan 2003 17:15:10 +0100
Date: Mon, 6 Jan 2003 17:15:05 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Jeremy Noetzelman <jjn@kriln.com>
Message-ID: <20030106161441.GE4098@bulbasaur.rediris.es>
Mail-Followup-To: Jeremy Noetzelman <jjn@kriln.com>,
	Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20030103201744.GN887@dogbert.sdsl.sun.ac.za>
	<20030103202530.S180-100000@nosferatu.kriln.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030103202530.S180-100000@nosferatu.kriln.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Non Threaded use of TCPSocket with select/poll?
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, 06 Jan 2003 16:23:14 -0000


	If you only want a limited number of threads and to simulate
concurrency through select/poll, I think the SocketPort and
SocketService classes are the most adequate classes in Common
C++. There is a tcpservice demo that shows how to use them.

On Fri, Jan 03, 2003 at 08:26:11PM +0000, Jeremy Noetzelman wrote:
> I'm more concerned about having a proper select polling loop for the
> server socket ... I'm less concerned about the client connection sockets.
> 
> On Fri, 3 Jan 2003, Albert Strasheim wrote:
> 
> > Hello,
> >
> > >From the Common C++ documentation for tcpstream (not TCPStream):
> >
> > A more natural C++ "tcpstream" class for use by non-threaded
> > applications. C++ "fstream" style tcpstream class.
> >
> > I don't know if this is what you want?
> >
> > Cheers,
> >
> > Albert
> >
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Wed Jan 08 01:51:39 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwtD-0005pz-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:47:43 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VZMR-0000r4-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 10:40:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VYrs-0005He-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 10:08:46 -0500
Received: from mail08a.verio.de ([213.198.55.86])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18VYqK-00056x-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 10:07:09 -0500
Received: from www.hillier.de (213.198.5.214)
	by mail08a.verio.de (RS ver 1.0.63s) with SMTP id 04323324
	for <bug-commoncpp@gnu.org>; Mon,  6 Jan 2003 16:06:56 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by gernot.hillier.de (Postfix) with ESMTP id 03F067572A
	for <bug-commoncpp@gnu.org>; Mon,  6 Jan 2003 15:58:51 +0100 (CET)
Received: by gernot.hillier.de (Postfix, from userid 501)
	id 37AFC31DC6; Mon,  6 Jan 2003 15:58:46 +0100 (CET)
Content-Type: text/plain;
  charset="us-ascii"
From: Gernot Hillier <gernot@hillier.de>
To: <bug-commoncpp@gnu.org>
Date: Mon, 6 Jan 2003 15:58:40 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301061558.46338.gernot@hillier.de>
X-Virus-Scanned: by AMaViS 0.3.12pre8
X-Loop-Detect: 1
Subject: crash in detached thread in ThreadImpl::ThreadDestructor
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, 06 Jan 2003 15:49:09 -0000

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

Hi!

Short: I use a detached thread which does "delete this" in its final()-me=
thod.=20
It crashes when calling terminate() from another thread.

Long:=20

I have a base class BaseClass implementing a CommonC++-Thread. It has a=20
final()-method which does "delete this" and a run() method which will do =
some=20
work. BaseClass::~BaseClass() calls terminate() like told in the docs.

I have a derived "class DerivedClass: public BaseClass". It reimplements=20
run(). This run() will call BaseClass::run() somewhere in the middle.

An object is created from DerivedClass which is started with detach(). Th=
is=20
object is later on called to terminate().=20

This will cause a crash:

0x400adb70 in ost::ThreadImpl::ThreadDestructor(ost::Thread*) (th=3D0x815=
7720)=20
at thread.cpp:878
878             if (th->priv->_type =3D=3D threadTypeDummy)
(gdb) bt
#0  0x400adb70 in ost::ThreadImpl::ThreadDestructor(ost::Thread*)=20
(th=3D0x8157720) at thread.cpp:878
#1  0x400accfa in ccxx_thread_destructor (arg=3D0x8157720) at thread.cpp:=
884
#2  0x4003cb16 in __pthread_destroy_specifics () from /lib/libpthread.so.=
0
#3  0x40038734 in __pthread_do_exit () from /lib/libpthread.so.0
#4  0x4003ba61 in pthread_handle_sigcancel () from /lib/libpthread.so.0
#5  <signal handler called>
#6  0x40304d01 in nanosleep () from /lib/libc.so.6
#7  0x4003e58c in nanosleep () from /lib/libpthread.so.0
#8  0x400afb66 in ost::Thread::sleep(unsigned long) (timeout=3D100) at=20
friends.cpp:134
#9  0x08067a56 in DerivedClass::run() (this=3D0x8157720) at idlescript.cp=
p:39
#10 0x400adb06 in ost::ThreadImpl::ThreadExecHandler(ost::Thread*)=20
(th=3D0x8157720) at thread.cpp:865
#11 0x400acd20 in ccxx_exec_handler (th=3D0x8157720) at thread.cpp:889
#12 0x400391b0 in pthread_start_thread () from /lib/libpthread.so.0
#13 0x4003922f in pthread_start_thread_event () from /lib/libpthread.so.0

Log output shows me that the thread object gets deleted *before* this cra=
sh.=20
The thread seems to be still in run() (see #9) but its object is already=20
deleted. So the cause for the crash is clear.=20

I don't understand how this can happen - especially why final() could be=20
called but run() is still active?!

cancelMode is set to cancelDeferred.

Can someone perhaps give me some idea where to look for this bug? I'm not=
 very=20
well experienced with libpthread unfortunately, so I only know what is to=
ld=20
to me in the Docs of CommonC++.

I can work around this by using some flag which is checked in run(). If I=
 just =20
set this flag from outside and don't use terminate(), everything is fine.=
=20

Perhaps some of you have some idea??

TIA!

- --=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)

iD8DBQE+GZmik997/GGeSeIRAqrOAKCol8vbUYolIq7RJ4DMwvStefD7sgCfaB9I
rLjEU/OO+oQClxlNozv7REg=3D
=3D6kxu
-----END PGP SIGNATURE-----



From MAILER-DAEMON Wed Jan 08 02:22:43 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwvG-0005w1-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:49:50 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Va2j-0002x7-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:24:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Va2M-0002Wd-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:23:41 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Va1p-00029G-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:23:05 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18Va2T-0002K0-00; Mon, 06 Jan 2003 17:23:45 +0100
Date: Mon, 6 Jan 2003 17:23:45 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ying-Chieh Liao <ijliao@csie.nctu.edu.tw>
Message-ID: <20030106162345.GF4098@bulbasaur.rediris.es>
Mail-Followup-To: Ying-Chieh Liao <ijliao@csie.nctu.edu.tw>,
	bug-commoncpp@gnu.org
References: <200301030815.32759.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301030815.32759.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Fwd: FreeBSD ports : commoncpp
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, 06 Jan 2003 16:24:20 -0000


	Hi, could you try commoncpp2 1.0.7 or, even better, the CVS
version. We fixed the issue with nanosleep some weeks ago, and recent
releases should build cleanly on FreeBSD. Note however that there may
be problems when building with gcc 3.x.

On Fri, Jan 03, 2003 at 08:15:32AM -0500, David Sugar wrote:
> Let's see what the list thinks of it, since we do want to make sure the next 
> point release is bsd clean...
> 
> ----------  Forwarded Message  ----------
> 
> Subject: FreeBSD ports : commoncpp
> Date: Fri, 3 Jan 2003 15:51:38 +0800
> From: Ying-Chieh Liao <ijliao@csie.nctu.edu.tw>
> To: dyfet@gnu.org
> Cc: Ying-Chieh Liao <ijliao@csie.nctu.edu.tw>
> 
> what do you think about pr/44205 ?
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/44205
> --
> char*p="char*p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
> 					-- Anonymous
> 
> -------------------------------------------------------
> 


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




From MAILER-DAEMON Wed Jan 08 02:34:38 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwvM-0005wK-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:49:56 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VaF6-0006ob-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:36:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VaF4-0006nr-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:36:47 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VaF3-0006nn-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 11:36:46 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18VaFk-0002Kg-00; Mon, 06 Jan 2003 17:37:28 +0100
Date: Mon, 6 Jan 2003 17:37:28 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Roee Friedman <roee_fr@netvision.net.il>
Message-ID: <20030106163727.GH4098@bulbasaur.rediris.es>
Mail-Followup-To: Roee Friedman <roee_fr@netvision.net.il>,
	bug-commoncpp@gnu.org
References: <200301031010.17837.roee_fr@netvision.net.il>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301031010.17837.roee_fr@netvision.net.il>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Included files order
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, 06 Jan 2003 16:36:48 -0000


	It may have to do with some configuration symbols being
wrongly defind/undefined. What is your system configuration?

On Fri, Jan 03, 2003 at 10:10:17AM +0200, Roee Friedman wrote:
> Hello!
> I have seen the problem discussed about a year ago, but it still not fixed.
> I am using CC++ 2 (1.0.7).
> It seems that still the inclusion of <fstream> or <iostream> before 
> <cc++/socket.h> breaks the compilation with error:
> 
> In file included from /usr/local/include/cc++/socket.h:54,
>                  from MailServer.h:3,
>                  from mailclin.h:10,
>                  from mailclin.cpp:1:
> /usr/local/include/cc++/thread.h:320: syntax error before `;'
> 
> the order of inclusion is:
> 
> #include <fstream>
> #include <iostream>
> #include <cstdio>
> #include <new>
> 
> #include "MailServer.h"  // <-- This file includes <cc++/socket.h>
> 
> In order to compile the project, I either have to move the last include to be 
> the first or include <cc++/socket.h> first.
> 
> Roee
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Wed Jan 08 02:38:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WAdm-0002Zo-00
	for mharc-bug-commoncpp@gnu.org; Wed, 08 Jan 2003 02:28:42 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WAYt-0000pN-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 02:23:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18W8i6-0006tx-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 00:25:33 -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 18W8KJ-0000bF-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 00:00:27 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h085Y4e09151;
	Wed, 8 Jan 2003 00:34:04 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>,
   Gernot Hillier <ghillie@suse.de>
Date: Wed, 8 Jan 2003 00:04:15 -0500
User-Agent: KMail/1.4.3
References: <200301041233.27796.ghillie@suse.de>
	<20030106190855.GI4098@bulbasaur.rediris.es>
In-Reply-To: <20030106190855.GI4098@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301080004.15449.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: [BUG] [PATCH] Buffer Overflow in Keydata::loadPrefix()
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, 08 Jan 2003 07:28:40 -0000

I think this is fine.

On Monday 06 January 2003 14:08, Federico Montesino Pouzols wrote:
> I would say that replacing strcp with strncpy here will
> prevent some crashes. Is there any objection to include this patch
> upstream?
>
> On Sat, Jan 04, 2003 at 12:33:27PM +0100, Gernot Hillier wrote:
> > Hi!
> >
> > I stumbled over a very dangerous code part in CommonC++ in the KeyDat=
a
> > implementation:
> >
> > void Keydata::loadPrefix(const char *pre, const char *keypath, const =
char
> > *environment)
> > {
> > [...]
> >         if(*keypath =3D=3D '~')
> >         {
> >                 prefix =3D getenv("HOME");
> >                 strcpy(path, prefix);
> >                 strcat(path, "/.");
> >                 ++keypath;
> >         }
> > [...]
> >
> > This is a classical buffer overflow (use a environment variable, rely=
 on
> > its length and copy it to an internal buffer).
> >
> > I tried to fix it for the time being - but I don't actually know the
> > class as I don't use it. Please triple-check my fixes - they're untes=
ted
> > and I don't have read the complete code of keydata.cpp!
> >
> > So please see my patch just as a suggestion. I'll attach it...
> >
> > --
> > Bye,
> >
> > Gernot
> >
> >
> > _______________________________________________
> > 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 MAILER-DAEMON Wed Jan 08 04:45:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwwR-00061i-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:51:03 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VdSk-0007rY-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 15:03:06 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VdSf-0007ef-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 15:03:05 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VdSd-0007Yo-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 15:03:00 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18VdSm-0002RD-00; Mon, 06 Jan 2003 21:03:08 +0100
Date: Mon, 6 Jan 2003 21:03:08 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030106200308.GJ4098@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>, bug-commoncpp@gnu.org
References: <NBBBJJODBJBNJFNIDDCNCEOHDDAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNCEOHDDAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: bugs in CRC32
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, 06 Jan 2003 20:03:06 -0000


	As for the algorithm results, either the cc++ implementation
or the two programs appear to be wrong. However, the three tests of
the crc32 demo are the official examples of the ATM standard. Do those
two programs you mention provide the result expected in the demo for
the three tests?  They may be using a different generator polynomial.

On Thu, Jan 02, 2003 at 05:59:38PM -0800, Chad Yates wrote:
> I have discovered and fixed some bugs in the CRC32Digest class while
> developing test cases for the digest classes.
> 
> 1) the virtual function overflow was not being called (at least on win32) so
> I changed the argument and return type to int (as in the other digest
> classes)...
> 
> 2) the lookup table was not using "reflection" during its initialization
> (apparently this is a part of the CRC32 standard implementation) so I added
> a reflect function and changed (replaced) the lookup code to use it. I
> commented out the old code so you can see it in the diff.
> 
> 3) I moved the crc32 = 0 from the constructor to the initDigest method so it
> is reset both during construction and reseting.
> 
> 4) I removed the crc32 = ~crc_reg in the overload method and moved it to
> both the getDigest and strDigest methods as a minor performance improvement
> (won't be re-computed for every octet in the stream)
> 
> finally, I checked the output agains two programs available on the net, and
> it matches both, however the existing CRC32 demo program now reports all
> failures.  I suspect that the tests were not valid to begin with, but if
> anyone would like to verify this (or comment) please do so.
> 
> ,chad
> 
> Index: digest.h
> ===================================================================
> RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/digest.h,v
> retrieving revision 1.10
> diff -r1.10 digest.h
> 204c204
> <    unsigned char overflow(unsigned char octet);
> ---
> >    int overflow(int octet);
> 207c207,209
> <
> ---
> >
> >    unsigned long reflect(unsigned long ref, unsigned char ch);
> >
> 
> Index: digest.cpp
> ===================================================================
> RCS file: /cvsroot/commoncpp/commoncpp2/src/digest.cpp,v
> retrieving revision 1.4
> diff -r1.4 digest.cpp
> 145d144
> <    crc32 = 0;
> 161,172c160,182
> <    for (i = 0; i < 256; i++)
> <    {
> <       crc = ( (unsigned long) i << 24 );
> <       for (j = 0; j < 8; j++)
> <       {
> <          if (crc & 0x80000000)
> <             crc = (crc << 1) ^ POLYNOMIAL;
> <          else
> <             crc <<= 1;
> <       }
> <       crc_table[i] = crc;
> <    }
> ---
> >   for(i = 0; i <= 0xFF; i++)
> >   {
> >     crc=reflect(i, 8) << 24;
> >     for (j = 0; j < 8; j++)
> >       crc = (crc << 1) ^ (crc & (1 << 31) ? POLYNOMIAL : 0);
> >     crc_table[i] = reflect(crc, 32);
> >   }
> >   /* old loop without reflection
> >   for (i = 0; i < 256; i++)
> >   {
> >     crc = ( (unsigned long) i << 24 );
> >     for (j = 0; j < 8; j++)
> >     {
> >       if (crc & 0x80000000)
> >         crc = (crc << 1) ^ POLYNOMIAL;
> >       else
> >         crc <<= 1;
> >     }
> >     crc_table[i] = crc;
> >   }
> >   */
> >
> >    crc32 = 0;
> 175c185,201
> < unsigned char CRC32Digest::overflow(unsigned char octet)
> ---
> > unsigned long CRC32Digest::reflect(unsigned long ref, unsigned char ch)
> > {
> >   unsigned long value = 0;
> >
> >   // Swap bit 0 for bit 7
> >   // bit 1 for bit 6, etc.
> >   for(int i = 1; i < (ch + 1); i++)
> >   {
> >     if(ref & 1)
> >       value |= 1 << (ch - i);
> >     ref >>= 1;
> >   }
> >
> >   return value;
> > }
> >
> > int CRC32Digest::overflow(int octet)
> 177,179c203,206
> <    crc_reg = crc_table[((crc_reg >> 24) ^ octet) & 0xFF] ^ (crc_reg << 8);
> <    crc32 = ~crc_reg;
> <
> ---
> >    //crc_reg = crc_table[((crc_reg >> 24) ^ octet) & 0xFF] ^ (crc_reg <<
> 8);
> >        crc_reg = (crc_reg >> 8) ^ crc_table[(crc_reg & 0xFF) ^ octet];
> >    //crc32 = ~crc_reg; deferred calculation until later rather than for
> every
> byte
> >
> 184a212
> >    crc32 = ~crc_reg; // finalize crc32 before exporting
> 198a227
> >    crc32 = ~crc_reg;  // finalize crc32 before exporting
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Wed Jan 08 05:29:48 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WDSL-0006JM-00
	for mharc-bug-commoncpp@gnu.org; Wed, 08 Jan 2003 05:29:05 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WDS3-0005uS-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 05:28:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WDRB-0005IJ-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 05:28:24 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WDRB-0005HC-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 05:27:53 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18WDRo-00013z-00; Wed, 08 Jan 2003 11:28:32 +0100
Date: Wed, 8 Jan 2003 11:28:21 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ian Gough <igough@istop.com>
Message-ID: <20030108102819.GB252@bulbasaur.rediris.es>
Mail-Followup-To: Ian Gough <igough@istop.com>, bug-commoncpp@gnu.org
References: <NDBBIOGMDMIANEEKGGEGKEGODLAA.igough@istop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NDBBIOGMDMIANEEKGGEGKEGODLAA.igough@istop.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Process class is not exported under Win32
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: Wed, 08 Jan 2003 10:28:55 -0000


	Yes, this is a bug in 1.0.7. It was already fixed in CVS for
the next release, 1.0.8.

On Tue, Jan 07, 2003 at 09:35:09PM -0500, Ian Gough wrote:
> Please forgive if this problem has already been reported.
> 
> cc++ version 1.07
> 
> It would seem that the Process.h is missing the statement:
> 
>   class CCXX_CLASS_EXPORT Process;
> 
> so that the Process class is visible in the windows import library.
> 
> Symptoms are that any program that uses any of the Win32 supported methods
> such as spawn fails to link due to an unresolved reference.

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




From MAILER-DAEMON Wed Jan 08 05:31:27 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwwH-00060p-00
	for mharc-bug-commoncpp@gnu.org; Tue, 07 Jan 2003 11:50:53 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Vcbh-0005QI-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 14:08:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Vcbf-0005Md-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 14:08:17 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Vcbf-0005Lq-00
	for bug-commoncpp@gnu.org; Mon, 06 Jan 2003 14:08:15 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18VccK-0002Q8-00; Mon, 06 Jan 2003 20:08:56 +0100
Date: Mon, 6 Jan 2003 20:08:56 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Gernot Hillier <ghillie@suse.de>
Message-ID: <20030106190855.GI4098@bulbasaur.rediris.es>
Mail-Followup-To: Gernot Hillier <ghillie@suse.de>, bug-commoncpp@gnu.org
References: <200301041233.27796.ghillie@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301041233.27796.ghillie@suse.de>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: [BUG] [PATCH] Buffer Overflow in Keydata::loadPrefix()
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, 06 Jan 2003 19:08:18 -0000


	I would say that replacing strcp with strncpy here will
prevent some crashes. Is there any objection to include this patch
upstream?

On Sat, Jan 04, 2003 at 12:33:27PM +0100, Gernot Hillier wrote:
> Hi!
> 
> I stumbled over a very dangerous code part in CommonC++ in the KeyData 
> implementation:
> 
> void Keydata::loadPrefix(const char *pre, const char *keypath, const char 
> *environment)
> {
> [...]
>         if(*keypath == '~')
>         {
>                 prefix = getenv("HOME");
>                 strcpy(path, prefix); 
>                 strcat(path, "/.");
>                 ++keypath;
>         }
> [...]
> 
> This is a classical buffer overflow (use a environment variable, rely on its 
> length and copy it to an internal buffer).
> 
> I tried to fix it for the time being - but I don't actually know the class as 
> I don't use it. Please triple-check my fixes - they're untested and I don't 
> have read the complete code of keydata.cpp! 
> 
> So please see my patch just as a suggestion. I'll attach it...
> 
> -- 
> Bye,
> 
> Gernot


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




From MAILER-DAEMON Wed Jan 08 06:13:29 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WE7b-0004s5-00
	for mharc-bug-commoncpp@gnu.org; Wed, 08 Jan 2003 06:11:43 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WE7W-0004li-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 06:11:38 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WE77-0004Uq-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 06:11:15 -0500
Received: from ns2.envia-tel.net ([193.98.112.146])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WE6Q-0003NY-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 06:10:30 -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 h08BASB4007163
	for <bug-commoncpp@gnu.org>; Wed, 8 Jan 2003 12:10:28 +0100
Received: by mailserver.wige-data.de with Internet Mail Service (5.5.2653.19)
	id <CFLZCV1C>; Wed, 8 Jan 2003 12:10:22 +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 CFLZCV1A; Wed, 8 Jan 2003 12:10:10 +0100
From: taraben.a@wige-data.de
To: bug-commoncpp@gnu.org
Message-ID: <3E1C0712.8080404@wige-data.de>
Date: Wed, 08 Jan 2003 12:10:10 +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
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: define HAVE_EXCEPTION makes sense ???
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, 08 Jan 2003 11:11:41 -0000

Hello,

I wonder what for is the define HAVE_EXCEPTION.
Undefine this the code wont compile properly. Because some classes trow 
exceptions and need the <exception.h>.

Thanks for pointing out.

Adib.



From MAILER-DAEMON Wed Jan 08 07:55:39 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WFj5-0001vG-00
	for mharc-bug-commoncpp@gnu.org; Wed, 08 Jan 2003 07:54:31 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WFA7-0004Lm-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 07:18:23 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WF83-0003Ol-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 07:16:46 -0500
Received: from sphere.barak.net.il ([212.150.48.98])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WEvd-0000DO-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 07:03:25 -0500
Received: from [10.100.0.13] ([62.90.161.92]) by sphere.barak.net.il
	b8419dca4a53cb56ee7ae4510b91963a)
	<20030108120021.MTTD11154.sphere@[62.90.161.92]>
	for <bug-commoncpp@gnu.org>; Wed, 8 Jan 2003 14:00:21 +0200
From: Ittay Freiman <ittay@qlusters.com>
To: bug-commoncpp@gnu.org
Content-Type: text/plain
Organization: Qlusters Inc.
Message-Id: <1042027341.1082.18.camel@rum>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.0 (1.2.0-3) 
Date: 08 Jan 2003 14:02:22 +0200
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 08 Jan 2003 07:54:28 -0500
Subject: Thread::detach bug
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, 08 Jan 2003 12:25:11 -0000

if i call Thread::detach, the thread is created in joinable mode, and a
line after pthread_detach is called. however, if the threads are short
lived, or the system is loaded, this line may execute after the thread
has finished its run, destroyed itself (in final(), as recommended in
the documentation) and therefore its resources are lost.

-- 
Ittay Freiman <ittay@qlusters.com>
Qlusters Inc.




From MAILER-DAEMON Wed Jan 08 07:57:48 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WFj4-0001vD-00
	for mharc-bug-commoncpp@gnu.org; Wed, 08 Jan 2003 07:54:30 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WAoV-0005gT-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 02:39:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WADH-00048H-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 02:01:22 -0500
Received: from adsl-161-92.barak.net.il ([62.90.161.92]
	helo=hirame.qlusters.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18WA6P-00025l-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 01:54:13 -0500
Received: from [10.100.0.13] ([10.100.0.13])
	by hirame.qlusters (8.10.2/8.10.2) with ESMTP id h086lOe26227
	for <bug-commoncpp@gnu.org>; Wed, 8 Jan 2003 08:47:24 +0200
From: Ittay Freiman <ittay@qlusters.com>
To: bug-commoncpp@gnu.org
Content-Type: text/plain
Organization: Qlusters Inc.
Message-Id: <1042008781.5628.10.camel@rum>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.0 (1.2.0-3) 
Date: 08 Jan 2003 08:53:01 +0200
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 08 Jan 2003 07:54:27 -0500
Subject: Thread bugs
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, 08 Jan 2003 08:18:30 -0000

1. according to the documentation, one should do 'delete this' in
final(). however, in close() there is a check on 'priv' after calling
final(). when an application has many threads opening and closing, this
memory can already be allocated to some other object, thus this check
will (has for us) fail. 

2. in terminate() a call to pthread_join() is made. according to the man
pages, this call is illegal for a detached thread. it does fail
sometimes for us.

ittay
-- 
Ittay Freiman <ittay@qlusters.com>
Qlusters Inc.




From MAILER-DAEMON Wed Jan 08 08:21:51 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WG88-0007cJ-00
	for mharc-bug-commoncpp@gnu.org; Wed, 08 Jan 2003 08:20:24 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WG1h-00045J-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 08:13:45 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WG0o-0003IP-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 08:13:22 -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 18WG0a-00032w-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 08:12:36 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h08DkHe12343;
	Wed, 8 Jan 2003 08:46:17 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: taraben.a@wige-data.de, bug-commoncpp@gnu.org
Date: Wed, 8 Jan 2003 08:16:34 -0500
User-Agent: KMail/1.4.3
References: <3E1C0712.8080404@wige-data.de>
In-Reply-To: <3E1C0712.8080404@wige-data.de>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301080816.34661.dyfet@ostel.com>
Subject: Re: define HAVE_EXCEPTION makes sense ???
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, 08 Jan 2003 13:20:23 -0000

At one time we built Common C++ so it could also work on broken libraries=
 that=20
did not have std/exception.  I suspect that this has become rare enough t=
hat=20
it has not been tested or used by anyone that way for a long time now...

On Wednesday 08 January 2003 06:10, taraben.a@wige-data.de wrote:
> Hello,
>
> I wonder what for is the define HAVE_EXCEPTION.
> Undefine this the code wont compile properly. Because some classes trow
> exceptions and need the <exception.h>.
>
> Thanks for pointing out.
>
> Adib.
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Wed Jan 08 08:39:04 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WGH4-0002bo-00
	for mharc-bug-commoncpp@gnu.org; Wed, 08 Jan 2003 08:29:38 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WGDk-0000Jt-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 08:26:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WG5o-0006Br-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 08:18:31 -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 18WG32-0004fL-00
	for bug-commoncpp@gnu.org; Wed, 08 Jan 2003 08:15:08 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h08Dmne12351;
	Wed, 8 Jan 2003 08:48:49 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>,
   Ian Gough <igough@istop.com>
Date: Wed, 8 Jan 2003 08:19:06 -0500
User-Agent: KMail/1.4.3
References: <NDBBIOGMDMIANEEKGGEGKEGODLAA.igough@istop.com>
	<20030108102819.GB252@bulbasaur.rediris.es>
In-Reply-To: <20030108102819.GB252@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301080819.06754.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: Process class is not exported under Win32
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, 08 Jan 2003 13:29:38 -0000

We have been a bit slow in getting 1.0.8 out because people have been fin=
ding=20
so many new issues that each need to be reviewed.  It is good that we now=
=20
have so many new people involved in Common C++ now and that many of the l=
ess=20
commonly used classes are finally getting thorough testing.=20

On Wednesday 08 January 2003 05:28, Federico Montesino Pouzols wrote:
> Yes, this is a bug in 1.0.7. It was already fixed in CVS for
> the next release, 1.0.8.
>
> On Tue, Jan 07, 2003 at 09:35:09PM -0500, Ian Gough wrote:
> > Please forgive if this problem has already been reported.
> >
> > cc++ version 1.07
> >
> > It would seem that the Process.h is missing the statement:
> >
> >   class CCXX_CLASS_EXPORT Process;
> >
> > so that the Process class is visible in the windows import library.
> >
> > Symptoms are that any program that uses any of the Win32 supported
> > methods such as spawn fails to link due to an unresolved reference.
> >
> > _______________________________________________
> > 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 MAILER-DAEMON Thu Jan 09 04:26:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WYwO-0007GZ-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:25:32 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WYvu-0006cn-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:25:02 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WYvY-0005vq-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:24:45 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WYvM-0005Gj-00; Thu, 09 Jan 2003 04:24:28 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18WYvs-00009d-00; Thu, 09 Jan 2003 10:25:00 +0100
Date: Thu, 9 Jan 2003 10:24:58 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20030109092453.GA313@bulbasaur.rediris.es>
Mail-Followup-To: David Sugar <dyfet@ostel.com>, ccrtp-devel@gnu.org,
	bug-commoncpp@gnu.org
References: <20030108112553.1663.qmail@sina.com>
	<200301080939.40354.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200301080939.40354.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: ccrtp-devel@gnu.org
cc: bug-commoncpp@gnu.org
Subject: Re: [Ccrtp-devel] ask--urgent
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: Thu, 09 Jan 2003 09:25:31 -0000


	Since this is a FAQ, I think we should add a more explicit
comment to OST_CCXX2_VERSION, as when an older version of cc++ is
found and it says "CommonC++ is always available from
ftp://ftp.gnu.org/gnu/commonc++/".

On Wed, Jan 08, 2003 at 09:39:40AM -0500, David Sugar wrote:
> You need to download and install GNU Common C++ before you can use ccrtp.
> 
> David
> 
> On Wednesday 08 January 2003 06:25, kungfuboxer wrote:
> > Dear Sir:
> >      I have download the ccRTP,and I want to build it,when I type
> > "./configure",it hints: loading cache ./config.cache
> > checking for a BSD compatible install... /usr/bin/install -c
> > checking whether build environment is sane... yes
> > checking whether make sets ${MAKE}... yes
> > checking for working aclocal... found
> > checking for working autoconf... found
> > checking for working automake... found
> > checking for working autoheader... found
> > checking for working makeinfo... found
> > checking for genorated automake files... found
> > checking whether to enable maintainer-specific portions of Makefiles... no
> > checking for ccgnu2-config... no
> > checking for commoncpp2 version >= 0.99.0... not found
> > *** The ccgnu2-config script installed by commoncpp2 0.99
> > *** or later could not be found.
> >
> >    Can you help with this problem?
> >    I'm expecting your answer!
> >
> >    Thanks!
> >           yours truly kungfuboxer
> >
> > ______________________________________
> >
> > ===================================================================
> > ??????????????????5M????????? ???????????? (http://vip.sina.com/sol_mail/promotion/pro_men.html)
> > ??????????????????????????????????? (http://classad.sina.com.cn/2shou/)
> > ÿ???1??????????????????????? (http://sms.sina.com.cn/act/beautyxmas.html)
> >
> >
> > _______________________________________________
> > Ccrtp-devel mailing list
> > Ccrtp-devel@gnu.org
> > http://mail.gnu.org/mailman/listinfo/ccrtp-devel
> 
> 
> 
> _______________________________________________
> Ccrtp-devel mailing list
> Ccrtp-devel@gnu.org
> http://mail.gnu.org/mailman/listinfo/ccrtp-devel



From MAILER-DAEMON Thu Jan 09 04:39:56 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WZ9v-0007Hj-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:39:31 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WZ9F-0005nE-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:38:49 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WZ7j-0003W8-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:37:17 -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 18WZ66-0002KK-00; Thu, 09 Jan 2003 04:35:34 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h09A9Ne23083;
	Thu, 9 Jan 2003 05:09:23 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>
Date: Thu, 9 Jan 2003 04:39:54 -0500
User-Agent: KMail/1.4.3
References: <20030108112553.1663.qmail@sina.com>
	<200301080939.40354.dyfet@ostel.com>
	<20030109092453.GA313@bulbasaur.rediris.es>
In-Reply-To: <20030109092453.GA313@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301090439.54932.dyfet@ostel.com>
cc: ccrtp-devel@gnu.org
cc: bug-commoncpp@gnu.org
Subject: Re: [Ccrtp-devel] ask--urgent
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, 09 Jan 2003 09:39:29 -0000

I think you are right...

On Thursday 09 January 2003 04:24, Federico Montesino Pouzols wrote:
> Since this is a FAQ, I think we should add a more explicit
> comment to OST_CCXX2_VERSION, as when an older version of cc++ is
> found and it says "CommonC++ is always available from
> ftp://ftp.gnu.org/gnu/commonc++/".
>
> On Wed, Jan 08, 2003 at 09:39:40AM -0500, David Sugar wrote:
> > You need to download and install GNU Common C++ before you can use cc=
rtp.
> >
> > David
> >
> > On Wednesday 08 January 2003 06:25, kungfuboxer wrote:
> > > Dear Sir:
> > >      I have download the ccRTP,and I want to build it,when I type
> > > "./configure",it hints: loading cache ./config.cache
> > > checking for a BSD compatible install... /usr/bin/install -c
> > > checking whether build environment is sane... yes
> > > checking whether make sets ${MAKE}... yes
> > > checking for working aclocal... found
> > > checking for working autoconf... found
> > > checking for working automake... found
> > > checking for working autoheader... found
> > > checking for working makeinfo... found
> > > checking for genorated automake files... found
> > > checking whether to enable maintainer-specific portions of Makefile=
s...
> > > no checking for ccgnu2-config... no
> > > checking for commoncpp2 version >=3D 0.99.0... not found
> > > *** The ccgnu2-config script installed by commoncpp2 0.99
> > > *** or later could not be found.
> > >
> > >    Can you help with this problem?
> > >    I'm expecting your answer!
> > >
> > >    Thanks!
> > >           yours truly kungfuboxer
> > >
> > > ______________________________________
> > >
> > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > ??????????????????5M????????? ????????????
> > > (http://vip.sina.com/sol_mail/promotion/pro_men.html)
> > > ??????????????????????????????????? (http://classad.sina.com.cn/2sh=
ou/)
> > > =FF???1???????????????????????
> > > (http://sms.sina.com.cn/act/beautyxmas.html)
> > >
> > >
> > > _______________________________________________
> > > Ccrtp-devel mailing list
> > > Ccrtp-devel@gnu.org
> > > http://mail.gnu.org/mailman/listinfo/ccrtp-devel
> >
> > _______________________________________________
> > Ccrtp-devel mailing list
> > Ccrtp-devel@gnu.org
> > http://mail.gnu.org/mailman/listinfo/ccrtp-devel




From MAILER-DAEMON Thu Jan 09 04:44:38 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WZDC-0002R9-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:42:54 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WZC7-0001CA-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:41:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WZBx-0000sQ-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:41:41 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WZB5-00086t-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:40:43 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18WZBn-0000AG-00; Thu, 09 Jan 2003 10:41:27 +0100
Date: Thu, 9 Jan 2003 10:41:27 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030109094126.GB313@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>, bug-commoncpp@gnu.org
References: <NBBBJJODBJBNJFNIDDCNIEPNDDAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNIEPNDDAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: commconcpp2 changes to date.cpp (copy)
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: Thu, 09 Jan 2003 09:42:52 -0000


	It seems that the list has been frozen for two or three days,
but I now see all the posts that you have reposted with '(copy)'
appended. In the meantime, the mail archives are working again, now
based on MHonArc. By the way, this new interface allows for searching
through the archives.

On Tue, Jan 07, 2003 at 12:25:31PM -0800, Chad Yates wrote:
> I just started recieving list messages again today.  It appears that my
> previous messages were lost, so I'm forwarding them again...
> 
> The recent changes to date.cpp broke the library under MSVC 6.0 on the
> following:
> 
>   nyear = int(trunc(i));
>   nmonth = int(trunc(j));
>   nday = int(trunc(k));
> 
> I removed the trunc() function, and wondered if it was redundant anyway?
> since the int() should suffice.
> 
> I also wrote a test suite for the date class (figured what better way to
> determine if trunc() was necessary, and it needed to be done anyway) The
> following are the test cases, and I'll save the code fore release with the
> test suite:
> 
>   DateTest.testSimpleGets ...
>   DateTest.testSimpleSets ...
>   DateTest.testIsValid ...
>   DateTest.testGetDate_String ...
>   DateTest.testGetDate_time_t ...
>   DateTest.testGeteDate_struct_tm ...
>   DateTest.testOperations ...
> 
> and implemented a functions that were defined in the class but not
> implemented (linker errors).  I also re-arranged some of the related methods
> to avoid duplicate code.  I've attached diffs showing what was changed. here
> is a summary:
> 
> date.cpp
> - added test fixture for the Date class and fixed/enhanced.
> - implemented missing tm* Date::getDate(tm*) function declared in
>   class but not in implementation. took the liberty to make it
>   also return a time_t instead of tm* in addition to filling the
>   provided tm structure.
> - simplified time_t Date::getDate(void) to use the above function.
> - changed setDate parameter to const and placed (char*) in calls to Number.
> setDate's use of Number seems to guarantee constness, but I don't know if
> Number itself does. hopefully these casts can be removed someday.
> 
> email me with questions and comments.
> 
> ,Chad



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




From MAILER-DAEMON Thu Jan 09 05:02:57 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WZUl-0003Xy-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:01:03 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WZUf-0003LG-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:00:57 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WZSu-0001RW-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:59:10 -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 18WZR2-0000l7-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 04:57:12 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h09AV0e23420;
	Thu, 9 Jan 2003 05:31:00 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>,
   Chad Yates <cyates@uidaho.edu>
Date: Thu, 9 Jan 2003 05:01:31 -0500
User-Agent: KMail/1.4.3
References: <NBBBJJODBJBNJFNIDDCNIEPNDDAA.cyates@uidaho.edu>
	<20030109094126.GB313@bulbasaur.rediris.es>
In-Reply-To: <20030109094126.GB313@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301090501.31843.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: commconcpp2 changes to date.cpp (copy)
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, 09 Jan 2003 10:01:01 -0000

Yes, that is nice.  We really should update the common c++ (and ccrtp) pa=
ges a=20
lot and also reference the link to the archive on them...

On Thursday 09 January 2003 04:41, Federico Montesino Pouzols wrote:
> It seems that the list has been frozen for two or three days,
> but I now see all the posts that you have reposted with '(copy)'
> appended. In the meantime, the mail archives are working again, now
> based on MHonArc. By the way, this new interface allows for searching
> through the archives.
>
> On Tue, Jan 07, 2003 at 12:25:31PM -0800, Chad Yates wrote:
> > I just started recieving list messages again today.  It appears that =
my
> > previous messages were lost, so I'm forwarding them again...
> >
> > The recent changes to date.cpp broke the library under MSVC 6.0 on th=
e
> > following:
> >
> >   nyear =3D int(trunc(i));
> >   nmonth =3D int(trunc(j));
> >   nday =3D int(trunc(k));
> >
> > I removed the trunc() function, and wondered if it was redundant anyw=
ay?
> > since the int() should suffice.
> >
> > I also wrote a test suite for the date class (figured what better way=
 to
> > determine if trunc() was necessary, and it needed to be done anyway) =
The
> > following are the test cases, and I'll save the code fore release wit=
h
> > the test suite:
> >
> >   DateTest.testSimpleGets ...
> >   DateTest.testSimpleSets ...
> >   DateTest.testIsValid ...
> >   DateTest.testGetDate_String ...
> >   DateTest.testGetDate_time_t ...
> >   DateTest.testGeteDate_struct_tm ...
> >   DateTest.testOperations ...
> >
> > and implemented a functions that were defined in the class but not
> > implemented (linker errors).  I also re-arranged some of the related
> > methods to avoid duplicate code.  I've attached diffs showing what wa=
s
> > changed. here is a summary:
> >
> > date.cpp
> > - added test fixture for the Date class and fixed/enhanced.
> > - implemented missing tm* Date::getDate(tm*) function declared in
> >   class but not in implementation. took the liberty to make it
> >   also return a time_t instead of tm* in addition to filling the
> >   provided tm structure.
> > - simplified time_t Date::getDate(void) to use the above function.
> > - changed setDate parameter to const and placed (char*) in calls to
> > Number. setDate's use of Number seems to guarantee constness, but I d=
on't
> > know if Number itself does. hopefully these casts can be removed some=
day.
> >
> > email me with questions and comments.
> >
> > ,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 MAILER-DAEMON Thu Jan 09 05:21:04 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WZlo-0008MF-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:18:40 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WZlV-00084m-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:18:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WZgF-0003Ig-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:12:56 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WZgD-0003Ds-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:12:53 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18WZgs-0000Ba-00; Thu, 09 Jan 2003 11:13:34 +0100
Date: Thu, 9 Jan 2003 11:13:33 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030109101333.GD313@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>, bug-commoncpp@gnu.org
References: <NBBBJJODBJBNJFNIDDCNEEOIDDAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNEEOIDDAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Small bug in MD5Digest
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: Thu, 09 Jan 2003 10:18:38 -0000


	It looks like the 'updated = false;' line prevents people from
being able to use initDigest, as if only the call from the constructor
had been taken into account. I have commited your patch.

On Thu, Jan 02, 2003 at 10:28:44PM -0800, Chad Yates wrote:
> I have isolated the bug in the MD5Digest class as pointed out by Albert.  It
> appears that if you use a MD5Digest, and then .initDigest and then export
> the digest, the last value is reported.  I have attributed it to code in
> initDigest that sets updated equal to false which apparently keeps it from
> updating the internal digest.  changing this seems to fix it without
> breaking my other test cases (Construction, Empty Message, Small Message,
> Re-Initialization, Large Message, Piecewise Message, and Typical Usage).
> 
> If someone that is an expert on the md5 class and the algorithm (I know very
> little about the internals of the md5 algorithm), can they let me know if
> this sounds right.
> 
> thanks,
> 
> Chad
> 
> P.S if this is correct we should also be able to remove the updated = true
> line in the constructor after the call to initDigest.
> 
> Index: md5.cpp
> ===================================================================
> RCS file: /cvsroot/commoncpp/commoncpp2/src/md5.cpp,v
> retrieving revision 1.2
> diff -r1.2 md5.cpp
> 142c142,143
> <       updated = false;
> ---
> >       //updated = false;
> >       updated = true; // CCY Added
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Thu Jan 09 05:26:39 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WZso-0005Wt-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:25:54 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WZsQ-00053j-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:25:30 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WZpe-0003ME-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:22:40 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WZnx-0001z3-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:20:53 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18WZog-0000Bm-00; Thu, 09 Jan 2003 11:21:38 +0100
Date: Thu, 9 Jan 2003 11:21:38 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Thai D." <netvirtuose@hotmail.com>
Message-ID: <20030109102138.GE313@bulbasaur.rediris.es>
Mail-Followup-To: "Thai D." <netvirtuose@hotmail.com>,
	bug-commoncpp@gnu.org
References: <F116DuNePJgzg8MTbQp00000bf0@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F116DuNePJgzg8MTbQp00000bf0@hotmail.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Socket programming
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: Thu, 09 Jan 2003 10:25:52 -0000


	Do you mean something based on a select/poll system call? In
that case, you can use the SocketPort and SocketService classes.

On Mon, Jan 06, 2003 at 04:22:09PM +0100, Thai D. wrote:
> Hi
> 
> I would like to developp a single thread server but with non blocking 
> socket. Do you think I can use common c++ to do that ?
> If yes, could you give me any starting point ?
> 
> Many thanks, Thai
> 
> _________________________________________________________________
> MSN Search, le moteur de recherche qui pense comme vous ! 
> http://search.msn.fr/worldwide.asp
> 



From MAILER-DAEMON Thu Jan 09 05:56:49 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WaJH-0003nf-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:53:15 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WaIP-0003Ob-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:52:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WaEl-00022p-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:48:37 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WaD5-0001Rg-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:46:52 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18WaDo-0000Dt-00; Thu, 09 Jan 2003 11:47:37 +0100
Date: Thu, 9 Jan 2003 11:47:36 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030109104736.GF313@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>, bug-commoncpp@gnu.org
References: <NBBBJJODBJBNJFNIDDCNOEPHDDAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNOEPHDDAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: commconcpp2 changes to date.cpp
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: Thu, 09 Jan 2003 10:53:14 -0000


	Committed to CVS.

On Mon, Jan 06, 2003 at 04:45:04PM -0800, Chad Yates wrote:
> The recent changes to date.cpp broke the library under MSVC 6.0 on the
> following:
> 
>   nyear = int(trunc(i));
>   nmonth = int(trunc(j));
>   nday = int(trunc(k));
> 
> I removed the trunc() function, and wondered if it was redundant anyway?
> since the int() should suffice.
> 
> I also wrote a test suite for the date class (figured what better way to
> determine if trunc() was necessary, and it needed to be done anyway) The
> following are the test cases, and I'll save the code fore release with the
> test suite:
> 
>   DateTest.testSimpleGets ...
>   DateTest.testSimpleSets ...
>   DateTest.testIsValid ...
>   DateTest.testGetDate_String ...
>   DateTest.testGetDate_time_t ...
>   DateTest.testGeteDate_struct_tm ...
>   DateTest.testOperations ...
> 
> and implemented a functions that were defined in the class but not
> implemented (linker errors).  I also re-arranged some of the related methods
> to avoid duplicate code.  I've attached diffs showing what was changed. here
> is a summary:
> 
> date.cpp
> - added test fixture for the Date class and fixed/enhanced.
> - implemented missing tm* Date::getDate(tm*) function declared in
>   class but not in implementation. took the liberty to make it
>   also return a time_t instead of tm* in addition to filling the
>   provided tm structure.
> - simplified time_t Date::getDate(void) to use the above function.
> - changed setDate parameter to const and placed (char*) in calls to Number.
> setDate's use of Number seems to guarantee constness, but I don't know if
> Number itself does. hopefully these casts can be removed someday.
> 
> email me with questions and comments.
> 
> ,Chad



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




From MAILER-DAEMON Thu Jan 09 06:01:48 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WaNI-00069A-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:57:24 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WaNC-00060m-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:57:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WaN2-0005m1-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:57:12 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WaJ8-0003ii-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 05:53:06 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18WaJq-0000EK-00; Thu, 09 Jan 2003 11:53:50 +0100
Date: Thu, 9 Jan 2003 11:53:49 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030109105348.GG313@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>, bug-commoncpp@gnu.org
References: <NBBBJJODBJBNJFNIDDCNAEPIDDAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNAEPIDDAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: urlstring testing/enhancement
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: Thu, 09 Jan 2003 10:57:23 -0000


	Hi, ...

On Mon, Jan 06, 2003 at 04:45:04PM -0800, Chad Yates wrote:
> I built urlstring testcases this weekend. Here are the test cases performed:
>   URLStringTest.testBinaryBase64EncodeDecode ...
>   URLStringTest.testStringVersion ...
>   URLStringTest.testTypicalUrlEncodeDecode ...
>   URLStringTest.testTypicalTextBase64EncodeDecode ...
>   URLStringTest.testSimpleTextBase64EncodeDecode ...
>   URLStringTest.testComplexTextBase64EncodeDecode ...
>   URLStringTest.testPaddingPerfect ...
>   URLStringTest.testPadding1Short ...
>   URLStringTest.testPadding2Short ...
> 
> I also added Base64 functions that take std::string arguments for the encode
> output and the decode input.  I don't know where the line is supposed to be
> relating to string usage as I see most of common c++ is char* based, but
> there seems to be std::string usage in some classes.  personally I like
> having it as an overload option.  I can post diffs showing the new functions
> if they are wanted.
> 

	I think we should include these new functions. For the last
months some things have been changed and updated to progresively
incorporate string as preferred to char*. These new functions do not
break backwards compatibility, so I see no reason to not include it.

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



From MAILER-DAEMON Thu Jan 09 06:11:54 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WaZj-0004MQ-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 06:10:15 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WaYx-0004CX-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 06:09:27 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WaYG-0003Rq-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 06:08:45 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WaXY-00032Z-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 06:08:00 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18WaYC-0000Ea-00; Thu, 09 Jan 2003 12:08:40 +0100
Date: Thu, 9 Jan 2003 12:08:39 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030109110839.GH313@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>,
	Federico Montesino Pouzols <fedemp@altern.org>,
	bug-commoncpp@gnu.org
References: <20030106200308.GJ4098@bulbasaur.rediris.es>
	<NBBBJJODBJBNJFNIDDCNEEPGDDAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNEEPGDDAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
cc: Federico Montesino Pouzols <fedemp@altern.org>
Subject: Re: bugs in CRC32
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: Thu, 09 Jan 2003 11:10:13 -0000


	Hi,

On Mon, Jan 06, 2003 at 02:45:44PM -0800, Chad Yates wrote:
> I did a little research -- I'm not an expert on CRC algorithms, allthough I
> might be after all this ;)
> 
> I did a myriad of searches on google to see if I could find out how many
> different versions of crc32 there are.  I had hoped to find a definite
> answer, however, that doesn't seem to be the case.  I found a document that
> discusses this problem
> (http://ce.sharif.edu/~cheraghchi/science/cs/crc_algorithm.htm if
> interestd).
> 

	I'll read it. In the meantime...

> it appears that the most common CRC32 version is the one for ethernet, and
> according to the above, is also "reportedly used in PKZip, AUTODIN II,
> Ethernet, and FDDI."  I'm not familiar with ATM, so don't know if it uses a
> different version.
> 

	As far as I know, the ATM CRC32 is the same as the Ethernet one.

> anyway, according to the docs above this version has these distinguishing
> attributes. (The Check: value is the result of running it against
> '123456789').
> 
>    Name   : "CRC-32"
>    Width  : 32
>    Poly   : 04C11DB7
>    Init   : FFFFFFFF
>    RefIn  : True
>    RefOut : True
>    XorOut : FFFFFFFF
>    Check  : CBF43926
> 

	We should include this specifications in the documentation to
avoid confusions.

> The fsum program I've been using to validate some of my tests also generates
> that number:
> 
>   ; SlavaSoft Optimizing Checksum Utility fsum 2.0 <www.slavasoft.com>
>   ; Generated on 01/06/03 at 14:19:17
>   cbf43926 ?CRC32*check.txt
> 
> So, it should be pretty safe to assume that it is implementing the same
> version of the algorithm.  the changes I made bring it into check with that
> version.  It's really a shame that there is the possiblilyt of multiple
> versions masquerading as "CRC32"  we may need to create 2 or more versions
> if we want to cover both the old and new versions.  perhaps the code could
> be templatized (using template values) and be instantiated into digest.cpp
> for CRC, CRC16, CRC32_Ethernet, CRC32_ATM, etc... or , if those weren't
> enough they could just use the template directly like so:
> 
>   CRC<32, 0x04C11DB7, 0xFFFFFFFF, true, true, 0xFFFFFFFF>
> 
> Its an idea anyway :)  I might even be willing to pursue it if it sounds
> useful (for educational reasons)
> 

	I think it is a good idea.

> another idea may be to copy the code from the above doc (it says the code is
> public domain) and then have the commoncpp2 classes call it with the right
> parms.  I don't know if it's fast or not.  the current CRC32 creates tables
> everytime it's called, so I'd say it's not exactly efficient either (maybe
> the initialization should be moved to a class initializer?)
> 

	Yes, making the tables only once would be more efficient by
far. Does the code you mention produce the results expected by the
current crc32 demo for the ATM tests?

> thoughts?
> 
> ,Chad
> 



From MAILER-DAEMON Thu Jan 09 07:18:21 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WbWn-00077a-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 07:11:17 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WbNY-0004Ww-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 07:01:44 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WbGr-0003Yi-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 06:54:52 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WbGg-0003V5-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 06:54:38 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18WbHL-0000JP-00; Thu, 09 Jan 2003 12:55:19 +0100
Date: Thu, 9 Jan 2003 12:55:18 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ittay Freiman <ittay@qlusters.com>
Message-ID: <20030109115518.GI313@bulbasaur.rediris.es>
Mail-Followup-To: Ittay Freiman <ittay@qlusters.com>, bug-commoncpp@gnu.org
References: <1042008781.5628.10.camel@rum>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1042008781.5628.10.camel@rum>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Thread bugs
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: Thu, 09 Jan 2003 12:11:15 -0000


	Hi,...

On Wed, Jan 08, 2003 at 08:53:01AM +0200, Ittay Freiman wrote:
> 1. according to the documentation, one should do 'delete this' in
> final(). however, in close() there is a check on 'priv' after calling
> final(). when an application has many threads opening and closing, this
> memory can already be allocated to some other object, thus this check
> will (has for us) fail. 
> 

	Um, that check is done in order to know if priv->_tid may be
set to 0, however, priv->_tid is already set to 0 in terminate. Should
not we remove the check and the priv->_tid = 0, or am I missing
something?

> 2. in terminate() a call to pthread_join() is made. according to the man
> pages, this call is illegal for a detached thread. it does fail
> sometimes for us.
> 

	Yes, pthread_join should only be called if it is not detached,
which can be checked with pthread_attr_getdetachstate.

> ittay
> -- 
> Ittay Freiman <ittay@qlusters.com>
> Qlusters Inc.
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Thu Jan 09 07:42:28 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Wbrs-0006WD-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 07:33:04 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Wbgm-0001nf-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 07:21:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WbYU-0007qi-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 07:13: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 18WbRI-0005Z3-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 07:05:36 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h09CdEe24204;
	Thu, 9 Jan 2003 07:39:14 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>,
   Chad Yates <cyates@uidaho.edu>
Date: Thu, 9 Jan 2003 07:09:48 -0500
User-Agent: KMail/1.4.3
References: <NBBBJJODBJBNJFNIDDCNAEPIDDAA.cyates@uidaho.edu>
	<20030109105348.GG313@bulbasaur.rediris.es>
In-Reply-To: <20030109105348.GG313@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301090709.48198.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: urlstring testing/enhancement
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, 09 Jan 2003 12:33:02 -0000

I agree, we can overload and should have std::string versions.  This has =
been=20
changing over time as Federico notes.

On Thursday 09 January 2003 05:53, Federico Montesino Pouzols wrote:
> Hi, ...
>
> On Mon, Jan 06, 2003 at 04:45:04PM -0800, Chad Yates wrote:
> > I built urlstring testcases this weekend. Here are the test cases
> > performed: URLStringTest.testBinaryBase64EncodeDecode ...
> >   URLStringTest.testStringVersion ...
> >   URLStringTest.testTypicalUrlEncodeDecode ...
> >   URLStringTest.testTypicalTextBase64EncodeDecode ...
> >   URLStringTest.testSimpleTextBase64EncodeDecode ...
> >   URLStringTest.testComplexTextBase64EncodeDecode ...
> >   URLStringTest.testPaddingPerfect ...
> >   URLStringTest.testPadding1Short ...
> >   URLStringTest.testPadding2Short ...
> >
> > I also added Base64 functions that take std::string arguments for the
> > encode output and the decode input.  I don't know where the line is
> > supposed to be relating to string usage as I see most of common c++ i=
s
> > char* based, but there seems to be std::string usage in some classes.=
=20
> > personally I like having it as an overload option.  I can post diffs
> > showing the new functions if they are wanted.
>
> =09I think we should include these new functions. For the last
> months some things have been changed and updated to progresively
> incorporate string as preferred to char*. These new functions do not
> break backwards compatibility, so I see no reason to not include it.
>
> > ,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 MAILER-DAEMON Thu Jan 09 07:42:46 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Wbzv-0001SP-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 07:41:23 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WbxB-0000Fj-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 07:38:33 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wbty-00075l-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 07:35:16 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Wbsd-0006yH-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 07:33:51 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18WbtG-0000Qo-00; Thu, 09 Jan 2003 13:34:30 +0100
Date: Thu, 9 Jan 2003 13:34:29 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ittay Freiman <ittay@qlusters.com>
Message-ID: <20030109123429.GJ313@bulbasaur.rediris.es>
Mail-Followup-To: Ittay Freiman <ittay@qlusters.com>, bug-commoncpp@gnu.org
References: <1042027341.1082.18.camel@rum>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1042027341.1082.18.camel@rum>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Thread::detach bug
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: Thu, 09 Jan 2003 12:41:22 -0000


	Yes, I think this code could be more robust if instead of
calling pthread_create and then pthread_detach, it set the detach
attribute of the thread before pthread_create.

On Wed, Jan 08, 2003 at 02:02:22PM +0200, Ittay Freiman wrote:
> if i call Thread::detach, the thread is created in joinable mode, and a
> line after pthread_detach is called. however, if the threads are short
> lived, or the system is loaded, this line may execute after the thread
> has finished its run, destroyed itself (in final(), as recommended in
> the documentation) and therefore its resources are lost.
> 
> -- 
> Ittay Freiman <ittay@qlusters.com>
> Qlusters Inc.
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Thu Jan 09 08:28:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WcjG-0001nw-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:28:14 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Wci2-0000zH-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:26:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wcch-0007LI-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:21:28 -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 18WcKZ-0000qL-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:02:44 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h09DaQe24755;
	Thu, 9 Jan 2003 08:36:26 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>,
   Ittay Freiman <ittay@qlusters.com>
Date: Thu, 9 Jan 2003 08:07:00 -0500
User-Agent: KMail/1.4.3
References: <1042008781.5628.10.camel@rum>
	<20030109115518.GI313@bulbasaur.rediris.es>
In-Reply-To: <20030109115518.GI313@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301090807.00982.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: Thread bugs
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, 09 Jan 2003 13:28:13 -0000

At one time I thought most things I would write would have self destructi=
ng=20
and detached threads.  This didn't end up being the case, so I had somewh=
at=20
ignored detached threads.  I simply assumed it would be safe to do a join=
 and=20
have it fail with an error on an already detached thread.  It would be a=20
simple change to have it check detach state first.  But is=20
pthread_attr_getdetachstate truelly common and portable or do we need to =
add=20
another .m4 test for it?

On Thursday 09 January 2003 06:55, Federico Montesino Pouzols wrote:
> Hi,...
>
> On Wed, Jan 08, 2003 at 08:53:01AM +0200, Ittay Freiman wrote:
> > 1. according to the documentation, one should do 'delete this' in
> > final(). however, in close() there is a check on 'priv' after calling
> > final(). when an application has many threads opening and closing, th=
is
> > memory can already be allocated to some other object, thus this check
> > will (has for us) fail.
>
> =09Um, that check is done in order to know if priv->_tid may be
> set to 0, however, priv->_tid is already set to 0 in terminate. Should
> not we remove the check and the priv->_tid =3D 0, or am I missing
> something?
>
> > 2. in terminate() a call to pthread_join() is made. according to the =
man
> > pages, this call is illegal for a detached thread. it does fail
> > sometimes for us.
>
> =09Yes, pthread_join should only be called if it is not detached,
> which can be checked with pthread_attr_getdetachstate.
>
> > ittay
> > --
> > Ittay Freiman <ittay@qlusters.com>
> > Qlusters Inc.
> >
> >
> >
> > _______________________________________________
> > 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 MAILER-DAEMON Thu Jan 09 08:37:28 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WcoJ-000428-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:33:27 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WcnC-0003Xa-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:32:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wcmf-0003Kq-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:31:47 -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 18WcGS-0007pl-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 07:58:28 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h09DWBe24719;
	Thu, 9 Jan 2003 08:32:11 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>,
   Ittay Freiman <ittay@qlusters.com>
Date: Thu, 9 Jan 2003 08:02:45 -0500
User-Agent: KMail/1.4.3
References: <1042027341.1082.18.camel@rum>
	<20030109123429.GJ313@bulbasaur.rediris.es>
In-Reply-To: <20030109123429.GJ313@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301090802.45598.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: Thread::detach bug
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, 09 Jan 2003 13:33:25 -0000

Since we now have a seperate "detach()" to kick off detached threads, yes=
, it=20
would be very easy to have it set the priv->attr for detach before the=20
pthread_create rather than doing so after the thread is created.  This wo=
uld=20
eliminate the race.

On Thursday 09 January 2003 07:34, Federico Montesino Pouzols wrote:
> Yes, I think this code could be more robust if instead of
> calling pthread_create and then pthread_detach, it set the detach
> attribute of the thread before pthread_create.
>
> On Wed, Jan 08, 2003 at 02:02:22PM +0200, Ittay Freiman wrote:
> > if i call Thread::detach, the thread is created in joinable mode, and=
 a
> > line after pthread_detach is called. however, if the threads are shor=
t
> > lived, or the system is loaded, this line may execute after the threa=
d
> > has finished its run, destroyed itself (in final(), as recommended in
> > the documentation) and therefore its resources are lost.
> >
> > --
> > Ittay Freiman <ittay@qlusters.com>
> > Qlusters Inc.
> >
> >
> >
> > _______________________________________________
> > 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 MAILER-DAEMON Thu Jan 09 08:45:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Wcyr-0000N1-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:44:21 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WcxM-00081Y-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:42:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wct7-0006Nl-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:38:28 -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 18WcZD-0005tA-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:17:51 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h09Dpae24908;
	Thu, 9 Jan 2003 08:51:36 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>,
   Ittay Freiman <ittay@qlusters.com>
Date: Thu, 9 Jan 2003 08:22:11 -0500
User-Agent: KMail/1.4.3
References: <1042008781.5628.10.camel@rum>
	<20030109115518.GI313@bulbasaur.rediris.es>
In-Reply-To: <20030109115518.GI313@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301090822.11008.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: Thread bugs
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, 09 Jan 2003 13:44:20 -0000

I have looked at this more.  Using getdetachstate we can certainly determ=
ine=20
if the thread was originally created "detached" with the fix for detach=20
creation since it would be stored in the objects private attribute.  Howe=
ver,=20
if a thread is arbitrarily detached then there is a race window between w=
hen=20
that occurs and the priv->attr may be updated to reflect it.  I think we =
can=20
assume most detached threads would likely be detached at creation and acc=
ept=20
the current join attempt against the rare situation where a thread is lat=
er=20
detached and then is attempted to be cancelled either without or before t=
he=20
priv->attr is modifed.

On Thursday 09 January 2003 06:55, Federico Montesino Pouzols wrote:
> Hi,...
>
> On Wed, Jan 08, 2003 at 08:53:01AM +0200, Ittay Freiman wrote:
> > 1. according to the documentation, one should do 'delete this' in
> > final(). however, in close() there is a check on 'priv' after calling
> > final(). when an application has many threads opening and closing, th=
is
> > memory can already be allocated to some other object, thus this check
> > will (has for us) fail.
>
> =09Um, that check is done in order to know if priv->_tid may be
> set to 0, however, priv->_tid is already set to 0 in terminate. Should
> not we remove the check and the priv->_tid =3D 0, or am I missing
> something?
>
> > 2. in terminate() a call to pthread_join() is made. according to the =
man
> > pages, this call is illegal for a detached thread. it does fail
> > sometimes for us.
>
> =09Yes, pthread_join should only be called if it is not detached,
> which can be checked with pthread_attr_getdetachstate.
>
> > ittay
> > --
> > Ittay Freiman <ittay@qlusters.com>
> > Qlusters Inc.
> >
> >
> >
> > _______________________________________________
> > 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 MAILER-DAEMON Thu Jan 09 08:47:59 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Wcyz-0000Rw-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:44:29 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Wcxk-0008Nb-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:43:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wcx2-0007le-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:42:31 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WcsL-0005gE-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 08:37:37 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18Wcss-0000T0-00; Thu, 09 Jan 2003 14:38:10 +0100
Date: Thu, 9 Jan 2003 14:38:10 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-ID: <20030109133810.GK313@bulbasaur.rediris.es>
Mail-Followup-To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20030102172955.GG17347@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030102172955.GG17347@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: Some issues with the codebase
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: Thu, 09 Jan 2003 13:44:28 -0000


	Hi,...

On Thu, Jan 02, 2003 at 07:29:55PM +0200, Albert Strasheim wrote:
> Hello,
> 
> While looking at some of the code in Common C++, I've noticed a few 
> general issues that we might want to address.
> 
> Firstly, identifier names. Here's an important quote from the C++ 
> standard via mozilla.org's C++ portability guide, available at
> http://www.mozilla.org/hacking/portable-cpp.html,
> 
> "Certain sets of names and function signatures are always reserved to 
> the implementation:
> 
>     * Each name that contains a double underscore (__) or begins with an 
> underscore followed by an uppercase letter (2.11) is reserved to the 
> implemenation for any use.
>     * Each name that begins with an underscore is reserved to the
> implementaiton for use as a name in the global namespace."
> 
> I've seen many member variables whose names start with an underscore. As 
> far as I understand, this is Very, Very Evil(TM). If you really want an 
> underscore in your identifier name, stick it on the end.
> 

	I agree, many people discourage the use of leading underscores
and there are good reasons for doing so. I believe there is no clear
convention for this in Common C++. Personally, I would suggest to use
trailing underscores in data members as a new recommendation for
contributions, modifications and new code.

> Secondly, what's up with the Common C++ namespace being called "ost"? I 
> assume this stands for Open Source Telecom? If another company were to 
> contribute code to this project, are we going to start seeing "acme" and 
> other namespaces too? :-)
> 
> I think Common C++ deserves a vendor-neutral namespace, say... mmm... 
> "ccxx"? :-)
> 

	Well, from the beginning most of the development has been done
by ost, so the choice of ost as namespace seems logical and fair. We
could provide the alternative ccxx namespace, though it could lead to
some confusion. Moreover, since ost is a corporation that truly and
widely supports free software, I, as a free software developer who has
found many troubles, and finally impossible to develop free software
for software corporations, like that the merits of ost be
recognized. In fact, ost is rather conspicuous about its support for
free software. I think it is really good to find free software deeply
related to commercial corporations. Hopefully, in the future we will
see more free software created and mostly developed by commercial
corporations, which perhaps looks a somewhat uncommon thing as opposed
to free software projects that are created by independent volunteers
and thus are vendor-neutral as for names.

	Of course, this is my personal point of view. If you or
someone else in the list disagree, I would like to further discuss
this issue.

> To provide backward compatability for a while, I think following 
> declaration sprinkled through some of the headers will do the trick:
> 
> #ifdef CCXX_NAMESPACES
> /**
>  * Old Common C++ namesspace (DEPRECATED).
>  */
> namespace ost
> {
>   using namespace ccxx;
> }
> #endif
> 
> Don't know exactly how one convinces doxygen to add a description for a 
> namespace, but anyway.
> 

	There is a \namespace command, and I think the rules for
namespaces are the same as for classes.

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



From MAILER-DAEMON Thu Jan 09 13:53:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Whfi-0004Z4-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 13:44:54 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WhP2-0001KG-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 13:27:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WhOi-0001E4-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 13:27:31 -0500
Received: from mx4.magma.ca ([206.191.0.253])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WhOi-00010D-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 13:27:20 -0500
Received: from mail6.magma.ca (mail6 [206.191.0.248])
	by mx4.magma.ca (Magma's Mail Server) with ESMTP id h09IPHkP020026
	for <bug-commoncpp@gnu.org>; Thu, 9 Jan 2003 13:25:18 -0500
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail6.magma.ca (Magma's Mail Server) with ESMTP id h09IPHsu011071
	for <bug-commoncpp@gnu.org>; Thu, 9 Jan 2003 13:25:17 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: <bug-commoncpp@gnu.org>
Date: Thu, 9 Jan 2003 13:25:12 -0500
Message-ID: <000001c2b80c$72f98a30$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0001_01C2B7E2.8A238230"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: CVS repository problems?
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, 09 Jan 2003 18:44:53 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0001_01C2B7E2.8A238230
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is the first time I have attempted to extract the commoncpp code
and I am seeing some strange behavior.
 
I am using anonymous CVS access checking out the commoncpp module. I get
no complaints from CVS, but there seems to be files that are not being
checked out. For example, the first attempt yielded an empty config
directory (except for the CVS subdir) and no INSTALL file. In the second
attempt the INSTALL file showed up, and I got Makefile.am to appear in
the config directory. Since there was no configure file, I ran autoconf
to generate it, but when running ./configure, it complains it "can not
find install-sh or install.sh in config ./config". A quick check of the
config directory shows that only Makefile.am is in that directory (and
the CVS Entries file has a reference to this file only). Am I missing
install.sh? Is there a problem with the repository? Am I doing something
fundamentally wrong?
 
Ian

------=_NextPart_000_0001_01C2B7E2.8A238230
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D189121318-09012003><FONT face=3DArial size=3D2>This =
is the first=20
time I have attempted to extract the commoncpp code and I am seeing some =
strange=20
behavior.</FONT></SPAN></DIV>
<DIV><SPAN class=3D189121318-09012003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D189121318-09012003><FONT face=3DArial size=3D2>I am =
using anonymous=20
CVS access checking out the commoncpp module. I get no complaints from =
CVS, but=20
there seems to be files that are not being checked out. For example, the =
first=20
attempt yielded an empty config directory (except for the CVS subdir) =
and no=20
INSTALL file. In the second attempt the INSTALL file showed up, and I =
got=20
Makefile.am to appear in the config directory. Since there was no =
configure=20
file, I ran autoconf to generate it, but when running ./configure, it =
complains=20
it "can not find install-sh or install.sh in config ./config". A quick =
check of=20
the config directory shows that only Makefile.am is in that directory =
(and the=20
CVS Entries file has a reference to this file only). Am I missing =
install.sh? Is=20
there a problem with the repository? Am I doing something fundamentally=20
wrong?</FONT></SPAN></DIV>
<DIV><SPAN class=3D189121318-09012003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D189121318-09012003><FONT face=3DArial=20
size=3D2>Ian</FONT></SPAN></DIV></BODY></HTML>

------=_NextPart_000_0001_01C2B7E2.8A238230--




From MAILER-DAEMON Thu Jan 09 15:01:16 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WiZG-00072T-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 14:42:18 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WiZA-0006zb-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 14:42:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WiYw-0006tf-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 14:42:09 -0500
Received: from maties2.sun.ac.za ([146.232.128.10])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WiYv-0006rc-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 14:41:58 -0500
Received: from dogbert.sdsl.sun.ac.za ([146.232.83.63])
	by maties2.sun.ac.za with smtp (Exim 4.05)
	id 18WiYn-0003oJ-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 21:41:49 +0200
Received: (qmail 25923 invoked from network); 9 Jan 2003 19:41:49 -0000
Received: from dogbert.localdomain (192.168.1.2)
  by 0 with SMTP; 9 Jan 2003 19:41:49 -0000
Received: from fullung by dogbert.localdomain with local (Exim 3.36 #1
	(Debian))	id 18WzY6-00012p-00; Fri, 10 Jan 2003 15:50:14 +0200
Date: Fri, 10 Jan 2003 15:50:14 +0200
From: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-ID: <20030110135013.GD3065@dogbert.sdsl.sun.ac.za>
References: <20030102172955.GG17347@dogbert.sdsl.sun.ac.za>
	<20030109133810.GK313@bulbasaur.rediris.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030109133810.GK313@bulbasaur.rediris.es>
User-Agent: Mutt/1.4i
Sender: Albert Strasheim <fullung@dogbert.localdomain>
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*18WiYn-0003oJ-00*26GnWnoQ8eU*
cc: bug-commoncpp@gnu.org
Subject: Re: Some issues with the codebase
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, 09 Jan 2003 19:42:16 -0000

Hello,

On Thu, 09 Jan 2003, Federico Montesino Pouzols wrote:

> On Thu, Jan 02, 2003 at 07:29:55PM +0200, Albert Strasheim wrote:
> >
> > While looking at some of the code in Common C++, I've noticed a few 
> > general issues that we might want to address.
> > 
> > Firstly, identifier names. Here's an important quote from the C++ 
> > standard via mozilla.org's C++ portability guide, available at
> > http://www.mozilla.org/hacking/portable-cpp.html,
> > 
> > "Certain sets of names and function signatures are always reserved to 
> > the implementation:
> > 
> >     * Each name that contains a double underscore (__) or begins with an 
> > underscore followed by an uppercase letter (2.11) is reserved to the 
> > implemenation for any use.
> >     * Each name that begins with an underscore is reserved to the
> > implementaiton for use as a name in the global namespace."
> > 
> > I've seen many member variables whose names start with an underscore. As 
> > far as I understand, this is Very, Very Evil(TM). If you really want an 
> > underscore in your identifier name, stick it on the end.
> > 
> 
> 	I agree, many people discourage the use of leading underscores
> and there are good reasons for doing so. I believe there is no clear
> convention for this in Common C++. Personally, I would suggest to use
> trailing underscores in data members as a new recommendation for
> contributions, modifications and new code.

I don't quite agree with using only a trailing underscore. Invariably 
you're going to make a typo somewhere, and leave out an underscore, 
which could be pretty disastrous if you start calling your parameters 
in your constructors and "set" methods the same as the members, without 
the underscore.

CppUnit seems to call all their member variables "m_<membername>". I 
haven't decided if this convention is optimal, or whether it qualifies 
as some kind of quasi-Hungarian notation (Very, Very Evil(TM)), but I 
think it's better than the trailing underscore convention.

I'd be interested to hear what other people suggest in this regard.

> > Secondly, what's up with the Common C++ namespace being called "ost"? I 
> > assume this stands for Open Source Telecom? If another company were to 
> > contribute code to this project, are we going to start seeing "acme" and 
> > other namespaces too? :-)
> > 
> > I think Common C++ deserves a vendor-neutral namespace, say... mmm... 
> > "ccxx"? :-)
> 
> 	Well, from the beginning most of the development has been done
> by ost, so the choice of ost as namespace seems logical and fair. We
> could provide the alternative ccxx namespace, though it could lead to
> some confusion. Moreover, since ost is a corporation that truly and
> widely supports free software, I, as a free software developer who has
> found many troubles, and finally impossible to develop free software
> for software corporations, like that the merits of ost be
> recognized. In fact, ost is rather conspicuous about its support for
> free software. I think it is really good to find free software deeply
> related to commercial corporations. Hopefully, in the future we will
> see more free software created and mostly developed by commercial
> corporations, which perhaps looks a somewhat uncommon thing as opposed
> to free software projects that are created by independent volunteers
> and thus are vendor-neutral as for names.

I totally agree with you; companies should contribute more to open 
source projects. I try to encourage this whenever I can.

However, I don't think you've really addressed my issues with company 
names in namespaces. What if a new company, say ACME Inc., takes an 
active interest in developing Common C++ and contributes much code. 
Are we then going to split stuff up into "ost" and "acme" namespaces?
I think not.

If OST wants recognition (which they richly deserve) for the work they 
have done on Common C++, stick an OST logo on the Common C++ homepage 
(unless this violates some kind of GNU homepage guideline). They will 
get much more recognition through this. You can't really miss the 
copyright notices either.

All other things aside, IMHO, the namespace of a C++ library is not the 
place to advertise the developer(s) of the code.
 
> 	Of course, this is my personal point of view. If you or
> someone else in the list disagree, I would like to further discuss
> this issue.

I hope you will reconsider my arguments. I'm not trying to be different, 
I'm just trying to help establish a great library.

> > To provide backward compatability for a while, I think following 
> > declaration sprinkled through some of the headers will do the trick:
> > 
> > #ifdef CCXX_NAMESPACES
> > /**
> >  * Old Common C++ namesspace (DEPRECATED).
> >  */
> > namespace ost
> > {
> >   using namespace ccxx;
> > }
> > #endif
> > 
> > Don't know exactly how one convinces doxygen to add a description for a 
> > namespace, but anyway.
> > 
> 
> 	There is a \namespace command, and I think the rules for
> namespaces are the same as for classes.

Cool.

Cheers,

Albert



From MAILER-DAEMON Thu Jan 09 15:06:55 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WigC-0000Sg-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 14:49:28 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WiMQ-0004E4-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 14:29:02 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wi6u-00015F-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 14:13:16 -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 18Wi2t-0000NR-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 14:08:51 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h09JgZe27420;
	Thu, 9 Jan 2003 14:42:35 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: "Ian Gough" <igough@gridiron-networks.com>, <bug-commoncpp@gnu.org>
Date: Thu, 9 Jan 2003 14:13:13 -0500
User-Agent: KMail/1.4.3
References: <000001c2b80c$72f98a30$0c02a8c0@gridironnetworks.com>
In-Reply-To: <000001c2b80c$72f98a30$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301091413.13696.dyfet@ostel.com>
Subject: Re: CVS repository problems?
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, 09 Jan 2003 19:49:27 -0000

The way you build from commoncpp2 cvs module is you run ./reconfig after =
your=20
checkout.  This rebuilds configure and all the makefile.in's.

On Thursday 09 January 2003 13:25, Ian Gough wrote:
> This is the first time I have attempted to extract the commoncpp code
> and I am seeing some strange behavior.
>
> I am using anonymous CVS access checking out the commoncpp module. I ge=
t
> no complaints from CVS, but there seems to be files that are not being
> checked out. For example, the first attempt yielded an empty config
> directory (except for the CVS subdir) and no INSTALL file. In the secon=
d
> attempt the INSTALL file showed up, and I got Makefile.am to appear in
> the config directory. Since there was no configure file, I ran autoconf
> to generate it, but when running ./configure, it complains it "can not
> find install-sh or install.sh in config ./config". A quick check of the
> config directory shows that only Makefile.am is in that directory (and
> the CVS Entries file has a reference to this file only). Am I missing
> install.sh? Is there a problem with the repository? Am I doing somethin=
g
> fundamentally wrong?
>
> Ian




From MAILER-DAEMON Thu Jan 09 15:15:44 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Wipf-0002R0-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 14:59:15 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WilB-0001XX-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 14:54:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wiiy-0001FL-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 14:52:32 -0500
Received: from mx2.magma.ca ([206.191.0.250])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Whcf-0003uB-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 13:41:45 -0500
Received: from mail3.magma.ca (mail3.magma.ca [206.191.0.221])
	by mx2.magma.ca (Magma Relay Server) with ESMTP id h09IfdKG019520
	for <bug-commoncpp@gnu.org>; Thu, 9 Jan 2003 13:41:39 -0500
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail3.magma.ca (Magma's Mail Server) with ESMTP id h09IfcRj027026
	for <bug-commoncpp@gnu.org>; Thu, 9 Jan 2003 13:41:38 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: <bug-commoncpp@gnu.org>
Date: Thu, 9 Jan 2003 13:41:33 -0500
Message-ID: <000501c2b80e$bbcc8170$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0006_01C2B7E4.D2F67970"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: 
Subject: RE: CVS repository problems?
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, 09 Jan 2003 19:59:13 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C2B7E4.D2F67970
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Ok, I screwed up a bit here. The difference between my first checkout
and the second was that the first checkout was against commoncpp2 and
the second against commoncpp, hence the difference in the file set that
was checked out.
 
So now, it would appear that commoncpp2 is missing the INSTALL file plus
all files in the config directory (install.sh). Maybe others. 
 
[commoncpp2]$ ./configure
creating cache ./config.cache
configure: error: can not find install-sh or install.sh in config
./config


-----Original Message-----
From: Ian Gough [mailto:igough@gridiron-networks.com] 
Sent: Thursday, January 09, 2003 1:25 PM
To: 'bug-commoncpp@gnu.org'
Subject: CVS repository problems?


This is the first time I have attempted to extract the commoncpp code
and I am seeing some strange behavior.
 
I am using anonymous CVS access checking out the commoncpp module. I get
no complaints from CVS, but there seems to be files that are not being
checked out. For example, the first attempt yielded an empty config
directory (except for the CVS subdir) and no INSTALL file. In the second
attempt the INSTALL file showed up, and I got Makefile.am to appear in
the config directory. Since there was no configure file, I ran autoconf
to generate it, but when running ./configure, it complains it "can not
find install-sh or install.sh in config ./config". A quick check of the
config directory shows that only Makefile.am is in that directory (and
the CVS Entries file has a reference to this file only). Am I missing
install.sh? Is there a problem with the repository? Am I doing something
fundamentally wrong?
 
Ian


------=_NextPart_000_0006_01C2B7E4.D2F67970
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D585342918-09012003>Ok, I=20
screwed up a bit here. The difference between my first checkout and the =
second=20
was that the first checkout was against commoncpp2 and the second =
against=20
commoncpp, hence the difference in the file set that was checked=20
out.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D585342918-09012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D585342918-09012003>So=20
now, it would appear that commoncpp2 is missing the INSTALL file plus =
all files=20
in the config directory (install.sh). Maybe others. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D585342918-09012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D585342918-09012003>[commoncpp2]$ ./configure<BR>creating cache=20
./config.cache<BR>configure: error: can not find install-sh or =
install.sh in=20
config ./config<BR></SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> Ian =
Gough=20
  [mailto:igough@gridiron-networks.com] <BR><B>Sent:</B> Thursday, =
January 09,=20
  2003 1:25 PM<BR><B>To:</B> 'bug-commoncpp@gnu.org'<BR><B>Subject:</B> =
CVS=20
  repository problems?<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D189121318-09012003><FONT face=3DArial size=3D2>This =
is the first=20
  time I have attempted to extract the commoncpp code and I am seeing =
some=20
  strange behavior.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D189121318-09012003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D189121318-09012003><FONT face=3DArial size=3D2>I am =
using=20
  anonymous CVS access checking out the commoncpp module. I get no =
complaints=20
  from CVS, but there seems to be files that are not being checked out. =
For=20
  example, the first attempt yielded an empty config directory (except =
for the=20
  CVS subdir) and no INSTALL file. In the second attempt the INSTALL =
file showed=20
  up, and I got Makefile.am to appear in the config directory. Since =
there was=20
  no configure file, I ran autoconf to generate it, but when running=20
  ./configure, it complains it "can not find install-sh or install.sh in =
config=20
  ./config". A quick check of the config directory shows that only =
Makefile.am=20
  is in that directory (and the CVS Entries file has a reference to this =
file=20
  only). Am I missing install.sh? Is there a problem with the =
repository? Am I=20
  doing something fundamentally wrong?</FONT></SPAN></DIV>
  <DIV><SPAN class=3D189121318-09012003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D189121318-09012003><FONT face=3DArial=20
  size=3D2>Ian</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0006_01C2B7E4.D2F67970--




From MAILER-DAEMON Thu Jan 09 15:34:29 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WjNl-0002ea-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 15:34:29 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Wj7n-0007RK-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 15:17:59 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wj2X-0005oN-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 15:12:46 -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 18Wj19-0005Xe-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 15:11:07 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8G00H0UQQH1Q@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 09 Jan 2003 12:11:05 -0800 (PST)
Date: Thu, 09 Jan 2003 12:11:05 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20030109133810.GK313@bulbasaur.rediris.es>
To: Federico Montesino Pouzols <fedemp@altern.org>,
 Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-id: <NBBBJJODBJBNJFNIDDCNAEBCDEAA.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
cc: bug-commoncpp@gnu.org
Subject: RE: Some issues with the codebase
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, 09 Jan 2003 20:34:28 -0000

(snip)

> 	I agree, many people discourage the use of leading underscores
> and there are good reasons for doing so. I believe there is no clear
> convention for this in Common C++. Personally, I would suggest to use
> trailing underscores in data members as a new recommendation for
> contributions, modifications and new code.

My personal opinion is they shouldn't be used period. and if they must, then
only as a word separator.  I'm also of the opinion that cryptic
abbreviations should not be used, especially in external api's.

I also like the "java" style with infix caps except the first word (ie.
getMyProperty, setMyProperty, doSomething, isActive...) and then classes
using plain infix caps (i.e. Digest, Thread, CRCDigest...)  for the most
part the areas I have used in common c++ seem to already be using that
style, except for a there are some places that use 'doSomething', and others
that use 'DoSomething'.  It would be nice to come up with a style guide for
all new code, and then slowly move the existing code that is out of spec
into spec deprecating the old method names, and at some point (say a major
release) removing them.

I'd be interested in doing some of this as I like a polished product, and it
gives me the chance to review and learning some parts of cc++ I may not
normally look at.  This is kind of why I like writing tests; I get the same
or better benifit by actually "trying" some of the classes/functions.  If I
was going to use a new area, I'd have to "test" it out anyway, because my
interpretation of how it works based on the docs may not be the same as how
it really works.

My opinion anyway. :)


(snip)
> > I think Common C++ deserves a vendor-neutral namespace, say... mmm...
> > "ccxx"? :-)
> >
>
> 	Well, from the beginning most of the development has been done
> by ost, so the choice of ost as namespace seems logical and fair. We
> could provide the alternative ccxx namespace, though it could lead to
> some confusion. Moreover, since ost is a corporation that truly and
> widely supports free software, I, as a free software developer who has
> found many troubles, and finally impossible to develop free software
> for software corporations, like that the merits of ost be
> recognized. In fact, ost is rather conspicuous about its support for
> free software. I think it is really good to find free software deeply
> related to commercial corporations. Hopefully, in the future we will
> see more free software created and mostly developed by commercial
> corporations, which perhaps looks a somewhat uncommon thing as opposed
> to free software projects that are created by independent volunteers
> and thus are vendor-neutral as for names.
>
> 	Of course, this is my personal point of view. If you or
> someone else in the list disagree, I would like to further discuss
> this issue.

on this, I think it makes sense to have a namespace carved out for the
product itself, since it is a library.  I'm not sure what ccxx is supposed
to mean (x's just placeholders for whatever?) but something that relates to
the lib would make sense.  I can see the bayonne project (is that an open
source telecom product?) using an ost namespace and any other ost specific
applications.  It's all a matter of preference, but when I first saw a
'using ost' declaration I had no clue what it meant.  cppunit uses cppunit
and the standard C++ lib uses std.  Perhaps having a vendor neutral
namespace would discourage bantering if and when (and I hope it happens)
there are more vendors contributing substantial parts to common c++.  too me
its not that big of a deal.  just my 2 cents and opinion.

cheers,

Chad




From MAILER-DAEMON Thu Jan 09 18:22:20 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Wlzh-00037q-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:21:49 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Wlx1-0002NR-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:19:03 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wlrm-00019U-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:13:49 -0500
Received: from ns2.envia-tel.net ([193.98.112.146])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Wlq5-0000kb-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:11:53 -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 h09NBpB4016393
	for <bug-commoncpp@gnu.org>; Fri, 10 Jan 2003 00:11:52 +0100
Received: by mailserver.wige-data.de with Internet Mail Service (5.5.2653.19)
	id <CFLZCWX8>; Fri, 10 Jan 2003 00:11:46 +0100
Received: from wige-data.de (dialin-145-254-178-241.arcor-ip.net
	[145.254.178.241]) by mailserver.wige-data.de with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2653.13)
	id CFLZCWX7; Fri, 10 Jan 2003 00:11:43 +0100
From: taraben.a@wige-data.de
To: bug-commoncpp@gnu.org
Message-ID: <3E1E01CC.1040709@wige-data.de>
Date: Fri, 10 Jan 2003 00:12:12 +0100
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Some issues with the codebase
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, 09 Jan 2003 23:21:48 -0000

  Chad Yates wrote:

>...
>
>My personal opinion is they shouldn't be used period. and if they must, then
>only as a word separator.  I'm also of the opinion that cryptic
>abbreviations should not be used, especially in external api's.
>
+1  from my side.

>I also like the "java" style with infix caps except the first word (ie.
>getMyProperty, setMyProperty, doSomething, isActive...) and then classes
>using plain infix caps (i.e. Digest, Thread, CRCDigest...)  for the most
>
but then how do you differ between class and instance.

>part the areas I have used in common c++ seem to already be using that
>style, except for a there are some places that use 'doSomething', and others
>that use 'DoSomething'.  It would be nice to come up with a style guide for
>all new code, and then slowly move the existing code that is out of spec
>into spec deprecating the old method names, and at some point (say a major
>release) removing them.
>  
>
In my opinion there should be a clear difference in between type, 
instance, constant, method (do,get,set), local or privat member member, 
global variable. Did I miss something?

>...
>
>on this, I think it makes sense to have a namespace carved out for the
>product itself, since it is a library.  I'm not sure what ccxx is supposed
>to mean (x's just placeholders for whatever?) but something that relates to
>the lib would make sense.  I can see the bayonne project (is that an open
>source telecom product?) using an ost namespace and any other ost specific
>applications.  It's all a matter of preference, but when I first saw a
>'using ost' declaration I had no clue what it meant.  cppunit uses cppunit
>and the standard C++ lib uses std.  Perhaps having a vendor neutral
>namespace would discourage bantering if and when (and I hope it happens)
>there are more vendors contributing substantial parts to common c++.  too me
>its not that big of a deal.  just my 2 cents and opinion.
>
>cheers,
>
>Chad
>
>  
>
why not simple using comm ?? placeholder for common c++ or communication :-)

I think this is a very esotheric issue and so many different opinions 
around ... so sorry for bugging you ;-)

Adib.





From MAILER-DAEMON Thu Jan 09 18:28:04 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Wm5k-0004JC-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:28:04 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Wm5i-0004In-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:28:02 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wm4Y-0003yf-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:27:02 -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 18Wlpe-0000eL-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:11:26 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8G00DHIZ30F0@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 09 Jan 2003 15:11:25 -0800 (PST)
Date: Thu, 09 Jan 2003 15:11:25 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp <bug-commoncpp@gnu.org>
Message-id: <NBBBJJODBJBNJFNIDDCNIEBFDEAA.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: Some issues with the codebase
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, 09 Jan 2003 23:28:02 -0000

(snip)
> I don't quite agree with using only a trailing underscore. Invariably
> you're going to make a typo somewhere, and leave out an underscore,
> which could be pretty disastrous if you start calling your parameters
> in your constructors and "set" methods the same as the members, without
> the underscore.
>
> CppUnit seems to call all their member variables "m_<membername>". I
> haven't decided if this convention is optimal, or whether it qualifies
> as some kind of quasi-Hungarian notation (Very, Very Evil(TM)), but I
> think it's better than the trailing underscore convention.
>
> I'd be interested to hear what other people suggest in this regard.

m_ very bad, unless your writing straight c and need a way to "simulate" a
class.  but in c++ it is obvious what it is when using the class.

MyClass a

a.getMyValue(); obviously a method due to the . and the ()
a.myValue; is a member, it can't be any other way (that I know of anyway)
a.m_myValue;  confusing to read.

MyClass mc_a;
mc_a.m_uMyValue; Even more confusing! (languages should have arbitrary
                 languages encoded, differently by everyone, where it
                 can be avoided.

the above was a MyClass (mc) access to a member variable (m_) that happens
to be an unsigned datatype (u) called MyValue.  what a mess! just look at
windows code.

eventually we will all be using more structured development environments and
hungarian notation and these bastarizagions ;) of the language will not have
*any* purpose but confusion, as the environment will tell you the type your
dealing with at a moments notice.

Mind you if it's an iternal function, it doesn't matter as much to me,
although I still like the same consistency if given a choice.

(snip)
> However, I don't think you've really addressed my issues with company
> names in namespaces. What if a new company, say ACME Inc., takes an
> active interest in developing Common C++ and contributes much code.
> Are we then going to split stuff up into "ost" and "acme" namespaces?
> I think not.
(snip)

yip, that could be a political/control/recognition issue.

(snip)

Did I say, I love the potential that common c++ has, hence the reason I've
started developing with it and contributing to it, and trying to think about
getting it more exposure and polish.

Thanks for starting such a sweet project!

,Chad




From MAILER-DAEMON Thu Jan 09 19:02:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Wmcc-0003bS-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 19:02:02 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Wmca-0003aI-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 19:02:00 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WmcO-0003Uf-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 19:01:59 -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 18Wm4U-0003xb-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:26:47 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8G00FFSZSLB4@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 09 Jan 2003 15:26:46 -0800 (PST)
Date: Thu, 09 Jan 2003 15:26:45 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp <bug-commoncpp@gnu.org>
Message-id: <NBBBJJODBJBNJFNIDDCNOEBGDEAA.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: Some issues with the codebase
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, 10 Jan 2003 00:02:01 -0000

> >I also like the "java" style with infix caps except the first word (ie.
> >getMyProperty, setMyProperty, doSomething, isActive...) and then classes
> >using plain infix caps (i.e. Digest, Thread, CRCDigest...)  for the most
> >
> but then how do you differ between class and instance.

this is an interesting point.  in the past I typically have used the naming
convention for methods. first letter lowercase, infix afterwards. but
sometimes underscores.

TCPSession clientSession;
or:
TCPSession client_session;
or (if compactness is key to it's readability and the number of local
    variables are limited), something like:
TCPSession clnt_ses;
or some other type.

Whichever way, I try and specialize the name away from the general class
name, afterall an instance isn't a general class, it's a very specific
object built using the class as a "guide" Car -> playerVehicle/playerCar for
a game, or vector<Car> favoriteCars. :) It's really not as important since
it's not a part of the "public" api. My opinion/style anyway.

> >part the areas I have used in common c++ seem to already be using that
> >style, except for a there are some places that use
> 'doSomething', and others
> >that use 'DoSomething'.  It would be nice to come up with a
> style guide for
> >all new code, and then slowly move the existing code that is out of spec
> >into spec deprecating the old method names, and at some point
> (say a major
> >release) removing them.
> >
> >
> In my opinion there should be a clear difference in between type,
> instance, constant, method (do,get,set), local or privat member member,
> global variable. Did I miss something?

After writing this and then checking out the latest patches/changes, I
discovered there is a Code style written up, it's in the texi documentation
(I still haven't figured out how to view).

If you want to know what I typically use:

1) Types: named like classes since they are in the same family and
   represent an object/primitive of some sort.
2) Instances/Attributes/Variables: named like methods but more lax.
3) Constants: all UPPERCASE, PI, MAX_SIZE, enum {RED, GREEN, BLUE}
4) Methods: as above, typcially verb prefix + (processJob, addElement..)
5) Private: in the private section of the class declaration. no
   distinction from other member variables (hey they may start public,
   but then be moved to private or vice versa.
6) Global: ?? I don't use these except under extreme conditions. but I
   would expect same as Methods and Member variables

> why not simple using comm ?? placeholder for common c++ or
> communication :-)
>
> I think this is a very esotheric issue and so many different opinions
> around ... so sorry for bugging you ;-)

It's really a can of worms isn't it. or maybe snakes. :)

Later!

chad




From MAILER-DAEMON Thu Jan 09 19:22:47 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WmPV-0000de-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:48:29 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WmBp-0005qz-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:34:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wm64-0004PJ-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:28:35 -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 18Wm29-0003cm-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 18:24:21 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8G00DOXZOKF0@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 09 Jan 2003 15:24:20 -0800 (PST)
Date: Thu, 09 Jan 2003 15:24:20 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <NBBBJJODBJBNJFNIDDCNIEBFDEAA.cyates@uidaho.edu>
To: bug-commoncpp <bug-commoncpp@gnu.org>
Message-id: <NBBBJJODBJBNJFNIDDCNIEBGDEAA.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: RE: Some issues with the codebase
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, 09 Jan 2003 23:48:27 -0000

Oops a couple of nasty typos.

> mc_a.m_uMyValue; Even more confusing! (languages should have arbitrary
>                  languages encoded, differently by everyone, where it
>                  can be avoided.

should = shouldn't

> eventually we will all be using more structured development
> environments and hungarian notation and these bastarizagions ;)
> of the language will not have *any* purpose but confusion, as the
> environment will tell you the type your dealing with at a moments notice.

bastarizagions = bastardizations -- if I'm going to use slang, please let me
use it right :)

I'm going to leave it at that, I don't want this to become one of those long
pointless threads.  I finally found common c++'s developer style guide, and
I think it looks pretty good from my initial skimming.

,Chad




From MAILER-DAEMON Fri Jan 10 00:08:33 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Wqx3-0003fg-00
	for mharc-bug-commoncpp@gnu.org; Thu, 09 Jan 2003 23:39:25 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Wqw2-0003Jc-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 23:38:22 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WqtB-0002Th-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 23:35:29 -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 18Wnmq-0003HV-00
	for bug-commoncpp@gnu.org; Thu, 09 Jan 2003 20:16:41 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8H00C014VRX3@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 09 Jan 2003 17:16:40 -0800 (PST)
Date: Thu, 09 Jan 2003 17:16:39 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20030109105348.GG313@bulbasaur.rediris.es>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-id: <NBBBJJODBJBNJFNIDDCNAEBJDEAA.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
cc: bug-commoncpp@gnu.org
Subject: RE: urlstring testing/enhancement
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, 10 Jan 2003 04:39:24 -0000


> > I also added Base64 functions that take std::string arguments
> for the encode
> > output and the decode input.  I don't know where the line is
> supposed to be
> > relating to string usage as I see most of common c++ is char* based, but
> > there seems to be std::string usage in some classes.  personally I like
> > having it as an overload option.  I can post diffs showing the
> new functions
> > if they are wanted.
> >
>
> 	I think we should include these new functions. For the last
> months some things have been changed and updated to progresively
> incorporate string as preferred to char*. These new functions do not
> break backwards compatibility, so I see no reason to not include it.

before I post a patch to add the new STL string functions I was wondering if
somebody knew the prefered way of dealing with excessive temporaries.  see
the following:

/** @relates URLStream
 * Encode a octet stream using base64 coding into a STL string
 * @return base 64 encoded string
 * @param src     source buffer
 * @param srcsize source buffer size
 */
CCXX_EXPORT(std::string) b64Encode(const unsigned char *src, size_t srcsize)
{
  size_t limit = (srcsize+2)/3*4+1;
  char* buffer = new char[limit];

  unsigned size = b64Encode(src, srcsize, buffer, limit);
  buffer[size] = '\0';

  std::string final = string(buffer);
  delete buffer;
  return final;
}

notice that I have to not only allocate a temporary buffer (since the
b64Encode function doesn't work with strings directly -- or some kind
streaming), but I have to make a copy before I unallocate it, and then yet
another on the actual return by value.  I have yet to delve into the realm
of autoptr's.  is that the best bet?  if so, the stl autoptr, or does common
c++ have a better one.

thanks,

Chad




From MAILER-DAEMON Fri Jan 10 13:55:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18X4JG-0002VI-00
	for mharc-bug-commoncpp@gnu.org; Fri, 10 Jan 2003 13:55:14 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18X4JD-0002Um-00
	for bug-commoncpp@gnu.org; Fri, 10 Jan 2003 13:55:11 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18X4JB-0002UY-00
	for bug-commoncpp@gnu.org; Fri, 10 Jan 2003 13:55:10 -0500
Received: from mx2.magma.ca ([206.191.0.250])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18X4JB-0002SV-00
	for bug-commoncpp@gnu.org; Fri, 10 Jan 2003 13:55:09 -0500
Received: from mail1.magma.ca (mail1.magma.ca [206.191.0.252])
	by mx2.magma.ca (Magma Relay Server) with ESMTP id h0AIt73C003936
	for <bug-commoncpp@gnu.org>; Fri, 10 Jan 2003 13:55:07 -0500
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail1.magma.ca (Magma's Mail Server) with ESMTP id h0AIt5jM029757
	for <bug-commoncpp@gnu.org>; Fri, 10 Jan 2003 13:55:05 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: "'bug-commoncpp'" <bug-commoncpp@gnu.org>
Date: Fri, 10 Jan 2003 13:55:06 -0500
Message-ID: <001101c2b8d9$ca84f3c0$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0012_01C2B8AF.E1AEEBC0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Subject: Building CC++ on Mac OS X
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, 10 Jan 2003 18:55:12 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0012_01C2B8AF.E1AEEBC0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Has anybody built Common C++ on Mac OS X (FreeBSD based) yet? If so, is
there a trick to get the system built or should it be built differently
from, say Linux? I have already figured out the libtoolize-glibtoolize
problem, but the automake system doesn't seem to recognize this as a BSD
system. How does the freebsd subdir fit into the equation?
 
 

------=_NextPart_000_0012_01C2B8AF.E1AEEBC0
Content-Type: text/html;
	charset="US-ASCII"
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=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D863491518-10012003>Has =
anybody built=20
Common C++ on Mac OS X (FreeBSD based) yet? If so, is there a trick to =
get the=20
system built or should it be built differently from, say Linux? I have =
already=20
figured out the libtoolize-glibtoolize problem, but the automake system =
doesn't=20
seem to recognize this as a BSD system. How does the freebsd subdir fit =
into the=20
equation?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D863491518-10012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D863491518-10012003>&nbsp;</DIV></SPAN></FONT></BODY></HTML>

------=_NextPart_000_0012_01C2B8AF.E1AEEBC0--




From MAILER-DAEMON Sat Jan 11 08:56:42 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XLzE-00042O-00
	for mharc-bug-commoncpp@gnu.org; Sat, 11 Jan 2003 08:47:44 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XLz0-0003C7-00
	for bug-commoncpp@gnu.org; Sat, 11 Jan 2003 08:47:30 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XLy6-0000Vm-00
	for bug-commoncpp@gnu.org; Sat, 11 Jan 2003 08:46:34 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XLy1-0000HS-00
	for bug-commoncpp@gnu.org; Sat, 11 Jan 2003 08:46:29 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18XLym-0002dq-00; Sat, 11 Jan 2003 14:47:16 +0100
Date: Sat, 11 Jan 2003 14:47:15 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ian Gough <igough@gridiron-networks.com>
Message-ID: <20030111134715.GB10068@bulbasaur.rediris.es>
Mail-Followup-To: Ian Gough <igough@gridiron-networks.com>,
	'bug-commoncpp' <bug-commoncpp@gnu.org>
References: <001101c2b8d9$ca84f3c0$0c02a8c0@gridironnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001101c2b8d9$ca84f3c0$0c02a8c0@gridironnetworks.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
Subject: Re: Building CC++ on Mac OS X
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: Sat, 11 Jan 2003 13:47:41 -0000


	I do not recall any report of cc++ working on Max OS X, the
autotools things should work however. What troubles did you find? The
files in freebsd/ are meant to build packages for the ports collection
through the freebsd pkg tools.

On Fri, Jan 10, 2003 at 01:55:06PM -0500, Ian Gough wrote:
> Has anybody built Common C++ on Mac OS X (FreeBSD based) yet? If so, is
> there a trick to get the system built or should it be built differently
> from, say Linux? I have already figured out the libtoolize-glibtoolize
> problem, but the automake system doesn't seem to recognize this as a BSD
> system. How does the freebsd subdir fit into the equation?
>  
>  
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Tue Jan 14 08:13:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YQqf-0003Jx-00
	for mharc-bug-commoncpp@gnu.org; Tue, 14 Jan 2003 08:11:21 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YNC3-0004lz-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 04:17:11 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YNC1-0004iA-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 04:17:10 -0500
Received: from cpe-203-51-32-67.nsw.bigpond.net.au ([203.51.32.67]
	helo=purcell.homeip.net)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18YNC0-0004fl-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 04:17:08 -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 18YNBx-0007gG-00; Tue, 14 Jan 2003 20:17:05 +1100
Received: from msp by htpc.purcell.homeip.net with local (Exim 3.36 #1
	(Debian))	id 18YNBv-0003mB-00; Tue, 14 Jan 2003 20:17:03 +1100
Date: Tue, 14 Jan 2003 20:17:02 +1100
From: Mark Purcell <msp@debian.org>
To: bug-commoncpp@gnu.org
Message-ID: <20030114091702.GC3512@htpc.purcell.homeip.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="LyciRD1jyfeSSjG0"
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-Operating-System: Linux/2.4.20-686 (i686)
X-Uptime: 20:13:13 up 12:01,  4 users,  load average: 1.13, 1.05, 0.56
Sender: Mark Purcell <msp@htpc.purcell.homeip.net>
X-Mailman-Approved-At: Tue, 14 Jan 2003 08:11:19 -0500
cc: GerhardTonn@gammatau.de
cc: 173081-forwarded@bugs.debian.org
Subject: [GerhardTonn@gammatau.de: Bug#173081: patch attached]
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, 14 Jan 2003 09:17:11 -0000


--LyciRD1jyfeSSjG0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi David (and others),

I have received this patch from Gerhard Tonn for the problem we had buildin=
g=20
commoncpp2 on a number of different architectures; s390, powerpc, hppa,=20
sparc, mips & m68k.

I have included this patch in the Debian GNU/Linux packaged version of=20
commoncpp2, but you might also like to include in the upstream source.

Thanks,
Mark

http://bugs.debian.org/src:libcommoncpp2

----- Forwarded message from Gerhard Tonn <GerhardTonn@gammatau.de> -----

From: Gerhard Tonn <GerhardTonn@gammatau.de>
Date: Sun, 12 Jan 2003 13:16:02 +0100
To: 173081@bugs.debian.org
X-Mailer: KMail [version 1.1.99]
Subject: Bug#173081: patch attached
Reply-To: Gerhard Tonn <GerhardTonn@gammatau.de>,
	173081@bugs.debian.org

Hi,
attached is a patch that fixes the problem.

Regards,
Gerhard
--- include/cc++/socket.h.bak	2003-01-12 12:07:14.000000000 +0000
+++ include/cc++/socket.h	2003-01-12 11:50:32.000000000 +0000
@@ -305,6 +305,8 @@
          * inet_addr() or htonl()=20
 	 */
 	InetAddress &operator=3D(unsigned long addr);
+	inline InetAddress &operator=3D(unsigned int addr)
+		{return *this =3D (unsigned long) addr;}
=20
 	inline bool operator!() const
 		{return !isInetAddress();};


----- End forwarded message -----

--LyciRD1jyfeSSjG0
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+I9WOoCzanz0IthIRAhacAKCYzycKNPZtk2h+uQp04MiQn6+krgCfa66m
ZGW2p6KOig5pbqhVKoJBr94=
=mYZc
-----END PGP SIGNATURE-----

--LyciRD1jyfeSSjG0--



From MAILER-DAEMON Tue Jan 14 08:13:03 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YQqf-0003Jw-00
	for mharc-bug-commoncpp@gnu.org; Tue, 14 Jan 2003 08:11:21 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YN6b-0004sU-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 04:11:33 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YN6B-00044Q-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 04:11:09 -0500
Received: from cpe-203-51-32-67.nsw.bigpond.net.au ([203.51.32.67]
	helo=purcell.homeip.net)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18YN5z-0003KE-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 04:10:55 -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 18YN5q-0007e6-00; Tue, 14 Jan 2003 20:10:46 +1100
Received: from msp by htpc.purcell.homeip.net with local (Exim 3.36 #1
	(Debian))	id 18YN5l-0002qO-00; Tue, 14 Jan 2003 20:10:41 +1100
Date: Tue, 14 Jan 2003 20:10:40 +1100
From: Mark Purcell <msp@debian.org>
To: bug-commoncpp@gnu.org
Message-ID: <20030114091040.GB3512@htpc.purcell.homeip.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb"
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-Operating-System: Linux/2.4.20-686 (i686)
X-Uptime: 20:07:35 up 11:56,  4 users,  load average: 1.89, 0.60, 0.24
Sender: Mark Purcell <msp@htpc.purcell.homeip.net>
X-Mailman-Approved-At: Tue, 14 Jan 2003 08:11:19 -0500
cc: 176525-forwarded@bugs.debian.org
cc: Peter Toneby <peter@toneby.com>
Subject: [peter@toneby.com: Bug#176525: libcommoncpp2-dev: error in
 declaration of nanosleep]
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, 14 Jan 2003 09:11:44 -0000


--VS++wcV0S1rZb1Fb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi David (and others),

I have received this bug report for commoncpp2 and have included in the
Debian GNU/Linux package of commoncpp2.

You might like to investigate and include in the upstream source.

Thanks,
Mark

http://bugs.debian.org/libcommoncpp2

----- Forwarded message from Peter Toneby <peter@toneby.com> -----

From: Peter Toneby <peter@toneby.com>
Date: Mon, 13 Jan 2003 15:37:51 +0100
To: Debian Bug Tracking System <submit@bugs.debian.org>
X-Mailer: reportbug 2.10
Subject: Bug#176525: libcommoncpp2-dev: error in declaration of nanosleep
Reply-To: Peter Toneby <peter@toneby.com>, 176525@bugs.debian.org

Package: libcommoncpp2-dev
Version: 1.0.7-2
Severity: grave
Tags: upstream
Justification: renders package unusable

SAFE -DHAVE_CONFIG_H -D_GNU_SOURCE -c main.cpp -o main.o
In file included from /usr/include/cc++2/cc++/socket.h:50,
                 from main.cpp:2:
/usr/include/cc++2/cc++/config.h:524: declaration of `int nanosleep(const=
=20
   timespec*, timespec*)' throws different exceptions
/usr/include/time.h:320: than previous declaration `int nanosleep(const=20
   timespec*, timespec*) throw ()'
make: *** [main.o] Error 1

Adding "throw()" to the end (before ";") of /usr/include/cc++2/cc++/config.=
h=20
fixes this.

/Peter Toneby

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux evelina 2.4.20 #1 SMP Mon Dec 16 15:08:49 CET 2002 i686
Locale: LANG=3Dswedish, LC_CTYPE=3Dsv_SE

Versions of packages libcommoncpp2-dev depends on:
ii  libcommoncpp2-1.0-0c102       1.0.7-2    A GNU package for creating por=
tabl

-- no debconf information



----- End forwarded message -----

--VS++wcV0S1rZb1Fb
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+I9QQoCzanz0IthIRAuw3AJ9uzhL3osa8QVbUhpDYGIUGl1RvUwCfWfj9
2Pu8BaUJ2b2nbWMvnLMR3t8=
=s5Kt
-----END PGP SIGNATURE-----

--VS++wcV0S1rZb1Fb--



From MAILER-DAEMON Tue Jan 14 12:31:32 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YUuN-0004dr-00
	for mharc-bug-commoncpp@gnu.org; Tue, 14 Jan 2003 12:31:27 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YUtI-0003m5-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 12:30:20 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YUsR-0002fO-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 12:29:33 -0500
Received: from mx1.magmacom.com ([206.191.0.217])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18YUsF-0002IF-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 12:29:15 -0500
Received: from mail4.magma.ca (mail4.magma.ca [206.191.0.222])
	h0EHTCkb027800;	Tue, 14 Jan 2003 12:29:12 -0500 (EST)
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail4.magma.ca (Magma's Mail Server) with ESMTP id h0EHT2Lm024764;
	Tue, 14 Jan 2003 12:29:11 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: "'Federico Montesino Pouzols'" <fedemp@altern.org>
Date: Tue, 14 Jan 2003 12:28:59 -0500
Message-ID: <001601c2bbf2$73fdae40$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <20030111134715.GB10068@bulbasaur.rediris.es>
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
Subject: RE: Building CC++ on Mac OS X
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, 14 Jan 2003 17:31:26 -0000

Here is what I found. Unfortunatly, I am not familiar with the
autotools, so I cannot make the changes to that part of the code with
any degree of confidence, so I hacked files and makefiles to get it to
build. I will leave it to somebody confident with the autotools to
figure out how to fix this in the proper manner. Note that this only
gets it to build, though the demos still have build problems that I
didn't look into yet (../include/cc++/xml.h:323:2: #error "XML support
is not available.")

I am in the process of testing the lib now.

1) in thread.cpp: sched_getscheduler does not exist on the Mac so I
added -D__FreeBSD__=4 to CXXFLAGS in the Makefile

2) in file.cpp: lockf is not fully implemented on the Mac; the structs
are there and the symbolic constants, but the function signature is
missing from the include files. So, though HAVE_SYS_FILE_H is defined,
which causes sys/file.h to be included, which defines F_LOCK, there is
no lockf so the lockf included in file.cpp needs to be used. Added -DMAC
to the makefile and added code in file.cpp to cause its version of lockf
to be conditionally compiled when MAC is set.

3) in socket.h: socklen_t is undefined. I found references on the inet
that spec that FreeBSD prior to 4.x and Solaris prior to 7 (2.7) do not
define the type socklen_t and some of the mac os X is based on FreeBSD
4.4. To cause this to be defined, I included -D_BSD_SOCKLEN_T_=int in
the Makefile.

4) in network.cpp:
g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
-g -O2 -D_GNU_SOURCE -D__FreeBSD__=4 -DMAC -D_BSD_SOCKLEN_T_=int -Wall
-ansi -pedantic -I../include -c network.cpp -MT network.lo -MD -MP -MF
.deps/network.TPlo  -fno-common -DPIC -o .libs/network.lo
network.cpp: In function `bool
   ost::enumNetworkDevices(std::vector<ost::NetworkDeviceInfo,
   std::allocator<ost::NetworkDeviceInfo> >&)':
network.cpp:110: ambiguous overload for `ost::InetAddress& = u_int32_t'
   operator
../include/cc++/socket.h:300: candidates are: ost::InetAddress&
   ost::InetAddress::operator=(const char*)
../include/cc++/socket.h:308:                 ost::InetAddress&
   ost::InetAddress::operator=(long unsigned int)
make: *** [network.lo] Error 1

Added a new assignment operator to c++/socket.h as specified in email
from Mark Purcell
	inline InetAddress &operator=(unsigned int addr)
		{return *this = (unsigned long) addr;}

5) in serial.cpp
g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
-g -O2 -D_GNU_SOURCE -D__FreeBSD__=4 -DMAC -D_BSD_SOCKLEN_T_=int -Wall
-ansi -pedantic -I../include -c serial.cpp -MT serial.lo -MD -MP -MF
.deps/serial.TPlo  -fno-common -DPIC -o .libs/serial.lo
serial.cpp: In member function `void ost::Serial::initConfig()':
serial.cpp:203: `ioctl' undeclared (first use this function)
serial.cpp:203: (Each undeclared identifier is reported only once for
each
   function it appears in.)

Added
#include <sys/ioctl.h>
to serial.cpp


-----Original Message-----
From: Federico Montesino Pouzols [mailto:fedemp@bulbasaur.rediris.es] On
Behalf Of Federico Montesino Pouzols
Sent: Saturday, January 11, 2003 8:47 AM
To: Ian Gough
Cc: 'bug-commoncpp'
Subject: Re: Building CC++ on Mac OS X



	I do not recall any report of cc++ working on Max OS X, the
autotools things should work however. What troubles did you find? The
files in freebsd/ are meant to build packages for the ports collection
through the freebsd pkg tools.

On Fri, Jan 10, 2003 at 01:55:06PM -0500, Ian Gough wrote:
> Has anybody built Common C++ on Mac OS X (FreeBSD based) yet? If so, 
> is there a trick to get the system built or should it be built 
> differently from, say Linux? I have already figured out the 
> libtoolize-glibtoolize problem, but the automake system doesn't seem 
> to recognize this as a BSD system. How does the freebsd subdir fit 
> into the equation?
>  
>  
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org 
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp





From MAILER-DAEMON Tue Jan 14 18:12:49 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YaDa-0003Mq-00
	for mharc-bug-commoncpp@gnu.org; Tue, 14 Jan 2003 18:11:38 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YaDU-0003JI-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 18:11:32 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YaC1-00023s-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 18:10:06 -0500
Received: from mx2.magma.ca ([206.191.0.250])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18YaC0-00020S-00
	for bug-commoncpp@gnu.org; Tue, 14 Jan 2003 18:10:00 -0500
Received: from mail3.magma.ca (mail3.magma.ca [206.191.0.221])
	by mx2.magma.ca (Magma Relay Server) with ESMTP id h0EN9w4n020188
	for <bug-commoncpp@gnu.org>; Tue, 14 Jan 2003 18:09:58 -0500
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail3.magma.ca (Magma's Mail Server) with ESMTP id h0EN9vRj019150
	for <bug-commoncpp@gnu.org>; Tue, 14 Jan 2003 18:09:58 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: <bug-commoncpp@gnu.org>
Date: Tue, 14 Jan 2003 18:09:56 -0500
Message-ID: <000201c2bc22$0e678350$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0003_01C2BBF8.25917B50"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: Thread problems on Mac OS X
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, 14 Jan 2003 23:11:37 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0003_01C2BBF8.25917B50
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

While trying out CC++ on Mac OS X, I found a problem that causes CC++ to
recurse to death.
 
When creating a Thread object, a Semaphore (joinSem) gets instantiated.
On this OS, the Semaphore constructor calls sem_init and if this fails,
calls getException(), which instantiates a Thread, which creates a
Semaphore, etc, causing the app to blow out the stack.
 
the following snippet from near line 130 in semaphore.cpp
 
Semaphore::Semaphore(size_t resource)
{
        if(sem_init(&_semaphore, 0, resource))
        {
                if(getException() == Thread::throwObject)
                        throw(this);

It seems that the sem_init is failing with ENOSYS, which means the
sem_init function is not implemented on this platform, nor is
sem_destroy(). It does seem though that sem_open() is implemented.
 
Perhaps the autotools need to test for correctly operating sem_init (one
that doesn't return -1 all the time!) and use sem_open() in that case.
 
Regardless of whether this gets done or not though, the recursion issue
should probably be addressed, even though it only occurs on a failed
sem_init() call.
 

------=_NextPart_000_0003_01C2BBF8.25917B50
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D039251121-14012003>While =
trying out=20
CC++ on Mac OS X, I found a problem that causes CC++ to recurse to=20
death.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D039251121-14012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D039251121-14012003>When =
creating a=20
Thread object, a Semaphore (joinSem) gets instantiated. On this OS, the=20
Semaphore constructor calls sem_init and if this fails, calls =
getException(),=20
which instantiates a Thread, which creates a Semaphore, etc, causing the =
app to=20
blow out the stack.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D039251121-14012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D039251121-14012003>the =
following=20
snippet from near line 130 in semaphore.cpp</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D039251121-14012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D039251121-14012003>Semaphore::Semaphore(size_t=20
resource)<BR>{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
if(sem_init(&amp;_semaphore, 0,=20
resource))<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
if(getException() =3D=3D=20
Thread::throwObject)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
throw(this);<BR></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D039251121-14012003>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D039251121-14012003>It =
seems that the=20
sem_init is failing with ENOSYS, which means the sem_init function is =
not=20
implemented on this platform, nor is sem_destroy(). It does =
seem&nbsp;though=20
that sem_open() is implemented.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D039251121-14012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D039251121-14012003>Perhaps the=20
autotools need to test for correctly operating sem_init (one that =
doesn't return=20
-1 all the time!) and use sem_open() in that case.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D039251121-14012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D039251121-14012003>Regardless of=20
whether this gets done or not though, the recursion issue should =
probably be=20
addressed, even though it only occurs on a failed sem_init()=20
call.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D039251121-14012003></SPAN></FONT>&nbsp;</DIV></DIV></SPAN></FONT>=
</BODY></HTML>

------=_NextPart_000_0003_01C2BBF8.25917B50--




From MAILER-DAEMON Wed Jan 15 07:17:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YmQQ-0001vU-00
	for mharc-bug-commoncpp@gnu.org; Wed, 15 Jan 2003 07:13:42 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YmMx-0000rh-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 07:10:07 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YmMN-0000YN-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 07:09:32 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18YmHN-0007ro-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 07:04:21 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18YmHz-0006FE-00; Wed, 15 Jan 2003 13:04:59 +0100
Date: Wed, 15 Jan 2003 13:04:58 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Mark Purcell <msp@debian.org>
Message-ID: <20030115120458.GB1340@bulbasaur.rediris.es>
Mail-Followup-To: Mark Purcell <msp@debian.org>, bug-commoncpp@gnu.org,
	176525-forwarded@bugs.debian.org, Peter Toneby <peter@toneby.com>
References: <20030114091040.GB3512@htpc.purcell.homeip.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030114091040.GB3512@htpc.purcell.homeip.net>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: 176525-forwarded@bugs.debian.org
cc: bug-commoncpp@gnu.org
cc: Peter Toneby <peter@toneby.com>
Subject: Re: [peter@toneby.com: Bug#176525: libcommoncpp2-dev: error in
 declaration of nanosleep]
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: Wed, 15 Jan 2003 12:13:41 -0000


	Umm, we already fixed this putting an #ifdef __FreeBSD__
around the declaration, since it seems to be necessary only on
FreeBSD, due to weird posix defines.

On Tue, Jan 14, 2003 at 08:10:40PM +1100, Mark Purcell wrote:
> Hi David (and others),
> 
> I have received this bug report for commoncpp2 and have included in the
> Debian GNU/Linux package of commoncpp2.
> 
> You might like to investigate and include in the upstream source.
> 
> Thanks,
> Mark
> 
> http://bugs.debian.org/libcommoncpp2
> 
> ----- Forwarded message from Peter Toneby <peter@toneby.com> -----
> 
> From: Peter Toneby <peter@toneby.com>
> Date: Mon, 13 Jan 2003 15:37:51 +0100
> To: Debian Bug Tracking System <submit@bugs.debian.org>
> X-Mailer: reportbug 2.10
> Subject: Bug#176525: libcommoncpp2-dev: error in declaration of nanosleep
> Reply-To: Peter Toneby <peter@toneby.com>, 176525@bugs.debian.org
> 
> Package: libcommoncpp2-dev
> Version: 1.0.7-2
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
> 
> SAFE -DHAVE_CONFIG_H -D_GNU_SOURCE -c main.cpp -o main.o
> In file included from /usr/include/cc++2/cc++/socket.h:50,
>                  from main.cpp:2:
> /usr/include/cc++2/cc++/config.h:524: declaration of `int nanosleep(const 
>    timespec*, timespec*)' throws different exceptions
> /usr/include/time.h:320: than previous declaration `int nanosleep(const 
>    timespec*, timespec*) throw ()'
> make: *** [main.o] Error 1
> 
> Adding "throw()" to the end (before ";") of /usr/include/cc++2/cc++/config.h 
> fixes this.
> 
> /Peter Toneby
> 
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux evelina 2.4.20 #1 SMP Mon Dec 16 15:08:49 CET 2002 i686
> Locale: LANG=swedish, LC_CTYPE=sv_SE
> 
> Versions of packages libcommoncpp2-dev depends on:
> ii  libcommoncpp2-1.0-0c102       1.0.7-2    A GNU package for creating portabl
> 
> -- no debconf information
> 
> 
> 
> ----- End forwarded message -----



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




From MAILER-DAEMON Wed Jan 15 07:20:07 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YmVc-0004LL-00
	for mharc-bug-commoncpp@gnu.org; Wed, 15 Jan 2003 07:19:04 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YmRU-0002al-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 07:14:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YmQK-0001qY-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 07:13:37 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18YmFW-0007Kn-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 07:02:26 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18YmFx-0006F1-00; Wed, 15 Jan 2003 13:02:54 +0100
Date: Wed, 15 Jan 2003 13:02:53 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Mark Purcell <msp@debian.org>
Message-ID: <20030115120253.GA1340@bulbasaur.rediris.es>
Mail-Followup-To: Mark Purcell <msp@debian.org>, bug-commoncpp@gnu.org,
	GerhardTonn@gammatau.de, 173081-forwarded@bugs.debian.org
References: <20030114091702.GC3512@htpc.purcell.homeip.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030114091702.GC3512@htpc.purcell.homeip.net>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: 173081-forwarded@bugs.debian.org
cc: GerhardTonn@gammatau.de
cc: bug-commoncpp@gnu.org
Subject: Re: [GerhardTonn@gammatau.de: Bug#173081: patch attached]
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: Wed, 15 Jan 2003 12:19:02 -0000


	Good, it is in CVS for 1.0.8.

On Tue, Jan 14, 2003 at 08:17:02PM +1100, Mark Purcell wrote:
> Hi David (and others),
> 
> I have received this patch from Gerhard Tonn for the problem we had building 
> commoncpp2 on a number of different architectures; s390, powerpc, hppa, 
> sparc, mips & m68k.
> 
> I have included this patch in the Debian GNU/Linux packaged version of 
> commoncpp2, but you might also like to include in the upstream source.
> 
> Thanks,
> Mark
> 
> http://bugs.debian.org/src:libcommoncpp2
> 
> ----- Forwarded message from Gerhard Tonn <GerhardTonn@gammatau.de> -----
> 
> From: Gerhard Tonn <GerhardTonn@gammatau.de>
> Date: Sun, 12 Jan 2003 13:16:02 +0100
> To: 173081@bugs.debian.org
> X-Mailer: KMail [version 1.1.99]
> Subject: Bug#173081: patch attached
> Reply-To: Gerhard Tonn <GerhardTonn@gammatau.de>,
> 	173081@bugs.debian.org
> 
> Hi,
> attached is a patch that fixes the problem.
> 
> Regards,
> Gerhard
> --- include/cc++/socket.h.bak	2003-01-12 12:07:14.000000000 +0000
> +++ include/cc++/socket.h	2003-01-12 11:50:32.000000000 +0000
> @@ -305,6 +305,8 @@
>           * inet_addr() or htonl() 
>  	 */
>  	InetAddress &operator=(unsigned long addr);
> +	inline InetAddress &operator=(unsigned int addr)
> +		{return *this = (unsigned long) addr;}
>  
>  	inline bool operator!() const
>  		{return !isInetAddress();};
> 
> 
> ----- End forwarded message -----



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




From MAILER-DAEMON Wed Jan 15 12:12:31 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Yr3Y-00046z-00
	for mharc-bug-commoncpp@gnu.org; Wed, 15 Jan 2003 12:10:24 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Yr39-0003tg-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 12:09:59 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Yr1T-0002lv-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 12:08:15 -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 18Yqzw-00025V-00; Wed, 15 Jan 2003 12:06:40 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h0FHfMe00508;
	Wed, 15 Jan 2003 12:41:22 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Mark Purcell <msp@debian.org>, bug-ccrtp@gnu.org, ccrtp-devel@gnu.org
Date: Wed, 15 Jan 2003 12:06:55 -0500
User-Agent: KMail/1.4.3
References: <20030115094528.GC663@htpc.purcell.homeip.net>
In-Reply-To: <20030115094528.GC663@htpc.purcell.homeip.net>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301151206.55821.dyfet@ostel.com>
cc: Ryan Murray <rmurray@cyberhqz.com>
cc: bug-commoncpp@gnu.org
Subject: Re: [rmurray@cyberhqz.com: Bug#176721:
 libccrtp_1.0pre0-1(mips/unstable): configure built with brokenlibtool.m4]
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, 15 Jan 2003 17:10:23 -0000

Mark,

for bug reports on ccrtp, the correct address is the list, bug-ccrtp@gnu.=
org. =20
That way more eyes get to look at it, and especially everyone with cvs=20
commit.  It would also be useful to pass it through the commonc++ list(s)=
=20
especially when (like this one) we are talking about a bug that effects=20
multiple packages.  I have an older "stable" reference system that I stil=
l=20
use for cutting all my primary "production release" tarballs for=20
distributions and I am loath to migrate it to a more recent GNU/Linux=20
distribution, though I probably should update automake/autoconf/libtool o=
n it=20
at least.

David

On Wednesday 15 January 2003 04:45, Mark Purcell wrote:
> David (and others),
>
> I have received the attached report from Ryan Murray regarding problems
> trying to autobuild ccrtp with a broken libtool.m4 on the mips
> architecture.
>
> As Ryan suggests this is fixed by updating all the libtool related file=
s
> in the source tree. I have applied this the to the Debian GNU/Linux sou=
rce
> tree for your application, but you might also like to update the upstre=
am
> source tree as well.
>
> Mark
>
> Btw, which is the correct address for bug reports, the included README =
file
> is not clear.
>
> ----- Forwarded message from Ryan Murray <rmurray@cyberhqz.com> -----
>
> From: rmurray@cyberhqz.com (Ryan Murray)
> Date: Tue, 14 Jan 2003 13:11:35 -0800
> To: submit@bugs.debian.org
> User-Agent: Mutt/1.3.28i
> Subject: Bug#176721: libccrtp_1.0pre0-1(mips/unstable): configure built
> with broken libtool.m4 Reply-To: rmurray@cyberhqz.com (Ryan Murray),
> 176721@bugs.debian.org
>
> Package: libccrtp
> Version: 1.0pre0-1
> Severity: serious
>
> There was an error while trying to autobuild your package:
> > Automatic build of libccrtp_1.0pre0-1 on resume.rfc822.org by sbuild/=
mips
> > 1.170 Build started at 20030107-1449
>
> [...]
>
> > ** Using build dependencies supplied by package:
> > Build-Depends: debhelper (>> 3.0.0), libcommoncpp2-dev, libxml2-dev
>
> The version of libtool used to build this source package is too old to
> correctly support shared libraries for the Debian mips and mipsel
> architectures.  At least version (1.4.2-7) and higher correctly support=
s
> them.  You need to update all of the libtool related files by running
> the following on your source tree:
>
> =09libtoolize --force --copy
> =09aclocal
> =09autoheader
> =09automake
> =09autoconf
>
> autoheader may not be needed, and you may need to use autoconf2.13
> rather than autoconf.
>
> You may also need to apply the patch in libtool bug #98342 if your
> package builds more than one library, where one library depends on the
> other.  Versions of libtool from 1.4.2-7.1 include a fix for this probl=
em
> already, so using the newest version is recommended.
>
> The correct 'configure' script will have output that looks like this:
> # This must be Linux ELF.
> linux-gnu*)
>   case $host_cpu in
>   alpha* | hppa* | i*86 | mips | mipsel | powerpc* | sparc* | ia64* | s=
390*
> ) lt_cv_deplibs_check_method=3Dpass_all ;;
>   *)
>
> Older versions of libtool used a file_magic check for the pattern
> file_magic ELF [0-9][0-9]*-bit [LM]SB (shared object|dynamic lib )
>
> The output of file(1) on a shared library on MIPS does not match this
> regular expression, however.  Earlier versions of file had been
> modified to match this regular expression, but the latest version uses
> the same output as upstream once again.  The file check often causes
> problems, and results on a build-dep on file that you might not
> otherwise be aware of.  The new method doesn't need file(1) at all,
> and is far less fragile, so it is best to upgrade the configure script
> with proper mips support.
>
>
> ----- End forwarded message -----




From MAILER-DAEMON Wed Jan 15 15:07:42 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Ytp7-0004wy-00
	for mharc-bug-commoncpp@gnu.org; Wed, 15 Jan 2003 15:07:41 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Ytp5-0004vY-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 15:07:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Ytp4-0004tu-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 15:07:38 -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 18YtnL-0004Mp-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 15:05:52 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h0FKeZe01815;
	Wed, 15 Jan 2003 15:40:35 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: "Ian Gough" <igough@gridiron-networks.com>, <bug-commoncpp@gnu.org>
Date: Wed, 15 Jan 2003 15:06:10 -0500
User-Agent: KMail/1.4.3
References: <000201c2bc22$0e678350$0c02a8c0@gridironnetworks.com>
In-Reply-To: <000201c2bc22$0e678350$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301151506.10766.dyfet@ostel.com>
Subject: Re: Thread problems on Mac OS X
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, 15 Jan 2003 20:07:40 -0000

I suppose we can check errno for ENOSYS and then have it try sem_open ins=
tead. =20
A naming scheme for generating valid and unique names (perhaps by pid and=
=20
seq) would also need to be used...

On Tuesday 14 January 2003 18:09, Ian Gough wrote:
> While trying out CC++ on Mac OS X, I found a problem that causes CC++ t=
o
> recurse to death.
>
> When creating a Thread object, a Semaphore (joinSem) gets instantiated.
> On this OS, the Semaphore constructor calls sem_init and if this fails,
> calls getException(), which instantiates a Thread, which creates a
> Semaphore, etc, causing the app to blow out the stack.
>
> the following snippet from near line 130 in semaphore.cpp
>
> Semaphore::Semaphore(size_t resource)
> {
>         if(sem_init(&_semaphore, 0, resource))
>         {
>                 if(getException() =3D=3D Thread::throwObject)
>                         throw(this);
>
> It seems that the sem_init is failing with ENOSYS, which means the
> sem_init function is not implemented on this platform, nor is
> sem_destroy(). It does seem though that sem_open() is implemented.
>
> Perhaps the autotools need to test for correctly operating sem_init (on=
e
> that doesn't return -1 all the time!) and use sem_open() in that case.
>
> Regardless of whether this gets done or not though, the recursion issue
> should probably be addressed, even though it only occurs on a failed
> sem_init() call.




From MAILER-DAEMON Wed Jan 15 19:56:35 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YyKL-0003rj-00
	for mharc-bug-commoncpp@gnu.org; Wed, 15 Jan 2003 19:56:13 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YyKB-0003Oq-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 19:56:03 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YyK6-00038K-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 19:56:00 -0500
Received: from mke-24-167-199-83.wi.rr.com ([24.167.199.83]
	helo=gandalf.libertyetech.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18YyJm-0001xU-00
	for bug-commoncpp@gnu.org; Wed, 15 Jan 2003 19:55:38 -0500
Received: from frodo.libertyetech.com ([192.168.1.2] ident=mail)
	by gandalf.libertyetech.com with esmtp (Exim 3.36 #1 (Debian))
	id 18YyJh-0002Kw-00
	for <bug-commoncpp@gnu.org>; Wed, 15 Jan 2003 18:55:33 -0600
Received: from danielb by frodo.libertyetech.com with local (Exim 3.36 #1
	(Debian))	id 18YyJe-0008Dr-00
	for <bug-commoncpp@gnu.org>; Wed, 15 Jan 2003 18:55:30 -0600
Date: Wed, 15 Jan 2003 18:55:30 -0600
From: Daniel E Baumann <danielb@libertyetech.com>
To: bug-commoncpp@gnu.org
Message-ID: <20030116005530.GA31601@frodo.libertyetech.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="BOKacYhQ+x31HxR3"
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: Daniel E Baumann <danielb@mail.libertyetech.com>
Subject: Small Patch for Piostreams due to -pedantic and -ansi
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, 16 Jan 2003 00:56:10 -0000


--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Ummm, here's a patch I made to fix various issues with compiling
piostreams in commoncpp2 cvs. Seems -pedantic ans -ansi were just
added? Well at any rate they helped me find some bugglets. Please
apply ASAP :).

Dan
-- 
And if cynics ridicule freedom, ridicule community...if ``hard nosed 
realists'' say that profit is the only ideal...just ignore them, and use 
copyleft all the same.
      -- RMS

Was I helpful?  Let others know: 
  http://svcs.affero.net/rm.php?r=chillywilly

--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="piostreams.diff"

Index: include/cc++/pios_init.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/pios_init.h,v
retrieving revision 1.1
diff -u -3 -p -r1.1 pios_init.h
--- include/cc++/pios_init.h	21 Sep 2002 18:26:57 -0000	1.1
+++ include/cc++/pios_init.h	13 Jan 2003 21:01:09 -0000
@@ -81,7 +81,7 @@ private:
 } // namespace ost
 #endif
 
-#endif /* CCXX_PIOS_INIT_H
+#endif // CCXX_PIOS_INIT_H 
 /** EMACS **
  * Local variables:
  * mode: c++
Index: include/cc++/pistream
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/pistream,v
retrieving revision 1.1
diff -u -3 -p -r1.1 pistream
--- include/cc++/pistream	21 Sep 2002 18:26:57 -0000	1.1
+++ include/cc++/pistream	13 Jan 2003 21:01:09 -0000
@@ -126,13 +126,15 @@ public:
 	pistream_type& 
 	operator>>(unsigned long& n);
 
-	//#ifdef _GLIBCPP_USE_LONG_LONG
+	/*
+	#ifdef _GLIBCPP_USE_LONG_LONG
 	pistream_type& 
 	operator>>(long long& n);
 
 	pistream_type& 
 	operator>>(unsigned long long& n);
-	//#endif
+	#endif
+	*/
 
 	pistream_type& 
 	operator>>(float& f);
@@ -272,8 +274,8 @@ class basic_piostream
 {
 public:
 	// Non-standard Types:
-	typedef basic_pistream<charT, Traits>		pistream_type;
-	typedef basic_postream<charT, Traits>		postream_type;
+	typedef basic_istream<charT, Traits>		istream_type;
+	typedef basic_ostream<charT, Traits>		ostream_type;
 	
 	explicit 
 	basic_piostream(basic_streambuf<charT, Traits>* sb)
Index: include/cc++/postream
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/postream,v
retrieving revision 1.2
diff -u -3 -p -r1.2 postream
--- include/cc++/postream	7 Oct 2002 22:35:26 -0000	1.2
+++ include/cc++/postream	13 Jan 2003 21:01:09 -0000
@@ -145,13 +145,16 @@ public:
 	operator<<(unsigned int n)
 	{ return this->operator<<(static_cast<unsigned long>(n)); }
 
-	//#ifdef _GLIBCPP_USE_LONG_LONG
+	/*
+	#ifdef _GLIBCPP_USE_LONG_LONG
 	postream_type& 
 	operator<<(long long n);
 
 	postream_type& 
 	operator<<(unsigned long long n);
-	//#endif
+	#endif
+	*/
+	
 
 	postream_type& 
 	operator<<(double f);
Index: include/cc++/postream.tcc
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/postream.tcc,v
retrieving revision 1.2
diff -u -3 -p -r1.2 postream.tcc
--- include/cc++/postream.tcc	7 Oct 2002 22:35:26 -0000	1.2
+++ include/cc++/postream.tcc	13 Jan 2003 21:01:09 -0000
@@ -181,7 +181,8 @@ basic_postream<charT, Traits>::operator<
 	return *this;
 }
 
-// TODO: #ifdef USE_LONG_LONG
+/*
+#ifdef USE_LONG_LONG
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>& 
 basic_postream<charT, Traits>::operator<<(long long n)
@@ -206,7 +207,8 @@ basic_postream<charT, Traits>::operator<
 
 	return *this;
 }
-//#endif
+#endif
+*/
 
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>& 
@@ -295,8 +297,8 @@ basic_postream<charT, Traits>::flush()
 	typename postream_type::psentry opfx(*this);
 
 	ostream_type::flush();
-
-	//this->unlockStream();
+ 
+	return *this;
 }
 
 template<typename charT, typename Traits>

--BOKacYhQ+x31HxR3--



From MAILER-DAEMON Thu Jan 16 01:33:34 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Z3ao-000867-00
	for mharc-bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:33:34 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Z3al-00085c-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:33:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Z3ak-00085Q-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:33:31 -0500
Received: from mke-24-167-199-83.wi.rr.com ([24.167.199.83]
	helo=gandalf.libertyetech.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18Z3ak-00085M-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:33:30 -0500
Received: from frodo.libertyetech.com ([192.168.1.2] ident=mail)
	by gandalf.libertyetech.com with esmtp (Exim 3.36 #1 (Debian))
	id 18Z3aj-000338-00
	for <bug-commoncpp@gnu.org>; Thu, 16 Jan 2003 00:33:29 -0600
Received: from danielb by frodo.libertyetech.com with local (Exim 3.36 #1
	(Debian))	id 18Z3ah-0004vL-00
	for <bug-commoncpp@gnu.org>; Thu, 16 Jan 2003 00:33:27 -0600
Date: Thu, 16 Jan 2003 00:33:27 -0600
From: Daniel E Baumann <danielb@libertyetech.com>
To: bug-commoncpp@gnu.org
Message-ID: <20030116063327.GA18915@frodo.libertyetech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.3i
Sender: Daniel E Baumann <danielb@mail.libertyetech.com>
Subject: Piostreams! Now with new identifying thread info!
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, 16 Jan 2003 06:33:32 -0000

Here's a patch which include the previous fixes and with new
functionality that prints out identifying thread info.

The format is (shamelessly ripped off from gdb):

[Thread <tid> (LWP <pid>)]: my regular stream output here.

Compile and run the pio.cpp demo program to see this funky stuff in
action. I probably should say that this was a quick hack that I
did. Ideally it should probably not be compiled in unless you compile
cc++ with debuggin' symbols. Also, I may want to add more to the
"header", but it's getting late here and I want to use this
functionality to find a deadlock in some code :-o. So enjoy :).

Dan
-- 
And if cynics ridicule freedom, ridicule community...if ``hard nosed 
realists'' say that profit is the only ideal...just ignore them, and use 
copyleft all the same.
      -- RMS

Was I helpful?  Let others know: 
  http://svcs.affero.net/rm.php?r=chillywilly



From MAILER-DAEMON Thu Jan 16 01:35:42 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Z3cs-0008PD-00
	for mharc-bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:35:42 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Z3cr-0008P1-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:35:41 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Z3co-0008OL-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:35:39 -0500
Received: from mke-24-167-199-83.wi.rr.com ([24.167.199.83]
	helo=gandalf.libertyetech.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18Z3cl-0008NV-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:35:37 -0500
Received: from frodo.libertyetech.com ([192.168.1.2] ident=mail)
	by gandalf.libertyetech.com with esmtp (Exim 3.36 #1 (Debian))
	id 18Z3ce-00033w-00
	for <bug-commoncpp@gnu.org>; Thu, 16 Jan 2003 00:35:28 -0600
Received: from danielb by frodo.libertyetech.com with local (Exim 3.36 #1
	(Debian))	id 18Z3cd-0004vp-00
	for <bug-commoncpp@gnu.org>; Thu, 16 Jan 2003 00:35:27 -0600
Date: Thu, 16 Jan 2003 00:35:27 -0600
From: Daniel E Baumann <danielb@libertyetech.com>
To: bug-commoncpp@gnu.org
Message-ID: <20030116063527.GA18948@frodo.libertyetech.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="x+6KMIRAuhnl3hBn"
Content-Disposition: inline
User-Agent: Mutt/1.5.3i
Sender: Daniel E Baumann <danielb@mail.libertyetech.com>
Subject: Piostreams! Now with new identifying thread info!
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, 16 Jan 2003 06:35:41 -0000


--x+6KMIRAuhnl3hBn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Here's a patch which include the previous fixes and with new
functionality that prints out identifying thread info.

The format is (shamelessly ripped off from gdb):

[Thread <tid> (LWP <pid>)]: my regular stream output here.

Compile and run the pio.cpp demo program to see this funky stuff in
action. I probably should say that this was a quick hack that I
did. Ideally it should probably not be compiled in unless you compile
cc++ with debuggin' symbols. Also, I may want to add more to the
"header", but it's getting late here and I want to use this
functionality to find a deadlock in some code :-o. So enjoy :).

Dan
-- 
And if cynics ridicule freedom, ridicule community...if ``hard nosed 
realists'' say that profit is the only ideal...just ignore them, and use 
copyleft all the same.
      -- RMS

Was I helpful?  Let others know: 
  http://svcs.affero.net/rm.php?r=chillywilly

--x+6KMIRAuhnl3hBn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="piostreams.diff"

? piostreams.diff
? config/depcomp
? config/texinfo.tex
? demo/netdevices
? demo/pio
? demo/shadigest
? doc/commoncpp2.info
? doc/commoncpp2.info-1
? doc/commoncpp2.info-2
? doc/commoncpp2.info-3
? include/cc++/pfstream
? ssl/Makefile
? ssl/Makefile.in
? win32/CCXX2.rc
Index: include/cc++/pios_init.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/pios_init.h,v
retrieving revision 1.1
diff -u -3 -p -r1.1 pios_init.h
--- include/cc++/pios_init.h	21 Sep 2002 18:26:57 -0000	1.1
+++ include/cc++/pios_init.h	16 Jan 2003 06:25:24 -0000
@@ -81,7 +81,7 @@ private:
 } // namespace ost
 #endif
 
-#endif /* CCXX_PIOS_INIT_H
+#endif // CCXX_PIOS_INIT_H 
 /** EMACS **
  * Local variables:
  * mode: c++
Index: include/cc++/pistream
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/pistream,v
retrieving revision 1.1
diff -u -3 -p -r1.1 pistream
--- include/cc++/pistream	21 Sep 2002 18:26:57 -0000	1.1
+++ include/cc++/pistream	16 Jan 2003 06:25:24 -0000
@@ -126,13 +126,15 @@ public:
 	pistream_type& 
 	operator>>(unsigned long& n);
 
-	//#ifdef _GLIBCPP_USE_LONG_LONG
+	/*
+	#ifdef _GLIBCPP_USE_LONG_LONG
 	pistream_type& 
 	operator>>(long long& n);
 
 	pistream_type& 
 	operator>>(unsigned long long& n);
-	//#endif
+	#endif
+	*/
 
 	pistream_type& 
 	operator>>(float& f);
@@ -272,8 +274,8 @@ class basic_piostream
 {
 public:
 	// Non-standard Types:
-	typedef basic_pistream<charT, Traits>		pistream_type;
-	typedef basic_postream<charT, Traits>		postream_type;
+	typedef basic_istream<charT, Traits>		istream_type;
+	typedef basic_ostream<charT, Traits>		ostream_type;
 	
 	explicit 
 	basic_piostream(basic_streambuf<charT, Traits>* sb)
Index: include/cc++/postream
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/postream,v
retrieving revision 1.2
diff -u -3 -p -r1.2 postream
--- include/cc++/postream	7 Oct 2002 22:35:26 -0000	1.2
+++ include/cc++/postream	16 Jan 2003 06:25:24 -0000
@@ -85,7 +85,7 @@ public:
 	explicit 
 	basic_postream(streambuf_type* sb)
 		: ostream_type(sb), currth(NULL), pid(0), tid(0), lockcnt(0),
-		  owned(false), header(false)
+		  owned(false), header(true)
 	{ }
 
 	virtual 
@@ -145,13 +145,16 @@ public:
 	operator<<(unsigned int n)
 	{ return this->operator<<(static_cast<unsigned long>(n)); }
 
-	//#ifdef _GLIBCPP_USE_LONG_LONG
+	/*
+	#ifdef _GLIBCPP_USE_LONG_LONG
 	postream_type& 
 	operator<<(long long n);
 
 	postream_type& 
 	operator<<(unsigned long long n);
-	//#endif
+	#endif
+	*/
+	
 
 	postream_type& 
 	operator<<(double f);
@@ -410,13 +413,10 @@ public:
 	bool owned;
 	bool header;
 
-	void lockStream();
-	void unlockStream();
 	void outputHeader();
 protected:
 	mutable Mutex lock;
 	mutable Mutex lockbuf;
-	//mutable Mutex mtx;
 };
 
 /**
Index: include/cc++/postream.tcc
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/postream.tcc,v
retrieving revision 1.2
diff -u -3 -p -r1.2 postream.tcc
--- include/cc++/postream.tcc	7 Oct 2002 22:35:26 -0000	1.2
+++ include/cc++/postream.tcc	16 Jan 2003 06:25:24 -0000
@@ -98,22 +98,6 @@ operator<<(postream_type& (*pf)(postream
 	return *this;
 }
 
-/*
-  template<typename charT, typename Traits>
-  basic_postream<charT, Traits>& 
-  basic_postream<charT, Traits>::
-  operator<<(ostream_type& (*pf)(ostream_type&))
-  {
-  // Create a psentry object (may set error bits or throw failure)
-  typedef basic_postream<charT, Traits> postream_type;
-  typename postream_type::psentry opfx(*this);
-  
-  ostream_type::operator<<(pf);
-  
-  return *this;
-  }
-*/
-
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>& 
 basic_postream<charT, Traits>::
@@ -150,6 +134,8 @@ basic_postream<charT, Traits>::operator<
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 	
+	outputHeader();
+
 	ostream_type::operator<<(n);
 
 	return *this;
@@ -163,6 +149,8 @@ basic_postream<charT, Traits>::operator<
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 
+	outputHeader();
+
 	ostream_type::operator<<(n);
 
 	return *this;
@@ -176,12 +164,15 @@ basic_postream<charT, Traits>::operator<
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 
+	outputHeader();
+	
 	ostream_type::operator<<(n);
       
 	return *this;
 }
 
-// TODO: #ifdef USE_LONG_LONG
+/*
+#ifdef USE_LONG_LONG
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>& 
 basic_postream<charT, Traits>::operator<<(long long n)
@@ -201,12 +192,15 @@ basic_postream<charT, Traits>::operator<
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
+
+	outputHeader();
 	
 	ostream_type::operator<<(n);
 
 	return *this;
 }
-//#endif
+#endif
+*/
 
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>& 
@@ -216,6 +210,8 @@ basic_postream<charT, Traits>::operator<
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 	
+	outputHeader();
+
 	ostream_type::operator<<(f);
 	
 	return *this;
@@ -229,6 +225,8 @@ basic_postream<charT, Traits>::operator<
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 	
+	outputHeader(); 
+
 	ostream_type::operator<<(f);
       
 	return *this;
@@ -242,6 +240,8 @@ basic_postream<charT, Traits>::operator<
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 
+	outputHeader();
+
 	ostream_type::operator<<(p);
       
 	return *this;
@@ -255,6 +255,8 @@ basic_postream<charT, Traits>::operator<
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 	
+	outputHeader();
+
 	ostream_type::operator<<(sbin);
 	
 	return *this;
@@ -283,7 +285,7 @@ basic_postream<charT, Traits>::write(con
       
 	ostream_type::write(s, n);
 
-	retrn *this;
+	return *this;
 }
 
 template<typename charT, typename Traits>
@@ -296,7 +298,9 @@ basic_postream<charT, Traits>::flush()
 
 	ostream_type::flush();
 
-	//this->unlockStream();
+	header = true;
+ 
+	return *this;
 }
 
 template<typename charT, typename Traits>
@@ -366,6 +370,8 @@ operator<<(basic_postream<charT, Traits>
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(out);
 
+	out.outputHeader();
+
 	std::operator<<(out, c);
 	
 	return out;
@@ -402,6 +408,25 @@ basic_postream<charT, Traits>::widen(cha
 	return ostream_type::widen(c);
 }
 
+template<typename charT, typename Traits>
+void
+basic_postream<charT, Traits>::outputHeader()
+{
+	pid = static_cast<int>(getpid());
+	tid = static_cast<int>(ost::getThread()->getThreadID());
+	if (header)
+		{
+			// Call the ostream methods so as not to have
+			// to worry about deadlocking
+			std::operator<<(*this, "[Thread ");
+			ostream_type::operator<<(tid);
+			std::operator<<(*this, " (LWP ");
+			ostream_type::operator<<(pid);
+			std::operator<<(*this, ")]: ");
+		}
+	header = false;
+}
+
 // Specializations
 template<typename Traits>
 basic_postream<char, Traits>&
@@ -410,6 +435,8 @@ operator<<(basic_postream<char, Traits>&
 	typedef basic_postream<char, Traits> postream_type;
 	typename postream_type::psentry opfx(out);
       
+	out.outputHeader();
+
 	std::operator<<(out, c);
 
 	return out;
@@ -423,6 +450,8 @@ operator<<(basic_postream<charT, Traits>
 	typedef basic_postream<char, Traits> postream_type;
 	typename postream_type::psentry opfx(out);
 	
+	out.outputHeader();
+
 	std::operator<<(out, s);
 	
 	return out;
@@ -436,7 +465,7 @@ operator<<(basic_postream<charT, Traits>
 	typedef basic_postream<char, Traits> postream_type;
 	typename postream_type::psentry opfx(out);
 	
-	out.currth = ost::getThread();
+	out.outputHeader();
 	
 	std::operator<<(out, s);
 
@@ -452,9 +481,7 @@ operator<<(basic_postream<char, Traits>&
 	typedef basic_postream<char, Traits> postream_type;
 	typename postream_type::psentry opfx(out);
      
-	out.currth = ost::getThread();
-	int tid = static_cast<int>(out.currth->getThreadID());
-	//out.operator<<(tid);
+	out.outputHeader();
  
 	std::operator<<(out, s);
 	
@@ -471,10 +498,7 @@ operator<<(basic_postream<charT, Traits>
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(out);
 
-	out.currth = ost::getThread();
-	int tid = (int)out.currth->getThreadID();
-	//printf("PID: %d\n", getpid());
-	//printf("TID: %d\n", tid);
+	out.outputHeader();
 
 	std::operator<<(out, str);
 
Index: include/cc++/thread.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/thread.h,v
retrieving revision 1.20
diff -u -3 -p -r1.20 thread.h
--- include/cc++/thread.h	9 Jan 2003 13:53:09 -0000	1.20
+++ include/cc++/thread.h	16 Jan 2003 06:25:24 -0000
@@ -1066,6 +1066,7 @@ friend class PosixThread;
 /** @internal */
 friend class DummyThread;
 private:
+	friend class postream_type;
 	friend class Slog;
 
 	Semaphore joinSem;

--x+6KMIRAuhnl3hBn--



From MAILER-DAEMON Thu Jan 16 01:41:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Z3gu-0006t2-00
	for mharc-bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:39:52 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Z3gZ-0005wf-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:39:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Z3gP-0005TL-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:39:24 -0500
Received: from mke-24-167-199-83.wi.rr.com ([24.167.199.83]
	helo=gandalf.libertyetech.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18Z3g4-0004S0-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 01:39:01 -0500
Received: from frodo.libertyetech.com ([192.168.1.2] ident=mail)
	by gandalf.libertyetech.com with esmtp (Exim 3.36 #1 (Debian))
	id 18Z3g3-00035Y-00
	for <bug-commoncpp@gnu.org>; Thu, 16 Jan 2003 00:38:59 -0600
Received: from danielb by frodo.libertyetech.com with local (Exim 3.36 #1
	(Debian))	id 18Z3ft-0004wE-00
	for <bug-commoncpp@gnu.org>; Thu, 16 Jan 2003 00:38:49 -0600
Date: Thu, 16 Jan 2003 00:38:49 -0600
From: Daniel E Baumann <danielb@libertyetech.com>
To: bug-commoncpp@gnu.org
Message-ID: <20030116063849.GA18975@frodo.libertyetech.com>
References: <20030116063527.GA18948@frodo.libertyetech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030116063527.GA18948@frodo.libertyetech.com>
User-Agent: Mutt/1.5.3i
Sender: Daniel E Baumann <danielb@mail.libertyetech.com>
Subject: Re: Piostreams! Now with new identifying thread info!
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, 16 Jan 2003 06:39:47 -0000

Sorry about all the posts, I forgot to attach the patch.

Dan
-- 
And if cynics ridicule freedom, ridicule community...if ``hard nosed 
realists'' say that profit is the only ideal...just ignore them, and use 
copyleft all the same.
      -- RMS

Was I helpful?  Let others know: 
  http://svcs.affero.net/rm.php?r=chillywilly



From MAILER-DAEMON Thu Jan 16 10:43:15 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZC9m-0004gd-00
	for mharc-bug-commoncpp@gnu.org; Thu, 16 Jan 2003 10:42:14 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZBJv-0008Rk-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 09:48:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZBGG-0006s3-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 09:44:54 -0500
Received: from pepelats.alarit.com ([193.201.100.1] helo=relay.alarit.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZBEK-0006Dn-00
	for bug-commoncpp@gnu.org; Thu, 16 Jan 2003 09:42:53 -0500
Received: from funt.alarit.com (funt.alarit.com [193.201.100.159])
	by relay.alarit.com (8.12.7/8.12.7) with ESMTP id h0GEgdE1004385
	for <bug-commoncpp@gnu.org>; Thu, 16 Jan 2003 16:42:40 +0200
Content-Type: text/plain;
  charset="us-ascii"
From: funtik <funt@alarit.com>
To: bug-commoncpp@gnu.org
Date: Thu, 16 Jan 2003 16:41:29 +0200
X-Mailer: KMail [version 1.4]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301161640.11713.funt@alarit.com>
X-Mailman-Approved-At: Thu, 16 Jan 2003 10:42:13 -0500
Subject: Bug in throw(this)
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, 16 Jan 2003 14:48:56 -0000


I have=20
gcc version 2.95.4 20020320 [FreeBSD]
Os FreeBSD 4.7

And this construction throw(this) (or throw this) crashed with core dumpe=
d.



From MAILER-DAEMON Fri Jan 17 03:22:56 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZRlU-0003EE-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 03:22:12 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZRlJ-0002hT-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 03:22:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZRlD-0002W6-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 03:21:56 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZRkz-00024c-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 03:21:41 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZRlV-0006G3-00; Fri, 17 Jan 2003 09:22:13 +0100
Date: Fri, 17 Jan 2003 09:22:12 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: funtik <funt@alarit.com>
Message-ID: <20030117082212.GF247@bulbasaur.rediris.es>
Mail-Followup-To: funtik <funt@alarit.com>, bug-commoncpp@gnu.org
References: <200301161640.11713.funt@alarit.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301161640.11713.funt@alarit.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Bug in throw(this)
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, 17 Jan 2003 08:22:10 -0000


	Could you be more specific on which 'throw' crashed, something
like the code that crashed or the debugger log?

On Thu, Jan 16, 2003 at 04:41:29PM +0200, funtik wrote:
> 
> I have 
> gcc version 2.95.4 20020320 [FreeBSD]
> Os FreeBSD 4.7
> 
> And this construction throw(this) (or throw this) crashed with core dumped.
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Fri Jan 17 04:07:13 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZSSm-0004eS-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 04:06:56 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZSSS-00046r-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 04:06:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZSSN-0003zj-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 04:06:32 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZSRF-0002ww-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 04:05:21 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZSRS-0000ki-00; Fri, 17 Jan 2003 10:05:34 +0100
Date: Fri, 17 Jan 2003 10:05:34 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Daniel E Baumann <danielb@libertyetech.com>
Message-ID: <20030117090534.GG247@bulbasaur.rediris.es>
Mail-Followup-To: Daniel E Baumann <danielb@libertyetech.com>,
	bug-commoncpp@gnu.org
References: <20030116063527.GA18948@frodo.libertyetech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030116063527.GA18948@frodo.libertyetech.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Piostreams! Now with new identifying thread info!
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, 17 Jan 2003 09:06:54 -0000


	It is in CVS. I have noticed a little detail: sometimes the
thread id number is formatted in hex or with a leading '+'. I do not
know if it is a bug or it is done so intentionally.

On Thu, Jan 16, 2003 at 12:35:27AM -0600, Daniel E Baumann wrote:
> Here's a patch which include the previous fixes and with new
> functionality that prints out identifying thread info.
> 
> The format is (shamelessly ripped off from gdb):
> 
> [Thread <tid> (LWP <pid>)]: my regular stream output here.
> 
> Compile and run the pio.cpp demo program to see this funky stuff in
> action. I probably should say that this was a quick hack that I
> did. Ideally it should probably not be compiled in unless you compile
> cc++ with debuggin' symbols. Also, I may want to add more to the
> "header", but it's getting late here and I want to use this
> functionality to find a deadlock in some code :-o. So enjoy :).
> 
> Dan
> -- 
> And if cynics ridicule freedom, ridicule community...if ``hard nosed 
> realists'' say that profit is the only ideal...just ignore them, and use 
> copyleft all the same.
>       -- RMS
> 
> Was I helpful?  Let others know: 
>   http://svcs.affero.net/rm.php?r=chillywilly

> ? piostreams.diff
> ? config/depcomp
> ? config/texinfo.tex
> ? demo/netdevices
> ? demo/pio
> ? demo/shadigest
> ? doc/commoncpp2.info
> ? doc/commoncpp2.info-1
> ? doc/commoncpp2.info-2
> ? doc/commoncpp2.info-3
> ? include/cc++/pfstream
> ? ssl/Makefile
> ? ssl/Makefile.in
> ? win32/CCXX2.rc
> Index: include/cc++/pios_init.h
> ===================================================================
> RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/pios_init.h,v
> retrieving revision 1.1
> diff -u -3 -p -r1.1 pios_init.h
> --- include/cc++/pios_init.h	21 Sep 2002 18:26:57 -0000	1.1
> +++ include/cc++/pios_init.h	16 Jan 2003 06:25:24 -0000
> @@ -81,7 +81,7 @@ private:
>  } // namespace ost
>  #endif
>  
> -#endif /* CCXX_PIOS_INIT_H
> +#endif // CCXX_PIOS_INIT_H 
>  /** EMACS **
>   * Local variables:
>   * mode: c++
> Index: include/cc++/pistream
> ===================================================================
> RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/pistream,v
> retrieving revision 1.1
> diff -u -3 -p -r1.1 pistream
> --- include/cc++/pistream	21 Sep 2002 18:26:57 -0000	1.1
> +++ include/cc++/pistream	16 Jan 2003 06:25:24 -0000
> @@ -126,13 +126,15 @@ public:
>  	pistream_type& 
>  	operator>>(unsigned long& n);
>  
> -	//#ifdef _GLIBCPP_USE_LONG_LONG
> +	/*
> +	#ifdef _GLIBCPP_USE_LONG_LONG
>  	pistream_type& 
>  	operator>>(long long& n);
>  
>  	pistream_type& 
>  	operator>>(unsigned long long& n);
> -	//#endif
> +	#endif
> +	*/
>  
>  	pistream_type& 
>  	operator>>(float& f);
> @@ -272,8 +274,8 @@ class basic_piostream
>  {
>  public:
>  	// Non-standard Types:
> -	typedef basic_pistream<charT, Traits>		pistream_type;
> -	typedef basic_postream<charT, Traits>		postream_type;
> +	typedef basic_istream<charT, Traits>		istream_type;
> +	typedef basic_ostream<charT, Traits>		ostream_type;
>  	
>  	explicit 
>  	basic_piostream(basic_streambuf<charT, Traits>* sb)
> Index: include/cc++/postream
> ===================================================================
> RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/postream,v
> retrieving revision 1.2
> diff -u -3 -p -r1.2 postream
> --- include/cc++/postream	7 Oct 2002 22:35:26 -0000	1.2
> +++ include/cc++/postream	16 Jan 2003 06:25:24 -0000
> @@ -85,7 +85,7 @@ public:
>  	explicit 
>  	basic_postream(streambuf_type* sb)
>  		: ostream_type(sb), currth(NULL), pid(0), tid(0), lockcnt(0),
> -		  owned(false), header(false)
> +		  owned(false), header(true)
>  	{ }
>  
>  	virtual 
> @@ -145,13 +145,16 @@ public:
>  	operator<<(unsigned int n)
>  	{ return this->operator<<(static_cast<unsigned long>(n)); }
>  
> -	//#ifdef _GLIBCPP_USE_LONG_LONG
> +	/*
> +	#ifdef _GLIBCPP_USE_LONG_LONG
>  	postream_type& 
>  	operator<<(long long n);
>  
>  	postream_type& 
>  	operator<<(unsigned long long n);
> -	//#endif
> +	#endif
> +	*/
> +	
>  
>  	postream_type& 
>  	operator<<(double f);
> @@ -410,13 +413,10 @@ public:
>  	bool owned;
>  	bool header;
>  
> -	void lockStream();
> -	void unlockStream();
>  	void outputHeader();
>  protected:
>  	mutable Mutex lock;
>  	mutable Mutex lockbuf;
> -	//mutable Mutex mtx;
>  };
>  
>  /**
> Index: include/cc++/postream.tcc
> ===================================================================
> RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/postream.tcc,v
> retrieving revision 1.2
> diff -u -3 -p -r1.2 postream.tcc
> --- include/cc++/postream.tcc	7 Oct 2002 22:35:26 -0000	1.2
> +++ include/cc++/postream.tcc	16 Jan 2003 06:25:24 -0000
> @@ -98,22 +98,6 @@ operator<<(postream_type& (*pf)(postream
>  	return *this;
>  }
>  
> -/*
> -  template<typename charT, typename Traits>
> -  basic_postream<charT, Traits>& 
> -  basic_postream<charT, Traits>::
> -  operator<<(ostream_type& (*pf)(ostream_type&))
> -  {
> -  // Create a psentry object (may set error bits or throw failure)
> -  typedef basic_postream<charT, Traits> postream_type;
> -  typename postream_type::psentry opfx(*this);
> -  
> -  ostream_type::operator<<(pf);
> -  
> -  return *this;
> -  }
> -*/
> -
>  template<typename charT, typename Traits>
>  basic_postream<charT, Traits>& 
>  basic_postream<charT, Traits>::
> @@ -150,6 +134,8 @@ basic_postream<charT, Traits>::operator<
>  	typedef basic_postream<charT, Traits> postream_type;
>  	typename postream_type::psentry opfx(*this);
>  	
> +	outputHeader();
> +
>  	ostream_type::operator<<(n);
>  
>  	return *this;
> @@ -163,6 +149,8 @@ basic_postream<charT, Traits>::operator<
>  	typedef basic_postream<charT, Traits> postream_type;
>  	typename postream_type::psentry opfx(*this);
>  
> +	outputHeader();
> +
>  	ostream_type::operator<<(n);
>  
>  	return *this;
> @@ -176,12 +164,15 @@ basic_postream<charT, Traits>::operator<
>  	typedef basic_postream<charT, Traits> postream_type;
>  	typename postream_type::psentry opfx(*this);
>  
> +	outputHeader();
> +	
>  	ostream_type::operator<<(n);
>        
>  	return *this;
>  }
>  
> -// TODO: #ifdef USE_LONG_LONG
> +/*
> +#ifdef USE_LONG_LONG
>  template<typename charT, typename Traits>
>  basic_postream<charT, Traits>& 
>  basic_postream<charT, Traits>::operator<<(long long n)
> @@ -201,12 +192,15 @@ basic_postream<charT, Traits>::operator<
>  	// Create a psentry object (may set error bits or throw failure)
>  	typedef basic_postream<charT, Traits> postream_type;
>  	typename postream_type::psentry opfx(*this);
> +
> +	outputHeader();
>  	
>  	ostream_type::operator<<(n);
>  
>  	return *this;
>  }
> -//#endif
> +#endif
> +*/
>  
>  template<typename charT, typename Traits>
>  basic_postream<charT, Traits>& 
> @@ -216,6 +210,8 @@ basic_postream<charT, Traits>::operator<
>  	typedef basic_postream<charT, Traits> postream_type;
>  	typename postream_type::psentry opfx(*this);
>  	
> +	outputHeader();
> +
>  	ostream_type::operator<<(f);
>  	
>  	return *this;
> @@ -229,6 +225,8 @@ basic_postream<charT, Traits>::operator<
>  	typedef basic_postream<charT, Traits> postream_type;
>  	typename postream_type::psentry opfx(*this);
>  	
> +	outputHeader(); 
> +
>  	ostream_type::operator<<(f);
>        
>  	return *this;
> @@ -242,6 +240,8 @@ basic_postream<charT, Traits>::operator<
>  	typedef basic_postream<charT, Traits> postream_type;
>  	typename postream_type::psentry opfx(*this);
>  
> +	outputHeader();
> +
>  	ostream_type::operator<<(p);
>        
>  	return *this;
> @@ -255,6 +255,8 @@ basic_postream<charT, Traits>::operator<
>  	typedef basic_postream<charT, Traits> postream_type;
>  	typename postream_type::psentry opfx(*this);
>  	
> +	outputHeader();
> +
>  	ostream_type::operator<<(sbin);
>  	
>  	return *this;
> @@ -283,7 +285,7 @@ basic_postream<charT, Traits>::write(con
>        
>  	ostream_type::write(s, n);
>  
> -	retrn *this;
> +	return *this;
>  }
>  
>  template<typename charT, typename Traits>
> @@ -296,7 +298,9 @@ basic_postream<charT, Traits>::flush()
>  
>  	ostream_type::flush();
>  
> -	//this->unlockStream();
> +	header = true;
> + 
> +	return *this;
>  }
>  
>  template<typename charT, typename Traits>
> @@ -366,6 +370,8 @@ operator<<(basic_postream<charT, Traits>
>  	typedef basic_postream<charT, Traits> postream_type;
>  	typename postream_type::psentry opfx(out);
>  
> +	out.outputHeader();
> +
>  	std::operator<<(out, c);
>  	
>  	return out;
> @@ -402,6 +408,25 @@ basic_postream<charT, Traits>::widen(cha
>  	return ostream_type::widen(c);
>  }
>  
> +template<typename charT, typename Traits>
> +void
> +basic_postream<charT, Traits>::outputHeader()
> +{
> +	pid = static_cast<int>(getpid());
> +	tid = static_cast<int>(ost::getThread()->getThreadID());
> +	if (header)
> +		{
> +			// Call the ostream methods so as not to have
> +			// to worry about deadlocking
> +			std::operator<<(*this, "[Thread ");
> +			ostream_type::operator<<(tid);
> +			std::operator<<(*this, " (LWP ");
> +			ostream_type::operator<<(pid);
> +			std::operator<<(*this, ")]: ");
> +		}
> +	header = false;
> +}
> +
>  // Specializations
>  template<typename Traits>
>  basic_postream<char, Traits>&
> @@ -410,6 +435,8 @@ operator<<(basic_postream<char, Traits>&
>  	typedef basic_postream<char, Traits> postream_type;
>  	typename postream_type::psentry opfx(out);
>        
> +	out.outputHeader();
> +
>  	std::operator<<(out, c);
>  
>  	return out;
> @@ -423,6 +450,8 @@ operator<<(basic_postream<charT, Traits>
>  	typedef basic_postream<char, Traits> postream_type;
>  	typename postream_type::psentry opfx(out);
>  	
> +	out.outputHeader();
> +
>  	std::operator<<(out, s);
>  	
>  	return out;
> @@ -436,7 +465,7 @@ operator<<(basic_postream<charT, Traits>
>  	typedef basic_postream<char, Traits> postream_type;
>  	typename postream_type::psentry opfx(out);
>  	
> -	out.currth = ost::getThread();
> +	out.outputHeader();
>  	
>  	std::operator<<(out, s);
>  
> @@ -452,9 +481,7 @@ operator<<(basic_postream<char, Traits>&
>  	typedef basic_postream<char, Traits> postream_type;
>  	typename postream_type::psentry opfx(out);
>       
> -	out.currth = ost::getThread();
> -	int tid = static_cast<int>(out.currth->getThreadID());
> -	//out.operator<<(tid);
> +	out.outputHeader();
>   
>  	std::operator<<(out, s);
>  	
> @@ -471,10 +498,7 @@ operator<<(basic_postream<charT, Traits>
>  	typedef basic_postream<charT, Traits> postream_type;
>  	typename postream_type::psentry opfx(out);
>  
> -	out.currth = ost::getThread();
> -	int tid = (int)out.currth->getThreadID();
> -	//printf("PID: %d\n", getpid());
> -	//printf("TID: %d\n", tid);
> +	out.outputHeader();
>  
>  	std::operator<<(out, str);
>  
> Index: include/cc++/thread.h
> ===================================================================
> RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/thread.h,v
> retrieving revision 1.20
> diff -u -3 -p -r1.20 thread.h
> --- include/cc++/thread.h	9 Jan 2003 13:53:09 -0000	1.20
> +++ include/cc++/thread.h	16 Jan 2003 06:25:24 -0000
> @@ -1066,6 +1066,7 @@ friend class PosixThread;
>  /** @internal */
>  friend class DummyThread;
>  private:
> +	friend class postream_type;
>  	friend class Slog;
>  
>  	Semaphore joinSem;

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




From MAILER-DAEMON Fri Jan 17 04:51:40 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZT9j-0003b7-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 04:51:19 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZT2b-00006q-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 04:43:57 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZT2X-0008WE-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 04:43:54 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZT0m-0007je-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 04:42:04 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZT1O-0001CM-00; Fri, 17 Jan 2003 10:42:42 +0100
Date: Fri, 17 Jan 2003 10:42:42 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: funtik <funt@alarit.com>
Message-ID: <20030117094242.GI247@bulbasaur.rediris.es>
Mail-Followup-To: funtik <funt@alarit.com>, bug-commoncpp@gnu.org
References: <200301161640.11713.funt@alarit.com>
	<20030117082212.GF247@bulbasaur.rediris.es>
	<200301171130.01387.funt@alarit.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301171130.01387.funt@alarit.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Bug in throw(this)
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, 17 Jan 2003 09:51:18 -0000


	I guess you solved the problem?

On Fri, Jan 17, 2003 at 11:30:01AM +0200, funtik wrote:
> Sorry, this my error.
> I am use this construction:
> 
> try
> {
> 	Socket sock;
> 	............................
> }
> catch(Socket s)
> {
> }
> 
> instead this:
> 
> try
> {
> 	Socket sock;
> 	............................
> }
> catch(Socket* s)
> {
> }
> 
> 
> On Friday 17 January 2003 10:22, you wrote:
> > Could you be more specific on which 'throw' crashed, something
> > like the code that crashed or the debugger log?
> >
> > On Thu, Jan 16, 2003 at 04:41:29PM +0200, funtik wrote:
> > > I have
> > > gcc version 2.95.4 20020320 [FreeBSD]
> > > Os FreeBSD 4.7
> > >
> > > And this construction throw(this) (or throw this) crashed with core
> > > dumped.
> > >
> > >
> > > _______________________________________________
> > > Bug-commoncpp mailing list
> > > Bug-commoncpp@gnu.org
> > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 



From MAILER-DAEMON Fri Jan 17 05:18:01 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZTZY-0004AJ-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:18:00 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZTZW-00047f-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:17:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZTZU-00046N-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:17:57 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZTZU-00046J-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:17:56 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZTZt-0001DR-00; Fri, 17 Jan 2003 11:18:21 +0100
Date: Fri, 17 Jan 2003 11:18:21 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20030117101820.GA4616@bulbasaur.rediris.es>
Mail-Followup-To: David Sugar <dyfet@ostel.com>,
	Chad Yates <cyates@uidaho.edu>,
	Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <NBBBJJODBJBNJFNIDDCNMEOIDDAA.cyates@uidaho.edu>
	<200301030831.10927.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301030831.10927.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>
cc: bug-commoncpp@gnu.org
cc: Chad Yates <cyates@uidaho.edu>
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: Fri, 17 Jan 2003 10:17:58 -0000


	Restarting the discussion on the CC++ templates, anyway with
the current directory layout there does not seem to be a clear way to
include tests/demos for the templates. Should we move the templates to
the general headers directory, at least in 1.1?

	Also, when UberCounter gets in cc++ 1.1, we will have
templates in ccgnu2...

On Fri, Jan 03, 2003 at 08:31:10AM -0500, David Sugar wrote:
> Ah yes, the mozilla c++ recommendations...
> 
> We may choose to keep the ccgnu2 half very clean in large part to enable one 
> to build very compact applications with Common C++, but I do not think we 
> ever got that anal even in that.  If anything, as practices and compilers 
> improve, we will continue to make greater use of the C++ language standard in 
> full.  However, the reality is that many broken compilers and poor std 
> library/stl implimentations still remain in everyday use so we do have to 
> pick and choose what language features we will make use of extensivily and 
> which we will not.  I much prefer isolating language features with 
> troublesome implimention history rather than excluding them, which is why we 
> had the templates library segregated, for example, or extensive facilities to 
> built with or without exception handling. 
> 
> On Friday 03 January 2003 01:37, Chad Yates wrote:
> > I also read that portable-cpp file a while ago and was actually appauled by
> > it.  It's my opinion that if compilers should be updated to the standard
> > (expected) functionality or new compilers should be found/used.  they
> > pretty much said not to use any of C++'s nice features, they may as well
> > have said just don't use C++.  Please don't let common c++ go that
> > direction.
> >
> > my 2 cents
> >
> > ,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: Thursday, January 02, 2003 6:25 AM
> > > To: David Sugar
> > > Cc: bug-commoncpp@gnu.org
> > > Subject: Re: Headers and templated classes
> >
> > (snip)
> >
> > > How many commercial compilers are still out there that handle templates
> > > poorly? I came across an interesting article, C++ portability guide,
> > > from mozilla.org,
> > >
> > > http://www.mozilla.org/hacking/portable-cpp.html
> > >
> > > They say to avoid templates. But also to avoid exceptions. (This was
> > > in 1998.) So I don't know where you draw the line. Personally, if
> > > you're not using gcc 3.2, you deserve to suffer, but I guess my
> > > philosophy doesn't work too well for an open source project. :-)
> > >
> > > It seems C++ templates have been around since 1995. So one has to ask
> > > the question: if your compiler doesn't support it after more than 8
> > > years, is it ever going to support it?
> >
> > (snip)
> >
> >
> >
> > _______________________________________________
> > 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 MAILER-DAEMON Fri Jan 17 05:43:13 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZTxu-0000yk-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:43:10 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZTwX-00072P-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:41:45 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZTwD-0006l7-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:41:28 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZTw5-0006dq-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:41:18 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZTwh-0001Du-00; Fri, 17 Jan 2003 11:41:55 +0100
Date: Fri, 17 Jan 2003 11:41:55 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-ID: <20030117104154.GB4616@bulbasaur.rediris.es>
Mail-Followup-To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	Chad Yates <cyates@uidaho.edu>, bug-commoncpp@gnu.org
References: <20030103143737.GG887@dogbert.sdsl.sun.ac.za>
	<NBBBJJODBJBNJFNIDDCNKEOODDAA.cyates@uidaho.edu>
	<20030103191113.GM887@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030103191113.GM887@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: Chad Yates <cyates@uidaho.edu>
cc: bug-commoncpp@gnu.org
Subject: Re: Test framework; and what should be in 1.1.0
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, 17 Jan 2003 10:43:03 -0000

On Fri, Jan 03, 2003 at 09:11:13PM +0200, Albert Strasheim wrote:
> >  * Orthodox performs a simple set of tests on an arbitary
> >  * class to make sure that it supports at least the
> >  * following operations:
> >  *
> >  *      default construction    - constructor
> >  *      equality/inequality     - operator== && operator!=
> >  *      assignment              - operator=
> >  *      negation                - operator!
> 
> I am quite surprised by this. I was looking over some of the Common C++ 
> documentation, and I couldn't figure out why everyone was including 
> operator! methods. To me negation doesn't mean much, except in specific 
> cases, and even then negating the return value of a "get" method would 
> probably be clearer in meaning. Or should negation generally return true 
> if something is "wrong" with the object?
> 

	Yes, for instance, you have the ! operator on InetAddress,
which tells you if the ip address is wrong. I find this operator very
nice for conditionals.



From MAILER-DAEMON Fri Jan 17 05:59:48 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZUD5-0006uM-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:58:51 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZUCo-0006Uv-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:58:34 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZUC6-0005Vs-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:57:51 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZUB0-0004zI-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 05:56:42 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZUBX-0001EP-00; Fri, 17 Jan 2003 11:57:15 +0100
Date: Fri, 17 Jan 2003 11:57:15 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030117105715.GC4616@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>,
	Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20030103072949.GC887@dogbert.sdsl.sun.ac.za>
	<NBBBJJODBJBNJFNIDDCNOEONDDAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNOEONDDAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Test framework
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, 17 Jan 2003 10:58:50 -0000

On Fri, Jan 03, 2003 at 10:46:08AM -0800, Chad Yates wrote:
> I would have to agree the cppunit tree was pretty organized.  I have no
> opinion on the naming for the test files, just as long as the word test is
> in there somewhere, and that they are consistent.  I've used <Class>Test for
> what I've done, but will gladly change to test_<class> if that is the
> direction we want to go. cppunit has a contrib directory, is that
> conceptually the same thing as common c++'s patches directory?
> 

	As far as I know there is no contrib nor patches dir in cc++.

> > A good guideline would probably be: one library header, one set of test
> > files, but this breaks down for thread.h and others, since it has about
> > 10 classes in there (which should be split up, IMHO).
> 
> I think some of the headers have become bogged down, and should be broken
> down.  I'm of the opinion that for most tests a single class will be
> exercised, and so should have it's own file where it makes sense (a unit).
> in the cases where your testing the way multiple classes interface that
> standard may have to be brushed aside as you'd be testing a composite.  on a
> side note, I am willing to re-org the persist.h, engine.cpp, persist.cpp,
> digest.h digest.cpp md5.cpp, and sha.cpp files to better break them down
> closer to the 1 class equals 1 each of .h/.cpp/.tcc (.tcc is for templates?)
> files as appropriate.  the timing would just need to be decided on so I
> don't cause trouble for a merge back into cvs (since the contents of the
> files would be exploded over multiple other files).  I'm sure other areas
> could also benefit also, but these are ones I've become the most familiar
> with.
> 
> Comments?
> 

	Yes, some headers could be partitioned, digest.h could be a
header that just includes md5.h, sha.h, etc, composing a kind of
digest subsistem. I think that whether one header should hold one or
more classes depends on the structure of the system. For instance, SHA
is implemented with several classes; I would see it very extreme to
make one header for each class.

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



From MAILER-DAEMON Fri Jan 17 06:13:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZUPZ-0005d6-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 06:11:45 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZUO7-0004x8-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 06:10:15 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZUNp-0004VA-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 06:09:58 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZUNe-000469-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 06:09:46 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZUOE-00020g-00; Fri, 17 Jan 2003 12:10:22 +0100
Date: Fri, 17 Jan 2003 12:10:22 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>
Message-ID: <20030117111022.GD4616@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>
	<20021231213955.GD32211@bulbasaur.rediris.es>
	<20021231221041.GC415@dogbert.sdsl.sun.ac.za>
	<20021231230456.GD415@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021231230456.GD415@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: Fri, 17 Jan 2003 11:11:43 -0000

On Wed, Jan 01, 2003 at 01:04:56AM +0200, Albert Strasheim wrote:
> 
> 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?
> 

	I haven't find any sys/atomic.h too :) I guess it does not
exist.

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



From MAILER-DAEMON Fri Jan 17 07:07:56 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZVHZ-00026C-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:07:33 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZVG1-0001ff-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:05:57 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZVDE-0001Aa-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:03:05 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZV3n-0007df-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 06:53:20 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZV4B-0003UM-00; Fri, 17 Jan 2003 12:53:43 +0100
Date: Fri, 17 Jan 2003 12:53:43 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030117115343.GE4616@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>,
	bug-commoncpp <bug-commoncpp@gnu.org>
References: <NBBBJJODBJBNJFNIDDCNIEPODDAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNIEPODDAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp <bug-commoncpp@gnu.org>
Subject: Re: base 64 encode/decode test
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, 17 Jan 2003 12:07:31 -0000


	It also fails on GNU/Linux. Looking at the numbers down here,
it does not seem an endian issue. I have committed these changes.

On Tue, Jan 07, 2003 at 12:55:10PM -0800, Chad Yates wrote:
> Here is the test program I promised.  On my win32 system and vc++ 6.0 the
> second two tests (testPadding1Short, testPadding2Short) fail unless I change
> part of the b64Decode function like so:
> 
> if (c == '=')
> {
>   if (bits & 0x40000)
>   {
>     if (dstsize < 2) break;
>     *(pdst++) = (bits >> 10);  // changed from '(bits >> 16)'
>     *(pdst++) = (bits >> 2) & 0xff;  // changed from '(bits >> 8) & 0xff'
>     break;
>   }
>   if (bits & 0x1000 && dstsize)
>     *(pdst++) = (bits >> 4);  // changed from '(bits >> 10)'
>   break;
> }
> 
> What I want to know if this is system specific (endian related?) or an
> actual bug.
> 
> thanks,
> 
> Chad


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




From MAILER-DAEMON Fri Jan 17 07:17:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZVQa-0004lk-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:16:52 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZVQ5-0004X1-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:16:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZVOg-0003p8-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:14:55 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZV9y-0000F8-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 06:59:42 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZVAX-0003UZ-00; Fri, 17 Jan 2003 13:00:17 +0100
Date: Fri, 17 Jan 2003 13:00:17 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>
Message-ID: <20030117120017.GF4616@bulbasaur.rediris.es>
Mail-Followup-To: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>,
	Federico Montesino Pouzols <fedemp@altern.org>,
	bug-commoncpp@gnu.org
References: <20030103214523.GP887@dogbert.sdsl.sun.ac.za>
	<20030106163246.GG4098@bulbasaur.rediris.es>
	<20030108160541.GB434@dogbert.sdsl.sun.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030108160541.GB434@dogbert.sdsl.sun.ac.za>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
cc: Federico Montesino Pouzols <fedemp@altern.org>
Subject: Re: doxygen @short directive in comments
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, 17 Jan 2003 12:16:51 -0000

On Wed, Jan 08, 2003 at 06:05:42PM +0200, Albert Strasheim wrote:
> 
> Here's a more general question: how is any autoconf/automake project 
> supposed to use the config.h file?
> 
> It seems to be as if the right way to go about things is to have 
> autoconf generate a config.h header which you include with your 
> installed headers (which seems to be what Common C++ does), and always 
> include if you need configuration info in your other headers.
> 

	Yes, that way, you have in config.h all the information that
the autools guessed for your system when you run configure.

> BTW, with autoconf 2.57, reconfig prints the following warning message 
> when you generate the files for the build system:
> 
> fullung@dogbert:~/work/commoncpp2> ./reconfig
> Putting files in AC_CONFIG_AUX_DIR, `config'.
> WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
> WARNING: and `config.h.top', to define templates for `config.h.in'
> WARNING: is deprecated and discouraged.
> 
> WARNING: Using the third argument of `AC_DEFINE' and
> WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
> WARNING: `acconfig.h':
> 
> WARNING:   AC_DEFINE([NEED_MAIN], 1,
> WARNING:             [Define if a function `main' is needed.])
> 
> WARNING: More sophisticated templates can also be produced, see the
> WARNING: documentation.
> 

	The autotools files of cc++ use the syntax of old autotools
releases, which now is somewhat deprecated. However, as long as
backwards compatibility is kept in the autotools, this has the
advantage that we do not impose the requirement of having an updated
autotools suite in order to use the CVS version of cc++.

	Perhaps, we should update these files for 1.1, in particular
to avoid the use of acconfig.h.

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



From MAILER-DAEMON Fri Jan 17 07:19:55 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZVSB-0005tG-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:18:31 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZVQn-0004rs-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:17:05 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZVOi-0003r7-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:14:57 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZVIR-0002KR-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:08:27 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZVJ7-0003V6-00
	for <bug-commoncpp@gnu.org>; Fri, 17 Jan 2003 13:09:09 +0100
Date: Fri, 17 Jan 2003 13:09:09 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Message-ID: <20030117120909.GG4616@bulbasaur.rediris.es>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <NBBBJJODBJBNJFNIDDCNIEPNDDAA.cyates@uidaho.edu>
	<20030109094126.GB313@bulbasaur.rediris.es>
	<200301090501.31843.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301090501.31843.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
Subject: CC++ 2 home page
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, 17 Jan 2003 12:18:30 -0000


	I have updated the cc++ page. Does anyone think that we should
include any additional information or fix there? Suggestions?

	Yes, I know, we should compile a list of people who have helped
for the last months in order to update the contributors list and the
THANKS file :)

On Thu, Jan 09, 2003 at 05:01:31AM -0500, David Sugar wrote:
> Yes, that is nice.  We really should update the common c++ (and ccrtp) pages a 
> lot and also reference the link to the archive on them...
> 
> On Thursday 09 January 2003 04:41, Federico Montesino Pouzols wrote:
> > It seems that the list has been frozen for two or three days,
> > but I now see all the posts that you have reposted with '(copy)'
> > appended. In the meantime, the mail archives are working again, now
> > based on MHonArc. By the way, this new interface allows for searching
> > through the archives.
> >



From MAILER-DAEMON Fri Jan 17 07:31:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZVe9-00038s-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:30:53 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZVa6-0000MT-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:26:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZVYv-00008Z-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:25:29 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZVXC-0007pI-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:23:43 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZVXr-0003Vb-00; Fri, 17 Jan 2003 13:24:23 +0100
Date: Fri, 17 Jan 2003 13:24:23 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030117122422.GH4616@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>,
	bug-commoncpp <bug-commoncpp@gnu.org>
References: <NBBBJJODBJBNJFNIDDCNOEBGDEAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNOEBGDEAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp <bug-commoncpp@gnu.org>
Subject: Re: Some issues with the codebase
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, 17 Jan 2003 12:30:52 -0000

On Thu, Jan 09, 2003 at 03:26:45PM -0800, Chad Yates wrote:
> After writing this and then checking out the latest patches/changes, I
> discovered there is a Code style written up, it's in the texi documentation
> (I still haven't figured out how to view).
> 

	Does not a 'commoncpp2.info' file get generated when you run
make? .info files can be read with 'info' or alternate tools, such as
'pinfo'. There are many tools to process texi files, among them GNU
makeinfo, with which you can generate htmls and xmls (DocBook or
TexInfoML). There is also 'texi2dvi', and 'texi2pdf'.

	We have not put this manual online since it is somewhat
incomplete and some parts are outdated, though, if people want, we
could put it on the web, as with the reference manual.

> If you want to know what I typically use:
> 
> 1) Types: named like classes since they are in the same family and
>    represent an object/primitive of some sort.
> 2) Instances/Attributes/Variables: named like methods but more lax.
> 3) Constants: all UPPERCASE, PI, MAX_SIZE, enum {RED, GREEN, BLUE}
> 4) Methods: as above, typcially verb prefix + (processJob, addElement..)
> 5) Private: in the private section of the class declaration. no
>    distinction from other member variables (hey they may start public,
>    but then be moved to private or vice versa.
> 6) Global: ?? I don't use these except under extreme conditions. but I
>    would expect same as Methods and Member variables

	Well, it seems that we mostly agree that the current
recommendations in the manual, though not always followed in cc++ :),
are quite good. Please, forget my obnoxious recommendation regarding
leading underscores :).

> 
> > why not simple using comm ?? placeholder for common c++ or
> > communication :-)
> >
> > I think this is a very esotheric issue and so many different opinions
> > around ... so sorry for bugging you ;-)
> 
> It's really a can of worms isn't it. or maybe snakes. :)
> 
> Later!
> 
> chad
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Fri Jan 17 07:40:05 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZVmg-0003cq-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:39:42 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZVmK-0002gD-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:39:20 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZVlo-0001yM-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:38:56 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZVlW-0001DY-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 07:38:30 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZVm8-0003e2-00; Fri, 17 Jan 2003 13:39:08 +0100
Date: Fri, 17 Jan 2003 13:39:08 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ian Gough <igough@gridiron-networks.com>
Message-ID: <20030117123908.GI4616@bulbasaur.rediris.es>
Mail-Followup-To: Ian Gough <igough@gridiron-networks.com>,
	'bug-commoncpp' <bug-commoncpp@gnu.org>
References: <20030111134715.GB10068@bulbasaur.rediris.es>
	<001601c2bbf2$73fdae40$0c02a8c0@gridironnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001601c2bbf2$73fdae40$0c02a8c0@gridironnetworks.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
Subject: Re: Building CC++ on Mac OS X
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, 17 Jan 2003 12:39:40 -0000


	Hi,...

On Tue, Jan 14, 2003 at 12:28:59PM -0500, Ian Gough wrote:
> Here is what I found. Unfortunatly, I am not familiar with the
> autotools, so I cannot make the changes to that part of the code with
> any degree of confidence, so I hacked files and makefiles to get it to
> build. I will leave it to somebody confident with the autotools to
> figure out how to fix this in the proper manner. Note that this only
> gets it to build, though the demos still have build problems that I
> didn't look into yet (../include/cc++/xml.h:323:2: #error "XML support
> is not available.")
> 
> I am in the process of testing the lib now.
> 
> 1) in thread.cpp: sched_getscheduler does not exist on the Mac so I
> added -D__FreeBSD__=4 to CXXFLAGS in the Makefile
> 

	It may be that it does not exist or that it is defined in a
different system header. Is there a sched.h? Also, could you grep for
sched_getscheduler through your system headers?

> 2) in file.cpp: lockf is not fully implemented on the Mac; the structs
> are there and the symbolic constants, but the function signature is
> missing from the include files. So, though HAVE_SYS_FILE_H is defined,
> which causes sys/file.h to be included, which defines F_LOCK, there is
> no lockf so the lockf included in file.cpp needs to be used. Added -DMAC
> to the makefile and added code in file.cpp to cause its version of lockf
> to be conditionally compiled when MAC is set.
> 

	May it be defined in some strange header?

> 3) in socket.h: socklen_t is undefined. I found references on the inet
> that spec that FreeBSD prior to 4.x and Solaris prior to 7 (2.7) do not
> define the type socklen_t and some of the mac os X is based on FreeBSD
> 4.4. To cause this to be defined, I included -D_BSD_SOCKLEN_T_=int in
> the Makefile.
> 

	Um, we will add a configuration test for this, in order to
define _BSD_SOCKLEN_T when it is missing.

> 4) in network.cpp:
> g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
> -g -O2 -D_GNU_SOURCE -D__FreeBSD__=4 -DMAC -D_BSD_SOCKLEN_T_=int -Wall
> -ansi -pedantic -I../include -c network.cpp -MT network.lo -MD -MP -MF
> .deps/network.TPlo  -fno-common -DPIC -o .libs/network.lo
> network.cpp: In function `bool
>    ost::enumNetworkDevices(std::vector<ost::NetworkDeviceInfo,
>    std::allocator<ost::NetworkDeviceInfo> >&)':
> network.cpp:110: ambiguous overload for `ost::InetAddress& = u_int32_t'
>    operator
> ../include/cc++/socket.h:300: candidates are: ost::InetAddress&
>    ost::InetAddress::operator=(const char*)
> ../include/cc++/socket.h:308:                 ost::InetAddress&
>    ost::InetAddress::operator=(long unsigned int)
> make: *** [network.lo] Error 1
> 
> Added a new assignment operator to c++/socket.h as specified in email
> from Mark Purcell
> 	inline InetAddress &operator=(unsigned int addr)
> 		{return *this = (unsigned long) addr;}
> 

	This is already fixed in CVS.

> 5) in serial.cpp
> g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
> -g -O2 -D_GNU_SOURCE -D__FreeBSD__=4 -DMAC -D_BSD_SOCKLEN_T_=int -Wall
> -ansi -pedantic -I../include -c serial.cpp -MT serial.lo -MD -MP -MF
> .deps/serial.TPlo  -fno-common -DPIC -o .libs/serial.lo
> serial.cpp: In member function `void ost::Serial::initConfig()':
> serial.cpp:203: `ioctl' undeclared (first use this function)
> serial.cpp:203: (Each undeclared identifier is reported only once for
> each
>    function it appears in.)
> 
> Added
> #include <sys/ioctl.h>
> to serial.cpp
> 
> 

	Fixed in CVS. Probably on other systems sys/ioctl.h is
included indirectly thorugh other system headers.



From MAILER-DAEMON Fri Jan 17 13:32:34 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZbI9-0006yI-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 13:32:33 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZbI7-0006xB-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 13:32:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZbI5-0006wq-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 13:32:30 -0500
Received: from mx1.magmacom.com ([206.191.0.217])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZbHg-0006qa-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 13:32:04 -0500
Received: from mail1.magma.ca (mail1.magma.ca [206.191.0.252])
	h0HIW1si018223;	Fri, 17 Jan 2003 13:32:01 -0500 (EST)
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail1.magma.ca (Magma's Mail Server) with ESMTP id h0HIW0ui026303;
	Fri, 17 Jan 2003 13:32:01 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: "'Federico Montesino Pouzols'" <fedemp@altern.org>
Date: Fri, 17 Jan 2003 13:32:01 -0500
Message-ID: <000401c2be56$b9e34760$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <20030117123908.GI4616@bulbasaur.rediris.es>
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
Subject: RE: Building CC++ on Mac OS X
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, 17 Jan 2003 18:32:31 -0000

> 	Hi,...
> 
> On Tue, Jan 14, 2003 at 12:28:59PM -0500, Ian Gough wrote:
> > Here is what I found. Unfortunatly, I am not familiar with the 
> > autotools, so I cannot make the changes to that part of the 
> code with 
> > any degree of confidence, so I hacked files and makefiles 
> to get it to 
> > build. I will leave it to somebody confident with the autotools to 
> > figure out how to fix this in the proper manner. Note that 
> this only 
> > gets it to build, though the demos still have build problems that I 
> > didn't look into yet (../include/cc++/xml.h:323:2: #error 
> "XML support 
> > is not available.")
> > 
> > I am in the process of testing the lib now.
> > 
> > 1) in thread.cpp: sched_getscheduler does not exist on the Mac so I 
> > added -D__FreeBSD__=4 to CXXFLAGS in the Makefile
> > 
> 
> 	It may be that it does not exist or that it is defined 
> in a different system header. Is there a sched.h? Also, could 
> you grep for sched_getscheduler through your system headers?
> 

No sched_getscheduler(), but there is a sched.h.

bash-2.05a$ pwd
/usr/include
bash-2.05a$ grep -r sched_getscheduler *
grep: warning: gcc/darwin/2.95.2/g++/std: recursive directory loop
bash-2.05a$ ls sched.h
sched.h
bash-2.05a$ cat sched.h
#ifndef _SCHED_H_
#define _SCHED_H_

#include <pthread_impl.h>

/*
 * Scheduling paramters
 */
#ifndef __POSIX_LIB__
struct sched_param { int sched_priority;  char
opaque[__SCHED_PARAM_SIZE__]; };
#endif

extern int sched_yield(void);
extern int sched_get_priority_min(int);
extern int sched_get_priority_max(int);
#endif /* _SCHED_H_ */


> > 2) in file.cpp: lockf is not fully implemented on the Mac; 
> the structs 
> > are there and the symbolic constants, but the function signature is 
> > missing from the include files. So, though HAVE_SYS_FILE_H 
> is defined, 
> > which causes sys/file.h to be included, which defines 
> F_LOCK, there is 
> > no lockf so the lockf included in file.cpp needs to be used. Added 
> > -DMAC to the makefile and added code in file.cpp to cause 
> its version 
> > of lockf to be conditionally compiled when MAC is set.
> > 
> 
> 	May it be defined in some strange header?
> 

I thought so at first, but I grepped all over hells half acre looking
for it but couldn't find it on this system, just reference to the lockf
structure. The Apple Rel notes for v10.2 say that the lockf() function
was added, but I have installed the latest patch 10.2.3 plus the latest
developer tools but still no luck.

> > 3) in socket.h: socklen_t is undefined. I found references 
> on the inet 
> > that spec that FreeBSD prior to 4.x and Solaris prior to 7 (2.7) do 
> > not define the type socklen_t and some of the mac os X is based on 
> > FreeBSD 4.4. To cause this to be defined, I included 
> > -D_BSD_SOCKLEN_T_=int in the Makefile.
> > 
> 
> 	Um, we will add a configuration test for this, in order 
> to define _BSD_SOCKLEN_T when it is missing.
> 
> > 4) in network.cpp:
> > g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src 
> > g++ -DCCXX_EXPORT_LIBRARY
> > -g -O2 -D_GNU_SOURCE -D__FreeBSD__=4 -DMAC 
> -D_BSD_SOCKLEN_T_=int -Wall 
> > -ansi -pedantic -I../include -c network.cpp -MT network.lo 
> -MD -MP -MF 
> > .deps/network.TPlo  -fno-common -DPIC -o .libs/network.lo
> > network.cpp: In function `bool
> >    ost::enumNetworkDevices(std::vector<ost::NetworkDeviceInfo,
> >    std::allocator<ost::NetworkDeviceInfo> >&)':
> > network.cpp:110: ambiguous overload for `ost::InetAddress& 
> = u_int32_t'
> >    operator
> > ../include/cc++/socket.h:300: candidates are: ost::InetAddress&
> >    ost::InetAddress::operator=(const char*)
> > ../include/cc++/socket.h:308:                 ost::InetAddress&
> >    ost::InetAddress::operator=(long unsigned int)
> > make: *** [network.lo] Error 1
> > 
> > Added a new assignment operator to c++/socket.h as 
> specified in email 
> > from Mark Purcell
> > 	inline InetAddress &operator=(unsigned int addr)
> > 		{return *this = (unsigned long) addr;}
> > 
> 
> 	This is already fixed in CVS.
> 
> > 5) in serial.cpp
> > g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src 
> > g++ -DCCXX_EXPORT_LIBRARY
> > -g -O2 -D_GNU_SOURCE -D__FreeBSD__=4 -DMAC 
> -D_BSD_SOCKLEN_T_=int -Wall 
> > -ansi -pedantic -I../include -c serial.cpp -MT serial.lo 
> -MD -MP -MF 
> > .deps/serial.TPlo  -fno-common -DPIC -o .libs/serial.lo
> > serial.cpp: In member function `void ost::Serial::initConfig()':
> > serial.cpp:203: `ioctl' undeclared (first use this function)
> > serial.cpp:203: (Each undeclared identifier is reported 
> only once for 
> > each
> >    function it appears in.)
> > 
> > Added
> > #include <sys/ioctl.h>
> > to serial.cpp
> > 
> > 
> 
> 	Fixed in CVS. Probably on other systems sys/ioctl.h is 
> included indirectly thorugh other system headers.
> 




From MAILER-DAEMON Fri Jan 17 14:12:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Zbuc-0000w4-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:12:18 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZbuZ-0000sa-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:12:15 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZbuX-0000qp-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:12:15 -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 18Zbt2-0000S2-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:10:40 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H8V003E7H9KIB@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Fri, 17 Jan 2003 11:10:32 -0800 (PST)
Date: Fri, 17 Jan 2003 11:10:32 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20030117105715.GC4616@bulbasaur.rediris.es>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-id: <NBBBJJODBJBNJFNIDDCNAEEFDEAA.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
cc: bug-commoncpp@gnu.org
Subject: RE: Test framework
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, 17 Jan 2003 19:12:16 -0000

> On Fri, Jan 03, 2003 at 10:46:08AM -0800, Chad Yates wrote:
> > I would have to agree the cppunit tree was pretty organized.  I have no
> > opinion on the naming for the test files, just as long as the
> word test is
> > in there somewhere, and that they are consistent.  I've used
> <Class>Test for
> > what I've done, but will gladly change to test_<class> if that is the
> > direction we want to go. cppunit has a contrib directory, is that
> > conceptually the same thing as common c++'s patches directory?
> >
>
> 	As far as I know there is no contrib nor patches dir in cc++.

sorry, my bad.  I think the directory i was looking at was on my end and was
created sometime ago to hold some patches from savannah and/or the list.
(urlparser, ssl, and urlstring before they were added).

> 	Yes, some headers could be partitioned, digest.h could be a
> header that just includes md5.h, sha.h, etc, composing a kind of
> digest subsistem. I think that whether one header should hold one or
> more classes depends on the structure of the system. For instance, SHA
> is implemented with several classes; I would see it very extreme to
> make one header for each class.

I agree.  should I go ahead and re-org the persistence engine or digest
classes when I have time, and then submit the resulting structure?

,chad




From MAILER-DAEMON Fri Jan 17 14:44:38 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZcI6-0008M1-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:36:34 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZcGs-0007Ck-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:35:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZcAy-00051t-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:29:13 -0500
Received: from mx2.magma.ca ([206.191.0.250])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZcAA-0004XR-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:28:22 -0500
Received: from mail6.magma.ca (mail6.magma.ca [206.191.0.248])
	by mx2.magma.ca (Magma Relay Server) with ESMTP id h0HJSL25029773
	for <bug-commoncpp@gnu.org>; Fri, 17 Jan 2003 14:28:22 -0500
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail6.magma.ca (Magma's Mail Server) with ESMTP id h0HJSLsu003213
	for <bug-commoncpp@gnu.org>; Fri, 17 Jan 2003 14:28:21 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: <bug-commoncpp@gnu.org>
Date: Fri, 17 Jan 2003 14:28:21 -0500
Message-ID: <000501c2be5e$98689830$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0006_01C2BE34.AF929030"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: Process::spawn() and atexit()
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, 17 Jan 2003 19:36:27 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C2BE34.AF929030
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

On Win32, Process::spawn() blocks as it spawns a new process. On all
other platforms, it forks, execs and then waits. The side effect comes
in that the parent process of the fork then exits, which causes the
function set up in atexit() to be called.
 
Normally, this wouldn't cause a problem, but the app I am building is a
server that spawns multiple processes and sets up communications links
to each of the children. To make sure the system gets shutdown
gracefully, in the atexit function I caused the server to tell each of
the children to quit gracefully. Now this works fine in Win32, but on
unix, due to the forking, the atexit function gets called when the
parent process of the fork exits, which causes the shutdown message to
be sent to the child processes before the server portion is actually
exiting, thereby tearing down half the system.
 
I think that perhaps this side effect needs to be documented for the
Process::spawn() method so that people can be aware there are issues
with using atexit() and spawn().
 
 

------=_NextPart_000_0006_01C2BE34.AF929030
Content-Type: text/html;
	charset="US-ASCII"
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=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D994373914-16012003>On =
Win32,=20
Process::spawn() blocks as it spawns a new process. On all other =
platforms, it=20
forks, execs and then waits. The side effect comes in that the parent =
process of=20
the fork then exits, which causes the function set up in&nbsp;atexit() =
to be=20
called.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D994373914-16012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D994373914-16012003>Normally, this=20
wouldn't cause a problem, but the app I am building is a server that =
spawns=20
multiple processes and sets up communications links to each of the =
children. To=20
make sure the system gets shutdown gracefully, in the atexit function I =
caused=20
the server to tell each of the children to quit gracefully. Now this =
works fine=20
in Win32, but on unix, due to the forking, the atexit function gets =
called when=20
the parent process of the fork exits, which causes the shutdown message =
to be=20
sent to the child processes before the server portion is actually =
exiting,=20
thereby tearing down half the system.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D994373914-16012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D994373914-16012003>I =
think that perhaps=20
this side effect needs to be documented for the Process::spawn() method =
so that=20
people can be aware there are issues with using atexit() and=20
spawn().</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D994373914-16012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D994373914-16012003></SPAN></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0006_01C2BE34.AF929030--




From MAILER-DAEMON Fri Jan 17 14:48:44 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZcT9-0000MT-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:47:59 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZcQF-0006VL-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:44:59 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZcPW-0005KK-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:44:16 -0500
Received: from mke-24-167-199-83.wi.rr.com ([24.167.199.83]
	helo=gandalf.libertyetech.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18ZcOU-0004UW-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 14:43:10 -0500
Received: from frodo.libertyetech.com ([192.168.1.2] ident=mail)
	by gandalf.libertyetech.com with esmtp (Exim 3.36 #1 (Debian))
	id 18ZcOV-0001tx-00
	for <bug-commoncpp@gnu.org>; Fri, 17 Jan 2003 13:43:11 -0600
Received: from danielb by frodo.libertyetech.com with local (Exim 3.36 #1
	(Debian))	id 18ZcOO-0005mH-00
	for <bug-commoncpp@gnu.org>; Fri, 17 Jan 2003 13:43:04 -0600
Date: Fri, 17 Jan 2003 13:43:04 -0600
From: Daniel E Baumann <baumannd@msoe.edu>
To: bug-commoncpp@gnu.org
Message-ID: <20030117194303.GC19461@frodo.libertyetech.com>
References: <20030116063527.GA18948@frodo.libertyetech.com>
	<20030117090534.GG247@bulbasaur.rediris.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030117090534.GG247@bulbasaur.rediris.es>
User-Agent: Mutt/1.5.3i
Sender: Daniel E Baumann <danielb@mail.libertyetech.com>
Subject: Re: Piostreams! Now with new identifying thread info!
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, 17 Jan 2003 19:47:57 -0000

It's a side effect of pmping the 'hex' manipulator through the
stream. I don't think I am going to worry about it. Maybe I'll attempt
to fix it down the road, but ppl will just have to deal with it for
now ;).

Dan

On Fri, Jan 17, 2003 at 10:05:34AM +0100, Federico Montesino Pouzols wrote:
> 
> 	It is in CVS. I have noticed a little detail: sometimes the
> thread id number is formatted in hex or with a leading '+'. I do not
> know if it is a bug or it is done so intentionally.
> 
> On Thu, Jan 16, 2003 at 12:35:27AM -0600, Daniel E Baumann wrote:
> > Here's a patch which include the previous fixes and with new
> > functionality that prints out identifying thread info.
> > 
> > The format is (shamelessly ripped off from gdb):
> > 
> > [Thread <tid> (LWP <pid>)]: my regular stream output here.
> > 
> > Compile and run the pio.cpp demo program to see this funky stuff in
> > action. I probably should say that this was a quick hack that I
> > did. Ideally it should probably not be compiled in unless you compile
> > cc++ with debuggin' symbols. Also, I may want to add more to the
> > "header", but it's getting late here and I want to use this
> > functionality to find a deadlock in some code :-o. So enjoy :).
> > 
> > Dan
> > -- 
> > And if cynics ridicule freedom, ridicule community...if ``hard nosed 
> > realists'' say that profit is the only ideal...just ignore them, and use 
> > copyleft all the same.
> >       -- RMS
> > 
> > Was I helpful?  Let others know: 
> >   http://svcs.affero.net/rm.php?r=chillywilly
> 
> > ? piostreams.diff
> > ? config/depcomp
> > ? config/texinfo.tex
> > ? demo/netdevices
> > ? demo/pio
> > ? demo/shadigest
> > ? doc/commoncpp2.info
> > ? doc/commoncpp2.info-1
> > ? doc/commoncpp2.info-2
> > ? doc/commoncpp2.info-3
> > ? include/cc++/pfstream
> > ? ssl/Makefile
> > ? ssl/Makefile.in
> > ? win32/CCXX2.rc
> > Index: include/cc++/pios_init.h
> > ===================================================================
> > RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/pios_init.h,v
> > retrieving revision 1.1
> > diff -u -3 -p -r1.1 pios_init.h
> > --- include/cc++/pios_init.h	21 Sep 2002 18:26:57 -0000	1.1
> > +++ include/cc++/pios_init.h	16 Jan 2003 06:25:24 -0000
> > @@ -81,7 +81,7 @@ private:
> >  } // namespace ost
> >  #endif
> >  
> > -#endif /* CCXX_PIOS_INIT_H
> > +#endif // CCXX_PIOS_INIT_H 
> >  /** EMACS **
> >   * Local variables:
> >   * mode: c++
> > Index: include/cc++/pistream
> > ===================================================================
> > RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/pistream,v
> > retrieving revision 1.1
> > diff -u -3 -p -r1.1 pistream
> > --- include/cc++/pistream	21 Sep 2002 18:26:57 -0000	1.1
> > +++ include/cc++/pistream	16 Jan 2003 06:25:24 -0000
> > @@ -126,13 +126,15 @@ public:
> >  	pistream_type& 
> >  	operator>>(unsigned long& n);
> >  
> > -	//#ifdef _GLIBCPP_USE_LONG_LONG
> > +	/*
> > +	#ifdef _GLIBCPP_USE_LONG_LONG
> >  	pistream_type& 
> >  	operator>>(long long& n);
> >  
> >  	pistream_type& 
> >  	operator>>(unsigned long long& n);
> > -	//#endif
> > +	#endif
> > +	*/
> >  
> >  	pistream_type& 
> >  	operator>>(float& f);
> > @@ -272,8 +274,8 @@ class basic_piostream
> >  {
> >  public:
> >  	// Non-standard Types:
> > -	typedef basic_pistream<charT, Traits>		pistream_type;
> > -	typedef basic_postream<charT, Traits>		postream_type;
> > +	typedef basic_istream<charT, Traits>		istream_type;
> > +	typedef basic_ostream<charT, Traits>		ostream_type;
> >  	
> >  	explicit 
> >  	basic_piostream(basic_streambuf<charT, Traits>* sb)
> > Index: include/cc++/postream
> > ===================================================================
> > RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/postream,v
> > retrieving revision 1.2
> > diff -u -3 -p -r1.2 postream
> > --- include/cc++/postream	7 Oct 2002 22:35:26 -0000	1.2
> > +++ include/cc++/postream	16 Jan 2003 06:25:24 -0000
> > @@ -85,7 +85,7 @@ public:
> >  	explicit 
> >  	basic_postream(streambuf_type* sb)
> >  		: ostream_type(sb), currth(NULL), pid(0), tid(0), lockcnt(0),
> > -		  owned(false), header(false)
> > +		  owned(false), header(true)
> >  	{ }
> >  
> >  	virtual 
> > @@ -145,13 +145,16 @@ public:
> >  	operator<<(unsigned int n)
> >  	{ return this->operator<<(static_cast<unsigned long>(n)); }
> >  
> > -	//#ifdef _GLIBCPP_USE_LONG_LONG
> > +	/*
> > +	#ifdef _GLIBCPP_USE_LONG_LONG
> >  	postream_type& 
> >  	operator<<(long long n);
> >  
> >  	postream_type& 
> >  	operator<<(unsigned long long n);
> > -	//#endif
> > +	#endif
> > +	*/
> > +	
> >  
> >  	postream_type& 
> >  	operator<<(double f);
> > @@ -410,13 +413,10 @@ public:
> >  	bool owned;
> >  	bool header;
> >  
> > -	void lockStream();
> > -	void unlockStream();
> >  	void outputHeader();
> >  protected:
> >  	mutable Mutex lock;
> >  	mutable Mutex lockbuf;
> > -	//mutable Mutex mtx;
> >  };
> >  
> >  /**
> > Index: include/cc++/postream.tcc
> > ===================================================================
> > RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/postream.tcc,v
> > retrieving revision 1.2
> > diff -u -3 -p -r1.2 postream.tcc
> > --- include/cc++/postream.tcc	7 Oct 2002 22:35:26 -0000	1.2
> > +++ include/cc++/postream.tcc	16 Jan 2003 06:25:24 -0000
> > @@ -98,22 +98,6 @@ operator<<(postream_type& (*pf)(postream
> >  	return *this;
> >  }
> >  
> > -/*
> > -  template<typename charT, typename Traits>
> > -  basic_postream<charT, Traits>& 
> > -  basic_postream<charT, Traits>::
> > -  operator<<(ostream_type& (*pf)(ostream_type&))
> > -  {
> > -  // Create a psentry object (may set error bits or throw failure)
> > -  typedef basic_postream<charT, Traits> postream_type;
> > -  typename postream_type::psentry opfx(*this);
> > -  
> > -  ostream_type::operator<<(pf);
> > -  
> > -  return *this;
> > -  }
> > -*/
> > -
> >  template<typename charT, typename Traits>
> >  basic_postream<charT, Traits>& 
> >  basic_postream<charT, Traits>::
> > @@ -150,6 +134,8 @@ basic_postream<charT, Traits>::operator<
> >  	typedef basic_postream<charT, Traits> postream_type;
> >  	typename postream_type::psentry opfx(*this);
> >  	
> > +	outputHeader();
> > +
> >  	ostream_type::operator<<(n);
> >  
> >  	return *this;
> > @@ -163,6 +149,8 @@ basic_postream<charT, Traits>::operator<
> >  	typedef basic_postream<charT, Traits> postream_type;
> >  	typename postream_type::psentry opfx(*this);
> >  
> > +	outputHeader();
> > +
> >  	ostream_type::operator<<(n);
> >  
> >  	return *this;
> > @@ -176,12 +164,15 @@ basic_postream<charT, Traits>::operator<
> >  	typedef basic_postream<charT, Traits> postream_type;
> >  	typename postream_type::psentry opfx(*this);
> >  
> > +	outputHeader();
> > +	
> >  	ostream_type::operator<<(n);
> >        
> >  	return *this;
> >  }
> >  
> > -// TODO: #ifdef USE_LONG_LONG
> > +/*
> > +#ifdef USE_LONG_LONG
> >  template<typename charT, typename Traits>
> >  basic_postream<charT, Traits>& 
> >  basic_postream<charT, Traits>::operator<<(long long n)
> > @@ -201,12 +192,15 @@ basic_postream<charT, Traits>::operator<
> >  	// Create a psentry object (may set error bits or throw failure)
> >  	typedef basic_postream<charT, Traits> postream_type;
> >  	typename postream_type::psentry opfx(*this);
> > +
> > +	outputHeader();
> >  	
> >  	ostream_type::operator<<(n);
> >  
> >  	return *this;
> >  }
> > -//#endif
> > +#endif
> > +*/
> >  
> >  template<typename charT, typename Traits>
> >  basic_postream<charT, Traits>& 
> > @@ -216,6 +210,8 @@ basic_postream<charT, Traits>::operator<
> >  	typedef basic_postream<charT, Traits> postream_type;
> >  	typename postream_type::psentry opfx(*this);
> >  	
> > +	outputHeader();
> > +
> >  	ostream_type::operator<<(f);
> >  	
> >  	return *this;
> > @@ -229,6 +225,8 @@ basic_postream<charT, Traits>::operator<
> >  	typedef basic_postream<charT, Traits> postream_type;
> >  	typename postream_type::psentry opfx(*this);
> >  	
> > +	outputHeader(); 
> > +
> >  	ostream_type::operator<<(f);
> >        
> >  	return *this;
> > @@ -242,6 +240,8 @@ basic_postream<charT, Traits>::operator<
> >  	typedef basic_postream<charT, Traits> postream_type;
> >  	typename postream_type::psentry opfx(*this);
> >  
> > +	outputHeader();
> > +
> >  	ostream_type::operator<<(p);
> >        
> >  	return *this;
> > @@ -255,6 +255,8 @@ basic_postream<charT, Traits>::operator<
> >  	typedef basic_postream<charT, Traits> postream_type;
> >  	typename postream_type::psentry opfx(*this);
> >  	
> > +	outputHeader();
> > +
> >  	ostream_type::operator<<(sbin);
> >  	
> >  	return *this;
> > @@ -283,7 +285,7 @@ basic_postream<charT, Traits>::write(con
> >        
> >  	ostream_type::write(s, n);
> >  
> > -	retrn *this;
> > +	return *this;
> >  }
> >  
> >  template<typename charT, typename Traits>
> > @@ -296,7 +298,9 @@ basic_postream<charT, Traits>::flush()
> >  
> >  	ostream_type::flush();
> >  
> > -	//this->unlockStream();
> > +	header = true;
> > + 
> > +	return *this;
> >  }
> >  
> >  template<typename charT, typename Traits>
> > @@ -366,6 +370,8 @@ operator<<(basic_postream<charT, Traits>
> >  	typedef basic_postream<charT, Traits> postream_type;
> >  	typename postream_type::psentry opfx(out);
> >  
> > +	out.outputHeader();
> > +
> >  	std::operator<<(out, c);
> >  	
> >  	return out;
> > @@ -402,6 +408,25 @@ basic_postream<charT, Traits>::widen(cha
> >  	return ostream_type::widen(c);
> >  }
> >  
> > +template<typename charT, typename Traits>
> > +void
> > +basic_postream<charT, Traits>::outputHeader()
> > +{
> > +	pid = static_cast<int>(getpid());
> > +	tid = static_cast<int>(ost::getThread()->getThreadID());
> > +	if (header)
> > +		{
> > +			// Call the ostream methods so as not to have
> > +			// to worry about deadlocking
> > +			std::operator<<(*this, "[Thread ");
> > +			ostream_type::operator<<(tid);
> > +			std::operator<<(*this, " (LWP ");
> > +			ostream_type::operator<<(pid);
> > +			std::operator<<(*this, ")]: ");
> > +		}
> > +	header = false;
> > +}
> > +
> >  // Specializations
> >  template<typename Traits>
> >  basic_postream<char, Traits>&
> > @@ -410,6 +435,8 @@ operator<<(basic_postream<char, Traits>&
> >  	typedef basic_postream<char, Traits> postream_type;
> >  	typename postream_type::psentry opfx(out);
> >        
> > +	out.outputHeader();
> > +
> >  	std::operator<<(out, c);
> >  
> >  	return out;
> > @@ -423,6 +450,8 @@ operator<<(basic_postream<charT, Traits>
> >  	typedef basic_postream<char, Traits> postream_type;
> >  	typename postream_type::psentry opfx(out);
> >  	
> > +	out.outputHeader();
> > +
> >  	std::operator<<(out, s);
> >  	
> >  	return out;
> > @@ -436,7 +465,7 @@ operator<<(basic_postream<charT, Traits>
> >  	typedef basic_postream<char, Traits> postream_type;
> >  	typename postream_type::psentry opfx(out);
> >  	
> > -	out.currth = ost::getThread();
> > +	out.outputHeader();
> >  	
> >  	std::operator<<(out, s);
> >  
> > @@ -452,9 +481,7 @@ operator<<(basic_postream<char, Traits>&
> >  	typedef basic_postream<char, Traits> postream_type;
> >  	typename postream_type::psentry opfx(out);
> >       
> > -	out.currth = ost::getThread();
> > -	int tid = static_cast<int>(out.currth->getThreadID());
> > -	//out.operator<<(tid);
> > +	out.outputHeader();
> >   
> >  	std::operator<<(out, s);
> >  	
> > @@ -471,10 +498,7 @@ operator<<(basic_postream<charT, Traits>
> >  	typedef basic_postream<charT, Traits> postream_type;
> >  	typename postream_type::psentry opfx(out);
> >  
> > -	out.currth = ost::getThread();
> > -	int tid = (int)out.currth->getThreadID();
> > -	//printf("PID: %d\n", getpid());
> > -	//printf("TID: %d\n", tid);
> > +	out.outputHeader();
> >  
> >  	std::operator<<(out, str);
> >  
> > Index: include/cc++/thread.h
> > ===================================================================
> > RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/thread.h,v
> > retrieving revision 1.20
> > diff -u -3 -p -r1.20 thread.h
> > --- include/cc++/thread.h	9 Jan 2003 13:53:09 -0000	1.20
> > +++ include/cc++/thread.h	16 Jan 2003 06:25:24 -0000
> > @@ -1066,6 +1066,7 @@ friend class PosixThread;
> >  /** @internal */
> >  friend class DummyThread;
> >  private:
> > +	friend class postream_type;
> >  	friend class Slog;
> >  
> >  	Semaphore joinSem;
> 
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 

-- 
And if cynics ridicule freedom, ridicule community...if ``hard nosed 
realists'' say that profit is the only ideal...just ignore them, and use 
copyleft all the same.
      -- RMS

Was I helpful?  Let others know: 
  http://svcs.affero.net/rm.php?r=chillywilly



From MAILER-DAEMON Fri Jan 17 20:47:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Zi4g-0005Ac-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 20:47:06 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Zi3O-0003wP-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 20:45:46 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Zi2k-0003la-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 20:45:08 -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 18Zi1k-0003AS-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 20:44:04 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id h0I2Ioq00839;
	Fri, 17 Jan 2003 21:18:50 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Fri, 17 Jan 2003 21:18:50 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
In-Reply-To: <20030117101820.GA4616@bulbasaur.rediris.es>
Message-ID: <Pine.LNX.4.44.0301172118310.731-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Albert Strasheim <albert@dogbert.sdsl.sun.ac.za>
cc: bug-commoncpp@gnu.org
cc: Chad Yates <cyates@uidaho.edu>
Subject: Re: 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: Sat, 18 Jan 2003 01:46:55 -0000


I am actually away until tomorrow, but I want to think about both these 
issues...

On Fri, 17 Jan 2003, Federico Montesino Pouzols wrote:

> 
> 	Restarting the discussion on the CC++ templates, anyway with
> the current directory layout there does not seem to be a clear way to
> include tests/demos for the templates. Should we move the templates to
> the general headers directory, at least in 1.1?
> 
> 	Also, when UberCounter gets in cc++ 1.1, we will have
> templates in ccgnu2...
> 
> On Fri, Jan 03, 2003 at 08:31:10AM -0500, David Sugar wrote:
> > Ah yes, the mozilla c++ recommendations...
> > 
> > We may choose to keep the ccgnu2 half very clean in large part to enable one 
> > to build very compact applications with Common C++, but I do not think we 
> > ever got that anal even in that.  If anything, as practices and compilers 
> > improve, we will continue to make greater use of the C++ language standard in 
> > full.  However, the reality is that many broken compilers and poor std 
> > library/stl implimentations still remain in everyday use so we do have to 
> > pick and choose what language features we will make use of extensivily and 
> > which we will not.  I much prefer isolating language features with 
> > troublesome implimention history rather than excluding them, which is why we 
> > had the templates library segregated, for example, or extensive facilities to 
> > built with or without exception handling. 
> > 
> > On Friday 03 January 2003 01:37, Chad Yates wrote:
> > > I also read that portable-cpp file a while ago and was actually appauled by
> > > it.  It's my opinion that if compilers should be updated to the standard
> > > (expected) functionality or new compilers should be found/used.  they
> > > pretty much said not to use any of C++'s nice features, they may as well
> > > have said just don't use C++.  Please don't let common c++ go that
> > > direction.
> > >
> > > my 2 cents
> > >
> > > ,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: Thursday, January 02, 2003 6:25 AM
> > > > To: David Sugar
> > > > Cc: bug-commoncpp@gnu.org
> > > > Subject: Re: Headers and templated classes
> > >
> > > (snip)
> > >
> > > > How many commercial compilers are still out there that handle templates
> > > > poorly? I came across an interesting article, C++ portability guide,
> > > > from mozilla.org,
> > > >
> > > > http://www.mozilla.org/hacking/portable-cpp.html
> > > >
> > > > They say to avoid templates. But also to avoid exceptions. (This was
> > > > in 1998.) So I don't know where you draw the line. Personally, if
> > > > you're not using gcc 3.2, you deserve to suffer, but I guess my
> > > > philosophy doesn't work too well for an open source project. :-)
> > > >
> > > > It seems C++ templates have been around since 1995. So one has to ask
> > > > the question: if your compiler doesn't support it after more than 8
> > > > years, is it ever going to support it?
> > >
> > > (snip)
> > >
> > >
> > >
> > > _______________________________________________
> > > 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 MAILER-DAEMON Fri Jan 17 20:50:17 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Zi6l-0007A3-00
	for mharc-bug-commoncpp@gnu.org; Fri, 17 Jan 2003 20:49:15 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Zi4U-0004vo-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 20:46:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Zi4P-0004mK-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 20:46:50 -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 18Zi4C-0004SJ-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 20:46:36 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id h0I2Ldp00864;
	Fri, 17 Jan 2003 21:21:39 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Fri, 17 Jan 2003 21:21:39 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
In-Reply-To: <20030117120909.GG4616@bulbasaur.rediris.es>
Message-ID: <Pine.LNX.4.44.0301172121010.731-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bug-commoncpp@gnu.org
Subject: Re: CC++ 2 home page
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, 18 Jan 2003 01:49:13 -0000


I think it is important to update the contributor info files.

On Fri, 17 Jan 2003, Federico Montesino Pouzols wrote:

> 
> 	I have updated the cc++ page. Does anyone think that we should
> include any additional information or fix there? Suggestions?
> 
> 	Yes, I know, we should compile a list of people who have helped
> for the last months in order to update the contributors list and the
> THANKS file :)
> 
> On Thu, Jan 09, 2003 at 05:01:31AM -0500, David Sugar wrote:
> > Yes, that is nice.  We really should update the common c++ (and ccrtp) pages a 
> > lot and also reference the link to the archive on them...
> > 
> > On Thursday 09 January 2003 04:41, Federico Montesino Pouzols wrote:
> > > It seems that the list has been frozen for two or three days,
> > > but I now see all the posts that you have reposted with '(copy)'
> > > appended. In the meantime, the mail archives are working again, now
> > > based on MHonArc. By the way, this new interface allows for searching
> > > through the archives.
> > >
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From MAILER-DAEMON Sat Jan 18 10:08:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZuZi-0004Bg-00
	for mharc-bug-commoncpp@gnu.org; Sat, 18 Jan 2003 10:07:58 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZuYg-00031x-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 10:06:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZuWO-0008OT-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 10:04:33 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZuUK-0005Qr-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 10:02:24 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18ZuV0-0005DO-00; Sat, 18 Jan 2003 16:03:06 +0100
Date: Sat, 18 Jan 2003 16:03:06 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ian Gough <igough@gridiron-networks.com>
Message-ID: <20030118150306.GB19918@bulbasaur.rediris.es>
Mail-Followup-To: Ian Gough <igough@gridiron-networks.com>,
	bug-commoncpp@gnu.org
References: <000501c2be5e$98689830$0c02a8c0@gridironnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000501c2be5e$98689830$0c02a8c0@gridironnetworks.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Process::spawn() and atexit()
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: Sat, 18 Jan 2003 15:07:57 -0000


	I see, I have added a '@warning' tag with a paragraph on this
issue to the spawn doxygen doc.

On Fri, Jan 17, 2003 at 02:28:21PM -0500, Ian Gough wrote:
> On Win32, Process::spawn() blocks as it spawns a new process. On all
> other platforms, it forks, execs and then waits. The side effect comes
> in that the parent process of the fork then exits, which causes the
> function set up in atexit() to be called.
>  
> Normally, this wouldn't cause a problem, but the app I am building is a
> server that spawns multiple processes and sets up communications links
> to each of the children. To make sure the system gets shutdown
> gracefully, in the atexit function I caused the server to tell each of
> the children to quit gracefully. Now this works fine in Win32, but on
> unix, due to the forking, the atexit function gets called when the
> parent process of the fork exits, which causes the shutdown message to
> be sent to the child processes before the server portion is actually
> exiting, thereby tearing down half the system.
>  
> I think that perhaps this side effect needs to be documented for the
> Process::spawn() method so that people can be aware there are issues
> with using atexit() and spawn().
>  
>  

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




From MAILER-DAEMON Sat Jan 18 17:10:07 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a1A9-0004kT-00
	for mharc-bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:10:01 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a19s-0003sD-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:09:44 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a19V-0002ky-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:09:24 -0500
Received: from service.sh.cvut.cz ([147.32.127.214])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18a19T-0002du-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:09:19 -0500
Received: from spampd.localdomain (localhost [127.0.0.1])
	by service.sh.cvut.cz (Postfix) with ESMTP id E9B1C1B8417
	for <bug-commoncpp@gnu.org>; Sat, 18 Jan 2003 23:09:17 +0100 (CET)
Received: from logout.sh.cvut.cz (logout.sh.cvut.cz [147.32.127.203])
	by service.sh.cvut.cz (Postfix) with ESMTP id 676E11B837F
	for <bug-commoncpp@gnu.org>; Sat, 18 Jan 2003 23:09:17 +0100 (CET)
Received: from logout (logout [147.32.127.203])
	by logout.sh.cvut.cz (Postfix) with ESMTP id 196E73C0B7
	for <bug-commoncpp@gnu.org>; Sat, 18 Jan 2003 23:09:26 +0100 (CET)
Date: Sat, 18 Jan 2003 23:09:26 +0100 (CET)
From: Vaclav Haisman <V.Haisman@sh.cvut.cz>
To: bug-commoncpp@gnu.org
Message-ID: <20030118230030.I90381-100000@logout.sh.cvut.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanned-By: AMaViS at Silicon Hill
Subject: Is CommonC++ still maintained?
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, 18 Jan 2003 22:09:59 -0000


I ask because I downloaded CommonC++ sources from SourceForge CVS and they
won't even compile without a this included patchlet.
Second thing that surprised me is that now non-conforming C++ strstream
header is still used.

Vaclav Haisman


Index: include/cc++/exception.h
===================================================================
RCS file: /cvsroot/cplusplus/CommonC++/include/cc++/exception.h,v
retrieving revision 1.3
diff -u -r1.3 exception.h
--- include/cc++/exception.h    30 Jun 2002 09:19:24 -0000      1.3
+++ include/cc++/exception.h    18 Jan 2003 22:04:56 -0000
@@ -78,7 +78,7 @@
        Exception(const std::string& what_arg) throw();
        virtual ~Exception() throw();
        virtual const char *getString() const;
-       virtual const char *what() const { return _what.c_str(); };
+       virtual const char *what() const throw () { return _what.c_str();
};
 };

 /**




From MAILER-DAEMON Sat Jan 18 17:33:29 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a1WO-0006Fs-00
	for mharc-bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:33:01 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a1Vv-0005UE-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:32:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a1Ve-0004qV-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:32:21 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18a1VK-0003pN-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:31:54 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18a1Vy-0005HU-00; Sat, 18 Jan 2003 23:32:34 +0100
Date: Sat, 18 Jan 2003 23:32:34 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030118223233.GC19918@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>,
	Albert Strasheim <fullung-ccpp@dogbert.sdsl.sun.ac.za>,
	bug-commoncpp@gnu.org
References: <20030117105715.GC4616@bulbasaur.rediris.es>
	<NBBBJJODBJBNJFNIDDCNAEEFDEAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNAEEFDEAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Test framework
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: Sat, 18 Jan 2003 22:32:58 -0000

On Fri, Jan 17, 2003 at 11:10:32AM -0800, Chad Yates wrote:
> 
> > 	Yes, some headers could be partitioned, digest.h could be a
> > header that just includes md5.h, sha.h, etc, composing a kind of
> > digest subsistem. I think that whether one header should hold one or
> > more classes depends on the structure of the system. For instance, SHA
> > is implemented with several classes; I would see it very extreme to
> > make one header for each class.
> 
> I agree.  should I go ahead and re-org the persistence engine or digest
> classes when I have time, and then submit the resulting structure?
> 

	If nobody objects to this, let's do the re-org.

> ,chad
> 



From MAILER-DAEMON Sat Jan 18 17:37:33 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a1am-00061C-00
	for mharc-bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:37:32 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a1aj-0005wP-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:37:29 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a1a9-0005de-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:36:54 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18a1Zw-0005Z8-00
	for bug-commoncpp@gnu.org; Sat, 18 Jan 2003 17:36:40 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18a1ah-0005Hn-00; Sat, 18 Jan 2003 23:37:27 +0100
Date: Sat, 18 Jan 2003 23:37:26 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Vaclav Haisman <V.Haisman@sh.cvut.cz>
Message-ID: <20030118223726.GD19918@bulbasaur.rediris.es>
Mail-Followup-To: Vaclav Haisman <V.Haisman@sh.cvut.cz>,
	bug-commoncpp@gnu.org
References: <20030118230030.I90381-100000@logout.sh.cvut.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030118230030.I90381-100000@logout.sh.cvut.cz>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Is CommonC++ still maintained?
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: Sat, 18 Jan 2003 22:37:30 -0000


	Yes, it is maintained :). Currently, Savannah (sv.gnu.org) is
preferred to Sourceforge. As always, later releases (which now include
the fix you mention) can be downloaded from any GNU mirror.

	The SF site is now rather outdated, perhaps we should put a
note there pointing to savannah...

On Sat, Jan 18, 2003 at 11:09:26PM +0100, Vaclav Haisman wrote:
> 
> I ask because I downloaded CommonC++ sources from SourceForge CVS and they
> won't even compile without a this included patchlet.
> Second thing that surprised me is that now non-conforming C++ strstream
> header is still used.
> 
> Vaclav Haisman
> 
> 



From MAILER-DAEMON Sun Jan 19 10:07:40 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aH2r-0003Vk-00
	for mharc-bug-commoncpp@gnu.org; Sun, 19 Jan 2003 10:07:33 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Zhqj-0002pQ-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 20:32:41 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Zhqg-0002kz-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 20:32:39 -0500
Received: from tandem.milestonerdl.com ([204.107.138.1])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Zhq7-0002JV-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 20:32:03 -0500
Received: from tandem.milestonerdl.com (tandem.milestonerdl.com
	[204.107.138.1])h0I1GQ9l087813
	for <bug-commoncpp@gnu.org>; Fri, 17 Jan 2003 19:16:26 -0600 (CST)
	(envelope-from marc@milestonerdl.com)
Date: Fri, 17 Jan 2003 19:16:26 -0600 (CST)
From: Marc Rassbach <marc@milestonerdl.com>
To: bug-commoncpp@gnu.org
Message-ID: <20030117191344.H86724-100000@tandem.milestonerdl.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Sun, 19 Jan 2003 10:07:29 -0500
Subject: Compile problem
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, 18 Jan 2003 01:32:47 -0000

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
socket.cpp  -fPIC -DPIC -o .libs/socket.lo
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
socket.cpp -o socket.o >/dev/null 2>&1
mv -f .libs/socket.lo socket.lo
/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
-D_THREAD_SAFE  -I/usr/local/include/libxml2 -I/usr/local/include
-I../include -c network.cpp
rm -f .libs/network.lo
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::NetworkDeviceInfo>
> &)':
network.cpp:119: `struct ifreq' has no member named `ifr_netmask'
*** Error code 1

Stop in /usr/home/marc/src/commoncpp2-1.0.7/src.
*** Error code 1

FreeBSD phone.int.milestonerdl.com 4.7-STABLE FreeBSD 4.7-STABLE #4: Fri
Jan 17 09:53:05 CST 2003
marc@phone.int.milestonerdl.com:/usr/obj/usr/src/sys/DUALV  i386




From MAILER-DAEMON Sun Jan 19 10:07:41 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aH2q-0003Uw-00
	for mharc-bug-commoncpp@gnu.org; Sun, 19 Jan 2003 10:07:32 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZfNv-0004ub-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 17:54:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZfNF-0004Gi-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 17:54:14 -0500
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZfNC-0004AG-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 17:54:02 -0500
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 18ZfNA-0007jC-00; Fri, 17 Jan 2003 17:54:00 -0500
To: bug-commoncpp@gnu.org,jmvignes@broadpark.no,fedemp@altern.org,noreply@savannah.gnu.org
From: nobody@savannah.gnu.org
Message-Id: <E18ZfNA-0007jC-00@subversions.gnu.org>
Date: Fri, 17 Jan 2003 17:54:00 -0500
X-Mailman-Approved-At: Sun, 19 Jan 2003 10:07:29 -0500
Subject: [Bug #2128] Weird troubles with iostream and commonc++
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, 17 Jan 2003 22:54:56 -0000


=================== BUG #2128: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=2128&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: 2003-Jan-17 23:53 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | None                      | fedemp
                  CC |                           | bug-commoncpp@gnu.org


------------------ Additional Follow-up Comments ----------------------------
Curiously enough, gcc 3.x seems to handle this
without trouble. It seems that gcc 2.9x finds
an ambiguity because of the Digest related <<
operators. I guess the easiest way to get 
around this problem is using test.c_str() 
instead of test, which seems to make gcc happy.




=================== BUG #2128: FULL BUG SNAPSHOT ===================


Submitted by: inful                   Project: commonc++                    
Submitted on: 2003-Jan-03 20:53
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  fedemp                  Status:  Open                         

Summary:  Weird troubles with iostream and commonc++

Original Submission:  The following snippet is the minimum of code needed to display the problem:
#include <cc++/digest.h>
#include <iostream>
#include <string>
int main(){
  const string &test("d");
  cout << test << endl;
}
When compiled, the following error-messages appear:
test.cpp: In function `int main()':
test.cpp:6: no match for `_IO_ostream_withassign & << const basic_string<char,string_char_traits<char>,__default_alloc_template<true,0> > &'
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:77: candidates are: class ostream & ostream::operator <<(char)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:78:                 class ostream & ostream::operator <<(unsigned char)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:79:                 class ostream & ostream::operator <<(signed char)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:80:                 class ostream & ostream::operator <<(const char *)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:82:                 class ostream & ostream::operator <<(const unsigned char *)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:84:                 class ostream & ostream::operator <<(const signed char *)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:85:                 class ostream & ostream::operator <<(const void *)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:86:                 class ostream & ostream::operator <<(int)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:87:                 class ostream & ostream::operator <<(unsigned int)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:88:                 class ostream & ostream::operator <<(long int)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:89:                 class ostream & ostream::operator <<(long unsigned int)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:91:                 class ostream & ostream::operator <<(long long int)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:92:                 class ostream & ostream::operator <<(long long unsigned int)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:94:                 class ostream & ostream::operator <<(short int)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:95:                 class ostream & ostream::operator <<(short unsigned int)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:97:                 class ostream & ostream::operator <<(bool)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:99:                 class ostream & ostream::operator <<(double)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:100:                 class ostream & ostream::operator <<(float)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:102:                 class ostream & ostream::operator <<(long double)
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:106:                 class ostream & ostream::operator <<(ostream & (*)(ostream &))
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:107:                 class ostream & ostream::operator <<(ios & (*)(ios &))
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/iostream.h:108:                 class ostream & ostream::operator <<(streambuf *)
/usr/include/cc++2/cc++/digest.h:125:                 class ostream & ost::operator <<(ostream &, ost::Digest &)
/usr/include/cc++2/cc++/digest.h:299:                 class ostream & ost::operator <<(ostream &, ost::SHATumbler<unsigned int> &)

This problem goes away as soon as you comment out 
#include <cc++/digest.h>


Follow-up Comments
*******************

-------------------------------------------------------
Date: 2003-Jan-17 23:53             By: fedemp
Curiously enough, gcc 3.x seems to handle this
without trouble. It seems that gcc 2.9x finds
an ambiguity because of the Digest related <<
operators. I guess the easiest way to get 
around this problem is using test.c_str() 
instead of test, which seems to make gcc happy.



CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=2128&group_id=89



From MAILER-DAEMON Sun Jan 19 10:08:44 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aH2q-0003Tc-00
	for mharc-bug-commoncpp@gnu.org; Sun, 19 Jan 2003 10:07:32 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZbX4-00026B-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 13:47:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZbPI-0004xL-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 13:40:02 -0500
Received: from [209.213.209.206] (helo=mail1.aasage.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZbNB-0002NP-00
	for bug-commoncpp@gnu.org; Fri, 17 Jan 2003 13:37:45 -0500
Received: from sf_mail.aasage.com (sf_mail.aasage.net [134.141.20.227])
	by mail1.aasage.com (8.11.6+Sun/8.11.6) with ESMTP id h0HIcCM29358
	for <bug-commoncpp@gnu.org>; Fri, 17 Jan 2003 10:38:12 -0800 (PST)
Received: by sf-mail.aasage.net with Internet Mail Service (5.5.2653.19)
	id <C7HRSM47>; Fri, 17 Jan 2003 10:33:54 -0800
Message-ID: <857B39B0D65BD311B14B0050DA0E107004033B31@sf-mail.aasage.net>
From: "Matthieu.Labour" <Matthieu.Labour@aasage.com>
To: "'bug-commoncpp@gnu.org'" <bug-commoncpp@gnu.org>
Date: Fri, 17 Jan 2003 10:33:53 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2BE56.FC9085F0"
X-Mailman-Approved-At: Sun, 19 Jan 2003 10:07:29 -0500
Subject: compiling for AIX
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, 17 Jan 2003 18:48:40 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2BE56.FC9085F0
Content-Type: text/plain;
	charset="iso-8859-1"

Hi, 

I try to compile commoncpp2-1.0.7 on AIX5.1. I am using the xlc_r compiler
version 6.

First, I had to add the xlc_r compiler in ./configure as followed otherwise
'configure' would fail.

for ac_prog in $CCC xlc_r c++ g++ gcc CC cxx cc++ cl

When I type 'make' to compile the package I get the following error

xlc_r -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
-I/usr/local/include -D_GNU_SOURCE -D_THREAD_SAFE -I../include -c
semaphore.cpp  -DPIC -o .libs/semaphore.lo
"semaphore.cpp", line 76.38: 1540-0274 (S) The name lookup for "throwObject"
did not find a declaration.
"semaphore.cpp", line 79.43: 1540-0274 (S) The name lookup for
"throwException" did not find a declaration.

and I can't actually  find the trowObject declaration in the package. Am I
missing something here ?

Thank you for your help

Matthieu


------_=_NextPart_001_01C2BE56.FC9085F0
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 =
5.5.2653.12">
<TITLE>compiling for AIX</TITLE>
</HEAD>
<BODY>

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

<P><FONT SIZE=3D2 FACE=3D"Arial">I try to compile commoncpp2-1.0.7 on =
AIX5.1. I am using the xlc_r compiler version 6.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">First, I had to add the xlc_r compiler =
in ./configure as followed otherwise 'configure' would fail.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">for ac_prog in $CCC xlc_r c++ g++ gcc =
CC cxx cc++ cl</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">When I type 'make' to compile the =
package I get the following error</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">xlc_r -DHAVE_CONFIG_H -I. -I. =
-I../include -I../src -DCCXX_EXPORT_LIBRARY -I/usr/local/include =
-D_GNU_SOURCE -D_THREAD_SAFE -I../include -c semaphore.cpp&nbsp; -DPIC =
-o .libs/semaphore.lo</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&quot;semaphore.cpp&quot;, line 76.38: =
1540-0274 (S) The name lookup for &quot;throwObject&quot; did not find =
a declaration.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&quot;semaphore.cpp&quot;, line =
79.43: 1540-0274 (S) The name lookup for &quot;throwException&quot; did =
not find a declaration.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">and I can't actually&nbsp; find the =
trowObject declaration in the package. Am I missing something here =
?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thank you for your help</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Matthieu</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2BE56.FC9085F0--



From MAILER-DAEMON Mon Jan 20 03:54:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aXhH-0003dz-00
	for mharc-bug-commoncpp@gnu.org; Mon, 20 Jan 2003 03:54:23 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aXhF-0003Zz-00
	for bug-commoncpp@gnu.org; Mon, 20 Jan 2003 03:54:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aXhC-0003XP-00
	for bug-commoncpp@gnu.org; Mon, 20 Jan 2003 03:54:19 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aXhB-0003Ok-00
	for bug-commoncpp@gnu.org; Mon, 20 Jan 2003 03:54:17 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18aXhb-0000M7-00; Mon, 20 Jan 2003 09:54:43 +0100
Date: Mon, 20 Jan 2003 09:54:40 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Marc Rassbach <marc@milestonerdl.com>
Message-ID: <20030120085431.GA242@bulbasaur.rediris.es>
Mail-Followup-To: Marc Rassbach <marc@milestonerdl.com>,
	bug-commoncpp@gnu.org
References: <20030117191344.H86724-100000@tandem.milestonerdl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030117191344.H86724-100000@tandem.milestonerdl.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: Compile problem
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, 20 Jan 2003 08:54:22 -0000


	This is already fixed in CVS for 1.0.8. In the meantime you
can quickly fix it replacing ifr_netmask with ifr_addr, if you prefer
not to use CVS.

On Fri, Jan 17, 2003 at 07:16:26PM -0600, Marc Rassbach wrote:
> 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
> socket.cpp  -fPIC -DPIC -o .libs/socket.lo
> 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
> socket.cpp -o socket.o >/dev/null 2>&1
> mv -f .libs/socket.lo socket.lo
> /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
> -D_THREAD_SAFE  -I/usr/local/include/libxml2 -I/usr/local/include
> -I../include -c network.cpp
> rm -f .libs/network.lo
> 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::NetworkDeviceInfo>
> > &)':
> network.cpp:119: `struct ifreq' has no member named `ifr_netmask'
> *** Error code 1
> 
> Stop in /usr/home/marc/src/commoncpp2-1.0.7/src.
> *** Error code 1
> 
> FreeBSD phone.int.milestonerdl.com 4.7-STABLE FreeBSD 4.7-STABLE #4: Fri
> Jan 17 09:53:05 CST 2003
> marc@phone.int.milestonerdl.com:/usr/obj/usr/src/sys/DUALV  i386
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Mon Jan 20 04:01:46 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aXoB-0005uD-00
	for mharc-bug-commoncpp@gnu.org; Mon, 20 Jan 2003 04:01:31 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aXns-00056H-00
	for bug-commoncpp@gnu.org; Mon, 20 Jan 2003 04:01:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aXnb-0004ss-00
	for bug-commoncpp@gnu.org; Mon, 20 Jan 2003 04:00:58 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aXnR-0004SZ-00
	for bug-commoncpp@gnu.org; Mon, 20 Jan 2003 04:00:46 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18aXnu-0000U8-00; Mon, 20 Jan 2003 10:01:14 +0100
Date: Mon, 20 Jan 2003 10:01:14 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Matthieu.Labour" <Matthieu.Labour@aasage.com>
Message-ID: <20030120090114.GB242@bulbasaur.rediris.es>
Mail-Followup-To: "Matthieu.Labour" <Matthieu.Labour@aasage.com>,
	"'bug-commoncpp@gnu.org'" <bug-commoncpp@gnu.org>
References: <857B39B0D65BD311B14B0050DA0E107004033B31@sf-mail.aasage.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <857B39B0D65BD311B14B0050DA0E107004033B31@sf-mail.aasage.net>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: "'bug-commoncpp@gnu.org'" <bug-commoncpp@gnu.org>
Subject: Re: compiling for AIX
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, 20 Jan 2003 09:01:30 -0000


	Hi,...

On Fri, Jan 17, 2003 at 10:33:53AM -0800, Matthieu.Labour wrote:
> Hi, 
> 
> I try to compile commoncpp2-1.0.7 on AIX5.1. I am using the xlc_r compiler
> version 6.
> 
> First, I had to add the xlc_r compiler in ./configure as followed otherwise
> 'configure' would fail.
> 
> for ac_prog in $CCC xlc_r c++ g++ gcc CC cxx cc++ cl
> 

	You can make it in a somewhat more elegant manner using
something like:
	
	$ CC=xlc_r CXX=xlc_r ./configure ...

	Other configure options are explain in INSTALL and in
configure --help.


> When I type 'make' to compile the package I get the following error
> 
> xlc_r -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
> -I/usr/local/include -D_GNU_SOURCE -D_THREAD_SAFE -I../include -c
> semaphore.cpp  -DPIC -o .libs/semaphore.lo
> "semaphore.cpp", line 76.38: 1540-0274 (S) The name lookup for "throwObject"
> did not find a declaration.
> "semaphore.cpp", line 79.43: 1540-0274 (S) The name lookup for
> "throwException" did not find a declaration.
> 
> and I can't actually  find the trowObject declaration in the package. Am I
> missing something here ?
> 

	Um, it is a bug that other compilers had ignored. These
identifiers should be Thread::throwObject and Thread::throwException,
respectively. I have fixed it in CVS for 1.0.8.

> Thank you for your help
> 
> Matthieu
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Mon Jan 20 10:09:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18adY2-0003H5-00
	for mharc-bug-commoncpp@gnu.org; Mon, 20 Jan 2003 10:09:14 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18adXz-0003Df-00
	for bug-commoncpp@gnu.org; Mon, 20 Jan 2003 10:09:11 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18adXy-0003DQ-00
	for bug-commoncpp@gnu.org; Mon, 20 Jan 2003 10:09:10 -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 18adXp-00030N-00
	for bug-commoncpp@gnu.org; Mon, 20 Jan 2003 10:09:01 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h0KFiOe10860;
	Mon, 20 Jan 2003 10:44:25 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>,
   Marc Rassbach <marc@milestonerdl.com>
Date: Mon, 20 Jan 2003 10:10:18 -0500
User-Agent: KMail/1.4.3
References: <20030117191344.H86724-100000@tandem.milestonerdl.com>
	<20030120085431.GA242@bulbasaur.rediris.es>
In-Reply-To: <20030120085431.GA242@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301201010.18258.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: Compile problem
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, 20 Jan 2003 15:09:12 -0000

I was away over the weekend, and I am largely tied up with demonstrating =
the=20
GNU telephone system this week at LinuxWorld, but I am hoping we can get =
the=20
1.0.8 release out very soon which covers this and many other issues...

On Monday 20 January 2003 03:54, Federico Montesino Pouzols wrote:
> This is already fixed in CVS for 1.0.8. In the meantime you
> can quickly fix it replacing ifr_netmask with ifr_addr, if you prefer
> not to use CVS.
>
> On Fri, Jan 17, 2003 at 07:16:26PM -0600, Marc Rassbach wrote:
> > 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
> > socket.cpp  -fPIC -DPIC -o .libs/socket.lo
> > 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
> > socket.cpp -o socket.o >/dev/null 2>&1
> > mv -f .libs/socket.lo socket.lo
> > /bin/sh ../libtool --mode=3Dcompile 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
> > rm -f .libs/network.lo
> > 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
> >orkDeviceInfo>
> >
> > > &)':
> >
> > network.cpp:119: `struct ifreq' has no member named `ifr_netmask'
> > *** Error code 1
> >
> > Stop in /usr/home/marc/src/commoncpp2-1.0.7/src.
> > *** Error code 1
> >
> > FreeBSD phone.int.milestonerdl.com 4.7-STABLE FreeBSD 4.7-STABLE #4: =
Fri
> > Jan 17 09:53:05 CST 2003
> > marc@phone.int.milestonerdl.com:/usr/obj/usr/src/sys/DUALV  i386
> >
> >
> >
> > _______________________________________________
> > 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 MAILER-DAEMON Tue Jan 21 05:05:09 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18avH4-0002pb-00
	for mharc-bug-commoncpp@gnu.org; Tue, 21 Jan 2003 05:04:54 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18avGY-0002jf-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 05:04:22 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18avFf-0002ZO-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 05:03:41 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18avBl-0001XY-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 04:59:25 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18avBh-0000TY-00; Tue, 21 Jan 2003 10:59:21 +0100
Date: Tue, 21 Jan 2003 10:59:21 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ian Gough <igough@gridiron-networks.com>
Message-ID: <20030121095921.GA1550@bulbasaur.rediris.es>
Mail-Followup-To: Ian Gough <igough@gridiron-networks.com>,
	'bug-commoncpp' <bug-commoncpp@gnu.org>
References: <20030117123908.GI4616@bulbasaur.rediris.es>
	<000401c2be56$b9e34760$0c02a8c0@gridironnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000401c2be56$b9e34760$0c02a8c0@gridironnetworks.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
Subject: Re: Building CC++ on Mac OS X
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, 21 Jan 2003 10:04:37 -0000

On Fri, Jan 17, 2003 at 01:32:01PM -0500, Ian Gough wrote:
> > > 3) in socket.h: socklen_t is undefined. I found references 
> > on the inet 
> > > that spec that FreeBSD prior to 4.x and Solaris prior to 7 (2.7) do 
> > > not define the type socklen_t and some of the mac os X is based on 
> > > FreeBSD 4.4. To cause this to be defined, I included 
> > > -D_BSD_SOCKLEN_T_=int in the Makefile.
> > > 
> > 
> > 	Um, we will add a configuration test for this, in order 
> > to define _BSD_SOCKLEN_T when it is missing.
> > 

	Um, I have just looked at this and actually there is already
some autoconf stuff. Could you confirm if, in the config.h of cc++,
the symbol HAVE_SOCKLEN_T is undefined?



From MAILER-DAEMON Tue Jan 21 10:20:19 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18b06C-00062P-00
	for mharc-bug-commoncpp@gnu.org; Tue, 21 Jan 2003 10:14:00 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18awRg-0006C7-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 06:19:56 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18awQp-00062O-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 06:19:19 -0500
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18awQK-0005qy-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 06:18:32 -0500
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 18awP1-0003jj-00; Tue, 21 Jan 2003 06:17:11 -0500
To: bug-commoncpp@gnu.org,raoleary@btinternet.com,fedemp@altern.org,noreply@savannah.gnu.org
From: nobody@savannah.gnu.org
Message-Id: <E18awP1-0003jj-00@subversions.gnu.org>
Date: Tue, 21 Jan 2003 06:17:11 -0500
X-Mailman-Approved-At: Tue, 21 Jan 2003 10:13:58 -0500
Subject: [Bug #2251] network.cpp: make fails on Solaris 8
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, 21 Jan 2003 11:54:07 -0000


=================== BUG #2251: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=2251&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: 2003-Jan-21 12:16 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
         Assigned to | None                      | fedemp
              Status | Open                      | Closed
                  CC |                           | bug-commoncpp@gnu.org


------------------ Additional Follow-up Comments ----------------------------

   Hi, I have just commited some code and autoconf stuff so
that sys/sockio.h is included when available. The issue with
ifr_netmask was already fixed in CVS, you can safely replace
ifr_netmask with ifr_addr.



=================== BUG #2251: FULL BUG SNAPSHOT ===================


Submitted by: raoleary                Project: commonc++                    
Submitted on: 2003-Jan-19 17:37
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Fixed                    
Assigned to:  fedemp                  Status:  Closed                       

Summary:  network.cpp: make fails on Solaris 8

Original Submission:  Hi, After ./configure, make fails at network.cpp:

/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 -D_REENTRANT  -I../include -c network.cpp
rm -f .libs/network.lo
c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY -I/usr/local/include -D_GNU_SOURCE -D_REENTRANT -I../include -c network.cpp  -fPIC -DPIC -o .libs/network.lo
In file included from /usr/include/fcntl.h:18,
                 from ../include/cc++/config.h:344,
                 from network.cpp:41:
/usr/include/sys/feature_tests.h:143: warning: `_POSIX_PTHREAD_SEMANTICS' redefined
../include/cc++/config.h:306: warning: this is the location of the previous definition
network.cpp: In function `bool ost::enumNetworkDevices(vector<ost::NetworkDeviceInfo,allocator<ost::NetworkDeviceInfo> > &)':
network.cpp:91: `SIOCGIFCONF' undeclared (first use this function)
network.cpp:91: (Each undeclared identifier is reported only once
network.cpp:91: for each function it appears in.)
network.cpp:112: `SIOCGIFBRDADDR' undeclared (first use this function)
network.cpp:117: `SIOCGIFNETMASK' undeclared (first use this function)
network.cpp:120: `struct ifreq' has no member named `ifr_netmask'
network.cpp:122: `SIOCGIFMTU' undeclared (first use this function)
network.cpp:125: `struct ifreq' has no member named `ifr_mtu'
*** Error code 1
make: Fatal error: Command failed for target `network.lo'
Current working directory /opt/sunr1/commoncpp2-1.0.7/src
*** Error code 1
make: Fatal error: Command failed for target `all-recursive'


Including sockio.h fixes the macro ioctls but the missing struct members are still a problem:
/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 -D_REENTRANT  -I../include -c network.cpp
rm -f .libs/network.lo
c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY -I/usr/local/include -D_GNU_SOURCE -D_REENTRANT -I../include -c network.cpp  -fPIC -DPIC -o .libs/network.lo
In file included from /usr/include/fcntl.h:18,
                 from ../include/cc++/config.h:344,
                 from network.cpp:41:
/usr/include/sys/feature_tests.h:143: warning: `_POSIX_PTHREAD_SEMANTICS' redefined
../include/cc++/config.h:306: warning: this is the location of the previous definition
network.cpp: In function `bool ost::enumNetworkDevices(vector<ost::NetworkDeviceInfo,allocator<ost::NetworkDeviceInfo> > &)':
network.cpp:120: `struct ifreq' has no member named `ifr_netmask'
network.cpp:125: `struct ifreq' has no member named `ifr_mtu'
*** Error code 1
make: Fatal error: Command failed for target `network.lo'
Current working directory /opt/sunr1/commoncpp2-1.0.7/src
*** Error code 1
make: Fatal error: Command failed for target `all-recursive'

There is an mtu member in the newer lifreq but no netmask member.

Regards,
Rob

Follow-up Comments
*******************

-------------------------------------------------------
Date: 2003-Jan-21 12:16             By: fedemp

   Hi, I have just commited some code and autoconf stuff so
that sys/sockio.h is included when available. The issue with
ifr_netmask was already fixed in CVS, you can safely replace
ifr_netmask with ifr_addr.


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=2251&group_id=89



From MAILER-DAEMON Tue Jan 21 10:34:05 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18b0H4-0001Ww-00
	for mharc-bug-commoncpp@gnu.org; Tue, 21 Jan 2003 10:25:14 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18b0GT-0001LN-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 10:24:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18b0FC-0000qz-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 10:23:20 -0500
Received: from mx4.magma.ca ([206.191.0.253])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18azh3-0006yh-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 09:48:02 -0500
Received: from mail6.magma.ca (mail6 [206.191.0.248])
	by mx4.magma.ca (Magma's Mail Server) with ESMTP id h0LElwRJ015654;
	Tue, 21 Jan 2003 09:47:58 -0500
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail6.magma.ca (Magma's Mail Server) with ESMTP id h0LElvsu011705;
	Tue, 21 Jan 2003 09:47:58 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: "'Federico Montesino Pouzols'" <fedemp@altern.org>
Date: Tue, 21 Jan 2003 09:47:57 -0500
Message-ID: <000701c2c15c$16876840$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <20030121095921.GA1550@bulbasaur.rediris.es>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
Subject: RE: Building CC++ on Mac OS X
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, 21 Jan 2003 15:25:12 -0000

> -----Original Message-----
> From: Federico Montesino Pouzols 
> [mailto:fedemp@bulbasaur.rediris.es] On Behalf Of Federico 
> Montesino Pouzols
> Sent: Tuesday, January 21, 2003 4:59 AM
> To: Ian Gough
> Cc: 'bug-commoncpp'
> Subject: Re: Building CC++ on Mac OS X
> 
> 
> On Fri, Jan 17, 2003 at 01:32:01PM -0500, Ian Gough wrote:
> > > > 3) in socket.h: socklen_t is undefined. I found references
> > > on the inet
> > > > that spec that FreeBSD prior to 4.x and Solaris prior 
> to 7 (2.7) 
> > > > do
> > > > not define the type socklen_t and some of the mac os X 
> is based on 
> > > > FreeBSD 4.4. To cause this to be defined, I included 
> > > > -D_BSD_SOCKLEN_T_=int in the Makefile.
> > > > 
> > > 
> > > 	Um, we will add a configuration test for this, in order
> > > to define _BSD_SOCKLEN_T when it is missing.
> > > 
> 
> 	Um, I have just looked at this and actually there is already
> some autoconf stuff. Could you confirm if, in the config.h of cc++,
> the symbol HAVE_SOCKLEN_T is undefined?
> 

It is commented out. From include/cc++/config.h

#define HAVE_INET_ATON 1
#define HAVE_INET_SOCKETS 1
#define HAVE_UNIX_SOCKETS 1
/* #undef HAVE_SOCKLEN_T */
/* #undef HAVE_SYS_LIBCSYS_H */
/* #undef HAVE_SYS_STREAM_H */
/* #undef HAVE_SYS_POLL_H */
/* #undef HAVE_POLL_H */




From MAILER-DAEMON Tue Jan 21 13:08:55 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18b2le-0003uX-00
	for mharc-bug-commoncpp@gnu.org; Tue, 21 Jan 2003 13:04:58 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18b2Ts-0006vj-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 12:46:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18b2GZ-00025z-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 12:32:52 -0500
Received: from mx1.magmacom.com ([206.191.0.217])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18b2Ej-0001Pu-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 12:30:57 -0500
Received: from mail4.magma.ca (mail4.magma.ca [206.191.0.222])
	by mx1.magmacom.com (Magma's Mail Server) with ESMTP id h0LHUu6b020338
	for <bug-commoncpp@gnu.org>; Tue, 21 Jan 2003 12:30:56 -0500 (EST)
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail4.magma.ca (Magma's Mail Server) with ESMTP id h0LHUuLm008724
	for <bug-commoncpp@gnu.org>; Tue, 21 Jan 2003 12:30:56 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: <bug-commoncpp@gnu.org>
Date: Tue, 21 Jan 2003 12:30:55 -0500
Message-ID: <000e01c2c172$da657570$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000F_01C2C148.F18F6D70"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: Process::spawn
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, 21 Jan 2003 18:04:56 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01C2C148.F18F6D70
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I was taking another look at Process::spawn and I think it might have
some implementation issues.
 
1) wait4 has an option value of 0. This prevents it from detecting that
the process on which it waits has been terminated by a signal such as
SIGSTOP. I noticed that spawn did not exit when I killed the spawned
process with 'kill'. Perhaps the option value should be WUNTRACED.
 
>From the man page on wait4 on Mac OS X:
"If the WUNTRACED option is set, children of the current process that
are stopped due to a 
SIGTTIN, SIGTTOU, SIGTSTP, or SIGSTOP signal also have their status
reported."
 
 
3) The vfork child calls execvp and then exit. It should probably check
for an exec error and call _exit().  From the man page:
 
Vfork() can normally be used just like fork.  It does not work, however,
     to return while running in the childs context from the procedure
that
     called vfork() since the eventual return from vfork() would then
return
     to a no longer existent stack frame.  Be careful, also, to call
_exit
     rather than exit if you can't execve, since exit will flush and
close
     standard I/O channels, and thereby mess up the parent processes
standard
     I/O data structures.  (Even with fork it is wrong to call exit
since
     buffered data would then be flushed twice.)

------=_NextPart_000_000F_01C2C148.F18F6D70
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D798030916-21012003><FONT face=3DArial size=3D2>I was =
taking another=20
look at Process::spawn and I think it might have some implementation=20
issues.</FONT></SPAN></DIV>
<DIV><SPAN class=3D798030916-21012003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D798030916-21012003><FONT face=3DArial size=3D2>1) =
wait4 has an=20
option value of 0. This prevents it from detecting that the process on =
which it=20
waits has been terminated by a signal such as SIGSTOP. I noticed that =
spawn did=20
not exit when I killed the spawned process with 'kill'. Perhaps the =
option value=20
should be WUNTRACED.</FONT></SPAN></DIV>
<DIV><SPAN class=3D798030916-21012003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D798030916-21012003><FONT face=3DArial size=3D2>From =
the man page on=20
wait4 on Mac OS X:</FONT></SPAN></DIV>
<DIV><SPAN class=3D798030916-21012003><FONT face=3DArial size=3D2>"If =
the WUNTRACED=20
option is set, children of&nbsp;the current process that are stopped due =
to a=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D798030916-21012003><FONT face=3DArial =
size=3D2>SIGTTIN, SIGTTOU,=20
SIGTSTP, </FONT></SPAN><SPAN class=3D798030916-21012003><FONT =
face=3DArial size=3D2>or=20
SIGSTOP signal also have their status reported."</FONT></SPAN><SPAN=20
class=3D798030916-21012003></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D798030916-21012003>3) The =
vfork child=20
calls execvp and then exit. It&nbsp;should probably check for an exec =
error and=20
call _exit(). &nbsp;From the man page:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D798030916-21012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D798030916-21012003>Vfork() can normally=20
be used just like fork.&nbsp; It does not work,=20
however,<BR>&nbsp;&nbsp;&nbsp;&nbsp; to return while running in the =
childs=20
context from the procedure that<BR>&nbsp;&nbsp;&nbsp;&nbsp; called =
vfork() since=20
the eventual return from vfork() would then =
return<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
to a no longer existent stack frame.&nbsp; Be careful, also, to call=20
_exit<BR>&nbsp;&nbsp;&nbsp;&nbsp; rather than exit if you can't execve, =
since=20
exit will flush and close<BR>&nbsp;&nbsp;&nbsp;&nbsp; standard I/O =
channels, and=20
thereby mess up the parent processes =
standard<BR>&nbsp;&nbsp;&nbsp;&nbsp; I/O=20
data structures.&nbsp; (Even with fork it is wrong to call exit=20
since<BR>&nbsp;&nbsp;&nbsp;&nbsp; buffered data would then be flushed=20
twice.)</SPAN></FONT></SPAN></DIV></BODY></HTML>

------=_NextPart_000_000F_01C2C148.F18F6D70--




From MAILER-DAEMON Tue Jan 21 14:32:06 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18b3vy-0003CT-00
	for mharc-bug-commoncpp@gnu.org; Tue, 21 Jan 2003 14:19:42 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18b3vt-000397-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 14:19:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18b3ue-0002qc-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 14:18:23 -0500
Received: from acate.com.br ([200.215.17.89] helo=cli004.brasmap)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18b3rt-0000zq-00
	for bug-commoncpp@gnu.org; Tue, 21 Jan 2003 14:15:29 -0500
Received: from brasmap.com.br (localhost.localdomain [127.0.0.1])
	by cli004.brasmap (Postfix) with SMTP id B71D85B4EB
	for <bug-commoncpp@gnu.org>; Tue, 21 Jan 2003 17:20:18 -0200 (BRST)
Date: Tue, 21 Jan 2003 17:20:18 -0200
From: Marcelo Dalmas <mad@brasmap.com.br>
To: ccxx <bug-commoncpp@gnu.org>
Message-Id: <20030121172018.3c689587.mad@brasmap.com.br>
Organization: BRASMAP Sistemas
X-Mailer: Sylpheed version 0.8.7 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="Multipart_Tue__21_Jan_2003_17:20:18_-0200_0821af30"
Subject: date.cpp 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: Tue, 21 Jan 2003 19:19:39 -0000

This is a multi-part message in MIME format.

--Multipart_Tue__21_Jan_2003_17:20:18_-0200_0821af30
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

I changed Date::setDate() Time::setTime() Datetime::setDatetime() to
recognize strings like:

Date: "mm/dd", "yy/mm/dd" and "yyyy/mm/dd", e.g. date("2003/01/21") or
date("01-21");
Time: "hh:mm" and "hh:mm:ss", e.g. time("14:00");
Datetime: "mm/dd hh:mm", "yy/mm/dd hh:mm", "yy/mm/dd hh:mm:ss" and
"yyyy/mm/dd hh:mm:ss" Datetime("01/21 16:00").

and throw exceptions, objects or nothing for invalid strings.

Regards,
-- 
Marcelo Dalmas
BRASMAP Sistemas
www.brasmap.com.br
Fone/Fax: (48) 333-2218 ramal 2114

Linux user #114373 http://counter.li.org/


--Multipart_Tue__21_Jan_2003_17:20:18_-0200_0821af30
Content-Type: application/octet-stream;
 name="date.patch"
Content-Disposition: attachment;
 filename="date.patch"
Content-Transfer-Encoding: base64

ZGlmZiAtcnUgLXhDVlMgY29tbW9uY3BwMi9zcmMvZGF0ZS5jcHAgY29tbW9uY3BwMi0xLjAuMC9z
cmMvZGF0ZS5jcHAKLS0tIGNvbW1vbmNwcDIvc3JjL2RhdGUuY3BwCTIwMDMtMDEtMTcgMTE6MTU6
NTkuMDAwMDAwMDAwIC0wMjAwCisrKyBjb21tb25jcHAyLTEuMC4wL3NyYy9kYXRlLmNwcAkyMDAz
LTAxLTIxIDE1OjMxOjQyLjAwMDAwMDAwMCAtMDIwMApAQCAtNDEsNiArNDEsOCBAQAogI2luY2x1
ZGUgPGNjKysvY29uZmlnLmg+CiAjaW5jbHVkZSA8Y2MrKy9leHBvcnQuaD4KICNpbmNsdWRlIDxj
YysrL251bWJlcnMuaD4KKyNpbmNsdWRlIDxjYysrL3RocmVhZC5oPgorI2luY2x1ZGUgPGNjKysv
ZXhjZXB0aW9uLmg+CiAjaW5jbHVkZSA8Y3N0ZGxpYj4KICNpbmNsdWRlIDxjc3RkaW8+CiAjaW5j
bHVkZSA8Y3RpbWU+CkBAIC05MCwzNSArOTIsNDYgQEAKIHsKIAl0aW1lX3Qgbm93OwogCXN0cnVj
dCB0bSAqZHQ7Ci0JaW50IHllYXI7Ci0JY29uc3QgY2hhciAqbWQ7CisJaW50IHllYXIgPSAwOwor
CWNvbnN0IGNoYXIgKm1kID0gc3RyOwogCiAJaWYoIXNpemUpCiAJCXNpemUgPSBzdHJsZW4oc3Ry
KTsKLQotCWlmKHNpemUgPCA1KQorLy8wMC8wMAorCWlmKHNpemUgPT0gNSkKIAl7CiAJCXRpbWUo
Jm5vdyk7CiAJCWR0ID0gbG9jYWx0aW1lKCZub3cpOwogCQl5ZWFyID0gZHQtPnRtX3llYXIgKyAx
OTAwOwogCQltZCA9IHN0cjsKIAl9Ci0JZWxzZSBpZihzaXplIDwgNykKKy8vMDAvMDAvMDAKKwll
bHNlIGlmKHNpemUgPT0gOCkKIAl7CiAJCXRpbWUoJm5vdyk7CiAJCWR0ID0gbG9jYWx0aW1lKCZu
b3cpOwotCQlOdW1iZXIgbnllYXIoKGNoYXIqKXN0ciwgMik7CisJCVpOdW1iZXIgbnllYXIoKGNo
YXIqKXN0ciwgMik7CiAJCXllYXIgPSAoKGR0LT50bV95ZWFyICsgMTkwMCkgLyAxMDApICogMTAw
ICsgbnllYXIoKTsKLQkJbWQgPSBzdHIgKyAyOworCQltZCA9IHN0ciArIDM7CiAJfQotCWVsc2UK
Ky8vMDAwMC8wMC8wMAorCWVsc2UgaWYoc2l6ZSA9PSAxMCkKIAl7Ci0JCU51bWJlciBueWVhcigo
Y2hhciopc3RyLCA0KTsKKwkJWk51bWJlciBueWVhcigoY2hhciopc3RyLCA0KTsKIAkJeWVhciA9
IG55ZWFyKCk7Ci0JCW1kID0gc3RyICsgNDsKKwkJbWQgPSBzdHIgKyA1OworCX0KKwllbHNlIGlm
KGdldEV4Y2VwdGlvbigpID09IFRocmVhZDo6dGhyb3dPYmplY3QpCisJeworCQl0aHJvdyB0aGlz
OwogCX0KLQlOdW1iZXIgbm1vbnRoKChjaGFyKiltZCwgMik7Ci0JTnVtYmVyIG5kYXkoKGNoYXIq
KW1kICsgMiwgMik7CisJZWxzZSBpZihnZXRFeGNlcHRpb24oKSA9PSBUaHJlYWQ6OnRocm93RXhj
ZXB0aW9uKQorCXsKKwkJdGhyb3cgRXhjZXB0aW9uKCJEYXRlOjpzZXREYXRlKCk6IEludmFsaWQg
ZGF0ZS4iKTsKKwl9CSAgICAJCisKKwlaTnVtYmVyIG5tb250aCgoY2hhciopbWQsIDIpOworCVpO
dW1iZXIgbmRheSgoY2hhciopbWQgKyAzLCAyKTsKIAl0b0p1bGlhbih5ZWFyLCBubW9udGgoKSwg
bmRheSgpKTsKIH0KIApAQCAtNDM0LDcgKzQ0Nyw3IEBACiAKIHZvaWQgVGltZTo6c2V0VGltZShj
aGFyICpzdHIsIHNpemVfdCBzaXplKQogewotCWludCBzZWNvbmRzOworCWludCBzZWNvbmRzID0g
MDA7CiAKIAlpZighc2l6ZSkKIAkJc2l6ZSA9IHN0cmxlbihzdHIpOwpAQCAtNDUwLDYgKzQ2Mywx
NSBAQAogCQlaTnVtYmVyIG5zZWNvbmQoc3RyICsgNiwgMik7CiAJCXNlY29uZHMgPSBuc2Vjb25k
KCk7CiAJfQorCWVsc2UgaWYoZ2V0RXhjZXB0aW9uKCkgPT0gVGhyZWFkOjp0aHJvd09iamVjdCkK
Kwl7CisJCXRocm93IHRoaXM7CisJfQorCWVsc2UgaWYoZ2V0RXhjZXB0aW9uKCkgPT0gVGhyZWFk
Ojp0aHJvd0V4Y2VwdGlvbikKKwl7CisJCXRocm93IEV4Y2VwdGlvbigiVGltZTo6c2V0VGltZSgp
OiBJbnZhbGlkIHRpbWUuIik7CisJfQkgICAgCQorCiAJWk51bWJlciBuaG91cihzdHIsIDIpOwog
CVpOdW1iZXIgbm1pbnV0ZShzdHIrMywgMik7CiAJdG9TZWNvbmRzKG5ob3VyKCksIG5taW51dGUo
KSwgc2Vjb25kcyk7CkBAIC02MjIsMzEgKzY0NCw0MiBAQAogCWlmICghc2l6ZSkKIAkJc2l6ZSA9
IHN0cmxlbihzdHIpOwogCi0JaWYgKHNpemUgPCA5KQorLy8gMDAvMDAgMDA6MDAKKwlpZiAoc2l6
ZSA9PSAgMTEpCiAJewotCQl0aW1lc3RyID0gc3RyICsgNDsKLQkJc2V0RGF0ZShzdHIsIDQpOwot
CQlzZXRUaW1lKHRpbWVzdHIsIDQpOworCQl0aW1lc3RyID0gc3RyICsgNjsKKwkJc2V0RGF0ZShz
dHIsIDUpOworCQlzZXRUaW1lKHRpbWVzdHIsIDUpOwogCX0KLQllbHNlIGlmIChzaXplIDwgMTMp
CisvLyAwMC8wMC8wMCAwMDowMAorCWVsc2UgaWYgKHNpemUgPT0gMTQpCiAJewotCQl0aW1lc3Ry
ID0gc3RyICsgODsKKwkJdGltZXN0ciA9IHN0ciArIDk7CiAJCXNldERhdGUoc3RyLCA4KTsKLQkJ
c2V0VGltZSh0aW1lc3RyLDQpOworCQlzZXRUaW1lKHRpbWVzdHIsNSk7CiAJfQotCWVsc2UgaWYg
KHNpemUgPCAxNSkKKy8vIDAwLzAwLzAwIDAwOjAwOjAwCisJZWxzZSBpZiAoc2l6ZSA9PSAxNykK
IAl7Ci0JCXRpbWVzdHIgPSBzdHIgKyA4OworCQl0aW1lc3RyID0gc3RyICsgOTsKIAkJc2V0RGF0
ZShzdHIsIDgpOwotCQlzZXRUaW1lKHRpbWVzdHIsNik7CisJCXNldFRpbWUodGltZXN0ciw4KTsK
IAl9Ci0JZWxzZQorLy8gMDAwMC8wMC8wMCAwMDowMDowMAorCWVsc2UgaWYgKHNpemUgPT0gMTkp
CiAJewogCQl0aW1lc3RyID0gc3RyICsgMTE7CiAJCXNldERhdGUoc3RyLCAxMCk7CiAJCXNldFRp
bWUodGltZXN0ciw4KTsKIAl9Ci0KKwllbHNlIGlmKGdldEV4Y2VwdGlvbigpID09IFRocmVhZDo6
dGhyb3dPYmplY3QpCisJeworCQl0aHJvdyB0aGlzOworCX0KKwllbHNlIGlmKGdldEV4Y2VwdGlv
bigpID09IFRocmVhZDo6dGhyb3dFeGNlcHRpb24pCisJeworCQl0aHJvdyBFeGNlcHRpb24oIlRp
bWU6OnNldFRpbWUoKTogSW52YWxpZCB0aW1lLiIpOworCX0JICAgIAkKIH0KIAogRGF0ZXRpbWU6
OkRhdGV0aW1lKGludCB5ZWFyLCB1bnNpZ25lZCBtb250aCwgdW5zaWduZWQgZGF5LAo=

--Multipart_Tue__21_Jan_2003_17:20:18_-0200_0821af30--



From MAILER-DAEMON Wed Jan 22 03:19:42 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bG6a-0002dp-00
	for mharc-bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:19:28 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bG6R-0002Lf-00
	for bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:19:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bG6O-0002E5-00
	for bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:19:17 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bG6G-00021N-00
	for bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:19:08 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18bG6t-0004jW-00; Wed, 22 Jan 2003 09:19:47 +0100
Date: Wed, 22 Jan 2003 09:19:47 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ian Gough <igough@gridiron-networks.com>
Message-ID: <20030122081946.GA7495@bulbasaur.rediris.es>
Mail-Followup-To: Ian Gough <igough@gridiron-networks.com>,
	'bug-commoncpp' <bug-commoncpp@gnu.org>
References: <20030121095921.GA1550@bulbasaur.rediris.es>
	<000701c2c15c$16876840$0c02a8c0@gridironnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000701c2c15c$16876840$0c02a8c0@gridironnetworks.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
Subject: Re: Building CC++ on Mac OS X
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: Wed, 22 Jan 2003 08:19:26 -0000


	Good, I have commited some modifications that should fix this
issue.

On Tue, Jan 21, 2003 at 09:47:57AM -0500, Ian Gough wrote:
> > 	Um, I have just looked at this and actually there is already
> > some autoconf stuff. Could you confirm if, in the config.h of cc++,
> > the symbol HAVE_SOCKLEN_T is undefined?
> > 
> 
> It is commented out. From include/cc++/config.h
> 
> #define HAVE_INET_ATON 1
> #define HAVE_INET_SOCKETS 1
> #define HAVE_UNIX_SOCKETS 1
> /* #undef HAVE_SOCKLEN_T */
> /* #undef HAVE_SYS_LIBCSYS_H */
> /* #undef HAVE_SYS_STREAM_H */
> /* #undef HAVE_SYS_POLL_H */
> /* #undef HAVE_POLL_H */
> 



From MAILER-DAEMON Wed Jan 22 03:23:46 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bGAV-0000WV-00
	for mharc-bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:23:31 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bGAQ-0000Gk-00
	for bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:23:26 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bGAF-0008Dz-00
	for bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:23:19 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bGAB-00081R-00
	for bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:23:12 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18bGAr-0004jr-00; Wed, 22 Jan 2003 09:23:53 +0100
Date: Wed, 22 Jan 2003 09:23:52 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Matthieu.Labour" <Matthieu.Labour@aasage.com>
Message-ID: <20030122082352.GB7495@bulbasaur.rediris.es>
Mail-Followup-To: "Matthieu.Labour" <Matthieu.Labour@aasage.com>,
	bug-commoncpp@gnu.org
References: <857B39B0D65BD311B14B0050DA0E107004033B41@sf-mail.aasage.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <857B39B0D65BD311B14B0050DA0E107004033B41@sf-mail.aasage.net>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: compiling for AIX
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: Wed, 22 Jan 2003 08:23:30 -0000


	The fixed code is currently in CVS (if you want to checkout
the stable version of cc++, you will have to specify the RELEASE1
tag). 1.0.8 is expected to be released (as a full release) shortly.

On Tue, Jan 21, 2003 at 12:33:36PM -0800, Matthieu.Labour wrote:
> Thank you for your answer. Even though I am using commoncpp2-1.0.7, I should
> download the patch 1.0.8 correct ? Is it a patch or only one file that has
> been updated ? Should I install cvs ?
> Thank you for your understanding
> Matt
> 
> 
> -----Original Message-----
> From: Federico Montesino Pouzols [mailto:fedemp@altern.org]
> Sent: Monday, January 20, 2003 1:01 AM
> To: Matthieu.Labour
> Cc: 'bug-commoncpp@gnu.org'
> Subject: Re: compiling for AIX
> 
> 
> 
> 	Hi,...
> 
> On Fri, Jan 17, 2003 at 10:33:53AM -0800, Matthieu.Labour wrote:
> > Hi, 
> > 
> > I try to compile commoncpp2-1.0.7 on AIX5.1. I am using the xlc_r compiler
> > version 6.
> > 
> > First, I had to add the xlc_r compiler in ./configure as followed
> otherwise
> > 'configure' would fail.
> > 
> > for ac_prog in $CCC xlc_r c++ g++ gcc CC cxx cc++ cl
> > 
> 
> 	You can make it in a somewhat more elegant manner using
> something like:
> 	
> 	$ CC=xlc_r CXX=xlc_r ./configure ...
> 
> 	Other configure options are explain in INSTALL and in
> configure --help.
> 
> 
> > When I type 'make' to compile the package I get the following error
> > 
> > xlc_r -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
> > -I/usr/local/include -D_GNU_SOURCE -D_THREAD_SAFE -I../include -c
> > semaphore.cpp  -DPIC -o .libs/semaphore.lo
> > "semaphore.cpp", line 76.38: 1540-0274 (S) The name lookup for
> "throwObject"
> > did not find a declaration.
> > "semaphore.cpp", line 79.43: 1540-0274 (S) The name lookup for
> > "throwException" did not find a declaration.
> > 
> > and I can't actually  find the trowObject declaration in the package. Am I
> > missing something here ?
> > 
> 
> 	Um, it is a bug that other compilers had ignored. These
> identifiers should be Thread::throwObject and Thread::throwException,
> respectively. I have fixed it in CVS for 1.0.8.
> 
> > Thank you for your help
> > 
> > Matthieu
> > 
> > _______________________________________________
> > 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 MAILER-DAEMON Wed Jan 22 03:37:19 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bGG4-0003ut-00
	for mharc-bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:29:16 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bGFh-0003jh-00
	for bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:28:53 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bGBY-0001ri-00
	for bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:24:38 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bGB6-0001Gp-00
	for bug-commoncpp@gnu.org; Wed, 22 Jan 2003 03:24:08 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18bGBk-0004k1-00; Wed, 22 Jan 2003 09:24:48 +0100
Date: Wed, 22 Jan 2003 09:24:48 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Marcelo Dalmas <mad@brasmap.com.br>
Message-ID: <20030122082448.GC7495@bulbasaur.rediris.es>
Mail-Followup-To: Marcelo Dalmas <mad@brasmap.com.br>,
	ccxx <bug-commoncpp@gnu.org>
References: <20030121172018.3c689587.mad@brasmap.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030121172018.3c689587.mad@brasmap.com.br>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: ccxx <bug-commoncpp@gnu.org>
Subject: Re: date.cpp 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: Wed, 22 Jan 2003 08:29:14 -0000


	It is committed in CVS.

On Tue, Jan 21, 2003 at 05:20:18PM -0200, Marcelo Dalmas wrote:
> Hi,
> 
> I changed Date::setDate() Time::setTime() Datetime::setDatetime() to
> recognize strings like:
> 
> Date: "mm/dd", "yy/mm/dd" and "yyyy/mm/dd", e.g. date("2003/01/21") or
> date("01-21");
> Time: "hh:mm" and "hh:mm:ss", e.g. time("14:00");
> Datetime: "mm/dd hh:mm", "yy/mm/dd hh:mm", "yy/mm/dd hh:mm:ss" and
> "yyyy/mm/dd hh:mm:ss" Datetime("01/21 16:00").
> 
> and throw exceptions, objects or nothing for invalid strings.
> 
> Regards,
> -- 
> Marcelo Dalmas
> BRASMAP Sistemas
> www.brasmap.com.br
> Fone/Fax: (48) 333-2218 ramal 2114
> 
> Linux user #114373 http://counter.li.org/
> 


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




From MAILER-DAEMON Sun Jan 26 10:47:21 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18cp03-00022H-00
	for mharc-bug-commoncpp@gnu.org; Sun, 26 Jan 2003 10:47:11 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18cozj-0001Cv-00
	for bug-commoncpp@gnu.org; Sun, 26 Jan 2003 10:46:51 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18cozM-0008Sc-00
	for bug-commoncpp@gnu.org; Sun, 26 Jan 2003 10:46: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 18cozA-0007qJ-00
	for bug-commoncpp@gnu.org; Sun, 26 Jan 2003 10:46:16 -0500
Received: from localhost.localdomain ([172.16.1.11])
	by home.sys (8.11.6/8.11.6) with ESMTP id h0QGMYP10942;
	Sun, 26 Jan 2003 11:22:34 -0500
Content-Type: text/plain;
  charset="us-ascii"
From: David Sugar <dyfet@ostel.com>
To: "'bug-commoncpp'" <bug-commoncpp@gnu.org>
Date: Sun, 26 Jan 2003 10:48:46 -0500
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301261048.46919.dyfet@ostel.com>
cc: bayonne-devel@lists.sourceforge.net
Subject: Common C++ 1.0.8 released
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, 26 Jan 2003 15:47:09 -0000

A new release of GNU Common C++, 1.0.8, was made available for general us=
e=20
this morning.  The missing 1.0.6 release of GNU ccAudio was also located =
over=20
the weekend...




From MAILER-DAEMON Mon Jan 27 11:07:43 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dBjt-00019X-00
	for mharc-bug-commoncpp@gnu.org; Mon, 27 Jan 2003 11:04:01 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dBjN-0000zt-00
	for bug-commoncpp@gnu.org; Mon, 27 Jan 2003 11:03:29 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dBfX-0007pQ-00
	for bug-commoncpp@gnu.org; Mon, 27 Jan 2003 10:59:32 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57]
	helo=home.localhost.localdomain)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18d9J7-0003bY-00
	for bug-commoncpp@gnu.org; Mon, 27 Jan 2003 08:28:13 -0500
Received: from localhost.localdomain ([172.16.1.11])h0RE4Jt27908;
	Mon, 27 Jan 2003 09:04:19 -0500
Content-Type: text/plain;
  charset="us-ascii"
From: David Sugar <dyfet@ostel.com>
To: bug-commoncpp@gnu.org
Date: Mon, 27 Jan 2003 08:30:47 -0500
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301270830.47367.dyfet@ostel.com>
cc: bayonne-devel@lists.sourceforge.net
Subject: New release of GNU ccRTP
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, 27 Jan 2003 16:03:59 -0000

A new release of GNU ccRTP has been made available today.  This release=20
(1.0pre2) incorporates many bug fixes and some changes in header file nam=
ing=20
for the Common C++ rtp stack.




From MAILER-DAEMON Mon Jan 27 11:28:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dC6w-0000b6-00
	for mharc-bug-commoncpp@gnu.org; Mon, 27 Jan 2003 11:27:50 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dC2m-0007Sp-00
	for bug-commoncpp@gnu.org; Mon, 27 Jan 2003 11:23:32 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dBwj-0005LU-00
	for bug-commoncpp@gnu.org; Mon, 27 Jan 2003 11:17:18 -0500
Received: from mx2.magma.ca ([206.191.0.250])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dBqa-0003IW-00
	for bug-commoncpp@gnu.org; Mon, 27 Jan 2003 11:10:56 -0500
Received: from mail3.magma.ca (mail3.magma.ca [206.191.0.221])
	by mx2.magma.ca (Magma Relay Server) with ESMTP id h0RGAl5C028645
	for <bug-commoncpp@gnu.org>; Mon, 27 Jan 2003 11:10:47 -0500
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail3.magma.ca (Magma's Mail Server) with ESMTP id h0RGAlRj027455
	for <bug-commoncpp@gnu.org>; Mon, 27 Jan 2003 11:10:47 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: "'bug-commoncpp'" <bug-commoncpp@gnu.org>
Date: Mon, 27 Jan 2003 11:10:46 -0500
Message-ID: <000a01c2c61e$a72518e0$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <20030122081946.GA7495@bulbasaur.rediris.es>
Subject: RE: Building CC++ on Mac OS X
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, 27 Jan 2003 16:27:47 -0000

Grabbed a new CVS snapshot this morning and tried to build after these
changes and I still get compilation failures:

g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
-I/usr/local/include -D_GNU_SOURCE -Wall -ansi -pedantic -I../include -c
thread.cpp -MT thread.lo -MD -MP -MF .deps/thread.TPlo  -fno-common
-DPIC -o .libs/thread.lo
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system
directory
thread.cpp: In constructor `ost::Thread::Thread(int, long unsigned
int)':
thread.cpp:536: `sched_getscheduler' undeclared (first use this
function)
thread.cpp:536: (Each undeclared identifier is reported only once for
each
   function it appears in.)
thread.cpp:554: `sched_getparam' undeclared (first use this function)
make[1]: *** [thread.lo] Error 1
make: *** [all-recursive] Error 1 

Checking if HAVE_SCHED_GETSCHEDULER is defined in one of the header
files shows that it is defined in config.h for some reason.

[/var/root/src/revgen/xGrid/ccxx 552] grep -r HAVE_SCHED *
acconfig.h:#undef HAVE_SCHED_GETSCHEDULER
acconfig.h:#ifdef HAVE_SCHED_H
config.log:#define HAVE_SCHED_H 1
config.log:#define HAVE_SCHED_GETSCHEDULER 1
config.status:${ac_dA}HAVE_SCHED_H${ac_dB}HAVE_SCHED_H${ac_dC}1${ac_dD}
config.status:${ac_dA}HAVE_SCHED_GETSCHEDULER${ac_dB}HAVE_SCHED_GETSCHED
ULER${ac_dC}1${ac_dD}
config.status:${ac_uA}HAVE_SCHED_H${ac_uB}HAVE_SCHED_H${ac_uC}1${ac_uD}
config.status:${ac_uA}HAVE_SCHED_GETSCHEDULER${ac_uB}HAVE_SCHED_GETSCHED
ULER${ac_uC}1${ac_uD}
configure:#define HAVE_SCHED_GETSCHEDULER 1
include/cc++/config.h:#define HAVE_SCHED_GETSCHEDULER 1
include/cc++/config.h:#define HAVE_SCHED_H 1
include/cc++/config.h:#ifdef HAVE_SCHED_H
include/cc++/config.tmp:#define HAVE_SCHED_GETSCHEDULER 1
include/cc++/config.tmp:#define HAVE_SCHED_H 1
include/cc++/config.tmp:#ifdef HAVE_SCHED_H
include/config.h:#define HAVE_SCHED_GETSCHEDULER 1
include/config.h:#define HAVE_SCHED_H 1
include/config.h:#ifdef HAVE_SCHED_H
include/config.h.in:#undef HAVE_SCHED_GETSCHEDULER
include/config.h.in:#undef HAVE_SCHED_H
include/config.h.in:#ifdef HAVE_SCHED_H
m4/ost_pthread.m4:              [AC_DEFINE(HAVE_SCHED_GETSCHEDULER)])
m4/ost_pthread.m4:dnl #undef HAVE_SCHED_GETSCHEDULER
m4/ost_pthread.m4:dnl #ifdef HAVE_SCHED_H
src/thread.cpp:#ifdef HAVE_SCHED_GETSCHEDULER
src/thread.cpp:#endif // ifdef HAVE_SCHED_GETSCHEDULER

But /usr/include/sched.h shows that there is no sched_getscheduler()
function.

#ifndef _SCHED_H_
#define _SCHED_H_

#include <pthread_impl.h>

/*
 * Scheduling paramters
 */
#ifndef __POSIX_LIB__
struct sched_param { int sched_priority;  char
opaque[__SCHED_PARAM_SIZE__]; };
#endif

extern int sched_yield(void);
extern int sched_get_priority_min(int);
extern int sched_get_priority_max(int);
#endif /* _SCHED_H_ */

I grepped for sched_getscheduler and turned up no hits, so I am not sure
why the autoconf system thinks that it exists.

I then defined __FreeBSD__ to get around this problem, but ran into
another compile problem.

g++ -DHAVE_CONFIG_H -I. -I. -I../include -D__FreeBSD__ -I../src
-DCCXX_EXPORT_LIBRARY -I/usr/local/include -D_GNU_SOURCE -Wall -ansi
-pedantic -I../include -c semaphore.cpp -MT semaphore.lo -MD -MP -MF
.deps/semaphore.TPlo  -fno-common -DPIC -o .libs/semaphore.lo
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system
directory
/usr/include/sys/sem.h: In destructor `virtual
ost::Semaphore::~Semaphore()':
/usr/include/sys/sem.h:242: too few arguments to function `int
ost::semctl(int,
   int, int, ost::semun)'
semaphore.cpp:100: at this point in file
/usr/include/sys/sem.h: In member function `int
ost::Semaphore::getValue()':
/usr/include/sys/sem.h:242: too few arguments to function `int
ost::semctl(int,
   int, int, ost::semun)'
semaphore.cpp:126: at this point in file
make: *** [semaphore.lo] Error 1

Mac OS X does not seem to have SYSV semaphores and an incomplete set of
POSIX semaphore functions. It does NOT have sem_init and sem_destroy,
but it does have sem_open and sem_close.

> -----Original Message-----
> From: Federico Montesino Pouzols 
> [mailto:fedemp@bulbasaur.rediris.es] On Behalf Of Federico 
> Montesino Pouzols
> Sent: Wednesday, January 22, 2003 3:20 AM
> To: Ian Gough
> Cc: 'bug-commoncpp'
> Subject: Re: Building CC++ on Mac OS X
> 
> 
> 
> 	Good, I have commited some modifications that should 
> fix this issue.
> 
> On Tue, Jan 21, 2003 at 09:47:57AM -0500, Ian Gough wrote:
> > > 	Um, I have just looked at this and actually there is 
> already some 
> > > autoconf stuff. Could you confirm if, in the config.h of 
> cc++, the 
> > > symbol HAVE_SOCKLEN_T is undefined?
> > > 
> > 
> > It is commented out. From include/cc++/config.h
> > 
> > #define HAVE_INET_ATON 1
> > #define HAVE_INET_SOCKETS 1
> > #define HAVE_UNIX_SOCKETS 1
> > /* #undef HAVE_SOCKLEN_T */
> > /* #undef HAVE_SYS_LIBCSYS_H */
> > /* #undef HAVE_SYS_STREAM_H */
> > /* #undef HAVE_SYS_POLL_H */
> > /* #undef HAVE_POLL_H */
> > 
> 




From MAILER-DAEMON Tue Jan 28 07:51:57 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dVDS-0003Xe-00
	for mharc-bug-commoncpp@gnu.org; Tue, 28 Jan 2003 07:51:50 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dVDE-00039l-00
	for bug-commoncpp@gnu.org; Tue, 28 Jan 2003 07:51:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dVD3-0002g5-00
	for bug-commoncpp@gnu.org; Tue, 28 Jan 2003 07:51:25 -0500
Received: from acate.com.br ([200.215.17.89] helo=cli004.brasmap)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dVA7-0008Sc-00
	for bug-commoncpp@gnu.org; Tue, 28 Jan 2003 07:48:24 -0500
Received: from brasmap.com.br (localhost.localdomain [127.0.0.1])
	by cli004.brasmap (Postfix) with SMTP id 394A25B4EA
	for <bug-commoncpp@gnu.org>; Tue, 28 Jan 2003 10:54:07 -0200 (BRST)
Date: Tue, 28 Jan 2003 10:54:06 -0200
From: Marcelo Dalmas <mad@brasmap.com.br>
To: ccxx <bug-commoncpp@gnu.org>
Message-Id: <20030128105406.5409a016.mad@brasmap.com.br>
Organization: BRASMAP Sistemas
X-Mailer: Sylpheed version 0.8.7 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="Multipart_Tue__28_Jan_2003_10:54:06_-0200_0821ade0"
Subject: time.cpp 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: Tue, 28 Jan 2003 12:51:47 -0000

This is a multi-part message in MIME format.

--Multipart_Tue__28_Jan_2003_10:54:06_-0200_0821ade0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

I'm sending a patch to resolve a overload problem in Time (test.cpp).
I think that Time should be equal Time. 
To do Time equal seconds:
	time t;
	t = time(0,0,10);

Also in patch, time format Time::fromSeconds() like "hh:mm:ss" and correct
message to Datetime::Datetime exception.

-- 
Marcelo Dalmas
BRASMAP Sistemas
www.brasmap.com.br
Fone/Fax: (48) 333-2218 ramal 2114

Linux user #114373 http://counter.li.org/


--Multipart_Tue__28_Jan_2003_10:54:06_-0200_0821ade0
Content-Type: application/octet-stream;
 name="time.patch"
Content-Disposition: attachment;
 filename="time.patch"
Content-Transfer-Encoding: base64

SW5kZXg6IGluY2x1ZGUvY2MrKy9udW1iZXJzLmgKPT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTogL2N2c3Jv
b3QvY29tbW9uY3BwL2NvbW1vbmNwcDIvaW5jbHVkZS9jYysrL251bWJlcnMuaCx2CnJldHJpZXZp
bmcgcmV2aXNpb24gMS4yLjIuNQpkaWZmIC11IC1yMS4yLjIuNSBudW1iZXJzLmgKLS0tIGluY2x1
ZGUvY2MrKy9udW1iZXJzLmgJOSBKYW4gMjAwMyAxMDo0MDo1NiAtMDAwMAkxLjIuMi41CisrKyBp
bmNsdWRlL2NjKysvbnVtYmVycy5oCTI4IEphbiAyMDAzIDEyOjEzOjQwIC0wMDAwCkBAIC0yNDEs
NyArMjQxLDYgQEAKIAkJe3JldHVybiBnZXRWYWx1ZSgpO307CiAKIAlzdGQ6OnN0cmluZyBvcGVy
YXRvcigpKCk7Ci0JVGltZSYgb3BlcmF0b3I9KGxvbmcgc2VjKTsKIAlUaW1lJiBvcGVyYXRvcisr
KCk7CiAJVGltZSYgb3BlcmF0b3ItLSgpOwogCVRpbWUmIG9wZXJhdG9yKz0oaW50IHZhbCk7Cklu
ZGV4OiBzcmMvZGF0ZS5jcHAKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTogL2N2c3Jvb3QvY29tbW9uY3Bw
L2NvbW1vbmNwcDIvc3JjL2RhdGUuY3BwLHYKcmV0cmlldmluZyByZXZpc2lvbiAxLjQuMi43CmRp
ZmYgLXUgLXIxLjQuMi43IGRhdGUuY3BwCi0tLSBzcmMvZGF0ZS5jcHAJMjIgSmFuIDIwMDMgMTA6
NDU6MDUgLTAwMDAJMS40LjIuNworKysgc3JjL2RhdGUuY3BwCTI4IEphbiAyMDAzIDEyOjEzOjQy
IC0wMDAwCkBAIC00ODcsMTIgKzQ4Nyw2IEBACiAJcmV0dXJuIHRpbWU7CiB9CiAKLVRpbWUgJiBU
aW1lOjpvcGVyYXRvcj0obG9uZyBzZWMpCi17Ci0Jc2Vjb25kcyA9IHNlYzsKLQlyZXR1cm4gKnRo
aXM7Ci19Ci0KIGxvbmcgVGltZTo6Z2V0VmFsdWUodm9pZCkKIHsKIAlyZXR1cm4gc2Vjb25kczsK
QEAgLTU3NSwxMyArNTY5LDE1IEBACiB2b2lkIFRpbWU6OmZyb21TZWNvbmRzKGNoYXIgKmJ1ZmZl
cikKIHsKIAlaTnVtYmVyIGhvdXIoYnVmZmVyLCAyKTsKLQlaTnVtYmVyIG1pbnV0ZShidWZmZXIg
KyAyLCAyKTsKLQlaTnVtYmVyIHNlY29uZChidWZmZXIgKyA0LCAyKTsKKwlaTnVtYmVyIG1pbnV0
ZShidWZmZXIgKyAzLCAyKTsKKwlaTnVtYmVyIHNlY29uZChidWZmZXIgKyA2LCAyKTsKIAogCWhv
dXIgPSBzZWNvbmRzIC8gMzYwMDsKIAltaW51dGUgPSAoc2Vjb25kcyAtICgzNjAwICogaG91cigp
KSkgLyA2MDsKIAlzZWNvbmQgPSBzZWNvbmRzIC0gKDM2MDAgKiBob3VyKCkpIC0gKDYwICogbWlu
dXRlKCkpOwotCWJ1ZmZlcls2XSA9ICdcMCc7CisJYnVmZmVyWzJdID0gJzonOworCWJ1ZmZlcls1
XSA9ICc6JzsKKwlidWZmZXJbOF0gPSAnXDAnOwogfQogCiBUaW1lIG9wZXJhdG9yKyhUaW1lICZ0
aW1lMSwgVGltZSAmdGltZTIpCkBAIC02NzgsNyArNjc0LDcgQEAKIAl9CiAJZWxzZSBpZihnZXRF
eGNlcHRpb24oKSA9PSBUaHJlYWQ6OnRocm93RXhjZXB0aW9uKQogCXsKLQkJdGhyb3cgRXhjZXB0
aW9uKCJUaW1lOjpzZXRUaW1lKCk6IEludmFsaWQgdGltZS4iKTsKKwkJdGhyb3cgRXhjZXB0aW9u
KCJEYXRldGltZTo6RGF0ZXRpbWUoKTogSW52YWxpZCB0aW1lLiIpOwogCX0JICAgIAkKIH0KIAo=

--Multipart_Tue__28_Jan_2003_10:54:06_-0200_0821ade0
Content-Type: application/octet-stream;
 name="test.cpp"
Content-Disposition: attachment;
 filename="test.cpp"
Content-Transfer-Encoding: base64

I2luY2x1ZGU8Y2MrKy9udW1iZXJzLmg+CiNpZmRlZiBDQ1hYX05BTUVTUEFDRVMKdXNpbmcgbmFt
ZXNwYWNlIHN0ZDsKdXNpbmcgbmFtZXNwYWNlIG9zdDsKI2VuZGlmCgpjbGFzcyBUZXN0CnsKIHBy
aXZhdGU6CglUaW1lIHRpbWU7CiBwdWJsaWM6CglUZXN0KGNoYXIqIHQpIDogdGltZSh0KSB7fTsK
CW9wZXJhdG9yIGxvbmcoKSB7IHJldHVybiA1O307CglvcGVyYXRvciBUaW1lKCkgeyByZXR1cm4g
dGltZTt9Owp9OwoKaW50IG1haW4oaW50IGFyZ2MsIGNoYXIgKiphcmd2KQp7CglUZXN0IHRlc3Qo
IjE2OjMwOjMwIik7CglUaW1lIHQ7CgkKCXQgID0gdGVzdDsKCglyZXR1cm4gMDsKfQoK

--Multipart_Tue__28_Jan_2003_10:54:06_-0200_0821ade0--



From MAILER-DAEMON Tue Jan 28 11:09:16 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dYFL-000568-00
	for mharc-bug-commoncpp@gnu.org; Tue, 28 Jan 2003 11:05:59 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dXWv-0002Ul-00
	for bug-commoncpp@gnu.org; Tue, 28 Jan 2003 10:20:05 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dXWf-000210-00
	for bug-commoncpp@gnu.org; Tue, 28 Jan 2003 10:19:54 -0500
Received: from pintail.mail.pas.earthlink.net ([207.217.120.122])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dXWX-0001Yz-00
	for bug-commoncpp@gnu.org; Tue, 28 Jan 2003 10:19:41 -0500
Received: from user-2ivf424.dialup.mindspring.com ([165.247.144.68]
	helo=chopin)
	by pintail.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 18dXWU-0000uV-00
	for bug-commoncpp@gnu.org; Tue, 28 Jan 2003 07:19:38 -0800
From: "Mike Suchoff" <mikes@in-tune.com>
To: <bug-commoncpp@gnu.org>
Date: Tue, 28 Jan 2003 10:27:12 -0500
Message-ID: <LLEGJHOMPFHINGBACKKLEEMGCHAA.mikes@in-tune.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailman-Approved-At: Tue, 28 Jan 2003 11:05:57 -0500
Subject: DateTime() constructor
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, 28 Jan 2003 15:20:25 -0000

In default constructor of DateTime
  DateTime::DateTime() : Date(), Time() {}

The separate calls to Date() and Time() will each make a different call to
operating system for current time.
If call to Date() returns 12/31/2002 23:59:59 and call to Time() returns
1/1/2003 0:0:0 then you end up with value that is off by 24 hours
(12/31/2002 0:0:0).






From MAILER-DAEMON Wed Jan 29 07:23:17 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dr0r-0000Iu-00
	for mharc-bug-commoncpp@gnu.org; Wed, 29 Jan 2003 07:08:17 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dqxV-00085D-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 07:04:49 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dqco-0005mx-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 06:43:28 -0500
Received: from acate.com.br ([200.215.17.89] helo=cli004.brasmap)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dqUI-0005Kd-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 06:34:39 -0500
Received: from brasmap.com.br (localhost.localdomain [127.0.0.1])
	by cli004.brasmap (Postfix) with SMTP
	id F0C935B4EA; Wed, 29 Jan 2003 09:40:29 -0200 (BRST)
Date: Wed, 29 Jan 2003 09:40:29 -0200
From: Marcelo Dalmas <mad@brasmap.com.br>
To: "Mike Suchoff" <mikes@in-tune.com>
Message-Id: <20030129094029.743bc346.mad@brasmap.com.br>
In-Reply-To: <LLEGJHOMPFHINGBACKKLEEMGCHAA.mikes@in-tune.com>
References: <LLEGJHOMPFHINGBACKKLEEMGCHAA.mikes@in-tune.com>
Organization: BRASMAP Sistemas
X-Mailer: Sylpheed version 0.8.7 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="Multipart_Wed__29_Jan_2003_09:40:29_-0200_08235b00"
cc: bug-commoncpp@gnu.org
Subject: Re: DateTime() constructor
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, 29 Jan 2003 12:08:16 -0000

This is a multi-part message in MIME format.

--Multipart_Wed__29_Jan_2003_09:40:29_-0200_08235b00
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

attached, a new constructor for Datetime.

On Tue, 28 Jan 2003 10:27:12 -0500
"Mike Suchoff" <mikes@in-tune.com> wrote:

> In default constructor of DateTime
>   DateTime::DateTime() : Date(), Time() {}
> 
> The separate calls to Date() and Time() will each make a different call to
> operating system for current time.
> If call to Date() returns 12/31/2002 23:59:59 and call to Time() returns
> 1/1/2003 0:0:0 then you end up with value that is off by 24 hours
> (12/31/2002 0:0:0).
> 
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 


-- 
Marcelo Dalmas
BRASMAP Sistemas
www.brasmap.com.br
Fone/Fax: (48) 333-2218 ramal 2114

Linux user #114373 http://counter.li.org/


--Multipart_Wed__29_Jan_2003_09:40:29_-0200_08235b00
Content-Type: application/octet-stream;
 name="date.patch"
Content-Disposition: attachment;
 filename="date.patch"
Content-Transfer-Encoding: base64

PyBkb2MvY29tbW9uY3BwMi5pbmZvCj8gd2luMzIvQ0NYWDIucmMKSW5kZXg6IGluY2x1ZGUvY2Mr
Ky9udW1iZXJzLmgKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTogL2N2c3Jvb3QvY29tbW9uY3BwL2NvbW1v
bmNwcDIvaW5jbHVkZS9jYysrL251bWJlcnMuaCx2CnJldHJpZXZpbmcgcmV2aXNpb24gMS4yLjIu
NQpkaWZmIC11IC1yMS4yLjIuNSBudW1iZXJzLmgKLS0tIGluY2x1ZGUvY2MrKy9udW1iZXJzLmgJ
OSBKYW4gMjAwMyAxMDo0MDo1NiAtMDAwMAkxLjIuMi41CisrKyBpbmNsdWRlL2NjKysvbnVtYmVy
cy5oCTI5IEphbiAyMDAzIDExOjAyOjQ0IC0wMDAwCkBAIC0yNDEsNyArMjQxLDYgQEAKIAkJe3Jl
dHVybiBnZXRWYWx1ZSgpO307CiAKIAlzdGQ6OnN0cmluZyBvcGVyYXRvcigpKCk7Ci0JVGltZSYg
b3BlcmF0b3I9KGxvbmcgc2VjKTsKIAlUaW1lJiBvcGVyYXRvcisrKCk7CiAJVGltZSYgb3BlcmF0
b3ItLSgpOwogCVRpbWUmIG9wZXJhdG9yKz0oaW50IHZhbCk7CkluZGV4OiBzcmMvZGF0ZS5jcHAK
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PQpSQ1MgZmlsZTogL2N2c3Jvb3QvY29tbW9uY3BwL2NvbW1vbmNwcDIvc3JjL2Rh
dGUuY3BwLHYKcmV0cmlldmluZyByZXZpc2lvbiAxLjQuMi43CmRpZmYgLXUgLXIxLjQuMi43IGRh
dGUuY3BwCi0tLSBzcmMvZGF0ZS5jcHAJMjIgSmFuIDIwMDMgMTA6NDU6MDUgLTAwMDAJMS40LjIu
NworKysgc3JjL2RhdGUuY3BwCTI5IEphbiAyMDAzIDExOjAyOjQ0IC0wMDAwCkBAIC0xMjksNyAr
MTI5LDEwIEBACiAJewogCQl0aHJvdyBFeGNlcHRpb24oIkRhdGU6OnNldERhdGUoKTogSW52YWxp
ZCBkYXRlLiIpOwogCX0JICAgIAkKLQorCWVsc2UgeworCQlyZXR1cm47CisJfQorCQogCVpOdW1i
ZXIgbm1vbnRoKChjaGFyKiltZCwgMik7CiAJWk51bWJlciBuZGF5KChjaGFyKiltZCArIDMsIDIp
OwogCXRvSnVsaWFuKHllYXIsIG5tb250aCgpLCBuZGF5KCkpOwpAQCAtMjIxLDE0ICsyMjQsMTQg
QEAKIAlyZXR1cm4gYXRvbChidWYpOwogfQogCi1EYXRlJglEYXRlOjpvcGVyYXRvcisrKCkKK0Rh
dGUmIERhdGU6Om9wZXJhdG9yKysoKQogewogCSsranVsaWFuOwogCXVwZGF0ZSgpOwogCXJldHVy
biAqdGhpczsKIH0KIAotRGF0ZSYJRGF0ZTo6b3BlcmF0b3ItLSgpCitEYXRlJiBEYXRlOjpvcGVy
YXRvci0tKCkKIHsKIAktLWp1bGlhbjsKIAl1cGRhdGUoKTsKQEAgLTI4MywxNCArMjg2LDE1IEBA
CiB7CiAJanVsaWFuID0gMHg3ZmZmZmZmZmw7CiAJCi0JaWYobW9udGggPCAxIHx8IG1vbnRoID4g
MTIpCi0JCXJldHVybjsKLQotCWlmKGRheSA8IDEgfHwgZGF5ID4gMzEpCQkKLQkJcmV0dXJuOwot
Ci0JaWYoeWVhciA9PSAwKQorCWlmKG1vbnRoIDwgMSB8fCBtb250aCA+IDEyIHx8IGRheSA8IDEg
fHwgZGF5ID4gMzEgfHwgeWVhciA9PSAwKSB7CisJCWlmKGdldEV4Y2VwdGlvbigpID09IFRocmVh
ZDo6dGhyb3dPYmplY3QpIHsKKwkJCXRocm93IHRoaXM7CisJCX0KKwkJZWxzZSBpZihnZXRFeGNl
cHRpb24oKSA9PSBUaHJlYWQ6OnRocm93RXhjZXB0aW9uKSB7CisJCQl0aHJvdyBFeGNlcHRpb24o
IkRhdGU6OnRvSnVsaWFuKCk6IEludmFsaWQgZGF0ZS4iKTsKKwkJfQogCQlyZXR1cm47CisJfQog
CiAJaWYoeWVhciA8IDApCiAJCXllYXItLTsKQEAgLTM2OCw3ICszNzIsNyBAQAogCXRpbWUoJm5v
dyk7CiAJZHQgPSBsb2NhbHRpbWUoJm5vdyk7CiAKLQl0b1NlY29uZHMoZHQtPnRtX2hvdXIgLCBk
dC0+dG1fbWluLCBkdC0+dG1fc2VjKTsKKwl0b1NlY29uZHMoZHQtPnRtX2hvdXIsIGR0LT50bV9t
aW4sIGR0LT50bV9zZWMpOwogfQogCiBUaW1lOjpUaW1lKHN0cnVjdCB0bSAqZHQpCkBAIC00NzEs
NiArNDc1LDkgQEAKIAl7CiAJCXRocm93IEV4Y2VwdGlvbigiVGltZTo6c2V0VGltZSgpOiBJbnZh
bGlkIHRpbWUuIik7CiAJfQkgICAgCQorCWVsc2UgeworCQlyZXR1cm47CisJfQogCiAJWk51bWJl
ciBuaG91cihzdHIsIDIpOwogCVpOdW1iZXIgbm1pbnV0ZShzdHIrMywgMik7CkBAIC00ODcsMTIg
KzQ5NCw2IEBACiAJcmV0dXJuIHRpbWU7CiB9CiAKLVRpbWUgJiBUaW1lOjpvcGVyYXRvcj0obG9u
ZyBzZWMpCi17Ci0Jc2Vjb25kcyA9IHNlYzsKLQlyZXR1cm4gKnRoaXM7Ci19Ci0KIGxvbmcgVGlt
ZTo6Z2V0VmFsdWUodm9pZCkKIHsKIAlyZXR1cm4gc2Vjb25kczsKQEAgLTY3OCw4ICs2NzksOCBA
QAogCX0KIAllbHNlIGlmKGdldEV4Y2VwdGlvbigpID09IFRocmVhZDo6dGhyb3dFeGNlcHRpb24p
CiAJewotCQl0aHJvdyBFeGNlcHRpb24oIlRpbWU6OnNldFRpbWUoKTogSW52YWxpZCB0aW1lLiIp
OwotCX0JICAgIAkKKwkJdGhyb3cgRXhjZXB0aW9uKCJEYXRldGltZTo6RGF0ZXRpbWUoKTogSW52
YWxpZCB0aW1lLiIpOworCX0KIH0KIAogRGF0ZXRpbWU6OkRhdGV0aW1lKGludCB5ZWFyLCB1bnNp
Z25lZCBtb250aCwgdW5zaWduZWQgZGF5LApAQCAtNjg3LDggKzY4OCwxNiBAQAogICBEYXRlKHll
YXIsIG1vbnRoLCBkYXkpLCBUaW1lKGhvdXIsIG1pbnV0ZSwgc2Vjb25kKQoge30KIAotRGF0ZXRp
bWU6OkRhdGV0aW1lKCkgOiBEYXRlKCksIFRpbWUoKQote30KK0RhdGV0aW1lOjpEYXRldGltZSgp
Cit7CisJdGltZV90IG5vdzsKKwlzdHJ1Y3QgdG0gKmR0OworCXRpbWUoJm5vdyk7CisJZHQgPSBs
b2NhbHRpbWUoJm5vdyk7CisKKwl0b1NlY29uZHMoZHQtPnRtX2hvdXIsIGR0LT50bV9taW4sIGR0
LT50bV9zZWMpOworCXRvSnVsaWFuKGR0LT50bV95ZWFyICsgMTkwMCwgZHQtPnRtX21vbiArIDEs
IGR0LT50bV9tZGF5KTsKK30KIAogYm9vbCBEYXRldGltZTo6aXNWYWxpZCh2b2lkKQogewpAQCAt
Nzc2LDcgKzc4NSw3IEBACiAKIAl0ID0gZ2V0RGF0ZXRpbWUoKTsKICAgICAgICAgdGJwID0gbG9j
YWx0aW1lKCZ0KTsKLQlsYXN0ID0gOjpzdHJmdGltZShidWZmZXIsIDY0LCBmb3JtYXQsIHRicCk7
CisJbGFzdCA9IHN0ZDo6c3RyZnRpbWUoYnVmZmVyLCA2NCwgZm9ybWF0LCB0YnApOwogCiAJYnVm
ZmVyW2xhc3RdID0gJ1wwJzsKIAlyZXR2YWwgPSBidWZmZXI7Cg==

--Multipart_Wed__29_Jan_2003_09:40:29_-0200_08235b00--



From MAILER-DAEMON Wed Jan 29 08:51:36 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dscq-0002kf-00
	for mharc-bug-commoncpp@gnu.org; Wed, 29 Jan 2003 08:51:36 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dscn-0002iA-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 08:51:33 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dsck-0002eI-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 08:51:33 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dsbx-0002Ad-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 08:50:42 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18dscq-0000Fy-00; Wed, 29 Jan 2003 14:51:36 +0100
Date: Wed, 29 Jan 2003 14:51:36 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Marcelo Dalmas <mad@brasmap.com.br>
Message-ID: <20030129135136.GA274@bulbasaur.rediris.es>
Mail-Followup-To: Marcelo Dalmas <mad@brasmap.com.br>,
	Mike Suchoff <mikes@in-tune.com>, bug-commoncpp@gnu.org
References: <LLEGJHOMPFHINGBACKKLEEMGCHAA.mikes@in-tune.com>
	<20030129094029.743bc346.mad@brasmap.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030129094029.743bc346.mad@brasmap.com.br>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
cc: Mike Suchoff <mikes@in-tune.com>
Subject: Re: DateTime() constructor
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: Wed, 29 Jan 2003 13:51:34 -0000


	Ok, it is in CVS. Marcelo, this patch seems to include your
previous one for Time, however I see a little difference as for the
fromSeconds method. Should we apply to CVS the changes to fromSeconds
that you included in the first patch?

On Wed, Jan 29, 2003 at 09:40:29AM -0200, Marcelo Dalmas wrote:
> Hi,
> 
> attached, a new constructor for Datetime.
> 
> On Tue, 28 Jan 2003 10:27:12 -0500
> "Mike Suchoff" <mikes@in-tune.com> wrote:
> 
> > In default constructor of DateTime
> >   DateTime::DateTime() : Date(), Time() {}
> > 
> > The separate calls to Date() and Time() will each make a different call to
> > operating system for current time.
> > If call to Date() returns 12/31/2002 23:59:59 and call to Time() returns
> > 1/1/2003 0:0:0 then you end up with value that is off by 24 hours
> > (12/31/2002 0:0:0).
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > 
> 
> 
> -- 
> Marcelo Dalmas
> BRASMAP Sistemas
> www.brasmap.com.br
> Fone/Fax: (48) 333-2218 ramal 2114
> 
> Linux user #114373 http://counter.li.org/
> 


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




From MAILER-DAEMON Wed Jan 29 11:02:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dufP-0004Uh-00
	for mharc-bug-commoncpp@gnu.org; Wed, 29 Jan 2003 11:02:23 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dufL-0004QI-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 11:02:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dufJ-0004P2-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 11:02:18 -0500
Received: from mx1.magmacom.com ([206.191.0.217])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18duer-0004B6-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 11:01:49 -0500
Received: from mail6.magma.ca (mail6 [206.191.0.248])
	by mx1.magmacom.com (Magma's Mail Server) with ESMTP id h0TG1lM5009066
	for <bug-commoncpp@gnu.org>; Wed, 29 Jan 2003 11:01:47 -0500 (EST)
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail6.magma.ca (Magma's Mail Server) with ESMTP id h0TG1csu026294
	for <bug-commoncpp@gnu.org>; Wed, 29 Jan 2003 11:01:39 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: <bug-commoncpp@gnu.org>
Date: Wed, 29 Jan 2003 11:01:38 -0500
Message-ID: <001f01c2c7af$b80d9fa0$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0020_01C2C785.CF3797A0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: TCPSession bug? 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: Wed, 29 Jan 2003 16:02:21 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0020_01C2C785.CF3797A0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0021_01C2C785.CF3797A0"


------=_NextPart_001_0021_01C2C785.CF3797A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I need some help determining if TCPSession is working correctly. The
included code was run on Windows. It is a slight modification of the
tcpthread.cpp demo. If you build it as-is, it creates a server socket
that accepts a connection on port 4096. When you connect to it with
telnet, it prints out banner messages and then echos back the decimal
value of any key you press in the telnet session, except for 'q' which
causes the connection to close. It is set up to (in theory) throw
exceptions in the session thread using 
 
 setException( Thread::throwException );
 
If you kill telnet while in the session, no exception gets thrown to
tell the server that the connection has closed. Also, the read of the
tcp stream returns the last thing sent on the socket from telnet and the
read thinks that it is getting a continuous stream of characters.
 
1) Should an exception be thrown on connection closure?
2) If not, how do you determine if the connection is closed or not?

Also, if you uncomment line 140 and comment out line 141 so that the
session thread is detached instead of started, you get no output on
telnet from the session. This doesn't seem particularly useful, as it
appears to be a socket set up with no ability to send data upon it.

------=_NextPart_001_0021_01C2C785.CF3797A0
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D763094715-29012003><FONT face=3DArial size=3D2>I need =
some help=20
determining if TCPSession is working correctly. The included code was =
run on=20
Windows. It is a slight modification of the tcpthread.cpp demo. If you =
build it=20
as-is, it creates a server socket that accepts a connection on port =
4096. When=20
you connect to it with telnet, it prints out banner messages and then =
echos back=20
the decimal value of any&nbsp;key you press in the telnet session, =
except for=20
'q' which causes the connection to close. It is set up to (in theory) =
throw=20
exceptions in the session thread using </FONT></SPAN></DIV>
<DIV><SPAN class=3D763094715-29012003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D763094715-29012003><FONT face=3DArial =
size=3D2>&nbsp;setException(=20
Thread::throwException );</FONT></SPAN></DIV>
<DIV><SPAN class=3D763094715-29012003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D763094715-29012003><FONT face=3DArial size=3D2>If you =
kill telnet=20
while in the session, no exception gets thrown to tell the server that =
the=20
connection has closed. Also, the read of the tcp stream returns the last =
thing=20
sent on the socket from telnet and the read thinks that it is getting a=20
continuous stream of characters.</FONT></SPAN></DIV>
<DIV><SPAN class=3D763094715-29012003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D763094715-29012003><FONT face=3DArial size=3D2>1) =
Should an=20
exception be thrown on connection closure?</FONT></SPAN></DIV>
<DIV><SPAN class=3D763094715-29012003><FONT face=3DArial size=3D2>2) If =
not, how do=20
you determine if the connection is closed or not?</FONT></DIV>
<DIV><BR><SPAN class=3D763094715-29012003><FONT face=3DArial =
size=3D2>Also, if you=20
uncomment line 140 and comment out line 141 so that the session thread =
is=20
detached instead of started, you get no output on telnet from the =
session. This=20
doesn't seem particularly useful, as it appears to be a socket set up =
with no=20
ability to send data upon it.</FONT></SPAN></DIV></SPAN></BODY></HTML>

------=_NextPart_001_0021_01C2C785.CF3797A0--

------=_NextPart_000_0020_01C2C785.CF3797A0
Content-Type: application/octet-stream;
	name="test.cpp"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="test.cpp"

// Copyright (C) 1999-2001 Open Source Telecom Corporation.
// =20
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation; either version 2 of the License, or
// (at your option) any later version.
//=20
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software=20
// Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, =
USA.
//=20
// As a special exception to the GNU General Public License, permission =
is=20
// granted for additional uses of the text contained in its release=20
// of APE.
//=20
// The exception is that, if you link the APE library with other files
// to produce an executable, this does not by itself cause the
// resulting executable to be covered by the GNU General Public License.
// Your use of that executable is in no way restricted on account of
// linking the APE library code into it.
//
// This exception does not however invalidate any other reasons why
// the executable file might be covered by the GNU General Public =
License.
//
// This exception applies only to the code released under the=20
// name APE.  If you copy code from other releases into a copy of
// APE, as the General Public License permits, the exception does
// not apply to the code that you add in this way.  To avoid misleading
// anyone as to the status of such modified files, you must delete
// this exception notice from them.
//=20
// If you write modifications of your own for APE, it is your choice
// whether to permit this exception to apply to your modifications.
// If you do not wish that, delete this exception notice.

#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)
{
	setException( Thread::throwException );

	InetAddress addr =3D getLocal();
	cout << "printing banner\n";
	*tcp() << "welcome to " << addr.getHostname() << " from socket " << so =
<< endl;
	mutex.enterMutex();
	*tcp() << "called from thread " << count << endl;
	mutex.leaveMutex();

	*tcp() << "Press a key, q to quit" << endl;
	tcp()->flush();

	char c;
	do
	{
		*tcp() >> c;
		cout << "Received " << (int)c << endl;
	} while ( c !=3D 'q' );

	cout << "ending session" << endl;
	*tcp() << "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 "127.0.0.1";
	cout << "binding for: " << addr.getHostname() << ":" << 4096 << endl;

	try
	{
		myTCPSocket server(addr);

		if ( server.isPendingConnection() )
		{
			cout << "before create" << endl;
			tcp =3D new myTCPSession(server);
			cout << "after create" << endl;
//			tcp->detach();
			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;
	}
	catch( ... )
	{
		cerr << "Got an error" << endl;
	}

	cout << "hit a key" << endl;
	char c;
	cin >> c;
	return 0;
}


------=_NextPart_000_0020_01C2C785.CF3797A0--




From MAILER-DAEMON Wed Jan 29 12:26:13 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dvwO-0000if-00
	for mharc-bug-commoncpp@gnu.org; Wed, 29 Jan 2003 12:24:00 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dvvy-0000H9-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 12:23:34 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dvvn-0008Vh-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 12:23:24 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dvvl-00081B-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 12:23:21 -0500
Received: from acate.com.br ([200.215.17.89] helo=cli004.brasmap)
	by gnudist.gnu.org with esmtp (Exim 4.10.13)
	id 18dvhv-0004Cx-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 12:09:03 -0500
Received: from brasmap.com.br (localhost.localdomain [127.0.0.1])
	by cli004.brasmap (Postfix) with SMTP
	id 302865B4EA; Wed, 29 Jan 2003 15:14:23 -0200 (BRST)
Date: Wed, 29 Jan 2003 15:14:22 -0200
From: Marcelo Dalmas <mad@brasmap.com.br>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-Id: <20030129151422.39db57bc.mad@brasmap.com.br>
In-Reply-To: <20030129135136.GA274@bulbasaur.rediris.es>
References: <LLEGJHOMPFHINGBACKKLEEMGCHAA.mikes@in-tune.com>
	<20030129094029.743bc346.mad@brasmap.com.br>
	<20030129135136.GA274@bulbasaur.rediris.es>
Organization: BRASMAP Sistemas
X-Mailer: Sylpheed version 0.8.7 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
cc: bug-commoncpp@gnu.org
cc: mikes@in-tune.com
Subject: Re: DateTime() constructor
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, 29 Jan 2003 17:23:58 -0000

The patch for fromSeconds method should't be apply because methods like
getHour,
getMinute, etc., use fromSeconds.

What do you think about add inserter, extractor and maipulators to Date,
Time and Datetime? Something like:

cout << width(5) << time << endl;  // 14:00
cout << width(8) << time << endl;  // 14:00:00
cout << pm << time << endl; // 2:00pm




On Wed, 29 Jan 2003 14:51:36 +0100
Federico Montesino Pouzols <fedemp@altern.org> wrote:

> 
> 	Ok, it is in CVS. Marcelo, this patch seems to include your
> previous one for Time, however I see a little difference as for the
> fromSeconds method. Should we apply to CVS the changes to fromSeconds
> that you included in the first patch?
> 
> On Wed, Jan 29, 2003 at 09:40:29AM -0200, Marcelo Dalmas wrote:
> > Hi,
> > 
> > attached, a new constructor for Datetime.
> > 
> > On Tue, 28 Jan 2003 10:27:12 -0500
> > "Mike Suchoff" <mikes@in-tune.com> wrote:
> > 
> > > In default constructor of DateTime
> > >   DateTime::DateTime() : Date(), Time() {}
> > > 
> > > The separate calls to Date() and Time() will each make a different
> > > call to operating system for current time.
> > > If call to Date() returns 12/31/2002 23:59:59 and call to Time()
> > > returns 1/1/2003 0:0:0 then you end up with value that is off by 24
> > > hours(12/31/2002 0:0:0).
> > > 
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Bug-commoncpp mailing list
> > > Bug-commoncpp@gnu.org
> > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > > 
> > 
> > 
> > -- 
> > Marcelo Dalmas
> > BRASMAP Sistemas
> > www.brasmap.com.br
> > Fone/Fax: (48) 333-2218 ramal 2114
> > 
> > Linux user #114373 http://counter.li.org/
> > 
> 
> 
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 
> 


-- 
Marcelo Dalmas
BRASMAP Sistemas
www.brasmap.com.br
Fone/Fax: (48) 333-2218 ramal 2114

Linux user #114373 http://counter.li.org/




From MAILER-DAEMON Wed Jan 29 12:41:32 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dwCD-0004iv-00
	for mharc-bug-commoncpp@gnu.org; Wed, 29 Jan 2003 12:40:21 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dwC5-0004XL-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 12:40:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dw9H-00034w-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 12:37:26 -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 18dw9A-0002k2-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 12:37:12 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H9H00GY6KXX22@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Wed, 29 Jan 2003 09:37:10 -0800 (PST)
Date: Wed, 29 Jan 2003 09:37:09 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20030122082448.GC7495@bulbasaur.rediris.es>
To: Federico Montesino Pouzols <fedemp@altern.org>,
 Marcelo Dalmas <mad@brasmap.com.br>
Message-id: <NBBBJJODBJBNJFNIDDCNAEHADEAA.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
cc: ccxx <bug-commoncpp@gnu.org>
Subject: RE: date.cpp 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: Wed, 29 Jan 2003 17:40:19 -0000

Hmmm...

setDate() now recognizes formats with /'s *BUT* it no longer recognizes the
formats that it used to, for example '20030129'.  This breaks backward
compatibility (and my test date test suites).

,Chad

> -----Original Message-----
> From: bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org
> [mailto:bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org]On Behalf Of
> Federico Montesino Pouzols
> Sent: Wednesday, January 22, 2003 12:25 AM
> To: Marcelo Dalmas
> Cc: ccxx
> Subject: Re: date.cpp patch
>
>
>
> 	It is committed in CVS.
>
> On Tue, Jan 21, 2003 at 05:20:18PM -0200, Marcelo Dalmas wrote:
> > Hi,
> >
> > I changed Date::setDate() Time::setTime() Datetime::setDatetime() to
> > recognize strings like:
> >
> > Date: "mm/dd", "yy/mm/dd" and "yyyy/mm/dd", e.g. date("2003/01/21") or
> > date("01-21");
> > Time: "hh:mm" and "hh:mm:ss", e.g. time("14:00");
> > Datetime: "mm/dd hh:mm", "yy/mm/dd hh:mm", "yy/mm/dd hh:mm:ss" and
> > "yyyy/mm/dd hh:mm:ss" Datetime("01/21 16:00").
> >
> > and throw exceptions, objects or nothing for invalid strings.
> >
> > Regards,
> > --
> > Marcelo Dalmas
> > BRASMAP Sistemas
> > www.brasmap.com.br
> > Fone/Fax: (48) 333-2218 ramal 2114
> >
> > Linux user #114373 http://counter.li.org/
> >
>
>
> > _______________________________________________
> > 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 MAILER-DAEMON Wed Jan 29 14:05:19 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dxVS-0001aQ-00
	for mharc-bug-commoncpp@gnu.org; Wed, 29 Jan 2003 14:04:18 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dxT5-0000XA-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 14:01:51 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dxOk-0007Jc-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 13:57:23 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dxNH-0006vi-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 13:55:51 -0500
Received: from agassiz
	(IDENT:RAKL1ZqIZLnGQ/61iJJpO/rrXOPWqSc/@localhost.localdomain [127.0.0.1])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id h0TItnq2015881;
	Wed, 29 Jan 2003 12:55:50 -0600
Date: Wed, 29 Jan 2003 12:56:47 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
To: Ian Gough <igough@gridiron-networks.com>
In-Reply-To: <001f01c2c7af$b80d9fa0$0c02a8c0@gridironnetworks.com>
Message-ID: <Pine.GSO.4.10.10301291255170.8922-100000@agassiz.cs.und.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bug-commoncpp@gnu.org
Subject: Re: TCPSession bug? 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: Wed, 29 Jan 2003 19:04:16 -0000


I use 'tcpstream' and have found that the '!' (not) operator works well
to determine if it is connected:
  tcpstream stream;
  bool disconnected = !stream;
  bool connected = !!stream;

Ari Johnson

On Wed, 29 Jan 2003, Ian Gough wrote:

> I need some help determining if TCPSession is working correctly. The
> included code was run on Windows. It is a slight modification of the
> tcpthread.cpp demo. If you build it as-is, it creates a server socket
> that accepts a connection on port 4096. When you connect to it with
> telnet, it prints out banner messages and then echos back the decimal
> value of any key you press in the telnet session, except for 'q' which
> causes the connection to close. It is set up to (in theory) throw
> exceptions in the session thread using 
>  
>  setException( Thread::throwException );
>  
> If you kill telnet while in the session, no exception gets thrown to
> tell the server that the connection has closed. Also, the read of the
> tcp stream returns the last thing sent on the socket from telnet and the
> read thinks that it is getting a continuous stream of characters.
>  
> 1) Should an exception be thrown on connection closure?
> 2) If not, how do you determine if the connection is closed or not?
> 
> Also, if you uncomment line 140 and comment out line 141 so that the
> session thread is detached instead of started, you get no output on
> telnet from the session. This doesn't seem particularly useful, as it
> appears to be a socket set up with no ability to send data upon it.
> 




From MAILER-DAEMON Wed Jan 29 15:49:16 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dz8z-0001wy-00
	for mharc-bug-commoncpp@gnu.org; Wed, 29 Jan 2003 15:49:13 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dz8P-00015p-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 15:48:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dz8E-0000zO-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 15:48:27 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dz7r-0000WT-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 15:48:03 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18dz8u-0000KE-00; Wed, 29 Jan 2003 21:49:08 +0100
Date: Wed, 29 Jan 2003 21:49:07 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Marcelo Dalmas <mad@brasmap.com.br>
Message-ID: <20030129204907.GA1211@bulbasaur.rediris.es>
Mail-Followup-To: Marcelo Dalmas <mad@brasmap.com.br>,
	bug-commoncpp@gnu.org, mikes@in-tune.com
References: <LLEGJHOMPFHINGBACKKLEEMGCHAA.mikes@in-tune.com>
	<20030129094029.743bc346.mad@brasmap.com.br>
	<20030129135136.GA274@bulbasaur.rediris.es>
	<20030129151422.39db57bc.mad@brasmap.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030129151422.39db57bc.mad@brasmap.com.br>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
cc: mikes@in-tune.com
Subject: Re: DateTime() constructor
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: Wed, 29 Jan 2003 20:49:11 -0000


	Um, it would be a very nice feature.

On Wed, Jan 29, 2003 at 03:14:22PM -0200, Marcelo Dalmas wrote:
> The patch for fromSeconds method should't be apply because methods like
> getHour,
> getMinute, etc., use fromSeconds.
> 
> What do you think about add inserter, extractor and maipulators to Date,
> Time and Datetime? Something like:
> 
> cout << width(5) << time << endl;  // 14:00
> cout << width(8) << time << endl;  // 14:00:00
> cout << pm << time << endl; // 2:00pm
> 



From MAILER-DAEMON Wed Jan 29 16:20:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dzbo-0007mF-00
	for mharc-bug-commoncpp@gnu.org; Wed, 29 Jan 2003 16:19:00 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dzaw-0007Wy-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 16:18:06 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dzaN-0006kH-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 16:17:32 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dzZT-00062y-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 16:16:35 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18dzaX-0000Kw-00; Wed, 29 Jan 2003 22:17:41 +0100
Date: Wed, 29 Jan 2003 22:17:40 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ian Gough <igough@gridiron-networks.com>
Message-ID: <20030129211740.GB1211@bulbasaur.rediris.es>
Mail-Followup-To: Ian Gough <igough@gridiron-networks.com>,
	'bug-commoncpp' <bug-commoncpp@gnu.org>
References: <20030122081946.GA7495@bulbasaur.rediris.es>
	<000a01c2c61e$a72518e0$0c02a8c0@gridironnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000a01c2c61e$a72518e0$0c02a8c0@gridironnetworks.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
Subject: Re: Building CC++ on Mac OS X
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: Wed, 29 Jan 2003 21:18:59 -0000


	Yes, the semaphore stuff is still pending, I expect to fix it
soon. As for the sched_getscheduler issue, it is weird that it is
detected, since the test is like this:

        AC_TRY_COMPILE(
                [#include <sched.h>],
                [
                int policy;
                policy = sched_getscheduler(0);
                ],
                [AC_DEFINE(HAVE_SCHED_GETSCHEDULER)])

	Could you try to compile on your system a simple C program
like the one above? It should not compile, but it seems that autoconf
is able to succesfully compile it.

On Mon, Jan 27, 2003 at 11:10:46AM -0500, Ian Gough wrote:
> Grabbed a new CVS snapshot this morning and tried to build after these
> changes and I still get compilation failures:
> 
> g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
> -I/usr/local/include -D_GNU_SOURCE -Wall -ansi -pedantic -I../include -c
> thread.cpp -MT thread.lo -MD -MP -MF .deps/thread.TPlo  -fno-common
> -DPIC -o .libs/thread.lo
> cc1plus: warning: changing search order for system directory
> "/usr/local/include"
> cc1plus: warning:   as it has already been specified as a non-system
> directory
> thread.cpp: In constructor `ost::Thread::Thread(int, long unsigned
> int)':
> thread.cpp:536: `sched_getscheduler' undeclared (first use this
> function)
> thread.cpp:536: (Each undeclared identifier is reported only once for
> each
>    function it appears in.)
> thread.cpp:554: `sched_getparam' undeclared (first use this function)
> make[1]: *** [thread.lo] Error 1
> make: *** [all-recursive] Error 1 
> 
> Checking if HAVE_SCHED_GETSCHEDULER is defined in one of the header
> files shows that it is defined in config.h for some reason.
> 
> [/var/root/src/revgen/xGrid/ccxx 552] grep -r HAVE_SCHED *
> acconfig.h:#undef HAVE_SCHED_GETSCHEDULER
> acconfig.h:#ifdef HAVE_SCHED_H
> config.log:#define HAVE_SCHED_H 1
> config.log:#define HAVE_SCHED_GETSCHEDULER 1
> config.status:${ac_dA}HAVE_SCHED_H${ac_dB}HAVE_SCHED_H${ac_dC}1${ac_dD}
> config.status:${ac_dA}HAVE_SCHED_GETSCHEDULER${ac_dB}HAVE_SCHED_GETSCHED
> ULER${ac_dC}1${ac_dD}
> config.status:${ac_uA}HAVE_SCHED_H${ac_uB}HAVE_SCHED_H${ac_uC}1${ac_uD}
> config.status:${ac_uA}HAVE_SCHED_GETSCHEDULER${ac_uB}HAVE_SCHED_GETSCHED
> ULER${ac_uC}1${ac_uD}
> configure:#define HAVE_SCHED_GETSCHEDULER 1
> include/cc++/config.h:#define HAVE_SCHED_GETSCHEDULER 1
> include/cc++/config.h:#define HAVE_SCHED_H 1
> include/cc++/config.h:#ifdef HAVE_SCHED_H
> include/cc++/config.tmp:#define HAVE_SCHED_GETSCHEDULER 1
> include/cc++/config.tmp:#define HAVE_SCHED_H 1
> include/cc++/config.tmp:#ifdef HAVE_SCHED_H
> include/config.h:#define HAVE_SCHED_GETSCHEDULER 1
> include/config.h:#define HAVE_SCHED_H 1
> include/config.h:#ifdef HAVE_SCHED_H
> include/config.h.in:#undef HAVE_SCHED_GETSCHEDULER
> include/config.h.in:#undef HAVE_SCHED_H
> include/config.h.in:#ifdef HAVE_SCHED_H
> m4/ost_pthread.m4:              [AC_DEFINE(HAVE_SCHED_GETSCHEDULER)])
> m4/ost_pthread.m4:dnl #undef HAVE_SCHED_GETSCHEDULER
> m4/ost_pthread.m4:dnl #ifdef HAVE_SCHED_H
> src/thread.cpp:#ifdef HAVE_SCHED_GETSCHEDULER
> src/thread.cpp:#endif // ifdef HAVE_SCHED_GETSCHEDULER
> 
> But /usr/include/sched.h shows that there is no sched_getscheduler()
> function.
> 
> #ifndef _SCHED_H_
> #define _SCHED_H_
> 
> #include <pthread_impl.h>
> 
> /*
>  * Scheduling paramters
>  */
> #ifndef __POSIX_LIB__
> struct sched_param { int sched_priority;  char
> opaque[__SCHED_PARAM_SIZE__]; };
> #endif
> 
> extern int sched_yield(void);
> extern int sched_get_priority_min(int);
> extern int sched_get_priority_max(int);
> #endif /* _SCHED_H_ */
> 
> I grepped for sched_getscheduler and turned up no hits, so I am not sure
> why the autoconf system thinks that it exists.
> 
> I then defined __FreeBSD__ to get around this problem, but ran into
> another compile problem.
> 
> g++ -DHAVE_CONFIG_H -I. -I. -I../include -D__FreeBSD__ -I../src
> -DCCXX_EXPORT_LIBRARY -I/usr/local/include -D_GNU_SOURCE -Wall -ansi
> -pedantic -I../include -c semaphore.cpp -MT semaphore.lo -MD -MP -MF
> .deps/semaphore.TPlo  -fno-common -DPIC -o .libs/semaphore.lo
> cc1plus: warning: changing search order for system directory
> "/usr/local/include"
> cc1plus: warning:   as it has already been specified as a non-system
> directory
> /usr/include/sys/sem.h: In destructor `virtual
> ost::Semaphore::~Semaphore()':
> /usr/include/sys/sem.h:242: too few arguments to function `int
> ost::semctl(int,
>    int, int, ost::semun)'
> semaphore.cpp:100: at this point in file
> /usr/include/sys/sem.h: In member function `int
> ost::Semaphore::getValue()':
> /usr/include/sys/sem.h:242: too few arguments to function `int
> ost::semctl(int,
>    int, int, ost::semun)'
> semaphore.cpp:126: at this point in file
> make: *** [semaphore.lo] Error 1
> 
> Mac OS X does not seem to have SYSV semaphores and an incomplete set of
> POSIX semaphore functions. It does NOT have sem_init and sem_destroy,
> but it does have sem_open and sem_close.
> 
> > -----Original Message-----
> > From: Federico Montesino Pouzols 
> > [mailto:fedemp@bulbasaur.rediris.es] On Behalf Of Federico 
> > Montesino Pouzols
> > Sent: Wednesday, January 22, 2003 3:20 AM
> > To: Ian Gough
> > Cc: 'bug-commoncpp'
> > Subject: Re: Building CC++ on Mac OS X
> > 
> > 
> > 
> > 	Good, I have commited some modifications that should 
> > fix this issue.
> > 
> > On Tue, Jan 21, 2003 at 09:47:57AM -0500, Ian Gough wrote:
> > > > 	Um, I have just looked at this and actually there is 
> > already some 
> > > > autoconf stuff. Could you confirm if, in the config.h of 
> > cc++, the 
> > > > symbol HAVE_SOCKLEN_T is undefined?
> > > > 
> > > 
> > > It is commented out. From include/cc++/config.h
> > > 
> > > #define HAVE_INET_ATON 1
> > > #define HAVE_INET_SOCKETS 1
> > > #define HAVE_UNIX_SOCKETS 1
> > > /* #undef HAVE_SOCKLEN_T */
> > > /* #undef HAVE_SYS_LIBCSYS_H */
> > > /* #undef HAVE_SYS_STREAM_H */
> > > /* #undef HAVE_SYS_POLL_H */
> > > /* #undef HAVE_POLL_H */
> > > 
> > 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Wed Jan 29 20:11:58 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18e3FC-0005hs-00
	for mharc-bug-commoncpp@gnu.org; Wed, 29 Jan 2003 20:11:54 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18e3F7-0005Q9-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 20:11:49 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18e3F2-0005Ei-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 20:11:45 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18e3Ew-00054O-00
	for bug-commoncpp@gnu.org; Wed, 29 Jan 2003 20:11:38 -0500
Received: from agassiz
	(IDENT:hSD7jnfBR5hkhKb95pNEVC2bc6DrZzfJ@localhost.localdomain [127.0.0.1])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id h0U1Bb8F024604
	for <bug-commoncpp@gnu.org>; Wed, 29 Jan 2003 19:11:37 -0600
Date: Wed, 29 Jan 2003 19:12:35 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
To: bug-commoncpp@gnu.org
Message-ID: <Pine.GSO.4.10.10301291908340.13023-100000@agassiz.cs.und.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: URLStream Example
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, 30 Jan 2003 01:11:52 -0000


Does anyone have a (preferably working) example of URLStream in use?  I
need to use it to download a file via either HTTP or FTP (haven't decided
which I'm using just yet) and then I'll be dlopen()ing that file.
However, the documentation for URLStream is entirely incomplete, and if
someone has samples of code that properly uses it then it'd save me a
great deal of decoding.

Ari Johnson





From MAILER-DAEMON Thu Jan 30 01:41:50 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18e8OT-0000U2-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 01:41:49 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18e8OQ-0000QD-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 01:41:46 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18e8ON-0000NP-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 01:41:45 -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 18e8OL-0000Hw-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 01:41:42 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H9I006SZL9BA0@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Wed, 29 Jan 2003 22:41:36 -0800 (PST)
Date: Wed, 29 Jan 2003 22:41:34 -0800
From: Chad Yates <cyates@uidaho.edu>
To: bug-commoncpp <bug-commoncpp@gnu.org>
Message-id: <NBBBJJODBJBNJFNIDDCNKEHJDEAA.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: multipart/mixed; boundary="Boundary_(ID_OItGkMNEphWhF9WGQO+MBQ)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
cc: albert@dogbert.sdsl.sun.ac.za
Subject: common C++ test suite
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, 30 Jan 2003 06:41:47 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_OItGkMNEphWhF9WGQO+MBQ)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Common C++ community,

As some of you may remember, I wrote some test suites in cppunit last month
and I would like to submit them as the beginnings of a common C++ test suite
as we had discussed then.  however it has a couple of issues I am hoping a
more experienced common c++ developer or maintainer can help with, as I am a
gnu autoconfig/automake newbie, I'll admit it. :)  also since I typically
develop using m$ visual studio 6.0 I'm not that proficient with
developing/debugging on the linux environment.

My date classes have some tests that are failing now with the recent patches
submitted that add the new YYYY/MM/DD style formats instead of the YYYYMMDD
formats.  whether the interface is changing or whether the tests need to be
updated to the new format needs to be determined.

My persistence tests (pretty extensive), work fine under windows, but throw
exceptions under linux.  I don't yet know why, and since I haven't come to
grips with a linux debugger yet (I've been babied by VC++'s gui debugger), I
can't dig into the reason yet.  I have another test case under windows, but
am not going to add it at this time as it has some linux compilation issues.

There are generalized test classes for the digest tests, however I could
never seem to get decent results out of the SHA digests on windows, they may
work fine under linux, though the testcase registration macros are commented
out right now.

There are also tests for the urlstring file including base64 encode decode.

I have attached a zip file containing a zipped directory called ccxx_tests
designed to be uncompressed under the commoncpp2 main directory.  eventually
I would hope the contents would live in tests instead, and all the existing
tests changed to components of the cppunit test suites, or something
similar.

I have also attached a diff of the changes I made to the configure.in and
Makefile.am to get it to build for me on my linux machine, however, I didn't
get the check for cppunit to work to my liking, and am sure the changes I
made were not ideal.  hopefully someone with more expertise in
autoconf/automake can make better changes there.

Anyway, I wanted to get this out there and in cvs so others can contribute
if wanted, and so we would have somewhat of a base to start/learn from.
Also, it would be a good habit for contributors to get the hang of adding
suites/testcases while finding/resolving bugs and making enhancements. This
way some inadvertant sideffects can hopefully be avoided.

Cheers,

chad

P.S. I spoke with albert today, and he will be contributing his testcases
etc a bit later.  Feel free to contact me if you have questions,
comments/suggestions, or if you have trouble compiling it.  I will
contribute new suites/testcases as I develop them.

--Boundary_(ID_OItGkMNEphWhF9WGQO+MBQ)
Content-type: application/x-zip-compressed; name=ccxx_tests.zip
Content-transfer-encoding: base64
Content-disposition: attachment; filename=ccxx_tests.zip

UEsDBAoAAAAAAIyxPS4AAAAAAAAAAAAAAAALABUAY2N4eF90ZXN0cy9VVAkAA0fCOD5Iwjg+VXgE
APQB+QFQSwMEFAAAAAgAXbE9LvVyb/gJBgAAigwAABkAFQBjY3h4X3Rlc3RzL2NjeHhfdGVzdHMu
Y3BwVVQJAAPxwTg+98E4PlV4BAD0AfkBfVZtTxtHEP7s+xVTR6LnYGwDaRKZQJU4kKIiQGBUtRVB
6/Oevcl597q3hyE0/73P7N75BUe1ELu3L7Mz8zzz8kLpJCvHkt4leV5q5brywUldKKOL7lAW7kQk
ztjHKzlRhbOPnelR9GLjzsDMcpVJe1G6vHRO2h8fK1XXQbyXe1Vq/fwcHlB6srqizExolR9FUbe7
WG1e//Z+WM5GeJAldaZN3h5cXt6cnw7vhsfXw7vrm9Ph8d3V8afT6+HV++HpxXm8fql1EEVlgddI
i5kscpFIKtwYqy/GMlVa0s3ZxfknKuGKiZZjyoyeRFFYTGyyv3fnBIT9vffL69sD6nbpzJivZU5+
lYS14pG1oiuZZjJx8CepggRZ+U+prJxJ7Sg1ltxUkklTlSiR0eBqsLO/B0WEHgs77rCAP01JidB4
VAon+UhBc+WmpnSkXJtGGCHkkeZG/+woMRpiZ+SMF70UFVSv1InDl5Vpm5KpsPjXip7w2k0BW43O
Hmn0SKcA7Q4PwtghmxW3oqgRbt6LrJRxj93YwLXruchppBz1vFE8e+M3eLa7WHvdJumSTtTAQqzg
AUWHtHuA4R3FyZS2abeFr+3tVtR4ihoNlcZQkbawjK+Gf5T+xRV6Fy7skIIKjQafOjpiWVHje4RP
V1odlDyIvnsgBiLL4BKAkJY6AOLtNBrQw1sKxgID9U16x8HsgGUnujdq/CNfPFVS4TE460LzkY8Q
YSbeUdgd8nP4WwM5N9mjNjOelkW4W+Hu7yhNl7//pfI2/aE0RgKAdAwJVkvXoRqAMrtcyjmk3kPv
VbK7Ox69qRABL4P9BVDOrSxAOKb7++vB6anHHIEtAbwZy+IZIj2PCAs9OVmFY5X36vaw5pJq09sW
I7L3irFgsL2oL0HUF4D7FoMX81wIjsTPViBot0WfN9a3KPa472P313X7+9TzNNiQXau4vtGm/T2c
J/y63YQDCWIV/2v2mzxsaiT1OPPcCmS68KQBqtlq1E9FQSMpNaXKswJQAlw+5uZmQTtkgZG5l22W
s87HEOLYz7IQ5yFDeZo+f6wTsYs/SU/KOGRO2uL0uknMwVToiRxirybmB2SG0nreg4PLLHcvrGLp
RTtEr0wE72s5EU7dy5pReNqacQkfTNVkyqFd+PNzsFTSN2mNX0MalHXCQwYKmcIJ64h9zknMm+qP
FtJ5YZ2a4ECYLes9pNWPEWabM6kxW6jMVH6JLJim0lbch1eCv6SeOJaItXPjGDEBhqcBEriDs6UT
CpCc35ydLaMiWJNbk8jCQwD4YU2QmipbuHCBQ7NOFiE5cbxrTNU4PHstA08Q3R+QAE9QJemjnIEF
zgoPemFKC0dyHPobHD6CZhIZHpk4pbGENKjg3fVMTWYYuOYDGMaC8GxVJ9gds8NYBXEvlxbjBs+D
v3AtTDgM1z3a8pKSO+hZC7qUNpQW3BfZxFhoNAM7SQqk4oVWdRYL5Yd52a6IvBEwgU7QYj6FFTH0
3tnhJOGh9zr5ydERJ5jPa2FZbW35JMWbL4Ml29u3QdvjB3QLBZP24sq/jBxYZhXtvAvQ0mjNenk1
OouyESR/piX1fA1h7s1AFp/bhJ0kVel8yR/3f98i7iJOKEywxMxmTI6MO4kFyZo7hcxSRLhrsgY6
hH9VH3IDVo1KlTEAMvkaZB0eheLhGyualXxG1t5NqraLpLVgDYMjXAcXR8ZkxG9xq8N+ZHXpiPMq
bSGPotPp9wM28YpSLTo8DMbs3nJl9xpoOcdkkOc3KG/9/g96Qtqy9ezwfw/2+xPp6o/YZ+CV4w/u
RoVroTck6wc+FWYdMR7zdlw/15mJr9KvtIK66Bdqq1v4fGL9Q/Lz/kJnJ5gCpm5TOf+JH7txeaiq
EyjmHELwZ9CGzFwH5OCh5emOP14pjKS2aIljv7Fi8UbT3O9XCi7vbFWCAnfjVps8dAk0bXl53onf
oxrzuSiuS05aacldQX271HGz2aZUZIWsgd1saA6i1Xo4lQ88wIR5HMr7erGJm7nKc9OsXF/Fzk+r
Gvi+GOlQWoe0guLYY7IXZcL7aOK49gmVoRAhvv4DUEsDBBQAAAAIAF2xPS5XNq+Hsg4AALAtAAAT
ABUAY2N4eF90ZXN0cy9NYWtlZmlsZVVUCQAD8cE4Pi/COD5VeAQA9AH5Ad1a63ebxhL/nP0r9jqc
WjSW5Dya28jVOSYSttXodSQ5cdL2yhhWFg0CFZAfTfK/35l9wIKwnTb9cM9tarHszszOzv7mscBj
OnA+soUfsIYf0ksWsthJmUcvbqmzSaMVDNKnjZeN53QRR6uc2Fk1yGPqujc385QladLMRig9zqQU
eWACEOtG4cK/3MSsQUBCJ1rfxv7lMqVPX716sYe/P/Dfl/z33/z3R/77ao8+29/f579P+e8zEHAU
M0an0SK9dmJGj6JN6DmpH4V7tBe6qONs6ScFHeB2gUyJZDqg6ZLdKQckXPpXLKGbMPBXPq5qzeKV
nyQwSNMI1rMGW4VeM4qp5ydp7F9sUkb9dA9Yr/10SWEAr9EmpavI8xe+yyUne9RJaBCFl3hNUc0w
Sn2XoYbrmCUsvmIetxJfwzqOLmNnhaP5PB6FFaH+y2jNoOGkMDNMFwT0gtFNwhabABUBWvquNzsZ
nc6oNXxP31mTiTWcvd/DJSA/u0lZmIq1pRIBgXN9oFQHGeyKibn81TrwgQRMFTthekujBR3Yk84J
SLRe9/q92Xtc9FFvNrSnU3o0mlAL+MfWZNbrnPatCR2fTsajqQ2LK4Kg1jH5Vtdxj+loDRNOo00M
NpmxgLmApk4Ur6OYGxB2V9kG97ZiY8GuDk3WzPWdAFbosnXKdw3WAOhego58b0HKX9/d8t6CkL+z
u4+/fXtxc0HKN21vtrkg6O9sb+XmTk/sfp+2afPCD5vJkpAkdj0/hp4GSaP1PL8FIIBNFv4NUm+S
uBlErhMQdsPceTZgfBLNL4SAQMFpfNJovuBEJLlrEAdI4F9gZyWBHCPg+Y4iyJiXgCiS3CYYv8qD
LHUJJ/CSFANfaRhwS/iCKkevnBi1uksj4oeLqMyDfWTlhOV+6AJ6N9h4W9PIbhIFXoGCm1sNrj9e
aouvybaJK1hFobteP0OSXNuaaJYJiirU8tsCIULgYuMHXg4Cq9Mfdaw+V5yj5wttLqMVa7q3YLmk
6V4l11H8UZPSFPmkyX0WnK1ejzchdVxu7zqkLmKdzkad0fDo24VCQsQBLnFgvbH/EYmYYjM9T2yr
a0/+EblL5ngsJsRZzeeuByI73bE1O2nvGManD9OT+Vt7Mu2Nhk8aX4waDsynNviwNRtNzB363XfU
9UhvOJ1ZwoMRJOjFfggYhuhTd9XofDwZHU+sAVda9n3JBrvWzCqM0PqKvnzxgkhB82SZ0dTyPhMm
qKDUpioR61TTzqQ3nlURKa1yim2N8y2o6YswSQrBMFlE8QrGkr0b+EeGo8nA6s9zO7XIeGIX70fT
WaFD8pwOy1ylHuQrdnFfmTuBDwmlTeUtJIp1wFLo8F/++LK+duuBH25u6pfhhiyjJM3p+d195KkT
XzKNQd7fx0LsM9s+Q0uS0eufRSsiRThx3a3BzPp2XINGxJqCmENrekisd2+geelcfySvrak97/de
oyKdDva6LjTOzubdntjLPN+YWbTrjMeClNZtvAFzz+ado751jHPUe3km0lkEFQSU3nEhW3H/AN03
oZ/WhfoZOajGRfY1cgidtB5IBgK6oi5PnmBLKvbkCSrWtcdiEQ2PrRPS7fdnoxEi4lA2D0n3/XDe
H0nc1gMvIHbnZARt5i4jcjSTAsixPRuNM21yd5iBOxT8WG7Stksm5E131Km0qhe5BCSLOQANfAro
kNoaNS7UlFwq8JtohzSKAtIfzpElCHGW/myOK4TLIbYH1s8cSPt4M7H7Nuw33D5tPCUDqzdE2D1G
BHZPB2i5Q9k8BCh23ljHSKslnvHsZAJePudIIVAoCeSAf2O+nY46b+zcSNNpn1/QRuj56A5EClBQ
UfeSh9bX6TKG+EtkkOWq7jf2CdRlw4yr/o5HUogqPnAwD2ot3yXvekONa28f/5GzQf9ZCXOItptV
8ExBDUi+gqIEbglr3AOk5CQlrHKU4iBc/oS/FfkAtrCtQUYY/MmTjJSFcUI6C/b+sYlS7MOyJKvk
tGiNyn5dKJA8dSgkMZK5V3PvNgwizHIg5BbKeDB6sYpUigiQwB9UsYAdMFLfRtX1Y6FqY0ybTSyA
+BRhhfs6sNEpleloHcLRCMzRnR8PT+fT0emkYwOqdUyYd2xub9jpn3ZtsQPVQanftbpdXg41YQjt
77oQap81AiefBE2PnpQ7vkk+6BtCwgjtpZwau/PDOiF5W+pfJGiA3emvhFb9N3XgeMBGF78zN32Y
brq5eJh0BnPOu7D9DxP5l3B5kMwOoQTl0uB4qa21yrZwMpK2VeBHw37IWpzHJBVSirGcSxPBvOH8
nRmSjayqtY1afZSoh5FkO4gq7KhkqVMTEQz0eqYYd5XvC+bGUjFwD5lLF7kXR0ZNpH+TaMNGrcRi
8hpUsx9WCp1ZCXFGTRQQZhFgefev5FEZUvlgjqACg46ZErGESNZLKhU0apWqF6ghP9vDrj3s9LgX
3YcKUKkKGBWuXsSbDD0EaoEj7uHdE+utPVc7jN3WaR/rzCy8QHxp8BgjMZLFmy0AYJGSJbJsLp66
haBS0UKgDIHovH4QjpKOpwFoY3BN5ivn9gLzgerA8kaBjTaaENJ4uWM2CzAYR9x2W8M5FrYpckzA
2PaAQMUdbBId26MaYscRL9VGgzFoz40BtzwowybJa2FXTH6kUG0QbNQgiyrr46jexiGZdEwhW7Sh
AipNK2ss2OL6KvJYG42Oz8NKCvEJ79fpHoUydSt1gla/m9mA3/aGbyq1g8PDR0HX7963zmxGCUkR
KVV2jagBZS+kaC1/GbXttGYKIjDXgBdU2gNsPfuTh6QQiKotiuWHsyKkMT09Ouqd2dOW1qQ8LTUC
ABv+f/E7yZyvqU3Voo8LWlT6Dj4eh5oE1i8eiMwHL0zyCI7xBWI8poOVUIR6JIFmhhBCqx7NE9VA
FSp1o1tJQiYHfHC1STQNMgrUIQsDjSI9TrIRz4eMQxFLS4EADOsGzAnrImeolNEijw4DP0nbu9vZ
ZPeAwiGcrvHJqGEg1QH1ImGHRfscTzzQv/6cMI/uJs0sRxlGs7l7fiAIOdUOhbN8fYHU8LfYkWOF
Tso7vShkpCLvtYpoUdmh2KvnB5PCysQEVWn0kfALcJ2SDM0HHpxPlBPC8xC5K6iWg1thZhkawL51
ocX3Wl50o5hBB14IwWfQd/KkzkXDJepJ431h+x4aPXZXkukB/B4CFcjvJsmieSVJMaRrCweostBT
644XOhfEAPD2RgSjCX9BAVD9aZdGfEHQPtyl8lzbDjk4Je4R0Wpi43uYcJemq3X14AxHf5WggP7B
qGvjvsq8amZjMhmIEzpGRnqO68G94lp9/iwAv5s7/e658ZNaw8Xv/6urcG8v1066pPVravx0LvUN
vsbocBy8R9/gfoWDr9FYT8N/2fK5YFEK8cx46brPi+4qV6O7XhCpkFkaRHxCV0Ln+KvjeEuKeuIC
Vak8U+P7BMhsLTj8zkT5x1LnMhF3WfWJXS2KXYT0uhj8xOGCRyCVKnngmY7xipSitoPQpuK5Rqdx
V7Ds8tALOv6xYe1zjPl+Vcyn1F9QZfQdw/B3+AvdkMpM4B9QFiRM3mbbwAcWvoz5GODp5yyZvoP4
u4uiP/E3i8kvhrH/Gz6OOaBf1KzwH4R1pADNalw1TmvSdeyHKQXRX2S+gXOZB9r1uqCOWA8huNAW
vcOEyhDF1AGSHhUspOxGHuHOtPlcSxaDtdbXnpj6Pqv/v5tdaPcnaFfjOJ5bE0ihhoHGUhuxI+SC
n0oiUzX0QrzYoQnLtBJStf095hus9kPUPq639fQTyyfcLCGIv3Yp1Xhq4JJPUPdh+FhTwDBwBt3d
uZdmvs7dGZDHeejxRFym7+GsfozP6Xl9rM5fEAfzatlUtxp2ZvZZb3g0EmbIHpNBNkSNUYXsVV5+
I5Yj7wEBNflM1qwbNfmk0ySKviUnVVEjKwPzTlkAilf+28DUYAn1GxLB5ooeT/ZIpHrthgSp184Q
qqPTj2U9uSP4dgCrWFbWGVSWe81f/tP87XvD2NvLyko1N9AD8w79VztnhS3cGmsop5Ewwhl3moLg
QHUatcJzHRPxrKxZIOVL0STt7sqBbEWZbdASXrNgjbJXewWv5YZUSwBeVF+zmS4Bzh5rWl9PtvlL
evPseOOn6N+SN9M0F5Lp+SC7vv4MArUceEKKJABmPkP1BNvEhZmkmuJYsGTuR8yd6nTIO1pU9RPR
3coOfTCN9mhM29lWdteiKjEDv2rihwH5AN7po/iqPh/FOxzNMnyL5skeT7B5O9P70aFRE0dIHvOw
KUNeac6tWZQ0uXL9TleRvzppYe1UPU3phXJ7J38DW3hDZcqgXRxEIe16IobOVezH1IfDJq/F5HYK
ny5NN7eHb9ucFjvaOePOuVpRoTbj38r5bkuVY/l9HoqzPhWNNQxsP23Fs5oDOQz+WFwvSzgUWvNv
hfDliBN6+K0Q0MMhBb+1g5iYsyf44c8mYTsZI8DXYwEDw4iEKb4mglM4jdkfGx+OfupDKawNOX/M
eJ5qgJC6lkyrXqbAnoB95dG5mkLYCRyDLwxho1qqTy6WFspWWvWAgFdV2magtMzsLZrvQGFAmwpQ
vHXCpeWjH/fx8mbSrcKaFnMvTHjlgw5XvpidX7lvLyJ0Dl5pi1s1UHAnrUc6nNajhBTK9nwYUNEq
uqNgL+OqRbeQhmIqOovG3GaTVimcW0B6aW+K98VxZf0K5ypvszq4ED2Y6aEtM0hjfDIavm/Jsgdf
xQliEZaz4CzQQLcm/QoEZmapAFIBNxJLXwOkAh+v91QZBSiSiOIIUjBSSEDO3CKFAF2O1oVorvOV
o7ucp2BYqgFN5+WhvRD4y1lA3fMXWbitJSDdiSwdF2U83AedCtzwQwFaNQNMIStW4egxfnga0CuI
qPhRJ/3leeOHV3vPGy+fm/hZ5PHwlPJvpCFahlEKVcI6ilOOtysn9p0LCLT4EfIICqT42of6xKHJ
bZKyFeXfm9Iahu3pbfKWQjAGXZPU5DH5gvHvVZmH34g2hiP7bDyazFrkv1BLAwQUAAAACABdsT0u
qBGv9lECAABqBAAAFgAVAGNjeHhfdGVzdHMvTWFrZWZpbGUuYW1VVAkAA/HBOD7xwTg+VXgEAPQB
+QGdUl1r4zAQfNevWEgfEkidtm/lOIgbO63BsYvt0KQcGEXeJLpTLCHJbXq//iT3+nFQCJxfdrWa
ndlZeQAzqV403+0tDGcjuLy+vj6/uri4hFxhC6XsNEOoUCCTB4fVSmpquWwDMiADqPbcwJYLBB81
Ihi5tc9U4zegBigYhYxTAXhkqHwf2D0C7exeatjxJzSOpWsFP3CLDSjUB25Mj5PA3GhA22bisA03
VvNNZ52UHcMzt3twZR9lZx3JQTZ8y1k/nBl7dSHbnY/WD9lKy1k/ptJoUD9h88mC0nKn6cFffwg1
wF/H3UuFLqHWSTtFIWCD0BncdmIMm179Ianu8mUFYbaGh7Aowqxaj70H349Hi619NWc97+YFBH3+
9jY94BP2So6IH5TgDuJ2qGlrX0BuYREXszvHGN4kaVKtve95UmVxWcI8LyCE+7CoktkyDQu4Xxb3
eRkHhCzCxLUkmWtO4zCbJ2lcwndY0F/oXyxw5t5yQuJVVYR1lJSVgxRxGC1iMlut5ml465umb/kU
zobVnQfU/XkEU2c3ez1MSZLN0mXU65wnZ0MrVW00a7geTXjLRNcgSaMwitx9EEzc1UTwDWO7trsK
BP3gTpMbR302jNZZneZhFBcj8thXPbP4TUgreWtsfV/kt0W48GXGjsfaorGGkI+8LvNlMYv/BQRM
KfhB4KuvpO4FMN/8RGZP48pucxpaOc06ohZPg/jOhZOwuN3xtmcjg09Wv1qt+/f+rna1SN/3+vie
9T0j8gXLpDN6IiSjwjP1bEp1LbcB/R+FP1BLAwQUAAAACABdsT0uBaaAUokOAADXLgAAFgAVAGNj
eHhfdGVzdHMvTWFrZWZpbGUuaW5VVAkAA/HBOD7xwTg+VXgEAPQB+QHlGmtz2zbys/ErcA6nlnqW
lFdzF7meISPRthq9RqQTJ22PoUXIZkOJKkk5cZv+99vFgwQoxW6TfrrLxNK+sAB2F7sLig/oKHzP
FnHC2vGKXrEVy8KCRfTyloabIl0Ckz5qP2s/oYssXVbC4bJNHlB7nq4W8dUmY0G8Wm8KmwCxl65v
s/jquqCPnj9/eoif3/HPZ/zzX/zz3/zz+SF9/PDhQ/75iH8+BgUnGWPUSxfFhzBj9CTdrKKwiNPV
IR2s5jitfx3nxroBXeCgXA46osU1+6we0HAV37CcblZJvIxxu2uWLeM8ByYtUjqHHdBwFXXSjEZx
XmTx5aZgNC4OYeiHuLimwMDvdFPQZRrFi3jONeeHNMxpkq6u8LvAZa7SIp4zXOE6YznLbljUJmoP
6yy9ysIlcqt5Igo7wvVfp2sGQFjAzDBdktBLRjc5W2wSXAjI0tcD/2xy7lNn/Ia+dmYzZ+y/OcQt
4Hj2sWCrQuytkE5Nwg9Haumgg90wMVe8XCcxiICpsnBV3NJ0QUfurHcGGp0Xg+HAf4ObPhn4Y9fz
6MlkRh0YP3Vm/qB3PnRmdHo+m048FzZne64fjJyXbi0cGr0md3oLvU0na5jaSzcZWMdnCZtDePXS
bJ1m3JTgZ2Ul9PIOF4OFQ5qv2TwOE9jrnK0L7j/YDYTuNayWexm0/HU/170MSr7Ezw++3tHoZtDy
VY4u3QyKvsTRO93snbnDIT2mNgfA1Xk2j+IMKQKySZGug4paYTZ5NXX8M10UjLaIPyJFQDZhH9k8
qMgaCnNdxiupVUA2yStSrmhJfInDJLnCbAKJIJRkCYKG2xzTmVJSYsC5hoCL8gIzo+QaFJgpnYeJ
LmAQ+EqqVXBKvFqkkiRBmyxDtQUBodQ82USsFFSYTdIkMpidTZ51JIWs319VO7QaEm527KnTe+mc
wsEEiXJNVkOANb6h3mpUqC6HTr3cxEkkxNpw/J3ecNJzeGhI0CbOuT/pTcYnnChhQcU8oagiZyB0
5jp9d6boAgO3h8sgmEdA7vUxgI73Lev3t95Z8MqdeYPJ+J/tP6wGMgLPhZB1/MmsuU+/+YbOIzIY
e74jAlaCtqIF09nkdOaMNJ4iVTJ9x3d0AcTRP+DjJAnyayWAhlK0Jm3NaWtJnz19qktW09WFdSmv
NxtM/V1CagmlhG1SqkWXZrQa+rqbpICzny/SbClOHE9OQUkMVuGS2WQ8mY2cYVBZrkumM9fEJ55v
EOSY83F9VI2C40wSj6IgTGLIqHiuK9SWPEib64QVJdcm12leVEMqTHK0AYhDtIbZFdNG6HjJ1UYJ
CgSee+G6F9zUArLJ5MUPkiIgm5iBhxyTApE98h0R1AgA7nHEA+j1Sw6+fmmTF47nBsPBCyQo2Ca9
HuK9HkIXF0F/MBO4gIE6nXLCdMphsK0f9E6GzqknyRpFk4BzODg1JDilkoDJDQ2IA/fighMvLjis
JueQTfruVK5PQEAZDv3JhJ8+CQLtzTgYTtQ5rzCbuL2zCbc1fNvkxFfaBGSTU9efTKulaWgV+p4P
R2HXyTYYNnnZn/SUNRVsE9AltIJz+RwGgfPVfiQItHEgROEbMD/giB9weOT8IGJCwZw6c4cueFjS
JWaTkTMY89DiAI+1/vloKoMNQYw2noFFmMlkPPXPZnDiAxErFWYT6BdkRAnIJt6k99KtbKihwPNE
YfdgV9xcHEPAJlJpGVk6XnKVVg2Fmi+SNNIlaBNoZcaVrgoDzmCsDagwm1yMho+1wNVQzjNZBqec
qEQEXS1XwTZ5C7t1nVHJ0XGblyFZDpGpoYL36yYtSg5HeCWvmpkS0SuIYCgMKjxksPlNEN2ukjSM
GO8A6jRIWtdZpbdEIGXx2IE/6O0grMAIQxe3ol+bFIz5zZ85EPoehh36bOTiua7yh4RtqCS6x5um
0wbj3vC8z+dpDaxG1fE1y9Zk2Hf6fd4pdIDVgc5jPr9abR63k7DSjWZuAlolhSZ5q5zRSn4jZJWi
qdQxRvJ8/vFjULC8yAmp4MCbnM96rinQnq/X9CdCd/3zQmiQ2eTyFzYv7pfzNpf3i/owZ9CHVvB+
ofgKvu4Vc1fQnHFtcMHS9rrLtnA3kLZV0Y2GfVtCfEyT7NDCO0rex6Imrm293qzioh1+yQz5Rrab
mqOW72XAAyfnbQq/TOAoPXbEU4aOIU3EwdZbHL0XLQNODm5fqwH8NATyONwZR1ZDFPsm0dhWozak
ydtSzX7YD/T8WsRZDdEmNM0Aq8g/kb16SFXMKoKMAXrM1IRliJRUsnOBVmPn0g1pKOHuuO+OewN+
iu6KCljSrsDYcdTNeJNphkDjcOKJtuHEwzbixDkfYn9ZZhVIK22eWmRolGlmy+/YwOjtj8xQ5WRQ
cfuKJpO8SO4RW8/T5freaJRyPOEDjHk0D5bh7SVmfkUg0OqBAQN/du5iM6TijrY7kN14c9TsGBEx
TcGM+qi9bdEqRO6WrsIG5LYZInD+hAoZTHdLasE+TXlTOBlNYbfckIDyfA5+ld+GZ5v8gqJgCCOr
AcVWeQ25OowsWY+aQreAoaOqTSt7MwiT1jKN2DE6DB8m1RbEJ7x7TXcsqFzuzjUBNOyXNuDoYPxy
5+qSePVeyA37d+2znFFGsEiyEmyl1IKjA5VcK31WY7siNoUQmGvEeyzt0a7eJJD7tBBIyF0KH61w
SUjbOz85GVy4XlcDKa9o7QSCEP9f/kLKA9zRpurKhpc3LcFo0ndFmBlL23kYNxnvZ8Ao4oFDMHra
JHvzyBTGJwFgOlShnjag7SElUS1VlysiCvjsunbugm5VIlmB8GnQJteWVUrgwspk0zblcZKNeDpj
2SJh19INuGCesHDVEoVJ1aUu2bOTOC+OD7ZL1sERhXs+XeMDSMtCqSMapcI4i+N3bH4NUWStP+Us
ogd5pyyEltXpHLw7EoJcap9mS9paoDT8LfYlzyBSTozSFSM7imvXjCtVgkyqXoSaFHYmJthVq/fE
CYJDVtOhnZZ75xM9izijGONLaLyTW2FmmUTAvi2xim+14jtPMwYE/CIEH/V+dkwRXrbnxMinxk1C
vz3cUS30O8YX6tLLyVep0+vN36BI1aevV1UWsK9SZVQ4XZPmaDiabBUpP2cLvexCdoQ82E67ZhHN
+W8gcEy/P6Ap9wPA9gGFfqlI0+R4lVIh/wLu+d7Q8c7Mte/JdIAHXS3V+haWeECL5Xo300fu3Vr5
MQIU8x2eBNnvNLeHCVFZd8UzTyxC9B3aCoOdb+3TJ5ExDqqsefDO+l4Z5fKX/xuzzG+v1mFxTVsf
qPX9O2mA5K+GxS3Lv8wAyd0WSP5eE+g92V+OjWoe+RBCYraZkaVJ9OyapKoq1ph4JIGU0wA/9aO7
pUUSCNxuxL2zhb/UQJvTJcT1xS2CFeFVLrDyFoOkLkUSIYM+1jdxSeVFRvVNvLZ4U/xGSXExgOql
SrYmp43eMeSAV1dY468bdvwOy3q8q6xTGi+oMvq+ZcX7/EfyFZXFPj6iLMmZREs3cMYilmUdazj9
VDZRr6HEHqDq3/lvtPmPlvXwZzDKoyP6h5oV/kHlRglYWYMvjcs26TqLVwUF1X/IlgLu9xGsbtCH
5Yj9EIIb7dLPmFAZwuwOQNOeYSFlN7KHnjnmc12zDKy1/hCJqe+y+v+62cXqfoPVNXgcB84MuiTL
QmMpR+wLvXBOpVBTAfqtzCRoyspVCa2af0+5g5U/RHs7j9SV2+iQ0VlCEf9Fr9bbK8YVn6AVA/tU
W4Bl4Qz6ceentDzr/DhD5PEx9HQmvrw3I/jEn3H4ZUld3iFjVlenpkK12PHdi8H4ZCLMUD5ahQYA
V4xLKH8trRCxHYlDBDTkY/1my2rIZ99NouS7clKVNcpOvyLKHl+8PLEdmFpYQouOQuBcQYkkRUZq
dNyWQRodlxGqR2ecySvDvhi3D7GKN4cWg8vDYefH/3R+/tayDg/Lm4OaG+Rh8D79x3E1FFy4xWur
QyPDCGfc7wiBI0W0GsbzwSbGs7KmIcq3omk6OJCMckelbdASUcewRv1UR8ap5YZUW4CxuHzNZroG
uHOuaWs92x5fWzevjh/jAs+3HFuutFJSrvPe4fr+yxBoVIEntEgBGMxn2D3BtrAxk1ymuPlds/l7
rJ3qUQEndKmiE0Hulpd9mEZ7xKp5tltiXaoKM4xXIL7jUTEQ07n4KkTFRQy5ZYXv0qrY4+OMCi7X
vWdbDfHogOc8BGXKq825NYvSJneuY/oS8fWgdRd7p93T1F5RON6vftw3fttsyqRtMlHJcSsXrHcq
92PpQ3aT92LSneJM16YL3PGrYy6LhONq4P47tSOjN+OvFMbzrmrHKrxKxSVNZWMtBraf2uN1PIQa
Bn8sa9U12GLV/K0r6ErxRRp86wrk4V4GSQlzYjU8x1eoNjnbLwdC+EYsYWAYUTDFe1nL8JZm7NdN
DLd79coZ9oZ8fMZ4nWqDkpZWTHf9AAc+AfvKpyO7JYSd4GDwjWHYKEjR5Gap0bbSXc+AeFelOQO1
lWbv0soDBkObCqJ46yEGrd92+RmvO5NuNdbUrL0w4U0Ma7iJxez8m5/tRYqHg3faAlUM4zhpFHng
NIpSYrTtFRuiomseRzG8HldduhVpqGYH0TTm9jBpFePeAtprvjFxk6+sv+Nw1d2sLi5ET2Z6aisN
0p6eTcZvurLtAZbMciItl8lZRAPdmvRPRGBplh2BZMSNjKU/E0jGON7vqTYKokhGFI8gFUYqEnBk
ZREjQdeztZHN9XH17C7nMQxLtUDTx/LUbiT+ehVQOP9BFN1aC6TPRpYeF/V4uCt0dsQNvxSgVcuA
Marirjh6gK/wJvQGMiq+Hkt/fNL+7vnhk/azJ018wfR0fE75q+SQLVdpAV3COs0KHm83YRaHl5Bo
8cXuCTRI2YcY+pOQ5rd5wZaUv7lLG5i2vdv8FYVkDGvNiybPyZeMv/nLInzbtj2euBfTyczvkv8C
UEsDBBQAAAAIAF2xPS7lhEfopgYAAC4SAAAbABUAY2N4eF90ZXN0cy9TYW1wbGVPYmplY3QuY3Bw
VVQJAAPxwTg++ME4PlV4BAD0AfkBrVdrbxpHFP3Or7jdSi4kBDtEVVVjW6WIJEgOsQArshQpWnYH
7zTLDN2dNaFV/3vPndm3cdJI9QfM3rmPc8997HB6ShO9OyTyPjLUnfRoeHY2fIGPVzSJ/JAmA7rz
jUgpOPC/3zIZ+pEeiDDrnJ4S8ccqkintEn2f+FvC100iBKV6Y/Z+IkZ00BkFvqJEhDI1iVxnRpA0
5KvwVCe01aHcHNgPZJkKRUImEmREsk1Jb+zDm/ktvRFKJH5MN9k6lgFdy0CoVJCP0CxJIxHS2vph
i9eMYZljoNcajn0jtRqRkDhP6EEkKZ5pWMTIHfZJJ+yk6xtGnpDesV0PcA8Ug4LSdMBqx/Kv0gxJ
Kus80jukFMEnktzLOKa1oCwVmyzuswso04fZ6u372xWN53f0YbxYjOeruxGUTaRxKh6EcyW3u1jC
MxJLfGUOwM8e3k0Xk7cwGf8+u56t7pAFvZ6t5tPlkl6/X9CYbsaL1Wxyez1e0M3t4ub9cjogWgqG
JdjBVzje2DKBx1AYX8YpZ84md6hsCnRxSJH/IFDhQMgHYPMpQE99u3rsxI+1urdpQrkickRyQ0qb
Pu0TiYYx+khd2b6qbZ9mKhj06edfaSXAkqCb2A8EvaBlxi5evTrr0+86Naz6bkxnw5cvX754+ers
lz7dLsdlPccpEkh3IpAALL4EwnZAgeDpbPq0Q9PK1PYVMmFf91wjMMIU+mEo2RMMUfqyuY34YsCX
ArXKdYw0KbiMhZ+6FKE40dstvE6eP6+1naihQzzurz7TxhMXS/XZuq8sIVsnfnJwZGseA/azkTHA
IDswH2bgC7MqvoggM/46RlK2KqGGDsqBEWN4It5gppFF0T2JSLPYSFSyMmWfaPNAY2DscH6Dv0He
UwnT49jBwNT8AQfYURq9f+CImLKAyUV6fhCgD0w+DJw8Y3ki/0CHcKYAT5qil+0QV3SW+UZ6j9FL
oP7gx9h9RthNYNkDBj/VKqV9VC6eGlwmlrZ2sX4vDUcQ+Tuee3SNig9FL9pE8k4Ja8uTzZW/rSeP
YZ+5zrCjaS03id6WmVgnqaOlnF92VPno87a14I/vCdv+Ju3nRNS5tIhAJ2fRhG+LzLgwHm5dIm0U
GIBXQPKgZQgSU8ALUVK7MdRBK7v5cz+p8U1m5ynNgsi9UXhF2s7uW+fbLDVYX7EwwlWqwS2QIQXH
BxxuyxnLKXMryPkN7K6x0dz7Ya/sdNdpwpKHf3scRBqu2dc+EpZqnjRLVBsFE1/QY20bAQc1PKG2
ZO7x1sun3qV2PK9Bp/OjVEGcgW1v6fNmfL/+QwRmEHmdzuzdzfX03XS++nQzXSxny9V0Ppl2V5iu
vsefXm/U6fCX83P+7PY65yRnWGr3Iume9fpgP1liEtV915tncezVRcNC1vm7Q6Tw9cYkdEnz2+vr
ESSnp5mSClsRs/WXCOdOYUTFH5cKNUbckr5M7fj9m9pl4yNFxcsTETO7C9gzPfgJ7XXyGaQRemLt
0m2GrouHkNefRxx4pzELVY/xOIFeDpo2fXL1GSK35z8NrviDTvTapV+whmB6PSieLJaCL3dUPo7Y
31rrmJxT3CIS3+jk8rJrc6YygOPAhkmEyRLVYfqqiI2QdHJC9rwWtxkYGk2FYVtjWKiobLtGQfLz
4qmyh25aGdun/JCvFMuGQl1Sus97JnfvnvLDY82Tax49ys2eNVvikp4xuLrsmOLwmGZJQylciE2R
bl3UVkvbSmm72HbpdKfqHteCE/KTIMLdql7oXEQXF1Wh8b0qYv1hOGpa5IVqSfMKPdJ1Y9mUHp3c
lrv6TD191MZWJ651VOuQp4xwUE4BYS2INrF4a4ePeG0wenVVMYrvFaP1hwZqHBxh1Km3wVrdR3RB
+i1G2d0TjLaO2tieYhRHTzBaNzrOqH0zO0Z3MDf5SkpNeH7usj6xlxBHbcA/Yi4u3EzzLkXJvPOP
yiuEHtU31jl57b4WKowbymUlzukn71Hne07WtqrKZ62aM1LYFYY27zpyB7IoNUC67Y2M+cLUzeWD
tUBzdfEiLARw1rXvRWjiBwg6cPsJ022X+UWocY0SV10O1EcIr9cbVXG/CiTvrkdAcnkFpBB8FYhT
+m4gtQ56BKR2VoGpC/8XQPXWf3HlutGrC73eo1f+Ub1hSxHjMmirQWbvRC0ePqrabu+G4s9M9Li/
2R/fELo2RSu/4KlZZusrJgkzUyZMsn4RKRnDb2H6oXFgWRvR8+ey5170ZTa4B24FfgjhJm1jeV8t
IXmX/+Hvo7J5YOb/BVBLAwQUAAAACABdsT0u/cQJqJUFAAB3DAAAGQAVAGNjeHhfdGVzdHMvU2Ft
cGxlT2JqZWN0LmhVVAkAA/HBOD4Nwjg+VXgEAPQB+QGVVl1vGzcQfK5+xSYGAjtW5C8URa3YqKzK
iQrHNnQyAj8F1B2lY3siVZInRQ3a395Z8k46JXaD+kGWeLvDmeHu8vbUVGdySuNBMr67+m3QH396
39rDitJyd7F1dER9s1hbNcs97fcP6PT4+PQNPs6on4uM+h16FF46Stf875dSZSI3HZmVnEr8Mc6V
o4U1MyvmhK9TKyU5M/UrYWWX1qakVGiyMlPOWzUpvSTlSejsyFiam0xN14yDtRK0Lflckpd27shM
w493tw/0TmppRUH35aRQKd2oVGonSWBrXnG5zGgScDjjmjkkFQe6NgAWXhndJanw3NJSWoffdFrv
UQG2yVgG2ReemVsyC847AN01FbBgk9rhsKf0b2VmpHQAz80CknJgQuRKFQVNJJVOTsuizRAIpo/D
8fu7hzH1bh/pY2806t2OH7sI9rnBU7mUEUrNF4UCMoRZof0a/Bnhw2DUf4+U3tXwZjh+hAq6Ho5v
B0lC13cj6tF9bzQe9h9ueiO6fxjd3yWDDlEimZZkgP/weBqOCT5m0gtVOFbOKY84WQd2RUa5WEqc
cCrVEtwEpaip758eg4jC6FmQieCtkV1SU9LGt2llFQrGmyfOlfO3Z9umoU47bfrxZxpLuCTpvhCp
pDeUlAxxdnbcpivjPId+6NHx6cnJyZuTs+Of2vSQ9Dbn2XMQ4BYyVSAsP6cyVEDN4Hk1bVqgaJUL
dQUljDXjM4IjbKHIMsVISMTRb4rby88efmlYq2PFKO/gZSGFixIR2DfzOVD7h4eNspMNdtiP66vN
tnHHFUr/EeC3mVibWGHX0WzDbcA4U1WADNTB+ayEX+hV+VmmpReTAqLCqWQGMTgOtBjTk8UUPQ0V
dfVY6crCK5zkNpUxUeapQcOE5vyOf52qpizbE91BwzTwwAPuaIPaX/OO6LKUzYU8kaaoA181A4tn
Ls/oT00GMA16yte1HJp4a+dGb25WaD2L8KUoMPu8DJMguAcOwhntaJVvBk+DLhtL8zBY/68NTzAS
C+57VI0u1nUtBiFVpWSN4cnpWsyb4tHsw1gZoTVD5tSa+UZJAHHRlk3/xuuhxmjztA3kn54Tofy9
a1dGNL0MjGAnq9ilHw6ZeaE94riEbBwwCI/BZGlUBhMd6GU40jAx9NroMPkrHOeFL0M/uTLN443C
IzJUdjuAz0vnMb4K6WU8qR1vwQwSoh8AnG96rLIsjqCIm4ZZE3aL98NKh+5u2oQhD/zwOM0NoBlr
lctgNXdaMOprFmx8bU/I3dmw0+CTmWDmCrde1fVR2tO6Oq3WntJpUcLtt2l6eHi04BvM+U5+2XgC
iVZ4YxtrLxPBczQpJ3eT32WKhJetVum4tbi83ILHKwZqt1p0Pjs/RyPuLkidFTsL3Lh61m3FwyQT
sLnps3CiaOx6DeNzkVNFV2oYmRbCOcx3xJzHmz+lK1RuJNj60iL6ddDHLTf4dD8YJcNkPLjtD/Y5
4aDVignnCEKdn52SGmI6z6TtUv3Hl7FwAPVrvrKRhuBImP8lFfVv107jIuQtQcTYt5nBZvKSdDmf
QMDXj2P+ZYWzfZzJP0u5ecrXblJHIIR14DheA7Uo7n2DeM3+9uHmBupw02Be/QVLFwZaue6ilg1C
qRtRtzVcjRBfVtxuFPcnbiqQK1lDE83VNRJJAWazr2kccgWGImcB7fDiE9+qGts8h3sa6DkJClkT
PswAHncK1IROw+Wx2XOLtgUbyelXhlchl9uYreH7Bxz8T/xKX+pm25X8d7eODsX5ykxC1sSYAu+Q
sbUuLvaDfbQJiXZ+E/jimUBsbqUvraYX+69Ds19cEO/E2wMkTMsFysVX+bGOXoV2PYghyvoSszvs
Fwbb/kDP8OrxioRNc7y/bUj9sBOLyy77JrTb4o330OJq2voXUEsDBBQAAAAIAF2xPS4WrxVOQQUA
AHMMAAAeABUAY2N4eF90ZXN0cy9TYW1wbGVTdWJPYmplY3QuY3BwVVQJAAPxwTg+/ME4PlV4BAD0
AfkBlVbvbxpHEP3OXzGikgvKGdtYVVVIohKEEyQbI8CKLFWKlrvFt+2xi3b3jFHV/71v9o7jcEjS
8gFud2fevnnz47i4oKHZ7Kx6Sj21hm3qXl52z/F1TcNUJDTs0KPw0lG845/fc5WI1HRkkjcuLoj4
a5EqRxtrnqxYEx5XVkpyZuW3wso+7UxOsdBkZaKct2qZe0nKk9DJhbG0Nola7RgHe7lOpCWfSvLS
rh2ZVVh8nDzQR6mlFRlN82WmYrpVsdROksDVvONSmdAy4LDHDXOYlxzoxgBYeGV0n6TCuaVnaR3W
1N3fUQJGZCyDtIRn5pbMhv3aoLujDBJUrh02OxX/IcyElA7gqdkgpBSYCHKrsoyWknInV3kWMQSM
6fN48en+YUGDySN9Hsxmg8nisQ9jnxqcymdZQKn1JlNARmBWaL8Df0a4G82Gn+Ay+DC+HS8eEQXd
jBeT0XxON/czGtB0MFuMhw+3gxlNH2bT+/moQzSXTEsywHc0XoU0QcdEeqEyx5GzyyMy68AuSygV
zxIZjqV6BjdBMWrqx9ljEJEZ/RTChPFByD6pFWnjI9pahYLx5kRe2f+Q24jGOu5E9MtvtJBQSdI0
E7Gkc5rnDHF9fRnRB+M8m94N6LJ7dXV1fnV9+WtED/NBlc+BQwBuI2MFwvIllqEC9gy+HU1EGxSt
cqGuEAljPXGOoAhLKJJEMRIckfqquL188dBLQ1pdVIzyDlpmUrgiRBgOzXoN1OGbN7WykzV2uI/r
K2LZuOMypf8K8AdP7C2tsLtCbMNtwDgrlYEMooPySQ690KvyRca5F8sMQYWsJAY2SAdajOnJbIWe
RhT76rHS5ZlXyOTBlTFR5rFBw4Tm/IF+nbKmLMtTqIOGqeGBB9TRBrW/4xvRZTGLi/BEHKMOfNkM
HDxz+Ub8sUkApkFP+X0thyY+yFnFm5otWs/C/FlkmH1ehkkQ1AMH4Yx2tE2rwVOjy8LSOgzW/yvD
CUZiw32PqtHZbl+LIZCyUpLa8GR3Ldb14NHs46IyQmsGz5U16yqSAOIKWar+ZaADRsTTNpA/PSdC
+XsXlULUtQyMICdHcUw/JJl5oT2KcYmwkWAQXoDJs1EJRHSglyClYWLondFh8pc4zgufh35yeZwW
bxQekaGyowC+zp3H+Mqkl0WmjrQFM4RQ6AHAddVjpWTFCCpw4zBrwm3F+2GrQ3fXZcKQB344jlMD
aMbapjJIzZ0WhHrNgoXfyxN8jy7s1PgkJoi5xVuv7PoitNNxdRqNn5SOsxxqN+eCJ+M8X94v/5Sx
76TNRmN8N70d3Y0miy/T0Ww+ni9Gk+GotUCDwS6iZvnUbPcbjfK51ysfWu1Gj9QYQ+5J2tZlO0I2
7BydqZ9azUmeZc36Vne/1/j7nxNYmIJIU7miM7OEXYMqeHpHZtnZr/o4qYCLo2p5dNZ9ddjtN3D5
0piMKgZ4P1vhjX337gQJCluBipU+txoPdVZHtOjsLBzXqB1fDwM6tui+NunuQXS+XuLfRnlerk7Q
DwXaGuknvELOSNg4xXu4zrvcordvD7zxfCBVX3T7xx7VvZUA5G0uT/DAQEy+onFE4P37AwE8HwjU
F0cEcPA9AmFAVAQ2cPdlCl3AOguTsK5FzP+nEFbz/D98/tDNcG3pVGSFRysD9HC632xSvSh61Hyt
tdRJdmRchdujn5tfZaNZ7L32OmgUvI7z9srvK+IFx72c4Fj0SdLr8bxvlfudpUQCW+jb/QbAWqGN
YYn/T8jy+gsKLnTM28TgLSDft/giDAtqttv9msqBCO0/nLF/AVBLAwQUAAAACABdsT0uq2HFiv0E
AADNCgAAHAAVAGNjeHhfdGVzdHMvU2FtcGxlU3ViT2JqZWN0LmhVVAkAA/HBOD4Nwjg+VXgEAPQB
+QGVVl1v2zYUfZ5+xS0CFMniOl8YhsVNMcdzWhdtElgKijwVNEVZ3GTSICm7RtH99p1LyY6yJiv2
4sTUvYfnnPsh7+nC5KqgbJxm6d3lzeX78Sj7/C7Zw6E26rvz5OiIRna5cXpeBtofHdDp8fHpK3yc
0agUOY36dC+C8iQ3/Of3WueitH2V15xK/JGV2tPS2bkTC8K/hVOKvC3CWjg1oI2tSQpDTuXaB6dn
dVCkAwmTH1lHC5vrYsM4OKtB3lEoFQXlFp5sEb+8vb6jt8ooJyq6rWeVlvRBS2W8IoGr+cSXKqdZ
xOGMK+aQthzoygJYBG3NgJTGc0cr5Ty+0+n2jhawR9YxyL4IzNyRXXLeAehuqIIFu9Q+hz2l/0Fm
TtpE8NIuIakEJkSudVXRTFHtVVFXPYZAMH2aZO9u7jIaXt/Tp+F0OrzO7gcIDqXFU7VSDZReLCsN
ZAhzwoQN+DPCx/F09A4pw8vJh0l2DxV0Ncmux2lKVzdTGtLtcJpNRncfhlO6vZve3qTjPlGqmJZi
gP/wuIhlgo+5CkJXnpVzyj0q68GuyqkUK4UKS6VX4CZIoqd+XD0GEZU18ygTwQ9GDkgXZGzo0dpp
NEywT9SV8x9q26OJkf0e/fIbZQouKbqthFT0itKaIc7Ojnt0aX3g0I9DOj49OTl5dXJ2/GuP7tLh
rp5DDwF+qaQGYfVFqtgBWwbPq+nREk2rfewrKGGsOdcIjrCFIs81IyERpd81d1BfAvwysNY0HaOD
h5eVEr6RiMCRXSyAOjo87LSd6rDDfdxfPbaNJ67S5q8I/5CJs5kTbtOYbXkMGKfQFchAHZzPa/iF
WVVflKyDmFUQFauSW8SgHBgxpqeqAjMNFdvuccrXVdCo5EMqY6LNpcXAxOH8gX/9tqcc29O4g4Hp
4IEH3DEWvb/hGzFlks2FPCEl+iC0w8Dimcsz+qXNAWZAT4dtL8chfrBzp7e0a4yeQ/hKVNh9QcVN
EN0DB+Gt8bQud4unQ5eNpUVcrP/XhicYiSXPPbrGVJttL0YhbafkneXJ6UYsuuIx7JOmM+JoxszC
2cVOSQTxjS27+W1eD1uMHm/bSP7pPRHbP/hea0TXy8gIdrKKx/RjkZkXxqNZl5CNAoNwBiYrq3OY
6EEvR0njxjAba+Lmb3F8EKGO8+RrWTZvFF6RsbN7EXxR+4D1Vamgmko98hbMIKHxA4CL3Yy1ljUr
qMGVcdfE25r3w9rE6e7ahCUP/PhYlhbQjLUuVbSaJy0a9W8WbPzWnpj76MJ+h09uo5lrvPXaqW+k
Pa2rnyR72siqhtuvpTw8PFryG8yHfvmm8wQSnQjWvUmS2vP0cAf5JW9Q7MxBe+hDfn6OWXt8oExe
PTrg2TTzQdLUi+zsTyUDz3WzCtVipnKuZ9NvGWb5pgnhkuLbNgP7c1lSy1cZOCkr4X3MSOsZnTdv
f0mX6N4GIvmaEP0xHuFNN/58O56mkzQbX4/G+23OQZI0OeeIw/Vnp6QnWNJz5QY46dDH/y5thTzz
4HT3ZIWrrXudW2CrN2RqSHQeDtCW7P7BoPMFGx8ytzpe2ll8+vculr5+44OZtRV+gzSlubh4Io3i
0XexL56Ppa9OhdoZerH/c+yYiwvi++lbpBtHbgl1oUXoKH8Zu2J3J0drF2rsgnh5HJT9sZnjVfaS
hJMlfg/son96FIvlmX8XOkiYwx76SRfJP1BLAwQUAAAACABdsT0u3SQ7WNwDAAApCAAAGAAVAGNj
eHhfdGVzdHMvVGVzdF9EYXRlLmNwcFVUCQAD8cE4Pv7BOD5VeAQA9AH5AZVVXW/iSBB851e09l4S
rQP50Ol0yst5OZK1lCUIjFY8RYPdxKOzZ9DMGMK/3+oxXzllb3UvJJjpmqrqrvZgQEO73jn9WgW6
GF7S7fX17RU+7mhYqZKGfVqowJ6Knfz5q9Wlqmyfy7Y3GBDJR15pT2tnX51qCP+uHDN5uwpb5fie
dralQhlyXGofnF62gUkHUqYcWEeNLfVqJzh41pqSHYWKKbBrPNlV/PI4ntMjG3aqpkm7rHVBT7pg
45kUrpYnvuKSlhFHKh6Ew2zPgR4sgFXQ1twTa/zuaMPO4zvdHu7YAyZknYBcqCDMHdm11F2C7o5q
WHAs7cuxj/SfZJakTQSv7BqSKmBC5FbXNS2ZWs+rtk4EAofpe5Z/fZ7nlI4X9D2dTtNxvrjH4VBZ
/Mob7qB0s641kCHMKRN24C8I30bT4VeUpF+ypyxfQAU9ZPl4NJvRw/OUUpqk0zwbzp/SKU3m08nz
bNQnmrHQYgH4D49XsU3wseSgdO1FuZQs0FkPdnVJldowOlyw3oCbogIz9evuCYiqrXmNMnH4ZOQ9
6RUZGxLaOo2BCfaDvkr9qbcJZaboJ/T7n5QzXGKa1KpguqJZKxB3d9cJfbE+yNFvKV3f3tzcXN3c
Xf+R0HyWHvuZegjway40CPNbwXECDgx+riahNYZW+zhXUCJYr9IjOCIWqrLUgoRCtP443IHfAvwy
sNZ0E6ODh5c1K99JxMGhbRqgDj9/Phs7PmOH+2S+ErFNEldr80+EP1Xi2dIpt+vMthIDwVnpGmSg
Ds6XLfxCVvmNizaoZQ1RsSulxRm0AxETelyvkGmoOEyPY9/WQaOTp1LBxJgXFoGJ4fyFf/39TDmx
p3MHgTnDAw+4Yyxmfyc3ImWFmAt5qigwB2EfBhEvXH6iv7AlwAzo6XCY5Rjik51HvZXdInoOxzeq
xu4LHDdBdA8clLfG07Y6Lp4zumIsNXGx/l8bPmCk1pJ7TI2pd4dZjEL2k1KeLU8pN6o5F4+wZ91k
xGjGypWzzVFJBPGdLcf8CtAJI5FtG8l/vCfi+Aef7I049zIygp2i4j392GThhXh06xKy0WAQzsFk
Y3UJEz3olWhp3BhmZ03c/HscH1RoY558W1TdG0VWZJzsJII3rQ9YXzUH7jr1zlswg4TODwA2x4zt
LetWUIdbxF0Tb+veD1sT031uE5Y88OPPRWUBLVjbiqPVkrRo1L9ZiPEHe2Ltuwv7Z3xKG83c4q23
T30n7WNd/V7vN22KuoXbn3LE5uVvjHG/+tTrDSeT+TjLX/LRLH+ZzbN89DIdPWazfJrm2fP4Qg5K
xeV97wdQSwMEFAAAAAgAXbE9LmX58JiJCAAAzxcAABYAFQBjY3h4X3Rlc3RzL1Rlc3RfRGF0ZS5o
VVQJAAPxwTg+/sE4PlV4BAD0AfkBpVhrTxvJEv28/hUVVtqMg/EDtFkFMFnHgcRSeCw2m4tWEWpm
2ngu89J0D8b3Kv/9nuqel8Hmofshzkx3VfU5p6uqe+h0aBgni9S/mWlyhk3a7na3t/CzQ8OZ8GjY
pkuhpSJ3wf/9mfmemMVt6WWNToeIfyYzX1GSxjepCAmP01RKUvFUz0Uq92gRZ+SKiFLp+Uqn/nWm
JfmaROR14pTC2POnC46DsSzyZEp6JknLNFQUT83Ll5ML+iIjmYqAzrLrwHfpm+/KSEkSWJpH1Ex6
dG3isMcRYxjnGOgoRmCh/TjaI+ljPqU7mSq803axRh6wRXHKQRyhGXlKccJ+TcBdUAAJStc2m63i
X9H0yI9M8FmcgNIMMUFy7gcBXUvKlJxmQYtDwJi+jyZfTy8mNDi5pO+D8/PByeRyD8Z6FmNW3kkb
yg+TwEdkEEtFpBfAzxGOD8+HX+Ey+DT6NppcggUdjSYnh+MxHZ2e04DOBueT0fDi2+Cczi7Oz07H
h22isWRYkgM8ofHUbBN09KQWfqCYObtcYmcV0AUezcSdxA670r8DNkEucur53eMgIoijG0MTxpWQ
e+RPKYp1i+apj4TR8Yp9Zf9qb1s0itx2i37/QBMJlSSdBcKVtEXjjEPs7HRb9ClWmk2PB9Td7vV6
W72d7h8tuhgPyv0cKBBQiXR9AJb3rjQZUCBYz6ZFCZLWVyavwIRj3fAeQRGWUHiez5HgiK0vk1vL
ew29Ikgb2YzxtYKWgRTKUoThMA5DRB1ubtbSTtbQYT3OrxbLxhUX+NGtCV95Yuw6FenCih1zGXCc
qR8ADNhBeS+DXqhVeS/dTIvrAKTMrngxbLAdKDGGJ4MpahosiuxJpcoC7WMnK1eOiTR3YxSMKc5n
9GvnOZWyPFYdFEwtHnBAnShG7i94RVSZy+KCnnBd5IHOi4HJM5Y1/N3YQ7AI8Hxd5LIp4krOku8s
nqP0UpjfiQC9T0vTCYx6wCBUHCmaz8rGU4PLwlJoGutrZViBSCRc98iaKFgUuWiI5Jni1Zonu0ci
rJNHsY9sZpjSNJ7TNA5LJiaIsrKU9cuBqhgt7rYG/Oo+YdJfq1YuRF1LgwhyMotl+GaTGRfKw7ZL
0MYGA/AESO5i34OICvA8bKnpGNEijkznz+MoLXRm6kll7syeKNwiTWa3TPAwUxrtK5Ba2p1a0hbI
QMHqgYBhWWO5ZLYF2biu6TVmNXs+zCNT3XWZ0OQR30y7sxihOdZ8Jo3UXGlGqIcoWPhCHuO7tGC7
hseLjZhznHp51Vtqq3m1G41f/cgNMqi97yZJFvm6g6aDPePAna8yAKBj4aaxas8O6sbu5mYnysJr
nHiYIT6k7ZyizyiFmqmPvopyCA+WxkIR+clBo5EpLkdOSZVwS4bxXj6otLe7y6Uc3ew1Gp137xr0
Dv0b23Xk3+ssNW2EKaWub/tNvaSzNLC+NM0i1wgFfw7xp8hwcqbLtxhMdBpuIJTFb5bZtRcIl4ZJ
cgFpdnd5OF+88d8G0fDs7OJkNLmaHI4nV+OL0eTQKbybew/mHayix3xIyy9Sq6fmx2vnR+pvbjar
JxGWV78aG95P22g/xM9aG2mMIGDm6isdrrY7RXLYFDTznc4DOT7lkizJNxRBINP90xR74MX3+7zQ
AR20aK1wNsrV4clnB3MNHEZacnffhR07EfdedkKHQj4kVwspUn439wceQIPOjEWGxL7hs5RHkSl6
9mjUE4tVY/F0LuUtz+RZxeP2sVheh9ZYmxejrxlw+ZmBm2Ri1KZ1KakvEqeJV84kMiyobxg5fMtu
Ua9F740aVNKCAc9Vg4YERnvVENBi4P3SgIVv7cx4rbhseQJ+Yl3wQPv71ZJ4ttZSo28Gztvu22Z9
cO5sNwsHC2fNZC4tPdAOqLBkGwNOja3ZM0wJHfvOskPbvTLGzZwLmk8obiUfTiw11l4ENivyVxEm
jV+IQhkCkfOb3aUW4dKn/P/IeOrYkWZteU+3dVhIXkqxRb0P3e6eWZIHFAJE6Fo8+sCV+1C/pglc
rZ95LRz/LaKMLx5Od6vXaz4MYXfykXSWZZ/CW34o+BjwPxtFei13m1qeFaU1GI8PzydXh39dDL45
BcOWka19I/Ul3pxCkbU+hkzldMyvz3uBTeXzWSxe5GFTeMnvdPodQ+zNwnYhieIrP+Sc891BXPP3
URC7Aqf9x+bTK5h8q6L/za85rp/491jW8bKsnc5SL+IBXN1xirgzJI7gyX9+AOEG12+3132/UZiZ
JZXty44xLPPSvBXiVP11CTx3OcdUSW69ggSZzykVA4x0b+0HgcWEC5W9zgJmdIN+5xjUkVSq+Sif
8tOnxrpG7sOPvbyzpG6yKIgYuviSer9hUfR29MyWQKPsei8hv5L6dRwHzhTEZEHaLxCuqIbl4/Eh
CXb/lE2nMv2n1+12fzyTkFU3auUnglMlJqhU4ZpPYbHHxDPVeXWMj/XBl0NnIz9V2HV3t1iqudGq
2kK9PrRcp8OD430pjXGMedpCfyrvHoEqP4xCod3ZE5h+K8KvTewqdEgWpCputkVw9HI3TKpeXgZ9
1NOp36fuChmq20uNvikJWxj9Wi2bAVwwT3A55n5Vns9/lBSMybXwauf3dot2usUhtY6ihYHraL8P
WvnSdu3CdXPTDK/MyMdxcPd1klRO/ftmPWCF/sWI3lSI3pSIXuS5v2H3nPat/4v9+qVj///wfA3U
g5Ljwev8KnEOXrliCfVgeZ+3tl6zz1tbK/e5HtAObpa3w+dzp/90ytiprZcHhOk6cM+nHzzflK62
zVc3vqPRv44P+c/HbzWhszBYZb4I53F6+/Hjx9zO3ENdvgfgEloRwnXMnJu96iYrIy94rh9ttJZj
eDm43rOdrNjyTeo9kvZ1a/YeCtnpWC34zySBFIm5meYnve16P2H5P1BLAwQUAAAACABdsT0uWcEc
+hcGAABeFAAAGgAVAGNjeHhfdGVzdHMvVGVzdF9EaWdlc3QuY3BwVVQJAAPxwTg+AsI4PlV4BAD0
AfkB1Vhdb+JGFH1efsUVfVhoHBISbatu0qosSxKkfFAwWuUJDfaAp2t7kGccQqv+9547NmCibNN0
s1KaB8D23DPnnvs1zsEBdfVilal5ZKnRbdLR4eHRPj6OqRuJkLotuhVWGgpW/PVrrkIR6ZYM89rB
ARF/+JEytMj0PBMJ4ecsk5KMntmlyOQJrXROgUgpk6EyNlPT3EpSlkQaHuiMEh2q2YpxcC9PQ5mR
jSRZmSWG9MxdnF+P6VymMhMxDfJprAK6VIFMjSSBrfmOiWRIU4fDFmfMYVRyoDMNYGGVTk9IKjzP
6E5mBtd0tN6jBPRIZwzSEJaZZ6QXbNcE3RXFkGBj2uJlj/m/dTMklTrwSC/gUgRMOLlUcUxTSbmR
szz2GAKL6VPfv7gZ+9S5vqVPneGwc+3fnmCxjTSeyjtZQKlkESsgw7FMpHYF/oxw1Rt2L2DS+dC/
7Pu38ILO+v51bzSis5shdWjQGfr97viyM6TBeDi4GfVaRCPJtCQD/IPGMxcm6BhKK1Rs2HM2uUVk
DdjFIUXiTiLCgVR34CYoQE49HT0GEbFO585NLN4KeUJqRqm2Hi0zhYSx+pG4sv02th7106Dl0buf
yJdQSdIgFoGkfRrlDHF8fOjRB20sL73q0OFRu93ebx8f/ujReNTZxLNj4IBZyECBsLwPpMuANYMv
e+PRAkmrjMsreMJYc44RFGEJRRgqRoIhQr9JbivvLfRKIW1aZIyyBlrGUpjCRSzs6iQBandvr5J2
ssIO+3F+eSwbV1ys0s8OfmuJe9NMZKtCbM1lwDgzFYMMvIPyYQ69UKvyXga5FdMYTrmohBprEA6U
GNOT8Qw1DS/W2ZNJk8dWIZJbU8ZEmgcaBeOK8wn9WmVOZSxPoQ4KpoIHHlAn1cj9Fe+IKgtYXLgn
ggB5YMtiYOeZyxf8D3QIsBT0lF3nsivirZwbfyO9ROllWH4nYvQ+K10ncOqBgzA6NbSMNo2nQpeF
pcQ11ufK8AgjseC6R9ak8Wqdi86RMlPCSvNk81QkVedR7P0iM1xpOstZppONJw7EFLJs6peBthge
d1tH/vE+4dLfGq8UoqqlYwQ52Ytd+i7IzAvlUbRLuI0Ag7APJndahRDRgF6IkLqOka506jp/iWOs
sLmrJ5MHUTFRuEW6zPYceJIbi/YVSyuLSO1oC2ZwodADgMmmxkrJihZU4Aau17jdivmwTF11V2VC
kwe+exxEGtCMtYykk5orzQn1kAULv5bH2e5s2KrwCbUTc4mpV1Z94drjfrVqte9UGsQ51K77KJvJ
RzXHVyuq14ranWNibeYuhDLcL02tOxiMr/v+xO+N/Mlo3Pd7k2HvvD/yhx2/f3Pd6EYy+GzypIBj
5ObJ00bDbvuH51ocHz3L4urju2etH1102s81OHq360XN8sxBfzgNYmEMlQ9XC9nl619qLpNd5ahg
a2lOHy58/94W14h8PDZiLhvN2p81Ig5VzgWS6XwebaLlmqIgWxigd8IC4597AY5YSEAECScXzn+3
E5CKH3R6SnNpr8y83YAD69stlSpbkKreLldfYlo/tLjJ7SJ3C4prfrJWsDMa9Yb+pPfbuHM5ucJx
pHPea+A5Uf1CuEPblTSO8hIF/bZOe7u74Lr+tu45i8qDyZqgx7LIe0xrTAK3qsqphRkBDF4jApuL
GCtA/K+XjlYXBWqzPOCqK6P1VdIUu9Dv3LXEzLr5g7MDJtAfrhtsBeklC7uCIq9MEEfro7DCqfFm
J4XWlL9tCm13eZBCL6UYvbBko0TEcenJI6p9+6J7tOBeYbFdimwuK0LhLfTNK+9R/0o39/etxfug
UhyB15W5la4FIiVfuLBd1Wb6mHVfLyWjOQGnDtzjfwrwKQavy/BvtdWvsvmrlHAo+zvNeDueMX+D
PHbvCOupOZUzfnPO5P6mg/Mx9rm1XeAXoyCTtIP1xOCuKFSvN08cT5yms/LonAECn1IkLzS01iT3
/2cja6BkIHGkXh+3ELdGnho1d2/l9DMdnuDrQYNpxTKd2wh6096ealbIVwqqEfDxgDZgQQT1v2/u
Apl8yo4qj9rNVjBxTvPv19LC/lOI/gZQSwMEFAAAAAgAXbE9Lkxz1MGSCgAANi0AABgAFQBjY3h4
X3Rlc3RzL1Rlc3RfRGlnZXN0LmhVVAkAA/HBOD4Cwjg+VXgEAPQB+QHtWPtv2zgS/t1/BZHDAU7j
2npLTnrFuk66NdCkQexgkTssCoqkbKKyZOiRNNvt/e03Q8q27Mhtkr5wQFrAscXhx5nhfPNQr0eG
6eI2k9NZQdrDfWIZhvUcPmwynFFOhl1yRQuRE3aLf34rJaeztCt42er1CMGPyUzmZJGl04zOCXyN
MiFInkbFDc3EEblNS8JoQjLBZV5kMiwLQWRBaMJ7aUbmKZfRLeLAszLhIiPFTJBCZPOcpJH68fvZ
JfldJCKjMTkvw1gy8lYykeSCUDgan+QzwUmocHDHa9RhXOlAXqcATAuZJkdESFjPyLXIcvhNrOUZ
FWCHpBmCtGmBmmckXeC+fVD3lsTggtXWLoo12b82kxOZKPBZugCTZoAJRt7IOCahIGUuojLuIAQI
kz9GkzfvLidkcHZF/hhcXAzOJldHIFzMUlgV10JDyfkiloAMhmU0KW5Bf0Q4PbkYvoEtg1ejt6PJ
FVhBXo8mZyfjMXn97oIMyPngYjIaXr4dXJDzy4vzd+OTLiFjgWoJBPiCjyN1TeBHLgoq4xwtxy1X
cLM5aBdzMqPXAm6YCXkNulHCIKa+fnsIQuM0mSozQXjtyCMiI5KkRYfcZBICpkgb7hX3r++2Q0YJ
63aI2ycTAV4S5DymTJDnZFwihG0bHfIqzQsUPR0QwzJN87lpG36HXI4Hq/sc5GBAvhBMgsLiIxMq
ApYa7LamQxYQtDJXcQWWINYU7wg8gi6knEtEgo1w9avgLsTHAvyVgGsTHTGyyMGXsaC5NhEEh+l8
DqjDg4Na2ImadnAexlcH3YaMi2XyQcGvd8KzMKPZrXZ2ijRAnEjGoAxYB57nJfgLuCo+ClYWNIzB
KHUrPAUZuA6gGKon4gg4DVYsoycTeRkXEm5yvRUxIcxZCoRR5PyK/7pVTGXoHu0dIEwND/QA7yQp
xP4tnggsY+hcMI8yBnFQVGRA41GXHfazlANYAurJYhnLisRrd67snaU3QL0MxK9pDLmvECoTKO+B
DjRPk5zczFaJp6YuOpbMVWJ9qBsaNKIL5D1ETRLfLmNRGVJFCq8lT9ye0HndeCD7SEeGoqbaGWXp
fGWJAsm1W1b8RaA1RgezrVK+OU+o8C/yTuWIui+VRuBOtGJTfXXJqBfQQ6dLMBsuGBSegCbXqeTg
xBzU43ClKmMkt2miMn+Fkxe0KBWf8pLNdEXBFKkiu6PA52VeQPqKRSH0TW34FjQDE7Q/AHC+4ljl
Mp2CNC5TuUadpuvDTaLYXXcTJHnAV8tslgI0Yt3MhHI1Mk05alsLdPzSPWrvxoHdmj48Vc68gapX
sV6b1mxXt9X6h0xYXIK3X7DFokxk0YOkA3eGwL03IgaFTinL0rw7e1kXZgcHPS6nQLXNhQi4J+j8
ZatV5kg0DLZ8gckW0utRq9V79qxFnuk0jJRhMc11gsIscy05NhTaYdBUQLqDZoAAuSjajvpnTEJ5
AAi8X62BBhE5BMb5FgYcntOpzmJZiTGUpeV0VtsM7gOwcRk+r1B0fgFvvZYfixJqSaUXXBMoqZWq
0FA3/VSFNRQGSDoIV+mFeSiZgg2ZUAy5EVDfaV7LExUcYmDZUrUFLlbHLzzUQMrc24UAA3Ndl0Ep
8ZyLSBWGvAyXumO8iY8Ua1wOu3Djb7SERiHbbNpgodcqqkt4oS/hWJ01gXOG+PtlSz9WlJasWlX6
HurOipHhYnEJMXN4iM8rf7U+tRaZvAbcwxYhIinn5NOr0dng4ur98WAyMN+PR/8+If8ilut9PiIE
YhdKHBAVcjSm7Q+wqYT4m6JlbEYzEsoEcvMxxID5nztAf0JMwQUVyvV44JYVlQePYCUv+OFhdSUq
SKu1d2WxKDE2SYOt7X14TMgn9am0naoUV2AjC3lUK6citBKBK2ivDICkSSQYa0DX8oLc0f6IHBzI
/Woj2bBU/gnbJPkn+umIqEK6EFQV0gUtoNtMMFBpDgkW0x9UD7zWtZqpsgoTjkrbquRAEmXYOsDD
RAieL+vwTLAP2JxNodHIC13m8QRI5FXTVeEqF6YVxxVme+/VWukuuGGvo6VkmoNoWfy9/qXN2z9a
Ogq2d1UCbbfVRT/br3sAcORfIo3atWf7m5tZnOaiXT37jMZfy6woQe3/7r5JJVeLBbjQ4mS+KG5P
8+lSBpwNoZyQvb0j0iQPouYd2YVcLNIdG95CK9u4KYzpjHyfj73KNU+YT5hPmE+YT5gP+thblpGt
/uMZ5u9akVMpfJXAa8Wpyvx6AM/xnQi2Z6tJHstS1XLq3q56QRJqET0nY02HksugbcWZRqHpgSgD
gUWqa33V1fZUX4xNKPSeaaZ6A1XsdX2ulcMd5e69Lo/t/e2Kt3Mn1rCH71pWv4fvrPl95+aWbkax
+VPTBVHzBY4FtHpFdVx10YRUyzt6YoJdMeiCk2Whu0gYsuJLdDa2Gd//hCG2vlnJcCj7MSeou0YH
Vn3S9z9hPKdxfKpD8sfY8JZmU/FDT1jH2Y/BvxAjmJMkjeVf9EF3TbDXhyvMN+ZfPQKWhRaEfAA6
qBdIU3mNzMGX6ES9Pq2oRMlCCnyDhwuFnMPo/2AbzhHhRuqO+/N6lh9X4+fyteVUt97LIbg24lbj
rcg3BubakLsamBO+OWmjV9Q7OxxV8nK+Mfl31TSrdVgKrBv/9bR6dyZ4sSn+soVz3vD8/PJsNHk/
ORlP3o8vR5OT9l1URaa6ZHs7YTRL1AnfLLEibPNynW3NEnW2NEuso715fTtam6VW8XBnWXvt/cnZ
sYrzdX7+Wh3aGo4Mo6oOX6pCW3usoHnPnRq0va/fvK+pAm1tDbSav4oSF0PT280HXL0vGdayu5mw
ifdEg59Cg8cQIaJ2+DgquA6LHk0GX7juL6aDbX2JDrZ1fzosZb9EhzreEx0eQ4f7TikNtKhR4z4T
yxYCj0zOLNt54PSyXTm41zcClz98krlTggw3YL79K+lzeuzuJA+s3ZM6K8mdxNnAeqLNT6QNd0we
MN7fg8YlMozQMhz4KvqBYfT7AX5lUeBYvng8rwwWBIYVhAAW2ZR68B++mo4teOB4+NQKhSnoNxLP
d4OAGwKPYX3450c2fKWOFTihacJXjzLT9EP3m5kpLBZ4LseTHNMD5ZX7PDuMKO0LNAiPAnf+SuqO
3wzMndzFxXuSdy26k72baCpke72vE7hB5g6FG2Q2SdwgcIfGDTJ3iNwgs0XlBolGMjfI/Tw6f0P1
M0wr8gIkiuMIbkSmhSzlNmO2bSCTTF8I5uLTgFnC527/2wjLLMaE7TAA7HvcpGEfD2fCZaEJ9RMZ
7VjU9jFbUJ+5fkS/koXuwV2nb3rcCxE+9CM/EB4mOcP2+gGjyGjb4qYbeELlDtfnEQt+MY0td/dA
p5fvT+WV8JfIvIH4ROf/SzpTy3IsQTHOXZf1HWbjVxH6LMIWF0I+jETU5y4SgVEG8igQCc8TnqrK
vuMK4dg+ZgHm2faSCI/vjB3fsF3b1MwCOrtYoLnHqQuFU5Vtz4XjUTsehGYYCJ0bQBak0RLb9wPu
WaraWq7fd+xvTwgGjSJLYAXnFg/6loXUd3waccdDVSBF9D3fQQEfMoMfuKhKyE1OAx8To/BN07A8
9FkY9R0nWL8B+h9QSwMEFAAAAAgAXbE9LkHMtAH2CwAA4zEAABoAFQBjY3h4X3Rlc3RzL1Rlc3Rf
RW5naW5lLmNwcFVUCQAD8cE4PgzCOD5VeAQA9AH5AdVabXPaSBL+7l8x5aurBQdjG+JsYuLUYYKz
VDm2i5fdym2lXIM0mImFxOrFmOTy3+/pGQlGIAnsS1x7X4zRdPd0P91PzwyjgwPW8qZzX96OQ1Zq
lVnt8LC2jz911hpzm7Wq7BMPRcCsOX38K5I2H3tVYUc7BweM0Z/+WAZs6nu3Pp8w/DvyhWCBNwpn
3BcNNvciZnGX+cKWQejLYRQKJkPGXfvA89nEs+VoTnbwLHJt4bNwLFgo/EnAvJH68uFywD4IV/jc
YdfR0JEWu5CWcAPBOKamJ8FY2Gyo7JDGOfnQi31g5x4M81B6boMJiXGf3Qs/wHdWS+aIDVaY55OR
Eg/Jc595U9Irw905cwDBQrVKYlnxL8O0mXSV8bE3RUhj2ESQM+k4bChYFIhR5FTIBITZH53+b1eD
PmtefmJ/NLvd5mX/UwPC4djDqLgX2pScTB0JywjM5244h/9k4WO72/oNKs2zzkWn/wlRsPNO/7Ld
67Hzqy5rsutmt99pDS6aXXY96F5f9dpVxnqC3BJkoADjkUoTcLRFyKUTUOSk8gmZDeCdY7MxvxfI
sCXkPXzjzEJNbc4eGeGO596qMCG8BLLB5Ii5XlhhM1+iYEIvI6+kv8xthXVcq1phx29YXwAlwa4d
bgm2z3oRmajXDyvszAtCEv3YZIe1o6Oj/aP64a8VNug1F/lsBgggmApLwmHxYAlVAYkH+dFU2BRF
KwNVV4iEbN1SjoAIQchtW5IlKCL1i+IOxUMIvFxA6+qKkWEALB3BAx0iBFveZAKrrRcvjLIThneY
j+qrQrAR4xzp3inzS008G/rcn2uwPaIB2RlJB84gOiBvR8ALXBUPwopCPnQQlMqK7UEG6QDFyD3h
jMBpRJFUjy+CyAklMrlUJZsoc8sDYRQ5N+BXjWvKJ3g0OiCMYQ9+AB3XQ+3PaUawzCJwER63LNRB
GJOBgidfcuK3PBvGXLgnw6SWFYmXcC7iHXszUM+H+D130PtCoTqBQg8+8MBzAzYbLxqP4S4Byyaq
sT4WhgyP+JR4j6pxnXlSiyqQuFJso3mSussnZvAge0dXhqKm0hz53mQRiTISaFgW/CVDSxsV6rbK
+ew+oco/DCoxECaWyiPASVGk3VdJJr9AD90uETYSDIf78OTekzZADOCejZSqjuHOPVd1/thOEPIw
UnwKImusVxRqkaqyK8r4JApCtC9HhEJnKoUtPEMIGg8YnCw4FkOmW5C2a6leo2bT68PMVew2YUKT
h301bI09mCZbs7FQUBPTFFCrXhDwCTxKNzVh1fDH9hSYM6x6Met1aNlxVXd2/iFdy4mA9m4ftLlp
u7foNdXx7s5O6/p6cNnp3/Tbvf5Nb9Dpt2+67Q+dXr/b7HeuLktalLTKjZ0dlY3lo5OTQISDaam8
822HMaoVMCKMOwhXLdgbfhFWqFtO4KEkg2gYPwxoC8DuuS89ZA/U4gxRTIQbBrBmeaT/cKVEq7KD
NnoL9E7ZcWNtFJ2gh2YAxp+y3fi/o90CuZohWMsQjFzpoleD8V+FfRk5znVIU18OLi4aKlBjmCGp
1E6CECVKZYFejokiK/RUsgOsWGjK5sLvTmkLEVDv4rTYuJiBle4BghjxuI9CUz1OitI0W4bDqLkS
yMok/DrEasnesiP6fPGCRlcDcqPJEHNWp1Ewvhly664ky5n4YGpTapfvbic33FLO2lLO3lJOkNya
IO1WeuvCX7OM5sjOHyH78AjZ2SNk7zODA4P0f7ooXTFjRMZeNMxAzJClos8fbVBZg86qP3lUWUl3
pYUEjQU1iWJNTU4SmHlZ0CREbXjMfbWVQWd2LbFOZ9PK/rsN5E7JpqkeDfUXciaT8Nm6tTVl3QQS
Tn3BOJHpC0hVo89sUqWtr1PsS2H2umK0qa2ZotmB14rDTinWVjTTMd9htI5Y7xBz/RifG2Im0+sh
3+mQUUoTfidoHx3aJye2+CtSO7q4TpMFwJje0W3MIcTxoSf/phxIlFDovWT2hhoxn5hYOnrYQhmy
cDL98/jws34STBF6OCrhYYXtqtr9p71bwXxH5QyTJuZQ0RIbAVsxkg1SAbKmqGlJaX3f+Z6xDGPp
8d9jJ1Iqs51v2QJBeO1L7DpwQAuWC7be2UyTERbOp4quKm0jxC9wpsX5cxqFTd8aQ6S0q+0urNEE
VazegFFpSS84OYHKf5bfhtLFvlv5r5Vjk/pLKWUfB3ByWA+dnGAPJP4gJ3VhqW3KdbfzsdPv/N6+
wXn5etCndLyusMOHQ53FbKFoKykIHb3SUrX6BmtbCUKuXkvkXh6/+nWD0a2FIfvqpSn7+k3zrPW+
fV5WrRwHZGxibk9oR69oofYPnKjG/Vt1UOD6F4UJf5CTaIKdmKNZiueRG8hbOo6q0zlMFPr8d/Bj
5Hi0Ea5Xj14eHb+pvTquH79+8+ubeq3++uWr2quX9VEBlrYXqbNuvnaBst6VoJ/woYUN3O1Yfrlz
Jq43/csPwuh+9jD/uoQmXtFTJV+1HC8QpUXr9GkjucJJRu2Azke0Z7bGwrpbZal0H0tS6RZyVBmM
KWoaz2BoFx5nErRzmfAzC0A9GhUPK6IVaxeNK0oVqxeNq+ouVi8aV1WZP6zrLn9cl5ZG1kzBsmLQ
7LO7fZfPzlRK42avzgpJhem27/MZ02lXp6+t2v7C7LO2/UUboCi02bNoNBL+n2edy2b3083Z4Py8
3b3pdf7d/rzY1SxPRutSxkkpZU9+hpY0OBqflRViMaAl1cKYqtu9ckofYOBM6I1K5sOygmAz5Y1c
PI3uxcn5GXTPTUwtLzPGNFWKOsE0C81aJpw1jWc2Hx6Z++Tnj2av1+72S2ulcLoSlPysOZdJuV7/
4ndB5/N8ykFke64t7D0r15TNezXvW9Uc31Eg2pFG5vgem3YSifhAui6UwUrEd9O6uuw3O5ermdE7
/8W8a79bMGPK/Xero99X6cvevk0HsTq4tzS3HVcpkUaQT+NrcYJ/Bl+LkltboSd7tzq4wha5TPqp
IZk3k1kmtcI6WXHCSE6WG3tm9Z2mpBVe8W+jKSNF/WNNvpDx7+lsW0x44wz8GO4ry89PfeWoURzK
jUbWqE6oGjfTaYo8kfXKZg7p1dj2nF+4n0n5ldGtGK8z+VTC52f1p/E9M6M5bF+OrZM9zvTpUi5n
EqMwakWVkcXzXAf2jGI7NWVXSZ5Y2JLjcQkUUPwjn25B8AmfPoresPr85IaTb+MfGZb1AE8auQI6
lxAxE7km9USew2xVuoHww5KyO+XSTxsuSfz34uiwbHQAaO2/20rtqFzYG+LAMztDamyrvkAF8NSu
kFcMP60n5BVCTltIRtabgqqM00SmaIZFJdU2llJWY8hxYW9RnqdLudWWoHW3bAgq83ntoGX+Zrv6
O+oZD4QeYWMpfI555lu1g5TV5+sK66Wf+kl6Y/0PknsfusNEQuPLXn1NGfnxSxbqZzzzwlSL7Zi/
7++xyRyTmtesdIdAt/ZLTX0vJXx6uYmmS25RXUswoUNQV6x0WXUXX8Jzh0g6x6fjWTwUtppyIyU3
J0S6cUd6MhV1D0wVegKCMZgF/SoJbj62e73mh3Zpd2BcLSvwI3cR+QI+MOXKl5iTOwhpb4n8yv1g
7GPeXG58Lw6UKWMwlViiy7D4zlxnc4OlzOv2LLPZ9/KLOdQkS+mi27/WmLu3wCTjCjHfT9Ogea8W
vwTHnRmfBwz7Ce6kLkprhnAqnnwPT3OkaqbYBlg3uOt6s9jXX7LR+GVrX/Pg/N8cDEJi8zPD+f2x
vU3fcqMoiWKWw4NAvdNCr4ClWpz2oBPfiTf+/n0o7eqPaEbx6y3LV1mMlwRWulLKgx/UmRJz1cd1
p8EW3WlhekOHenR9sakv9s3FM2niuvjyl9Jm0vbTb4n8H9Sd6fmPqz3CcW0pXCx/abR+SLWZJn/G
gpi2v0Xd5W1pPyIl7eSdwWd4N2DDmeap51t1elDvI9101L+nxp002Q/9+YIoq/vepZpOzMFBkprz
ZueitNvitK/0ki0nS1o/jLAYiXjRCsc+1lX1BmQM6W6MP2NIlzUuJf4vMIeoOhXTxEVlIR6qtyLU
i1WpXEFAkVg932ZcEP4XUEsDBBQAAAAIAF2xPS748gSoaQYAALUQAAAYABUAY2N4eF90ZXN0cy9U
ZXN0X0VuZ2luZS5oVVQJAAPxwTg+DMI4PlV4BAD0AfkBnVfbbhs3EH3XVwzih9qOIvmComicBJEV
OREQy4IuCVwUMCgu5WW7Wm5JrmWh6L/3DKnLypHjOC+2peGcOXPmQrrZpLYpFlbfpp722wd0cnR0
8go/TqmdioTaDboWXjmSC/71vtSJSE1DJWWt2STiH6NUOyqsubViRvhzapUiZ6Z+Lqw6o4UpSYqc
rEq081ZPSq9IexJ50jSWZibR0wXj4LsyT5Qlnyryys4cmWn48LE3po8qV1Zk1C8nmZb0WUuVO0UC
ofkbl6qEJgGHPS6Yw3DJgS4MgIXXJj8jpWG3dKesw2c6WcVYAtbJWAbZF56ZWzIF+x2A7oIySLB2
bfCxXflv0kxI5wE8NQVSSoGJJOc6y2iiqHRqWmZ1hsBh+todfboaj6jVu6avrcGg1Rtdn+GwTw2s
6k5FKD0rMg1kJGZF7hfgzwiXnUH7E1xa593P3dE1sqCL7qjXGQ7p4mpALeq3BqNue/y5NaD+eNC/
GnYaREPFtBQDfEfjaSgTdEyUFzpznDm7XKOyDuyyhFJxp1BhqfQduAmS6Kmnq8cgIjP5bUgThzdC
npGeUm58neZWo2G82VFX9t/Utk7dXDbq9OvvNFJQSVE/E1LRKxqWDHF6elSnc+M8H71s0dHJ8fHx
q+PTo9/qNB621vVsOSTgCiU1CKt7qUIHrBg8nk2dCjStdqGvkAlj3XKNoAhLKJJEMxIcUfp1c3t1
76FXDmnz2DHaO2iZKeFiijjYNrMZUNsvX1baTlXYIR73V51l44nLdP53gN944ruJFXYRxTY8Bowz
1RnIIDson5TQC7Oq7pUsvZhkSCpUJTE4g3JgxJieyqaYaWSx6h6rXJl5jUpuXBkTbS4NBiYM5xP6
NZY9ZVmeqA4GpoIHHlAnN+j9BUfElEkWF+kJKdEHfjkMnDxzeSR/aRKA5aCn/aqXwxBv5Fznm5o5
Rs/i+J3IsPu8CpsgqAcOwpnc0TxdL54KXRaWZmGxPleGHYxEwXOPrsmzxaoXQyLLTkkqy5PdczGr
Jo9h78bOCKMZPKfWzNaZBBAXZVnPLwNtMOq8bQP53XsitL939aUQVS0DI8jJWWzTD0VmXhiPuC6R
NgoMwiMwuTM6gYgO9BKUNGyMfGHysPmXOM4LX4Z5cqVM443CKzJ0dj2Az0rnsb4y5VWs1Ja2YIYU
oh4AnK1nbClZXEERV4ZdE6LF+2Geh+muyoQlD/xglqkBNGPNUxWk5kkLQj1kwcKv5Am+WwEbFT6J
CWLOcestpz6mtjuvRq22p3OZlVD7jSyKMte+iaWDmjFw85PKQOhSSGtcI31XPSxfvmwWfN05v2V5
MRS8YK8mfykJy4uKzxRjqcTsXa1WOp5B7kNX8B7G5j0DlURNsejovNtrDa5vzscXF53BzbD7R4eO
j46O1vbh6PNN+woXWre3ZWcZXFkUxnqaBc6sl0R/hN7Jb10oB94qYR2hTIXVUBsXE/lFEVuRrY4m
6P2KFQ8SKgwGYFmkB24rYqPOcHTTH3Qvu6Pul84Nruz+eLTPZ+qEHVGqA/qzRsEpxLnZ2wt/v43W
s7X1sGre2ytwIlfzYNqPQPEsrv+i9J38lqO/eVP12n3gcBu3IvoD7t3eivoDzidb+BuyJzvZxlM6
35B4924HTLvfH/e6o5vWcNgZIGxVm7db5w92Ih4+YPAjqA99lsircdkFWLFtadg8PKzRIZ4W2CQX
+t6XNtxwPG1W6ngVVm+bfpwblaP1VUgC7ozwXpR409nt9zUMzZrMhHMUMw5xXsfHraR2UYwxtq9f
89fL6LV/K+mHyg7H3VFnf+N/cPbgRJCnv2pst9s+EPNzneOi3G3GYH7B1Bv7qPmD+oeb9xHrpSh2
26Addsp9XCrhSLP5zaFL3Bmd1YL7NoEowU2n92Efthpm+A7qvsapoKeshmB7UJfN4Z5xyo+L/QAa
Pnsl7Acs+IAFOtwBtOoBKZZPY4Hn/HIj4dLhtSEqa4MdotcjdSeu/DpgtTxPhCUr5rhfSjz0sOUm
oWSEF4p4fsx1yZ/OFGsWRaTYAs+PtO6eH44UuumnAgXPJ+LEGOjJn4oAvx/IY9V2FPuOUo3Xk5Up
qqVs+IcpvDzO4RRPPJ/L1ux8n1LcRfy4qDzSIiThxpZxkRXfbK/Nm1hIXyIxfshaM/8GZKH4vzbF
//T/4gO7EJff2s/Oa3vcObH/kNv/UEsDBBQAAAAIAF2xPS5+IqMsCAEAALUBAAAcABUAY2N4eF90
ZXN0cy9UZXN0X1NIQVR1bWJsZXIuaFVUCQAD8cE4PvHBOD5VeAQA9AH5AW2OQWsCMRCF7/kVAz10
RejS9raKUKxFDxXB9SzZ2XENzSYhM2mF4n9v1IsWj++9b+a9sgTU7lGgIwHZGwbx8OPjFzSEOjFl
k2A9f6tT31iKkAnnBTQiMetswS76/ky11qoH49CmlmCMISRnpKSDkGPjHZdzsoHip8bo+Wk/uYZx
OCzRu53p7gSt6YjlNtixRNL9RKnExnXgdE8cNBJ4lpFSaDXz1fA6f4AKQmqsQZiGsMnjqupkf5iD
pEjqVwFMV6vNclFv69m63q43i3pW3P4YjP5RhdxzL7fb2fK9yFmIXgiF2kpdBlQZ//amhdNxMcjq
VA5Xe8fJOHl9mYBcdPF87jiq40j9AVBLAwQUAAAACABdsT0uoWQZo+MDAAAzCAAAHQAVAGNjeHhf
dGVzdHMvdGVzdF91cmxzdHJpbmcuY3BwVVQJAAPxwTg+8cE4PlV4BAD0AfkBlVVdb9s4EHz3r1j0
XhJUcb5wOBR5OdVwUgGpY1gyijwFtLSOiJNIg6Ts+N/fLOWvHNIW9+LEMnc4M7uzurykkV1tnX6t
A52Nzunm6urmAh+3NKpVRaMhPavAnsqt/Pm705Wq7ZCrbnB5SSQfRa09rZx9daol/Lt0zOTtMmyU
4zva2o5KZchxpX1wetEFJh1ImerSOmptpZdbwcGzzlTsKNRMgV3ryS7jl4fJnB7YsFMNTbtFo0t6
1CUbz6RwtTzxNVe0iDhScS8c8h0HurcAVkFbc0es8bujNTuP73Szv2MHmJB1AnKmgjB3ZFdSdw66
W2pgwaF0KMc+0n+UWZE2Eby2K0iqgQmRG900tGDqPC+7JhEIHKYfWfHtaV5QOnmmH+lslk6K5zsc
DrXFr7zmHkq3q0YDGcKcMmEL/oLwfTwbfUNJ+jV7zIpnqKD7rJiM85zun2aU0jSdFdlo/pjOaDqf
TZ/y8ZAoZ6HFAvALj5exTfCx4qB040W5lDyjsx7smopqtWZ0uGS9BjdFJWbq990TENVY8xpl4vDR
yDvSSzI2JLRxGgMT7Ad9lfpjbxPKTDlM6M8vVDBcYpo2qmS6oLwTiNvbq4S+Wh/k6PeUrm6ur68v
rm+v/kponqeHfqYeAvyKSw3C/FZynIA9g5+rSWiFodU+zhWUCNar9AiOiIWqqrQgoRCtPwx34LcA
vwysNf3E6ODhZcPK9xJxcGTbFqijz59Pxo5P2OE+ma9EbJPENdr8E+GPlXi2cMpte7OtxEBwlroB
GaiD81UHv5BVfuOyC2rRQFTsSmVxBu1AxIQeN0tkGir20+PYd03Q6OSxVDAx5qVFYGI4f+PfcDdT
Tuzp3UFgTvDAA+4Yi9nfyo1IWSnmQp4qS8xB2IVBxAuXn+gvbQUwA3o67Gc5hvho50FvbTeInsPx
tWqw+wLHTRDdAwflrfG0qQ+L54SuGEttXKz/14YPGKmV5B5TY5rtfhajkN2kVCfLU8qNak/FI+xZ
PxkxmrFy6Wx7UBJBfG/LIb8CdMRIZNtG8h/viTj+wSc7I069jIxgp6h4Tz82WXghHv26hGw0GIQL
MFlbXcFED3oVWho3htlaEzf/DscHFbqYJ9+Vdf9GkRUZJzuJ4G3nA9ZXw4H7Tr3zFswgofcDgO0h
YzvL+hXU45Zx18Tb+vfDxsR0n9qEJQ/8+HNZW0AL1qbmaLUkLRr1XxZi/N6eWPvuwuEJn8pGMzd4
6+1S30v7WNdwMPhDm7Lp4PYnvMPDS+caCY95HdafBoPRdDqfZMVLMc6Ll3yeFeOX2fghy4tZWmRP
k7P57DGPpwvUnt8N/gVQSwMEFAAAAAgAXbE9Lqn+UeQtCwAA3yYAABsAFQBjY3h4X3Rlc3RzL3Rl
c3RfdXJsc3RyaW5nLmhVVAkAA/HBOD7xwTg+VXgEAPQB+QHtWWt72kYW/s6vmLqrDcQYhDB2bJpu
gXANEBtxMSRpdiQNaGzdqgsYd7O/fc+MBAhbdup9um2zTz74gjTnnfe85zIzTD6ParazdulC91G6
lkGSKEpH8KuIajrWUC2HptgnHlLX7M9PAdWwbueIFqTyeYTYr6FOPeS49sLFJoJ/5y4hyLPn/gq7
pIzWdoBUbCGXaNTzXaoEPkHUR9jS8raLTFuj8zXDgWeBpREX+TpBPnFND9lz/qHZH6EmsYiLDXQR
KAZVUZeqxPIIwjA1e+LpREMKx2EWDcZBjjighg3A2Ke2VUaEwnsXLYnrwWckbeaIALPIdhlIGvuM
uYtsh9llgO4aGSDB1jTHhiX5v3NTQ9Ti4LrtgEs6YIKTK2oYSCEo8Mg8MLIMAgajSXvYejcaokp/
iiaVwaDSH07LMNjXbXhLliSEoqZjUEAGx1xs+WvgzxB69UGtBSaVarvbHk7BC9RoD/t1WUaNdwNU
QReVwbBdG3UrA3QxGly8k+s5hGTCaBEG8ITGcx4m0FEjPqaGxzxnJlOIrAfsDA3peEkgwiqhS+CG
kQo59eXoMRBs2NaCuwmDd0KWEZ0jy/azaOVSSBjfTogrs9/FNovalprLotIZGhJQiaALA6sEHSE5
YBDFophFVdvz2dBeBYlSoVA4KhTF0ywayZVtPCseOOA5RKVAmNyqhGfAhsHj3mSRA0lLPZ5X4AnD
WrAYgSJMQqxplCGBIYR+m9w+ufVBLwuktcKMob4HWhoEe6GLMLBmmyag1g4PY2lHYuxgPpZfWSYb
qziDWjccfmcJzxQXu+tQbJuVAcOZUwPIgHegvBaAXlCr5JaogY8VA5ziUdFsGAPhgBJj9Igxh5oG
LzbZ4xIvMHwKkdyZMkxIc9WGguHF+QX9clFOuUyeUB0omBge8AB1LBtyf81mhCpTmbjgHlZVyAM/
KgbmPOPyiP+qrQGYBfSov8llXsQ7Obf+6vYKSs+F4UtsQO/zCe8EXD3ggD3b8tBK3zaeGF0mLDJ5
Y32uDAmMsMPqHrLGMtabXOSORJmixZonM7ewGXceir0dZgYvTW45d21z6wkH8UJZtvXLgHYYWdZt
OfnkPsHT3/eykRBxLTkjkJN5sU+fB5nxgvII2yW4DQEGwkNgsrSpBiJ6QE+DkPKOYa1ti3f+CMfz
sR/wevICVQ9XFNYieWZnObgZeD60L4P4JIzUnrbADFwI9QBAc1tjkWRhCwpxVd5r+Gzh+rCyeHXH
ZYImD/j8tarbAM2wVjrhUrNK40LdZ8GE38jDbfcmzMX4aDYXcwWrXlT1oWvJfuVSqe+ppRoBqP2D
6jiBRf08NB2IGQPOt4gBhHpYdW0vp/8YG0yhWUKOm/Fnqnp4mA9cg1WftWDjU4HHio0lnOewhgtW
5eih52vn5+HQciqVf/kyhV5Cd4ZgNOitH7i8STDCrkrDbhIv2O00aB5YKpcB7BnETziAddHd36PA
i3xKNbDnodGgK3NLPtd5uEdQUc1xRuD9+Tl7HDFI/ZpCqHZxMeq3h5+GdXn4SR61h/X0HkSmfG9Q
Gubzq9SCflKFwjk5rlssnd8Q9jt5dIg2DncPyUOGawfibYxc48tw0dghRPI3M2CbB/IcCwgGWNw+
x+SCrXPW4oK4c6I+Ilw0piBDDJ8eIiUPCWP0qd5/k4Z3KcelS8iAcxiVh/zgHQHCDasqRF/VMevf
TuBDtrhe4f1H9Bod/LMgFY9LJ6evzsSj1x8+XE7qg+F01H538f5jRX7TaLY6b7vlF7Or2rja72Vz
+X9/99P3fxN+/vvLdObT4b9+WRHXXwfUdn79jD1tvtCvb4zzDwd3t+pSscwffvzHQfk+D3ILewpY
r94F/o5LQRRFzmf6pr7u3V0W+tfq8bthxb8Y3w7G4lgeN4yxPDq7nBQK1ZE4aA5E/a0srk47BWd6
WZjVhjei16Vnh+1R5bpTG5MOte2341fuvNUozq46IrkaO0qxejqfNO5mzZmFm46rvLEpsfRrzewE
ynB1eLF6/foh33u6SaFufFmibIvEopR7xCzBV2nn67ipO+q6yn70dmtgqMXLgANB/aIQAKt+gKMq
0Lh9aF5G0AajTSesqsSyg4XOG3C4l/J8bx8iTNXnQqTChsESiq9AjxdnOgNjWAtB9wX7A/MMPap6
SEI4EXc0BEkTippQUndchJIilLQtH6GoCNJpxEmQ1FxeOCWCVBCOwbgoSMeCVBJK8OREkLAgvRKk
M6E0FyRFOFV3jIVT+KxtWQtFGCpFxIWiKhSJUJwDfc4/2Kia3gmYTciCLPLoHbHn6YevMplQik2f
qMgy+PepfjmqdD/14CRUadbTB2EXZssOTAnB55uQFfbO0YsDdIjC9SZGIrN7ePDiIJPdfEjQevcy
mdzG0Shxkpx7mLP/hVMaSXYqgdUjzsXcv+fTHjXO7XMqXiSPLYmxMglg37FgRx2eswo3eIN9/F4q
nXyMZ3NItLobEIV+Z5J5eRxZ7IOGCjxtGhnChhfRKDbQA9IU6kWE0yf6AT20KaPDQ5rhY1GcOWVV
tkFRNp7HLLMJYNmHHm6HPXizSW5Gl42B+WCeSNsEnAcKbKEfvNmm5vPcp/FXTIHvXifoTj9uxv8a
/U3O5X2sBP4MqbyFUGBberP5+DmVUCJp3w1IQoLu7cJiWZlIalMbiQsWBHAX6s3I+8tj5qmu9LhV
Nhbdp0kkFeGTW8O/+oL1V9oR3avnP2xpUnjU/oTVaZd1/5PVKfLrz1ygnjoDxUsjaQv8+A4YfWHz
+8W9771MS4dw+6vay0w8AcFrg1j7SvzfJeWjS16Sp+n7cj3MiHtyPEwWlHRsYDYseC8+iC++uoTf
P4//thTHGCuKAgvBn5uZX13kow3J75YA6AA+bjc9BwfZ6P+kpEDsWLspsf1xiS6z4eGLx1Im/Hrm
eRnzLWG+/lYhPT/u38L+FYf9yS95f1MabPoe3xqZthYYhF0nLqlGvN139/y7/nD3gC0tcvmDdbCx
DklHd1Dsu7hqbMfBbxPYpSy/2qEWGjRqSBKPS+goBtFr9+oo3WN3kU7gOrZHUNvyiWsRH/UwNVB9
e++RyfEr1HCOGMR2NnbtSaJ0AUIucVziEUg17CrU5zeJHvklgPH8MjcGYUML9vllJWaHajO85LII
APE7VIL0wMTsIg+OsRq7LMyhSsz+pHTEVIboERd5geIB+/T7ytEMH92JR2eH+dcfM+wCaiQfVeRa
u82oBh7RsntuAC5z4wQp7EI5vIzdOgFUHAB3QPHwtnI74TM3tJv5on2tr0iDgtIcLdRWZ6mZxs3s
qreYWeNgWhw4ilS6gz3vst2Ez9LZzUyu6op5uZg1x9dgZ9SsvqiaRrB1YlbsLfCkJCrrqogB9NKE
I9twKm4A4J3VbvVXs0nfmZmGMatVHYVW5cFNb9G7roh9ueLXbgqd4Wi02IK+rRcKSmvgqK3xWm2e
3QGLjmLBTtwsGVqt2p9ODK9dHx9rMIkqGXBs7TldWh3FCdTMkMAWlDNpGnftJgBJhqWY4xvuaqtj
qOxHGgcArqtmx9FaHV21bhbw7FabMKAx2J2ZNfPsGiYVt6DsnADu6O3mbKma4kJr6jqABLMJgDdL
S/ifAntbmxRAx9sSm2w6GehT89YAxtXa9bTQnfTt6VVH34JCIAyVVu+0SedudnW5eNvwq92xo3ev
7FV3eON27wraW7m6nNHqeLRmR+x+R5b5gaUAjG+6FcdQzAZVmvFArStSu8lc6wHLV4upCRlgjlfw
czeDAM4mlwu1OV63W9U1C+h00vGA+TVuNtbTSV+cXbW/nYK+nYJ+3zXuczn1H1BLAQIXAwoAAAAA
AIyxPS4AAAAAAAAAAAAAAAALAA0AAAAAAAAAEADtQQAAAABjY3h4X3Rlc3RzL1VUBQADR8I4PlV4
AABQSwECFwMUAAAACABdsT0u9XJv+AkGAACKDAAAGQANAAAAAAABAAAApIE+AAAAY2N4eF90ZXN0
cy9jY3h4X3Rlc3RzLmNwcFVUBQAD8cE4PlV4AABQSwECFwMUAAAACABdsT0uVzavh7IOAACwLQAA
EwANAAAAAAABAAAApIGTBgAAY2N4eF90ZXN0cy9NYWtlZmlsZVVUBQAD8cE4PlV4AABQSwECFwMU
AAAACABdsT0uqBGv9lECAABqBAAAFgANAAAAAAABAAAApIGLFQAAY2N4eF90ZXN0cy9NYWtlZmls
ZS5hbVVUBQAD8cE4PlV4AABQSwECFwMUAAAACABdsT0uBaaAUokOAADXLgAAFgANAAAAAAABAAAA
pIElGAAAY2N4eF90ZXN0cy9NYWtlZmlsZS5pblVUBQAD8cE4PlV4AABQSwECFwMUAAAACABdsT0u
5YRH6KYGAAAuEgAAGwANAAAAAAABAAAApIH3JgAAY2N4eF90ZXN0cy9TYW1wbGVPYmplY3QuY3Bw
VVQFAAPxwTg+VXgAAFBLAQIXAxQAAAAIAF2xPS79xAmolQUAAHcMAAAZAA0AAAAAAAEAAACkgest
AABjY3h4X3Rlc3RzL1NhbXBsZU9iamVjdC5oVVQFAAPxwTg+VXgAAFBLAQIXAxQAAAAIAF2xPS4W
rxVOQQUAAHMMAAAeAA0AAAAAAAEAAACkgcwzAABjY3h4X3Rlc3RzL1NhbXBsZVN1Yk9iamVjdC5j
cHBVVAUAA/HBOD5VeAAAUEsBAhcDFAAAAAgAXbE9LqthxYr9BAAAzQoAABwADQAAAAAAAQAAAKSB
XjkAAGNjeHhfdGVzdHMvU2FtcGxlU3ViT2JqZWN0LmhVVAUAA/HBOD5VeAAAUEsBAhcDFAAAAAgA
XbE9Lt0kO1jcAwAAKQgAABgADQAAAAAAAQAAAKSBqj4AAGNjeHhfdGVzdHMvVGVzdF9EYXRlLmNw
cFVUBQAD8cE4PlV4AABQSwECFwMUAAAACABdsT0uZfnwmIkIAADPFwAAFgANAAAAAAABAAAApIHR
QgAAY2N4eF90ZXN0cy9UZXN0X0RhdGUuaFVUBQAD8cE4PlV4AABQSwECFwMUAAAACABdsT0uWcEc
+hcGAABeFAAAGgANAAAAAAABAAAApIGjSwAAY2N4eF90ZXN0cy9UZXN0X0RpZ2VzdC5jcHBVVAUA
A/HBOD5VeAAAUEsBAhcDFAAAAAgAXbE9Lkxz1MGSCgAANi0AABgADQAAAAAAAQAAAKSBB1IAAGNj
eHhfdGVzdHMvVGVzdF9EaWdlc3QuaFVUBQAD8cE4PlV4AABQSwECFwMUAAAACABdsT0uQcy0AfYL
AADjMQAAGgANAAAAAAABAAAApIHkXAAAY2N4eF90ZXN0cy9UZXN0X0VuZ2luZS5jcHBVVAUAA/HB
OD5VeAAAUEsBAhcDFAAAAAgAXbE9LvjyBKhpBgAAtRAAABgADQAAAAAAAQAAAKSBJ2kAAGNjeHhf
dGVzdHMvVGVzdF9FbmdpbmUuaFVUBQAD8cE4PlV4AABQSwECFwMUAAAACABdsT0ufiKjLAgBAAC1
AQAAHAANAAAAAAABAAAApIHbbwAAY2N4eF90ZXN0cy9UZXN0X1NIQVR1bWJsZXIuaFVUBQAD8cE4
PlV4AABQSwECFwMUAAAACABdsT0uoWQZo+MDAAAzCAAAHQANAAAAAAABAAAApIEycQAAY2N4eF90
ZXN0cy90ZXN0X3VybHN0cmluZy5jcHBVVAUAA/HBOD5VeAAAUEsBAhcDFAAAAAgAXbE9Lqn+UeQt
CwAA3yYAABsADQAAAAAAAQAAAKSBZXUAAGNjeHhfdGVzdHMvdGVzdF91cmxzdHJpbmcuaFVUBQAD
8cE4PlV4AABQSwUGAAAAABIAEgDdBQAA4IAAAAAA

--Boundary_(ID_OItGkMNEphWhF9WGQO+MBQ)
Content-type: application/octet-stream; name=ccxx_tests_patch.diff
Content-transfer-encoding: quoted-printable
Content-disposition: attachment; filename=ccxx_tests_patch.diff

Index: Makefile.am
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/commoncpp/commoncpp2/Makefile.am,v
retrieving revision 1.16
diff -u -r1.16 Makefile.am
--- Makefile.am	17 Jan 2003 11:07:17 -0000	1.16
+++ Makefile.am	30 Jan 2003 05:55:19 -0000
@@ -26,14 +26,18 @@
 	config/ltconfig config/ltmain.sh config/missing config/mkinstalldirs \
 	pkginfo CommonC++.spec INSTALL
=20
-DIST_SUBDIRS =3D src win32 m4 doc demo template tests include ssl
+DIST_SUBDIRS =3D src win32 m4 doc demo template tests include ssl =
ccxx_tests
 if WIN32
 SUBDIRS =3D include win32 template @SSL@ doc
 else
 if MSWIN32
 SUBDIRS =3D include win32 template @SSL@ doc
 else
+if HAVE_CPPUNIT
 SUBDIRS =3D include src template @SSL@ doc
+else
+SUBDIRS =3D include src template @SSL@ doc
+endif
 endif
 endif
=20
Index: configure.in
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/commoncpp/commoncpp2/configure.in,v
retrieving revision 1.32
diff -u -r1.32 configure.in
--- configure.in	17 Jan 2003 07:56:45 -0000	1.32
+++ configure.in	30 Jan 2003 05:55:19 -0000
@@ -26,9 +26,9 @@
 	else
 		bprefix=3D/usr/local
 	fi
-	if test -d $bprefix/include ; then
-		CXXFLAGS=3D"$CXXFLAGS -I$bprefix/include"
-	fi
+#	if test -d $bprefix/include ; then
+#		CXXFLAGS=3D"$CXXFLAGS -I$bprefix/include"
+#	fi
 	if test -d $bprefix/lib ; then
 		LIBS=3D"$LIBS -L$bprefix/lib"
 	fi
@@ -92,6 +92,8 @@
 AC_LANG_CPLUSPLUS
 AC_CHECK_HEADERS(sstream)
 AC_LANG_RESTORE
+AM_PATH_CPPUNIT(1.8.0)
+AM_CONDITIONAL(HAVE_CPPUNIT, test "&CPPUNIT_LIBS")
=20
 AC_DEFINE(CCXX_CONFIG_H_)
 OST_DEBUG
@@ -136,7 +138,7 @@
=20
 AC_OUTPUT(src/ccgnu2-config src/Makefile win32/Makefile ssl/Makefile =
m4/Makefile
 doc/Makefile demo/Makefile include/Makefile include/cc++/Makefile =
Makefile template/Makefile freebsd/pkg-plist
-pkginfo commoncpp2.spec freebsd/Makefile win32/CCXX2.rc tests/Makefile
+pkginfo commoncpp2.spec freebsd/Makefile win32/CCXX2.rc tests/Makefile =
ccxx_tests/Makefile
 commoncpp2.proto)
=20
 if test -f doc/html/index.html ; then

--Boundary_(ID_OItGkMNEphWhF9WGQO+MBQ)--



From MAILER-DAEMON Thu Jan 30 05:25:40 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eBt5-00020Y-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 05:25:39 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eBt2-0001zE-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 05:25:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eBt0-0001yO-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 05:25:35 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18eBsz-0001tD-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 05:25:34 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18eBu4-0000yv-00; Thu, 30 Jan 2003 11:26:40 +0100
Date: Thu, 30 Jan 2003 11:26:40 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ari Johnson <ariston@cs.und.edu>
Message-ID: <20030130102640.GA269@bulbasaur.rediris.es>
Mail-Followup-To: Ari Johnson <ariston@cs.und.edu>, bug-commoncpp@gnu.org
References: <Pine.GSO.4.10.10301291908340.13023-100000@agassiz.cs.und.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.10.10301291908340.13023-100000@agassiz.cs.und.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: URLStream Example
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: Thu, 30 Jan 2003 10:25:37 -0000


	Have you taken a look at the urlfetch demo?

On Wed, Jan 29, 2003 at 07:12:35PM -0600, Ari Johnson wrote:
> 
> Does anyone have a (preferably working) example of URLStream in use?  I
> need to use it to download a file via either HTTP or FTP (haven't decided
> which I'm using just yet) and then I'll be dlopen()ing that file.
> However, the documentation for URLStream is entirely incomplete, and if
> someone has samples of code that properly uses it then it'd save me a
> great deal of decoding.
> 
> Ari Johnson
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Thu Jan 30 05:47:40 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eCEN-0001Jg-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 05:47:39 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eCEL-0001Fb-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 05:47:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eCEJ-0001FC-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 05:47:36 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18eCEI-0001F5-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 05:47:34 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18eCFS-0000zl-00; Thu, 30 Jan 2003 11:48:46 +0100
Date: Thu, 30 Jan 2003 11:48:45 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030130104845.GB269@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>,
	bug-commoncpp <bug-commoncpp@gnu.org>,
	albert@dogbert.sdsl.sun.ac.za
References: <NBBBJJODBJBNJFNIDDCNKEHJDEAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNKEHJDEAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: albert@dogbert.sdsl.sun.ac.za
cc: bug-commoncpp <bug-commoncpp@gnu.org>
Subject: Re: common C++ test suite
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: Thu, 30 Jan 2003 10:47:37 -0000


	Hi,...

On Wed, Jan 29, 2003 at 10:41:34PM -0800, Chad Yates wrote:
> Common C++ community,
> 
> As some of you may remember, I wrote some test suites in cppunit last month
> and I would like to submit them as the beginnings of a common C++ test suite
> as we had discussed then.  however it has a couple of issues I am hoping a
> more experienced common c++ developer or maintainer can help with, as I am a
> gnu autoconfig/automake newbie, I'll admit it. :)  also since I typically
> develop using m$ visual studio 6.0 I'm not that proficient with
> developing/debugging on the linux environment.
> 
> My date classes have some tests that are failing now with the recent patches
> submitted that add the new YYYY/MM/DD style formats instead of the YYYYMMDD
> formats.  whether the interface is changing or whether the tests need to be
> updated to the new format needs to be determined.
> 

	I would expect Marcelo's opinion, though I think that we
should keep backwards compatibility.

> My persistence tests (pretty extensive), work fine under windows, but throw
> exceptions under linux.  I don't yet know why, and since I haven't come to
> grips with a linux debugger yet (I've been babied by VC++'s gui debugger), I
> can't dig into the reason yet.  I have another test case under windows, but
> am not going to add it at this time as it has some linux compilation issues.
> 
> There are generalized test classes for the digest tests, however I could
> never seem to get decent results out of the SHA digests on windows, they may
> work fine under linux, though the testcase registration macros are commented
> out right now.
> 
> There are also tests for the urlstring file including base64 encode decode.
> 
> I have attached a zip file containing a zipped directory called ccxx_tests
> designed to be uncompressed under the commoncpp2 main directory.  eventually
> I would hope the contents would live in tests instead, and all the existing
> tests changed to components of the cppunit test suites, or something
> similar.
> 

	Um, I would like the new tests to go directly into tests/, and
integrate the old tests as soon as possible. Since there seems to be a
few issues to solve, I would put the new tests there now for the
development branch, and, when these issues are clarified, commit the
new test suite for the stable releases. This would be a very
interesting new feature for 1.0.9. It would also be interesting to
include the VC++ project files for the test suite.

	Do you agree with this plan?

> I have also attached a diff of the changes I made to the configure.in and
> Makefile.am to get it to build for me on my linux machine, however, I didn't
> get the check for cppunit to work to my liking, and am sure the changes I
> made were not ideal.  hopefully someone with more expertise in
> autoconf/automake can make better changes there.
> 
> Anyway, I wanted to get this out there and in cvs so others can contribute
> if wanted, and so we would have somewhat of a base to start/learn from.
> Also, it would be a good habit for contributors to get the hang of adding
> suites/testcases while finding/resolving bugs and making enhancements. This
> way some inadvertant sideffects can hopefully be avoided.
> 

	I totally agree.

> Cheers,
> 
> chad
> 
> P.S. I spoke with albert today, and he will be contributing his testcases
> etc a bit later.  Feel free to contact me if you have questions,
> comments/suggestions, or if you have trouble compiling it.  I will
> contribute new suites/testcases as I develop them.



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




From MAILER-DAEMON Thu Jan 30 06:32:22 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eCvd-0006IU-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 06:32:21 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eCtK-0005IM-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 06:29:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eCtC-00055g-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 06:29:52 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18eCsZ-0004MB-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 06:29:11 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18eCtk-00011E-00; Thu, 30 Jan 2003 12:30:24 +0100
Date: Thu, 30 Jan 2003 12:30:24 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Yates <cyates@uidaho.edu>
Message-ID: <20030130113024.GA3841@bulbasaur.rediris.es>
Mail-Followup-To: Chad Yates <cyates@uidaho.edu>,
	Federico Montesino Pouzols <fedemp@altern.org>,
	bug-commoncpp@gnu.org
References: <20030109105348.GG313@bulbasaur.rediris.es>
	<NBBBJJODBJBNJFNIDDCNAEBJDEAA.cyates@uidaho.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NBBBJJODBJBNJFNIDDCNAEBJDEAA.cyates@uidaho.edu>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
cc: Federico Montesino Pouzols <fedemp@altern.org>
Subject: Re: urlstring testing/enhancement
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: Thu, 30 Jan 2003 11:32:18 -0000

On Thu, Jan 09, 2003 at 05:16:39PM -0800, Chad Yates wrote:
> before I post a patch to add the new STL string functions I was wondering if
> somebody knew the prefered way of dealing with excessive temporaries.  see
> the following:
> 
> /** @relates URLStream
>  * Encode a octet stream using base64 coding into a STL string
>  * @return base 64 encoded string
>  * @param src     source buffer
>  * @param srcsize source buffer size
>  */
> CCXX_EXPORT(std::string) b64Encode(const unsigned char *src, size_t srcsize)
> {
>   size_t limit = (srcsize+2)/3*4+1;
>   char* buffer = new char[limit];
> 
>   unsigned size = b64Encode(src, srcsize, buffer, limit);
>   buffer[size] = '\0';
> 
>   std::string final = string(buffer);
>   delete buffer;
>   return final;
> }
> 
> notice that I have to not only allocate a temporary buffer (since the
> b64Encode function doesn't work with strings directly -- or some kind
> streaming), but I have to make a copy before I unallocate it, and then yet
> another on the actual return by value.  I have yet to delve into the realm
> of autoptr's.  is that the best bet?  if so, the stl autoptr, or does common
> c++ have a better one.

	I guess there is no good solution for this. The first copy
seems unavoidable and the second one, as far as I know, could only be
avoided if the core routine operated over a string object instead of
the array of char, but that would be a lot worse. Well, after all, you
loose some performance, but you can save significant space :).

	Also, what about adding an encode method that takes a string
object as argument.

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



From MAILER-DAEMON Thu Jan 30 11:48:53 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eHmG-0007Hn-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 11:43:00 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eHm9-00078m-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 11:42:53 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eHlu-0006qF-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 11:42:39 -0500
Received: from mx2.magma.ca ([206.191.0.250])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18eHl3-0005s3-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 11:41:45 -0500
Received: from mail5.magma.ca (mail5.magma.ca [206.191.0.225])
	by mx2.magma.ca (Magma Relay Server) with ESMTP id h0UGfcrq028129; 
	Thu, 30 Jan 2003 11:41:38 -0500
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail5.magma.ca (Magma's Mail Server) with ESMTP id h0UGfRsm015747;
	Thu, 30 Jan 2003 11:41:28 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: "'Federico Montesino Pouzols'" <fedemp@altern.org>
Date: Thu, 30 Jan 2003 11:41:28 -0500
Message-ID: <000f01c2c87e$73ff4960$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <20030129211740.GB1211@bulbasaur.rediris.es>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
Subject: RE: Building CC++ on Mac OS X
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, 30 Jan 2003 16:42:58 -0000

OK, found the problem.

If I call the small sched_getscheduler test program test.c, then it
compiles with no errors or warnings. If I call the same program but
named test.cpp, then gcc complains about an undefined identifier.

The autoconf test creates conftest.c when testing for sched_getscheduler
(and probably other functions too) and so the compiler never complains
about missing functions. Using the -std=c99 options to gcc causes
warnings to be reported on the c files.

[commoncpp2 613] cat test.c
#include <sched.h>

int main ()
{
  int policy;
  policy = sched_getscheduler(0);
  return 0;
}
[commoncpp2 614] cat test.cpp
#include <sched.h>

int main ()
{
  int policy;
  policy = sched_getscheduler(0);
  return 0;
}
[commoncpp2 615] gcc -c -g -O2 test.cpp
test.cpp: In function `int main()':
test.cpp:6: `sched_getscheduler' undeclared (first use this function)
test.cpp:6: (Each undeclared identifier is reported only once for each
function
   it appears in.)
[commoncpp2 616] gcc -c -g -O2 test.c
[commoncpp2 617]
[commoncpp2 618] gcc -c -g -O2 -std=c99 test.c
test.c: In function `main':
test.c:6: warning: implicit declaration of function `sched_getscheduler'


> -----Original Message-----
> From: Federico Montesino Pouzols 
> [mailto:fedemp@bulbasaur.rediris.es] On Behalf Of Federico 
> Montesino Pouzols
> Sent: Wednesday, January 29, 2003 4:18 PM
> To: Ian Gough
> Cc: 'bug-commoncpp'
> Subject: Re: Building CC++ on Mac OS X
> 
> 
> 
> 	Yes, the semaphore stuff is still pending, I expect to 
> fix it soon. As for the sched_getscheduler issue, it is weird 
> that it is detected, since the test is like this:
> 
>         AC_TRY_COMPILE(
>                 [#include <sched.h>],
>                 [
>                 int policy;
>                 policy = sched_getscheduler(0);
>                 ],
>                 [AC_DEFINE(HAVE_SCHED_GETSCHEDULER)])
> 
> 	Could you try to compile on your system a simple C 
> program like the one above? It should not compile, but it 
> seems that autoconf is able to succesfully compile it.
> 
> On Mon, Jan 27, 2003 at 11:10:46AM -0500, Ian Gough wrote:
> > Grabbed a new CVS snapshot this morning and tried to build 
> after these 
> > changes and I still get compilation failures:
> > 
> > g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src 
> > g++ -DCCXX_EXPORT_LIBRARY
> > -I/usr/local/include -D_GNU_SOURCE -Wall -ansi -pedantic 
> -I../include 
> > -c thread.cpp -MT thread.lo -MD -MP -MF .deps/thread.TPlo  
> -fno-common 
> > -DPIC -o .libs/thread.lo
> > cc1plus: warning: changing search order for system directory 
> > "/usr/local/include"
> > cc1plus: warning:   as it has already been specified as a non-system
> > directory
> > thread.cpp: In constructor `ost::Thread::Thread(int, long unsigned
> > int)':
> > thread.cpp:536: `sched_getscheduler' undeclared (first use this
> > function)
> > thread.cpp:536: (Each undeclared identifier is reported 
> only once for 
> > each
> >    function it appears in.)
> > thread.cpp:554: `sched_getparam' undeclared (first use this 
> function)
> > make[1]: *** [thread.lo] Error 1
> > make: *** [all-recursive] Error 1
> > 
> > Checking if HAVE_SCHED_GETSCHEDULER is defined in one of the header 
> > files shows that it is defined in config.h for some reason.
> > 
> > [/var/root/src/revgen/xGrid/ccxx 552] grep -r HAVE_SCHED * 
> > acconfig.h:#undef HAVE_SCHED_GETSCHEDULER acconfig.h:#ifdef 
> > HAVE_SCHED_H config.log:#define HAVE_SCHED_H 1
> > config.log:#define HAVE_SCHED_GETSCHEDULER 1
> > 
> config.status:${ac_dA}HAVE_SCHED_H${ac_dB}HAVE_SCHED_H${ac_dC}
> 1${ac_dD}
> > 
> config.status:${ac_dA}HAVE_SCHED_GETSCHEDULER${ac_dB}HAVE_SCHE
D_GETSCHED
> > ULER${ac_dC}1${ac_dD}
> > 
> config.status:${ac_uA}HAVE_SCHED_H${ac_uB}HAVE_SCHED_H${ac_uC}
> 1${ac_uD}
> > 
> config.status:${ac_uA}HAVE_SCHED_GETSCHEDULER${ac_uB}HAVE_SCHE
D_GETSCHED
> > ULER${ac_uC}1${ac_uD}
> > configure:#define HAVE_SCHED_GETSCHEDULER 1
> > include/cc++/config.h:#define HAVE_SCHED_GETSCHEDULER 1
> > include/cc++/config.h:#define HAVE_SCHED_H 1
> > include/cc++/config.h:#ifdef HAVE_SCHED_H
> > include/cc++/config.tmp:#define HAVE_SCHED_GETSCHEDULER 1
> > include/cc++/config.tmp:#define HAVE_SCHED_H 1
> > include/cc++/config.tmp:#ifdef HAVE_SCHED_H
> > include/config.h:#define HAVE_SCHED_GETSCHEDULER 1
> > include/config.h:#define HAVE_SCHED_H 1
> > include/config.h:#ifdef HAVE_SCHED_H
> > include/config.h.in:#undef HAVE_SCHED_GETSCHEDULER
> > include/config.h.in:#undef HAVE_SCHED_H
> > include/config.h.in:#ifdef HAVE_SCHED_H
> > m4/ost_pthread.m4:              
> [AC_DEFINE(HAVE_SCHED_GETSCHEDULER)])
> > m4/ost_pthread.m4:dnl #undef HAVE_SCHED_GETSCHEDULER
> > m4/ost_pthread.m4:dnl #ifdef HAVE_SCHED_H
> > src/thread.cpp:#ifdef HAVE_SCHED_GETSCHEDULER
> > src/thread.cpp:#endif // ifdef HAVE_SCHED_GETSCHEDULER
> > 
> > But /usr/include/sched.h shows that there is no 
> sched_getscheduler() 
> > function.
> > 
> > #ifndef _SCHED_H_
> > #define _SCHED_H_
> > 
> > #include <pthread_impl.h>
> > 
> > /*
> >  * Scheduling paramters
> >  */
> > #ifndef __POSIX_LIB__
> > struct sched_param { int sched_priority;  char 
> > opaque[__SCHED_PARAM_SIZE__]; }; #endif
> > 
> > extern int sched_yield(void);
> > extern int sched_get_priority_min(int);
> > extern int sched_get_priority_max(int);
> > #endif /* _SCHED_H_ */
> > 
> > I grepped for sched_getscheduler and turned up no hits, so I am not 
> > sure why the autoconf system thinks that it exists.
> > 
> > I then defined __FreeBSD__ to get around this problem, but ran into 
> > another compile problem.
> > 
> > g++ -DHAVE_CONFIG_H -I. -I. -I../include -D__FreeBSD__ -I../src
> > -DCCXX_EXPORT_LIBRARY -I/usr/local/include -D_GNU_SOURCE 
> -Wall -ansi 
> > -pedantic -I../include -c semaphore.cpp -MT semaphore.lo 
> -MD -MP -MF 
> > .deps/semaphore.TPlo  -fno-common -DPIC -o .libs/semaphore.lo
> > cc1plus: warning: changing search order for system directory 
> > "/usr/local/include"
> > cc1plus: warning:   as it has already been specified as a non-system
> > directory
> > /usr/include/sys/sem.h: In destructor `virtual
> > ost::Semaphore::~Semaphore()':
> > /usr/include/sys/sem.h:242: too few arguments to function `int 
> > ost::semctl(int,
> >    int, int, ost::semun)'
> > semaphore.cpp:100: at this point in file
> > /usr/include/sys/sem.h: In member function `int
> > ost::Semaphore::getValue()':
> > /usr/include/sys/sem.h:242: too few arguments to function `int 
> > ost::semctl(int,
> >    int, int, ost::semun)'
> > semaphore.cpp:126: at this point in file
> > make: *** [semaphore.lo] Error 1
> > 
> > Mac OS X does not seem to have SYSV semaphores and an 
> incomplete set 
> > of POSIX semaphore functions. It does NOT have sem_init and 
> > sem_destroy, but it does have sem_open and sem_close.
> > 
> > > -----Original Message-----
> > > From: Federico Montesino Pouzols
> > > [mailto:fedemp@bulbasaur.rediris.es] On Behalf Of Federico 
> > > Montesino Pouzols
> > > Sent: Wednesday, January 22, 2003 3:20 AM
> > > To: Ian Gough
> > > Cc: 'bug-commoncpp'
> > > Subject: Re: Building CC++ on Mac OS X
> > > 
> > > 
> > > 
> > > 	Good, I have commited some modifications that should
> > > fix this issue.
> > > 
> > > On Tue, Jan 21, 2003 at 09:47:57AM -0500, Ian Gough wrote:
> > > > > 	Um, I have just looked at this and actually there is
> > > already some
> > > > > autoconf stuff. Could you confirm if, in the config.h of
> > > cc++, the
> > > > > symbol HAVE_SOCKLEN_T is undefined?
> > > > > 
> > > > 
> > > > It is commented out. From include/cc++/config.h
> > > > 
> > > > #define HAVE_INET_ATON 1
> > > > #define HAVE_INET_SOCKETS 1
> > > > #define HAVE_UNIX_SOCKETS 1
> > > > /* #undef HAVE_SOCKLEN_T */
> > > > /* #undef HAVE_SYS_LIBCSYS_H */
> > > > /* #undef HAVE_SYS_STREAM_H */
> > > > /* #undef HAVE_SYS_POLL_H */
> > > > /* #undef HAVE_POLL_H */
> > > > 
> > > 
> > 
> > 
> > 
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org 
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From MAILER-DAEMON Thu Jan 30 11:58:10 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eHyy-00074o-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 11:56:08 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eHyk-0006xA-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 11:55:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eHyO-0005uz-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 11:55:37 -0500
Received: from acate.com.br ([200.215.17.89] helo=cli004.brasmap)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18eHmz-0007Tc-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 11:43:46 -0500
Received: from brasmap.com.br (localhost.localdomain [127.0.0.1])
	by cli004.brasmap (Postfix) with SMTP
	id A55DA5B4EA; Thu, 30 Jan 2003 14:49:44 -0200 (BRST)
Date: Thu, 30 Jan 2003 14:49:44 -0200
From: Marcelo Dalmas <mad@brasmap.com.br>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-Id: <20030130144944.2b7b29db.mad@brasmap.com.br>
In-Reply-To: <20030130104845.GB269@bulbasaur.rediris.es>
References: <NBBBJJODBJBNJFNIDDCNKEHJDEAA.cyates@uidaho.edu>
	<20030130104845.GB269@bulbasaur.rediris.es>
Organization: BRASMAP Sistemas
X-Mailer: Sylpheed version 0.8.7 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
cc: albert@dogbert.sdsl.sun.ac.za
cc: bug-commoncpp@gnu.org
cc: cyates@uidaho.edu
Subject: Re: common C++ test suite
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, 30 Jan 2003 16:56:06 -0000

On Thu, 30 Jan 2003 11:48:45 +0100
Federico Montesino Pouzols <fedemp@altern.org> wrote:

> 
> 	Hi,...
> 
> On Wed, Jan 29, 2003 at 10:41:34PM -0800, Chad Yates wrote:
> > Common C++ community,
> > 
> > As some of you may remember, I wrote some test suites in cppunit last
> > month and I would like to submit them as the beginnings of a common
> > C++ test suite as we had discussed then.  however it has a couple of
> > issues I am hoping a more experienced common c++ developer or
> > maintainer can help with, as I am a gnu autoconfig/automake newbie,
> > I'll admit it. :)  also since I typically develop using m$ visual
> > studio 6.0 I'm not that proficient with developing/debugging on the
> > linux environment.
> > 
> > My date classes have some tests that are failing now with the recent
> > patches submitted that add the new YYYY/MM/DD style formats instead of
> > the YYYYMMDD formats.  whether the interface is changing or whether
> > the tests need to be updated to the new format needs to be determined.
> > 
> 
> 	I would expect Marcelo's opinion, though I think that we
> should keep backwards compatibility.

I agree. I wrote a new patch and I will test it with Chad's test suite
before send it.
> 
> > My persistence tests (pretty extensive), work fine under windows, but
> > throw exceptions under linux.  I don't yet know why, and since I
> > haven't come to grips with a linux debugger yet (I've been babied by
> > VC++'s gui debugger), I can't dig into the reason yet.  I have another
> > test case under windows, but am not going to add it at this time as it
> > has some linux compilation issues.
> > 
> > There are generalized test classes for the digest tests, however I
> > could never seem to get decent results out of the SHA digests on
> > windows, they may work fine under linux, though the testcase
> > registration macros are commented out right now.
> > 
> > There are also tests for the urlstring file including base64 encode
> > decode.
> > 
> > I have attached a zip file containing a zipped directory called
> > ccxx_tests designed to be uncompressed under the commoncpp2 main
> > directory.  eventually I would hope the contents would live in tests
> > instead, and all the existing tests changed to components of the
> > cppunit test suites, or something similar.
> > 
> 
> 	Um, I would like the new tests to go directly into tests/, and
> integrate the old tests as soon as possible. Since there seems to be a
> few issues to solve, I would put the new tests there now for the
> development branch, and, when these issues are clarified, commit the
> new test suite for the stable releases. This would be a very
> interesting new feature for 1.0.9. It would also be interesting to
> include the VC++ project files for the test suite.
> 
> 	Do you agree with this plan?
> 
> > I have also attached a diff of the changes I made to the configure.in
> > and Makefile.am to get it to build for me on my linux machine,
> > however, I didn't get the check for cppunit to work to my liking, and
> > am sure the changes I made were not ideal.  hopefully someone with
> > more expertise in autoconf/automake can make better changes there.
> > 
> > Anyway, I wanted to get this out there and in cvs so others can
> > contribute if wanted, and so we would have somewhat of a base to
> > start/learn from. Also, it would be a good habit for contributors to
> > get the hang of adding suites/testcases while finding/resolving bugs
> > and making enhancements. This way some inadvertant sideffects can
> > hopefully be avoided.
> > 
> 
> 	I totally agree.
> 
> > Cheers,
> > 
> > chad
> > 
> > P.S. I spoke with albert today, and he will be contributing his
> > testcases etc a bit later.  Feel free to contact me if you have
> > questions, comments/suggestions, or if you have trouble compiling it. 
> > I will contribute new suites/testcases as I develop them.
> 
> 
> 
> > _______________________________________________
> > 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
> 


-- 
Marcelo Dalmas
BRASMAP Sistemas
www.brasmap.com.br
Fone/Fax: (48) 333-2218 ramal 2114

Linux user #114373 http://counter.li.org/




From MAILER-DAEMON Thu Jan 30 12:29:53 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eIV0-00042m-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 12:29:14 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eIUs-0003hc-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 12:29:06 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eITL-0001nA-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 12:27:34 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57]
	helo=home.localhost.localdomain)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18eISv-0001Hn-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 12:27:06 -0500
Received: from localhost.localdomain ([172.16.1.11])h0UI3lt32025;
	Thu, 30 Jan 2003 13:03:47 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: "Ian Gough" <igough@gridiron-networks.com>,
   "'Federico Montesino Pouzols'" <fedemp@altern.org>
Date: Thu, 30 Jan 2003 12:22:33 -0500
User-Agent: KMail/1.4.3
References: <000f01c2c87e$73ff4960$0c02a8c0@gridironnetworks.com>
In-Reply-To: <000f01c2c87e$73ff4960$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301301222.33979.dyfet@ostel.com>
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
Subject: Re: Building CC++ on Mac OS X
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, 30 Jan 2003 17:29:12 -0000

The AC_LANG_CPP and AC_LANG_RESTORE options will need to be used in the=20
section that tests for this function.  This will make sure they are teste=
d=20
with the local machines C++ compiler rather than the C compiler....

On Thursday 30 January 2003 11:41, Ian Gough wrote:
> OK, found the problem.
>
> If I call the small sched_getscheduler test program test.c, then it
> compiles with no errors or warnings. If I call the same program but
> named test.cpp, then gcc complains about an undefined identifier.
>
> The autoconf test creates conftest.c when testing for sched_getschedule=
r
> (and probably other functions too) and so the compiler never complains
> about missing functions. Using the -std=3Dc99 options to gcc causes
> warnings to be reported on the c files.
>
> [commoncpp2 613] cat test.c
> #include <sched.h>
>
> int main ()
> {
>   int policy;
>   policy =3D sched_getscheduler(0);
>   return 0;
> }
> [commoncpp2 614] cat test.cpp
> #include <sched.h>
>
> int main ()
> {
>   int policy;
>   policy =3D sched_getscheduler(0);
>   return 0;
> }
> [commoncpp2 615] gcc -c -g -O2 test.cpp
> test.cpp: In function `int main()':
> test.cpp:6: `sched_getscheduler' undeclared (first use this function)
> test.cpp:6: (Each undeclared identifier is reported only once for each
> function
>    it appears in.)
> [commoncpp2 616] gcc -c -g -O2 test.c
> [commoncpp2 617]
> [commoncpp2 618] gcc -c -g -O2 -std=3Dc99 test.c
> test.c: In function `main':
> test.c:6: warning: implicit declaration of function `sched_getscheduler=
'
>
> > -----Original Message-----
> > From: Federico Montesino Pouzols
> > [mailto:fedemp@bulbasaur.rediris.es] On Behalf Of Federico
> > Montesino Pouzols
> > Sent: Wednesday, January 29, 2003 4:18 PM
> > To: Ian Gough
> > Cc: 'bug-commoncpp'
> > Subject: Re: Building CC++ on Mac OS X
> >
> >
> >
> > =09Yes, the semaphore stuff is still pending, I expect to
> > fix it soon. As for the sched_getscheduler issue, it is weird
> > that it is detected, since the test is like this:
> >
> >         AC_TRY_COMPILE(
> >                 [#include <sched.h>],
> >                 [
> >                 int policy;
> >                 policy =3D sched_getscheduler(0);
> >                 ],
> >                 [AC_DEFINE(HAVE_SCHED_GETSCHEDULER)])
> >
> > =09Could you try to compile on your system a simple C
> > program like the one above? It should not compile, but it
> > seems that autoconf is able to succesfully compile it.
> >
> > On Mon, Jan 27, 2003 at 11:10:46AM -0500, Ian Gough wrote:
> > > Grabbed a new CVS snapshot this morning and tried to build
> >
> > after these
> >
> > > changes and I still get compilation failures:
> > >
> > > g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src
> > > g++ -DCCXX_EXPORT_LIBRARY
> > > -I/usr/local/include -D_GNU_SOURCE -Wall -ansi -pedantic
> >
> > -I../include
> >
> > > -c thread.cpp -MT thread.lo -MD -MP -MF .deps/thread.TPlo
> >
> > -fno-common
> >
> > > -DPIC -o .libs/thread.lo
> > > cc1plus: warning: changing search order for system directory
> > > "/usr/local/include"
> > > cc1plus: warning:   as it has already been specified as a non-syste=
m
> > > directory
> > > thread.cpp: In constructor `ost::Thread::Thread(int, long unsigned
> > > int)':
> > > thread.cpp:536: `sched_getscheduler' undeclared (first use this
> > > function)
> > > thread.cpp:536: (Each undeclared identifier is reported
> >
> > only once for
> >
> > > each
> > >    function it appears in.)
> > > thread.cpp:554: `sched_getparam' undeclared (first use this
> >
> > function)
> >
> > > make[1]: *** [thread.lo] Error 1
> > > make: *** [all-recursive] Error 1
> > >
> > > Checking if HAVE_SCHED_GETSCHEDULER is defined in one of the header
> > > files shows that it is defined in config.h for some reason.
> > >
> > > [/var/root/src/revgen/xGrid/ccxx 552] grep -r HAVE_SCHED *
> > > acconfig.h:#undef HAVE_SCHED_GETSCHEDULER acconfig.h:#ifdef
> > > HAVE_SCHED_H config.log:#define HAVE_SCHED_H 1
> > > config.log:#define HAVE_SCHED_GETSCHEDULER 1
> >
> > config.status:${ac_dA}HAVE_SCHED_H${ac_dB}HAVE_SCHED_H${ac_dC}
> > 1${ac_dD}
> >
> > config.status:${ac_dA}HAVE_SCHED_GETSCHEDULER${ac_dB}HAVE_SCHE
>
> D_GETSCHED
>
> > > ULER${ac_dC}1${ac_dD}
> >
> > config.status:${ac_uA}HAVE_SCHED_H${ac_uB}HAVE_SCHED_H${ac_uC}
> > 1${ac_uD}
> >
> > config.status:${ac_uA}HAVE_SCHED_GETSCHEDULER${ac_uB}HAVE_SCHE
>
> D_GETSCHED
>
> > > ULER${ac_uC}1${ac_uD}
> > > configure:#define HAVE_SCHED_GETSCHEDULER 1
> > > include/cc++/config.h:#define HAVE_SCHED_GETSCHEDULER 1
> > > include/cc++/config.h:#define HAVE_SCHED_H 1
> > > include/cc++/config.h:#ifdef HAVE_SCHED_H
> > > include/cc++/config.tmp:#define HAVE_SCHED_GETSCHEDULER 1
> > > include/cc++/config.tmp:#define HAVE_SCHED_H 1
> > > include/cc++/config.tmp:#ifdef HAVE_SCHED_H
> > > include/config.h:#define HAVE_SCHED_GETSCHEDULER 1
> > > include/config.h:#define HAVE_SCHED_H 1
> > > include/config.h:#ifdef HAVE_SCHED_H
> > > include/config.h.in:#undef HAVE_SCHED_GETSCHEDULER
> > > include/config.h.in:#undef HAVE_SCHED_H
> > > include/config.h.in:#ifdef HAVE_SCHED_H
> > > m4/ost_pthread.m4:
> >
> > [AC_DEFINE(HAVE_SCHED_GETSCHEDULER)])
> >
> > > m4/ost_pthread.m4:dnl #undef HAVE_SCHED_GETSCHEDULER
> > > m4/ost_pthread.m4:dnl #ifdef HAVE_SCHED_H
> > > src/thread.cpp:#ifdef HAVE_SCHED_GETSCHEDULER
> > > src/thread.cpp:#endif // ifdef HAVE_SCHED_GETSCHEDULER
> > >
> > > But /usr/include/sched.h shows that there is no
> >
> > sched_getscheduler()
> >
> > > function.
> > >
> > > #ifndef _SCHED_H_
> > > #define _SCHED_H_
> > >
> > > #include <pthread_impl.h>
> > >
> > > /*
> > >  * Scheduling paramters
> > >  */
> > > #ifndef __POSIX_LIB__
> > > struct sched_param { int sched_priority;  char
> > > opaque[__SCHED_PARAM_SIZE__]; }; #endif
> > >
> > > extern int sched_yield(void);
> > > extern int sched_get_priority_min(int);
> > > extern int sched_get_priority_max(int);
> > > #endif /* _SCHED_H_ */
> > >
> > > I grepped for sched_getscheduler and turned up no hits, so I am not
> > > sure why the autoconf system thinks that it exists.
> > >
> > > I then defined __FreeBSD__ to get around this problem, but ran into
> > > another compile problem.
> > >
> > > g++ -DHAVE_CONFIG_H -I. -I. -I../include -D__FreeBSD__ -I../src
> > > -DCCXX_EXPORT_LIBRARY -I/usr/local/include -D_GNU_SOURCE
> >
> > -Wall -ansi
> >
> > > -pedantic -I../include -c semaphore.cpp -MT semaphore.lo
> >
> > -MD -MP -MF
> >
> > > .deps/semaphore.TPlo  -fno-common -DPIC -o .libs/semaphore.lo
> > > cc1plus: warning: changing search order for system directory
> > > "/usr/local/include"
> > > cc1plus: warning:   as it has already been specified as a non-syste=
m
> > > directory
> > > /usr/include/sys/sem.h: In destructor `virtual
> > > ost::Semaphore::~Semaphore()':
> > > /usr/include/sys/sem.h:242: too few arguments to function `int
> > > ost::semctl(int,
> > >    int, int, ost::semun)'
> > > semaphore.cpp:100: at this point in file
> > > /usr/include/sys/sem.h: In member function `int
> > > ost::Semaphore::getValue()':
> > > /usr/include/sys/sem.h:242: too few arguments to function `int
> > > ost::semctl(int,
> > >    int, int, ost::semun)'
> > > semaphore.cpp:126: at this point in file
> > > make: *** [semaphore.lo] Error 1
> > >
> > > Mac OS X does not seem to have SYSV semaphores and an
> >
> > incomplete set
> >
> > > of POSIX semaphore functions. It does NOT have sem_init and
> > > sem_destroy, but it does have sem_open and sem_close.
> > >
> > > > -----Original Message-----
> > > > From: Federico Montesino Pouzols
> > > > [mailto:fedemp@bulbasaur.rediris.es] On Behalf Of Federico
> > > > Montesino Pouzols
> > > > Sent: Wednesday, January 22, 2003 3:20 AM
> > > > To: Ian Gough
> > > > Cc: 'bug-commoncpp'
> > > > Subject: Re: Building CC++ on Mac OS X
> > > >
> > > >
> > > >
> > > > =09Good, I have commited some modifications that should
> > > > fix this issue.
> > > >
> > > > On Tue, Jan 21, 2003 at 09:47:57AM -0500, Ian Gough wrote:
> > > > > > =09Um, I have just looked at this and actually there is
> > > >
> > > > already some
> > > >
> > > > > > autoconf stuff. Could you confirm if, in the config.h of
> > > >
> > > > cc++, the
> > > >
> > > > > > symbol HAVE_SOCKLEN_T is undefined?
> > > > >
> > > > > It is commented out. From include/cc++/config.h
> > > > >
> > > > > #define HAVE_INET_ATON 1
> > > > > #define HAVE_INET_SOCKETS 1
> > > > > #define HAVE_UNIX_SOCKETS 1
> > > > > /* #undef HAVE_SOCKLEN_T */
> > > > > /* #undef HAVE_SYS_LIBCSYS_H */
> > > > > /* #undef HAVE_SYS_STREAM_H */
> > > > > /* #undef HAVE_SYS_POLL_H */
> > > > > /* #undef HAVE_POLL_H */
> > >
> > > _______________________________________________
> > > 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 MAILER-DAEMON Thu Jan 30 13:33:17 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eJUy-0001Ca-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 13:33:16 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eJUv-0001BO-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 13:33:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eJUt-0001A1-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 13:33:12 -0500
Received: from mx1.magmacom.com ([206.191.0.217])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18eJUs-00019p-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 13:33:11 -0500
Received: from mail6.magma.ca (mail6 [206.191.0.248])h0UIX4H6013589;
	Thu, 30 Jan 2003 13:33:04 -0500 (EST)
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail6.magma.ca (Magma's Mail Server) with ESMTP id h0UIWxsu029335;
	Thu, 30 Jan 2003 13:33:02 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: "'David Sugar'" <dyfet@ostel.com>,
   "'Federico Montesino Pouzols'" <fedemp@altern.org>
Date: Thu, 30 Jan 2003 13:33:00 -0500
Message-ID: <002201c2c88e$06cd3c20$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <200301301222.33979.dyfet@ostel.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
Subject: RE: Building CC++ on Mac OS X
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, 30 Jan 2003 18:33:14 -0000

Wouldn't the C/C++ issue be a general problem for ANY test that uses
AC_TRY_COMPILE?. If you use the C compiler, autoconf cannot detect
missing functionality properly.

Will somebody be making this change or is there an expectation that I
would make the change? Not that I know what file in which to make any
changes. :-)

> -----Original Message-----
> From: David Sugar [mailto:dyfet@ostel.com] 
> Sent: Thursday, January 30, 2003 12:23 PM
> To: Ian Gough; 'Federico Montesino Pouzols'
> Cc: 'bug-commoncpp'
> Subject: Re: Building CC++ on Mac OS X
> 
> 
> The AC_LANG_CPP and AC_LANG_RESTORE options will need to be 
> used in the 
> section that tests for this function.  This will make sure 
> they are tested 
> with the local machines C++ compiler rather than the C compiler....
> 
> On Thursday 30 January 2003 11:41, Ian Gough wrote:
> > OK, found the problem.
> >
> > If I call the small sched_getscheduler test program test.c, then it 
> > compiles with no errors or warnings. If I call the same program but 
> > named test.cpp, then gcc complains about an undefined identifier.
> >
> > The autoconf test creates conftest.c when testing for 
> > sched_getscheduler (and probably other functions too) and so the 
> > compiler never complains about missing functions. Using the 
> -std=c99 
> > options to gcc causes warnings to be reported on the c files.
> >
> > [commoncpp2 613] cat test.c
> > #include <sched.h>
> >
> > int main ()
> > {
> >   int policy;
> >   policy = sched_getscheduler(0);
> >   return 0;
> > }
> > [commoncpp2 614] cat test.cpp
> > #include <sched.h>
> >
> > int main ()
> > {
> >   int policy;
> >   policy = sched_getscheduler(0);
> >   return 0;
> > }
> > [commoncpp2 615] gcc -c -g -O2 test.cpp
> > test.cpp: In function `int main()':
> > test.cpp:6: `sched_getscheduler' undeclared (first use this 
> function)
> > test.cpp:6: (Each undeclared identifier is reported only 
> once for each 
> > function
> >    it appears in.)
> > [commoncpp2 616] gcc -c -g -O2 test.c
> > [commoncpp2 617]
> > [commoncpp2 618] gcc -c -g -O2 -std=c99 test.c
> > test.c: In function `main':
> > test.c:6: warning: implicit declaration of function 
> > `sched_getscheduler'
> >
> > > -----Original Message-----
> > > From: Federico Montesino Pouzols 
> > > [mailto:fedemp@bulbasaur.rediris.es] On Behalf Of 
> Federico Montesino 
> > > Pouzols
> > > Sent: Wednesday, January 29, 2003 4:18 PM
> > > To: Ian Gough
> > > Cc: 'bug-commoncpp'
> > > Subject: Re: Building CC++ on Mac OS X
> > >
> > >
> > >
> > > 	Yes, the semaphore stuff is still pending, I expect to
> > > fix it soon. As for the sched_getscheduler issue, it is 
> weird that 
> > > it is detected, since the test is like this:
> > >
> > >         AC_TRY_COMPILE(
> > >                 [#include <sched.h>],
> > >                 [
> > >                 int policy;
> > >                 policy = sched_getscheduler(0);
> > >                 ],
> > >                 [AC_DEFINE(HAVE_SCHED_GETSCHEDULER)])
> > >
> > > 	Could you try to compile on your system a simple C
> > > program like the one above? It should not compile, but it 
> seems that 
> > > autoconf is able to succesfully compile it.
> > >
> > > On Mon, Jan 27, 2003 at 11:10:46AM -0500, Ian Gough wrote:
> > > > Grabbed a new CVS snapshot this morning and tried to build
> > >
> > > after these
> > >
> > > > changes and I still get compilation failures:
> > > >
> > > > g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src 
> > > > g++ -DCCXX_EXPORT_LIBRARY
> > > > -I/usr/local/include -D_GNU_SOURCE -Wall -ansi -pedantic
> > >
> > > -I../include
> > >
> > > > -c thread.cpp -MT thread.lo -MD -MP -MF .deps/thread.TPlo
> > >
> > > -fno-common
> > >
> > > > -DPIC -o .libs/thread.lo
> > > > cc1plus: warning: changing search order for system directory 
> > > > "/usr/local/include"
> > > > cc1plus: warning:   as it has already been specified as 
> a non-system
> > > > directory
> > > > thread.cpp: In constructor `ost::Thread::Thread(int, 
> long unsigned
> > > > int)':
> > > > thread.cpp:536: `sched_getscheduler' undeclared (first use this
> > > > function)
> > > > thread.cpp:536: (Each undeclared identifier is reported
> > >
> > > only once for
> > >
> > > > each
> > > >    function it appears in.)
> > > > thread.cpp:554: `sched_getparam' undeclared (first use this
> > >
> > > function)
> > >
> > > > make[1]: *** [thread.lo] Error 1
> > > > make: *** [all-recursive] Error 1
> > > >
> > > > Checking if HAVE_SCHED_GETSCHEDULER is defined in one of the 
> > > > header files shows that it is defined in config.h for 
> some reason.
> > > >
> > > > [/var/root/src/revgen/xGrid/ccxx 552] grep -r HAVE_SCHED * 
> > > > acconfig.h:#undef HAVE_SCHED_GETSCHEDULER acconfig.h:#ifdef 
> > > > HAVE_SCHED_H config.log:#define HAVE_SCHED_H 1 
> config.log:#define 
> > > > HAVE_SCHED_GETSCHEDULER 1
> > >
> > > config.status:${ac_dA}HAVE_SCHED_H${ac_dB}HAVE_SCHED_H${ac_dC}
> > > 1${ac_dD}
> > >
> > > config.status:${ac_dA}HAVE_SCHED_GETSCHEDULER${ac_dB}HAVE_SCHE
> >
> > D_GETSCHED
> >
> > > > ULER${ac_dC}1${ac_dD}
> > >
> > > config.status:${ac_uA}HAVE_SCHED_H${ac_uB}HAVE_SCHED_H${ac_uC}
> > > 1${ac_uD}
> > >
> > > config.status:${ac_uA}HAVE_SCHED_GETSCHEDULER${ac_uB}HAVE_SCHE
> >
> > D_GETSCHED
> >
> > > > ULER${ac_uC}1${ac_uD}
> > > > configure:#define HAVE_SCHED_GETSCHEDULER 1 
> > > > include/cc++/config.h:#define HAVE_SCHED_GETSCHEDULER 1 
> > > > include/cc++/config.h:#define HAVE_SCHED_H 1 
> > > > include/cc++/config.h:#ifdef HAVE_SCHED_H 
> > > > include/cc++/config.tmp:#define HAVE_SCHED_GETSCHEDULER 1 
> > > > include/cc++/config.tmp:#define HAVE_SCHED_H 1 
> > > > include/cc++/config.tmp:#ifdef HAVE_SCHED_H 
> > > > include/config.h:#define HAVE_SCHED_GETSCHEDULER 1 
> > > > include/config.h:#define HAVE_SCHED_H 1 include/config.h:#ifdef 
> > > > HAVE_SCHED_H include/config.h.in:#undef HAVE_SCHED_GETSCHEDULER
> > > > include/config.h.in:#undef HAVE_SCHED_H
> > > > include/config.h.in:#ifdef HAVE_SCHED_H
> > > > m4/ost_pthread.m4:
> > >
> > > [AC_DEFINE(HAVE_SCHED_GETSCHEDULER)])
> > >
> > > > m4/ost_pthread.m4:dnl #undef HAVE_SCHED_GETSCHEDULER 
> > > > m4/ost_pthread.m4:dnl #ifdef HAVE_SCHED_H src/thread.cpp:#ifdef 
> > > > HAVE_SCHED_GETSCHEDULER src/thread.cpp:#endif // ifdef 
> > > > HAVE_SCHED_GETSCHEDULER
> > > >
> > > > But /usr/include/sched.h shows that there is no
> > >
> > > sched_getscheduler()
> > >
> > > > function.
> > > >
> > > > #ifndef _SCHED_H_
> > > > #define _SCHED_H_
> > > >
> > > > #include <pthread_impl.h>
> > > >
> > > > /*
> > > >  * Scheduling paramters
> > > >  */
> > > > #ifndef __POSIX_LIB__
> > > > struct sched_param { int sched_priority;  char 
> > > > opaque[__SCHED_PARAM_SIZE__]; }; #endif
> > > >
> > > > extern int sched_yield(void);
> > > > extern int sched_get_priority_min(int);
> > > > extern int sched_get_priority_max(int);
> > > > #endif /* _SCHED_H_ */
> > > >
> > > > I grepped for sched_getscheduler and turned up no hits, so I am 
> > > > not sure why the autoconf system thinks that it exists.
> > > >
> > > > I then defined __FreeBSD__ to get around this problem, but ran 
> > > > into another compile problem.
> > > >
> > > > g++ -DHAVE_CONFIG_H -I. -I. -I../include -D__FreeBSD__ -I../src
> > > > -DCCXX_EXPORT_LIBRARY -I/usr/local/include -D_GNU_SOURCE
> > >
> > > -Wall -ansi
> > >
> > > > -pedantic -I../include -c semaphore.cpp -MT semaphore.lo
> > >
> > > -MD -MP -MF
> > >
> > > > .deps/semaphore.TPlo  -fno-common -DPIC -o .libs/semaphore.lo
> > > > cc1plus: warning: changing search order for system directory 
> > > > "/usr/local/include"
> > > > cc1plus: warning:   as it has already been specified as 
> a non-system
> > > > directory
> > > > /usr/include/sys/sem.h: In destructor `virtual
> > > > ost::Semaphore::~Semaphore()':
> > > > /usr/include/sys/sem.h:242: too few arguments to function `int 
> > > > ost::semctl(int,
> > > >    int, int, ost::semun)'
> > > > semaphore.cpp:100: at this point in file
> > > > /usr/include/sys/sem.h: In member function `int
> > > > ost::Semaphore::getValue()':
> > > > /usr/include/sys/sem.h:242: too few arguments to function `int 
> > > > ost::semctl(int,
> > > >    int, int, ost::semun)'
> > > > semaphore.cpp:126: at this point in file
> > > > make: *** [semaphore.lo] Error 1
> > > >
> > > > Mac OS X does not seem to have SYSV semaphores and an
> > >
> > > incomplete set
> > >
> > > > of POSIX semaphore functions. It does NOT have sem_init and 
> > > > sem_destroy, but it does have sem_open and sem_close.
> > > >
> > > > > -----Original Message-----
> > > > > From: Federico Montesino Pouzols 
> > > > > [mailto:fedemp@bulbasaur.rediris.es] On Behalf Of Federico 
> > > > > Montesino Pouzols
> > > > > Sent: Wednesday, January 22, 2003 3:20 AM
> > > > > To: Ian Gough
> > > > > Cc: 'bug-commoncpp'
> > > > > Subject: Re: Building CC++ on Mac OS X
> > > > >
> > > > >
> > > > >
> > > > > 	Good, I have commited some modifications that 
> should fix this 
> > > > > issue.
> > > > >
> > > > > On Tue, Jan 21, 2003 at 09:47:57AM -0500, Ian Gough wrote:
> > > > > > > 	Um, I have just looked at this and actually there is
> > > > >
> > > > > already some
> > > > >
> > > > > > > autoconf stuff. Could you confirm if, in the config.h of
> > > > >
> > > > > cc++, the
> > > > >
> > > > > > > symbol HAVE_SOCKLEN_T is undefined?
> > > > > >
> > > > > > It is commented out. From include/cc++/config.h
> > > > > >
> > > > > > #define HAVE_INET_ATON 1
> > > > > > #define HAVE_INET_SOCKETS 1
> > > > > > #define HAVE_UNIX_SOCKETS 1
> > > > > > /* #undef HAVE_SOCKLEN_T */
> > > > > > /* #undef HAVE_SYS_LIBCSYS_H */
> > > > > > /* #undef HAVE_SYS_STREAM_H */
> > > > > > /* #undef HAVE_SYS_POLL_H */
> > > > > > /* #undef HAVE_POLL_H */
> > > >
> > > > _______________________________________________
> > > > 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 MAILER-DAEMON Thu Jan 30 14:58:54 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eKpp-00023i-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 14:58:53 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eKpm-0001wC-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 14:58:50 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eKpk-0001vu-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 14:58:49 -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 18eKpj-0001uM-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 14:58:48 -0500
Received: from falcon ([129.101.69.98]) by mailA.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H9J00GRRM5WCR@mailA.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 30 Jan 2003 11:58:44 -0800 (PST)
Date: Thu, 30 Jan 2003 11:58:44 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20030130104845.GB269@bulbasaur.rediris.es>
To: bug-commoncpp <bug-commoncpp@gnu.org>
Message-id: <NBBBJJODBJBNJFNIDDCNCEHNDEAA.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: multipart/mixed; boundary="Boundary_(ID_qjavf2ykReG8ieF6fJuC0w)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Subject: RE: common C++ test suite
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, 30 Jan 2003 19:58:50 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_qjavf2ykReG8ieF6fJuC0w)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Attached is a zip file containing the msvc++ 6.0 project file.  I made no
effort to setup the release target environment, just the debug one.

It resides in commoncpp2/win32/tests is called ccxx_testsuite and builds
it's debug output in commoncpp2/win32/Debug like the other tests.  it
expects to find it's source files in commoncpp2/tests, and may reference at
least 1 file that I have not submitted yet (SampleNode.cpp/SampleNode.cpp).

The file b64test.cpp I think I included in the source code zip can safely be
omitted since it was a isolated set of test cases for the b64 bugs I
previously submitted, and they are included in test_urlstring.cpp.

Please let me know if you have any trouble. :)

,Chad

P.S. You'll probably want to add it to some of the ccxx workspaces so it
gets exposure.

> -----Original Message-----
> From: bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org
> [mailto:bug-commoncpp-bounces+cyates=uidaho.edu@gnu.org]On Behalf Of
> Federico Montesino Pouzols
> Sent: Thursday, January 30, 2003 2:49 AM
> To: Chad Yates
> Cc: albert@dogbert.sdsl.sun.ac.za; bug-commoncpp
> Subject: Re: common C++ test suite
>
>
>
> 	Hi,...
>
> On Wed, Jan 29, 2003 at 10:41:34PM -0800, Chad Yates wrote:
> > Common C++ community,
> >
> > As some of you may remember, I wrote some test suites in
> cppunit last month
> > and I would like to submit them as the beginnings of a common
> C++ test suite
> > as we had discussed then.  however it has a couple of issues I
> am hoping a
> > more experienced common c++ developer or maintainer can help
> with, as I am a
> > gnu autoconfig/automake newbie, I'll admit it. :)  also since I
> typically
> > develop using m$ visual studio 6.0 I'm not that proficient with
> > developing/debugging on the linux environment.
> >
> > My date classes have some tests that are failing now with the
> recent patches
> > submitted that add the new YYYY/MM/DD style formats instead of
> the YYYYMMDD
> > formats.  whether the interface is changing or whether the
> tests need to be
> > updated to the new format needs to be determined.
> >
>
> 	I would expect Marcelo's opinion, though I think that we
> should keep backwards compatibility.
>
> > My persistence tests (pretty extensive), work fine under
> windows, but throw
> > exceptions under linux.  I don't yet know why, and since I
> haven't come to
> > grips with a linux debugger yet (I've been babied by VC++'s gui
> debugger), I
> > can't dig into the reason yet.  I have another test case under
> windows, but
> > am not going to add it at this time as it has some linux
> compilation issues.
> >
> > There are generalized test classes for the digest tests, however I could
> > never seem to get decent results out of the SHA digests on
> windows, they may
> > work fine under linux, though the testcase registration macros
> are commented
> > out right now.
> >
> > There are also tests for the urlstring file including base64
> encode decode.
> >
> > I have attached a zip file containing a zipped directory called
> ccxx_tests
> > designed to be uncompressed under the commoncpp2 main
> directory.  eventually
> > I would hope the contents would live in tests instead, and all
> the existing
> > tests changed to components of the cppunit test suites, or something
> > similar.
> >
>
> 	Um, I would like the new tests to go directly into tests/, and
> integrate the old tests as soon as possible. Since there seems to be a
> few issues to solve, I would put the new tests there now for the
> development branch, and, when these issues are clarified, commit the
> new test suite for the stable releases. This would be a very
> interesting new feature for 1.0.9. It would also be interesting to
> include the VC++ project files for the test suite.
>
> 	Do you agree with this plan?
>
> > I have also attached a diff of the changes I made to the
> configure.in and
> > Makefile.am to get it to build for me on my linux machine,
> however, I didn't
> > get the check for cppunit to work to my liking, and am sure the
> changes I
> > made were not ideal.  hopefully someone with more expertise in
> > autoconf/automake can make better changes there.
> >
> > Anyway, I wanted to get this out there and in cvs so others can
> contribute
> > if wanted, and so we would have somewhat of a base to start/learn from.
> > Also, it would be a good habit for contributors to get the hang
> of adding
> > suites/testcases while finding/resolving bugs and making
> enhancements. This
> > way some inadvertant sideffects can hopefully be avoided.
> >
>
> 	I totally agree.
>
> > Cheers,
> >
> > chad
> >
> > P.S. I spoke with albert today, and he will be contributing his
> testcases
> > etc a bit later.  Feel free to contact me if you have questions,
> > comments/suggestions, or if you have trouble compiling it.  I will
> > contribute new suites/testcases as I develop them.
>
>
>
> > _______________________________________________
> > 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

--Boundary_(ID_qjavf2ykReG8ieF6fJuC0w)
Content-type: application/x-zip-compressed; name=ccxx_tests_msvc_project.zip
Content-transfer-encoding: base64
Content-disposition: attachment; filename=ccxx_tests_msvc_project.zip

UEsDBAoAAAAAAIdaPi4AAAAAAAAAAAAAAAARAAAAY29tbW9uY3BwMi93aW4zMi9QSwMECgAAAAAA
hlo+LgAAAAAAAAAAAAAAABcAAABjb21tb25jcHAyL3dpbjMyL0RlYnVnL1BLAwQKAAAAAAB8Wj4u
AAAAAAAAAAAAAAAAFwAAAGNvbW1vbmNwcDIvd2luMzIvdGVzdHMvUEsDBBQAAAAIAElJPi5R2tAn
FgQAANUQAAApAAAAY29tbW9uY3BwMi93aW4zMi90ZXN0cy9jY3h4X3Rlc3RzdWl0ZS5kc3DtV21v
2kgQ/h4p/2Hq3oek6gGFKmrj4yTAhkMNLwr0eukXtF4PZhPba+2uE/Lvb2xjAnmBXO566odIGHZn
Zp95dnb8YL+FgeBKajk34OA1hjJBBROT+kLCWMlL5Aa6IkT4FYYswqbF+XI5M6iNToVBi+xjxq9Y
gDC6iVE1f/v4++HB212wPaQ4ZtCHdipCP4d/D12pImbgT1RayBhOKrVahvPuHTgjGI6m4Dr9KU0P
DzLztHXem16MXbC+ibhRh6Plp5Nj6MhYS+LaSpJQcGYIyILasvah1siWdbq95jZ9Yl+sd9BLg8OD
NwN3Mmn1XJguhAb6xNIAg2sWCh8idoVz4lqBqQQvp26ysGRVplSLOIDhoPXFfb8BlWqkOAR3mUhl
YLBCAS6jiMU+ZJdK440VG8McDapzuFf3CpGxKo+vuZApcBaDTpCL+S3x5zKeiyBVeUXgZoFxljFe
091Y7N2CT/xyX8Y6YnSOQJUDWpkZStqhiKkSdGqASxYlIZ6+YAcZ8P2W2j4T63HUsdRaeFkVF1Jw
1DAnItvbZOopSk8lPMcQmaaePvLox892vLe9jp+BW2zkpahFw7cxEHF5R2aG8floDK0wlDdjVJ18
5w4mGPsYc0EFqa2DJpzPsoXZ/QuWtWU/k5yFY2YWuaMzHjd5WMElHh6cTzpNxYsxsel3Aaxfjui8
ji1oNvfWsGCd52m3Ji581TgbdDsbtNbmvDyzM+EppraZ5yGj1CSpmTlCgXWHvhnRjw2qCH1BorIr
bspUgCukO9dDZrtJ7eTzDCoPWLQcp+BH5YdqLEMZSKh+a0C19xdUR3WoOtQx/WGjbuXDoeO2v/aK
8awzGk5GZ+5qNmh3JjS8oHVdB6q8hP9xyDlx6hWohqS0H2ufoeqvgcqgp/3tSadRb3qaZ+JaNNsG
bu4tia8928az/vALQZAcXT1YX/jgClWMYaNeCYWXybFaDQNfrEY3ItaJlGE+IYXzw2DlYf41S8ow
vcCwxKFb9m7EUlPCp8IvrL7HywAa8mQ1+bnYrJtCp56+1QajU77SoypJ/4JE/rTf+HRSlvW1ov9d
RUlV3bOJ+1xlLf8OX6yrH57W1RJ7t6o+FvVvNPWO0A4ue2n8Ez2NCuX73if18++r3+zZ6tf7DjvF
9YekeVxpZ3uUdvaqtD+/LvhZR2/LA1QT3zO3CZ5qTMyr/P5PZc40eeiQJG8+dRcKU1iKh+i9D797
Au8krMjQUzJNwJrIVHHMX4j1ptI7OGdpaGbkIDEk1CSxuU3QtuI2va7ZypZ+aAu6Fsml7TGTY7v0
mpYjP0j0BzKfgPYmWhBeYi8o0SKyRRzugT1H/cwdCC5tnirbixKbuoH2UafL2J6IbRVoOxBz+zIJ
6ML862HibFIeTDFbvxz9DVBLAwQUAAAACAC9WT4usaoy6VEEAAD8EAAAKQAAAGNvbW1vbmNwcDIv
d2luMzIvdGVzdHMvY2N4eF90ZXN0c3VpdGUucGxnzVhbb+JGFH5H4j9MyEsrNXYh3bSyotVuDFtF
Ik0EJF2pVGiwD2Y24xl3Lgv0ob+9Z7DZ7GJjTPpSHsxcvnOZ78yxz8z10qT8bbt1PZfxxv1nCtzf
svv2xjIek6FMrn3subFLfF5U/EIpFiyxihomRUCiaL2eGdBGW2aAXJDfmbjskT7MbVIljqr9rW5n
IZRpSgXaZQJ0MR4qQNUiIQbSTCqqNmTBOJBOGEz79+Hj3eCf7jTaULQ5Hd6H74dj7E8QOx2NHwY3
HzyTZh2yYmZJIikMCKPbrT/arWdQAvhlz+NsTqwGVTSTmBWtFRM6k5JvO5FMY54UMzT+TLMdTC+B
7/RIDi8tas1OvWVxPhrPox0Am1FWdP5XzkRZZgUz8SzmuTlfSC4TSXxt53qjMRABUqlRK/GZiBSk
yCrlwQY08bN4HnS24fa/3QseznSIH7sp4qc0WmKUg9vLX66IL60JOp7nV8rBGjpbvWaTQaAhM6Td
8qZb7PQF68n5p5fxMU0zDvfzTxCZqpmxnVdNTlDTrI+bqWqYJfhXMTEQCS7l2wnn0swqro3CzVvl
wW8yLmSmD0o6V/Q0nGJoUykwBL3pymXOl2XC2vS2cWuIT4Td4f/8KouiIsU4ekw6+Hx2/JJ3p2RT
nqz31mTWuPyO5apIVkzcZ7dcz/uviRt2vTk1VYn7DqKlJHKxaEjE/l4iFxr4wg3VMXOKk+3WyArh
dIThx4/E7QkydubaLVVMuC3lxj1nd8xc/H8FowkyRWpR4x1qcBQ2e88Nvkdw8oNUKTV1ym/1E+Us
roOgf64/G293cBOkYSk+jiBhC8W0sJGZmbQOfZ9B/lnZ5ylcQvSsbZpn5Bf8ZJOxiPJHTRNoJoEf
r9wTNNJMYpBmZoNe0mbwcUo5vwPd3KUhVQmcJHHDBCZXc59GcIuvd4bx/5s2X/gDgwhWTJecGoXd
qxMCUQGvi0IF/GAIKrB1/FfA68ivgB9mvgJ8jPYKkRrOL3sncV6C13NegtdwXsLWc16C13Negtdx
XgIf57wkcojzu/6b5oyXwTV8l8GH2C4ja7gug2uYLoMP8lyGHmG5LHCI47yQeoEplqLez7D//t/D
jegq97YeNp4Mn7BYkOoorA9/2SO+IeqOZvUYPM7gp3md15n10Nz/iYJ9s4+jYf4B3oPeUA1XPw1E
hFVkH9zzJMGJzCdPUpB3n0DpcpDL6F16KH6SkUJsgvXuK9aYV0OvFC7i9UrpBxrH2H8AtSiH+yC8
O15K1Rjd+xrdbp2ff6CMWwV4Uo/y1LPiWciVOD8nARkoJVW75ZQQQVMIDlWO7VZEbbI0O2kC6wiP
WajPWWm3CiuanJ2dbYvdgLz5mRCys26kO/6R7suQDsiP2Nt6gO1uu7VtomKIbF5uB65Ox6ODnuZn
SizZozR2FbqXW82PGSPQlpvdbUBVOY92wSn/Tn//A1pdUeVIxJ67WyiuNPzdFYdf3Hn8C1BLAwQK
AAAAAAAmXj4uAAAAAAAAAAAAAAAACwAAAGNvbW1vbmNwcDIvUEsBAhQACgAAAAAAh1o+LgAAAAAA
AAAAAAAAABEAAAAAAAAAAAAQAP9BAAAAAGNvbW1vbmNwcDIvd2luMzIvUEsBAhQACgAAAAAAhlo+
LgAAAAAAAAAAAAAAABcAAAAAAAAAAAAQAP9BLwAAAGNvbW1vbmNwcDIvd2luMzIvRGVidWcvUEsB
AhQACgAAAAAAfFo+LgAAAAAAAAAAAAAAABcAAAAAAAAAAAAQAP9BZAAAAGNvbW1vbmNwcDIvd2lu
MzIvdGVzdHMvUEsBAhQAFAAAAAgASUk+LlHa0CcWBAAA1RAAACkAAAAAAAAAAQAgALaBmQAAAGNv
bW1vbmNwcDIvd2luMzIvdGVzdHMvY2N4eF90ZXN0c3VpdGUuZHNwUEsBAhQAFAAAAAgAvVk+LrGq
MulRBAAA/BAAACkAAAAAAAAAAQAgALaB9gQAAGNvbW1vbmNwcDIvd2luMzIvdGVzdHMvY2N4eF90
ZXN0c3VpdGUucGxnUEsBAhQACgAAAAAAJl4+LgAAAAAAAAAAAAAAAAsAAAAAAAAAAAAQAP9BjgkA
AGNvbW1vbmNwcDIvUEsFBgAAAAAGAAYAsAEAALcJAAAAAA==

--Boundary_(ID_qjavf2ykReG8ieF6fJuC0w)--



From MAILER-DAEMON Thu Jan 30 16:03:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eLpK-0005za-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 16:02:26 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eLgb-00012X-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 15:53:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eLfU-0000an-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 15:52:19 -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 18eLe3-0000M9-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 15:50:48 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H9J00B65OKLA9@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 30 Jan 2003 12:50:45 -0800 (PST)
Date: Thu, 30 Jan 2003 12:50:45 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20030130113024.GA3841@bulbasaur.rediris.es>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-id: <NBBBJJODBJBNJFNIDDCNOEHNDEAA.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: multipart/mixed; boundary="Boundary_(ID_4AoZkCXahvgdFs0Tj/48Kg)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
cc: bug-commoncpp@gnu.org
Subject: RE: urlstring testing/enhancement
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, 30 Jan 2003 21:02:25 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_4AoZkCXahvgdFs0Tj/48Kg)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

(snip)
>
> 	I guess there is no good solution for this. The first copy
> seems unavoidable and the second one, as far as I know, could only be
> avoided if the core routine operated over a string object instead of
> the array of char, but that would be a lot worse. Well, after all, you
> loose some performance, but you can save significant space :).
>
> 	Also, what about adding an encode method that takes a string
> object as argument.

Albert suggested the same thing.  I'm going to leave it as it is for now,
and maybe add an overloaded pair to allow the string ref to be passed in.
I've attached a patch to urlstring with the current code changes (It will be
required to compile the ccxx_tests without modifying the urlstring test
cases)

,Chad

--Boundary_(ID_4AoZkCXahvgdFs0Tj/48Kg)
Content-type: application/octet-stream; name=urlstring_stdstring.patch
Content-transfer-encoding: quoted-printable
Content-disposition: attachment; filename=urlstring_stdstring.patch

Index: src/urlstring.cpp
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/commoncpp/commoncpp2/src/urlstring.cpp,v
retrieving revision 1.4
diff -u -r1.4 urlstring.cpp
--- src/urlstring.cpp	17 Jan 2003 11:51:36 -0000	1.4
+++ src/urlstring.cpp	30 Jan 2003 20:46:50 -0000
@@ -231,6 +231,78 @@
 	return ret;
 }
=20
+/** @relates URLStream
+ * Encode a STL string using base64 coding into a STL string
+ * @return base 64 encoded string
+ * @param src source string
+ */
+CCXX_EXPORT(std::string) b64Encode(const std::string& src)
+{
+  size_t limit =3D (src.length()+2)/3*4+1;  // size + null must be =
included
+  char* buffer =3D new char[limit];
+
+  unsigned size =3D b64Encode((const unsigned char *)src.c_str(), =
src.length(), buffer, limit);
+  buffer[size] =3D '\0';
+
+  std::string final =3D string(buffer);
+  delete buffer;
+  return final;
+}
+
+/** @relates URLStream
+ * Decode a STL string using base64 coding into an STL String.
+ * Destination size should be at least strlen(src)/4*3.
+ * Destination are not string terminated (It's just a octet stream).
+ * @return decoded string
+ * @param src     source string
+ */
+CCXX_EXPORT(std::string) b64Decode(const std::string& src)
+{
+  size_t limit =3D src.length()/4*3;
+  unsigned char* buffer =3D new unsigned char[limit+1];
+
+  unsigned size =3D b64Decode(src.c_str(), buffer, limit);
+  buffer[size] =3D '\0';
+
+  std::string final =3D string((char*)buffer);
+  delete buffer;
+  return final;
+}
+
+/** @relates URLStream
+ * Encode a octet stream using base64 coding into a STL string
+ * @return base 64 encoded string
+ * @param src     source buffer
+ * @param srcsize source buffer size
+ */
+CCXX_EXPORT(std::string) b64Encode(const unsigned char *src, size_t =
srcsize)
+{
+  size_t limit =3D (srcsize+2)/3*4+1;
+  char* buffer =3D new char[limit];
+
+  unsigned size =3D b64Encode(src, srcsize, buffer, limit);
+  buffer[size] =3D '\0';
+
+  std::string final =3D string(buffer);
+  delete buffer;
+  return final;
+}
+
+/** @relates URLStream
+ * Decode an STL string encoded using base64.
+ * Destination size should be at least strlen(src)/4*3.
+ * Destination are not string terminated (It's just a octet stream).
+ * @return number of octets written into destination buffer
+ * @param src     source string
+ * @param dst     destination octet buffer
+ * @param dstsize destination buffer size
+ */
+CCXX_EXPORT(size_t) b64Decode(const std::string& src,
+  unsigned char *dst, size_t dstsize)
+{
+  return b64Decode(src.c_str(), dst, dstsize);
+}
+
 #ifdef	CCXX_NAMESPACES
 };
 #endif
Index: include/cc++/urlstring.h
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/urlstring.h,v
retrieving revision 1.2
diff -u -r1.2 urlstring.h
--- include/cc++/urlstring.h	16 Nov 2002 13:19:08 -0000	1.2
+++ include/cc++/urlstring.h	30 Jan 2003 20:46:51 -0000
@@ -50,6 +50,8 @@
 #include <cc++/config.h>
 #endif
=20
+#include <string>
+
 #ifdef	CCXX_NAMESPACES
 namespace ost {
 #endif
@@ -118,6 +120,42 @@
  * @param dstsize destination buffer size
  */
 CCXX_EXPORT(size_t) b64Decode(const char *src,
+		unsigned char *dst, size_t dstsize);
+
+/** @relates URLStream
+ * Encode a STL string using base64 coding into a STL string
+ * @return base 64 encoded string
+ * @param src source string
+ */
+CCXX_EXPORT(std::string) b64Encode(const std::string& src);
+
+/** @relates URLStream
+ * Decode a STL string using base64 coding into an STL String.
+ * Destination size should be at least strlen(src)/4*3.
+ * Destination are not string terminated (It's just a octet stream).
+ * @return decoded string
+ * @param src     source string
+ */
+CCXX_EXPORT(std::string) b64Decode(const std::string& src);
+
+/** @relates URLStream
+ * Encode a octet stream using base64 coding into a STL string
+ * @return base 64 encoded string
+ * @param src     source buffer
+ * @param srcsize source buffer size
+ */
+CCXX_EXPORT(std::string) b64Encode(const unsigned char *src, size_t =
srcsize);
+
+/** @relates URLStream
+ * Decode a string using base64 coding.
+ * Destination size should be at least strlen(src)/4*3.
+ * Destination are not string terminated (It's just a octet stream).
+ * @return number of octets written into destination buffer
+ * @param src     source string
+ * @param dst     destination octet buffer
+ * @param dstsize destination buffer size
+ */
+CCXX_EXPORT(size_t) b64Decode(const std::string& src,
 		unsigned char *dst, size_t dstsize);
=20
 #ifdef	CCXX_NAMESPACES

--Boundary_(ID_4AoZkCXahvgdFs0Tj/48Kg)--



From MAILER-DAEMON Thu Jan 30 16:07:52 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eLqI-0006d1-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 16:03:26 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eLiQ-0002RY-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 15:55:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eLi9-0002DU-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 15:55:03 -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 18eLfW-0000b5-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 15:52:18 -0500
Received: from falcon ([129.101.69.98]) by mailB.its.uidaho.edu (Go Vandals!)
 with ESMTPP id <0H9J00BKNON4A9@mailB.its.uidaho.edu> for
 bug-commoncpp@gnu.org; Thu, 30 Jan 2003 12:52:17 -0800 (PST)
Date: Thu, 30 Jan 2003 12:52:17 -0800
From: Chad Yates <cyates@uidaho.edu>
In-reply-to: <20030130104845.GB269@bulbasaur.rediris.es>
To: Federico Montesino Pouzols <fedemp@altern.org>
Message-id: <NBBBJJODBJBNJFNIDDCNCEHODEAA.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
cc: albert@dogbert.sdsl.sun.ac.za
cc: bug-commoncpp <bug-commoncpp@gnu.org>
Subject: RE: common C++ test suite
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, 30 Jan 2003 21:03:24 -0000

(snip)
> > I have attached a zip file containing a zipped directory called
> ccxx_tests
> > designed to be uncompressed under the commoncpp2 main
> directory.  eventually
> > I would hope the contents would live in tests instead, and all
> the existing
> > tests changed to components of the cppunit test suites, or something
> > similar.
> >
>
> 	Um, I would like the new tests to go directly into tests/, and
> integrate the old tests as soon as possible. Since there seems to be a
> few issues to solve, I would put the new tests there now for the
> development branch, and, when these issues are clarified, commit the
> new test suite for the stable releases. This would be a very
> interesting new feature for 1.0.9. It would also be interesting to
> include the VC++ project files for the test suite.
>
> 	Do you agree with this plan?

Sounds good to me, as an official developer I would expect you could move
the source/Makefile.am I sent you to tests (to go along with the msvc++
project I sent) and make any appropriate changes to the build system.

Let me know when I should pull a new copy of commoncpp2 with the changes.

(snip)

,Chad




From MAILER-DAEMON Thu Jan 30 16:17:30 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eM3u-0004GS-00
	for mharc-bug-commoncpp@gnu.org; Thu, 30 Jan 2003 16:17:30 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eM3r-0004FS-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 16:17:27 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eM3p-0004E5-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 16:17:26 -0500
Received: from mx2.magma.ca ([206.191.0.250])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18eM3p-0004DZ-00
	for bug-commoncpp@gnu.org; Thu, 30 Jan 2003 16:17:25 -0500
Received: from mail1.magma.ca (mail1.magma.ca [206.191.0.252])
	by mx2.magma.ca (Magma Relay Server) with ESMTP id h0ULHGuP016565; 
	Thu, 30 Jan 2003 16:17:22 -0500
Received: from igough (ottawa-hs-64-26-156-25.s-ip.magma.ca [64.26.156.25])
	by mail1.magma.ca (Magma's Mail Server) with ESMTP id h0ULH5Jq019759;
	Thu, 30 Jan 2003 16:17:11 -0500 (EST)
From: "Ian Gough" <igough@gridiron-networks.com>
To: "'Ari Johnson'" <ariston@cs.und.edu>
Date: Thu, 30 Jan 2003 16:17:05 -0500
Message-ID: <002f01c2c8a4$f70e0c80$0c02a8c0@gridironnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <Pine.GSO.4.10.10301291255170.8922-100000@agassiz.cs.und.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
cc: bug-commoncpp@gnu.org
Subject: RE: TCPSession bug? 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: Thu, 30 Jan 2003 21:17:28 -0000

> -----Original Message-----
> From: Ari Johnson [mailto:ariston@cs.und.edu] 
> Sent: Wednesday, January 29, 2003 1:57 PM
> To: Ian Gough
> Cc: bug-commoncpp@gnu.org
> Subject: Re: TCPSession bug? Questions
> 
> 
> 
> I use 'tcpstream' and have found that the '!' (not) operator 
> works well to determine if it is connected:
>   tcpstream stream;
>   bool disconnected = !stream;
>   bool connected = !!stream;
> 
> Ari Johnson
> 

The docs imply that tcpstream is not threadsafe, which is no good for my
app. I have tried using TCPSession::isConnected() but under the
circumstances shown in the test app, isConnected() always returns true,
at least running on Windows it does.

Ari, have you tried determining if a disconnect has occurred on Windows
using tcpstream?

> On Wed, 29 Jan 2003, Ian Gough wrote:
> 
> > I need some help determining if TCPSession is working 
> correctly. The 
> > included code was run on Windows. It is a slight 
> modification of the 
> > tcpthread.cpp demo. If you build it as-is, it creates a 
> server socket 
> > that accepts a connection on port 4096. When you connect to it with 
> > telnet, it prints out banner messages and then echos back 
> the decimal 
> > value of any key you press in the telnet session, except 
> for 'q' which 
> > causes the connection to close. It is set up to (in theory) throw 
> > exceptions in the session thread using
> >  
> >  setException( Thread::throwException );
> >  
> > If you kill telnet while in the session, no exception gets 
> thrown to 
> > tell the server that the connection has closed. Also, the 
> read of the 
> > tcp stream returns the last thing sent on the socket from 
> telnet and 
> > the read thinks that it is getting a continuous stream of 
> characters.
> >  
> > 1) Should an exception be thrown on connection closure?
> > 2) If not, how do you determine if the connection is closed or not?
> > 
> > Also, if you uncomment line 140 and comment out line 141 so 
> that the 
> > session thread is detached instead of started, you get no output on 
> > telnet from the session. This doesn't seem particularly 
> useful, as it 
> > appears to be a socket set up with no ability to send data upon it.
> > 
> 
> 




From MAILER-DAEMON Fri Jan 31 04:04:33 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eX5H-0002CR-00
	for mharc-bug-commoncpp@gnu.org; Fri, 31 Jan 2003 04:03:39 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eX4q-0001R9-00
	for bug-commoncpp@gnu.org; Fri, 31 Jan 2003 04:03:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eX3a-0000ay-00
	for bug-commoncpp@gnu.org; Fri, 31 Jan 2003 04:02:01 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18eX31-0007hC-00
	for bug-commoncpp@gnu.org; Fri, 31 Jan 2003 04:01:19 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 18eX41-0004S7-00; Fri, 31 Jan 2003 10:02:21 +0100
Date: Fri, 31 Jan 2003 10:02:20 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ian Gough <igough@gridiron-networks.com>
Message-ID: <20030131090220.GA253@bulbasaur.rediris.es>
Mail-Followup-To: Ian Gough <igough@gridiron-networks.com>,
	'David Sugar' <dyfet@ostel.com>,
	'Federico Montesino Pouzols' <fedemp@altern.org>,
	'bug-commoncpp' <bug-commoncpp@gnu.org>
References: <200301301222.33979.dyfet@ostel.com>
	<002201c2c88e$06cd3c20$0c02a8c0@gridironnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002201c2c88e$06cd3c20$0c02a8c0@gridironnetworks.com>
User-Agent: Mutt/1.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: 'Federico Montesino Pouzols' <fedemp@altern.org>
cc: 'bug-commoncpp' <bug-commoncpp@gnu.org>
cc: 'David Sugar' <dyfet@ostel.com>
Subject: Re: Building CC++ on Mac OS X
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, 31 Jan 2003 09:03:37 -0000


	Ah, I have replaced the test with a call to AC_CHECK_FUNCS,
which I suspect is what I should have done first instead of using
AC_TRY_COMPILE. After all, CHECK_FUNCS is the predefined autoconf
macro for this issues.

On Thu, Jan 30, 2003 at 01:33:00PM -0500, Ian Gough wrote:
> Wouldn't the C/C++ issue be a general problem for ANY test that uses
> AC_TRY_COMPILE?. If you use the C compiler, autoconf cannot detect
> missing functionality properly.
> 
> Will somebody be making this change or is there an expectation that I
> would make the change? Not that I know what file in which to make any
> changes. :-)
> 
> > -----Original Message-----
> > From: David Sugar [mailto:dyfet@ostel.com] 
> > Sent: Thursday, January 30, 2003 12:23 PM
> > To: Ian Gough; 'Federico Montesino Pouzols'
> > Cc: 'bug-commoncpp'
> > Subject: Re: Building CC++ on Mac OS X
> > 
> > 
> > The AC_LANG_CPP and AC_LANG_RESTORE options will need to be 
> > used in the 
> > section that tests for this function.  This will make sure 
> > they are tested 
> > with the local machines C++ compiler rather than the C compiler....
> > 
> > On Thursday 30 January 2003 11:41, Ian Gough wrote:
> > > OK, found the problem.
> > >
> > > If I call the small sched_getscheduler test program test.c, then it 
> > > compiles with no errors or warnings. If I call the same program but 
> > > named test.cpp, then gcc complains about an undefined identifier.
> > >
> > > The autoconf test creates conftest.c when testing for 
> > > sched_getscheduler (and probably other functions too) and so the 
> > > compiler never complains about missing functions. Using the 
> > -std=c99 
> > > options to gcc causes warnings to be reported on the c files.
> > >
> > > [commoncpp2 613] cat test.c
> > > #include <sched.h>
> > >
> > > int main ()
> > > {
> > >   int policy;
> > >   policy = sched_getscheduler(0);
> > >   return 0;
> > > }
> > > [commoncpp2 614] cat test.cpp
> > > #include <sched.h>
> > >
> > > int main ()
> > > {
> > >   int policy;
> > >   policy = sched_getscheduler(0);
> > >   return 0;
> > > }
> > > [commoncpp2 615] gcc -c -g -O2 test.cpp
> > > test.cpp: In function `int main()':
> > > test.cpp:6: `sched_getscheduler' undeclared (first use this 
> > function)
> > > test.cpp:6: (Each undeclared identifier is reported only 
> > once for each 
> > > function
> > >    it appears in.)
> > > [commoncpp2 616] gcc -c -g -O2 test.c
> > > [commoncpp2 617]
> > > [commoncpp2 618] gcc -c -g -O2 -std=c99 test.c
> > > test.c: In function `main':
> > > test.c:6: warning: implicit declaration of function 
> > > `sched_getscheduler'
> > >
> > > > -----Original Message-----
> > > > From: Federico Montesino Pouzols 
> > > > [mailto:fedemp@bulbasaur.rediris.es] On Behalf Of 
> > Federico Montesino 
> > > > Pouzols
> > > > Sent: Wednesday, January 29, 2003 4:18 PM
> > > > To: Ian Gough
> > > > Cc: 'bug-commoncpp'
> > > > Subject: Re: Building CC++ on Mac OS X
> > > >
> > > >
> > > >
> > > > 	Yes, the semaphore stuff is still pending, I expect to
> > > > fix it soon. As for the sched_getscheduler issue, it is 
> > weird that 
> > > > it is detected, since the test is like this:
> > > >
> > > >         AC_TRY_COMPILE(
> > > >                 [#include <sched.h>],
> > > >                 [
> > > >                 int policy;
> > > >                 policy = sched_getscheduler(0);
> > > >                 ],
> > > >                 [AC_DEFINE(HAVE_SCHED_GETSCHEDULER)])
> > > >
> > > > 	Could you try to compile on your system a simple C
> > > > program like the one above? It should not compile, but it 
> > seems that 
> > > > autoconf is able to succesfully compile it.
> > > >
> > > > On Mon, Jan 27, 2003 at 11:10:46AM -0500, Ian Gough wrote:
> > > > > Grabbed a new CVS snapshot this morning and tried to build
> > > >
> > > > after these
> > > >
> > > > > changes and I still get compilation failures:
> > > > >
> > > > > g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src 
> > > > > g++ -DCCXX_EXPORT_LIBRARY
> > > > > -I/usr/local/include -D_GNU_SOURCE -Wall -ansi -pedantic
> > > >
> > > > -I../include
> > > >
> > > > > -c thread.cpp -MT thread.lo -MD -MP -MF .deps/thread.TPlo
> > > >
> > > > -fno-common
> > > >
> > > > > -DPIC -o .libs/thread.lo
> > > > > cc1plus: warning: changing search order for system directory 
> > > > > "/usr/local/include"
> > > > > cc1plus: warning:   as it has already been specified as 
> > a non-system
> > > > > directory
> > > > > thread.cpp: In constructor `ost::Thread::Thread(int, 
> > long unsigned
> > > > > int)':
> > > > > thread.cpp:536: `sched_getscheduler' undeclared (first use this
> > > > > function)
> > > > > thread.cpp:536: (Each undeclared identifier is reported
> > > >
> > > > only once for
> > > >
> > > > > each
> > > > >    function it appears in.)
> > > > > thread.cpp:554: `sched_getparam' undeclared (first use this
> > > >
> > > > function)
> > > >
> > > > > make[1]: *** [thread.lo] Error 1
> > > > > make: *** [all-recursive] Error 1
> > > > >
> > > > > Checking if HAVE_SCHED_GETSCHEDULER is defined in one of the 
> > > > > header files shows that it is defined in config.h for 
> > some reason.
> > > > >
> > > > > [/var/root/src/revgen/xGrid/ccxx 552] grep -r HAVE_SCHED * 
> > > > > acconfig.h:#undef HAVE_SCHED_GETSCHEDULER acconfig.h:#ifdef 
> > > > > HAVE_SCHED_H config.log:#define HAVE_SCHED_H 1 
> > config.log:#define 
> > > > > HAVE_SCHED_GETSCHEDULER 1
> > > >
> > > > config.status:${ac_dA}HAVE_SCHED_H${ac_dB}HAVE_SCHED_H${ac_dC}
> > > > 1${ac_dD}
> > > >
> > > > config.status:${ac_dA}HAVE_SCHED_GETSCHEDULER${ac_dB}HAVE_SCHE
> > >
> > > D_GETSCHED
> > >
> > > > > ULER${ac_dC}1${ac_dD}
> > > >
> > > > config.status:${ac_uA}HAVE_SCHED_H${ac_uB}HAVE_SCHED_H${ac_uC}
> > > > 1${ac_uD}
> > > >
> > > > config.status:${ac_uA}HAVE_SCHED_GETSCHEDULER${ac_uB}HAVE_SCHE
> > >
> > > D_GETSCHED
> > >
> > > > > ULER${ac_uC}1${ac_uD}
> > > > > configure:#define HAVE_SCHED_GETSCHEDULER 1 
> > > > > include/cc++/config.h:#define HAVE_SCHED_GETSCHEDULER 1 
> > > > > include/cc++/config.h:#define HAVE_SCHED_H 1 
> > > > > include/cc++/config.h:#ifdef HAVE_SCHED_H 
> > > > > include/cc++/config.tmp:#define HAVE_SCHED_GETSCHEDULER 1 
> > > > > include/cc++/config.tmp:#define HAVE_SCHED_H 1 
> > > > > include/cc++/config.tmp:#ifdef HAVE_SCHED_H 
> > > > > include/config.h:#define HAVE_SCHED_GETSCHEDULER 1 
> > > > > include/config.h:#define HAVE_SCHED_H 1 include/config.h:#ifdef 
> > > > > HAVE_SCHED_H include/config.h.in:#undef HAVE_SCHED_GETSCHEDULER
> > > > > include/config.h.in:#undef HAVE_SCHED_H
> > > > > include/config.h.in:#ifdef HAVE_SCHED_H
> > > > > m4/ost_pthread.m4:
> > > >
> > > > [AC_DEFINE(HAVE_SCHED_GETSCHEDULER)])
> > > >
> > > > > m4/ost_pthread.m4:dnl #undef HAVE_SCHED_GETSCHEDULER 
> > > > > m4/ost_pthread.m4:dnl #ifdef HAVE_SCHED_H src/thread.cpp:#ifdef 
> > > > > HAVE_SCHED_GETSCHEDULER src/thread.cpp:#endif // ifdef 
> > > > > HAVE_SCHED_GETSCHEDULER
> > > > >
> > > > > But /usr/include/sched.h shows that there is no
> > > >
> > > > sched_getscheduler()
> > > >
> > > > > function.
> > > > >
> > > > > #ifndef _SCHED_H_
> > > > > #define _SCHED_H_
> > > > >
> > > > > #include <pthread_impl.h>
> > > > >
> > > > > /*
> > > > >  * Scheduling paramters
> > > > >  */
> > > > > #ifndef __POSIX_LIB__
> > > > > struct sched_param { int sched_priority;  char 
> > > > > opaque[__SCHED_PARAM_SIZE__]; }; #endif
> > > > >
> > > > > extern int sched_yield(void);
> > > > > extern int sched_get_priority_min(int);
> > > > > extern int sched_get_priority_max(int);
> > > > > #endif /* _SCHED_H_ */
> > > > >
> > > > > I grepped for sched_getscheduler and turned up no hits, so I am 
> > > > > not sure why the autoconf system thinks that it exists.
> > > > >
> > > > > I then defined __FreeBSD__ to get around this problem, but ran 
> > > > > into another compile problem.
> > > > >
> > > > > g++ -DHAVE_CONFIG_H -I. -I. -I../include -D__FreeBSD__ -I../src
> > > > > -DCCXX_EXPORT_LIBRARY -I/usr/local/include -D_GNU_SOURCE
> > > >
> > > > -Wall -ansi
> > > >
> > > > > -pedantic -I../include -c semaphore.cpp -MT semaphore.lo
> > > >
> > > > -MD -MP -MF
> > > >
> > > > > .deps/semaphore.TPlo  -fno-common -DPIC -o .libs/semaphore.lo
> > > > > cc1plus: warning: changing search order for system directory 
> > > > > "/usr/local/include"
> > > > > cc1plus: warning:   as it has already been specified as 
> > a non-system
> > > > > directory
> > > > > /usr/include/sys/sem.h: In destructor `virtual
> > > > > ost::Semaphore::~Semaphore()':
> > > > > /usr/include/sys/sem.h:242: too few arguments to function `int 
> > > > > ost::semctl(int,
> > > > >    int, int, ost::semun)'
> > > > > semaphore.cpp:100: at this point in file
> > > > > /usr/include/sys/sem.h: In member function `int
> > > > > ost::Semaphore::getValue()':
> > > > > /usr/include/sys/sem.h:242: too few arguments to function `int 
> > > > > ost::semctl(int,
> > > > >    int, int, ost::semun)'
> > > > > semaphore.cpp:126: at this point in file
> > > > > make: *** [semaphore.lo] Error 1
> > > > >
> > > > > Mac OS X does not seem to have SYSV semaphores and an
> > > >
> > > > incomplete set
> > > >
> > > > > of POSIX semaphore functions. It does NOT have sem_init and 
> > > > > sem_destroy, but it does have sem_open and sem_close.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Federico Montesino Pouzols 
> > > > > > [mailto:fedemp@bulbasaur.rediris.es] On Behalf Of Federico 
> > > > > > Montesino Pouzols
> > > > > > Sent: Wednesday, January 22, 2003 3:20 AM
> > > > > > To: Ian Gough
> > > > > > Cc: 'bug-commoncpp'
> > > > > > Subject: Re: Building CC++ on Mac OS X
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	Good, I have commited some modifications that 
> > should fix this 
> > > > > > issue.
> > > > > >
> > > > > > On Tue, Jan 21, 2003 at 09:47:57AM -0500, Ian Gough wrote:
> > > > > > > > 	Um, I have just looked at this and actually there is
> > > > > >
> > > > > > already some
> > > > > >
> > > > > > > > autoconf stuff. Could you confirm if, in the config.h of
> > > > > >
> > > > > > cc++, the
> > > > > >
> > > > > > > > symbol HAVE_SOCKLEN_T is undefined?
> > > > > > >
> > > > > > > It is commented out. From include/cc++/config.h
> > > > > > >
> > > > > > > #define HAVE_INET_ATON 1
> > > > > > > #define HAVE_INET_SOCKETS 1
> > > > > > > #define HAVE_UNIX_SOCKETS 1
> > > > > > > /* #undef HAVE_SOCKLEN_T */
> > > > > > > /* #undef HAVE_SYS_LIBCSYS_H */
> > > > > > > /* #undef HAVE_SYS_STREAM_H */
> > > > > > > /* #undef HAVE_SYS_POLL_H */
> > > > > > > /* #undef HAVE_POLL_H */
> > > > >
> > > > > _______________________________________________
> > > > > 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 MAILER-DAEMON Fri Jan 31 20:34:17 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18emXU-0003jz-00
	for mharc-bug-commoncpp@gnu.org; Fri, 31 Jan 2003 20:33:48 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18emWW-0001Z7-00
	for bug-commoncpp@gnu.org; Fri, 31 Jan 2003 20:32:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18emVV-0007vY-00
	for bug-commoncpp@gnu.org; Fri, 31 Jan 2003 20:31:47 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18emU4-0006dg-00
	for bug-commoncpp@gnu.org; Fri, 31 Jan 2003 20:30:16 -0500
Received: from agassiz
	(IDENT:PtDmccKEPFmWny6fLBro1qFWPh9MPjvw@localhost.localdomain [127.0.0.1])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id h111UCOb010606
	for <bug-commoncpp@gnu.org>; Fri, 31 Jan 2003 19:30:13 -0600
Date: Fri, 31 Jan 2003 19:31:09 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
To: bug-commoncpp@gnu.org
Message-ID: <Pine.GSO.4.10.10301311929240.23478-100000@agassiz.cs.und.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Recommended way of specifying file paths?
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, 01 Feb 2003 01:33:47 -0000


Is there a recommended cross-platform way to specify paths to files that
works on both Windows and *nix, using CommonC++?  Also, would the
CommonC++ File interface be any more or less portable to use than fstream
and friends?

Ari Johnson





