From MAILER-DAEMON Wed Mar 10 23:32:29 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B1GBb-0006Wz-8b
	for mharc-bug-commoncpp@gnu.org; Wed, 10 Mar 2004 21:44:39 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B0Kir-0003TV-E1
	for bug-commoncpp@gnu.org; Mon, 08 Mar 2004 08:23:09 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B0KiF-0003Hy-DH
	for bug-commoncpp@gnu.org; Mon, 08 Mar 2004 08:23:02 -0500
Received: from [193.98.115.211] (helo=bns1.envia-tel.net)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B0KiE-0003GG-DK
	for bug-commoncpp@gnu.org; Mon, 08 Mar 2004 08:22:30 -0500
Received: from mail.wigemic.lpz (gw1.wige-data.de [80.243.44.1])
	by bns1.envia-tel.net (8.12.10/8.12.10) with ESMTP id i28DMOGH009002
	for <bug-commoncpp@gnu.org>; Mon, 8 Mar 2004 14:22:25 +0100
Received: from wige-data.de ([10.1.11.14]) by mail.wigemic.lpz with Microsoft
	SMTPSVC(6.0.3790.0); Mon, 8 Mar 2004 14:22:19 +0100
Message-ID: <404C738B.6050303@wige-data.de>
Date: Mon, 08 Mar 2004 14:22:19 +0100
From: Adib Taraben <taraben.a@wige-data.de>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: CommonC++ Mailingliste <bug-commoncpp@gnu.org>
Content-Type: multipart/mixed; boundary="------------020805000402020602000501"
X-OriginalArrivalTime: 08 Mar 2004 13:22:19.0561 (UTC)
	FILETIME=[62095190:01C40510]
Subject: serial.cpp, proper win32 checks for dev
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2004 13:23:10 -0000

This is a multi-part message in MIME format.
--------------020805000402020602000501
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

  Attached there is a patch to make proper win32 checks
against the file-handle dev.

Also I don't know exactly whether an valid FILE in UNIX is:
dev > 0
or
dev >= 0

This patch is against the serial.cpp version that I
found in
commoncpp2-1.1.0.tar.gz
from sourceforge using following command:
   diff -c serial_org.cpp serial.cpp > devcheck.patch

HTH,

Adib.

--------------020805000402020602000501
Content-Type: text/plain;
 name="devcheck.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="devcheck.patch"

*** serial_org.cpp	Sat Jan 17 11:51:02 2004
--- serial.cpp	Mon Mar  8 13:05:56 2004
***************
*** 118,124 ****
--- 118,128 ----
  
  	open(fname);
  
+ #ifdef	WIN32
+ 	if(INVALID_HANDLE_VALUE == dev)
+ #else
  	if(0 > dev)
