From fedemp@wanadoo.es Wed Oct 02 11:18:21 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17wlGX-0004du-00
	for bug-commoncpp@gnu.org; Wed, 02 Oct 2002 11:18:21 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17wlGQ-0004dC-00
	for bug-commoncpp@gnu.org; Wed, 02 Oct 2002 11:18:20 -0400
Received: from [62.37.236.139] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17wlGP-0004cc-00
	for bug-commoncpp@gnu.org; Wed, 02 Oct 2002 11:18:13 -0400
Received: from risitas ([80.103.119.217])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAHHCFA20877;
	Sun, 17 Nov 2002 18:12:24 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17wlIN-00028Z-00; Wed, 02 Oct 2002 17:20:15 +0200
Date: Wed, 2 Oct 2002 17:20:10 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Anders Backman <vr-anders@users.sourceforge.net>
Cc: bug-commoncpp@gnu.org
Subject: Re: (Sourceforge bug report) [ 617582 ] ttystream::close() recursive call.
Message-ID: <20021002152010.GA867@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Anders Backman <vr-anders@users.sourceforge.net>,
	bug-commoncpp@gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Hi,

>During the destructor of ttystream (or ttystream::close()
>for that matter) a call to close() is recursive.
>This of course crashes the application.
>
>So it looks like
>
>ttystream::close() {
>close();
>}

	Um, I think this should be TTYStream::close(), which in fact
calls to Serial::close(). This is fixed now in the CVS at savannah.

>This goes for the last version (2.0.1) on all platforms.

	The last release of CC++ 2 is 1.0.2. You can get it from any
GNU mirror or from savannah (http://sv.gnu.org/projects/commoncpp/).




From fedemp@wanadoo.es Thu Oct 03 14:02:16 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17xAIh-0002RT-00
	for bug-commoncpp@gnu.org; Thu, 03 Oct 2002 14:02:15 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17xAIa-0002Qr-00
	for bug-commoncpp@gnu.org; Thu, 03 Oct 2002 14:02:15 -0400
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17xAIa-0002Qd-00
	for bug-commoncpp@gnu.org; Thu, 03 Oct 2002 14:02:08 -0400
Received: from risitas (62-37-141-218.dialup.uni2.es [62.37.141.218])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g93I1cX22612
	for <bug-commoncpp@gnu.org>; Thu, 3 Oct 2002 20:01:39 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17xALJ-0000MS-00
	for <bug-commoncpp@gnu.org>; Thu, 03 Oct 2002 20:04:57 +0200
Date: Thu, 3 Oct 2002 20:04:56 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: (Sourceforge bug report) [ 617514 ] getElapsed()=getTimer() for WIN32
Message-ID: <20021003180456.GA964@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Hi, I think your proposal makes much more sense that the
current code. It looks like this method has been overlooked so far,
so, if there is no objection, this will be incorporated for the next
release.

>For WIN32, TimerPort::getElapsed() returns getTimer().
>timeout_t TimerPort::getElapsed(void) const
>{
>return getTimer();
>}
>
>The following code is proposed, for WIN32:
>timeout_t TimerPort::getElapsed(void) const
>{
>DWORD now;
>long diff;
>
>if(!active)
>return TIMEOUT_INF;
>
>now = GetTickCount();
>diff = now - timer;
>
>if(diff < 0)
>return 0l;
>
>return diff;
>} 



From dyfet@ostel.com Fri Oct 04 07:49:33 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17xQxZ-0003Ne-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 07:49:33 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17xQxX-0003NM-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 07:49:32 -0400
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)
	id 17xQxW-0003NE-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 07:49:31 -0400
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id g94C9H702765;
	Fri, 4 Oct 2002 08:09:17 -0400
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Fri, 4 Oct 2002 08:09:17 -0400 (EDT)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: (Sourceforge bug report) [ 617514 ] getElapsed()=getTimer() for
 WIN32
In-Reply-To: <20021003180456.GA964@risitas>
Message-ID: <Pine.LNX.4.44.0210040809020.2737-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Yes, I think so too...I missed noticing this one.

David

On Thu, 3 Oct 2002, Federico Montesino Pouzols wrote:

> 
> 	Hi, I think your proposal makes much more sense that the
> current code. It looks like this method has been overlooked so far,
> so, if there is no objection, this will be incorporated for the next
> release.
> 
> >For WIN32, TimerPort::getElapsed() returns getTimer().
> >timeout_t TimerPort::getElapsed(void) const
> >{
> >return getTimer();
> >}
> >
> >The following code is proposed, for WIN32:
> >timeout_t TimerPort::getElapsed(void) const
> >{
> >DWORD now;
> >long diff;
> >
> >if(!active)
> >return TIMEOUT_INF;
> >
> >now = GetTickCount();
> >diff = now - timer;
> >
> >if(diff < 0)
> >return 0l;
> >
> >return diff;
> >} 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From fedemp@wanadoo.es Fri Oct 04 15:31:26 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17xYAX-0003hi-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 15:31:25 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17xYAV-0003h2-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 15:31:25 -0400
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17xY98-00033X-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 15:29:58 -0400
Received: from risitas (62-36-187-6.dialup.uni2.es [62.36.187.6])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g94JTGX15803;
	Fri, 4 Oct 2002 21:29:16 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17xYA6-0000yD-00; Fri, 04 Oct 2002 21:30:58 +0200
Date: Fri, 4 Oct 2002 21:30:58 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Norbert Koch <nkoch@users.sourceforge.net>
Cc: bug-commoncpp@gnu.org
Subject: Re: (Sourceforge bug report) [ 618427 ] Documentation of MappedFile
Message-ID: <20021004193058.GA3289@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Norbert Koch <nkoch@users.sourceforge.net>,
	bug-commoncpp@gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Yes, the documentation is somewhat confusing, since MappedFile
is said to be portable to Win32, but at the same time there is a
"@todo implement in win32". I guess there is the intention to make it
portable to Win32.

	As far as I see, this class is not implemented on
Win32. However, it should be feasible and even easy to implement it.

	Are there people interested in this port or even willing to
provide help with the implementation/testing?

>The documentation in file.h states that MappedFile
>is implemented in WIN32 environment.
>As far as I can see from the sources this
>is not (yet) true, is it?
>Or did I miss something?



From fedemp@wanadoo.es Fri Oct 04 15:35:49 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17xYEn-0004Pa-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 15:35:49 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17xYEl-0004PG-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 15:35:48 -0400
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17xYEl-0004P6-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 15:35:47 -0400
Received: from risitas (62-36-187-6.dialup.uni2.es [62.36.187.6])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g94JZ8X17382;
	Fri, 4 Oct 2002 21:35:08 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17xYHT-0000zI-00; Fri, 04 Oct 2002 21:38:35 +0200
Date: Fri, 4 Oct 2002 21:38:35 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Norbert Koch <nkoch@users.sourceforge.net>
Cc: bug-commoncpp@gnu.org
Subject: Re: (Sourceforge bug report) [ 618427 ] Documentation of MappedFile
Message-ID: <20021004193835.GA3775@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Norbert Koch <nkoch@users.sourceforge.net>,
	bug-commoncpp@gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Yes, the documentation is somewhat confusing, since it says
that MappedFile is portable to both posix and Win32, but a "@todo
implement in win32" item is specified. I guess there is the intention
to port it to Win32. It should be feasible or even easy.

	Are there people interested in this port or even willing to
help with its implementation/testing?

>Documentation of MappedFile
>The documentation in file.h states that MappedFile
>is implemented in WIN32 environment.
>As far as I can see from the sources this
>is not (yet) true, is it?
>Or did I miss something?



From byrial@image.dk Sun Oct 06 04:34:35 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17y6ry-0005q3-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 04:34:34 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17y6rd-0005N4-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 04:34:15 -0400
Received: from smtp020.tiscali.dk ([212.54.64.104])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17y6rX-0005F3-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 04:34:08 -0400
Received: from cpmail.dk.tiscali.com (mail.tiscali.dk [212.54.64.159])
	by smtp020.tiscali.dk (8.12.5/8.12.5) with ESMTP id g968SV5d025334
	for <bug-commoncpp@gnu.org>; Sun, 6 Oct 2002 10:28:32 +0200 (MEST)
Received: from ask.ask (213.237.84.202) by cpmail.dk.tiscali.com (6.0.053)
        id 3D9BF5F30006F03D for bug-commoncpp@gnu.org; Sun, 6 Oct 2002 10:34:04 +0200
Received: (qmail 17104 invoked by uid 500); 6 Oct 2002 08:30:36 -0000
Date: Sun, 6 Oct 2002 10:30:36 +0200
From: Byrial Jensen <byrial@image.dk>
To: bug-commoncpp@gnu.org
Subject: SocketService and SocketPort
Message-ID: <20021006083036.GC893@ask.ask>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

[Note: I sent my first message to the list a week ago when I was not
yet subscribed to the list. I got a mesage back that it awaited
moderator approval because it was posted by a non-member. However the
moderator seems to be sleeping - at least I never saw my message at
the list.]

I have programmed a simple tcp proxy-server using Common C++ and
have some experience and suggestions with regard to SocketService
and SocketPort I would like to share:

  - There is currently no way to create SocketPorts for non-server
    connections. I would like a SocketPort constructor which creates
    an outgoing client tcp connection as I need a lot of such
    connections in a proxy server.

  - The virtual callback functions of the SocketPort class (expired,
    pending, output) may /not/ delete the current SocketPort object
    (*this) because SocketService::run will still use a pointer
    (SocketPort *port) to the object /after/ the return of these
    callback functions and thus use deallocated memory.

    This is not documented and it is disobeyed by the tcpservice.cpp
    demo program. So the demo program contains undefined behaviour!

    I would like that the callback functions are allowed to not only
    delete the current SocketPort object, but also to create new 
    SocketPorts attached to the same SocketService and to delete
    other SocketPorts than *this, as this is useful in a proxy
    server. I have done it this way in my code (here implemented
    only inside "#ifdef CCXX_USE_POLL"):

diff -udrpb commoncpp2-1.0.2-org/include/cc++/socket.h commoncpp2-1.0.2/include/cc++/socket.h
--- commoncpp2-1.0.2-org/include/cc++/socket.h	Tue Aug 27 04:11:07 2002
+++ commoncpp2-1.0.2/include/cc++/socket.h	Sun Oct  6 09:22:21 2002
@@ -1814,6 +1814,7 @@ private:
 	bool detect_pending;
 	bool detect_output;
 	bool detect_disconnect;
+	volatile bool recent_changes;
 	
 	friend class SocketService;
 
diff -udrpb commoncpp2-1.0.2-org/src/port.cpp commoncpp2-1.0.2/src/port.cpp
--- commoncpp2-1.0.2-org/src/port.cpp	Thu Jul 18 16:52:25 2002
+++ commoncpp2-1.0.2/src/port.cpp	Sun Oct  6 09:34:06 2002
@@ -403,6 +403,7 @@ void SocketService::attach(SocketPort *p
 
 	++count;
 	if(!first) first = port;
+	recent_changes = true;
 	
 	// start thread if necessary
 	if (count == 1)
@@ -438,6 +439,7 @@ void SocketService::detach(SocketPort *p
 	port->service = NULL;
 	
 	--count;
+	recent_changes = true;
 	leaveMutex();
 	update();
 }
@@ -533,6 +535,7 @@ void SocketService::run(void)
 		
 		MUTEX_START
 		onEvent();
+		recent_changes = false;
 		port = first;
 		while(port)
 		{
@@ -544,19 +547,22 @@ void SocketService::run(void)
 					port->detect_disconnect = false;
 					p_ufd->events &= ~POLLHUP;
 
-					SocketPort* p = port;
-					port = port->next;
-					detach(p);
-					reallocate = true;
-					p->disconnect();
-					continue;
+					port->disconnect();
+					if (recent_changes)
+						break;
 				}
 	
-				if ( ( POLLIN | POLLPRI ) & p_ufd->revents )
+				if ( ( POLLIN | POLLPRI ) & p_ufd->revents ) {
 					port->pending();
+					if (recent_changes)
+						break;
+				}
 	
-				if ( POLLOUT & p_ufd->revents )
+				if ( POLLOUT & p_ufd->revents ) {
 					port->output();
+					if (recent_changes)
+						break;
+				}
 
 			} else {
 				reallocate = true;
@@ -573,6 +579,8 @@ retry:
 			{
 				port->endTimer();
 				port->expired();
+				if (recent_changes)
+					break;
 				goto retry;
 			}
 
  - It would be more effective if SocketService::Run used the return
    values from the poll/select system calls.

  - TCPSocket does not support onAccept as claimed in the
    documentation. Yes, the function exists but it is not called by
    the SocketPort(SocketService *svc, TCPSocket &tcp) constructor.

Best regards
Byrial



From dyfet@ostel.com Sun Oct 06 09:34:15 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yBWx-0007fz-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 09:33:11 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yBWs-0007YS-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 09:33:08 -0400
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)
	id 17yBWJ-0006ht-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 09:32:31 -0400
Received: from home.sys (IDENT:zEuVrrEpx+CpMbzr2ChaiqFtp3np/3rf@home.sys [172.16.1.254])
	by home.sys (8.11.6/8.11.6) with ESMTP id g96Dqbr25846;
	Sun, 6 Oct 2002 09:52:38 -0400
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Byrial Jensen <byrial@image.dk>, bug-commoncpp@gnu.org
Subject: Re: SocketService and SocketPort
Date: Sun, 6 Oct 2002 09:52:37 -0400
User-Agent: KMail/1.4.3
References: <20021006083036.GC893@ask.ask>
In-Reply-To: <20021006083036.GC893@ask.ask>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200210060952.37162.dyfet@ostel.com>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Did this get missed earlier?  We get a HUGE amount of junk mail attempts=20
through this list.  It's very easy to miss a real pending message.  I wou=
ld=20
like to think about this...I know how I originally was thinking of what l=
ater=20
became SocketService; it was based on the coding model I was originally u=
sing=20
for channel ports in ACS.=20

On Sunday 06 October 2002 04:30, Byrial Jensen wrote:
> [Note: I sent my first message to the list a week ago when I was not
> yet subscribed to the list. I got a mesage back that it awaited
> moderator approval because it was posted by a non-member. However the
> moderator seems to be sleeping - at least I never saw my message at
> the list.]
>
> I have programmed a simple tcp proxy-server using Common C++ and
> have some experience and suggestions with regard to SocketService
> and SocketPort I would like to share:
>
>   - There is currently no way to create SocketPorts for non-server
>     connections. I would like a SocketPort constructor which creates
>     an outgoing client tcp connection as I need a lot of such
>     connections in a proxy server.
>
>   - The virtual callback functions of the SocketPort class (expired,
>     pending, output) may /not/ delete the current SocketPort object
>     (*this) because SocketService::run will still use a pointer
>     (SocketPort *port) to the object /after/ the return of these
>     callback functions and thus use deallocated memory.
>
>     This is not documented and it is disobeyed by the tcpservice.cpp
>     demo program. So the demo program contains undefined behaviour!
>
>     I would like that the callback functions are allowed to not only
>     delete the current SocketPort object, but also to create new
>     SocketPorts attached to the same SocketService and to delete
>     other SocketPorts than *this, as this is useful in a proxy
>     server. I have done it this way in my code (here implemented
>     only inside "#ifdef CCXX_USE_POLL"):
>
> diff -udrpb commoncpp2-1.0.2-org/include/cc++/socket.h
> commoncpp2-1.0.2/include/cc++/socket.h ---
> commoncpp2-1.0.2-org/include/cc++/socket.h=09Tue Aug 27 04:11:07 2002 +=
++
> commoncpp2-1.0.2/include/cc++/socket.h=09Sun Oct  6 09:22:21 2002 @@ -1=
814,6
> +1814,7 @@ private:
>  =09bool detect_pending;
>  =09bool detect_output;
>  =09bool detect_disconnect;
> +=09volatile bool recent_changes;
>
>  =09friend class SocketService;
>
> diff -udrpb commoncpp2-1.0.2-org/src/port.cpp commoncpp2-1.0.2/src/port=
=2Ecpp
> --- commoncpp2-1.0.2-org/src/port.cpp=09Thu Jul 18 16:52:25 2002
> +++ commoncpp2-1.0.2/src/port.cpp=09Sun Oct  6 09:34:06 2002
> @@ -403,6 +403,7 @@ void SocketService::attach(SocketPort *p
>
>  =09++count;
>  =09if(!first) first =3D port;
> +=09recent_changes =3D true;
>
>  =09// start thread if necessary
>  =09if (count =3D=3D 1)
> @@ -438,6 +439,7 @@ void SocketService::detach(SocketPort *p
>  =09port->service =3D NULL;
>
>  =09--count;
> +=09recent_changes =3D true;
>  =09leaveMutex();
>  =09update();
>  }
> @@ -533,6 +535,7 @@ void SocketService::run(void)
>
>  =09=09MUTEX_START
>  =09=09onEvent();
> +=09=09recent_changes =3D false;
>  =09=09port =3D first;
>  =09=09while(port)
>  =09=09{
> @@ -544,19 +547,22 @@ void SocketService::run(void)
>  =09=09=09=09=09port->detect_disconnect =3D false;
>  =09=09=09=09=09p_ufd->events &=3D ~POLLHUP;
>
> -=09=09=09=09=09SocketPort* p =3D port;
> -=09=09=09=09=09port =3D port->next;
> -=09=09=09=09=09detach(p);
> -=09=09=09=09=09reallocate =3D true;
> -=09=09=09=09=09p->disconnect();
> -=09=09=09=09=09continue;
> +=09=09=09=09=09port->disconnect();
> +=09=09=09=09=09if (recent_changes)
> +=09=09=09=09=09=09break;
>  =09=09=09=09}
>
> -=09=09=09=09if ( ( POLLIN | POLLPRI ) & p_ufd->revents )
> +=09=09=09=09if ( ( POLLIN | POLLPRI ) & p_ufd->revents ) {
>  =09=09=09=09=09port->pending();
> +=09=09=09=09=09if (recent_changes)
> +=09=09=09=09=09=09break;
> +=09=09=09=09}
>
> -=09=09=09=09if ( POLLOUT & p_ufd->revents )
> +=09=09=09=09if ( POLLOUT & p_ufd->revents ) {
>  =09=09=09=09=09port->output();
> +=09=09=09=09=09if (recent_changes)
> +=09=09=09=09=09=09break;
> +=09=09=09=09}
>
>  =09=09=09} else {
>  =09=09=09=09reallocate =3D true;
> @@ -573,6 +579,8 @@ retry:
>  =09=09=09{
>  =09=09=09=09port->endTimer();
>  =09=09=09=09port->expired();
> +=09=09=09=09if (recent_changes)
> +=09=09=09=09=09break;
>  =09=09=09=09goto retry;
>  =09=09=09}
>
>   - It would be more effective if SocketService::Run used the return
>     values from the poll/select system calls.
>
>   - TCPSocket does not support onAccept as claimed in the
>     documentation. Yes, the function exists but it is not called by
>     the SocketPort(SocketService *svc, TCPSocket &tcp) constructor.
>
> Best regards
> Byrial
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From d99-vlu@nada.kth.se Fri Oct 04 11:00:31 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17xTtG-0003ug-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 10:57:18 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17xTsB-00022f-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 10:56:20 -0400
Received: from knatte.nada.kth.se ([130.237.226.102])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17xTqH-0007wT-00
	for bug-commoncpp@gnu.org; Fri, 04 Oct 2002 10:54:13 -0400
Received: from localhost (d99-vlu@localhost)
	by knatte.nada.kth.se (8.9.3+Sun/8.9.3) with ESMTP id QAA17944
	for <bug-commoncpp@gnu.org>; Fri, 4 Oct 2002 16:54:10 +0200 (MEST)
X-Authentication-Warning: knatte.nada.kth.se: d99-vlu owned process doing -bs
Date: Fri, 4 Oct 2002 16:54:10 +0200 (MEST)
From: =?ISO-8859-1?Q?Viktor_Lundstr=F6m?= <d99-vlu@nada.kth.se>
To: <bug-commoncpp@gnu.org>
Subject: Need help concerning weird SIGABRT on socket timeout
Message-ID: <Pine.SOL.4.30.0210041645330.17511-100000@knatte.nada.kth.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by knatte.nada.kth.se id QAA17944
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hello!
I have a problem handling socket timeouts in a
subclass of TCPSession.
When I use a set timeout (using setTimeout(...) in
the constructor), and an I/O operation times out,
no exception is thrown, but instead the process receives
a SIGABRT signal, making it exit to prompt with the
message "Abort".

Other I/O errors such as unexpected eof successfully
throw exceptions (when iostream exception flags are set).

I've also tried this using TCPStream in a non-threaded
application and with the same results.

I'm using SunOS 5.8.

Any help would be appreciated.

/Viktor Lundstr=F6m




From kspinka@gist.com Sun Oct 06 06:10:29 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17y8MK-00021L-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 06:10:00 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17y8LO-0001WG-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 06:09:03 -0400
Received: from [204.215.183.134] (helo=gsrv2003.corp.NYC.gist.com)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17y8LJ-0001Lr-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 06:08:57 -0400
Received: from gist.com (freelancer.corp.nyc.gist.com [192.168.9.73]) by gsrv2003.corp.NYC.gist.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id T864XC23; Sun, 6 Oct 2002 06:07:22 -0400
Message-ID: <3DA00BA5.3020905@gist.com>
Date: Sun, 06 Oct 2002 06:08:37 -0400
From: "Spinka, Kristofer" <kspinka@gist.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2a) Gecko/20020910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
Subject: Solaris 9, SocketPort
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

   I haven't had the time to track anything down, however, if you try 
running the portsample (SampleSocketPort.cpp), you will see the problem 
immediately after the first client disconnects.

     /kris




From dyfet@ostel.com Sun Oct 06 12:00:36 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yDpb-0006W9-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 12:00:35 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yDov-0005Tq-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 11:59:54 -0400
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)
	id 17yDmg-0003jC-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 11:57:34 -0400
Received: from home.sys (IDENT:CHp6kPpjtXKSxUHkmyouOGjY/YabFHI4@home.sys [172.16.1.254])
	by home.sys (8.11.6/8.11.6) with ESMTP id g96GHar26819;
	Sun, 6 Oct 2002 12:17:36 -0400
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Damien Vincent <damien.vincent@enst-bretagne.fr>, bug-commoncpp@gnu.org
Subject: Re: Explanations on MappedFile
Date: Sun, 6 Oct 2002 12:17:36 -0400
User-Agent: KMail/1.4.3
References: <20020926162255.GA1570@vincentsd>
In-Reply-To: <20020926162255.GA1570@vincentsd>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200210061217.36145.dyfet@ostel.com>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Generally I had been assuming people would use MappedFile to construct mo=
re=20
complete objects that manage mapped memory in specific ways, rather than =
use=20
MappedFile itself as a generic mapped file access class.

On Thursday 26 September 2002 12:22, Damien Vincent wrote:
>   Hi,
>
> I'd like to know why all types (Mapping, Access, ...) are in the protec=
ted
> section of the class "File". With this design, you can't make a MappedF=
ile
> object since in the constructor of this class, you need to specify an
> access mode (-> MappedFile (const char *fname, Access mode) ). So, the =
only
> way to create a mapped file is to make a class which derives from
> MappedFile. With the version 1.6.4 of the library, you can make an inst=
ance
> of the MappedFile class.
>
>   Thanks,
>
> Damien
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From dyfet@ostel.com Sun Oct 06 12:00:46 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yDoK-00054E-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 11:59:16 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yDo6-0004ri-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 11:59:04 -0400
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)
	id 17yDnb-0004VT-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 11:58:31 -0400
Received: from home.sys (IDENT:01zWUjhMKiQj280CdL7WeJKYyy4N2Mg/@home.sys [172.16.1.254])
	by home.sys (8.11.6/8.11.6) with ESMTP id g96GIYr26834;
	Sun, 6 Oct 2002 12:18:34 -0400
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Emmanuel Debanne <emde@ocegr.fr>, bug-commoncpp@gnu.org
Subject: Re: install of commomc++-1.0.2 on cygwin
Date: Sun, 6 Oct 2002 12:18:34 -0400
User-Agent: KMail/1.4.3
References: <3D8B4E95.9010904@ocegr.fr>
In-Reply-To: <3D8B4E95.9010904@ocegr.fr>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200210061218.34623.dyfet@ostel.com>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

There were a number of problems introduced when we merged the win32 and p=
osix=20
thread code for cross-compiling under MingW32...these are being worked on=
=2E

David

On Friday 20 September 2002 12:36, Emmanuel Debanne wrote:
> Hi all,
>
> I'm installing commonc++-1.0.2 on cygwin.
> I've got the following error:
> thread.cpp:357: invalid use of undefined type `struct ost::PosixThread'
>
> Here is the whole output.
>
> Emmanuel Debanne
>
> $ make
> Making all in include
> make[1]: Entering directory `/home/emde/commoncpp2-1.0.2/include'
> make[2]: Entering directory `/home/emde/commoncpp2-1.0.2/include'
> cd .. \
>    && CONFIG_FILES=3D CONFIG_HEADERS=3Dinclude/config.h \
>       /bin/bash ./config.status
> config.status: creating include/config.h
> config.status: executing default-1 commands
> make[2]: Leaving directory `/home/emde/commoncpp2-1.0.2/include'
> make  all-recursive
> make[2]: Entering directory `/home/emde/commoncpp2-1.0.2/include'
> Making all in cc++
> make[3]: Entering directory `/home/emde/commoncpp2-1.0.2/include/cc++'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/emde/commoncpp2-1.0.2/include/cc++'
> make[3]: Entering directory `/home/emde/commoncpp2-1.0.2/include'
> make[3]: Leaving directory `/home/emde/commoncpp2-1.0.2/include'
> make[2]: Leaving directory `/home/emde/commoncpp2-1.0.2/include'
> make[1]: Leaving directory `/home/emde/commoncpp2-1.0.2/include'
> Making all in src
> make[1]: Entering directory `/home/emde/commoncpp2-1.0.2/src'
> /bin/bash ../libtool --mode=3Dcompile g++ -DHAVE_CONFIG_H -I. -I.
> -I../include -I../src -DCCXX_EXPORT_LIBRARY  -g -O2 -D_GNU_SOURCE
> -I/usr/include/libxml2/li
> bxml -I/usr/include/libxml2 -I../include -c thread.cpp
> mkdir .libs
> g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
> -g -O2 -
> D_GNU_SOURCE -I/usr/include/libxml2/libxml -I/usr/include/libxml2
> -I../include -
> c thread.cpp  -DDLL_EXPORT -DPIC -o .libs/thread.lo
> thread.cpp:357: invalid use of undefined type `struct ost::PosixThread'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp:357: assignment (not initialization) in declaration
> thread.cpp:358: invalid use of undefined type `struct ost::PosixThread'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp: In static member function `static void
>     ost::ThreadImpl::PosixThreadSigHandler(int)':
> thread.cpp:1202: cannot dynamic_cast `t' (of type `class ost::Thread*')
> to type
>
>     `struct ost::PosixThread*' (target is not pointer or reference to
> complete
>     type)
> thread.cpp:1209: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp:1213: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp:1217: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp:1221: incomplete type `ost::PosixThread' does not have membe=
r `
>     _timer'
> thread.cpp:1223: incomplete type `ost::PosixThread' does not have membe=
r `
>     _timer'
> thread.cpp:1224: incomplete type `ost::PosixThread' does not have membe=
r `
>     _timer'
> thread.cpp:1229: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp:1237: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp:1241: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp: At global scope:
> thread.cpp:1249: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp: In constructor `ost::PosixThread::PosixThread(int, unsigned
> int)':
> thread.cpp:1250: type `class ost::Thread' is not a direct base of `
>     ost::PosixThread'
> thread.cpp:1252: `_alarm' undeclared (first use this function)
> thread.cpp:1252: (Each undeclared identifier is reported only once for =
each
>     function it appears in.)
> thread.cpp: At global scope:
> thread.cpp:1256: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp: In member function `void ost::PosixThread::setTimer(long
> unsigned
>     int)':
> thread.cpp:1270: `_arm' undeclared (first use this function)
> thread.cpp:1271: `_timer' undeclared (first use this function)
> thread.cpp: At global scope:
> thread.cpp:1285: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp:1305: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp:1330: `signo_t' was not declared in this scope
> thread.cpp:1330: parse error before `)' token
> thread.cpp:1331: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp: In member function `void ost::PosixThread::waitSignal(...)'=
:
> thread.cpp:1335: `signo' undeclared (first use this function)
> thread.cpp:1339: `sigwait' undeclared (first use this function)
> thread.cpp: At global scope:
> thread.cpp:1344: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp:1356: type specifier omitted for parameter `signo_t'
> thread.cpp:1356: parse error before `)' token
> thread.cpp:1357: invalid use of undefined type `struct ost::PosixThread=
'
> ../include/cc++/thread.h:1055: forward declaration of `struct
> ost::PosixThread'
> thread.cpp: In member function `void ost::PosixThread::signalThread(...=
)':
> thread.cpp:1358: `th' undeclared (first use this function)
> make[1]: *** [thread.lo] Error 1
> make[1]: Leaving directory `/home/emde/commoncpp2-1.0.2/src'
> make: *** [all-recursive] Error 1
>
> emde@TAUSTE ~/commoncpp2-1.0.2
> $ g++ -v
> Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/specs
> Configured with: /netrel/src/gcc-3.2-1/configure
> --enable-languages=3Dc,c++,f77,ja
> va --enable-libgcj --enable-threads=3Dposix --with-system-zlib
> --enable-nls --with
> out-included-gettext --enable-interpreter --disable-sjlj-exceptions
> --disable-ve
> rsion-specific-runtime-libs --enable-shared --build=3Di686-pc-linux
> --host=3Di686-pc
> -cygwin --target=3Di686-pc-cygwin --enable-haifa --prefix=3D/usr
> --exec-prefix=3D/usr
> --sysconfdir=3D/etc --libdir=3D/usr/lib --includedir=3D/nonexistent/inc=
lude
> --libexecd
> ir=3D/usr/sbin
> Thread model: posix
> gcc version 3.2 20020818 (prerelease)
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From dyfet@ostel.com Sun Oct 06 12:02:03 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yDqq-0008N0-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 12:01:52 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yDqc-0007yZ-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 12:01:39 -0400
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)
	id 17yDqH-0007XP-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 12:01:18 -0400