+ #endif
  	{
  		error(errOpenFailed);
  		return;
***************
*** 254,260 ****
--- 258,268 ----
  
  void Serial::endSerial(void)
  {
+ #ifdef	WIN32
+ 	if(INVALID_HANDLE_VALUE != dev)
+ #else
  	if(0 < dev)
+ #endif
  #ifdef	WIN32
  	{
  		SetCommState(dev, (DCB *)original);
***************
*** 390,396 ****
--- 398,408 ----
  {
  	Serial::close();
  
+ #ifdef	WIN32
+ 	if(INVALID_HANDLE_VALUE == ser.dev)
+ #else
  	if(ser.dev < 0)
+ #endif
  		return *this;
  
  #ifdef	WIN32
***************
*** 1060,1066 ****
--- 1072,1082 ----
  
  void TTYStream::interactive(bool iflag)
  {
+ #ifdef	WIN32
+ 	if(INVALID_HANDLE_VALUE == dev)
+ #else
  	if(dev < 0)
+ #endif
  		return;
  
  	if(bufsize >= 1)
***************
*** 1305,1311 ****
--- 1321,1331 ----
  	
  	Serial::open(pathname);
  
+ #ifdef	WIN32
  	if(INVALID_HANDLE_VALUE == dev)
+ #else
+ 	if(dev < 0)
+ #endif
  	{
  		error(errOpenFailed);
  		return;

--------------020805000402020602000501--



From MAILER-DAEMON Thu Mar 11 00:58:02 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B1Iwv-0003oE-7C
	for mharc-bug-commoncpp@gnu.org; Thu, 11 Mar 2004 00:41:41 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B0znS-000610-GT
	for bug-commoncpp@gnu.org; Wed, 10 Mar 2004 04:14:38 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B0zmn-0005tk-9R
	for bug-commoncpp@gnu.org; Wed, 10 Mar 2004 04:14:28 -0500
Received: from [193.98.115.211] (helo=bns1.envia-tel.net)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B0zhX-0005As-86
	for bug-commoncpp@gnu.org; Wed, 10 Mar 2004 04:08:31 -0500
Received: from mail.wigemic.lpz (gw1.wige-data.de [80.243.44.1])
	by bns1.envia-tel.net (8.12.10/8.12.10) with ESMTP id i2A98OGH021252;
	Wed, 10 Mar 2004 10:08:24 +0100
Received: from wige-data.de ([10.1.11.14]) by mail.wigemic.lpz with Microsoft
	SMTPSVC(6.0.3790.0); Wed, 10 Mar 2004 10:08:19 +0100
Message-ID: <404EDB5A.9050401@wige-data.de>
Date: Wed, 10 Mar 2004 10:09:46 +0100
From: Adib Taraben <taraben.a@wige-data.de>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: CommonC++ Mailingliste <bug-commoncpp@gnu.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Mar 2004 09:08:19.0518 (UTC)
	FILETIME=[3B16CDE0:01C4067F]
Cc: dyfet@ostel.com
Subject: is this list/project alive
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2004 09:14:40 -0000

Hello,

does no hear for a couple of time.
How is the progress?

Thanks,

Adib.



From MAILER-DAEMON Thu Mar 11 01:13:26 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B1JMn-000892-Hc
	for mharc-bug-commoncpp@gnu.org; Thu, 11 Mar 2004 01:08:25 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B15XT-0005io-7W
	for bug-commoncpp@gnu.org; Wed, 10 Mar 2004 10:22:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B15Ww-0005Ut-Kg
	for bug-commoncpp@gnu.org; Wed, 10 Mar 2004 10:22:30 -0500
Received: from [195.41.178.3] (helo=proinfo.dk)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B15Wv-0005UD-PR
	for bug-commoncpp@gnu.org; Wed, 10 Mar 2004 10:21:57 -0500
Received: from mars.prointra.dk ([148.170.19.5]) by gate1.proinfo.dk with
	ESMTP id <334228>; Wed, 10 Mar 2004 16:22:35 +0100
Received: by mars.prointra.dk with Internet Mail Service (5.5.2650.21)
	id <FRZ2550B>; Wed, 10 Mar 2004 16:21:46 +0100
Message-ID: <CC2F8BD52F20D41184D40040C77A41A10157ECF1@mars.prointra.dk>
From: Byrial Jensen <bje@prosafe.as>
To: "'bug-commoncpp@gnu.org'" <bug-commoncpp@gnu.org>
Date: Wed, 10 Mar 2004 16:21:46 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
Subject: Bug in SocketService
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2004 15:22:31 -0000

Hi,

I had some trouble using SocketService which I think could be caused
by SocketService::count and SocketService::first not being declared
volatile.

These 2 variables are read several times inside a loop in
SocketService::run(), and an optimizing compiler may reduce the
number of actual read accesses or even move the reading out of
the main loop. That would give bad results as the variables may
be changed by other threads calling SocketService::attach() and
SocketService::detach().

I suggest the following patch to fix the problem:

--- include/cc++/socket.h~      Wed Dec 10 10:41:07 2003
+++ include/cc++/socket.h       Wed Mar 10 16:19:47 2004
@@ -2077,8 +2077,8 @@
        class Sync;
        Sync* sync;
 #endif
-       int count;
-       SocketPort *first, *last;
+       int volatile count;
+       SocketPort * volatile first, *last;

        /**
         * Attach a new socket port to this service thread.

Best regards,
Byrial Jensen



From MAILER-DAEMON Fri Mar 12 08:21:26 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B1mbN-0000k3-O1
	for mharc-bug-commoncpp@gnu.org; Fri, 12 Mar 2004 08:21:25 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B1mbJ-0000jS-TF
	for bug-commoncpp@gnu.org; Fri, 12 Mar 2004 08:21:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B1maz-0000gz-Hr
	for bug-commoncpp@gnu.org; Fri, 12 Mar 2004 08:21:20 -0500
Received: from [216.218.222.122] (helo=mail.ostel.com)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B1maz-0000gn-0m
	for bug-commoncpp@gnu.org; Fri, 12 Mar 2004 08:21:01 -0500
Received: by mail.ostel.com (Postfix, from userid 1005)
	id 9DB942F286D; Fri, 12 Mar 2004 05:21:09 -0800 (PST)
Received: from 192.168.1.102 (pool-138-89-95-237.mad.east.verizon.net
	[138.89.95.237]) by mail.ostel.com (Postfix) with ESMTP
	id 010BD2F2867; Fri, 12 Mar 2004 05:21:08 -0800 (PST)
From: David Sugar <dyfet@ostel.com>
To: Adib Taraben <taraben.a@wige-data.de>,
	CommonC++ Mailingliste <bug-commoncpp@gnu.org>
Date: Thu, 11 Mar 2004 20:22:42 -0500
User-Agent: KMail/1.5.3
References: <404EDB5A.9050401@wige-data.de>
In-Reply-To: <404EDB5A.9050401@wige-data.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200403112022.42328.dyfet@ostel.com>
Cc: 
Subject: Re: is this list/project alive
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2004 13:21:23 -0000

Right now we are getting ready to release the 1.1.1 release of Common C++ 2...

David

On Wednesday 10 March 2004 04:09 am, Adib Taraben wrote:
> Hello,
>
> does no hear for a couple of time.
> How is the progress?
>
> Thanks,
>
> Adib.




From MAILER-DAEMON Tue Mar 16 11:18:22 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B3HC0-0001yp-Q9
	for mharc-bug-commoncpp@gnu.org; Tue, 16 Mar 2004 11:13:24 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B3HBh-0001xe-Dx
	for bug-commoncpp@gnu.org; Tue, 16 Mar 2004 11:13:05 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B3HB9-0001sq-Hn
	for bug-commoncpp@gnu.org; Tue, 16 Mar 2004 11:13:03 -0500
Received: from [62.24.128.26] (helo=vmail-2.opaltelecom.net)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B3H80-0001c7-K2
	for bug-commoncpp@gnu.org; Tue, 16 Mar 2004 11:09:16 -0500
Received: from thecko.noc.opaltelecom.net ([62.24.170.129] helo=THECKOLAPTOP)
	by vmail-2.opaltelecom.net with asmtp (Exim 4.22) id 1B3H7p-0005vg-LD
	for bug-commoncpp@gnu.org; Tue, 16 Mar 2004 16:09:05 +0000
Message-ID: <015d01c40b71$00945e70$8106a8c0@dfstest.opaltelecom.co>
From: "Paul Thexton" <pthexton@opaltelecom.co.uk>
To: <bug-commoncpp@gnu.org>
Date: Tue, 16 Mar 2004 16:09:04 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-uvscan-result: clean 1B3H7p-0005vg-LD
Subject: ost::Thread::detach() stability issue
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2004 16:13:22 -0000

Hi,

I've spent the last day or so looking around on this lists' archive, and
also on the savannah site looking for a solution but unfortunatley have
found nothing suitable...

I did however find a post from someone suffering the same problem as me, I
have replied with the following but thought I would post this here as well
in case anyone can enlighten me as to whether I am doing something wrong, or
if it is indeed a bug with commonc++

Basically I have a small application which (right now) is simply accepting a
connection in on a port, printing down a couple of messages to the client
connection and then finishing the thread ....

Unfortunately, the application is randomly (ie I cannot fully replicate the
problem, as in "it happens after x number of connections" etc ...) core
dumping on me, I can force this to happen by launching telnet to the
application port one after the other in quick succession (although this has
happened when the application is running under more "normal" operating
paramters)....

I have analysed the core dump and posted to savannah
(http://savannah.gnu.org/bugs/index.php?func=detailitem&item_id=6057) as
below......

I've come across this exact same error, I'm currently running on :

gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)

commonc++ version is 2-1.1.0

This problem does appear to be entirely random however the only time I can
force it to happen is if I force lots of connections to go through in a
short time ....

The output from the debugger is:

(gdb) bt full
#0 0x403b03be in ost::Thread::detach(ost::Semaphore*) (this=0x805e1f0,
start=0x0) at thread.cpp:789
rtn = 0
#1 0x0804d0d8 in main () at IPXP2.cpp:49
server = {<TCPSocket> = {<Socket> = {_vptr.Socket = 0x8058648, errid =
errSuccess, errstr = 0x0, syserr = 0, flags = {
thrown = false, broadcast = false, route = true, keepalive = false, loopback
= true, multicast = false,
completion = false, linger = false, ttl = 1}, so = 3, state = BOUND}, <No
data fields>}, <No data fields>}
tcp = (myTCPSession *) 0x805e168
addr = {<InetAddress> = {_vptr.InetAddress = 0x80586b8, validator = 0x0,
ipaddr = 0x805e158, addr_count = 1,
hostname = 0x0, static mutex = {_vptr.Mutex = 0x403c61b8, static _debug =
Cannot access memory at address 0x0



The line the debugger believes to have caused the crash is:

788: rtn = pthread_create(&priv->_tid, &priv->_attr,
exec_t(&ccxx_exec_handler), this);
789: if(!rtn && priv->_tid)
790: return 0;
791: return -1;

Since the core file suggests that the value of rtn = 0, then I'm assuming
the problem is with priv->_tid .... is there some kind of mutex needing to
go on here? or is pthread_create() not doing its job properly?

I'm really confused by this error, I really do want to use this threading
model for an application I am writing currently but if I cannot get this
resolved, then I am going to have to revert back to a more basic (and
unmanagable) ansi C implementation.

Thanks if anyone can help!




From MAILER-DAEMON Thu Mar 18 11:25:26 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B3zBb-0007ym-2Y
	for mharc-bug-commoncpp@gnu.org; Thu, 18 Mar 2004 10:11:55 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B3yfl-0001Fx-59
	for bug-commoncpp@gnu.org; Thu, 18 Mar 2004 09:39:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B3yfD-00016x-WB
	for bug-commoncpp@gnu.org; Thu, 18 Mar 2004 09:38:59 -0500
Received: from [213.56.76.234] (helo=mh2.cvf.fr)
	by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.30) id 1B3yeA-0000pi-61
	for bug-commoncpp@gnu.org; Thu, 18 Mar 2004 09:37:22 -0500
Received: from [10.33.99.113] (helo=ms.int33.cvf) by mh2.cvf.fr with esmtp 
	for <bug-commoncpp@gnu.org>id 1B3ye2-0002Dz-00;
	Thu, 18 Mar 2004 15:37:14 +0100
Received: from [127.0.0.1] (helo=beepbeep.dev33.cvf)
	by ms.int33.cvf with esmtp id 1B3ye2-0006e3-00
	for <bug-commoncpp@gnu.org>; Thu, 18 Mar 2004 15:37:14 +0100
Received: by beepbeep.dev33.cvf (Postfix, from userid 503)
	id E148B1A806; Thu, 18 Mar 2004 15:36:57 +0100 (CET)
Sender: lmazardo@cvf.fr
To: bug-commoncpp@gnu.org
X-Face: #wZ#V}4Q$LQxR+z[sn~km1Q"PzS@K(uPAf)t{I~J#+gh,
	^t"s=-12r&8aps4D^u7?_@>PE_ !^4HIF_Zy;%y.
From: Luc Mazardo <Luc.Mazardo@cvf.fr>
Date: 18 Mar 2004 15:36:57 +0100
Message-ID: <m0vfl2b4s6.fsf@beepbeep.dev33.cvf>
Lines: 13
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-complaints-to: abuse@cvf.fr
Subject: Slog use
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Mar 2004 15:11:53 -0000

I use the Slog class and want to log long messages.
Is there a reason why _msgbuf is limited to 128 in src/private.h ?
        char _msgbuf[128];

Buffer Overflow ??

It is possible to extend this area ?

Thanks for your work.

-- 
Luc (dot) Mazardo (at) cvf (dot) fr
	



From MAILER-DAEMON Tue Mar 23 04:12:58 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B5hxx-00068L-Td
	for mharc-bug-commoncpp@gnu.org; Tue, 23 Mar 2004 04:12:57 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B5hxu-00067C-EU
	for bug-commoncpp@gnu.org; Tue, 23 Mar 2004 04:12:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B5hxL-0005xb-9D
	for bug-commoncpp@gnu.org; Tue, 23 Mar 2004 04:12:50 -0500
Received: from [193.98.115.211] (helo=bns1.envia-tel.net)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B5hxK-0005wi-MM
	for bug-commoncpp@gnu.org; Tue, 23 Mar 2004 04:12:18 -0500
Received: from mail.wigemic.lpz (gw1.wige-data.de [80.243.44.1])
	by bns1.envia-tel.net (8.12.10/8.12.10) with ESMTP id i2N9CBGH006289
	for <bug-commoncpp@gnu.org>; Tue, 23 Mar 2004 10:12:11 +0100
Received: from wige-data.de ([10.1.11.14]) by mail.wigemic.lpz with Microsoft
	SMTPSVC(6.0.3790.0); Tue, 23 Mar 2004 10:12:06 +0100
Message-ID: <405FFFC3.6000807@wige-data.de>
Date: Tue, 23 Mar 2004 10:13:39 +0100
From: Adib Taraben <taraben.a@wige-data.de>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: CommonC++ Mailingliste <bug-commoncpp@gnu.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Mar 2004 09:12:06.0442 (UTC)
	FILETIME=[E9B768A0:01C410B6]
Subject: commoncpp does not compile out of the box
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2004 09:12:56 -0000

Hello,

I found a new release in the sourceforge repository :-)

Unfortunaltely it does not compile out of the box for win32:
1. spelling in serial.cpp
void TTYStream::interactive(bool iflag)
{
#ifdef	WIN32
	if(dev == INVALID_FILE_HANDLE)
#else
	if(dev < 0)
#endif

INVALID_FILE_HANDLE must rename to INVALID_HANDLE_VALUE

2. the makefiles requires a win32 subdirectory, which was renamed to w32 
early this year.
I would suggest to go back to the old directory name, which was win32. 
This would be the minimal impact. Otherwise we have to change all the 
makefiles and projectfiles in the repository.


HTH so far,

Adib.



From MAILER-DAEMON Thu Mar 25 11:32:37 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B6XmW-0001dG-I2
	for mharc-bug-commoncpp@gnu.org; Thu, 25 Mar 2004 11:32:36 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B6XmO-0001by-IF
	for bug-commoncpp@gnu.org; Thu, 25 Mar 2004 11:32:28 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B6Xlr-0001Ra-SJ
	for bug-commoncpp@gnu.org; Thu, 25 Mar 2004 11:32:27 -0500
Received: from [66.235.192.199] (helo=host134.ipowerweb.com)
	by monty-python.gnu.org with smtp (Exim 4.30) id 1B6Xlq-0001R5-D9
	for bug-commoncpp@gnu.org; Thu, 25 Mar 2004 11:31:54 -0500
Received: (qmail 62942 invoked from network); 25 Mar 2004 16:34:18 -0000
Received: from unknown (HELO ralphlaptop.ralphdellamorte.com) (64.74.50.140)
	by host134.ipowerweb.com with SMTP; 25 Mar 2004 16:34:18 -0000
Message-Id: <5.1.0.14.0.20040325112924.00badad8@mail.ralphdellamorte.com>
X-Sender: ralph@ralphdellamorte.com@mail.ralphdellamorte.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 25 Mar 2004 11:31:45 -0500
To: bug-commoncpp@gnu.org
From: Ralph Dellamorte <ralph@ralphdellamorte.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: win32 thread class bug
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2004 16:32:29 -0000

I see that this problem has been previously discussed as shown below. I am 
using the latest version commoncpp2-1.1.1 on a windows machine am am having 
this problem. Any help would be appreciated :)

Re: fatal bug in class Thread, thread.cpp line~ 858

--------------------------------------------------------------------------------
From:  David Sugar
Subject:  Re: fatal bug in class Thread, thread.cpp line~ 858
Date:  Sat, 20 Dec 2003 06:34:57 -0500
User-agent:  KMail/1.5.3

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

Actually thats not correct either, since _self is part of the current "Thread"
object.  What would be better, as a temporary solution, is to change "final"
so that it can return a bool, and have it return true when final has deleted
the current object...that way any further processing could be bypassed if
final is true.  Let me think more on this....

On Friday 19 December 2003 08:54 am, Tobias Erbsland wrote:
 > Hello
 >
 > The Thread class has a fatal bug:
 >
 > ==== thread.cpp ==== Line 848 ====
 >       // final can call destructor (that call Terminate)
 >       final();
 >
 >       // test if this class have been deleted
 > #ifdef WIN32
 >       if (_self.getKey() == this)
 > #else
 >       if (ThreadImpl::_self.getKey() == this)
 > #endif
 >       {
 >               if(priv)
 >                       priv->_tid = 0;
 >               joinSem.post();
 >       }
 > ====================================
 >
 > The API documentation suggest to place a "delete this" in the final()
 > method to delete the thread on exit. This implementation is found for
 > example in the TCPSession class.
 >
 > After the final() method, the object could be deleted, so each access to
 > a member of the object is invalid.
 >
 > The C++ compiler from the new .NET edition of the MS Visual Studio
 > (Version 7.0) fills each deleted memory segment with the "word" 0xfeee
 > in debug mode (i don't know why, but that's the fact).
 >
 > The line "if(priv)" is true in this case, and the assignment "priv->_tid
 > = 0" results in an access violation (unix: core dump).
 >
 > IMHO, instead this strange test, there should be a hook in the virtual
 > destructor of the Thread class.
 >
 > regards
 > Tobias





From MAILER-DAEMON Fri Mar 26 10:54:50 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B6tfW-00080A-KY
	for mharc-bug-commoncpp@gnu.org; Fri, 26 Mar 2004 10:54:50 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B6tfU-0007zt-Iq
	for bug-commoncpp@gnu.org; Fri, 26 Mar 2004 10:54:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B6tey-0007vg-Ma
	for bug-commoncpp@gnu.org; Fri, 26 Mar 2004 10:54:47 -0500
Received: from [216.68.248.32] (helo=Milcor21.milacron.com)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B6tSg-0005Y1-Ni
	for bug-commoncpp@gnu.org; Fri, 26 Mar 2004 10:41:34 -0500
Received: from dmeusmail.dmeus.milacron.com ([143.62.132.57]) by
	Milcor21.milacron.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Fri, 26 Mar 2004 10:41:07 -0500
Received: by dmeusmail.dmeus.milacron.com with Internet Mail Service
	(5.5.2657.72) id <HJ3X5CXP>; Fri, 26 Mar 2004 10:41:05 -0500
Message-ID: <EF398F42BE1BDF479B1E481F6E0053F201C97D77@dmeusmail.dmeus.milacron.com>
From: erik_ohrnberger@dme.net
To: bug-commoncpp@gnu.org
Date: Fri, 26 Mar 2004 10:41:00 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 26 Mar 2004 15:41:08.0083 (UTC)
	FILETIME=[C1A86C30:01C41348]
Subject: Interoperability between std::string, ost::String and Gtkmm-2.2
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2004 15:54:49 -0000

	I've got a gtkmm-2.2 application that stores it's data in the ost
persistent stream files. To date, I've been using the 1.0.x version of the
common C++ library for this persistence function.

	I've noticed that in the 1.0.x versions of the library, the
exceptions for persistent streams basically don't work and the application
just calls abort(). So, I figure that it's time to upgrade to the current
version, who's persistent exception in fact do work.

	While porting to the new version of the library, I noticed that
there is a ost::String class, which is the only way to get strings in and
out of the persistent streams.  However, the gtkmm library is designed to
integrate nicely with std::string. 

	What's the best way to integrate the two packages so that they work
nicely with each other?

	I was considering writing a number of global type conversion
operators, but that didn't seem to work pretty well, and suffered from
numerous compiler errors.

	Then I thought that I should create a sub-class of ost::String to
add the additional type conversion operators to and from std::string in a
nice, quite, and clean manner. But this appears not to work nicely as
desired either.

	I'm open to any suggestions as to how to best accomplish the desired
inter-operability.  Perhaps someone already has done this?

	Thanks,
		Erik. 



From MAILER-DAEMON Sun Mar 28 08:10:44 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B7a3o-0003RD-5o
	for mharc-bug-commoncpp@gnu.org; Sun, 28 Mar 2004 08:10:44 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B7XRz-0003EN-Ra
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 05:23:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B7XRN-0002yv-B5
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 05:23:24 -0500
Received: from [64.4.11.85] (helo=hotmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B7XRN-0001tJ-0v
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 05:22:53 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Sun, 28 Mar 2004 02:21:51 -0800
Received: from 148.243.90.41 by by7fd.bay7.hotmail.msn.com with HTTP;
	Sun, 28 Mar 2004 10:21:50 GMT
X-Originating-IP: [148.243.90.41]
X-Originating-Email: [edgarwander@hotmail.com]
X-Sender: edgarwander@hotmail.com
From: "edgar wander" <edgarwander@hotmail.com>
To: bug-commoncpp@gnu.org
Bcc: 
Date: Sun, 28 Mar 2004 10:21:50 +0000
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Message-ID: <BAY7-F85bnRWslcoFjM000078a3@hotmail.com>
X-OriginalArrivalTime: 28 Mar 2004 10:21:51.0148 (UTC)
	FILETIME=[7C0F9EC0:01C414AE]
X-Mailman-Approved-At: Sun, 28 Mar 2004 08:10:41 -0500
Subject: LGPL
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Mar 2004 10:23:34 -0000

Hello,

   I need to release a CLOSED SOURCE software, for comercial use (enterprise 
commpetitive reazons). That sofware are based in Threads and Socket from 
Common C++ library.

   In order to provide the sofware I need a binary representation: .o or 
executable.

   I thing that, I can make Wrappers Classes in order to decouple and 
isolate the cc++ library services from my code, then compile them to create 
a .o files, and then THIS OBJECTS FILES ARE MY PRODUCT, AND I CAN COPY RIGTH 
THEM. The cc++ library are then dynamic linked.

  But, I wonder (because I feel "legal fear"):
-- is it a really legal action ?
-- Can I copy rigth the .o code, compiled using g++ ?
-- where can I found specific information about, using the LGPL as a basis 
for CLOSED SOFTWARE ?,( the LGPL-GPL FAQ are not clear, considering that it 
is a legal matter !)

Thanks !

_________________________________________________________________
Charla con tus amigos en línea mediante MSN Messenger:  
http://messenger.microsoft.com/es




From MAILER-DAEMON Sun Mar 28 10:15:46 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B7c0n-0004WG-SJ
	for mharc-bug-commoncpp@gnu.org; Sun, 28 Mar 2004 10:15:45 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B7bq2-0004kD-Ju
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 10:04:38 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B7bpV-0004LW-PO
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 10:04:36 -0500
Received: from [64.233.217.29] (helo=server.echohome.org)
	by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.30) id 1B7bpR-0004Fw-TL
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 10:04:02 -0500
Received: from echo (echo.echohome.org [192.168.2.254])
	by server.echohome.org (8.12.8/8.12.8) with ESMTP id i2SF3xmY019764
	for <bug-commoncpp@gnu.org>; Sun, 28 Mar 2004 10:04:00 -0500
From: "Erik Ch. Ohrnberger" <Erik@mail.echohome.org>
To: <bug-commoncpp@gnu.org>
Date: Sun, 28 Mar 2004 10:03:59 -0500
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA1z/y+RiMjUG0rnE3+S6yhMKAAAAQAAAAa7LwIHbBhEOH3STOieqpIQEAAAAA@EchoHome.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <BAY7-F85bnRWslcoFjM000078a3@hotmail.com>
X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65',
	clamav-milter version '0.60p'
X-Mailman-Approved-At: Sun, 28 Mar 2004 10:15:42 -0500
Subject: RE: LGPL
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
Reply-To: Erik@mail.echohome.org
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Mar 2004 15:04:45 -0000

Edgar,
	I think you are right to be concerned.  Quoting now from the COPYING
file in the commoncpp2-1.1.1 distribution:

This General Public License does not permit incorporating your program =
into
proprietary programs.  If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with =
the
library.  If this is what you want to do, use the GNU Library General
Public License instead of this License.

	If this is the case, I guess I'll have to stop using the library as
well, even though I'm only using the object persistence part.

	Well, back to the drawing board.  My employer can't, or will not,
release the program that I'm writing for him as open source.  I'm afraid
it's a policy that I'll not be able to change.

	Erik.

> -----Original Message-----
> From: bug-commoncpp-bounces+erik=3Dechohome.org@gnu.org=20
> [mailto:bug-commoncpp-bounces+erik=3Dechohome.org@gnu.org] On=20
> Behalf Of edgar wander
> Sent: Sunday, March 28, 2004 5:22 AM
> To: bug-commoncpp@gnu.org
> Subject: LGPL
>=20
>=20
> Hello,
>=20
>    I need to release a CLOSED SOURCE software, for comercial=20
> use (enterprise=20
> commpetitive reazons). That sofware are based in Threads and=20
> Socket from=20
> Common C++ library.
>=20
>    In order to provide the sofware I need a binary=20
> representation: .o or=20
> executable.
>=20
>    I thing that, I can make Wrappers Classes in order to decouple and=20
> isolate the cc++ library services from my code, then compile=20
> them to create=20
> a .o files, and then THIS OBJECTS FILES ARE MY PRODUCT, AND I=20
> CAN COPY RIGTH=20
> THEM. The cc++ library are then dynamic linked.
>=20
>   But, I wonder (because I feel "legal fear"):
> -- is it a really legal action ?
> -- Can I copy rigth the .o code, compiled using g++ ?
> -- where can I found specific information about, using the=20
> LGPL as a basis=20
> for CLOSED SOFTWARE ?,( the LGPL-GPL FAQ are not clear,=20
> considering that it=20
> is a legal matter !)
>=20
> Thanks !
>=20
> _________________________________________________________________
> Charla con tus amigos en l=EDnea mediante MSN Messenger: =20
> http://messenger.microsoft.com/es
>=20
>=20
>=20
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org=20
> http://mail.gnu.org/mailman/listinfo/bug-> commoncpp
>=20




From MAILER-DAEMON Sun Mar 28 10:15:47 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B7c0o-0004WK-NA
	for mharc-bug-commoncpp@gnu.org; Sun, 28 Mar 2004 10:15:46 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B7bu0-0006Ux-NN
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 10:08:44 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B7btS-0006Cs-MJ
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 10:08:42 -0500
Received: from [64.233.217.29] (helo=server.echohome.org)
	by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.30) id 1B7btR-0006CB-Rx
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 10:08:10 -0500
Received: from echo (echo.echohome.org [192.168.2.254])
	by server.echohome.org (8.12.8/8.12.8) with ESMTP id i2SF81mY019826
	for <bug-commoncpp@gnu.org>; Sun, 28 Mar 2004 10:08:06 -0500
From: "Erik Ch. Ohrnberger" <Erik@mail.echohome.org>
To: <bug-commoncpp@gnu.org>
Date: Sun, 28 Mar 2004 10:08:01 -0500
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA1z/y+RiMjUG0rnE3+S6yhMKAAAAQAAAAezgAULS+vUqjxZgXCK6sagEAAAAA@EchoHome.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: 
X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65',
	clamav-milter version '0.60p'
X-Mailman-Approved-At: Sun, 28 Mar 2004 10:15:43 -0500
Subject: RE: LGPL - wait a minute!
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
Reply-To: Erik@mail.echohome.org
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Mar 2004 15:08:45 -0000

Hold on one minute!

In COPYING.addendum it states:

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 Common C++.
=20
The exception is that, if you link the Common C++ 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 Common C++ 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.


	If this is the case, then it would appear that I can link the
CommonC++ code into my executable and I'll still be OK for a proprietary =
end
resulting program.  (Do I have this correct?)

	Darn.  Now I'm very confused.  Would one of the authors of Common
C++ Please clear this issue up?

	Thanks,
		Erik.

> -----Original Message-----
> From: Erik Ch. Ohrnberger [mailto:Erik@EchoHome.org]=20
> Sent: Sunday, March 28, 2004 10:04 AM
> To: 'bug-commoncpp@gnu.org'
> Subject: RE: LGPL
>=20
>=20
> Edgar,
> 	I think you are right to be concerned.  Quoting now=20
> from the COPYING file in the commoncpp2-1.1.1 distribution:
>=20
> This General Public License does not permit incorporating=20
> your program into proprietary programs.  If your program is a=20
> subroutine library, you may consider it more useful to permit=20
> linking proprietary applications with the library.  If this=20
> is what you want to do, use the GNU Library General Public=20
> License instead of this License.
>=20
> 	If this is the case, I guess I'll have to stop using=20
> the library as well, even though I'm only using the object=20
> persistence part.
>=20
> 	Well, back to the drawing board.  My employer can't, or=20
> will not, release the program that I'm writing for him as=20
> open source.  I'm afraid it's a policy that I'll not be able=20
> to change.
>=20
> 	Erik.
>=20
> > -----Original Message-----
> > From: bug-commoncpp-bounces+erik=3Dechohome.org@gnu.org
> > [mailto:bug-commoncpp-bounces+erik=3Dechohome.org@gnu.org] On=20
> > Behalf Of edgar wander
> > Sent: Sunday, March 28, 2004 5:22 AM
> > To: bug-commoncpp@gnu.org
> > Subject: LGPL
> >=20
> >=20
> > Hello,
> >=20
> >    I need to release a CLOSED SOURCE software, for comercial
> > use (enterprise=20
> > commpetitive reazons). That sofware are based in Threads and=20
> > Socket from=20
> > Common C++ library.
> >=20
> >    In order to provide the sofware I need a binary
> > representation: .o or=20
> > executable.
> >=20
> >    I thing that, I can make Wrappers Classes in order to=20
> decouple and
> > isolate the cc++ library services from my code, then compile=20
> > them to create=20
> > a .o files, and then THIS OBJECTS FILES ARE MY PRODUCT, AND I=20
> > CAN COPY RIGTH=20
> > THEM. The cc++ library are then dynamic linked.
> >=20
> >   But, I wonder (because I feel "legal fear"):
> > -- is it a really legal action ?
> > -- Can I copy rigth the .o code, compiled using g++ ?
> > -- where can I found specific information about, using the
> > LGPL as a basis=20
> > for CLOSED SOFTWARE ?,( the LGPL-GPL FAQ are not clear,=20
> > considering that it=20
> > is a legal matter !)
> >=20
> > Thanks !
> >=20
> > _________________________________________________________________
> > Charla con tus amigos en l=EDnea mediante MSN Messenger:
> > http://messenger.microsoft.com/es
> >=20
> >=20
> >=20
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-> commoncpp
> >=20
>=20




From MAILER-DAEMON Sun Mar 28 13:49:59 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B7fM6-0002z3-Sx
	for mharc-bug-commoncpp@gnu.org; Sun, 28 Mar 2004 13:49:58 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B7fM3-0002xD-Fz
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 13:49:55 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B7fLW-0002o4-Bx
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 13:49:53 -0500
Received: from [216.218.222.122] (helo=mail.ostel.com)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B7fLU-0002nK-Pz
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 13:49:21 -0500
Received: by mail.ostel.com (Postfix, from userid 1005)
	id C778D2F2884; Sun, 28 Mar 2004 10:51:38 -0800 (PST)
Received: from 192.168.1.102 (pool-138-89-45-226.mad.east.verizon.net
	[138.89.45.226]) by mail.ostel.com (Postfix) with ESMTP
	id C76242F2867; Sun, 28 Mar 2004 10:51:31 -0800 (PST)
From: David Sugar <dyfet@ostel.com>
To: Erik@mail.echohome.org, <bug-commoncpp@gnu.org>
Date: Sun, 28 Mar 2004 01:51:28 -0500
User-Agent: KMail/1.5.3
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA1z/y+RiMjUG0rnE3+S6yhMKAAAAQAAAAezgAULS+vUqjxZgXCK6sagEAAAAA@EchoHome.org>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA1z/y+RiMjUG0rnE3+S6yhMKAAAAQAAAAezgAULS+vUqjxZgXCK6sagEAAAAA@EchoHome.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200403280151.28201.dyfet@ostel.com>
Cc: 
Subject: Re: LGPL - wait a minute!
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Mar 2004 18:49:56 -0000

At the time we started, the LGPL had problems in wording and in terms of=20
applicability to C++ class libraries.  This had to do with the nature of=20
templates, to meaning of inline headers, and to definition of derivation an=
d=20
class, which suggested in effect a class library could never be LGPL'd.  I=
=20
recall speaking about this recently with Craig Southern while in Germany. =
=20
Like some people, since he wanted a class framework that would be licensed =
in=20
a manner like the LGPL could then do for standard linkable C libraries, he=
=20
choose to use something else, the MPL, for openh323, and, if given the=20
current version of the LGPL back then, would have likely chosen the LGPL=20
instead.

=46rom our perspective, we simply looked at how other GNU projects tried to=
=20
accomidate this problem, and we choose the solution that Guile (and cygnus)=
=20
were using, in relation to object oriented frameworks, which is, rather tha=
n=20
relying on the LGPL for this purpose and waiting for future versions to get=
=20
the language correct, to use an immediate and simple license privilege over=
=20
the standard GPL which can achieve much the same effect the LGPL was trying=
=20
to achieve but without ambiguity.

On Sunday 28 March 2004 10:08 am, Erik Ch. Ohrnberger wrote:
> Hold on one minute!
>
> In COPYING.addendum it states:
>
> As a special exception to the GNU General Public License, permission is
> granted for additional uses of the text contained in its release
> of Common C++.
>
> The exception is that, if you link the Common C++ 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 Common C++ 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.
>
>
> 	If this is the case, then it would appear that I can link the
> CommonC++ code into my executable and I'll still be OK for a proprietary
> end resulting program.  (Do I have this correct?)
>
> 	Darn.  Now I'm very confused.  Would one of the authors of Common
> C++ Please clear this issue up?
>
> 	Thanks,
> 		Erik.
>
> > -----Original Message-----
> > From: Erik Ch. Ohrnberger [mailto:Erik@EchoHome.org]
> > Sent: Sunday, March 28, 2004 10:04 AM
> > To: 'bug-commoncpp@gnu.org'
> > Subject: RE: LGPL
> >
> >
> > Edgar,
> > 	I think you are right to be concerned.  Quoting now
> > from the COPYING file in the commoncpp2-1.1.1 distribution:
> >
> > This General Public License does not permit incorporating
> > your program into proprietary programs.  If your program is a
> > subroutine library, you may consider it more useful to permit
> > linking proprietary applications with the library.  If this
> > is what you want to do, use the GNU Library General Public
> > License instead of this License.
> >
> > 	If this is the case, I guess I'll have to stop using
> > the library as well, even though I'm only using the object
> > persistence part.
> >
> > 	Well, back to the drawing board.  My employer can't, or
> > will not, release the program that I'm writing for him as
> > open source.  I'm afraid it's a policy that I'll not be able
> > to change.
> >
> > 	Erik.
> >
> > > -----Original Message-----
> > > From: bug-commoncpp-bounces+erik=3Dechohome.org@gnu.org
> > > [mailto:bug-commoncpp-bounces+erik=3Dechohome.org@gnu.org] On
> > > Behalf Of edgar wander
> > > Sent: Sunday, March 28, 2004 5:22 AM
> > > To: bug-commoncpp@gnu.org
> > > Subject: LGPL
> > >
> > >
> > > Hello,
> > >
> > >    I need to release a CLOSED SOURCE software, for comercial
> > > use (enterprise
> > > commpetitive reazons). That sofware are based in Threads and
> > > Socket from
> > > Common C++ library.
> > >
> > >    In order to provide the sofware I need a binary
> > > representation: .o or
> > > executable.
> > >
> > >    I thing that, I can make Wrappers Classes in order to
> >
> > decouple and
> >
> > > isolate the cc++ library services from my code, then compile
> > > them to create
> > > a .o files, and then THIS OBJECTS FILES ARE MY PRODUCT, AND I
> > > CAN COPY RIGTH
> > > THEM. The cc++ library are then dynamic linked.
> > >
> > >   But, I wonder (because I feel "legal fear"):
> > > -- is it a really legal action ?
> > > -- Can I copy rigth the .o code, compiled using g++ ?
> > > -- where can I found specific information about, using the
> > > LGPL as a basis
> > > for CLOSED SOFTWARE ?,( the LGPL-GPL FAQ are not clear,
> > > considering that it
> > > is a legal matter !)
> > >
> > > Thanks !
> > >
> > > _________________________________________________________________
> > > Charla con tus amigos en l=EDnea mediante MSN Messenger:
> > > http://messenger.microsoft.com/es
> > >
> > >
> > >
> > > _______________________________________________
> > > 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 Sun Mar 28 14:11:45 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B7fhA-00076W-QZ
	for mharc-bug-commoncpp@gnu.org; Sun, 28 Mar 2004 14:11:44 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B7fh7-00073v-BA
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 14:11:41 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B7fbt-00062E-0y
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 14:06:48 -0500
Received: from [216.218.222.122] (helo=mail.ostel.com)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B7fb4-0005uh-Q2
	for bug-commoncpp@gnu.org; Sun, 28 Mar 2004 14:05:27 -0500
Received: by mail.ostel.com (Postfix, from userid 1005)
	id 176222F2884; Sun, 28 Mar 2004 11:07:43 -0800 (PST)
Received: from 192.168.1.102 (pool-138-89-45-226.mad.east.verizon.net
	[138.89.45.226]) by mail.ostel.com (Postfix) with ESMTP
	id 4EEA22F2867; Sun, 28 Mar 2004 11:07:39 -0800 (PST)
From: David Sugar <dyfet@ostel.com>
To: Ralph Dellamorte <ralph@ralphdellamorte.com>,
	bug-commoncpp@gnu.org
Date: Sun, 28 Mar 2004 02:07:35 -0500
User-Agent: KMail/1.5.3
References: <5.1.0.14.0.20040325112924.00badad8@mail.ralphdellamorte.com>
In-Reply-To: <5.1.0.14.0.20040325112924.00badad8@mail.ralphdellamorte.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200403280207.35738.dyfet@ostel.com>
Cc: 
Subject: Re: win32 thread class bug
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Mar 2004 19:11:42 -0000

The solution we use in 1.1.1 to this problem is very simple.  You NEVER use 
"delete this" in final().  Rather if the thread is a "detached" thread (a 
concept that exists in posix, in w32 there originally was no distinction) the 
thread will now automatically delete itself as it actually is terminated.  So 
just use detach() rather than start(), and do NOT use "delete this"...

On Thursday 25 March 2004 11:31 am, Ralph Dellamorte wrote:
> I see that this problem has been previously discussed as shown below. I am
> using the latest version commoncpp2-1.1.1 on a windows machine am am having
> this problem. Any help would be appreciated :)
>
> Re: fatal bug in class Thread, thread.cpp line~ 858
>
> ---------------------------------------------------------------------------
>----- From:  David Sugar
> Subject:  Re: fatal bug in class Thread, thread.cpp line~ 858
> Date:  Sat, 20 Dec 2003 06:34:57 -0500
> User-agent:  KMail/1.5.3
>
> ---------------------------------------------------------------------------
>-----
>
> Actually thats not correct either, since _self is part of the current
> "Thread" object.  What would be better, as a temporary solution, is to
> change "final" so that it can return a bool, and have it return true when
> final has deleted the current object...that way any further processing
> could be bypassed if final is true.  Let me think more on this....
>
> On Friday 19 December 2003 08:54 am, Tobias Erbsland wrote:
>  > Hello
>  >
>  > The Thread class has a fatal bug:
>  >
>  > ==== thread.cpp ==== Line 848 ====
>  >       // final can call destructor (that call Terminate)
>  >       final();
>  >
>  >       // test if this class have been deleted
>  > #ifdef WIN32
>  >       if (_self.getKey() == this)
>  > #else
>  >       if (ThreadImpl::_self.getKey() == this)
>  > #endif
>  >       {
>  >               if(priv)
>  >                       priv->_tid = 0;
>  >               joinSem.post();
>  >       }
>  > ====================================
>  >
>  > The API documentation suggest to place a "delete this" in the final()
>  > method to delete the thread on exit. This implementation is found for
>  > example in the TCPSession class.
>  >
>  > After the final() method, the object could be deleted, so each access to
>  > a member of the object is invalid.
>  >
>  > The C++ compiler from the new .NET edition of the MS Visual Studio
>  > (Version 7.0) fills each deleted memory segment with the "word" 0xfeee
>  > in debug mode (i don't know why, but that's the fact).
>  >
>  > The line "if(priv)" is true in this case, and the assignment "priv->_tid
>  > = 0" results in an access violation (unix: core dump).
>  >
>  > IMHO, instead this strange test, there should be a hook in the virtual
>  > destructor of the Thread class.
>  >
>  > regards
>  > Tobias
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Mon Mar 29 12:28:48 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B80Z6-0001PQ-9J
	for mharc-bug-commoncpp@gnu.org; Mon, 29 Mar 2004 12:28:48 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B80Z2-0001Nz-Ae
	for bug-commoncpp@gnu.org; Mon, 29 Mar 2004 12:28:44 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B80YS-0001AJ-TC
	for bug-commoncpp@gnu.org; Mon, 29 Mar 2004 12:28:40 -0500
Received: from [12.27.46.144] (helo=mnmail02.metriscompanies.com)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B80YS-00019e-Jd
	for bug-commoncpp@gnu.org; Mon, 29 Mar 2004 12:28:08 -0500
Received: from mnmail02.metriscompanies.com ([172.31.130.233])
	by mnmail02.metriscompanies.com (Lotus Domino Release 6.0.3)
	with ESMTP id 2004032911333094-184242 ;
	Mon, 29 Mar 2004 11:33:30 -0600 
Received: from azmail01.metriscompanies.com ([172.31.160.55]) by mnmail02 with
	trend_isnt_name_B; Mon, 29 Mar 2004 11:33:30 -0600
To: bug-commoncpp@gnu.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.3 September 26, 2003
Message-ID: <OFF1D16E93.6D87B86C-ON07256E66.005EE983-07256E66.005FF509@metriscompanies.com>
From: Jason.Majors@metriscompanies.com
Date: Mon, 29 Mar 2004 10:31:47 -0700
X-MIMETrack: Serialize by Router on AZMAIL01/Servers/Metris(Release
	6.0.3|September 26, 2003) at 03/29/2004 10:31:56 AM,
	Serialize complete at 03/29/2004 10:31:56 AM,
	Itemize by SMTP Server on MNMAIL02/Servers/Metris(Release
	6.0.3|September 26, 2003) at 03/29/2004 11:33:30 AM,
	Serialize by Router on MNMAIL02/Servers/Metris(Release 6.0.3|September
	26, 2003) at 03/29/2004 11:33:32 AM,
	Serialize complete at 03/29/2004 11:33:32 AM
Content-Type: text/plain; charset="US-ASCII"
Subject: segfault before main() is called
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Mar 2004 17:28:46 -0000

I'm trying to use the TCPSession and TCPSocket classes for a threaded 
daemon I'm writing. To test the code in the daemon, I wrote a main that 
bypasses the networking classes (and all cc++ include headers). When I try 
to run it, I get a segfault, before it even reaches the first line of 
main, which is a cout. I loaded it in gdb to trace the execution, but I'm 
not sure how to interpret the output, since it seems to be all library 
code. Can somebody with more knowledge of the libraray tell me what this 
means? 
Thanks.

I'm using gcc 3.3 on AIX 4.3.3 with common cpp 1.1.0.

This GDB was configured as "powerpc-ibm-aix4.3.2.0"...
Core was generated by `jist_test'.
Program terminated with signal 11, Segmentation fault.
#0  0xd31ee0f4 in pthread_mutexattr_init ()
(gdb) where
#0  0xd31ee0f4 in pthread_mutexattr_init ()
#1  0xd31e1db4 in _ZN3ost5MutexC1EPKc (this=<incomplete type>, name=0x0)
    at mutex.cpp:180
#2  0xd31eaf74 in _Z41__static_initialization_and_destruction_0ii (
    __initialize_p=0, __priority=0) at string.cpp:62
#3  0xd3208770 in _GLOBAL__FI_libccgnu2_1_1_so ()
#4  0xd018f100 in mod_init1 ()
#5  0xd018f014 in __modinit ()
#6  0x1000019c in __start ()



From MAILER-DAEMON Wed Mar 31 09:25:37 2004
Received: from list by monty-python.gnu.org with archive (Exim 4.30)
	id 1B8gX9-0008DX-2A
	for mharc-bug-commoncpp@gnu.org; Wed, 31 Mar 2004 09:17:35 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1B8gWt-0008AV-IA
	for bug-commoncpp@gnu.org; Wed, 31 Mar 2004 09:17:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1B8fXW-00063T-3F
	for bug-commoncpp@gnu.org; Wed, 31 Mar 2004 08:14:25 -0500
Received: from [200.215.17.89] (helo=cli005.brasmap.com.br)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1B8fXU-00062V-Vn
	for bug-commoncpp@gnu.org; Wed, 31 Mar 2004 08:13:53 -0500
Received: from cli005.brasmap (localhost.localdomain [127.0.0.1])
	by cli005.brasmap.com.br (Postfix) with SMTP id 526DA5BBAF
	for <bug-commoncpp@gnu.org>; Wed, 31 Mar 2004 10:12:49 -0300 (BRT)
Date: Wed, 31 Mar 2004 10:12:44 -0300
From: Marcelo Dalmas <mad@brasmap.com.br>
To: ccxx <bug-commoncpp@gnu.org>
Message-Id: <20040331101244.33e1eb17.mad@brasmap.com.br>
Organization: BRASMAP Sistemas, Consultoria e =?ISO-8859-1?Q?Com=E9rcio?= LTDA.
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i586-pc-linux-gnu)
X-Face: ?)Du, i:^D^'QRQ,
	wzSC{c%%.{Pc_UyXWu"LS+jW^LFdcGy:ZxGj&%_>T23<E''q++`^{z{e
	~leB|cC4F+ko]%BEUoVkDT0t+}"ohRV@DJN+oZ89{"bOCnLC=sAJh~h"/_ErZ&h)s-OA&jw${i|RMv
	+}.[3*2RYpa3Qn"BvB|-n8Hd_CmQcjF7A-Tl\|xvmH,*,e
Mime-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg="pgp-sha1";
	boundary="Signature=_Wed__31_Mar_2004_10_12_45_-0300_.MadY=JO_pho/jwx"
Subject: CVS tags
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Mar 2004 14:17:30 -0000

--Signature=_Wed__31_Mar_2004_10_12_45_-0300_.MadY=JO_pho/jwx
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi all,

Which tags exists in the CVS?

I know "release1" for 1.0.14 and "stable1" for 1.1.2, rigth?

And "HEAD" and "testing"?

There are plans for Common C++ "2" 1.2 ?




--=20
-------------------------------------------------
  Marcelo Dalmas - Eng. de Controle e Automa=E7=E3o
-------------------------------------------------
  BRASMAP Sistemas, Consultoria e Com=E9rcio Ltda.
        Engenharia em Aquisi=E7=E3o de Dados

     www.brasmap.com.br - info@brasmap.com.br
Fone: (48) 333-2218 ramal 2114 Fax: (48) 333-3745
-------------------------------------------------


--Signature=_Wed__31_Mar_2004_10_12_45_-0300_.MadY=JO_pho/jwx
Content-Type: application/pgp-signature

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

iD8DBQFAasPQ95NRejZp8BwRAp7xAKCOGFOdLq2CXXjfEsZDqQr9rCfbYwCgzPRR
hIKZKh8Hb15vuW9GcIHaqS0=
=X4vd
-----END PGP SIGNATURE-----

--Signature=_Wed__31_Mar_2004_10_12_45_-0300_.MadY=JO_pho/jwx--