Received: from home.sys (IDENT:MB3Hbx4pC2dy8tHVCPOF2SlJxApWQICQ@home.sys [172.16.1.254])
	by home.sys (8.11.6/8.11.6) with ESMTP id g96GLQr27200;
	Sun, 6 Oct 2002 12:21:27 -0400
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Victor Porton <porton@ex-code.com>, bug-commoncpp@gnu.org
Subject: Re: My patch
Date: Sun, 6 Oct 2002 12:21:26 -0400
User-Agent: KMail/1.4.3
References: <E17q41I-0002Qw-00.porton-narod-ru@home.porton.narod.ru>
In-Reply-To: <E17q41I-0002Qw-00.porton-narod-ru@home.porton.narod.ru>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200210061221.26143.dyfet@ostel.com>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

I have found a slightly different approach to this, but yes, it will be f=
ixed.

On Friday 13 September 2002 23:54, Victor Porton wrote:
> As std::string::string(const char*) cannot be called with NULL argument
> (SIGSEGV for me), it should be patched. See the attachment.




From dyfet@ostel.com Sun Oct 06 12:13:06 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yE14-0001Ax-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 12:12:26 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yE0b-0008Rh-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 12:12:01 -0400
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)
	id 17yE0B-0007VN-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 12:11:31 -0400
Received: from home.sys (IDENT:kN7Grvx3fFhhfLcmuyEXAB0q8ktPvLGw@home.sys [172.16.1.254])
	by home.sys (8.11.6/8.11.6) with ESMTP id g96GVdr03501;
	Sun, 6 Oct 2002 12:31:39 -0400
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Ville V Sinkko <vsinkko@cc.helsinki.fi>, <bug-commoncpp@gnu.org>
Subject: Re: Threadlock class causing a compile error; make gripe
Date: Sun, 6 Oct 2002 12:31:39 -0400
User-Agent: KMail/1.4.3
References: <Pine.OSF.4.30.0209291640330.12040-100000@vesuri.Helsinki.FI>
In-Reply-To: <Pine.OSF.4.30.0209291640330.12040-100000@vesuri.Helsinki.FI>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200210061231.39339.dyfet@ostel.com>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

You need to use the compile time flags that "ccgnu2-config" reports to=20
correctly compile and link Common C++.

On Sunday 29 September 2002 09:54, Ville V Sinkko wrote:
> First:
>
> gcc 2.95.4, commoncpp-1.0.2. Compiling a first test program which inclu=
des
> cc++/thread.h. Error:
>
> =09/usr/local/include/cc++/thread.h:313: syntax error before `;'
>
> Ie. the first effective line of the declaration of class ThreadLock. My
> system does have pthread_rwlock_t (defined in bits/pthreadtypes.h, it
> seems).
>
>
>
> Second:
>
> 'Make install' puts all the header files in <wherever>/cc++2/cc++/, but
> all the headers look for each other in just <wherever>/cc++/, so you ne=
ed
> to move the header directory by hand after installing it if you want th=
e
> headers to function.
>
>
>
>
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From dyfet@ostel.com Sun Oct 06 12:16:09 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yE3f-0008Kn-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 12:15:07 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yE3T-0007ig-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 12:15:00 -0400
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)
	id 17yE2K-0004mn-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 12:13:44 -0400
Received: from home.sys (IDENT:0lfWO12H4cPvJhX/6+wXLYnTXsT//4mo@home.sys [172.16.1.254])
	by home.sys (8.11.6/8.11.6) with ESMTP id g96GXrr03531;
	Sun, 6 Oct 2002 12:33:53 -0400
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: "Laurent" <laurent@c64.org>, <bug-commoncpp@gnu.org>
Subject: Re: Restarting a Thread under Win32
Date: Sun, 6 Oct 2002 12:33:53 -0400
User-Agent: KMail/1.4.3
References: <008301c256a9$56f47bc0$0200a8c0@sid6581>
In-Reply-To: <008301c256a9$56f47bc0$0200a8c0@sid6581>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200210061233.53147.dyfet@ostel.com>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Once a thread exits run it cannot be "restarted", at least at present.  Y=
ou=20
can "suspend" and "resume" a thread while it is in "run", but that is=20
different...



On Saturday 07 September 2002 16:01, Laurent wrote:
> Hi,
>
> I'm no sure this is a bug :
> When i create a thread, start it, and when it exit from the run() metho=
d, i
> can't start() it again. Is it normal ? the isRunning() method returns
> false, so i thought i could restart it.
>
> Also, could you tell me where can i suscribe to this mailing list, as i
> don't think i'll be able to receive your answer.
>
> Thank you,
> Laurent




From fedemp@wanadoo.es Sun Oct 06 14:59:23 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yGbO-00060I-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 14:58:06 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yGaq-000570-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 14:57:33 -0400
Received: from [62.37.236.138] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yGaA-0004uJ-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 14:56:50 -0400
Received: from risitas ([80.103.113.164])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g96IuJt23695
	for <bug-commoncpp@gnu.org>; Sun, 6 Oct 2002 20:56:20 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17yGd4-0000Lr-00
	for <bug-commoncpp@gnu.org>; Sun, 06 Oct 2002 20:59:50 +0200
Date: Sun, 6 Oct 2002 20:59:50 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: What is going on this list? There are a lot of sudden bug reports :)
Message-ID: <20021006185950.GA601@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Hi,

	From what I read in some of the later posts to this list, I
guess that the flood of old bug reports and comments that have
appeared consists of posts that were blocked by mailman because the
authors are not subscribed to the list. Are we still receiving so much
SPAM as some months ago? I believed the Savannah hackers had
incorporated SPAM filters to the GNU mail machines.

	Apart from other fixes that were pending before this flood, we
now have some more fixes to do. Among them, there is a serious bug
report from Mark Purcell regarding the use of asm/atomic.h. I think
this is of high priority and I will incorporate this patch if there is
no problem with removing the use of asm/atomic.h and the
HAVE_ASM_ATOMIC... defines.




From fedemp@wanadoo.es Sun Oct 06 15:04:44 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yGgX-00052W-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:03:25 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yGfw-0004hS-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:02:49 -0400
Received: from [62.37.236.139] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yGfU-000493-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:02:20 -0400
Received: from risitas ([80.103.113.164])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gALKuoA22808;
	Thu, 21 Nov 2002 21:56:50 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17yGiM-0000Rg-00; Sun, 06 Oct 2002 21:05:18 +0200
Date: Sun, 6 Oct 2002 21:05:18 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chris Ahlstrom <ahlstromc@comcast.net>
Cc: bug-commoncpp@gnu.org
Subject: Re: Linkage problem?
Message-ID: <20021006190518.GB601@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Chris Ahlstrom <ahlstromc@comcast.net>,
	bug-commoncpp@gnu.org
References: <Pine.LNX.4.33.0209042239280.28001-100000@mlsmoe>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.33.0209042239280.28001-100000@mlsmoe>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Hi,

	I do not understand well the problem you describe. Is the file
`tcptest' generated? Does g++ or ld report any warning/error?

	Anyway, your makefile should use the compiler options provided
by the script `ccgnu2-config', which is installed on your machine
binary path when you install commoncpp2. The usage of this script is
described in the chapter "Compiler Options" of the manual included
with later releases of commoncpp2.

On Wed, Sep 04, 2002 at 10:44:14PM -0400, Chris Ahlstrom wrote:
> I am building a project with a simple makefile (no
> automake/libtool stuff).  The makefile compiles
> my modules, then uses ld to link them to Common C++.
> When I run the executable, I get this:
> 
> bash: ./tcptest: No such file or directory
> 
> and get a similar result using gdb and ldd.
> 
> Is this a linkage problem?  Where can I go to
> learn how to fix this problem?
> 
> Thanks, even if you can't help me.
> 
> Chris (a linonut)
> 
> -- 
> Hope your day is as good as mine!




From fedemp@wanadoo.es Sun Oct 06 15:16:04 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yGrm-00059p-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:15:02 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yGod-0004Rc-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:11:49 -0400
Received: from [62.37.236.139] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yGlh-0002NO-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:08:45 -0400
Received: from risitas ([80.103.113.164])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gALL3BA23750;
	Thu, 21 Nov 2002 22:03:11 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17yGoV-0000Ru-00; Sun, 06 Oct 2002 21:11:39 +0200
Date: Sun, 6 Oct 2002 21:11:39 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: COFFMAN Steven <SCoffman@covansys.com>
Cc: "'bug-commoncpp@gnu.org'" <bug-commoncpp@gnu.org>
Subject: Re: Problems compiling on Red Hat latest beta
Message-ID: <20021006191139.GC601@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: COFFMAN Steven <SCoffman@COVANSYS.com>,
	"'bug-commoncpp@gnu.org'" <bug-commoncpp@gnu.org>
References: <4EB41326BAB06F4398681348D8118C9C042EAE@fth-ex01.CVNS.corp.covansys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4EB41326BAB06F4398681348D8118C9C042EAE@fth-ex01.CVNS.corp.covansys.com>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Yes, we have received other bug reports regarding
asm/atomic.h. This will be fixed soon. In the meantime, as a quick and
very dirty hack, you can simply comment all the
HAVE_ASM_ATOMIC... defines in the common c++ config.h.

	As for the automake/aclocal problem, with some of the last
releases of the autotools you may see some warnings because of the
combination of different releases of different tools. Many times, it
simply works regardless of the warnings. If you can, upgrade to the
latest release of Common C++ (Common C++ 2 1.0.4) and try it.

On Fri, Sep 06, 2002 at 12:20:07PM -0400, COFFMAN Steven wrote:
> Hi,
> 
> 	My apologies if this problem has been dealt with before, but my
> google skills failed to turn up anything similar.
> 
> 	I had trouble compiling CommonC++ 1.9.7 on the latest Red Hat beta
> (null) which means I use gcc 3.2, a modified 2.4.18 kernel, and automake
> 1.6.3. I "./configure" just fine. When I "make", I get everything fine until
> this:
> 
> mutex.cpp: In member function `int ost::AtomicCounter::operator++()':
> mutex.cpp:341: `atomic_inc' undeclared (first use this function)
> mutex.cpp:341: (Each undeclared identifier is reported only once for each
> function it appears in.)
> mutex.cpp: In member function `int ost::AtomicCounter::operator--()':
> mutex.cpp:347: `atomic_dec_and_test' undeclared (first use this function)
> mutex.cpp: In member function `int ost::atomicCounter::operator-=(int)':
> mutex.cpp:364: `atomic_sub' undeclared (first use this function)
> make[1]: *** [mutex.o] Error 1
> make[1]: Leaving directory `home/gears/building/CommonC++-1.9.7/src'
> make: *** [all-recursive] Error 1
> 
> Since you use a kernel header in a userland program, I don't know if the
> kernel version is not compatible with this release of CommonC++ or what. Is
> there a patch or something obvious to change?
> 
> As an alternative, I attempted to install the Mandrake cooker Source RPM for
> CommonC++ 1.6.0, but when I "rpmbuild -rebuild CommonC++-1.6.0-1mdk.src.rpm"
> on the latest Red Hat beta, I get past the Patch #1 (libxml2 patch), to the 
> Automake Makefile and get get:
> Configure.in:19: your implementation of AM_INIT_AUTOMAKE comes from an old
> Automake version. You should recreate aclocal.m4 with aclocal and run
> automake again.
> 
> Since I have automake 1.6.3 installed, and I have no idea what the heck that
> aclocal stuff is all about, that only confused me more.
> 
> I realize this is probably something incredibly simple I've missed, but I
> would be very grateful to anyone who could help out. To further compound my
> ignorance, I didn't notice where to subscribe to this list. Could you
> possibly cc me with any replies?
> 
> -Steve
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fedemp@wanadoo.es Sun Oct 06 15:16:39 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yGtG-00060q-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:16:34 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yGsu-0005nz-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:16:13 -0400
Received: from [62.37.236.138] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yGqa-0004oj-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:13:48 -0400
Received: from risitas ([80.103.113.164])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g96JDHt26721;
	Sun, 6 Oct 2002 21:13:17 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17yGtU-0000SK-00; Sun, 06 Oct 2002 21:16:48 +0200
Date: Sun, 6 Oct 2002 21:16:47 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Laurent <laurent@c64.org>
Cc: bug-commoncpp@gnu.org
Subject: Re: Restarting a Thread under Win32
Message-ID: <20021006191647.GD601@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Laurent <laurent@c64.org>, bug-commoncpp@gnu.org
References: <008301c256a9$56f47bc0$0200a8c0@sid6581>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <008301c256a9$56f47bc0$0200a8c0@sid6581>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

On Sat, Sep 07, 2002 at 10:01:21PM +0200, Laurent wrote:
> Also, could you tell me where can i suscribe to this mailing list, as i don't think i'll be able to receive your answer.
> 

	You can use the generic mailman interface for GNU lists. The
Common C++ one is at:

	http://mail.gnu.org/mailman/listinfo/bug-commoncpp/

	You can also use the Savannah interface: http://sv.gnu.org

> Thank you,
> Laurent



From fedemp@wanadoo.es Sun Oct 06 15:23:32 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yGzy-0002HA-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:23:30 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yGzY-0001SY-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:23:07 -0400
Received: from [62.37.236.139] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yGyl-0007Us-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:22:15 -0400
Received: from risitas ([80.103.113.164])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gALLGjA25921;
	Thu, 21 Nov 2002 22:16:46 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17yH1e-0000TA-00; Sun, 06 Oct 2002 21:25:14 +0200
Date: Sun, 6 Oct 2002 21:25:14 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Leonard Thornton <leonardt@intelis-inc.com>
Cc: bug-commoncpp@gnu.org
Subject: Re: Bug in Win32 yield()
Message-ID: <20021006192513.GE601@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Leonard Thornton <leonardt@intelis-inc.com>,
	bug-commoncpp@gnu.org
References: <5.1.1.6.0.20020911142732.03b2cdc0@pop.business.earthlink.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.1.1.6.0.20020911142732.03b2cdc0@pop.business.earthlink.net>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Thanks. Fixed in CVS for next releases. Very curious
optimization :)

On Wed, Sep 11, 2002 at 02:31:28PM -0400, Leonard Thornton wrote:
>   void    Thread::yield(void)
>   {
>   #ifdef WIN32
>   //      Thread::sleep(0);       <=======Currently
>           Thread::sleep(1);       <=======Should be
>   #else
>   .
>   .
>   .
>
>   This resolves a known problem in Win32 where all Sleep(0) is compiled to a
>   NOP rather than a processor yield.
>
>   Leonard Thornton
>   Intelis, Inc.
>   770.825.0032
>   leonardt@intelis-inc.com _______________________________________________
>   Bug-commoncpp mailing list Bug-commoncpp@gnu.org
>   http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>



From dyfet@ostel.com Sun Oct 06 15:28:42 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yH4r-0003Fw-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:28:33 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yH4b-0002hW-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:28:24 -0400
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)
	id 17yH4O-000215-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:28:04 -0400
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id g96JmAJ04849;
	Sun, 6 Oct 2002 15:48:10 -0400
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sun, 6 Oct 2002 15:48:10 -0400 (EDT)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: What is going on this list? There are a lot of sudden bug reports
 :)
In-Reply-To: <20021006185950.GA601@risitas>
Message-ID: <Pine.LNX.4.44.0210061547070.4835-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Yes, I discovered that they did, and that was a much cleaner result :).  
I think the atomic issue is critically important on some compile targets, 
and of course debian is targetted architecturally everywhere :)..

On Sun, 6 Oct 2002, Federico Montesino Pouzols wrote:

> 
> 	Hi,
> 
> 	From what I read in some of the later posts to this list, I
> guess that the flood of old bug reports and comments that have
> appeared consists of posts that were blocked by mailman because the
> authors are not subscribed to the list. Are we still receiving so much
> SPAM as some months ago? I believed the Savannah hackers had
> incorporated SPAM filters to the GNU mail machines.
> 
> 	Apart from other fixes that were pending before this flood, we
> now have some more fixes to do. Among them, there is a serious bug
> report from Mark Purcell regarding the use of asm/atomic.h. I think
> this is of high priority and I will incorporate this patch if there is
> no problem with removing the use of asm/atomic.h and the
> HAVE_ASM_ATOMIC... defines.
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From fedemp@wanadoo.es Sun Oct 06 15:26:43 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yH2j-0005wu-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:26:21 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yH2Y-0005WS-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:26:16 -0400
Received: from [62.37.236.138] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yH1U-00040V-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:25:05 -0400
Received: from risitas ([80.103.113.164])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g96JORt28607;
	Sun, 6 Oct 2002 21:24:27 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17yH4I-0000TR-00; Sun, 06 Oct 2002 21:27:58 +0200
Date: Sun, 6 Oct 2002 21:27:58 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Victor Porton <porton@ex-code.com>
Cc: bug-commoncpp@gnu.org
Subject: Re: My patch
Message-ID: <20021006192758.GF601@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Victor Porton <porton@ex-code.com>, bug-commoncpp@gnu.org
References: <E17q4Ds-0002iv-00.porton-narod-ru@home.porton.narod.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E17q4Ds-0002iv-00.porton-narod-ru@home.porton.narod.ru>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

On Sat, Sep 14, 2002 at 10:07:56AM +0600, Victor Porton wrote:
> Well, this should be applied not only to include/cc++, but also to src dir. 
> Why, you have copies of the same files in two places? Please distribute your 
> .tar.gz with symlinks, not with copies of *.h files.
> 

	What files are included twice?




From dyfet@ostel.com Sun Oct 06 15:30:16 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yH6D-00079x-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:29:57 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yH5z-0006UW-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:29:45 -0400
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)
	id 17yH5s-00069M-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:29:36 -0400
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id g96Jnh104862;
	Sun, 6 Oct 2002 15:49:43 -0400
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sun, 6 Oct 2002 15:49:43 -0400 (EDT)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: Leonard Thornton <leonardt@intelis-inc.com>, <bug-commoncpp@gnu.org>
Subject: Re: Bug in Win32 yield()
In-Reply-To: <20021006192513.GE601@risitas>
Message-ID: <Pine.LNX.4.44.0210061549180.4835-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Yes, that is an ammusing optimization :)...

On Sun, 6 Oct 2002, Federico Montesino Pouzols wrote:

> 
> 	Thanks. Fixed in CVS for next releases. Very curious
> optimization :)
> 
> On Wed, Sep 11, 2002 at 02:31:28PM -0400, Leonard Thornton wrote:
> >   void    Thread::yield(void)
> >   {
> >   #ifdef WIN32
> >   //      Thread::sleep(0);       <=======Currently
> >           Thread::sleep(1);       <=======Should be
> >   #else
> >   .
> >   .
> >   .
> >
> >   This resolves a known problem in Win32 where all Sleep(0) is compiled to a
> >   NOP rather than a processor yield.
> >
> >   Leonard Thornton
> >   Intelis, Inc.
> >   770.825.0032
> >   leonardt@intelis-inc.com _______________________________________________
> >   Bug-commoncpp mailing list Bug-commoncpp@gnu.org
> >   http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> >
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From fedemp@wanadoo.es Sun Oct 06 15:42:33 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yHGi-0007Li-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:40:48 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yHG1-0006h1-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:40:07 -0400
Received: from [62.37.236.136] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yHFE-0005kd-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 15:39:16 -0400
Received: from risitas ([80.103.113.164])
	by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id g96JWxu28298;
	Sun, 6 Oct 2002 21:32:59 +0200 (MEST)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17yHHy-0000U7-00; Sun, 06 Oct 2002 21:42:06 +0200
Date: Sun, 6 Oct 2002 21:42:06 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ville V Sinkko <vsinkko@cc.helsinki.fi>
Cc: bug-commoncpp@gnu.org
Subject: Re: Threadlock class causing a compile error; make gripe
Message-ID: <20021006194206.GG601@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Ville V Sinkko <vsinkko@cc.helsinki.fi>,
	bug-commoncpp@gnu.org
References: <Pine.OSF.4.30.0209291640330.12040-100000@vesuri.Helsinki.FI> <200210061231.39339.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200210061231.39339.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Yes, the usage of ccgnu2-config is described in the chapter
"Compiler Options" in the manual distributed with later versions of
commoncpp2.

On Sun, Oct 06, 2002 at 12:31:39PM -0400, David Sugar wrote:
> You need to use the compile time flags that "ccgnu2-config" reports to 
> correctly compile and link Common C++.
> 
> On Sunday 29 September 2002 09:54, Ville V Sinkko wrote:
> > First:
> >
> > gcc 2.95.4, commoncpp-1.0.2. Compiling a first test program which includes
> > cc++/thread.h. Error:
> >
> > 	/usr/local/include/cc++/thread.h:313: syntax error before `;'
> >
> > Ie. the first effective line of the declaration of class ThreadLock. My
> > system does have pthread_rwlock_t (defined in bits/pthreadtypes.h, it
> > seems).
> >
> >
> >
> > Second:
> >
> > 'Make install' puts all the header files in <wherever>/cc++2/cc++/, but
> > all the headers look for each other in just <wherever>/cc++/, so you need
> > to move the header directory by hand after installing it if you want the
> > headers to function.
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fedemp@wanadoo.es Sun Oct 06 16:25:14 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yHwf-0003JW-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 16:24:09 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yHvv-0001jq-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 16:23:24 -0400
Received: from [62.37.236.138] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yHtt-00018f-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 16:21:17 -0400
Received: from risitas ([80.103.113.164])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g96KK7t05772;
	Sun, 6 Oct 2002 22:20:08 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17yHwA-0005aP-00; Sun, 06 Oct 2002 22:23:38 +0200
Date: Sun, 6 Oct 2002 22:23:38 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Mark Purcell <msp@debian.org>
Cc: bug-commoncpp@gnu.org, 154911-forwarded@bugs.debian.org
Subject: Re: [owner@bugs.debian.org: Bug#154911: marked as done (commoncpp2: FTBFS: including <asm/atomic.h> is not legal in user space)]
Message-ID: <20021006202338.GH601@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Mark Purcell <msp@debian.org>, bug-commoncpp@gnu.org,
	154911-forwarded@bugs.debian.org
References: <20020922034622.GA26277@htpc.purcell.homeip.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020922034622.GA26277@htpc.purcell.homeip.net>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Hi, this has been fixed in CVS, for both 1.1 and 1.0
series. Now, there is no check for <asm/atomic.h> and there are no
HAVE_ASM_ATOMIC... defines. Thanks for the report.

On Sun, Sep 22, 2002 at 01:46:23PM +1000, Mark Purcell wrote:
> David (and others),
> 
> I have received this bug report about the commoncpp2 libraries. This patch 
> has been included in the Debian GNU/Linux commoncpp2 package, but you 
> might also like to include it with your upstream source.
> 
> Mark
> 
> 
> ----- Forwarded message from Debian Bug Tracking System <owner@bugs.debian.org> -----
> 



From fedemp@wanadoo.es Sun Oct 06 16:34:42 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yI6L-0001N5-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 16:34:09 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yI4s-0008An-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 16:32:43 -0400
Received: from [62.37.236.138] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yI43-0006o8-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 16:31:47 -0400
Received: from risitas ([80.103.113.164])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g96KV3t07684;
	Sun, 6 Oct 2002 22:31:04 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17yI6l-0005ae-00; Sun, 06 Oct 2002 22:34:35 +0200
Date: Sun, 6 Oct 2002 22:34:34 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Spinka, Kristofer" <kspinka@gist.com>
Cc: bug-commoncpp@gnu.org
Subject: Re: Solaris 9, SocketPort
Message-ID: <20021006203434.GI601@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: "Spinka, Kristofer" <kspinka@gist.com>,
	bug-commoncpp@gnu.org
References: <3DA00BA5.3020905@gist.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DA00BA5.3020905@gist.com>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Hi, the problem you are talking about seems to arise on Win32
too. Some weeks ago, we received the following report from Klaus
Triendl:

--------------------------------------------
i tested the SampleSocketServiceServer with linux and windows. under windows
an exception is thrown in StopServer().
i traced the problem and figured out that WSAGetLastError() in
Socket::connectError() returns WSAEFAULT (=10014L).


	virtual void StopServer()
	{
		m_bQuitServer = true;

		InetHostAddress host;
		tpport_t port;
		host = getLocal(&port);

		//This is required so that CreateSocketPort can return.
		TCPStream strm(host, port);

		waitMutex.enterMutex();
		waitMutex.leaveMutex();
	}


if i change the code a little and the host is initialized with an address
other than 0, there is not such a problem.


	virtual void StopServer()
	{
		m_bQuitServer = true;

		InetHostAddress host("127.0.0.1");
		tpport_t port;
		getLocal(&port);

		//This is required so that CreateSocketPort can return.
		TCPStream strm(host, port);

		waitMutex.enterMutex();
		waitMutex.leaveMutex();
	}
-----------------------------------------

	Could you confirm if the same happens to you? You can also
read the whole thread on this mail list archives (September, thread
"exception in SampleSocketServiceServer::StopServer()"). We were
planning to add some checks on Win32, but if it is the same problem
what you are having on Solaris 9, we should probably add the checks
for all platforms.

On Sun, Oct 06, 2002 at 06:08:37AM -0400, Spinka, Kristofer wrote:
>   I haven't had the time to track anything down, however, if you try 
> running the portsample (SampleSocketPort.cpp), you will see the problem 
> immediately after the first client disconnects.
> 
>     /kris
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Sun Oct 06 19:38:27 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yKyc-0002p9-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 19:38:22 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yKwt-0001tr-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 19:36:39 -0400
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)
	id 17yKsu-0000f9-00
	for bug-commoncpp@gnu.org; Sun, 06 Oct 2002 19:32:28 -0400
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id g96NqbR06258;
	Sun, 6 Oct 2002 19:52:37 -0400
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sun, 6 Oct 2002 19:52:37 -0400 (EDT)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: Mark Purcell <msp@debian.org>, <bug-commoncpp@gnu.org>,
   <154911-forwarded@bugs.debian.org>
Subject: Re: [owner@bugs.debian.org: Bug#154911: marked as done (commoncpp2:
 FTBFS: including <asm/atomic.h> is not legal in user space)]
In-Reply-To: <20021006202338.GH601@risitas>
Message-ID: <Pine.LNX.4.44.0210061951540.6249-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

We will probably do a new (1.0.4) release by the end of next week to give
enough time to evaluate some of the other bug reports...


On Sun, 6 Oct 2002, Federico Montesino Pouzols wrote:

> 
> 	Hi, this has been fixed in CVS, for both 1.1 and 1.0
> series. Now, there is no check for <asm/atomic.h> and there are no
> HAVE_ASM_ATOMIC... defines. Thanks for the report.
> 
> On Sun, Sep 22, 2002 at 01:46:23PM +1000, Mark Purcell wrote:
> > David (and others),
> > 
> > I have received this bug report about the commoncpp2 libraries. This patch 
> > has been included in the Debian GNU/Linux commoncpp2 package, but you 
> > might also like to include it with your upstream source.
> > 
> > Mark
> > 
> > 
> > ----- Forwarded message from Debian Bug Tracking System <owner@bugs.debian.org> -----
> > 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From baumannd@msoe.edu Mon Oct 07 01:24:56 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yQO0-0001cE-00
	for bug-commoncpp@gnu.org; Mon, 07 Oct 2002 01:24:56 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yQNv-0001WB-00
	for bug-commoncpp@gnu.org; Mon, 07 Oct 2002 01:24:55 -0400
Received: from mke-24-167-202-50.wi.rr.com ([24.167.202.50] helo=frell.dyndns.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yQNu-0001KF-00
	for bug-commoncpp@gnu.org; Mon, 07 Oct 2002 01:24:50 -0400
Received: from obfuscation.dyndns.org ([192.168.1.2] ident=mail)
	by frell.dyndns.org with esmtp (Exim 3.36 #1 (Debian))
	id 17yQNm-0007vR-00
	for <bug-commoncpp@gnu.org>; Mon, 07 Oct 2002 00:24:42 -0500
Received: from localhost
	([127.0.0.1] helo=localhost.localdomain ident=danielb)
	by obfuscation.dyndns.org with esmtp (Exim 3.36 #1 (Debian))
	id 17yQNk-0003ej-00
	for <bug-commoncpp@gnu.org>; Mon, 07 Oct 2002 00:24:40 -0500
Subject: Piostreams Update
From: Daniel E Baumann <baumannd@msoe.edu>
To: GNU Common C++ List <bug-commoncpp@gnu.org>
Content-Type: multipart/mixed; boundary="=-QYI/PhWuNJ94Mw99Vg19"
X-Mailer: Ximian Evolution 1.0.8 
Date: 07 Oct 2002 00:24:39 -0500
Message-Id: <1033968280.14005.6.camel@obfuscation>
Mime-Version: 1.0
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

--=-QYI/PhWuNJ94Mw99Vg19
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Here's a small update to piostreams. All it really adds is some more
thread-safe methods to postream, i.e., for setting the state,
formatting, accessing the stream buffer, etc. Expect more to following
in the coming days like input streams :-) and perhaps the ability to
print identifying thread info with an even more comprehensive test
program (I really need to hit all methods of the stream classes).

Happy Hacking,
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

--=-QYI/PhWuNJ94Mw99Vg19
Content-Disposition: attachment; filename=piostreams.diff
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; name=piostreams.diff; charset=ANSI_X3.4-1968

? piostreams.diff
? config/depcomp
? config/texinfo.tex
? demo/pio
? doc/commoncpp2.info
? doc/commoncpp2.info-1
? doc/commoncpp2.info-2
? doc/commoncpp2.info-3
? include/stamp-h1
? include/cc++/pfstream
? ssl/Makefile
? ssl/Makefile.in
? win32/CCXX2.rc
Index: include/cc++/postream
=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++/postream,v
retrieving revision 1.1
diff -u -3 -p -r1.1 postream
--- include/cc++/postream	21 Sep 2002 18:26:57 -0000	1.1
+++ include/cc++/postream	7 Oct 2002 05:17:23 -0000
@@ -71,14 +71,15 @@ public:
 	typedef Traits                    		traits_type;
    =20
 	// Non-standard Types:
-	typedef basic_streambuf<charT, Traits> 	  streambuf_type;
-	//typedef basic_pstreambuf<charT, Traits> 	  pstreambuf_type;
-	typedef basic_ios<charT, Traits>		  ios_type;
-	typedef basic_ostream<charT, Traits>              ostream_type;
-	typedef basic_postream<charT, Traits>	          postream_type;
-	typedef ostreambuf_iterator<charT, Traits>        ostreambuf_iter;
-	typedef num_put<charT, ostreambuf_iter>           numput_type;
-	typedef ctype<charT>                              ctype_type;
+	typedef basic_streambuf<charT, Traits> 	        streambuf_type;
+	typedef basic_ios<charT, Traits>		ios_type;
+	typedef basic_ostream<charT, Traits>            ostream_type;
+	typedef basic_postream<charT, Traits>	        postream_type;
+	typedef ostreambuf_iterator<charT, Traits>      ostreambuf_iter;
+	typedef num_put<charT, ostreambuf_iter>         numput_type;
+	typedef ctype<charT>                            ctype_type;
+=09
+	typedef typename basic_postream<charT, Traits>::iostate  iostate_type;
=20
 	// Constructor/destructor:
 	explicit=20
@@ -98,22 +99,19 @@ public:
 	postream_type&
 	operator<<(postream_type& (*pf)(postream_type&));
=20
-	//postream_type&
-	//operator<<(ostream_type& (*pf)(ostream_type&));
-
 	postream_type&
 	operator<<(ios_type& (*pf)(ios_type&));
-     =20
+
 	postream_type&
 	operator<<(ios_base& (*pf)(ios_base&));
=20
 	// Arithmetic Inserters
 	postream_type&=20
 	operator<<(long n);
-     =20
+
 	postream_type&=20
 	operator<<(unsigned long n);
-=20
+
 	postream_type&=20
 	operator<<(bool n);
=20
@@ -187,6 +185,7 @@ public:
=20
 	postream_type&=20
 	seekp(pos_type);
+
 	postream_type&=20
 	seekp(off_type, ios_base::seekdir);
=20
@@ -197,96 +196,212 @@ public:
 	flags() const
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::flags();
+		return ostream_type::flags();
 	}
=20
 	inline ios_base::fmtflags=20
 	flags(ios_base::fmtflags fmtfl)
 	{=20
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::flags(fmtfl);
+		return ostream_type::flags(fmtfl);
 	}
=20
 	inline ios_base::fmtflags=20
 	setf(ios_base::fmtflags fmtfl)
 	{=20
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::setf(fmtfl);
+		return ostream_type::setf(fmtfl);
 	}
=20
 	inline ios_base::fmtflags=20
 	setf(ios_base::fmtflags fmtfl, ios_base::fmtflags mask)
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::setf(fmtfl, mask);
+		return ostream_type::setf(fmtfl, mask);
 	}
=20
 	inline void=20
 	unsetf(ios_base::fmtflags mask)=20
 	{=20
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::unsetf(mask);
+		ostream_type::unsetf(mask);
 	}
=20
 	inline streamsize=20
 	precision() const=20
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::precision();
+		return ostream_type::precision();
 	}
=20
 	inline streamsize=20
 	precision(streamsize prec)
 	{=20
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::precision(prec);
+		return ostream_type::precision(prec);
 	}
=20
 	inline streamsize=20
 	width() const=20
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::width();
+		return ostream_type::width();
 	}
=20
 	inline streamsize=20
 	width(streamsize wide)
 	{=20
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::width(wide);
+		return ostream_type::width(wide);
 	}
=20
-	static bool=20
-	sync_with_stdio(bool sync =3D true);
-
-	// Locales:
-	locale=20
-	imbue(const locale& loc);
+	//static bool=20
+	//sync_with_stdio(bool sync =3D true);
=20
 	inline locale=20
 	getloc() const=20
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::getloc();
+		return ostream_type::getloc();
 	}
=20
 	// Storage:
-	static int=20
-	xalloc() throw();
+	//static int=20
+	//xalloc() throw();
=20
 	inline long&=20
 	iword(int ix)
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::iword(ix);
+		return ostream_type::iword(ix);
 	}
=20
 	inline void*&=20
 	pword(int ix)
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::pword(ix);
+		return ostream_type::pword(ix);
+	}
+
+	// std::basic_ios methods
+
+	//operator void*() const=20
+	//{ return this->fail() ? 0 : const_cast<basic_ios*>(this); }
+
+	//bool=20
+	//operator!() const=20
+	//{ return this->fail(); }
+
+	iostate_type=20
+	rdstate() const=20
+	{=20
+		MutexLock mlock(lock);
+		return ostream_type::rdstate();
+	}
+
+	void=20
+	clear(iostate_type state =3D goodbit);
+
+	void=20
+	setstate(iostate_type state)=20
+	{=20
+		MutexLock mlock(lock);
+		ostream_type::setstate(state);
+	}
+
+	bool=20
+	good() const=20
+	{=20
+		MutexLock mlock(lock);
+		return ostream_type::good();
+	}
+
+	bool=20
+	eof() const=20
+	{=20
+		MutexLock mlock(lock);
+		return ostream_type::eof();
+	}
+
+	bool=20
+	fail() const=20
+	{
+		MutexLock mlock(lock);
+		return ostream_type::fail();
+	}
+
+	bool=20
+	bad() const=20
+	{
+		MutexLock mlock(lock);
+		return ostream_type::bad();
 	}
+
+	iostate_type=20
+	exceptions() const=20
+	{=20
+		MutexLock mlock(lock);
+		return ostream_type::exceptions();
+	}
+
+	void=20
+	exceptions(iostate_type except)=20
+	{=20
+		MutexLock mlock(lock);
+		ostream_type::exceptions(except);
+	}
+
+	// Members:
+        basic_postream<charT, Traits>*
+	tie() const     =20
+	{
+		MutexLock mlock(lock);
+		return ostream_type::tie();
+	}
+
+	basic_ostream<charT, Traits>*
+	tie(basic_ostream<charT, Traits>* tiestr)
+	{
+		MutexLock mlock(lock);
+		return ostream_type::tie(tiestr);
+	}
+
+	basic_streambuf<charT, Traits>*
+	rdbuf() const   =20
+	{
+		MutexLock mlock(lock);
+		return ostream_type::rdbuf();
+	}
+
+	basic_streambuf<charT, Traits>*=20
+	rdbuf(basic_streambuf<charT, Traits>* sb);
+
+	//std::basic_ios&
+	//copyfmt(const basic_ios& rhs);
+
+	char_type=20
+	fill() const=20
+	{
+		MutexLock mlock(lock);
+		return ostream_type::fill();
+	}
+
+	char_type=20
+	fill(char_type ch)
+	{
+		MutexLock mlock(lock);
+		return ostream_type::fill(ch);
+	}
+
+	// Locales:
+	locale=20
+	imbue(const locale& locb);
+
+	char=20
+	narrow(char_type c, char dfault) const;
+
+	char_type=20
+	widen(char c) const;
=20
 	Thread* currth;
 	int pid;
Index: include/cc++/postream.tcc
=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++/postream.tcc,v
retrieving revision 1.1
diff -u -3 -p -r1.1 postream.tcc
--- include/cc++/postream.tcc	21 Sep 2002 18:26:57 -0000	1.1
+++ include/cc++/postream.tcc	7 Oct 2002 05:17:23 -0000
@@ -144,38 +144,25 @@ operator<<(ios_base& (*pf)(ios_base&))
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(streambuf_type* sbin)
+basic_postream<charT, Traits>::operator<<(long n)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 =09
-	ostream_type::operator<<(sbin);
-=09
-	return *this;
-}
-
-template<typename charT, typename Traits>
-basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(bool n)
-{
-	// 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<<(n);
-     =20
+
 	return *this;
 }
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(long n)
+basic_postream<charT, Traits>::operator<<(unsigned long n)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
-=09
+
 	ostream_type::operator<<(n);
=20
 	return *this;
@@ -183,14 +170,14 @@ basic_postream<charT, Traits>::operator<
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(unsigned long n)
+basic_postream<charT, Traits>::operator<<(bool n)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
=20
 	ostream_type::operator<<(n);
-
+     =20
 	return *this;
 }
=20
@@ -223,44 +210,57 @@ basic_postream<charT, Traits>::operator<
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(double n)
+basic_postream<charT, Traits>::operator<<(double f)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 =09
-	ostream_type::operator<<(n);
+	ostream_type::operator<<(f);
 =09
 	return *this;
 }
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(long double n)
+basic_postream<charT, Traits>::operator<<(long double f)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 =09
-	ostream_type::operator<<(n);
+	ostream_type::operator<<(f);
      =20
 	return *this;
 }
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(const void* n)
+basic_postream<charT, Traits>::operator<<(const void* p)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
=20
-	ostream_type::operator<<(n);
+	ostream_type::operator<<(p);
      =20
 	return *this;
 }
=20
 template<typename charT, typename Traits>
+basic_postream<charT, Traits>&=20
+basic_postream<charT, Traits>::operator<<(streambuf_type* sbin)
+{
+	// Create a psentry object (may set error bits or throw failure)
+	typedef basic_postream<charT, Traits> postream_type;
+	typename postream_type::psentry opfx(*this);
+=09
+	ostream_type::operator<<(sbin);
+=09
+	return *this;
+}
+
+template<typename charT, typename Traits>
 basic_postream<charT, Traits>&
 basic_postream<charT, Traits>::put(char_type c)
 {=20
@@ -303,7 +303,7 @@ template<typename charT, typename Traits
 typename basic_postream<charT, Traits>::pos_type
 basic_postream<charT, Traits>::tellp()
 {
-	// TODO: make this operation thread-safe?
+	MutexLock mlock(lock);
 	ostream_type::tellp();
      =20
 	return *this;
@@ -313,10 +313,10 @@ template<typename charT, typename Traits
 basic_postream<charT, Traits>&
 basic_postream<charT, Traits>::seekp(pos_type pos)
 {
-	// TODO: make this operation thread-safe?
+	MutexLock mlock(lock);
 	ostream_type::seekp(pos);
 =09
-	return this;
+	return *this;
 }
=20
 template<typename charT, typename Traits>
@@ -324,61 +324,40 @@ basic_postream<charT, Traits>&
 basic_postream<charT, Traits>::
 seekp(off_type off, ios_base::seekdir d)
 {
-	// TODO: make this operation thread-safe?
+	MutexLock mlock(lock);
 	ostream_type::seekp(d);
 =09
 	return *this;
 }
=20
-template<typename charT, typename Traits>
-void
-basic_postream<charT, Traits>::lockStream()
-{
-	if(!owned)
-	{
-		currth =3D ost::getThread();
-		owned =3D true;
-		pid =3D getpid();
-		tid =3D currth->getThreadID();
-		if(!header)
-		{
-			outputHeader();
-			header =3D true;
-		}
-	}
-	lock.enterMutex();
-	lockcnt++;
-}
=20
-template<typename charT, typename Traits>
-void
-basic_postream<charT, Traits>::unlockStream()
-{
-	mtx.enterMutex();
-	if(owned)
-	{
-		currth =3D NULL;
-		owned =3D false;
-		pid =3D 0;
-		tid =3D 0;
-		header =3D false;
-	}
-	while(lockcnt !=3D 0)
-	{
-		lock.leaveMutex();
-		lockcnt--;
-	}
-	mtx.leaveMutex();
-	printf("fully unlocked\n");
-}
+// TODO: May have to move this to pios.cpp?
+//int
+//postream::xalloc() throw()
+//{
+	//MutexLock mlock(lock);
+//	return ostream_type::xalloc();
+//}
=20
 template<typename charT, typename Traits>
-void
-basic_postream<charT, Traits>::outputHeader()
+basic_streambuf<charT, Traits>*
+basic_postream<charT, Traits>::
+rdbuf(basic_streambuf<charT, Traits>* sb)
 {
-	*this << "PID: " << pid << ", TID: " << tid << "> ";
+	MutexLock mlock(lock);
+	return ostream_type::rdbuf();
 }
=20
+//template<typename charT, typename Traits>
+//basic_ios&
+//basic_postream<charT, Traits>::
+//copyfmt(const basic_ios& rhs)
+//{
+//	MutexLock mlock(lock);
+//	return ostream_type::copyfmt(rhs);
+//}
+							  =20
+
 // Character inserters.
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&
@@ -393,6 +372,36 @@ operator<<(basic_postream<charT, Traits>
 	//~psentry
 }
=20
+
+// Locales:
+template<typename charT, typename Traits>
+locale
+basic_postream<charT, Traits>::
+imbue(const locale& locb)
+{
+	MutexLock mlock(lock);
+	return ostream_type::imbue(locb);
+}
+
+template<typename charT, typename Traits>
+char=20
+basic_postream<charT, Traits>::
+narrow(char_type c, char dfault) const
+{
+	MutexLock mlock(lock);
+	return ostream_type::narrow(c, dfault);
+}
+
+template<typename charT, typename Traits>
+//char_type
+//char
+charT
+basic_postream<charT, Traits>::widen(char c) const
+{
+	MutexLock mlock(lock);
+	return ostream_type::widen(c);
+}
+
 // Specializations
 template<typename Traits>
 basic_postream<char, Traits>&
@@ -401,7 +410,7 @@ operator<<(basic_postream<char, Traits>&
 	typedef basic_postream<char, Traits> postream_type;
 	typename postream_type::psentry opfx(out);
      =20
-	std::operator<<(out, c);     =20
+	std::operator<<(out, c);
=20
 	return out;
 	//~psentry

--=-QYI/PhWuNJ94Mw99Vg19--




From danielb@obfuscation.dyndns.org Mon Oct 07 01:52:53 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yQp2-00047n-00
	for bug-commoncpp@gnu.org; Mon, 07 Oct 2002 01:52:52 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yQou-0003pI-00
	for bug-commoncpp@gnu.org; Mon, 07 Oct 2002 01:52:49 -0400
Received: from mke-24-167-202-50.wi.rr.com ([24.167.202.50] helo=frell.dyndns.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yQor-0003oP-00
	for bug-commoncpp@gnu.org; Mon, 07 Oct 2002 01:52:42 -0400
Received: from obfuscation.dyndns.org ([192.168.1.2] ident=mail)
	by frell.dyndns.org with esmtp (Exim 3.36 #1 (Debian))
	id 17yQop-0007wB-00
	for <bug-commoncpp@gnu.org>; Mon, 07 Oct 2002 00:52:39 -0500
Received: from danielb by obfuscation.dyndns.org with local (Exim 3.36 #1 (Debian))
	id 17yQon-0003fn-00
	for <bug-commoncpp@gnu.org>; Mon, 07 Oct 2002 00:52:37 -0500
Date: Mon, 7 Oct 2002 00:52:37 -0500
From: Daniel E Baumann <baumannd@msoe.edu>
To: bug-commoncpp@gnu.org
Subject: Re: Piostreams Update
Message-ID: <20021007055237.GA14120@obfuscation.dyndns.org>
References: <1033968280.14005.6.camel@obfuscation>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="DocE+STaALJfprDB"
Content-Disposition: inline
In-Reply-To: <1033968280.14005.6.camel@obfuscation>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

--DocE+STaALJfprDB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Er, here's a better patch without all the crap at the top.

Dan

On Mon, 2002-10-07 at 00:24, Daniel E Baumann wrote:
> Here's a small update to piostreams. All it really adds is some more
> thread-safe methods to postream, i.e., for setting the state,
> formatting, accessing the stream buffer, etc. Expect more to following
> in the coming days like input streams :-) and perhaps the ability to
> print identifying thread info with an even more comprehensive test
> program (I really need to hit all methods of the stream classes).
> 
> Happy Hacking,
> 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/pio
> ? doc/commoncpp2.info
> ? doc/commoncpp2.info-1
> ? doc/commoncpp2.info-2
> ? doc/commoncpp2.info-3
> ? include/stamp-h1
> ? include/cc++/pfstream
> ? ssl/Makefile
> ? ssl/Makefile.in
> ? win32/CCXX2.rc
> Index: include/cc++/postream
> ===================================================================
> RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/postream,v
> retrieving revision 1.1
> diff -u -3 -p -r1.1 postream
> --- include/cc++/postream	21 Sep 2002 18:26:57 -0000	1.1
> +++ include/cc++/postream	7 Oct 2002 05:17:23 -0000
> @@ -71,14 +71,15 @@ public:
>  	typedef Traits                    		traits_type;
>      
>  	// Non-standard Types:
> -	typedef basic_streambuf<charT, Traits> 	  streambuf_type;
> -	//typedef basic_pstreambuf<charT, Traits> 	  pstreambuf_type;
> -	typedef basic_ios<charT, Traits>		  ios_type;
> -	typedef basic_ostream<charT, Traits>              ostream_type;
> -	typedef basic_postream<charT, Traits>	          postream_type;
> -	typedef ostreambuf_iterator<charT, Traits>        ostreambuf_iter;
> -	typedef num_put<charT, ostreambuf_iter>           numput_type;
> -	typedef ctype<charT>                              ctype_type;
> +	typedef basic_streambuf<charT, Traits> 	        streambuf_type;
> +	typedef basic_ios<charT, Traits>		ios_type;
> +	typedef basic_ostream<charT, Traits>            ostream_type;
> +	typedef basic_postream<charT, Traits>	        postream_type;
> +	typedef ostreambuf_iterator<charT, Traits>      ostreambuf_iter;
> +	typedef num_put<charT, ostreambuf_iter>         numput_type;
> +	typedef ctype<charT>                            ctype_type;
> +	
> +	typedef typename basic_postream<charT, Traits>::iostate  iostate_type;
>  
>  	// Constructor/destructor:
>  	explicit 
> @@ -98,22 +99,19 @@ public:
>  	postream_type&
>  	operator<<(postream_type& (*pf)(postream_type&));
>  
> -	//postream_type&
> -	//operator<<(ostream_type& (*pf)(ostream_type&));
> -
>  	postream_type&
>  	operator<<(ios_type& (*pf)(ios_type&));
> -      
> +
>  	postream_type&
>  	operator<<(ios_base& (*pf)(ios_base&));
>  
>  	// Arithmetic Inserters
>  	postream_type& 
>  	operator<<(long n);
> -      
> +
>  	postream_type& 
>  	operator<<(unsigned long n);
> - 
> +
>  	postream_type& 
>  	operator<<(bool n);
>  
> @@ -187,6 +185,7 @@ public:
>  
>  	postream_type& 
>  	seekp(pos_type);
> +
>  	postream_type& 
>  	seekp(off_type, ios_base::seekdir);
>  
> @@ -197,96 +196,212 @@ public:
>  	flags() const
>  	{
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::flags();
> +		return ostream_type::flags();
>  	}
>  
>  	inline ios_base::fmtflags 
>  	flags(ios_base::fmtflags fmtfl)
>  	{ 
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::flags(fmtfl);
> +		return ostream_type::flags(fmtfl);
>  	}
>  
>  	inline ios_base::fmtflags 
>  	setf(ios_base::fmtflags fmtfl)
>  	{ 
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::setf(fmtfl);
> +		return ostream_type::setf(fmtfl);
>  	}
>  
>  	inline ios_base::fmtflags 
>  	setf(ios_base::fmtflags fmtfl, ios_base::fmtflags mask)
>  	{
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::setf(fmtfl, mask);
> +		return ostream_type::setf(fmtfl, mask);
>  	}
>  
>  	inline void 
>  	unsetf(ios_base::fmtflags mask) 
>  	{ 
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::unsetf(mask);
> +		ostream_type::unsetf(mask);
>  	}
>  
>  	inline streamsize 
>  	precision() const 
>  	{
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::precision();
> +		return ostream_type::precision();
>  	}
>  
>  	inline streamsize 
>  	precision(streamsize prec)
>  	{ 
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::precision(prec);
> +		return ostream_type::precision(prec);
>  	}
>  
>  	inline streamsize 
>  	width() const 
>  	{
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::width();
> +		return ostream_type::width();
>  	}
>  
>  	inline streamsize 
>  	width(streamsize wide)
>  	{ 
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::width(wide);
> +		return ostream_type::width(wide);
>  	}
>  
> -	static bool 
> -	sync_with_stdio(bool sync = true);
> -
> -	// Locales:
> -	locale 
> -	imbue(const locale& loc);
> +	//static bool 
> +	//sync_with_stdio(bool sync = true);
>  
>  	inline locale 
>  	getloc() const 
>  	{
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::getloc();
> +		return ostream_type::getloc();
>  	}
>  
>  	// Storage:
> -	static int 
> -	xalloc() throw();
> +	//static int 
> +	//xalloc() throw();
>  
>  	inline long& 
>  	iword(int ix)
>  	{
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::iword(ix);
> +		return ostream_type::iword(ix);
>  	}
>  
>  	inline void*& 
>  	pword(int ix)
>  	{
>  		MutexLock mlock(lock);
> -		basic_ostream<charT, Traits>::pword(ix);
> +		return ostream_type::pword(ix);
> +	}
> +
> +	// std::basic_ios methods
> +
> +	//operator void*() const 
> +	//{ return this->fail() ? 0 : const_cast<basic_ios*>(this); }
> +
> +	//bool 
> +	//operator!() const 
> +	//{ return this->fail(); }
> +
> +	iostate_type 
> +	rdstate() const 
> +	{ 
> +		MutexLock mlock(lock);
> +		return ostream_type::rdstate();
> +	}
> +
> +	void 
> +	clear(iostate_type state = goodbit);
> +
> +	void 
> +	setstate(iostate_type state) 
> +	{ 
> +		MutexLock mlock(lock);
> +		ostream_type::setstate(state);
> +	}
> +
> +	bool 
> +	good() const 
> +	{ 
> +		MutexLock mlock(lock);
> +		return ostream_type::good();
> +	}
> +
> +	bool 
> +	eof() const 
> +	{ 
> +		MutexLock mlock(lock);
> +		return ostream_type::eof();
> +	}
> +
> +	bool 
> +	fail() const 
> +	{
> +		MutexLock mlock(lock);
> +		return ostream_type::fail();
> +	}
> +
> +	bool 
> +	bad() const 
> +	{
> +		MutexLock mlock(lock);
> +		return ostream_type::bad();
>  	}
> +
> +	iostate_type 
> +	exceptions() const 
> +	{ 
> +		MutexLock mlock(lock);
> +		return ostream_type::exceptions();
> +	}
> +
> +	void 
> +	exceptions(iostate_type except) 
> +	{ 
> +		MutexLock mlock(lock);
> +		ostream_type::exceptions(except);
> +	}
> +
> +	// Members:
> +        basic_postream<charT, Traits>*
> +	tie() const      
> +	{
> +		MutexLock mlock(lock);
> +		return ostream_type::tie();
> +	}
> +
> +	basic_ostream<charT, Traits>*
> +	tie(basic_ostream<charT, Traits>* tiestr)
> +	{
> +		MutexLock mlock(lock);
> +		return ostream_type::tie(tiestr);
> +	}
> +
> +	basic_streambuf<charT, Traits>*
> +	rdbuf() const    
> +	{
> +		MutexLock mlock(lock);
> +		return ostream_type::rdbuf();
> +	}
> +
> +	basic_streambuf<charT, Traits>* 
> +	rdbuf(basic_streambuf<charT, Traits>* sb);
> +
> +	//std::basic_ios&
> +	//copyfmt(const basic_ios& rhs);
> +
> +	char_type 
> +	fill() const 
> +	{
> +		MutexLock mlock(lock);
> +		return ostream_type::fill();
> +	}
> +
> +	char_type 
> +	fill(char_type ch)
> +	{
> +		MutexLock mlock(lock);
> +		return ostream_type::fill(ch);
> +	}
> +
> +	// Locales:
> +	locale 
> +	imbue(const locale& locb);
> +
> +	char 
> +	narrow(char_type c, char dfault) const;
> +
> +	char_type 
> +	widen(char c) const;
>  
>  	Thread* currth;
>  	int pid;
> Index: include/cc++/postream.tcc
> ===================================================================
> RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/postream.tcc,v
> retrieving revision 1.1
> diff -u -3 -p -r1.1 postream.tcc
> --- include/cc++/postream.tcc	21 Sep 2002 18:26:57 -0000	1.1
> +++ include/cc++/postream.tcc	7 Oct 2002 05:17:23 -0000
> @@ -144,38 +144,25 @@ operator<<(ios_base& (*pf)(ios_base&))
>  
>  template<typename charT, typename Traits>
>  basic_postream<charT, Traits>& 
> -basic_postream<charT, Traits>::operator<<(streambuf_type* sbin)
> +basic_postream<charT, Traits>::operator<<(long n)
>  {
>  	// 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<<(sbin);
> -	
> -	return *this;
> -}
> -
> -template<typename charT, typename Traits>
> -basic_postream<charT, Traits>& 
> -basic_postream<charT, Traits>::operator<<(bool n)
> -{
> -	// 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<<(n);
> -      
> +
>  	return *this;
>  }
>  
>  template<typename charT, typename Traits>
>  basic_postream<charT, Traits>& 
> -basic_postream<charT, Traits>::operator<<(long n)
> +basic_postream<charT, Traits>::operator<<(unsigned long n)
>  {
>  	// 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<<(n);
>  
>  	return *this;
> @@ -183,14 +170,14 @@ basic_postream<charT, Traits>::operator<
>  
>  template<typename charT, typename Traits>
>  basic_postream<charT, Traits>& 
> -basic_postream<charT, Traits>::operator<<(unsigned long n)
> +basic_postream<charT, Traits>::operator<<(bool n)
>  {
>  	// 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<<(n);
> -
> +      
>  	return *this;
>  }
>  
> @@ -223,44 +210,57 @@ basic_postream<charT, Traits>::operator<
>  
>  template<typename charT, typename Traits>
>  basic_postream<charT, Traits>& 
> -basic_postream<charT, Traits>::operator<<(double n)
> +basic_postream<charT, Traits>::operator<<(double f)
>  {
>  	// 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<<(n);
> +	ostream_type::operator<<(f);
>  	
>  	return *this;
>  }
>  
>  template<typename charT, typename Traits>
>  basic_postream<charT, Traits>& 
> -basic_postream<charT, Traits>::operator<<(long double n)
> +basic_postream<charT, Traits>::operator<<(long double f)
>  {
>  	// 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<<(n);
> +	ostream_type::operator<<(f);
>        
>  	return *this;
>  }
>  
>  template<typename charT, typename Traits>
>  basic_postream<charT, Traits>& 
> -basic_postream<charT, Traits>::operator<<(const void* n)
> +basic_postream<charT, Traits>::operator<<(const void* p)
>  {
>  	// 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<<(n);
> +	ostream_type::operator<<(p);
>        
>  	return *this;
>  }
>  
>  template<typename charT, typename Traits>
> +basic_postream<charT, Traits>& 
> +basic_postream<charT, Traits>::operator<<(streambuf_type* sbin)
> +{
> +	// 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<<(sbin);
> +	
> +	return *this;
> +}
> +
> +template<typename charT, typename Traits>
>  basic_postream<charT, Traits>&
>  basic_postream<charT, Traits>::put(char_type c)
>  { 
> @@ -303,7 +303,7 @@ template<typename charT, typename Traits
>  typename basic_postream<charT, Traits>::pos_type
>  basic_postream<charT, Traits>::tellp()
>  {
> -	// TODO: make this operation thread-safe?
> +	MutexLock mlock(lock);
>  	ostream_type::tellp();
>        
>  	return *this;
> @@ -313,10 +313,10 @@ template<typename charT, typename Traits
>  basic_postream<charT, Traits>&
>  basic_postream<charT, Traits>::seekp(pos_type pos)
>  {
> -	// TODO: make this operation thread-safe?
> +	MutexLock mlock(lock);
>  	ostream_type::seekp(pos);
>  	
> -	return this;
> +	return *this;
>  }
>  
>  template<typename charT, typename Traits>
> @@ -324,61 +324,40 @@ basic_postream<charT, Traits>&
>  basic_postream<charT, Traits>::
>  seekp(off_type off, ios_base::seekdir d)
>  {
> -	// TODO: make this operation thread-safe?
> +	MutexLock mlock(lock);
>  	ostream_type::seekp(d);
>  	
>  	return *this;
>  }
>  
> -template<typename charT, typename Traits>
> -void
> -basic_postream<charT, Traits>::lockStream()
> -{
> -	if(!owned)
> -	{
> -		currth = ost::getThread();
> -		owned = true;
> -		pid = getpid();
> -		tid = currth->getThreadID();
> -		if(!header)
> -		{
> -			outputHeader();
> -			header = true;
> -		}
> -	}
> -	lock.enterMutex();
> -	lockcnt++;
> -}
>  
> -template<typename charT, typename Traits>
> -void
> -basic_postream<charT, Traits>::unlockStream()
> -{
> -	mtx.enterMutex();
> -	if(owned)
> -	{
> -		currth = NULL;
> -		owned = false;
> -		pid = 0;
> -		tid = 0;
> -		header = false;
> -	}
> -	while(lockcnt != 0)
> -	{
> -		lock.leaveMutex();
> -		lockcnt--;
> -	}
> -	mtx.leaveMutex();
> -	printf("fully unlocked\n");
> -}
> +// TODO: May have to move this to pios.cpp?
> +//int
> +//postream::xalloc() throw()
> +//{
> +	//MutexLock mlock(lock);
> +//	return ostream_type::xalloc();
> +//}
>  
>  template<typename charT, typename Traits>
> -void
> -basic_postream<charT, Traits>::outputHeader()
> +basic_streambuf<charT, Traits>*
> +basic_postream<charT, Traits>::
> +rdbuf(basic_streambuf<charT, Traits>* sb)
>  {
> -	*this << "PID: " << pid << ", TID: " << tid << "> ";
> +	MutexLock mlock(lock);
> +	return ostream_type::rdbuf();
>  }
>  
> +//template<typename charT, typename Traits>
> +//basic_ios&
> +//basic_postream<charT, Traits>::
> +//copyfmt(const basic_ios& rhs)
> +//{
> +//	MutexLock mlock(lock);
> +//	return ostream_type::copyfmt(rhs);
> +//}
> +							   
> +
>  // Character inserters.
>  template<typename charT, typename Traits>
>  basic_postream<charT, Traits>&
> @@ -393,6 +372,36 @@ operator<<(basic_postream<charT, Traits>
>  	//~psentry
>  }
>  
> +
> +// Locales:
> +template<typename charT, typename Traits>
> +locale
> +basic_postream<charT, Traits>::
> +imbue(const locale& locb)
> +{
> +	MutexLock mlock(lock);
> +	return ostream_type::imbue(locb);
> +}
> +
> +template<typename charT, typename Traits>
> +char 
> +basic_postream<charT, Traits>::
> +narrow(char_type c, char dfault) const
> +{
> +	MutexLock mlock(lock);
> +	return ostream_type::narrow(c, dfault);
> +}
> +
> +template<typename charT, typename Traits>
> +//char_type
> +//char
> +charT
> +basic_postream<charT, Traits>::widen(char c) const
> +{
> +	MutexLock mlock(lock);
> +	return ostream_type::widen(c);
> +}
> +
>  // Specializations
>  template<typename Traits>
>  basic_postream<char, Traits>&
> @@ -401,7 +410,7 @@ operator<<(basic_postream<char, Traits>&
>  	typedef basic_postream<char, Traits> postream_type;
>  	typename postream_type::psentry opfx(out);
>        
> -	std::operator<<(out, c);      
> +	std::operator<<(out, c);
>  
>  	return out;
>  	//~psentry
-- 
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

--DocE+STaALJfprDB
Content-Type: text/x-patch; name="piostreams.diff";
	charset="ANSI_X3.4-1968"
Content-Disposition: attachment; filename="piostreams.diff"
Content-Transfer-Encoding: quoted-printable

Index: include/cc++/postream
=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++/postream,v
retrieving revision 1.1
diff -u -3 -p -r1.1 postream
--- include/cc++/postream	21 Sep 2002 18:26:57 -0000	1.1
+++ include/cc++/postream	7 Oct 2002 05:17:23 -0000
@@ -71,14 +71,15 @@ public:
 	typedef Traits                    		traits_type;
    =20
 	// Non-standard Types:
-	typedef basic_streambuf<charT, Traits> 	  streambuf_type;
-	//typedef basic_pstreambuf<charT, Traits> 	  pstreambuf_type;
-	typedef basic_ios<charT, Traits>		  ios_type;
-	typedef basic_ostream<charT, Traits>              ostream_type;
-	typedef basic_postream<charT, Traits>	          postream_type;
-	typedef ostreambuf_iterator<charT, Traits>        ostreambuf_iter;
-	typedef num_put<charT, ostreambuf_iter>           numput_type;
-	typedef ctype<charT>                              ctype_type;
+	typedef basic_streambuf<charT, Traits> 	        streambuf_type;
+	typedef basic_ios<charT, Traits>		ios_type;
+	typedef basic_ostream<charT, Traits>            ostream_type;
+	typedef basic_postream<charT, Traits>	        postream_type;
+	typedef ostreambuf_iterator<charT, Traits>      ostreambuf_iter;
+	typedef num_put<charT, ostreambuf_iter>         numput_type;
+	typedef ctype<charT>                            ctype_type;
+=09
+	typedef typename basic_postream<charT, Traits>::iostate  iostate_type;
=20
 	// Constructor/destructor:
 	explicit=20
@@ -98,22 +99,19 @@ public:
 	postream_type&
 	operator<<(postream_type& (*pf)(postream_type&));
=20
-	//postream_type&
-	//operator<<(ostream_type& (*pf)(ostream_type&));
-
 	postream_type&
 	operator<<(ios_type& (*pf)(ios_type&));
-     =20
+
 	postream_type&
 	operator<<(ios_base& (*pf)(ios_base&));
=20
 	// Arithmetic Inserters
 	postream_type&=20
 	operator<<(long n);
-     =20
+
 	postream_type&=20
 	operator<<(unsigned long n);
-=20
+
 	postream_type&=20
 	operator<<(bool n);
=20
@@ -187,6 +185,7 @@ public:
=20
 	postream_type&=20
 	seekp(pos_type);
+
 	postream_type&=20
 	seekp(off_type, ios_base::seekdir);
=20
@@ -197,96 +196,212 @@ public:
 	flags() const
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::flags();
+		return ostream_type::flags();
 	}
=20
 	inline ios_base::fmtflags=20
 	flags(ios_base::fmtflags fmtfl)
 	{=20
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::flags(fmtfl);
+		return ostream_type::flags(fmtfl);
 	}
=20
 	inline ios_base::fmtflags=20
 	setf(ios_base::fmtflags fmtfl)
 	{=20
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::setf(fmtfl);
+		return ostream_type::setf(fmtfl);
 	}
=20
 	inline ios_base::fmtflags=20
 	setf(ios_base::fmtflags fmtfl, ios_base::fmtflags mask)
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::setf(fmtfl, mask);
+		return ostream_type::setf(fmtfl, mask);
 	}
=20
 	inline void=20
 	unsetf(ios_base::fmtflags mask)=20
 	{=20
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::unsetf(mask);
+		ostream_type::unsetf(mask);
 	}
=20
 	inline streamsize=20
 	precision() const=20
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::precision();
+		return ostream_type::precision();
 	}
=20
 	inline streamsize=20
 	precision(streamsize prec)
 	{=20
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::precision(prec);
+		return ostream_type::precision(prec);
 	}
=20
 	inline streamsize=20
 	width() const=20
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::width();
+		return ostream_type::width();
 	}
=20
 	inline streamsize=20
 	width(streamsize wide)
 	{=20
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::width(wide);
+		return ostream_type::width(wide);
 	}
=20
-	static bool=20
-	sync_with_stdio(bool sync =3D true);
-
-	// Locales:
-	locale=20
-	imbue(const locale& loc);
+	//static bool=20
+	//sync_with_stdio(bool sync =3D true);
=20
 	inline locale=20
 	getloc() const=20
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::getloc();
+		return ostream_type::getloc();
 	}
=20
 	// Storage:
-	static int=20
-	xalloc() throw();
+	//static int=20
+	//xalloc() throw();
=20
 	inline long&=20
 	iword(int ix)
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::iword(ix);
+		return ostream_type::iword(ix);
 	}
=20
 	inline void*&=20
 	pword(int ix)
 	{
 		MutexLock mlock(lock);
-		basic_ostream<charT, Traits>::pword(ix);
+		return ostream_type::pword(ix);
+	}
+
+	// std::basic_ios methods
+
+	//operator void*() const=20
+	//{ return this->fail() ? 0 : const_cast<basic_ios*>(this); }
+
+	//bool=20
+	//operator!() const=20
+	//{ return this->fail(); }
+
+	iostate_type=20
+	rdstate() const=20
+	{=20
+		MutexLock mlock(lock);
+		return ostream_type::rdstate();
+	}
+
+	void=20
+	clear(iostate_type state =3D goodbit);
+
+	void=20
+	setstate(iostate_type state)=20
+	{=20
+		MutexLock mlock(lock);
+		ostream_type::setstate(state);
+	}
+
+	bool=20
+	good() const=20
+	{=20
+		MutexLock mlock(lock);
+		return ostream_type::good();
+	}
+
+	bool=20
+	eof() const=20
+	{=20
+		MutexLock mlock(lock);
+		return ostream_type::eof();
+	}
+
+	bool=20
+	fail() const=20
+	{
+		MutexLock mlock(lock);
+		return ostream_type::fail();
+	}
+
+	bool=20
+	bad() const=20
+	{
+		MutexLock mlock(lock);
+		return ostream_type::bad();
 	}
+
+	iostate_type=20
+	exceptions() const=20
+	{=20
+		MutexLock mlock(lock);
+		return ostream_type::exceptions();
+	}
+
+	void=20
+	exceptions(iostate_type except)=20
+	{=20
+		MutexLock mlock(lock);
+		ostream_type::exceptions(except);
+	}
+
+	// Members:
+        basic_postream<charT, Traits>*
+	tie() const     =20
+	{
+		MutexLock mlock(lock);
+		return ostream_type::tie();
+	}
+
+	basic_ostream<charT, Traits>*
+	tie(basic_ostream<charT, Traits>* tiestr)
+	{
+		MutexLock mlock(lock);
+		return ostream_type::tie(tiestr);
+	}
+
+	basic_streambuf<charT, Traits>*
+	rdbuf() const   =20
+	{
+		MutexLock mlock(lock);
+		return ostream_type::rdbuf();
+	}
+
+	basic_streambuf<charT, Traits>*=20
+	rdbuf(basic_streambuf<charT, Traits>* sb);
+
+	//std::basic_ios&
+	//copyfmt(const basic_ios& rhs);
+
+	char_type=20
+	fill() const=20
+	{
+		MutexLock mlock(lock);
+		return ostream_type::fill();
+	}
+
+	char_type=20
+	fill(char_type ch)
+	{
+		MutexLock mlock(lock);
+		return ostream_type::fill(ch);
+	}
+
+	// Locales:
+	locale=20
+	imbue(const locale& locb);
+
+	char=20
+	narrow(char_type c, char dfault) const;
+
+	char_type=20
+	widen(char c) const;
=20
 	Thread* currth;
 	int pid;
Index: include/cc++/postream.tcc
=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++/postream.tcc,v
retrieving revision 1.1
diff -u -3 -p -r1.1 postream.tcc
--- include/cc++/postream.tcc	21 Sep 2002 18:26:57 -0000	1.1
+++ include/cc++/postream.tcc	7 Oct 2002 05:17:23 -0000
@@ -144,38 +144,25 @@ operator<<(ios_base& (*pf)(ios_base&))
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(streambuf_type* sbin)
+basic_postream<charT, Traits>::operator<<(long n)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 =09
-	ostream_type::operator<<(sbin);
-=09
-	return *this;
-}
-
-template<typename charT, typename Traits>
-basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(bool n)
-{
-	// 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<<(n);
-     =20
+
 	return *this;
 }
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(long n)
+basic_postream<charT, Traits>::operator<<(unsigned long n)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
-=09
+
 	ostream_type::operator<<(n);
=20
 	return *this;
@@ -183,14 +170,14 @@ basic_postream<charT, Traits>::operator<
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(unsigned long n)
+basic_postream<charT, Traits>::operator<<(bool n)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
=20
 	ostream_type::operator<<(n);
-
+     =20
 	return *this;
 }
=20
@@ -223,44 +210,57 @@ basic_postream<charT, Traits>::operator<
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(double n)
+basic_postream<charT, Traits>::operator<<(double f)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 =09
-	ostream_type::operator<<(n);
+	ostream_type::operator<<(f);
 =09
 	return *this;
 }
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(long double n)
+basic_postream<charT, Traits>::operator<<(long double f)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
 =09
-	ostream_type::operator<<(n);
+	ostream_type::operator<<(f);
      =20
 	return *this;
 }
=20
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&=20
-basic_postream<charT, Traits>::operator<<(const void* n)
+basic_postream<charT, Traits>::operator<<(const void* p)
 {
 	// Create a psentry object (may set error bits or throw failure)
 	typedef basic_postream<charT, Traits> postream_type;
 	typename postream_type::psentry opfx(*this);
=20
-	ostream_type::operator<<(n);
+	ostream_type::operator<<(p);
      =20
 	return *this;
 }
=20
 template<typename charT, typename Traits>
+basic_postream<charT, Traits>&=20
+basic_postream<charT, Traits>::operator<<(streambuf_type* sbin)
+{
+	// Create a psentry object (may set error bits or throw failure)
+	typedef basic_postream<charT, Traits> postream_type;
+	typename postream_type::psentry opfx(*this);
+=09
+	ostream_type::operator<<(sbin);
+=09
+	return *this;
+}
+
+template<typename charT, typename Traits>
 basic_postream<charT, Traits>&
 basic_postream<charT, Traits>::put(char_type c)
 {=20
@@ -303,7 +303,7 @@ template<typename charT, typename Traits
 typename basic_postream<charT, Traits>::pos_type
 basic_postream<charT, Traits>::tellp()
 {
-	// TODO: make this operation thread-safe?
+	MutexLock mlock(lock);
 	ostream_type::tellp();
      =20
 	return *this;
@@ -313,10 +313,10 @@ template<typename charT, typename Traits
 basic_postream<charT, Traits>&
 basic_postream<charT, Traits>::seekp(pos_type pos)
 {
-	// TODO: make this operation thread-safe?
+	MutexLock mlock(lock);
 	ostream_type::seekp(pos);
 =09
-	return this;
+	return *this;
 }
=20
 template<typename charT, typename Traits>
@@ -324,61 +324,40 @@ basic_postream<charT, Traits>&
 basic_postream<charT, Traits>::
 seekp(off_type off, ios_base::seekdir d)
 {
-	// TODO: make this operation thread-safe?
+	MutexLock mlock(lock);
 	ostream_type::seekp(d);
 =09
 	return *this;
 }
=20
-template<typename charT, typename Traits>
-void
-basic_postream<charT, Traits>::lockStream()
-{
-	if(!owned)
-	{
-		currth =3D ost::getThread();
-		owned =3D true;
-		pid =3D getpid();
-		tid =3D currth->getThreadID();
-		if(!header)
-		{
-			outputHeader();
-			header =3D true;
-		}
-	}
-	lock.enterMutex();
-	lockcnt++;
-}
=20
-template<typename charT, typename Traits>
-void
-basic_postream<charT, Traits>::unlockStream()
-{
-	mtx.enterMutex();
-	if(owned)
-	{
-		currth =3D NULL;
-		owned =3D false;
-		pid =3D 0;
-		tid =3D 0;
-		header =3D false;
-	}
-	while(lockcnt !=3D 0)
-	{
-		lock.leaveMutex();
-		lockcnt--;
-	}
-	mtx.leaveMutex();
-	printf("fully unlocked\n");
-}
+// TODO: May have to move this to pios.cpp?
+//int
+//postream::xalloc() throw()
+//{
+	//MutexLock mlock(lock);
+//	return ostream_type::xalloc();
+//}
=20
 template<typename charT, typename Traits>
-void
-basic_postream<charT, Traits>::outputHeader()
+basic_streambuf<charT, Traits>*
+basic_postream<charT, Traits>::
+rdbuf(basic_streambuf<charT, Traits>* sb)
 {
-	*this << "PID: " << pid << ", TID: " << tid << "> ";
+	MutexLock mlock(lock);
+	return ostream_type::rdbuf();
 }
=20
+//template<typename charT, typename Traits>
+//basic_ios&
+//basic_postream<charT, Traits>::
+//copyfmt(const basic_ios& rhs)
+//{
+//	MutexLock mlock(lock);
+//	return ostream_type::copyfmt(rhs);
+//}
+							  =20
+
 // Character inserters.
 template<typename charT, typename Traits>
 basic_postream<charT, Traits>&
@@ -393,6 +372,36 @@ operator<<(basic_postream<charT, Traits>
 	//~psentry
 }
=20
+
+// Locales:
+template<typename charT, typename Traits>
+locale
+basic_postream<charT, Traits>::
+imbue(const locale& locb)
+{
+	MutexLock mlock(lock);
+	return ostream_type::imbue(locb);
+}
+
+template<typename charT, typename Traits>
+char=20
+basic_postream<charT, Traits>::
+narrow(char_type c, char dfault) const
+{
+	MutexLock mlock(lock);
+	return ostream_type::narrow(c, dfault);
+}
+
+template<typename charT, typename Traits>
+//char_type
+//char
+charT
+basic_postream<charT, Traits>::widen(char c) const
+{
+	MutexLock mlock(lock);
+	return ostream_type::widen(c);
+}
+
 // Specializations
 template<typename Traits>
 basic_postream<char, Traits>&
@@ -401,7 +410,7 @@ operator<<(basic_postream<char, Traits>&
 	typedef basic_postream<char, Traits> postream_type;
 	typename postream_type::psentry opfx(out);
      =20
-	std::operator<<(out, c);     =20
+	std::operator<<(out, c);
=20
 	return out;
 	//~psentry

--DocE+STaALJfprDB--



From fedemp@wanadoo.es Tue Oct 08 20:42:32 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17z4uV-00024U-00
	for bug-commoncpp@gnu.org; Tue, 08 Oct 2002 20:41:11 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17z4uL-0001Ye-00
	for bug-commoncpp@gnu.org; Tue, 08 Oct 2002 20:41:05 -0400
Received: from [62.37.236.138] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17z4uK-0001TQ-00
	for bug-commoncpp@gnu.org; Tue, 08 Oct 2002 20:41:01 -0400
Received: from risitas ([80.103.118.242])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g990eNt07117
	for <bug-commoncpp@gnu.org>; Wed, 9 Oct 2002 02:40:23 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17z4xM-0000Bn-00
	for <bug-commoncpp@gnu.org>; Wed, 09 Oct 2002 02:44:08 +0200
Date: Wed, 9 Oct 2002 02:44:08 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: Piostreams Update
Message-ID: <20021009004408.GA645@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <1033968280.14005.6.camel@obfuscation> <20021007055237.GA14120@obfuscation.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021007055237.GA14120@obfuscation.dyndns.org>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	OK, it has been integrated. Expecting more patches...

On Mon, Oct 07, 2002 at 12:52:37AM -0500, Daniel E Baumann wrote:
> Er, here's a better patch without all the crap at the top.
> 
> Dan
> 
> On Mon, 2002-10-07 at 00:24, Daniel E Baumann wrote:
> > Here's a small update to piostreams. All it really adds is some more
> > thread-safe methods to postream, i.e., for setting the state,
> > formatting, accessing the stream buffer, etc. Expect more to following
> > in the coming days like input streams :-) and perhaps the ability to
> > print identifying thread info with an even more comprehensive test
> > program (I really need to hit all methods of the stream classes).
> > 
> > Happy Hacking,
> > 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 ariston@cs.und.edu Tue Oct 08 23:36:57 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17z7eb-0003nv-00
	for bug-commoncpp@gnu.org; Tue, 08 Oct 2002 23:36:57 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17z7eZ-0003ng-00
	for bug-commoncpp@gnu.org; Tue, 08 Oct 2002 23:36:56 -0400
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17z7eY-0003jj-00
	for bug-commoncpp@gnu.org; Tue, 08 Oct 2002 23:36:54 -0400
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id g993b0lh005634
	for <bug-commoncpp@gnu.org>; Tue, 8 Oct 2002 22:37:00 -0500
Date: Tue, 8 Oct 2002 22:37:50 -0500 (CDT)
From: Ari Johnson <ariston@cs.und.edu>
To: <bug-commoncpp@gnu.org>
Subject: Incremental XML Parsing
Message-ID: <Pine.GSO.4.33.0210082159280.23418-100000@agassiz.cs.und.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Has anyone written code to allow incremental XML parsing?  There are two
ways that this could be done, and actually I feel that both should be
available.  They both require using libxml's xmlCreatePushParserCtxt() and
xmlParseChunk() instead of xmlCreateIOParserCtxt and xmlParseDocument().
(I don't know whether my first method absolutely requires this - but I'm
assuming that all the other libxml SAX routines want the whole document at
once.)

Method 1:  ost::XMLStream::parse() does a loop until it encounters and
error or the end of the document, and each time through that loop, it does
a read() (as in its virtual member) and sends the read data to
xmlParseChunk().

Method 2:  ost::XMLStream::parse() takes a string containing a portion of
the XML data stream (hence the name, XMLStream, right?) and sends it to
xmlParseChunk().

The reason that this is important to me is that I'm writing a Jabber
client library (as part of a much larger project, but you have to start
with the foundation...), and need to read in and process one level-1 child
of the root element at a time.  I have my own XML stream library working
to do that and send each level-1 child to a callback function, but I've
found that only when I reach the end of a document (which doesn't happen
until the very end of your Jabber connection) do the various callbacks
(aside from beginDocument) get called.

I would write this feature myself, but I'd rather see things done the
CommonC++-prefered way, so that when I upgrade to a future version of the
library I don't have to deal with custom patches.
 -- Ari Johnson





From ariston@cs.und.edu Wed Oct 09 13:03:29 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17zKF7-0007n8-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 13:03:29 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17zKF5-0007mp-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 13:03:28 -0400
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17zKF5-0007mj-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 13:03:27 -0400
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id g99H3Zlh009112
	for <bug-commoncpp@gnu.org>; Wed, 9 Oct 2002 12:03:35 -0500
Date: Wed, 9 Oct 2002 12:04:23 -0500 (CDT)
From: Ari Johnson <ariston@cs.und.edu>
To: <bug-commoncpp@gnu.org>
Subject: Re: Incremental XML Parsing
In-Reply-To: <Pine.GSO.4.33.0210082159280.23418-100000@agassiz.cs.und.edu>
Message-ID: <Pine.GSO.4.33.0210091203320.27716-200000@agassiz.cs.und.edu>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-1034183063=:27716"
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

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

---559023410-851401618-1034183063=:27716
Content-Type: TEXT/PLAIN; charset=US-ASCII


I did go ahead and implement this; took about 3 minutes total.  My patch
to xml.cpp is attached to this message.
 -- Ari Johnson



---559023410-851401618-1034183063=:27716
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="commoncpp2.push-parser.patch"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.GSO.4.33.0210091204230.27716@agassiz.cs.und.edu>
Content-Description: 
Content-Disposition: attachment; filename="commoncpp2.push-parser.patch"

ZGlmZiAtcjEuOSB4bWwuY3BwDQoxMzhhMTM5LDE0MA0KPiAJY2hhciBidWZm
ZXJbMTAyNF07DQo+IAlpbnQgcmVzOw0KMTUyLDE1NWMxNTQsMTU1DQo8IAl4
bWwgPSB4bWxDcmVhdGVJT1BhcnNlckN0eHQoJnNheCwgdGhpcywNCjwgCQko
eG1sSW5wdXRSZWFkQ2FsbGJhY2spJnhtbFJlYWRDYWxsYmFjaywNCjwgCQko
eG1sSW5wdXRDbG9zZUNhbGxiYWNrKSZ4bWxDbG9zZUNhbGxiYWNrLA0KPCAJ
CXRoaXMsICh4bWxDaGFyRW5jb2RpbmcpMCk7DQotLS0NCj4gCXhtbCA9IHht
bENyZWF0ZVB1c2hQYXJzZXJDdHh0KCZzYXgsIHRoaXMsDQo+IAkJTlVMTCwg
MCwgTlVMTCk7DQoxNjBjMTYwLDE2Mw0KPCAJeG1sUGFyc2VEb2N1bWVudCh4
bWwpOw0KLS0tDQo+IAl3aGlsZSgocmVzID0gcmVhZCgodW5zaWduZWQgY2hh
ciAqKSBidWZmZXIsIDEwMjQpKSkNCj4gCQl4bWxQYXJzZUNodW5rKHhtbCwg
YnVmZmVyLCByZXMsIDApOw0KPiAJeG1sUGFyc2VDaHVuayh4bWwsIGJ1ZmZl
ciwgMCwgMSk7DQo+IA0K
---559023410-851401618-1034183063=:27716--



From dyfet@ostel.com Wed Oct 09 13:19:07 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17zKUF-0007WV-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 13:19:07 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17zKUC-0007Sf-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 13:19:05 -0400
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)
	id 17zKUB-0007Rk-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 13:19:03 -0400
Received: from home.sys (IDENT:FvG1DJJsPtQCEBGPRAmUtZReurnRftBY@home.sys [172.16.1.254])
	by home.sys (8.11.6/8.11.6) with ESMTP id g99HdEr07572;
	Wed, 9 Oct 2002 13:39:14 -0400
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Ari Johnson <ariston@cs.und.edu>, <bug-commoncpp@gnu.org>
Subject: Re: Incremental XML Parsing
Date: Wed, 9 Oct 2002 13:39:14 -0400
User-Agent: KMail/1.4.3
References: <Pine.GSO.4.33.0210091203320.27716-200000@agassiz.cs.und.edu>
In-Reply-To: <Pine.GSO.4.33.0210091203320.27716-200000@agassiz.cs.und.edu>
Cc: Federico Montesino Pouzols <fedemp@suidzer0.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200210091339.14383.dyfet@ostel.com>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

We may want to have this in the RELEASE1 tree as well...?  It seems harml=
ess=20
enough for existing code.

On Wednesday 09 October 2002 13:04, Ari Johnson wrote:
> I did go ahead and implement this; took about 3 minutes total.  My patc=
h
> to xml.cpp is attached to this message.
>  -- Ari Johnson




From fedemp@wanadoo.es Wed Oct 09 15:43:35 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17zMk3-00085T-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 15:43:35 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17zMk0-000851-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 15:43:34 -0400
Received: from [62.37.236.139] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17zMjy-00084f-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 15:43:31 -0400
Received: from risitas (62-36-191-242.dialup.uni2.es [62.36.191.242])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAOMbRt04073;
	Sun, 24 Nov 2002 23:37:28 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17zMme-0000p0-00; Wed, 09 Oct 2002 21:46:16 +0200
Date: Wed, 9 Oct 2002 21:46:05 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>, Ari Johnson <ariston@cs.und.edu>
Cc: bug-commoncpp@gnu.org
Subject: Re: Incremental XML Parsing
Message-ID: <20021009194605.GA2685@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: David Sugar <dyfet@ostel.com>,
	Ari Johnson <ariston@cs.und.edu>, bug-commoncpp@gnu.org
References: <Pine.GSO.4.33.0210091203320.27716-200000@agassiz.cs.und.edu> <200210091339.14383.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200210091339.14383.dyfet@ostel.com>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Yes, I think this patch should go on both the stable and
unstable branches. It adds a very interesting capability and should
not harm applications that do not need partial parsing.

	It is also interesting to discuss the following two points:

	* The patch from Ari implements the "Method 1" he described in
his first mail. Should we also add a special parse() -say
partialParse()- method that implements the "Method 2"? I suppose this
method would be almost equal to the normal parse(), except that it
would run just one iteration of the loop.

	* What do we do with the read() and close() virtual methods
now?  Should we remove them, or would it be valid to call read()
inside the loop and close() after the loop? I think this last option
makes sense but I am not too certain.

On Wed, Oct 09, 2002 at 01:39:14PM -0400, David Sugar wrote:
> We may want to have this in the RELEASE1 tree as well...?  It seems harmless 
> enough for existing code.
> 
> On Wednesday 09 October 2002 13:04, Ari Johnson wrote:
> > I did go ahead and implement this; took about 3 minutes total.  My patch
> > to xml.cpp is attached to this message.
> >  -- Ari Johnson
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Wed Oct 09 16:05:54 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17zN5e-0005Rs-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 16:05:54 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17zN5a-0005Oz-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 16:05:52 -0400
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)
	id 17zN5Z-0005Mn-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 16:05:49 -0400
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id g99KQLC08697;
	Wed, 9 Oct 2002 16:26:21 -0400
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 9 Oct 2002 16:26:20 -0400 (EDT)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: Ari Johnson <ariston@cs.und.edu>, <bug-commoncpp@gnu.org>
Subject: Re: Incremental XML Parsing
In-Reply-To: <20021009194605.GA2685@risitas>
Message-ID: <Pine.LNX.4.44.0210091623060.8668-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

The read and close virtuals ultimately have to be called, because those 
can be overriden and bind xml to streams or to other things such as 
passed xml memory buffers.  I think having a seperate parsePartial may 
also be useful, and we should pass the length of the buffer to request for 
that.  What if we broadcast XML content over multiple UDP 
packets, for example.

On Wed, 9 Oct 2002, Federico Montesino Pouzols wrote:

> 
> 	Yes, I think this patch should go on both the stable and
> unstable branches. It adds a very interesting capability and should
> not harm applications that do not need partial parsing.
> 
> 	It is also interesting to discuss the following two points:
> 
> 	* The patch from Ari implements the "Method 1" he described in
> his first mail. Should we also add a special parse() -say
> partialParse()- method that implements the "Method 2"? I suppose this
> method would be almost equal to the normal parse(), except that it
> would run just one iteration of the loop.
> 
> 	* What do we do with the read() and close() virtual methods
> now?  Should we remove them, or would it be valid to call read()
> inside the loop and close() after the loop? I think this last option
> makes sense but I am not too certain.
> 
> On Wed, Oct 09, 2002 at 01:39:14PM -0400, David Sugar wrote:
> > We may want to have this in the RELEASE1 tree as well...?  It seems harmless 
> > enough for existing code.
> > 
> > On Wednesday 09 October 2002 13:04, Ari Johnson wrote:
> > > I did go ahead and implement this; took about 3 minutes total.  My patch
> > > to xml.cpp is attached to this message.
> > >  -- Ari Johnson
> > 
> > 
> > 
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From ariston@cs.und.edu Wed Oct 09 22:12:12 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17zSo7-0002su-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 22:12:11 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17zSnr-0002LA-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 22:12:07 -0400
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17zSnr-0002L6-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 22:11:55 -0400
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id g9A2C2lh012349;
	Wed, 9 Oct 2002 21:12:02 -0500
Date: Wed, 9 Oct 2002 21:12:49 -0500 (CDT)
From: Ari Johnson <ariston@cs.und.edu>
To: David Sugar <dyfet@ostel.com>
cc: Federico Montesino Pouzols <fedemp@altern.org>, <bug-commoncpp@gnu.org>
Subject: Re: Incremental XML Parsing
In-Reply-To: <Pine.LNX.4.44.0210091623060.8668-100000@home.sys>
Message-ID: <Pine.GSO.4.33.0210092105470.4554-100000@agassiz.cs.und.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

I wouldn't recommend taking out the read or close virtuals at all.  Keep
everything as it is, but with the change that I made in my patch.  My
patch basically emulates a pull parser by using libxml2's push interface,
which is advantageous because it means that when the read virtual returns
a given number of bytes that contain so many complete xml elements, those
elements get parsed right away, rather than waiting for the whole file to
be read (or at least a full buffer of unknown size to be filled) before
libxml2 actually parses anything.  This means that people can call it
exactly as they always have, but that it simply adds the feature that I
needed.

If you wanted to add a push interface, I would recommend superclassing
XMLStream and doing the following in the superclass:
 - no the open/read/close virtuals
 - parse(const char * buffer, int len) sends the given buffer off to
   libxml2 (as per in the while loop in my patch; I'd recommend using
   a different name than parse() though, to avoid confusion)
 - end() or complete() or done() or youNameIt() tells libxml2 that the
   end of input has been reached; this will be called by the user, as
   per the end of my patch's while() loop

Then, XMLStream will be a subclass of the new class, and it will simply
implement its various virtuals, and parse() will now pass what it read()s
down to the parent class's parseWhatever(), and call end() at the end of
input.
 -- Ari Johnson

On Wed, 9 Oct 2002, David Sugar wrote:

>
> The read and close virtuals ultimately have to be called, because those
> can be overriden and bind xml to streams or to other things such as
> passed xml memory buffers.  I think having a seperate parsePartial may
> also be useful, and we should pass the length of the buffer to request for
> that.  What if we broadcast XML content over multiple UDP
> packets, for example.
>
> On Wed, 9 Oct 2002, Federico Montesino Pouzols wrote:
>
> >
> > 	Yes, I think this patch should go on both the stable and
> > unstable branches. It adds a very interesting capability and should
> > not harm applications that do not need partial parsing.
> >
> > 	It is also interesting to discuss the following two points:
> >
> > 	* The patch from Ari implements the "Method 1" he described in
> > his first mail. Should we also add a special parse() -say
> > partialParse()- method that implements the "Method 2"? I suppose this
> > method would be almost equal to the normal parse(), except that it
> > would run just one iteration of the loop.
> >
> > 	* What do we do with the read() and close() virtual methods
> > now?  Should we remove them, or would it be valid to call read()
> > inside the loop and close() after the loop? I think this last option
> > makes sense but I am not too certain.
> >
> > On Wed, Oct 09, 2002 at 01:39:14PM -0400, David Sugar wrote:
> > > We may want to have this in the RELEASE1 tree as well...?  It seems harmless
> > > enough for existing code.
> > >
> > > On Wednesday 09 October 2002 13:04, Ari Johnson wrote:
> > > > I did go ahead and implement this; took about 3 minutes total.  My patch
> > > > to xml.cpp is attached to this message.
> > > >  -- Ari Johnson
> > >
> > >
> > >
> > > _______________________________________________
> > > Bug-commoncpp mailing list
> > > Bug-commoncpp@gnu.org
> > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> >
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>




From dyfet@ostel.com Wed Oct 09 22:28:52 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17zT4G-00046K-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 22:28:52 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17zT4B-00043d-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 22:28:51 -0400
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)
	id 17zT4A-00041F-00
	for bug-commoncpp@gnu.org; Wed, 09 Oct 2002 22:28:46 -0400
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id g9A2nNd18032;
	Wed, 9 Oct 2002 22:49:23 -0400
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 9 Oct 2002 22:49:23 -0400 (EDT)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Ari Johnson <ariston@cs.und.edu>
cc: Federico Montesino Pouzols <fedemp@altern.org>, <bug-commoncpp@gnu.org>
Subject: Re: Incremental XML Parsing
In-Reply-To: <Pine.GSO.4.33.0210092105470.4554-100000@agassiz.cs.und.edu>
Message-ID: <Pine.LNX.4.44.0210092246220.15996-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

This also has some use in Bayonne's XML parser, since Bayonne can make a
web query to parse and XML script document.  Usually it had to also wait
until the entire fetch was completed which also is an indeterminate size
document, typically from a web site.  Maybe I can now do something a bit
more interactive...

On Wed, 9 Oct 2002, Ari Johnson wrote:

> 
> I wouldn't recommend taking out the read or close virtuals at all.  Keep
> everything as it is, but with the change that I made in my patch.  My
> patch basically emulates a pull parser by using libxml2's push interface,
> which is advantageous because it means that when the read virtual returns
> a given number of bytes that contain so many complete xml elements, those
> elements get parsed right away, rather than waiting for the whole file to
> be read (or at least a full buffer of unknown size to be filled) before
> libxml2 actually parses anything.  This means that people can call it
> exactly as they always have, but that it simply adds the feature that I
> needed.
> 
> If you wanted to add a push interface, I would recommend superclassing
> XMLStream and doing the following in the superclass:
>  - no the open/read/close virtuals
>  - parse(const char * buffer, int len) sends the given buffer off to
>    libxml2 (as per in the while loop in my patch; I'd recommend using
>    a different name than parse() though, to avoid confusion)
>  - end() or complete() or done() or youNameIt() tells libxml2 that the
>    end of input has been reached; this will be called by the user, as
>    per the end of my patch's while() loop
> 
> Then, XMLStream will be a subclass of the new class, and it will simply
> implement its various virtuals, and parse() will now pass what it read()s
> down to the parent class's parseWhatever(), and call end() at the end of
> input.
>  -- Ari Johnson
> 
> On Wed, 9 Oct 2002, David Sugar wrote:
> 
> >
> > The read and close virtuals ultimately have to be called, because those
> > can be overriden and bind xml to streams or to other things such as
> > passed xml memory buffers.  I think having a seperate parsePartial may
> > also be useful, and we should pass the length of the buffer to request for
> > that.  What if we broadcast XML content over multiple UDP
> > packets, for example.
> >
> > On Wed, 9 Oct 2002, Federico Montesino Pouzols wrote:
> >
> > >
> > > 	Yes, I think this patch should go on both the stable and
> > > unstable branches. It adds a very interesting capability and should
> > > not harm applications that do not need partial parsing.
> > >
> > > 	It is also interesting to discuss the following two points:
> > >
> > > 	* The patch from Ari implements the "Method 1" he described in
> > > his first mail. Should we also add a special parse() -say
> > > partialParse()- method that implements the "Method 2"? I suppose this
> > > method would be almost equal to the normal parse(), except that it
> > > would run just one iteration of the loop.
> > >
> > > 	* What do we do with the read() and close() virtual methods
> > > now?  Should we remove them, or would it be valid to call read()
> > > inside the loop and close() after the loop? I think this last option
> > > makes sense but I am not too certain.
> > >
> > > On Wed, Oct 09, 2002 at 01:39:14PM -0400, David Sugar wrote:
> > > > We may want to have this in the RELEASE1 tree as well...?  It seems harmless
> > > > enough for existing code.
> > > >
> > > > On Wednesday 09 October 2002 13:04, Ari Johnson wrote:
> > > > > I did go ahead and implement this; took about 3 minutes total.  My patch
> > > > > to xml.cpp is attached to this message.
> > > > >  -- Ari Johnson
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Bug-commoncpp mailing list
> > > > Bug-commoncpp@gnu.org
> > > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > >
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> >
> 
> 




From ariston@cs.und.edu Sun Oct 13 14:05:11 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 180n71-0002wQ-00
	for bug-commoncpp@gnu.org; Sun, 13 Oct 2002 14:05:11 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 180n6z-0002wD-00
	for bug-commoncpp@gnu.org; Sun, 13 Oct 2002 14:05:10 -0400
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 180n6z-0002ve-00
	for bug-commoncpp@gnu.org; Sun, 13 Oct 2002 14:05:09 -0400
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id g9DI5Qlh023666
	for <bug-commoncpp@gnu.org>; Sun, 13 Oct 2002 13:05:27 -0500
Date: Sun, 13 Oct 2002 13:06:02 -0500 (CDT)
From: Ari Johnson <ariston@cs.und.edu>
To: <bug-commoncpp@gnu.org>
Subject: GCC 3.x Compatibility
Message-ID: <Pine.GSO.4.33.0210131305010.22662-100000@agassiz.cs.und.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Has anyone successfully built CommonC++ using the gcc 3.x C++ compiler?  I
seem to be having a few hangup points.
 -- Ari Johnson





From fedemp@wanadoo.es Sun Oct 13 15:13:55 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 180oBW-0004vn-00
	for bug-commoncpp@gnu.org; Sun, 13 Oct 2002 15:13:54 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 180oBS-0004tz-00
	for bug-commoncpp@gnu.org; Sun, 13 Oct 2002 15:13:54 -0400
Received: from [62.37.236.138] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 180oBS-0004tV-00
	for bug-commoncpp@gnu.org; Sun, 13 Oct 2002 15:13:50 -0400
Received: from risitas (62-36-190-121.dialup.uni2.es [62.36.190.121])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g9DJCmt17415;
	Sun, 13 Oct 2002 21:12:49 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 180oDz-0000H4-00; Sun, 13 Oct 2002 21:16:27 +0200
Date: Sun, 13 Oct 2002 21:16:27 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ari Johnson <ariston@cs.und.edu>
Cc: bug-commoncpp@gnu.org
Subject: Re: GCC 3.x Compatibility
Message-ID: <20021013191627.GA613@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Ari Johnson <ariston@cs.und.edu>, bug-commoncpp@gnu.org
References: <Pine.GSO.4.33.0210131305010.22662-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.33.0210131305010.22662-100000@agassiz.cs.und.edu>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Yes, CC++ 2 should compile and work well with gcc 3.x. I have
successfully used some 3.0.x and 3.1.x; other people are also
successfully using gcc 3.2.x. What are the problems?

On Sun, Oct 13, 2002 at 01:06:02PM -0500, Ari Johnson wrote:
> 
> Has anyone successfully built CommonC++ using the gcc 3.x C++ compiler?  I
> seem to be having a few hangup points.
>  -- Ari Johnson
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From apavloff@eason.com Mon Oct 14 13:05:39 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 1818ex-0004AB-00
	for bug-commoncpp@gnu.org; Mon, 14 Oct 2002 13:05:39 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 1818ev-00049s-00
	for bug-commoncpp@gnu.org; Mon, 14 Oct 2002 13:05:38 -0400
Received: from b.smtp-out.sonic.net ([208.201.224.39])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 1818ev-00049V-00
	for bug-commoncpp@gnu.org; Mon, 14 Oct 2002 13:05:37 -0400
Received: (qmail 8144 invoked from network); 14 Oct 2002 17:05:36 -0000
Received: from prop.sonic.net (208.201.224.193)
  by b.smtp-out.sonic.net with SMTP; 14 Oct 2002 17:05:36 -0000
Received: from mailman.eason.com (adsl-209-204-139-80.sonic.net [209.204.139.80])
	by prop.sonic.net (8.11.6/8.8.5) with ESMTP id g9EH5ad17369;
	Mon, 14 Oct 2002 10:05:36 -0700
X-envelope-info: <apavloff@eason.com>
Received: by mailman.eason.com with Internet Mail Service (5.5.2653.19)
	id <4TF98NLW>; Mon, 14 Oct 2002 10:05:35 -0700
Message-ID: <D3AF5F134D627243993F2F2FC32EE4D229C359@mailman.eason.com>
From: Alex Pavloff <apavloff@eason.com>
To: "'Ari Johnson'" <ariston@cs.und.edu>, bug-commoncpp@gnu.org
Subject: RE: GCC 3.x Compatibility
Date: Mon, 14 Oct 2002 10:05:33 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

> -----Original Message-----
> From: Ari Johnson [mailto:ariston@cs.und.edu]
> Sent: Sunday, October 13, 2002 11:06 AM
> To: bug-commoncpp@gnu.org
> Subject: GCC 3.x Compatibility
> 
> 
> 
> Has anyone successfully built CommonC++ using the gcc 3.x C++ 
> compiler?  I seem to be having a few hangup points.
>  -- Ari Johnson

I am using GCC 3.2 compiled from source on Red Hat 7.3 with
--enable-threads=posix.  Works fine.  

Alex Pavloff - apavloff@eason.com
Eason Technology -- www.eason.com
 



From ariston@cs.und.edu Tue Oct 15 09:48:20 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 181S3Y-0004ZR-00
	for bug-commoncpp@gnu.org; Tue, 15 Oct 2002 09:48:20 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 181S3R-0004Ff-00
	for bug-commoncpp@gnu.org; Tue, 15 Oct 2002 09:48:19 -0400
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 181S3Q-00045U-00
	for bug-commoncpp@gnu.org; Tue, 15 Oct 2002 09:48:12 -0400
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id g9FDmXlh001811;
	Tue, 15 Oct 2002 08:48:34 -0500
Date: Tue, 15 Oct 2002 08:49:04 -0500 (CDT)
From: Ari Johnson <ariston@cs.und.edu>
To: Alex Pavloff <apavloff@eason.com>
cc: <bug-commoncpp@gnu.org>
Subject: RE: GCC 3.x Compatibility
In-Reply-To: <D3AF5F134D627243993F2F2FC32EE4D229C359@mailman.eason.com>
Message-ID: <Pine.GSO.4.33.0210150845250.10667-100000@agassiz.cs.und.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

I'm running FreeBSD with gcc 3.2.1 installed from the ports tree.  So far
I've noticed no problems with it, until I tried to compile CommonC++.
Maybe it's a problem with my installation of gcc, but I have my doubts
about that given that these problems only seem to occur with CommonC++.

The problem that seems to be occurring, from what I can ascertain, is that
the compiler can't find symbols from C.  For example, 'nanosleep' is found
just fine by configure, but at compile-time, it has no idea where to find
it.  The same applies to a long list of functions from math.h, which is
included by cmath, which is itself eventually included by iostream.  This
leads me to believe that somehow CommonC++ is hiding things from the
compiler, as these headers all work flawlessly in other cases.

Has anyone had a similar problem to this?
 -- Ari Johnson

On Mon, 14 Oct 2002, Alex Pavloff wrote:

>
> > -----Original Message-----
> > From: Ari Johnson [mailto:ariston@cs.und.edu]
> > Sent: Sunday, October 13, 2002 11:06 AM
> > To: bug-commoncpp@gnu.org
> > Subject: GCC 3.x Compatibility
> >
> >
> >
> > Has anyone successfully built CommonC++ using the gcc 3.x C++
> > compiler?  I seem to be having a few hangup points.
> >  -- Ari Johnson
>
> I am using GCC 3.2 compiled from source on Red Hat 7.3 with
> --enable-threads=posix.  Works fine.
>
> Alex Pavloff - apavloff@eason.com
> Eason Technology -- www.eason.com
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>




From leonardt@intelis-inc.com Tue Oct 15 18:34:01 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 181aGH-0000wR-00
	for bug-commoncpp@gnu.org; Tue, 15 Oct 2002 18:34:01 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 181aGF-0000w8-00
	for bug-commoncpp@gnu.org; Tue, 15 Oct 2002 18:34:00 -0400
Received: from [216.95.231.206] (helo=reserve.guest-tek.com)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 181aGE-0000vw-00
	for bug-commoncpp@gnu.org; Tue, 15 Oct 2002 18:33:58 -0400
Received: from phoenix.intelis-inc.com ([192.168.1.104])
	by reserve.guest-tek.com (8.11.6/8.8.7) with ESMTP id g9FMYZS04812;
	Tue, 15 Oct 2002 18:34:35 -0400
Message-Id: <5.1.1.6.0.20021015183244.00b848e8@pop.business.earthlink.net>
X-Sender: leonardt@intelis-inc.com@pop.business.earthlink.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 15 Oct 2002 18:33:42 -0400
To: Ari Johnson <ariston@cs.und.edu>, Alex Pavloff <apavloff@eason.com>
From: Leonard Thornton <leonardt@intelis-inc.com>
Subject: RE: GCC 3.x Compatibility
Cc: <bug-commoncpp@gnu.org>
In-Reply-To: <Pine.GSO.4.33.0210150845250.10667-100000@agassiz.cs.und.ed
 u>
References: <D3AF5F134D627243993F2F2FC32EE4D229C359@mailman.eason.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

I once had a problem similar to this which was caused by having the kernel 
sources and includes loaded on the machine and appearing first in my 
INCLUDE variable......

just a thought

At 08:49 AM 10/15/2002 -0500, Ari Johnson wrote:

>I'm running FreeBSD with gcc 3.2.1 installed from the ports tree.  So far
>I've noticed no problems with it, until I tried to compile CommonC++.
>Maybe it's a problem with my installation of gcc, but I have my doubts
>about that given that these problems only seem to occur with CommonC++.
>
>The problem that seems to be occurring, from what I can ascertain, is that
>the compiler can't find symbols from C.  For example, 'nanosleep' is found
>just fine by configure, but at compile-time, it has no idea where to find
>it.  The same applies to a long list of functions from math.h, which is
>included by cmath, which is itself eventually included by iostream.  This
>leads me to believe that somehow CommonC++ is hiding things from the
>compiler, as these headers all work flawlessly in other cases.
>
>Has anyone had a similar problem to this?
>  -- Ari Johnson
>
>On Mon, 14 Oct 2002, Alex Pavloff wrote:
>
> >
> > > -----Original Message-----
> > > From: Ari Johnson [mailto:ariston@cs.und.edu]
> > > Sent: Sunday, October 13, 2002 11:06 AM
> > > To: bug-commoncpp@gnu.org
> > > Subject: GCC 3.x Compatibility
> > >
> > >
> > >
> > > Has anyone successfully built CommonC++ using the gcc 3.x C++
> > > compiler?  I seem to be having a few hangup points.
> > >  -- Ari Johnson
> >
> > I am using GCC 3.2 compiled from source on Red Hat 7.3 with
> > --enable-threads=posix.  Works fine.
> >
> > Alex Pavloff - apavloff@eason.com
> > Eason Technology -- www.eason.com
> >
> >
> >
> > _______________________________________________
> > 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

Leonard Thornton
Intelis, Inc.
770.825.0032
leonardt@intelis-inc.com





From danielb@obfuscation.dyndns.org Fri Oct 18 17:42:50 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 182etO-0003zd-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 17:42:50 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 182etL-0003yI-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 17:42:48 -0400
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 182aaY-0002fZ-01
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 13:07:06 -0400
Received: from mke-24-167-202-50.wi.rr.com ([24.167.202.50] helo=frell.dyndns.org)
	by gnudist.gnu.org with esmtp (Exim 4.10)
	id 182KCe-000143-00
	for bug-commoncpp@gnu.org; Thu, 17 Oct 2002 19:37:20 -0400
Received: from obfuscation.dyndns.org ([192.168.1.2] ident=mail)
	by frell.dyndns.org with esmtp (Exim 3.36 #1 (Debian))
	id 182K93-00024N-00
	for <bug-commoncpp@gnu.org>; Thu, 17 Oct 2002 18:33:37 -0500
Received: from danielb by obfuscation.dyndns.org with local (Exim 3.36 #1 (Debian))
	id 182K90-0005VR-00
	for <bug-commoncpp@gnu.org>; Thu, 17 Oct 2002 18:33:34 -0500
Date: Thu, 17 Oct 2002 18:33:34 -0500
From: Daniel E Baumann <baumannd@msoe.edu>
To: bug-commoncpp@gnu.org
Subject: Piostreams Patch
Message-ID: <20021017233333.GA21161@obfuscation.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Here's a patch to fix building against piostreams. It seems that a few
headers were missing in the Makefile.am :-o. Also the demo does not
work in the case that you do not compile piostreams in. So also
included is a patch to fix this.

Happy Hacking,
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 danielb@obfuscation.dyndns.org Fri Oct 18 21:59:15 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 182itX-0003Vy-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 21:59:15 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 182itV-0003VS-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 21:59:14 -0400
Received: from mke-24-167-202-50.wi.rr.com ([24.167.202.50] helo=frell.dyndns.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 182itV-0003VG-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 21:59:13 -0400
Received: from obfuscation.dyndns.org ([192.168.1.2] ident=mail)
	by frell.dyndns.org with esmtp (Exim 3.36 #1 (Debian))
	id 182itU-00039L-00
	for <bug-commoncpp@gnu.org>; Fri, 18 Oct 2002 20:59:12 -0500
Received: from danielb by obfuscation.dyndns.org with local (Exim 3.36 #1 (Debian))
	id 182itR-0006Po-00
	for <bug-commoncpp@gnu.org>; Fri, 18 Oct 2002 20:59:09 -0500
Date: Fri, 18 Oct 2002 20:59:09 -0500
From: Daniel E Baumann <baumannd@msoe.edu>
To: bug-commoncpp@gnu.org
Subject: Re: Piostreams Patch
Message-ID: <20021019015909.GA24602@obfuscation.dyndns.org>
References: <20021017233333.GA21161@obfuscation.dyndns.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="45Z9DzgjV8m4Oswq"
Content-Disposition: inline
In-Reply-To: <20021017233333.GA21161@obfuscation.dyndns.org>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

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

Although it does help to atatch the freakin file! gah! I *always* do
this!

Dan

On Thu, Oct 17, 2002 at 06:33:34PM -0500, Daniel E Baumann wrote:
> Here's a patch to fix building against piostreams. It seems that a few
> headers were missing in the Makefile.am :-o. Also the demo does not
> work in the case that you do not compile piostreams in. So also
> included is a patch to fix this.
> 
> Happy Hacking,
> 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
> 
> 
> _______________________________________________
> 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

--45Z9DzgjV8m4Oswq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="piostream.diff"

Index: include/cc++/Makefile.am
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/Makefile.am,v
retrieving revision 1.6
diff -u -3 -p -r1.6 Makefile.am
--- include/cc++/Makefile.am	29 Sep 2002 17:35:29 -0000	1.6
+++ include/cc++/Makefile.am	17 Oct 2002 23:30:35 -0000
@@ -23,7 +23,8 @@ ccxxinclude_HEADERS = \
 	cmdoptns.h common.h config.h digest.h exception.h export.h file.h \
 	ftp.h groups.h misc.h numbers.h persist.h serial.h slog.h \
 	socket.h strchar.h thread.h unix.h url.h xml.h process.h urlstring.h \
-	piostream piomanip pios postream postream.tcc pistream piosfwd
+	piostream piomanip pios postream postream.tcc pistream pistream.tcc \
+	piosfwd pios_init.h
 
 kdoc_headers = \
 	cmdoptns.h common.h config.h digest.h exception.h export.h file.h \
Index: demo/pio.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/demo/pio.cpp,v
retrieving revision 1.2
diff -u -3 -p -r1.2 pio.cpp
--- demo/pio.cpp	29 Sep 2002 17:35:29 -0000	1.2
+++ demo/pio.cpp	17 Oct 2002 23:30:35 -0000
@@ -249,6 +249,10 @@ int main(int argc, char* argv[])
 #else
 
 #include <cc++/common.h>
+#include <iostream>
+
+using namespace std;
+
 int main(int argc, char* argv[])
 {
   cout << "piostream support disabled!" << endl;

--45Z9DzgjV8m4Oswq--



From dyfet@ostel.com Fri Oct 18 22:21:49 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 182jFM-0001Kf-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 22:21:48 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 182jFK-0001K3-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 22:21:48 -0400
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 182cKc-0002uW-02
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 14:58:46 -0400
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by gnudist.gnu.org with esmtp (Exim 4.10)
	id 181qdS-0003Ja-00
	for bug-commoncpp@gnu.org; Wed, 16 Oct 2002 12:03:02 -0400
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id g9GGN2329452;
	Wed, 16 Oct 2002 12:23:02 -0400
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 16 Oct 2002 12:23:02 -0400 (EDT)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Tim Esselens <tim@ba.be>
cc: bug-commoncpp@gnu.org
Subject: Re: question about Common C++ 2 serial class
In-Reply-To: <200210161702.43728.tim@ba.be>
Message-ID: <Pine.LNX.4.44.0210161220020.29355-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

I believe you should be able to use the isPending method to test if the
device is writable (isPending(SERIAL_PEND_OUTPUT, maxtime)) to safely test
if you can use this->flush with a timeout.  flushOutput() is meant to
flush the device i/o queue and wait for i/o completion rather than the
stream buffer.  The aRead and aWrite methods may also be overriden in a
derived class, and can be replaced with async i/o routines depending on
your environment.

David

On Wed, 16 Oct 2002, Tim Esselens wrote:

> Hi,
> 
> I've been using your serial class for a HA (high availability) project. I've 
> managed to get 2 machines to ping eachother over serial line. But there is a 
> rather big problem coming up. If I flush (this->flush()) my object 
> (SerialBeat: public TTYSession) the thread blocks, flushOutput() doesn't seem 
> to be flushing at all.
> 
> So, the problem I'm having is quite simple, how to flush in a nonblocking kind 
> of mode, so after n msecs of 'unflushability' it could start throwing errors.
> I only hope the answer is as easy as the question.
> 
> If this is not possible for some reason, is there a way around this (still 
> using your serial class ofcourse)? I need to detect the other side is down, 
> that's really it (maybe something the serial protocol allready includes, but 
> I'm new to serial lines, so I wouldn't know).
> 
> kind regards,
> Tim Esselens
> 
> ps: NEWS stated sending questions to dyfet, README to bug-commoncpp, I did 
> both <g>
> 




From dyfet@ostel.com Fri Oct 18 22:25:55 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 182jJL-0002SF-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 22:25:55 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 182jJJ-0002Rs-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 22:25:55 -0400
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 182cKV-0001tj-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 14:58:39 -0400
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by gnudist.gnu.org with esmtp (Exim 4.10)
	id 181qgN-0004h9-00
	for bug-commoncpp@gnu.org; Wed, 16 Oct 2002 12:06:03 -0400
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id g9GGQ8V29473;
	Wed, 16 Oct 2002 12:26:08 -0400
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 16 Oct 2002 12:26:07 -0400 (EDT)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Tim Esselens <tim@ba.be>
cc: bug-commoncpp@gnu.org
Subject: Re: question about Common C++ 2 serial class
In-Reply-To: <200210161730.38591.tim@ba.be>
Message-ID: <Pine.LNX.4.44.0210161225190.29355-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Ah, you wanted to call the i/o methods directly...yes, you can use aRead 
and aWrite for this...



On Wed, 16 Oct 2002, Tim Esselens wrote:

> > So, the problem I'm having is quite simple, how to flush in a nonblocking
> > kind of mode, so after n msecs of 'unflushability' it could start throwing
> > errors. I only hope the answer is as easy as the question.
> and of course, it is! :)
> 
> aRead and aWrite seem to be doing just te things I needed,
> nevertheless I would like to see something I described in my prior mail, so 
> consider it a 'ah, he used it this way' report :)
> 
> I would also like to say you guys do a great job, I've worked with your lib 
> before (needed threading) and it just couldn't get any better, my new project 
> included just one thing not in your old lib, serial connections. Since that 
> is coded now, I think your lib will be one of my most used ones.
> So, thanks again, keep up the good work!
> 
> kind regards,
> Tim Esselens
> 




From chad_pettit@xontech.com Mon Oct 21 11:12:48 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 183eEZ-0007Uk-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 11:12:47 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 183eEY-0007UZ-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 11:12:47 -0400
Received: from filter.xontech.com ([216.180.56.2])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 183eEX-0007UQ-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 11:12:46 -0400
Received: from xontech.com (host31.xontech.com [216.180.56.31])
	by filter.xontech.com (8.11.6/8.11.2) with ESMTP id g9LFCG225977
	for <bug-commoncpp@gnu.org>; Mon, 21 Oct 2002 10:12:16 -0500
Message-ID: <3DB4193A.4040503@xontech.com>
Date: Mon, 21 Oct 2002 11:11:54 -0400
From: Chad Pettit <chad_pettit@xontech.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
Subject: Deleting a non-autofree thread
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner: Found to be clean
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

What is the proper way to delete a non-autofree thread?  I have tried 
several combo's with endStream(), terminate(), endSocket() and others 
and nothing appears to be working.  I get an out of resource error when 
I would try to allocate another thread.  I am using TCSession.




From fedemp@wanadoo.es Mon Oct 21 15:37:02 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 183iMI-00038m-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 15:37:02 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 183iMF-00036p-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 15:37:01 -0400
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 183iME-000344-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 15:36:58 -0400
Received: from risitas (62-36-181-229.dialup.uni2.es [62.36.181.229])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g9LJZEX25628;
	Mon, 21 Oct 2002 21:35:15 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 183iPX-0000Jv-00; Mon, 21 Oct 2002 21:40:23 +0200
Date: Mon, 21 Oct 2002 21:40:20 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Pettit <chad_pettit@xontech.com>
Cc: bug-commoncpp@gnu.org
Subject: Re: Deleting a non-autofree thread
Message-ID: <20021021194020.GA642@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Chad Pettit <chad_pettit@xontech.com>,
	bug-commoncpp@gnu.org
References: <3DB4193A.4040503@xontech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DB4193A.4040503@xontech.com>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

On Mon, Oct 21, 2002 at 11:11:54AM -0400, Chad Pettit wrote:
> What is the proper way to delete a non-autofree thread?  

	Do you mean a thread that does not do 'delete this' in its
final() method? Normally, threads can be deleted using 'delete
thread' if they are dynamically created.

> I have tried 
> several combo's with endStream(), terminate(), endSocket() and others 
> and nothing appears to be working.  I get an out of resource error when 
> I would try to allocate another thread.  I am using TCSession.
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From chad_pettit@xontech.com Mon Oct 21 16:11:24 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 183it2-0005HW-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 16:10:52 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 183ist-0004m7-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 16:10:49 -0400
Received: from filter.xontech.com ([216.180.56.2])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 183isr-0004cz-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 16:10:41 -0400
Received: from xontech.com (host31.xontech.com [216.180.56.31])
	by filter.xontech.com (8.11.6/8.11.2) with ESMTP id g9LK5a220874;
	Mon, 21 Oct 2002 15:05:36 -0500
Message-ID: <3DB45DFA.50400@xontech.com>
Date: Mon, 21 Oct 2002 16:05:14 -0400
From: Chad Pettit <chad_pettit@xontech.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Federico Montesino Pouzols <fedemp@altern.org>
CC: bug-commoncpp@gnu.org
Subject: Re: Deleting a non-autofree thread
References: <3DB4193A.4040503@xontech.com> <20021021194020.GA642@risitas>
Content-Type: multipart/alternative;
 boundary="------------020403050908080106090304"
X-MailScanner: Found to be clean
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

--------------020403050908080106090304
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Yes.  A thread that does not do a delete this in its final method.

Currently, I am doing a delete thread once the main thread retrieves 
some information off of the processing thread.  This; however, only 
works for the first 512 threads.  After that I am getting a resource 
allocation error.  To me, this indicates that the thread is not being 
completely destroyed, since the thread limit should not come into play 
as long as the threads are being cleaned up properly.

Federico Montesino Pouzols wrote:

>On Mon, Oct 21, 2002 at 11:11:54AM -0400, Chad Pettit wrote:
>  
>
>>What is the proper way to delete a non-autofree thread?  
>>    
>>
>
>	Do you mean a thread that does not do 'delete this' in its
>final() method? Normally, threads can be deleted using 'delete
>thread' if they are dynamically created.
>
>  
>
>>I have tried 
>>several combo's with endStream(), terminate(), endSocket() and others 
>>and nothing appears to be working.  I get an out of resource error when 
>>I would try to allocate another thread.  I am using TCSession.
>>
>>
>>
>>_______________________________________________
>>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
>
>  
>

--------------020403050908080106090304
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body>
Yes. &nbsp;A thread that does not do a delete this in its final method.<br>
<br>
Currently, I am doing a delete thread once the main thread retrieves some
information off of the processing thread. &nbsp;This; however, only works for
the first 512 threads. &nbsp;After that I am getting a resource allocation error.
&nbsp;To me, this indicates that the thread is not being completely destroyed,
since the thread limit should not come into play as long as the threads are
being cleaned up properly.<br>
<br>
Federico Montesino Pouzols wrote:<br>
<blockquote type="cite" cite="mid20021021194020.GA642@risitas">
  <pre wrap="">On Mon, Oct 21, 2002 at 11:11:54AM -0400, Chad Pettit wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">What is the proper way to delete a non-autofree thread?  
    </pre>
  </blockquote>
  <pre wrap=""><!---->
	Do you mean a thread that does not do 'delete this' in its
final() method? Normally, threads can be deleted using 'delete
thread' if they are dynamically created.

  </pre>
  <blockquote type="cite">
    <pre wrap="">I have tried 
several combo's with endStream(), terminate(), endSocket() and others 
and nothing appears to be working.  I get an out of resource error when 
I would try to allocate another thread.  I am using TCSession.



_______________________________________________
Bug-commoncpp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bug-commoncpp@gnu.org">Bug-commoncpp@gnu.org</a>
<a class="moz-txt-link-freetext" href="http://mail.gnu.org/mailman/listinfo/bug-commoncpp">http://mail.gnu.org/mailman/listinfo/bug-commoncpp</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->

_______________________________________________
Bug-commoncpp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bug-commoncpp@gnu.org">Bug-commoncpp@gnu.org</a>
<a class="moz-txt-link-freetext" href="http://mail.gnu.org/mailman/listinfo/bug-commoncpp">http://mail.gnu.org/mailman/listinfo/bug-commoncpp</a>

  </pre>
</blockquote>
</body>
</html>

--------------020403050908080106090304--




From anand_narwani@yahoo.com Mon Oct 21 18:04:21 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 183keq-0000if-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 18:04:20 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 183kei-0000FQ-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 18:04:16 -0400
Received: from web12306.mail.yahoo.com ([216.136.173.104])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 183keh-0000AJ-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 18:04:11 -0400
Message-ID: <20021021220410.43636.qmail@web12306.mail.yahoo.com>
Received: from [24.93.64.110] by web12306.mail.yahoo.com via HTTP; Mon, 21 Oct 2002 15:04:10 PDT
Date: Mon, 21 Oct 2002 15:04:10 -0700 (PDT)
From: Anand Narwani <anand_narwani@yahoo.com>
Subject: Timers and Signals on Solaris 2.8
To: bug-commoncpp@gnu.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hello Folks,
I am attempting to do something seemingly simple, but
It does not work correctly on Solaris.  Here is my
configuration:
- Solaris 2.8
- g++ 2.95.2
- Common C++2 1.03

The program I am attempting to write has one main
thread which is essentially a scheduler that does some
work and then sleeps for a predefined period.  Here's
the source for a test program I which is similar to
what I am attmpting to do:

http://www.employees.org/~anarwani/thread-test.html


There are two problems that I see:
1.  The onTimer function never gets called.  After
playing with the source in thread.cpp, It appears that
the SIGALARM is not getting sent to the thread.  This
seems to work just fine on Linux
2.  The delete operator does not force a join.  I
finally used a semaphore to get this to work.  This
does *not* work on linux either.

I'm sure I must be missing something simple, but I
cannot find it.  Any help would be very much
appreciated.

Regards,
Anand

__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/



From chad_pettit@xontech.com Tue Oct 22 14:56:24 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 1844CW-0008R7-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 14:56:24 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 1844CS-0008QU-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 14:56:23 -0400
Received: from filter.xontech.com ([216.180.56.2])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 1844CR-0008QI-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 14:56:19 -0400
Received: from xontech.com (host31.xontech.com [216.180.56.31])
	by filter.xontech.com (8.11.6/8.11.2) with ESMTP id g9MItvN07679
	for <bug-commoncpp@gnu.org>; Tue, 22 Oct 2002 13:55:58 -0500
Message-ID: <3DB59F27.7050802@xontech.com>
Date: Tue, 22 Oct 2002 14:55:35 -0400
From: Chad Pettit <chad_pettit@xontech.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
Subject: synchronized reading and writing
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner: Found to be clean
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Using TCPSession how does synchronized reading and writing work.

I have something like this:

void Connection::runTransmitter()
{
    char line[200];
    std::iostream *connection = tcp();
    connection->write(_message.c_str(), _message.length());

    if (isPending(Socket::pendingInput))
        *connection >> line;  
    std::cerr << "Transmit: " << line << std::endl;
}

void Connection::runReceiver()
{   
    char line[200];
    std::iostream* connection = tcp();

    if (isPending(Socket::pendingInput))
        *connection >> line;
   
    std::cerr << "Receive: " << line << std::endl;
    *connection << "message successfully received";   
}

It hangs at the isPending function on the Receiver side.  If I put in a 
endStream() call on the transmitter side, the receiver gets the message, 
but the tranmitter then hangs on its isPending.  The endStream function 
ends the socket as well as the stream.  I don't believe this is correct 
because I eventually want the communication to be ongoing between the 
receiver and transmitter.

Any help would be greatly appreciated.




From fedemp@wanadoo.es Tue Oct 22 15:57:43 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18459r-0000Ma-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 15:57:43 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18459p-0000ME-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 15:57:42 -0400
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18459o-0000M8-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 15:57:41 -0400
Received: from risitas ([80.103.114.39])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g9MJtqX13450;
	Tue, 22 Oct 2002 21:55:53 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 1845DC-0000Jr-00; Tue, 22 Oct 2002 22:01:10 +0200
Date: Tue, 22 Oct 2002 22:01:10 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Chad Pettit <chad_pettit@xontech.com>
Cc: Federico Montesino Pouzols <fedemp@altern.org>, bug-commoncpp@gnu.org
Subject: Re: Deleting a non-autofree thread
Message-ID: <20021022200110.GC640@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Chad Pettit <chad_pettit@xontech.com>,
	Federico Montesino Pouzols <fedemp@altern.org>,
	bug-commoncpp@gnu.org
References: <3DB4193A.4040503@xontech.com> <20021021194020.GA642@risitas> <3DB45DFA.50400@xontech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DB45DFA.50400@xontech.com>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	This is strange, what system does this problem occur on? Could
you post your code?

On Mon, Oct 21, 2002 at 04:05:14PM -0400, Chad Pettit wrote:
> Yes.  A thread that does not do a delete this in its final method.
> 
> Currently, I am doing a delete thread once the main thread retrieves 
> some information off of the processing thread.  This; however, only 
> works for the first 512 threads.  After that I am getting a resource 
> allocation error.  To me, this indicates that the thread is not being 
> completely destroyed, since the thread limit should not come into play 
> as long as the threads are being cleaned up properly.
> 
> Federico Montesino Pouzols wrote:
> 
> >On Mon, Oct 21, 2002 at 11:11:54AM -0400, Chad Pettit wrote:
> > 
> >
> >>What is the proper way to delete a non-autofree thread?  
> >>   
> >>
> >
> >	Do you mean a thread that does not do 'delete this' in its
> >final() method? Normally, threads can be deleted using 'delete
> >thread' if they are dynamically created.
> >
> > 
> >
> >>I have tried 
> >>several combo's with endStream(), terminate(), endSocket() and others 
> >>and nothing appears to be working.  I get an out of resource error when 
> >>I would try to allocate another thread.  I am using TCSession.
> >>
> >>
> >>
> >>_______________________________________________
> >>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 chad_pettit@xontech.com Tue Oct 22 16:08:57 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 1845Kj-0008B8-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 16:08:57 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 1845Kg-000874-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 16:08:56 -0400
Received: from filter.xontech.com ([216.180.56.2])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 1845Kc-00083C-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 16:08:52 -0400
Received: from xontech.com (host31.xontech.com [216.180.56.31])
	by filter.xontech.com (8.11.6/8.11.2) with ESMTP id g9MK8HN14709;
	Tue, 22 Oct 2002 15:08:17 -0500
Message-ID: <3DB5B01A.8080408@xontech.com>
Date: Tue, 22 Oct 2002 16:07:54 -0400
From: Chad Pettit <chad_pettit@xontech.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Federico Montesino Pouzols <fedemp@altern.org>
CC: bug-commoncpp@gnu.org
Subject: Re: Deleting a non-autofree thread
References: <3DB4193A.4040503@xontech.com> <20021021194020.GA642@risitas> <3DB45DFA.50400@xontech.com> <20021022200110.GC640@risitas>
Content-Type: multipart/mixed;
 boundary="------------040706010404020501070906"
X-MailScanner: Found to be clean
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

This is a multi-part message in MIME format.
--------------040706010404020501070906
Content-Type: multipart/alternative;
 boundary="------------070002090902060700010606"


--------------070002090902060700010606
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

It happens on a linux box, running Mandrake 9.0.

I attached my code.  

The Dtran class basically controls both the transmitter and receiver 
connections, which are TCPSessions.  When isRunning() is false for one 
of the connections it deletes the connection.

Federico Montesino Pouzols wrote:

>	This is strange, what system does this problem occur on? Could
>you post your code?
>
>On Mon, Oct 21, 2002 at 04:05:14PM -0400, Chad Pettit wrote:
>  
>
>>Yes.  A thread that does not do a delete this in its final method.
>>
>>Currently, I am doing a delete thread once the main thread retrieves 
>>some information off of the processing thread.  This; however, only 
>>works for the first 512 threads.  After that I am getting a resource 
>>allocation error.  To me, this indicates that the thread is not being 
>>completely destroyed, since the thread limit should not come into play 
>>as long as the threads are being cleaned up properly.
>>
>>Federico Montesino Pouzols wrote:
>>
>>    
>>
>>>On Mon, Oct 21, 2002 at 11:11:54AM -0400, Chad Pettit wrote:
>>>
>>>
>>>      
>>>
>>>>What is the proper way to delete a non-autofree thread?  
>>>>  
>>>>
>>>>        
>>>>
>>>	Do you mean a thread that does not do 'delete this' in its
>>>final() method? Normally, threads can be deleted using 'delete
>>>thread' if they are dynamically created.
>>>
>>>
>>>
>>>      
>>>
>>>>I have tried 
>>>>several combo's with endStream(), terminate(), endSocket() and others 
>>>>and nothing appears to be working.  I get an out of resource error when 
>>>>I would try to allocate another thread.  I am using TCSession.
>>>>
>>>>
>>>>
>>>>_______________________________________________
>>>>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
>>>
>>>
>>>
>>>      
>>>
>
>  
>

--------------070002090902060700010606
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body>
It happens on a linux box, running Mandrake 9.0.<br>
<br>
I attached my code. &nbsp;<br>
<br>
The Dtran class basically controls both the transmitter and receiver connections,
which are TCPSessions. &nbsp;When isRunning() is false for one of the connections
it deletes the connection.<br>
<br>
Federico Montesino Pouzols wrote:<br>
<blockquote type="cite" cite="mid20021022200110.GC640@risitas">
  <pre wrap="">	This is strange, what system does this problem occur on? Could
you post your code?

On Mon, Oct 21, 2002 at 04:05:14PM -0400, Chad Pettit wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Yes.  A thread that does not do a delete this in its final method.

Currently, I am doing a delete thread once the main thread retrieves 
some information off of the processing thread.  This; however, only 
works for the first 512 threads.  After that I am getting a resource 
allocation error.  To me, this indicates that the thread is not being 
completely destroyed, since the thread limit should not come into play 
as long as the threads are being cleaned up properly.

Federico Montesino Pouzols wrote:

    </pre>
    <blockquote type="cite">
      <pre wrap="">On Mon, Oct 21, 2002 at 11:11:54AM -0400, Chad Pettit wrote:


      </pre>
      <blockquote type="cite">
        <pre wrap="">What is the proper way to delete a non-autofree thread?  
  

        </pre>
      </blockquote>
      <pre wrap="">	Do you mean a thread that does not do 'delete this' in its
final() method? Normally, threads can be deleted using 'delete
thread' if they are dynamically created.



      </pre>
      <blockquote type="cite">
        <pre wrap="">I have tried 
several combo's with endStream(), terminate(), endSocket() and others 
and nothing appears to be working.  I get an out of resource error when 
I would try to allocate another thread.  I am using TCSession.



_______________________________________________
Bug-commoncpp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bug-commoncpp@gnu.org">Bug-commoncpp@gnu.org</a>
<a class="moz-txt-link-freetext" href="http://mail.gnu.org/mailman/listinfo/bug-commoncpp">http://mail.gnu.org/mailman/listinfo/bug-commoncpp</a>
  

        </pre>
      </blockquote>
      <pre wrap="">
_______________________________________________
Bug-commoncpp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bug-commoncpp@gnu.org">Bug-commoncpp@gnu.org</a>
<a class="moz-txt-link-freetext" href="http://mail.gnu.org/mailman/listinfo/bug-commoncpp">http://mail.gnu.org/mailman/listinfo/bug-commoncpp</a>



      </pre>
    </blockquote>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>

--------------070002090902060700010606--

--------------040706010404020501070906
Content-Type: text/plain;
 name="Connection.h"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Connection.h"

#ifndef CONNECTION_H
#define CONNECTION_H

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

typedef std::string string;

class Connection : public ost::TCPSession
{
	public:
		Connection(ost::TCPSocket &server);
		Connection(const ost::InetHostAddress &host, ost::tpport_t port, const string &message);
		
		~Connection();
		bool isRunning();
	
	protected:
		void run();
		void final();
		void close();
	
		void runTransmitter();
		void runReceiver();
			
	private:
		void init();
			
		bool _type; // 0 Transmitter 1 Receiver
		string _message;
		bool _isRun;
		
};

#endif

--------------040706010404020501070906
Content-Type: text/plain;
 name="Dtran.h"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Dtran.h"

#ifndef DTRAN_H
#define DTRAN_H

#include "Connection.h"
#include <cc++/socket.h>
#include <vector>

typedef std::string string;

class Dtran : public ost::TCPSocket
{
	public:
		Dtran(const ost::InetAddress &bind, ost::tpport_t port);
		~Dtran();
	
		void serve();
		void send(const ost::InetHostAddress &host, const string &message);
		void status();
	
	protected:
		void statusReceiver();
		void statusTransmitter();
	
	private:
		int rec;
		ost::tpport_t _port;
		std::vector<Connection*> _receiverList;
		std::vector<Connection*> _transmitterList;
};

#endif


--------------040706010404020501070906
Content-Type: text/plain;
 name="Connection.cpp"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Connection.cpp"

#include "Connection.h"
#include <iostream>

Connection::Connection(const ost::InetHostAddress &host, ost::tpport_t port, const string &message)
	: ost::TCPSession(host, port)
{
	_type = 0;
	_message = message;
	init();
	
}

Connection::Connection(ost::TCPSocket &server)
	: ost::TCPSession(server)
{
	_type = 1;
	init();
}

void Connection::init()
{
	_isRun = true;
}

Connection::~Connection()
{
	terminate();
}

bool Connection::isRunning()
{
	return _isRun;
}

void Connection::close()
{
	exit();
}

void Connection::run()
{
	_isRun = true;
	
	if (_type == 0)
		runTransmitter();
	else
		runReceiver();
	
	close();
}

void Connection::final()
{
	_isRun = false;
}

void Connection::runTransmitter()
{
	std::iostream* connection = tcp();
	*connection << _message.c_str();
}

void Connection::runReceiver()
{	
	char line[200];
	std::iostream* connection = tcp();

	while (!connection->eof())
	{
		*connection >> line;
		std::cerr << "Receive: " << line << std::endl;
	}
}


--------------040706010404020501070906
Content-Type: text/plain;
 name="Dtran.cpp"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Dtran.cpp"

#include "Dtran.h"
#include <iostream>

Dtran::Dtran(const ost::InetAddress &bind, ost::tpport_t port)
		: ost::TCPSocket(bind, port)
{
	_port = port;
	rec = 0;
}

Dtran::~Dtran()
{
	for (int i = _receiverList.size() - 1; i >= 0; --i)
	{
		delete _receiverList[i];
	}
	for (int i = _transmitterList.size() - 1; i >= 0; --i)
	{
		delete _transmitterList[i];
	}

	_receiverList.clear();
	_transmitterList.clear();
}

void Dtran::serve()
{
	int error;
	
	while (isPendingConnection(200))
	{
		Connection *connection = new Connection(*this);
		
		if ((error = connection->start()) == 0)
			_receiverList.push_back(connection);
		else
			std::cerr << "**************START REC FAILED********** " << strerror(error) << std::endl;
		std::cerr << "Number of connections: " << rec++ << std::endl;
	}
}

void Dtran::send(const ost::InetHostAddress &host, const string &message)
{
	int error;
	
	Connection *connection = new Connection(host, _port, message);
	if ((error = connection->start()) == 0)
		_transmitterList.push_back(connection);
	else
		std::cerr << "**************START TRANS FAILED********** " << strerror(error) << std::endl;
	
}

void Dtran::status()
{
	statusReceiver();
	statusTransmitter();
}

void Dtran::statusReceiver()
{	
	for (int i = _receiverList.size() - 1; i >= 0; --i)
	{
		std::cerr << "recv(" << i << ") " << _receiverList[i]->isRunning() << std::endl;
		if (!_receiverList[i]->isRunning())
		{
			// receiver is finished
			delete _receiverList[i];
			_receiverList.erase(_receiverList.begin() + i);
		}
	}
}

void Dtran::statusTransmitter()
{
	for (int i = _transmitterList.size() - 1; i >= 0; --i)
	{
		std::cerr << "trans(" << i << ") " << _transmitterList[i]->isRunning() << std::endl;
		if (!_transmitterList[i]->isRunning())
		{
			// transmitter is finished
			delete _transmitterList[i];
			_transmitterList.erase(_transmitterList.begin() + i);
		}
	}
}



--------------040706010404020501070906
Content-Type: text/plain;
 name="servDriver.cpp"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="servDriver.cpp"

#include "Dtran.h"

int main(int argc, char *argv[])
{
	ost::tpport_t port;
	ost::tcpstream tcp;
	
	sscanf(argv[2], "%d", &port);
	
	Dtran *dtran = new Dtran(argv[1], port);
	
	for (;;)
	{
		dtran->serve();
		dtran->send(argv[3], argv[4]);
		dtran->status();
	}
		
	delete dtran;
	
	return 0;
}

--------------040706010404020501070906--




From anand_narwani@yahoo.com Fri Oct 25 15:42:53 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 185AM8-0003ON-00
	for bug-commoncpp@gnu.org; Fri, 25 Oct 2002 15:42:52 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 185AKN-0001pC-00
	for bug-commoncpp@gnu.org; Fri, 25 Oct 2002 15:41:08 -0400
Received: from web12302.mail.yahoo.com ([216.136.173.100])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 185AKM-0001m9-00
	for bug-commoncpp@gnu.org; Fri, 25 Oct 2002 15:41:02 -0400
Message-ID: <20021025194101.31977.qmail@web12302.mail.yahoo.com>
Received: from [24.93.64.110] by web12302.mail.yahoo.com via HTTP; Fri, 25 Oct 2002 12:41:01 PDT
Date: Fri, 25 Oct 2002 12:41:01 -0700 (PDT)
From: Anand Narwani <anand_narwani@yahoo.com>
Subject: Solaris 8 and pthread issues.
To: bug-commoncpp@gnu.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hello Folks,
I am attempting to write a simple program using Common
C++2 1.0.3 on Solaris 8.  Here is the code:

/**** Code Starts Here ****/
#include <cc++/thread.h>
#include <cstdio>
#include <cstring>
#include <iostream>

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

class Foo: public Thread {
    public:
        Foo(Event *e){myevent = e;};
        void run();
    private:
        Event *myevent;
};

void Foo::run() {
    while (1) {
        for (int i=0; i< 5; i++) {
            cout << "counting... i=" << i << endl;
            sleep(500);
            yield();
        }
        myevent->signal();
        sleep(1000);
    }
}

int main (int argc,char** argv) {

    Event *ev;
    Foo *f;

    ev = new Event();
    f = new Foo(ev);
    f->start();
    ev->wait();
    cout << "**** Caught Event ****" << endl;

}
/***** Code Ends Here ****/

I've attempted to run this with GCC 2.95.2 and also
GCC 3.2 both seem to have the same results: 
Event::wait() never returns when I do a
Event::signal().  If I test with Event::wait(timeout),
it never times out.  
I've looked at the source for the Event Class and I
can see the call to pthread_cond_wait() or
pthread_cond_waittimeout().  When these are called,
neither one returns.  I've searched and searched the
newsgroups and the web.  The only issue I've found is
that Solaris *might* have a problem with recursive
mutexes.  Has anyone experienced problems like this? 
Am I missing something silly?

Thanks in advance,
Anand

__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/



From fedemp@wanadoo.es Sat Oct 26 15:33:41 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 185Wgn-0006PA-00
	for bug-commoncpp@gnu.org; Sat, 26 Oct 2002 15:33:41 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 185Wgj-0006Ou-00
	for bug-commoncpp@gnu.org; Sat, 26 Oct 2002 15:33:40 -0400
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 185Wgj-0006NK-00
	for bug-commoncpp@gnu.org; Sat, 26 Oct 2002 15:33:37 -0400
Received: from risitas (62-36-178-133.dialup.uni2.es [62.36.178.133])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g9QJVaX16958;
	Sat, 26 Oct 2002 21:31:36 +0200
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 185WkP-0004A2-00; Sat, 26 Oct 2002 21:37:25 +0200
Date: Sat, 26 Oct 2002 21:37:25 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Anand Narwani <anand_narwani@yahoo.com>
Cc: bug-commoncpp@gnu.org
Subject: Re: Solaris 8 and pthread issues.
Message-ID: <20021026193725.GC9569@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Anand Narwani <anand_narwani@yahoo.com>,
	bug-commoncpp@gnu.org
References: <20021025194101.31977.qmail@web12302.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021025194101.31977.qmail@web12302.mail.yahoo.com>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	I have just tried this on a Debian GNU/Linux box and it worked
well, so as you suggest it is probably a platform specific issue. Any
other details about what happens on your platform when you run this
program? Could you confirm if it gets blocked in the
pthread_... system call?

On Fri, Oct 25, 2002 at 12:41:01PM -0700, Anand Narwani wrote:
> Hello Folks,
> I am attempting to write a simple program using Common
> C++2 1.0.3 on Solaris 8.  Here is the code:
> 
> /**** Code Starts Here ****/
> /***** Code Ends Here ****/
> 
> I've attempted to run this with GCC 2.95.2 and also
> GCC 3.2 both seem to have the same results: 
> Event::wait() never returns when I do a
> Event::signal().  If I test with Event::wait(timeout),
> it never times out.  
> I've looked at the source for the Event Class and I
> can see the call to pthread_cond_wait() or
> pthread_cond_waittimeout().  When these are called,
> neither one returns.  I've searched and searched the
> newsgroups and the web.  The only issue I've found is
> that Solaris *might* have a problem with recursive
> mutexes.  Has anyone experienced problems like this? 
> Am I missing something silly?
> 
> Thanks in advance,
> Anand



From kspinka@gist.com Mon Oct 07 01:02:13 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17yQ1P-0001bs-00
	for bug-commoncpp@gnu.org; Mon, 07 Oct 2002 01:01:35 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17yQ14-0000a4-00
	for bug-commoncpp@gnu.org; Mon, 07 Oct 2002 01:01:20 -0400
Received: from [204.215.183.134] (helo=gsrv2003.corp.NYC.gist.com)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 17yQ0s-0008JJ-00
	for bug-commoncpp@gnu.org; Mon, 07 Oct 2002 01:01:03 -0400
Received: from gist.com (freelancer.corp.nyc.gist.com [192.168.9.73]) by gsrv2003.corp.NYC.gist.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id T864XGWD; Mon, 7 Oct 2002 00:59:28 -0400
Message-ID: <3DA11505.4020507@gist.com>
Date: Mon, 07 Oct 2002 01:00:53 -0400
From: "Spinka, Kristofer" <kspinka@gist.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2a) Gecko/20020910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Federico Montesino Pouzols <fedemp@altern.org>
CC: bug-commoncpp@gnu.org
Subject: Re: Solaris 9, SocketPort
References: <3DA00BA5.3020905@gist.com> <20021006203434.GI601@risitas>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Not only does endSocket() cause a segfault, but also during high volume 
accept's through use of SocketPort's.

    /kris

Federico Montesino Pouzols wrote:

>	Hi, the problem you are talking about seems to arise on Win32
>too. Some weeks ago, we received the following report from Klaus
>Triendl:
>
>--------------------------------------------
>i tested the SampleSocketServiceServer with linux and windows. under windows
>an exception is thrown in StopServer().
>i traced the problem and figured out that WSAGetLastError() in
>Socket::connectError() returns WSAEFAULT (=10014L).
>
>
>	virtual void StopServer()
>	{
>		m_bQuitServer = true;
>
>		InetHostAddress host;
>		tpport_t port;
>		host = getLocal(&port);
>
>		//This is required so that CreateSocketPort can return.
>		TCPStream strm(host, port);
>
>		waitMutex.enterMutex();
>		waitMutex.leaveMutex();
>	}
>
>
>if i change the code a little and the host is initialized with an address
>other than 0, there is not such a problem.
>
>
>	virtual void StopServer()
>	{
>		m_bQuitServer = true;
>
>		InetHostAddress host("127.0.0.1");
>		tpport_t port;
>		getLocal(&port);
>
>		//This is required so that CreateSocketPort can return.
>		TCPStream strm(host, port);
>
>		waitMutex.enterMutex();
>		waitMutex.leaveMutex();
>	}
>-----------------------------------------
>
>	Could you confirm if the same happens to you? You can also
>read the whole thread on this mail list archives (September, thread
>"exception in SampleSocketServiceServer::StopServer()"). We were
>planning to add some checks on Win32, but if it is the same problem
>what you are having on Solaris 9, we should probably add the checks
>for all platforms.
>
>On Sun, Oct 06, 2002 at 06:08:37AM -0400, Spinka, Kristofer wrote:
>  
>
>>  I haven't had the time to track anything down, however, if you try 
>>running the portsample (SampleSocketPort.cpp), you will see the problem 
>>immediately after the first client disconnects.
>>
>>    /kris
>>
>>
>>
>>_______________________________________________
>>Bug-commoncpp mailing list
>>Bug-commoncpp@gnu.org
>>http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>>    
>>




From test.nospam@t-online.de Tue Oct 08 17:43:03 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 17z287-0008Lt-00
	for bug-commoncpp@gnu.org; Tue, 08 Oct 2002 17:43:03 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 17z285-0008LJ-00
	for bug-commoncpp@gnu.org; Tue, 08 Oct 2002 17:43:02 -0400
Received: from pd950a04c.dip.t-dialin.net ([217.80.160.76] helo=test)
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 17z27v-0007ql-00
	for bug-commoncpp@gnu.org; Tue, 08 Oct 2002 17:42:52 -0400
Subject: typo: sigInstall with lowercase i in thread.cpp
Message-Id: <E17z27v-0007ql-00@monty-python.gnu.org>
From: test.nospam@t-online.de
Bcc: 
Date: Tue, 08 Oct 2002 17:42:52 -0400
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

thread.h:     friend void sigInstall(int signo);
/doc/man3/ost_PosixThread.3cc:.RI "void \fBsigInstall\fP (int signo)"
/doc/man3/ost_PosixThread.3cc:.SS "void sigInstall (int signo)\fC [friend]\fP"

typos in thread.cpp:

/src/thread.cpp:void siginstall(int);
/src/thread.cpp:               siginstall(SIGHUP);
/src/thread.cpp:               siginstall(SIGALRM);
/src/thread.cpp:               siginstall(SIGPIPE);
/src/thread.cpp:               siginstall(SIGABRT);
/src/thread.cpp:void siginstall(int signo)

regards

nospam




From tim@ba.be Fri Oct 18 15:48:38 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 182d6r-0007fl-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 15:48:37 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 182d6n-0007ew-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 15:48:36 -0400
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 182cS0-0002uW-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 15:06:24 -0400
Received: from [194.78.235.202] (helo=central.ba.be)
	by gnudist.gnu.org with smtp (Exim 4.10)
	id 181pib-0004Pz-00
	for bug-commoncpp@gnu.org; Wed, 16 Oct 2002 11:04:18 -0400
Received: (qmail 4977 invoked by uid 511); 16 Oct 2002 15:02:34 -0000
Received: from tim@ba.be by central.ba.be
	 by uid 506 with qmail-scanner-1.10 (uvscan: v4.1.40/v4191. . Clear:0. Processed in 0.125043 secs); 16 Oct 2002 15:02:34 -0000
Received: from unknown (HELO 10.0.1.202) (10.0.1.202)
  by central.ba.be with SMTP; 16 Oct 2002 15:02:33 -0000
From: Tim Esselens <tim@ba.be>
Organization: Better Access
To: bug-commoncpp@gnu.org
Subject: question about Common C++ 2 serial class
Date: Wed, 16 Oct 2002 17:02:43 +0200
User-Agent: KMail/1.4.7
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Message-Id: <200210161702.43728.tim@ba.be>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hi,

I've been using your serial class for a HA (high availability) project. I've 
managed to get 2 machines to ping eachother over serial line. But there is a 
rather big problem coming up. If I flush (this->flush()) my object 
(SerialBeat: public TTYSession) the thread blocks, flushOutput() doesn't seem 
to be flushing at all.

So, the problem I'm having is quite simple, how to flush in a nonblocking kind 
of mode, so after n msecs of 'unflushability' it could start throwing errors.
I only hope the answer is as easy as the question.

If this is not possible for some reason, is there a way around this (still 
using your serial class ofcourse)? I need to detect the other side is down, 
that's really it (maybe something the serial protocol allready includes, but 
I'm new to serial lines, so I wouldn't know).

kind regards,
Tim Esselens

ps: NEWS stated sending questions to dyfet, README to bug-commoncpp, I did 
both <g>



From tim@ba.be Fri Oct 18 21:50:55 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 182ilT-0001Gn-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 21:50:55 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 182ilQ-0001Fo-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 21:50:53 -0400
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 182cMf-0001tj-00
	for bug-commoncpp@gnu.org; Fri, 18 Oct 2002 15:00:53 -0400
Received: from [194.78.235.202] (helo=central.ba.be)
	by gnudist.gnu.org with smtp (Exim 4.10)
	id 181q88-0006NN-00
	for bug-commoncpp@gnu.org; Wed, 16 Oct 2002 11:30:40 -0400
Received: (qmail 5791 invoked by uid 511); 16 Oct 2002 15:30:28 -0000
Received: from tim@ba.be by central.ba.be
	 by uid 506 with qmail-scanner-1.10 (uvscan: v4.1.40/v4191. . Clear:0. Processed in 0.124215 secs); 16 Oct 2002 15:30:28 -0000
Received: from unknown (HELO 10.0.1.202) (10.0.1.202)
  by central.ba.be with SMTP; 16 Oct 2002 15:30:28 -0000
From: Tim Esselens <tim@ba.be>
Organization: Better Access
To: bug-commoncpp@gnu.org
Subject: Re: question about Common C++ 2 serial class
Date: Wed, 16 Oct 2002 17:30:38 +0200
User-Agent: KMail/1.4.7
References: <200210161702.43728.tim@ba.be>
In-Reply-To: <200210161702.43728.tim@ba.be>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Message-Id: <200210161730.38591.tim@ba.be>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

> So, the problem I'm having is quite simple, how to flush in a nonblocking
> kind of mode, so after n msecs of 'unflushability' it could start throwing
> errors. I only hope the answer is as easy as the question.
and of course, it is! :)

aRead and aWrite seem to be doing just te things I needed,
nevertheless I would like to see something I described in my prior mail, so 
consider it a 'ah, he used it this way' report :)

I would also like to say you guys do a great job, I've worked with your lib 
before (needed threading) and it just couldn't get any better, my new project 
included just one thing not in your old lib, serial connections. Since that 
is coded now, I think your lib will be one of my most used ones.
So, thanks again, keep up the good work!

kind regards,
Tim Esselens



From ozaki@blueyonder.co.uk Sun Oct 20 07:10:43 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 183Dyl-0002ws-00
	for bug-commoncpp@gnu.org; Sun, 20 Oct 2002 07:10:43 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 183Dyj-0002wL-00
	for bug-commoncpp@gnu.org; Sun, 20 Oct 2002 07:10:42 -0400
Received: from pcow035o.blueyonder.co.uk ([195.188.53.121] helo=blueyonder.co.uk)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 183Dyj-0002w8-00
	for bug-commoncpp@gnu.org; Sun, 20 Oct 2002 07:10:41 -0400
Received: from pcow035o.blueyonder.co.uk ([127.0.0.1]) by blueyonder.co.uk  with Microsoft SMTPSVC(5.5.1877.757.75);
	 Sun, 20 Oct 2002 12:10:40 +0100
Received: from Gateway (unverified [80.194.109.2]) by pcow035o.blueyonder.co.uk
 (Content Technologies SMTPRS 4.2.9) with SMTP id <T5e0e1f07fbac1785ed21a@pcow035o.blueyonder.co.uk> for <bug-commoncpp@gnu.org>;
 Sun, 20 Oct 2002 12:10:40 +0100
From: <ozaki@blueyonder.co.uk>
To: <bug-commoncpp@gnu.org>
Subject: CommonC++-1.9.7 - win32
Date: Sun, 20 Oct 2002 12:10:33 +0100
Message-ID: <000201c27829$4fb41770$026dc250@Gateway>
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 CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hi,

I am trying to build the win32 lib (e.g ccgnu3D.dll and  ccgnu3.dll). While
building CCXX project I am getting 8 errors (and some warnings).

One of the error is:

C:\CommonC++-1.9.7\src\url.h(47) : fatal error C1083: Cannot open include
file: 'net/if.h': No such file or directory

This because the following line in url.cpp:

#include <net/if.h>


Any suggestions.


Thanks
O.Zaki






From anand_narwani@yahoo.com Sun Oct 20 22:53:32 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 183Sh9-0003ON-00
	for bug-commoncpp@gnu.org; Sun, 20 Oct 2002 22:53:31 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 183Sh8-0003O4-00
	for bug-commoncpp@gnu.org; Sun, 20 Oct 2002 22:53:31 -0400
Received: from web12307.mail.yahoo.com ([216.136.173.105])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 183Sh7-0003Lz-00
	for bug-commoncpp@gnu.org; Sun, 20 Oct 2002 22:53:29 -0400
Message-ID: <20021021025328.4576.qmail@web12307.mail.yahoo.com>
Received: from [24.93.64.110] by web12307.mail.yahoo.com via HTTP; Sun, 20 Oct 2002 19:53:28 PDT
Date: Sun, 20 Oct 2002 19:53:28 -0700 (PDT)
From: Anand Narwani <anand_narwani@yahoo.com>
Subject: Help with Timers on Solaris
To: bug-commoncpp@gnu.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hello folks,
I am attmepting to do something that seems to be
reasonably simple but I cannot seem to make it work. 
Here is my configuration:
- Solaris 2.8
- Common C++2 1.03
- g++ 2.95.2

Essentially I am attempting to implement a Posix
Thread which goes to sleep for a specified period,
gets woken up, does some work and then goes back to
sleep.  Please take a look at the source at:

http://www.employees.org/~anarwani/thread-test.html

I have 2 problems:
1. My derived onTimer() routine never gets called when
the timer expires.
2.  I am unable to use the delete operator to force my
main thread to join with my thread.  it simply exits
the program.  I have since worked around the problem
using a semaphore.

I have tested this program on Linux and it works
correctly.  I suspect that the pthreads implementation
differences between the two operating systems are the
reason for the failure on Solaris, but I have no idea
how to fix this. Any assistance is very much
appreciated.

Regards,
Anand

__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/



From chad_pettit@xontech.com Mon Oct 21 09:19:43 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 183cT9-0005uz-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 09:19:43 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 183cT0-0005iJ-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 09:19:42 -0400
Received: from filter.xontech.com ([216.180.56.2])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 183cT0-0005gP-00
	for bug-commoncpp@gnu.org; Mon, 21 Oct 2002 09:19:34 -0400
Received: from xontech.com (host31.xontech.com [216.180.56.31])
	by filter.xontech.com (8.11.6/8.11.2) with ESMTP id g9LDJA217931
	for <bug-commoncpp@gnu.org>; Mon, 21 Oct 2002 08:19:10 -0500
Message-ID: <3DB3FEB8.4060605@xontech.com>
Date: Mon, 21 Oct 2002 09:18:48 -0400
From: Chad Pettit <chad_pettit@xontech.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
Subject: Deleting a non-autofree thread
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner: Found to be clean
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

What is the proper way to delete a non-autofree thread?  I have tried 
several combo's with endStream(), terminate(), endSocket() and others 
and nothing appears to be working.  I get an out of resource error when 
I would try to allocate another thread.  I am using TCSession.




From netvirtuose@hotmail.com Tue Oct 22 19:06:03 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 184867-0000LC-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 19:06:03 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 184865-0000Ks-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 19:06:02 -0400
Received: from f111.law10.hotmail.com ([64.4.15.111] helo=hotmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 184865-0000Kk-00
	for bug-commoncpp@gnu.org; Tue, 22 Oct 2002 19:06:01 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 22 Oct 2002 16:05:59 -0700
Received: from 81.48.180.141 by lw10fd.law10.hotmail.msn.com with HTTP;
	Tue, 22 Oct 2002 23:05:59 GMT
X-Originating-IP: [81.48.180.141]
From: "Thai D." <netvirtuose@hotmail.com>
To: bug-commoncpp@gnu.org
Bcc: 
Subject: how to compile under windows ?
Date: Wed, 23 Oct 2002 01:05:59 +0200
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Message-ID: <F111kTO0sLgZCWEYpIV0000cfd2@hotmail.com>
X-OriginalArrivalTime: 22 Oct 2002 23:05:59.0875 (UTC) FILETIME=[95FCE930:01C27A1F]
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

hi

I would like to know if there are good examples to show how to link the 
Common C++ lib to the windows executable.
In fact, I use Mingw under linux to cross compile to windows target.

Cheers
Thai









_________________________________________________________________
MSN Search, le moteur de recherche qui pense comme vous ! 
http://search.msn.fr/worldwide.asp




From fedemp@wanadoo.es Sun Oct 27 07:49:25 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 185mr7-00079E-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 07:49:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 185mr4-00078p-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 07:49:24 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 185mr3-00078k-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 07:49:22 -0500
Received: from risitas (62-37-140-83.dialup.uni2.es [62.37.140.83])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g9RClJX14377;
	Sun, 27 Oct 2002 13:47:19 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 185mun-0000BC-00; Sun, 27 Oct 2002 13:53:13 +0100
Date: Sun, 27 Oct 2002 13:53:12 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: ozaki@blueyonder.co.uk
Cc: bug-commoncpp@gnu.org
Subject: Re: CommonC++-1.9.7 - win32
Message-ID: <20021027125312.GA666@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: ozaki@blueyonder.co.uk, bug-commoncpp@gnu.org
References: <000201c27829$4fb41770$026dc250@Gateway>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000201c27829$4fb41770$026dc250@Gateway>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Hi, cc++ 1.9.7 is rather old, I would suggest you to upgrade
to cc++ 2. The last release is 1.0.5, which should compile and work
cleanly. It also includes workspaces for demo and test apps.

On Sun, Oct 20, 2002 at 12:10:33PM +0100, ozaki@blueyonder.co.uk wrote:
> Hi,
> 
> I am trying to build the win32 lib (e.g ccgnu3D.dll and  ccgnu3.dll). While
> building CCXX project I am getting 8 errors (and some warnings).
> 
> One of the error is:
> 
> C:\CommonC++-1.9.7\src\url.h(47) : fatal error C1083: Cannot open include
> file: 'net/if.h': No such file or directory
> 
> This because the following line in url.cpp:
> 
> #include <net/if.h>
> 
> 
> Any suggestions.
> 
> 
> Thanks
> O.Zaki
> 
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fedemp@wanadoo.es Sun Oct 27 07:53:26 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 185mv0-0002ws-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 07:53:26 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 185mux-0002wW-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 07:53:25 -0500
Received: from [62.37.236.139] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 185mux-0002wS-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 07:53:23 -0500
Received: from risitas (62-37-140-83.dialup.uni2.es [62.37.140.83])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gBCFkit21336;
	Thu, 12 Dec 2002 16:46:44 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 185myf-0000BQ-00; Sun, 27 Oct 2002 13:57:13 +0100
Date: Sun, 27 Oct 2002 13:57:12 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Thai D." <netvirtuose@hotmail.com>
Cc: bug-commoncpp@gnu.org
Subject: Re: how to compile under windows ?
Message-ID: <20021027125712.GB666@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: "Thai D." <netvirtuose@hotmail.com>,
	bug-commoncpp@gnu.org
References: <F111kTO0sLgZCWEYpIV0000cfd2@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F111kTO0sLgZCWEYpIV0000cfd2@hotmail.com>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	It may depend on how Mingw is configured on your system. Are
you using the .debs? Nevertheless, the CC++ 2 Makefile.gcc provides a
good example with the rules for ccext2.dll. You can also take a look
at the mingw32 makefiles of GNU ccaudio and GNU ccrtp.

On Wed, Oct 23, 2002 at 01:05:59AM +0200, Thai D. wrote:
> hi
> 
> I would like to know if there are good examples to show how to link the 
> Common C++ lib to the windows executable.
> In fact, I use Mingw under linux to cross compile to windows target.
> 
> Cheers
> Thai
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _________________________________________________________________
> MSN Search, le moteur de recherche qui pense comme vous ! 
> http://search.msn.fr/worldwide.asp
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fedemp@wanadoo.es Sun Oct 27 08:26:14 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 185nQk-0006pU-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 08:26:14 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 185nQh-0006oY-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 08:26:13 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 185nQh-0006oQ-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 08:26:11 -0500
Received: from risitas (62-37-140-83.dialup.uni2.es [62.37.140.83])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g9RDO9X23857;
	Sun, 27 Oct 2002 14:24:09 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 185nUR-00021d-00; Sun, 27 Oct 2002 14:30:03 +0100
Date: Sun, 27 Oct 2002 14:30:03 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: test.nospam@t-online.de
Cc: bug-commoncpp@gnu.org
Subject: Re: typo: sigInstall with lowercase i in thread.cpp
Message-ID: <20021027133003.GC666@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: test.nospam@t-online.de, bug-commoncpp@gnu.org
References: <E17z27v-0007ql-00@monty-python.gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E17z27v-0007ql-00@monty-python.gnu.org>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Ok, fixed in cvs for both 1.0.x and 1.1.x, thanks for the
report.

On Tue, Oct 08, 2002 at 05:42:52PM -0400, test.nospam@t-online.de wrote:
> thread.h:     friend void sigInstall(int signo);
> /doc/man3/ost_PosixThread.3cc:.RI "void \fBsigInstall\fP (int signo)"
> /doc/man3/ost_PosixThread.3cc:.SS "void sigInstall (int signo)\fC [friend]\fP"
> 
> typos in thread.cpp:
> 
> /src/thread.cpp:void siginstall(int);
> /src/thread.cpp:               siginstall(SIGHUP);
> /src/thread.cpp:               siginstall(SIGALRM);
> /src/thread.cpp:               siginstall(SIGPIPE);
> /src/thread.cpp:               siginstall(SIGABRT);
> /src/thread.cpp:void siginstall(int signo)
> 
> regards
> 
> nospam
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Sun Oct 27 08:26:43 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 185nRC-0007nX-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 08:26:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 185nR7-0007Yc-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 08:26:41 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 185nR6-0007Vj-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 08:26:37 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id g9RDnjO23369;
	Sun, 27 Oct 2002 08:49:45 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sun, 27 Oct 2002 08:49:45 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: "Thai D." <netvirtuose@hotmail.com>
cc: bug-commoncpp@gnu.org
Subject: Re: how to compile under windows ?
In-Reply-To: <F111kTO0sLgZCWEYpIV0000cfd2@hotmail.com>
Message-ID: <Pine.LNX.4.44.0210270848340.23364-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Common C++ has a win32 directory that includes a Makefile.gcc.  Just use
make -f Makefile.gcc from a Debian system with the mingw32 cross-compile 
package, and it will produce dll's for use with win32 systems.  There is 
also a Visual Studio project file in the distribution.

On Wed, 23 Oct 2002, Thai D. wrote:

> hi
> 
> I would like to know if there are good examples to show how to link the 
> Common C++ lib to the windows executable.
> In fact, I use Mingw under linux to cross compile to windows target.
> 
> Cheers
> Thai
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _________________________________________________________________
> MSN Search, le moteur de recherche qui pense comme vous ! 
> http://search.msn.fr/worldwide.asp
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From dyfet@ostel.com Sun Oct 27 08:30:13 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 185nUa-0004pc-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 08:30:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 185nUX-0004iK-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 08:30:12 -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)
	id 185nUW-0004fV-00
	for bug-commoncpp@gnu.org; Sun, 27 Oct 2002 08:30:08 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id g9RDrHI23478;
	Sun, 27 Oct 2002 08:53:17 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sun, 27 Oct 2002 08:53:17 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Anand Narwani <anand_narwani@yahoo.com>
cc: bug-commoncpp@gnu.org
Subject: Re: Help with Timers on Solaris
In-Reply-To: <20021021025328.4576.qmail@web12307.mail.yahoo.com>
Message-ID: <Pine.LNX.4.44.0210270851330.23452-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

The behavior of signals in threaded applications is different between 
Linux and Solaris.  The onTimer handler and other signal related handlers 
are non-portable and are meant only to be used on platforms that have 
useful properties.  You might want to use a conditional object or 
something similar to sleep for a specified period of time or until woken, 
or to create a seperate timer management thread.


On Sun, 20 Oct 2002, Anand Narwani wrote:

> Hello folks,
> I am attmepting to do something that seems to be
> reasonably simple but I cannot seem to make it work. 
> Here is my configuration:
> - Solaris 2.8
> - Common C++2 1.03
> - g++ 2.95.2
> 
> Essentially I am attempting to implement a Posix
> Thread which goes to sleep for a specified period,
> gets woken up, does some work and then goes back to
> sleep.  Please take a look at the source at:
> 
> http://www.employees.org/~anarwani/thread-test.html
> 
> I have 2 problems:
> 1. My derived onTimer() routine never gets called when
> the timer expires.
> 2.  I am unable to use the delete operator to force my
> main thread to join with my thread.  it simply exits
> the program.  I have since worked around the problem
> using a semaphore.
> 
> I have tested this program on Linux and it works
> correctly.  I suspect that the pthreads implementation
> differences between the two operating systems are the
> reason for the failure on Solaris, but I have no idea
> how to fix this. Any assistance is very much
> appreciated.
> 
> Regards,
> Anand
> 
> __________________________________________________
> Do you Yahoo!?
> Y! Web Hosting - Let the expert host your web site
> http://webhosting.yahoo.com/
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From anand_narwani@yahoo.com Mon Oct 28 09:12:31 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 186Ad4-0007Bb-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 09:12:30 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 186Acz-00070I-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 09:12:30 -0500
Received: from web12305.mail.yahoo.com ([216.136.173.103])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 186Acy-0006xy-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 09:12:25 -0500
Message-ID: <20021028141224.55404.qmail@web12305.mail.yahoo.com>
Received: from [24.93.64.110] by web12305.mail.yahoo.com via HTTP; Mon, 28 Oct 2002 06:12:24 PST
Date: Mon, 28 Oct 2002 06:12:24 -0800 (PST)
From: Anand Narwani <anand_narwani@yahoo.com>
Subject: Re: Help with Timers on Solaris
To: bug-commoncpp@gnu.org
In-Reply-To: <Pine.LNX.4.44.0210270851330.23452-100000@home.sys>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hi David,
Thanks for the info...  I finally decided to implement
it using an Event object, but I'm still having lots of
trouble with that (please see my other posing Re:
Solaris 8 and pthread issues. ).

thanks again,
Anand
--- David Sugar <dyfet@ostel.com> wrote:
> 
> The behavior of signals in threaded applications is
> different between 
> Linux and Solaris.  The onTimer handler and other
> signal related handlers 
> are non-portable and are meant only to be used on
> platforms that have 
> useful properties.  You might want to use a
> conditional object or 
> something similar to sleep for a specified period of
> time or until woken, 
> or to create a seperate timer management thread.
> 
> 
> On Sun, 20 Oct 2002, Anand Narwani wrote:
> 
> > Hello folks,
> > I am attmepting to do something that seems to be
> > reasonably simple but I cannot seem to make it
> work. 
> > Here is my configuration:
> > - Solaris 2.8
> > - Common C++2 1.03
> > - g++ 2.95.2
> > 
> > Essentially I am attempting to implement a Posix
> > Thread which goes to sleep for a specified period,
> > gets woken up, does some work and then goes back
> to
> > sleep.  Please take a look at the source at:
> > 
> >
> http://www.employees.org/~anarwani/thread-test.html
> > 
> > I have 2 problems:
> > 1. My derived onTimer() routine never gets called
> when
> > the timer expires.
> > 2.  I am unable to use the delete operator to
> force my
> > main thread to join with my thread.  it simply
> exits
> > the program.  I have since worked around the
> problem
> > using a semaphore.
> > 
> > I have tested this program on Linux and it works
> > correctly.  I suspect that the pthreads
> implementation
> > differences between the two operating systems are
> the
> > reason for the failure on Solaris, but I have no
> idea
> > how to fix this. Any assistance is very much
> > appreciated.
> > 
> > Regards,
> > Anand
> > 
> > __________________________________________________
> > Do you Yahoo!?
> > Y! Web Hosting - Let the expert host your web site
> > http://webhosting.yahoo.com/
> > 
> > 
> > _______________________________________________
> > 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




__________________________________________________
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute



From anand_narwani@yahoo.com Mon Oct 28 09:27:49 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 186Art-0001JK-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 09:27:49 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 186Aro-0001Fy-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 09:27:48 -0500
Received: from web12308.mail.yahoo.com ([216.136.173.106])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 186Arn-0001DV-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 09:27:43 -0500
Message-ID: <20021028142742.13292.qmail@web12308.mail.yahoo.com>
Received: from [24.93.64.110] by web12308.mail.yahoo.com via HTTP; Mon, 28 Oct 2002 06:27:42 PST
Date: Mon, 28 Oct 2002 06:27:42 -0800 (PST)
From: Anand Narwani <anand_narwani@yahoo.com>
Subject: Re: Help with Timers on Solaris
To: bug-commoncpp@gnu.org
In-Reply-To: <Pine.LNX.4.44.0210270851330.23452-100000@home.sys>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hi David,
Thanks for the info...  I finally decided to implement
it using an Event object, but I'm still having lots of
trouble with that (please see my other posing Re:
Solaris 8 and pthread issues. ).

thanks again,
Anand
--- David Sugar <dyfet@ostel.com> wrote:
> 
> The behavior of signals in threaded applications is
> different between 
> Linux and Solaris.  The onTimer handler and other
> signal related handlers 
> are non-portable and are meant only to be used on
> platforms that have 
> useful properties.  You might want to use a
> conditional object or 
> something similar to sleep for a specified period of
> time or until woken, 
> or to create a seperate timer management thread.
> 
> 
> On Sun, 20 Oct 2002, Anand Narwani wrote:
> 
> > Hello folks,
> > I am attmepting to do something that seems to be
> > reasonably simple but I cannot seem to make it
> work. 
> > Here is my configuration:
> > - Solaris 2.8
> > - Common C++2 1.03
> > - g++ 2.95.2
> > 
> > Essentially I am attempting to implement a Posix
> > Thread which goes to sleep for a specified period,
> > gets woken up, does some work and then goes back
> to
> > sleep.  Please take a look at the source at:
> > 
> >
> http://www.employees.org/~anarwani/thread-test.html
> > 
> > I have 2 problems:
> > 1. My derived onTimer() routine never gets called
> when
> > the timer expires.
> > 2.  I am unable to use the delete operator to
> force my
> > main thread to join with my thread.  it simply
> exits
> > the program.  I have since worked around the
> problem
> > using a semaphore.
> > 
> > I have tested this program on Linux and it works
> > correctly.  I suspect that the pthreads
> implementation
> > differences between the two operating systems are
> the
> > reason for the failure on Solaris, but I have no
> idea
> > how to fix this. Any assistance is very much
> > appreciated.
> > 
> > Regards,
> > Anand
> > 
> > __________________________________________________
> > Do you Yahoo!?
> > Y! Web Hosting - Let the expert host your web site
> > http://webhosting.yahoo.com/
> > 
> > 
> > _______________________________________________
> > 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




__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/



From anand_narwani@yahoo.com Mon Oct 28 09:31:13 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 186AvB-0006rf-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 09:31:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 186Av5-0006c6-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 09:31:12 -0500
Received: from web12308.mail.yahoo.com ([216.136.173.106])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 186Av4-0006ZZ-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 09:31:06 -0500
Message-ID: <20021028143106.14132.qmail@web12308.mail.yahoo.com>
Received: from [24.93.64.110] by web12308.mail.yahoo.com via HTTP; Mon, 28 Oct 2002 06:31:06 PST
Date: Mon, 28 Oct 2002 06:31:06 -0800 (PST)
From: Anand Narwani <anand_narwani@yahoo.com>
Subject: Re: Solaris 8 and pthread issues.
To: Federico Montesino Pouzols <fedemp@altern.org>
Cc: bug-commoncpp@gnu.org
In-Reply-To: <20021026193725.GC9569@risitas>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hi Fredrico,
I ran some tests and added cout's to event.cpp it
appears that the calls to get blocked in
pthread_cond_wait* calls.  I will attempt to re-run
those tests and I'll send you the output.

Thanks,
Anand
--- Federico Montesino Pouzols <fedemp@altern.org>
wrote:
> 
> 	I have just tried this on a Debian GNU/Linux box
> and it worked
> well, so as you suggest it is probably a platform
> specific issue. Any
> other details about what happens on your platform
> when you run this
> program? Could you confirm if it gets blocked in the
> pthread_... system call?
> 
> On Fri, Oct 25, 2002 at 12:41:01PM -0700, Anand
> Narwani wrote:
> > Hello Folks,
> > I am attempting to write a simple program using
> Common
> > C++2 1.0.3 on Solaris 8.  Here is the code:
> > 
> > /**** Code Starts Here ****/
> > /***** Code Ends Here ****/
> > 
> > I've attempted to run this with GCC 2.95.2 and
> also
> > GCC 3.2 both seem to have the same results: 
> > Event::wait() never returns when I do a
> > Event::signal().  If I test with
> Event::wait(timeout),
> > it never times out.  
> > I've looked at the source for the Event Class and
> I
> > can see the call to pthread_cond_wait() or
> > pthread_cond_waittimeout().  When these are
> called,
> > neither one returns.  I've searched and searched
> the
> > newsgroups and the web.  The only issue I've found
> is
> > that Solaris *might* have a problem with recursive
> > mutexes.  Has anyone experienced problems like
> this? 
> > Am I missing something silly?
> > 
> > Thanks in advance,
> > Anand
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/



From anand_narwani@yahoo.com Mon Oct 28 17:38:02 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 186IWI-0003cQ-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 17:38:02 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 186IWG-0003c3-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 17:38:01 -0500
Received: from web12305.mail.yahoo.com ([216.136.173.103])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 186IWG-0003bs-00
	for bug-commoncpp@gnu.org; Mon, 28 Oct 2002 17:38:00 -0500
Message-ID: <20021028223758.94380.qmail@web12305.mail.yahoo.com>
Received: from [24.93.64.110] by web12305.mail.yahoo.com via HTTP; Mon, 28 Oct 2002 14:37:58 PST
Date: Mon, 28 Oct 2002 14:37:58 -0800 (PST)
From: Anand Narwani <anand_narwani@yahoo.com>
Subject: Re: Solaris 8 and pthread issues. [ Resolved ]
To: bug-commoncpp@gnu.org
In-Reply-To: <20021028143106.14132.qmail@web12308.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Folks,
After trying several things, I finally threw in the
towel and upgraded the OS to Solaris 9.  This fixed
the problem.  So my question is:  Does anyone know
what Solaris 8 Patch might have the same effect?

Thanks,
Anand
--- Anand Narwani <anand_narwani@yahoo.com> wrote:
> Hi Fredrico,
> I ran some tests and added cout's to event.cpp it
> appears that the calls to get blocked in
> pthread_cond_wait* calls.  I will attempt to re-run
> those tests and I'll send you the output.
> 
> Thanks,
> Anand
> --- Federico Montesino Pouzols <fedemp@altern.org>
> wrote:
> > 
> > 	I have just tried this on a Debian GNU/Linux box
> > and it worked
> > well, so as you suggest it is probably a platform
> > specific issue. Any
> > other details about what happens on your platform
> > when you run this
> > program? Could you confirm if it gets blocked in
> the
> > pthread_... system call?
> > 
> > On Fri, Oct 25, 2002 at 12:41:01PM -0700, Anand
> > Narwani wrote:
> > > Hello Folks,
> > > I am attempting to write a simple program using
> > Common
> > > C++2 1.0.3 on Solaris 8.  Here is the code:
> > > 
> > > /**** Code Starts Here ****/
> > > /***** Code Ends Here ****/
> > > 
> > > I've attempted to run this with GCC 2.95.2 and
> > also
> > > GCC 3.2 both seem to have the same results: 
> > > Event::wait() never returns when I do a
> > > Event::signal().  If I test with
> > Event::wait(timeout),
> > > it never times out.  
> > > I've looked at the source for the Event Class
> and
> > I
> > > can see the call to pthread_cond_wait() or
> > > pthread_cond_waittimeout().  When these are
> > called,
> > > neither one returns.  I've searched and searched
> > the
> > > newsgroups and the web.  The only issue I've
> found
> > is
> > > that Solaris *might* have a problem with
> recursive
> > > mutexes.  Has anyone experienced problems like
> > this? 
> > > Am I missing something silly?
> > > 
> > > Thanks in advance,
> > > Anand
> > 
> > 
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Y! Web Hosting - Let the expert host your web site
> http://webhosting.yahoo.com/
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


__________________________________________________
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute



From anand_narwani@yahoo.com Tue Oct 29 13:18:13 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 186awO-0000Hj-00
	for bug-commoncpp@gnu.org; Tue, 29 Oct 2002 13:18:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 186awJ-0000Gy-00
	for bug-commoncpp@gnu.org; Tue, 29 Oct 2002 13:18:12 -0500
Received: from web12304.mail.yahoo.com ([216.136.173.102])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 186aoQ-0006Ov-00
	for bug-commoncpp@gnu.org; Tue, 29 Oct 2002 13:09:58 -0500
Message-ID: <20021029180951.6008.qmail@web12304.mail.yahoo.com>
Received: from [64.102.253.213] by web12304.mail.yahoo.com via HTTP; Tue, 29 Oct 2002 10:09:51 PST
Date: Tue, 29 Oct 2002 10:09:51 -0800 (PST)
From: Anand Narwani <anand_narwani@yahoo.com>
Subject: Re: Solaris 8 and pthread issues. [ Resolved ]
To: bug-commoncpp@gnu.org
In-Reply-To: <20021028223758.94380.qmail@web12305.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Folks,
After some testing I have found the patch required to
fix this problem on Solaris 8.  The following patches
need to be installed (order is important):
112396
108987
111111
111293
111310
108528
108527

Here's the info on the patch that finally fixed it:

Patch-ID# 108827-30 
Keywords: security libthread malloc libc libnsl
libthread_db lipthread POSIX 
Synopsis: SunOS 5.8: /usr/lib/libthread.so.1 patch 
Date: Sep/06/2002 

Anand
--- Anand Narwani <anand_narwani@yahoo.com> wrote:
> Folks,
> After trying several things, I finally threw in the
> towel and upgraded the OS to Solaris 9.  This fixed
> the problem.  So my question is:  Does anyone know
> what Solaris 8 Patch might have the same effect?
> 
> Thanks,
> Anand
> --- Anand Narwani <anand_narwani@yahoo.com> wrote:
> > Hi Fredrico,
> > I ran some tests and added cout's to event.cpp it
> > appears that the calls to get blocked in
> > pthread_cond_wait* calls.  I will attempt to
> re-run
> > those tests and I'll send you the output.
> > 
> > Thanks,
> > Anand
> > --- Federico Montesino Pouzols <fedemp@altern.org>
> > wrote:
> > > 
> > > 	I have just tried this on a Debian GNU/Linux
> box
> > > and it worked
> > > well, so as you suggest it is probably a
> platform
> > > specific issue. Any
> > > other details about what happens on your
> platform
> > > when you run this
> > > program? Could you confirm if it gets blocked in
> > the
> > > pthread_... system call?
> > > 
> > > On Fri, Oct 25, 2002 at 12:41:01PM -0700, Anand
> > > Narwani wrote:
> > > > Hello Folks,
> > > > I am attempting to write a simple program
> using
> > > Common
> > > > C++2 1.0.3 on Solaris 8.  Here is the code:
> > > > 
> > > > /**** Code Starts Here ****/
> > > > /***** Code Ends Here ****/
> > > > 
> > > > I've attempted to run this with GCC 2.95.2 and
> > > also
> > > > GCC 3.2 both seem to have the same results: 
> > > > Event::wait() never returns when I do a
> > > > Event::signal().  If I test with
> > > Event::wait(timeout),
> > > > it never times out.  
> > > > I've looked at the source for the Event Class
> > and
> > > I
> > > > can see the call to pthread_cond_wait() or
> > > > pthread_cond_waittimeout().  When these are
> > > called,
> > > > neither one returns.  I've searched and
> searched
> > > the
> > > > newsgroups and the web.  The only issue I've
> > found
> > > is
> > > > that Solaris *might* have a problem with
> > recursive
> > > > mutexes.  Has anyone experienced problems like
> > > this? 
> > > > Am I missing something silly?
> > > > 
> > > > Thanks in advance,
> > > > Anand
> > > 
> > > 
> > > _______________________________________________
> > > Bug-commoncpp mailing list
> > > Bug-commoncpp@gnu.org
> > >
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > 
> > 
> > 
> > __________________________________________________
> > Do you Yahoo!?
> > Y! Web Hosting - Let the expert host your web site
> > http://webhosting.yahoo.com/
> > 
> > 
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 
> 
> __________________________________________________
> Yahoo! - We Remember
> 9-11: A tribute to the more than 3,000 lives lost
> http://dir.remember.yahoo.com/tribute
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/



From akantor@uiuc.edu Wed Oct 30 19:23:18 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18737F-0007kz-00
	for bug-commoncpp@gnu.org; Wed, 30 Oct 2002 19:23:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18737C-0007eK-00
	for bug-commoncpp@gnu.org; Wed, 30 Oct 2002 19:23:16 -0500
Received: from express.cites.uiuc.edu ([128.174.5.156])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18737B-0007c1-00
	for bug-commoncpp@gnu.org; Wed, 30 Oct 2002 19:23:13 -0500
Received: from express.cites.uiuc.edu (localhost.cites.uiuc.edu [127.0.0.1])
	by express.cites.uiuc.edu (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ACK40103;
	Wed, 30 Oct 2002 18:23:11 -0600 (CST)
Message-Id: <200210310023.ACK40103@express.cites.uiuc.edu>
Received: from 128.174.240.242
	by express.cites.uiuc.edu (Mirapoint Messaging Server MOS 3.2.1-GA)
	with HTTPS/1.1;
	Wed, 30 Oct 2002 18:23:11 -0600
Date: Wed, 30 Oct 2002 18:23:11 -0600
From: Arthur Kantor <akantor@uiuc.edu>
Subject: process.cpp:204: implicit declaration of function `int ost::snprintf(...)'
To: bug-commoncpp@gnu.org
Reply-To: akantor@uiuc.edu
X-Mailer: Webmail Mirapoint Direct 3.2.1-GA
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>


compiling with 
gcc 2.95.3 
on 
SunOS csil-suna33.cs.uiuc.edu 5.8 Generic_108528-16 sun4u 
sparc SUNW,Sun-Blade-1000


the error:
c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -
DCCXX_EXPORT_LIBRARY -g -O2 -D_GNU_SOURCE -D_REENTRANT -
I/usr/dcs/software/supported/encap/libxml2-
2.4.21/include/libxml2 -I../include -c exception.cpp -o 
exception.o >/dev/null 2>&1
mv -f .libs/exception.lo exception.lo
/bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -
I. -I../include     -I../src -DCCXX_EXPORT_LIBRARY  -g -O2 -
D_GNU_SOURCE -D_REENTRANT  -
I/usr/dcs/software/supported/encap/libxml2-
2.4.21/include/libxml2 -I../include -c process.cpp
rm -f .libs/process.lo
c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -
DCCXX_EXPORT_LIBRARY -g -O2 -D_GNU_SOURCE -D_REENTRANT -
I/usr/dcs/software/supported/encap/libxml2-
2.4.21/include/libxml2 -I../include -c process.cpp  -fPIC -
DPIC -o .libs/process.lo
In file included from /usr/include/fcntl.h:18,
                 from ../include/cc++/config.h:343,
                 from process.cpp:41:
/usr/include/sys/feature_tests.h:143: warning: 
`_POSIX_PTHREAD_SEMANTICS' redefined
../include/cc++/config.h:305: warning: this is the location 
of the previous definition
process.cpp: In function `static void ost::Process::setEnv
(const char *, const char *, bool)':
process.cpp:204: implicit declaration of function `int 
ost::snprintf(...)'
*** Error code 1
make: Fatal error: Command failed for target `process.lo'
Current working 
directory /home/student/akantor/cs338/p2/commoncpp2-1.0.5/src
*** Error code 1
make: Fatal error: Command failed for target `all-recursive'


you probably want to 
#include <stdio.h>
when compiling for sun.

cheers,
-Arthur



From mmatus@dinha.acms.arizona.edu Wed Oct 30 20:03:16 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 1873jv-0001An-00
	for bug-commoncpp@gnu.org; Wed, 30 Oct 2002 20:03:15 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 1873jQ-00013L-00
	for bug-commoncpp@gnu.org; Wed, 30 Oct 2002 20:03:15 -0500
Received: from dinha.acms.arizona.edu ([128.196.89.193])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 1873jP-00013D-00
	for bug-commoncpp@gnu.org; Wed, 30 Oct 2002 20:02:44 -0500
Received: from acms.arizona.edu (lt01.acms.arizona.edu [128.196.89.233])
	by dinha.acms.arizona.edu (SGI-8.9.3/8.9.3) with ESMTP id SAA54541
	for <bug-commoncpp@gnu.org>; Wed, 30 Oct 2002 18:02:41 -0700 (MST)
Message-ID: <3DC07EF9.2000909@acms.arizona.edu>
Date: Wed, 30 Oct 2002 17:53:13 -0700
From: Marcelo Matus <mmatus@dinha.acms.arizona.edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
Subject: Compiling warnings (one error at least)
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

I just compile the commoncpp2-1.0.1 version and
I've got the following warnings:


****************

thread.cpp(303): warning #418: declaration requires a typedef name
  };
   ^

file.cpp(342): warning #592: variable "pos" is used before its value is set
      lseek(fd, pos, SEEK_SET);
                ^
serial.cpp(449): warning #858: type qualifier on return type is meaningless
  const int Serial::aRead(char *Data, const int Length)
            ^

serial.cpp(454): warning #858: type qualifier on return type is meaningless
  const int Serial::aWrite(const char *Data, const int Length)
            ^
engine.cpp(119): warning #186: pointless comparison of unsigned integer 
with zero
            if (myZStream.avail_out >= 0)
                                    ^
unix.cpp(468): warning #187: use of "=" where "==" may have been intended
           if( errno = EINPROGRESS )
               ^

************************

and at least the last one (unix.cpp) seems to be an error. Also, the 
warning for
the  file.cpp file seems to be important.


Marcelo




From cproch@seculogix.de Thu Oct 31 12:46:40 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187JOy-0003SX-00
	for bug-commoncpp@gnu.org; Thu, 31 Oct 2002 12:46:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187JOp-0003Iw-00
	for bug-commoncpp@gnu.org; Thu, 31 Oct 2002 12:46:38 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 187JOp-0003IM-00
	for bug-commoncpp@gnu.org; Thu, 31 Oct 2002 12:46:31 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP id C3CC613AD5
	for <bug-commoncpp@gnu.org>; Thu, 31 Oct 2002 18:43:58 +0100 (CET)
Content-Type: text/plain;
  charset="us-ascii"
From: "Prochnow, Christian" <cproch@seculogix.de>
Reply-To: cproch@seculogix.de
To: bug-commoncpp@gnu.org
Subject: Missing "connect" constructor in class SocketPort?
Date: Thu, 31 Oct 2002 18:46:28 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200210311846.28193.cproch@seculogix.de>
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hi,

i'm missing constructor in the SocketPort class for initiating an outboun=
d tcp=20
connection to a given host address and port.

it would be nice to include such a constructor into the SocketPort class.

Regards,
Christian Prochnow





From xiaowenwu3@yahoo.com Thu Oct 31 13:19:39 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187Jut-00045U-00
	for bug-commoncpp@gnu.org; Thu, 31 Oct 2002 13:19:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187Jul-00044M-00
	for bug-commoncpp@gnu.org; Thu, 31 Oct 2002 13:19:38 -0500
Received: from web40910.mail.yahoo.com ([66.218.78.207])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 187Jul-00043p-00
	for bug-commoncpp@gnu.org; Thu, 31 Oct 2002 13:19:31 -0500
Message-ID: <20021031181930.81445.qmail@web40910.mail.yahoo.com>
Received: from [208.185.161.233] by web40910.mail.yahoo.com via HTTP; Thu, 31 Oct 2002 10:19:30 PST
Date: Thu, 31 Oct 2002 10:19:30 -0800 (PST)
From: Xiaowen WU <xiaowenwu3@yahoo.com>
Subject: Compile Error in Visual C++ on Windows 2000
To: bug-commoncpp@gnu.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

Hi, 

I just downloaded the common C++, and tried to install
it on Windows. I got the following error when try to
generate the DLL. Are there anyway to work around
this. I'm using VC++ on Windows, common C++ 2 v1.0.3.

Thanks in advanced.

Xiaowen

-------------------Configuration: ccext2 - Win32
Debug--------------------
Compiling...
date.cpp
y:\collector\win32\commoncpp2-1.0.3\src\date.cpp(428)
: warning C4101: 'min' : unreferenced local variable
y:\collector\win32\commoncpp2-1.0.3\src\date.cpp(608)
: error C2436: '__ctor' : member function or nested
class in constructor initializer list
y:\collector\win32\commoncpp2-1.0.3\src\date.cpp(608)
: error C2436: '__ctor' : member function or nested
class in constructor initializer list
y:\collector\win32\commoncpp2-1.0.3\src\date.cpp(647)
: error C2436: '__ctor' : member function or nested
class in constructor initializer list
y:\collector\win32\commoncpp2-1.0.3\src\date.cpp(647)
: error C2436: '__ctor' : member function or nested
class in constructor initializer list
y:\collector\win32\commoncpp2-1.0.3\src\date.cpp(650)
: error C2436: '__ctor' : member function or nested
class in constructor initializer list
y:\collector\win32\commoncpp2-1.0.3\src\date.cpp(650)
: error C2436: '__ctor' : member function or nested
class in constructor initializer list
y:\collector\win32\commoncpp2-1.0.3\src\date.cpp(739)
: error C2039: 'strftime' : is not a member of 'std'
y:\collector\win32\commoncpp2-1.0.3\src\date.cpp(739)
: error C2660: 'strftime' : function does not take 4
parameters
xml.cpp
buffer.cpp
cmdoptns.cpp
digest.cpp
y:\collector\win32\commoncpp2-1.0.3\src\digest.cpp(61)
: warning C4355: 'this' : used in base member
initializer list
engine.cpp
fifo.cpp 

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/



