From ariston@cs.und.edu Fri Nov 01 02:39:29 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187WOT-00052i-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 02:39:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187WOM-0004zI-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 02:38:59 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 187WL9-0003vf-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 02:35:35 -0500
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gA17dbsY020685
	for <bug-commoncpp@gnu.org>; Fri, 1 Nov 2002 01:39:37 -0600
Date: Fri, 1 Nov 2002 01:36:22 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
To: <bug-commoncpp@gnu.org>
Subject: FreeBSD Problems
Message-ID: <Pine.GSO.4.33.0211010134020.20208-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 think I'm going to just sit down and try to figure out what's wrong with
CommonC++ (from cvs) on FreeBSD.  I keep figuring out a quick hack around
things, but they are things that should be fixed.  So here's #1:

friends.cpp: In function `static void ost::Thread::sleep(long unsigned int)':
friends.cpp:134: implicit declaration of function `int ost::nanosleep(...)'

Anyone with insight as to why this is occurring?
 -- Ari Johnson




From ariston@cs.und.edu Fri Nov 01 05:11:26 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187Yly-0005er-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 05:11:26 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187Ylv-0005do-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 05:11:25 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 187Ylu-0005b1-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 05:11:22 -0500
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gA1AFasY002983
	for <bug-commoncpp@gnu.org>; Fri, 1 Nov 2002 04:15:36 -0600
Date: Fri, 1 Nov 2002 04:12:19 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
To: <bug-commoncpp@gnu.org>
Subject: Suggestion regarding header files...
Message-ID: <Pine.GSO.4.33.0211010411090.20258-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 was just scratching my head after a reinstall, wondering why I all the
sudden couldn't use XMLStream, and then I realized that it was being
#ifdef'd out of the header because I forgot to install libxml2 before
building CommonC++.  Maybe an #error for the #ifndef in each header this
happens in would be helpful.  Thanks.
 -- Ari Johnson





From fedemp@wanadoo.es Fri Nov 01 17:08:07 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187jxX-0001Zq-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 17:08:07 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187jxT-0001YE-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 17:08:05 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 187jxR-0001Xg-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 17:08:02 -0500
Received: from risitas (62-36-176-152.dialup.uni2.es [62.36.176.152])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gA1M5dX06026
	for <bug-commoncpp@gnu.org>; Fri, 1 Nov 2002 23:05:39 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 187jyB-0000T0-00
	for <bug-commoncpp@gnu.org>; Fri, 01 Nov 2002 23:08:47 +0100
Date: Fri, 1 Nov 2002 23:08:46 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: [ Patch #623 ] ost::Conditional is broken with posix threads
Message-ID: <20021101220846.GA828@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 this patch needs to be commented on this
list. This patch does the lock/unlock of the mutex attached to the
condition variable inside the Conditional class. However, I think the
Conditional class is designed so that the user of the class is
responsible for calling enterMutex and leaveMutex as needed.

	In fact, if you call enterMutex like this patch proposes, the
user of Conditional would not be able to check for any condition
between enterMutex and pthread_cond_wait. Also, you would need to
incorporate the enter/leaveMutex around the signal/broadcast calls.

	Perhaps, a note should be added to the documentation of
Conditional stating that its user is responsible for calling
enterMutex and leaveMutex to avoid race conditions.

	Anders Blomgren wrote:

> ost::Conditional is totally broken on most systems with posix
> threads as it doesnt lock it's mutex before doing
> pthread_cond_wait().
>
>This patch is against 1.0.5
>
>--- commoncpp2-1.0.5/src/mutex.cpp      Thu May  9 01:18:30 2002
>+++ commoncpp2-1.0.5q/src/mutex.cpp     Fri Nov  1 05:51:38 2002
>@@ -148,11 +148,15 @@
>
>        if(!timeout)
>        {
>+               enterMutex();
>                pthread_cond_wait(&_cond, &_mutex);
>+               leaveMutex();
>                return;
>        }
>        getTimeout(&ts, timeout);
>+       enterMutex();
>        pthread_cond_timedwait(&_cond, &_mutex, &ts);
>



From fedemp@wanadoo.es Fri Nov 01 17:19:00 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187k83-00042C-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 17:18:59 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187k7z-000413-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 17:18:57 -0500
Received: from [62.37.236.138] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 187k7x-00040X-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 17:18:54 -0500
Received: from risitas (62-36-176-152.dialup.uni2.es [62.36.176.152])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gA1MGrx30492;
	Fri, 1 Nov 2002 23:16:56 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 187k8U-0000Tn-00; Fri, 01 Nov 2002 23:19:26 +0100
Date: Fri, 1 Nov 2002 23:19:26 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ari Johnson <ariston@cs.und.edu>
Cc: bug-commoncpp@gnu.org
Subject: Re: Suggestion regarding header files...
Message-ID: <20021101221926.GB828@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.0211010411090.20258-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.0211010411090.20258-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/>

	Well, cc++ is designed so that it can be compiled without xml
support (because you do not have libxml or because you specify
--without-xml to configure). I think that a #warning in xml.cpp
(implementation of all XML classes) saying "xml related classes are
not being compiled in Common C++ libraries" or something similar would
be good so as to avoid problems like the one you describe.

On Fri, Nov 01, 2002 at 04:12:19AM -0600, Ari Johnson wrote:
> 
> I was just scratching my head after a reinstall, wondering why I all the
> sudden couldn't use XMLStream, and then I realized that it was being
> #ifdef'd out of the header because I forgot to install libxml2 before
> building CommonC++.  Maybe an #error for the #ifndef in each header this
> happens in would be helpful.  Thanks.
>  -- Ari Johnson
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Fri Nov 01 17:55:58 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187khq-0003Kd-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 17:55:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187kho-0003KD-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 17:55:57 -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 187aN3-0002En-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 06:53:49 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gA1CHar02018;
	Fri, 1 Nov 2002 07:17:36 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Fri, 1 Nov 2002 07:17:36 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Ari Johnson <ariston@cs.und.edu>
cc: bug-commoncpp@gnu.org
Subject: Re: FreeBSD Problems
In-Reply-To: <Pine.GSO.4.33.0211010134020.20208-100000@agassiz.cs.und.edu>
Message-ID: <Pine.LNX.4.44.0211010716230.1997-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 would like to see us have a clean and consistent build under FreeBSD.  
Currently, there are two choices possible with it; one to build against
LinuxThreads, and one to do so with the native runtime thread library.  
Which do you think would be better for FreeBSD?

David

On Fri, 1 Nov 2002, Ari Johnson wrote:

> 
> I think I'm going to just sit down and try to figure out what's wrong with
> CommonC++ (from cvs) on FreeBSD.  I keep figuring out a quick hack around
> things, but they are things that should be fixed.  So here's #1:
> 
> friends.cpp: In function `static void ost::Thread::sleep(long unsigned int)':
> friends.cpp:134: implicit declaration of function `int ost::nanosleep(...)'
> 
> Anyone with insight as to why this is occurring?
>  -- Ari Johnson
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From ariston@cs.und.edu Fri Nov 01 20:38:33 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187nFA-0007Lq-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 20:38:32 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187nF5-0007KS-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 20:38:31 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 187nF3-0007Iw-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 20:38:25 -0500
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gA21glsY008211;
	Fri, 1 Nov 2002 19:42:48 -0600
Date: Fri, 1 Nov 2002 19:39:17 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: <bug-commoncpp@gnu.org>
Subject: Re: Suggestion regarding header files...
In-Reply-To: <20021101221926.GB828@risitas>
Message-ID: <Pine.GSO.4.33.0211011938110.21865-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/>

If you compiled without XML support, but you try to include cc++/xml.h,
you should be informed that you're trying to use a part of the library
that you didn't install.  I think that xml.h is a good place to put this,
and also that it should be an #error (just like trying to start a car
without an engine is an error and not something that can be ignored as a
warning).
 -- Ari Johnson

On Fri, 1 Nov 2002, Federico Montesino Pouzols wrote:

>
> 	Well, cc++ is designed so that it can be compiled without xml
> support (because you do not have libxml or because you specify
> --without-xml to configure). I think that a #warning in xml.cpp
> (implementation of all XML classes) saying "xml related classes are
> not being compiled in Common C++ libraries" or something similar would
> be good so as to avoid problems like the one you describe.
>
> On Fri, Nov 01, 2002 at 04:12:19AM -0600, Ari Johnson wrote:
> >
> > I was just scratching my head after a reinstall, wondering why I all the
> > sudden couldn't use XMLStream, and then I realized that it was being
> > #ifdef'd out of the header because I forgot to install libxml2 before
> > building CommonC++.  Maybe an #error for the #ifndef in each header this
> > happens in would be helpful.  Thanks.
> >  -- Ari Johnson
> >
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>




From ariston@cs.und.edu Fri Nov 01 20:40:24 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187nGx-0007kM-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 20:40:23 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187nGw-0007kA-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 20:40:23 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 187nGv-0007k6-00
	for bug-commoncpp@gnu.org; Fri, 01 Nov 2002 20:40:21 -0500
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gA21insY008313;
	Fri, 1 Nov 2002 19:44:49 -0600
Date: Fri, 1 Nov 2002 19:41:19 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
To: David Sugar <dyfet@ostel.com>
cc: <bug-commoncpp@gnu.org>
Subject: Re: FreeBSD Problems
In-Reply-To: <Pine.LNX.4.44.0211010716230.1997-100000@home.sys>
Message-ID: <Pine.GSO.4.33.0211011939380.21865-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'd say that the native thread library is the way to go.  FreeBSD
implements pthreads quite nicely, and I've had excellent luck using them
with CommonC++.  The problems come in with things like friends.cpp failing
to compile because nanosleep() isn't declared (putting an extern "C"
declaration for it right where it's used in a macro in cc++/config.h works
for me), and the fact that I absolutely cannot compile the library with
GCC 3.x, due to some kind of screwy include file monkey business; although
I can compile anything else with GCC 3.x just fine.
 -- Ari Johnson

On Fri, 1 Nov 2002, David Sugar wrote:

>
> I would like to see us have a clean and consistent build under FreeBSD.
> Currently, there are two choices possible with it; one to build against
> LinuxThreads, and one to do so with the native runtime thread library.
> Which do you think would be better for FreeBSD?
>
> David
>
> On Fri, 1 Nov 2002, Ari Johnson wrote:
>
> >
> > I think I'm going to just sit down and try to figure out what's wrong with
> > CommonC++ (from cvs) on FreeBSD.  I keep figuring out a quick hack around
> > things, but they are things that should be fixed.  So here's #1:
> >
> > friends.cpp: In function `static void ost::Thread::sleep(long unsigned int)':
> > friends.cpp:134: implicit declaration of function `int ost::nanosleep(...)'
> >
> > Anyone with insight as to why this is occurring?
> >  -- Ari Johnson
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> >
>




From fedemp@wanadoo.es Sat Nov 02 08:13:05 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187y5I-0004zZ-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 08:13:04 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187y5E-0004tT-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 08:13:02 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 187y5E-0004tL-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 08:13:00 -0500
Received: from risitas (62-37-139-56.dialup.uni2.es [62.37.139.56])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gA2DARX15212;
	Sat, 2 Nov 2002 14:10:28 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 187y5s-0000Jx-00; Sat, 02 Nov 2002 14:13:40 +0100
Date: Sat, 2 Nov 2002 14:13:39 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ari Johnson <ariston@cs.und.edu>
Cc: bug-commoncpp@gnu.org
Subject: Re: Suggestion regarding header files...
Message-ID: <20021102131339.GA743@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Ari Johnson <ariston@cs.und.edu>, bug-commoncpp@gnu.org
References: <20021101221926.GB828@risitas> <Pine.GSO.4.33.0211011938110.21865-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.0211011938110.21865-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/>

	I see. your solution seems much better. We will also have to
put the '#include <xml.h>' in common.h inside an #ifdef. And we should
also apply the #error idea to ftp.h and piostream, which are optional
too.

	If there is no objection, this will be done within a few days.

On Fri, Nov 01, 2002 at 07:39:17PM -0600, Ari Johnson wrote:
> 
> If you compiled without XML support, but you try to include cc++/xml.h,
> you should be informed that you're trying to use a part of the library
> that you didn't install.  I think that xml.h is a good place to put this,
> and also that it should be an #error (just like trying to start a car
> without an engine is an error and not something that can be ignored as a
> warning).
>  -- Ari Johnson
> 



From cproch@seculogix.de Sat Nov 02 08:01:24 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187xtz-000473-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 08:01:23 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187xtv-0003wE-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 08:01:22 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 187xtu-0003us-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 08:01:18 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP id 8CB7713AC4
	for <bug-commoncpp@gnu.org>; Sat,  2 Nov 2002 13:58:47 +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: Logging package for Common C++ / SocketPort connecting constructor
Date: Sat, 2 Nov 2002 14:01:16 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211021401.16908.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 List,

i have to things, first thing is:

I've done a logging package for Common C++ 2 that's more powerfull than t=
he=20
sLog class provided, and i want to contribute it to the Common C++ Librar=
ies=20
as "cclog".=20
The logging class supports multiple logging targets which can also be=20
dynamically loaded from plugins. Some first Logtarget-Plugins for logging=
 to=20
console, files, oracle and mysql databases are included in the package.

second thing:

For a network protocol daemon i needed to patch the SocketPort class that=
 it=20
can do non-blocking outbound tcp connections - but i did'nt find a nice n=
ame=20
for it cause of the udp constructor.=20
Any suggestions how this should be done in the preffered Common C++ way?
1. Solution is modifiying the "UDP" constructor that it takes additional=20
arguments.
2. Solution is to provide a static function that returns a connecting=20
SocketPort object.


Regards,

Christian Prochnow




From dyfet@ostel.com Sat Nov 02 09:04:25 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187ysy-0008Pq-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 09:04:24 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187yrv-00080h-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 09:03:24 -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 187yrt-0007zF-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 09:03:18 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gA2ERFP29918;
	Sat, 2 Nov 2002 09:27:15 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sat, 2 Nov 2002 09:27:15 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: "Prochnow, Christian" <cproch@seculogix.de>
cc: bug-commoncpp@gnu.org
Subject: Re: Logging package for Common C++ / SocketPort connecting constructor
In-Reply-To: <200211021401.16908.cproch@seculogix.de>
Message-ID: <Pine.LNX.4.44.0211020925130.29866-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/>

On Sat, 2 Nov 2002, Prochnow, Christian wrote:

> Hi List,
> 
> i have to things, first thing is:
> 
> I've done a logging package for Common C++ 2 that's more powerfull than the 
> sLog class provided, and i want to contribute it to the Common C++ Libraries 
> as "cclog". 
> The logging class supports multiple logging targets which can also be 
> dynamically loaded from plugins. Some first Logtarget-Plugins for logging to 
> console, files, oracle and mysql databases are included in the package.

Hmm...this could be very interesting.  Perhaps it can in some way be 
merged into or extended from the existing slog class?  I just don't like 
the idea of having two completely different logging systems :).

 > 
> second thing:
> 
> For a network protocol daemon i needed to patch the SocketPort class that it 
> can do non-blocking outbound tcp connections - but i did'nt find a nice name 
> for it cause of the udp constructor. 
> Any suggestions how this should be done in the preffered Common C++ way?
> 1. Solution is modifiying the "UDP" constructor that it takes additional 
> arguments.

Why not simply have an alternate constructor?

> 2. Solution is to provide a static function that returns a connecting 
> SocketPort object.
> 
> 
> Regards,
> 
> Christian Prochnow
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From dyfet@ostel.com Sat Nov 02 09:10:09 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187yyX-0004Rb-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 09:10:09 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187yyS-0004QE-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 09:10:06 -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 187yyQ-0004Nn-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 09:10:03 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gA2EY0Y29957;
	Sat, 2 Nov 2002 09:34:00 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sat, 2 Nov 2002 09:34:00 -0500 (EST)
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: Suggestion regarding header files...
In-Reply-To: <20021102131339.GA743@risitas>
Message-ID: <Pine.LNX.4.44.0211020927550.29866-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 find usually when I choose not to build Common C++ with "XML support"  
(there is a configure option to do this implicitly), I also only link with
ccgnu rather than with ccext, so, in a sense it is a "build requirement"  
to have XML support, but certainly not a runtime requirement if one builds
small footprint applications that only link with ccgnu.  It would also be
interesting if we could alternately use other xml parsers into the Common
C++ XML classes.  If no XML support is present at build time, however, 
should that be an error or a warning?  I think it should be at least a 
warning, which it isn't now.

On Sat, 2 Nov 2002, Federico Montesino Pouzols wrote:

> 
> 	I see. your solution seems much better. We will also have to
> put the '#include <xml.h>' in common.h inside an #ifdef. And we should
> also apply the #error idea to ftp.h and piostream, which are optional
> too.
> 
> 	If there is no objection, this will be done within a few days.
> 
> On Fri, Nov 01, 2002 at 07:39:17PM -0600, Ari Johnson wrote:
> > 
> > If you compiled without XML support, but you try to include cc++/xml.h,
> > you should be informed that you're trying to use a part of the library
> > that you didn't install.  I think that xml.h is a good place to put this,
> > and also that it should be an #error (just like trying to start a car
> > without an engine is an error and not something that can be ignored as a
> > warning).
> >  -- Ari Johnson
> > 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From fedemp@wanadoo.es Sat Nov 02 10:04:56 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187zn7-0003qL-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 10:02:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187zn2-0003lT-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 10:02:23 -0500
Received: from [62.37.236.135] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 187zn2-0003lP-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 10:02:20 -0500
Received: from risitas ([80.103.113.161])
	by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id gA2FnjJ17467;
	Sat, 2 Nov 2002 16:49:46 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 187znU-0000ax-00; Sat, 02 Nov 2002 16:02:48 +0100
Date: Sat, 2 Nov 2002 16:02:48 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Cc: Ari Johnson <ariston@cs.und.edu>, bug-commoncpp@gnu.org
Subject: Re: Suggestion regarding header files...
Message-ID: <20021102150248.GA1846@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: <20021102131339.GA743@risitas> <Pine.LNX.4.44.0211020927550.29866-100000@home.sys>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0211020927550.29866-100000@home.sys>
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/>

	Currently, the autoconf stuff defines two symbols:
COMMON_XML_PARSING (A) and HAVE_LIBXML (B). Only B is used for the
#ifdefs. Using both A and B we could do things like this:

#if defined(A) && defined(B)
	// libxml based stuff as it is currently defined.
#if defined(A) && !defined(B)
	// at present, #error "libxml not installed"
	// in the future, check another HAVE_... alternative xml lib.
#if !defined(A)
	// put in xml.cpp something like #warning "XML support is not
	// being compiled, are you sure?". And put in xml.h #error
	// "XML support not available"
	

On Sat, Nov 02, 2002 at 09:34:00AM -0500, David Sugar wrote:
> 
> I find usually when I choose not to build Common C++ with "XML support"  
> (there is a configure option to do this implicitly), I also only link with
> ccgnu rather than with ccext, so, in a sense it is a "build requirement"  
> to have XML support, but certainly not a runtime requirement if one builds
> small footprint applications that only link with ccgnu.  It would also be
> interesting if we could alternately use other xml parsers into the Common
> C++ XML classes.  If no XML support is present at build time, however, 
> should that be an error or a warning?  I think it should be at least a 
> warning, which it isn't now.
> 
> On Sat, 2 Nov 2002, Federico Montesino Pouzols wrote:
> 
> > 
> > 	I see. your solution seems much better. We will also have to
> > put the '#include <xml.h>' in common.h inside an #ifdef. And we should
> > also apply the #error idea to ftp.h and piostream, which are optional
> > too.
> > 
> > 	If there is no objection, this will be done within a few days.
> > 
> > On Fri, Nov 01, 2002 at 07:39:17PM -0600, Ari Johnson wrote:
> > > 
> > > If you compiled without XML support, but you try to include cc++/xml.h,
> > > you should be informed that you're trying to use a part of the library
> > > that you didn't install.  I think that xml.h is a good place to put this,
> > > and also that it should be an #error (just like trying to start a car
> > > without an engine is an error and not something that can be ignored as a
> > > warning).
> > >  -- 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 cproch@seculogix.de Sat Nov 02 09:54:43 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 187zff-0004Mb-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 09:54:43 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 187zfd-0004Kg-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 09:54:42 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 187zfd-0004JM-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 09:54:41 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP id 6FBC613AC4
	for <bug-commoncpp@gnu.org>; Sat,  2 Nov 2002 15:52:10 +0100 (CET)
Content-Type: text/plain;
  charset="iso-8859-1"
From: "Prochnow, Christian" <cproch@seculogix.de>
Reply-To: cproch@seculogix.de
To: bug-commoncpp@gnu.org
Subject: Re: Logging package for Common C++ / SocketPort connecting constructor
Date: Sat, 2 Nov 2002 15:54:34 +0100
User-Agent: KMail/1.4.3
References: <Pine.LNX.4.44.0211020925130.29866-100000@home.sys>
In-Reply-To: <Pine.LNX.4.44.0211020925130.29866-100000@home.sys>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211021554.34344.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/>

May i post the cclog source-tarball on the list ?

Greetings,
Christian

> On Sat, 2 Nov 2002, Prochnow, Christian wrote:
> > Hi List,
> >
> > i have to things, first thing is:
> >
> > I've done a logging package for Common C++ 2 that's more powerfull th=
an
> > the sLog class provided, and i want to contribute it to the Common C+=
+
> > Libraries as "cclog".
> > The logging class supports multiple logging targets which can also be
> > dynamically loaded from plugins. Some first Logtarget-Plugins for log=
ging
> > to console, files, oracle and mysql databases are included in the
> > package.
>
> Hmm...this could be very interesting.  Perhaps it can in some way be
> merged into or extended from the existing slog class?  I just don't lik=
e
> the idea of having two completely different logging systems :).
>
> > second thing:
> >
> > For a network protocol daemon i needed to patch the SocketPort class =
that
> > it can do non-blocking outbound tcp connections - but i did'nt find a
> > nice name for it cause of the udp constructor.
> > Any suggestions how this should be done in the preffered Common C++ w=
ay?
> > 1. Solution is modifiying the "UDP" constructor that it takes additio=
nal
> > arguments.
>
> Why not simply have an alternate constructor?
>
> > 2. Solution is to provide a static function that returns a connecting
> > SocketPort object.
> >
> >
> > Regards,
> >
> > Christian Prochnow
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From dyfet@ostel.com Sat Nov 02 10:32:49 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 1880GX-0003vj-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 10:32:49 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 1880GT-0003ug-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 10:32:48 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 1880GS-0003s4-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 10:32:44 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gA2FugN15784;
	Sat, 2 Nov 2002 10:56:42 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sat, 2 Nov 2002 10:56:42 -0500 (EST)
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: Suggestion regarding header files...
In-Reply-To: <20021102131339.GA743@risitas>
Message-ID: <Pine.LNX.4.44.0211021056340.15779-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, re-reading this, this makes perfect sense.

On Sat, 2 Nov 2002, Federico Montesino Pouzols wrote:

> 
> 	I see. your solution seems much better. We will also have to
> put the '#include <xml.h>' in common.h inside an #ifdef. And we should
> also apply the #error idea to ftp.h and piostream, which are optional
> too.
> 
> 	If there is no objection, this will be done within a few days.
> 
> On Fri, Nov 01, 2002 at 07:39:17PM -0600, Ari Johnson wrote:
> > 
> > If you compiled without XML support, but you try to include cc++/xml.h,
> > you should be informed that you're trying to use a part of the library
> > that you didn't install.  I think that xml.h is a good place to put this,
> > and also that it should be an #error (just like trying to start a car
> > without an engine is an error and not something that can be ignored as a
> > warning).
> >  -- Ari Johnson
> > 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From fedemp@wanadoo.es Sat Nov 02 15:33:03 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 1884x5-0000UL-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 15:33:03 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 1884x2-0000Tz-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 15:33:02 -0500
Received: from [62.37.236.137] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 1884x1-0000Ts-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 15:32:59 -0500
Received: from risitas (62-36-178-215.dialup.uni2.es [62.36.178.215])
	by smtp.wanadoo.es (8.11.3/8.11.3) with ESMTP id gA2KdG027813;
	Sat, 2 Nov 2002 21:39:16 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 1884xP-0000Ci-00; Sat, 02 Nov 2002 21:33:23 +0100
Date: Sat, 2 Nov 2002 21:33:23 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Prochnow, Christian" <cproch@seculogix.de>
Cc: bug-commoncpp@gnu.org
Subject: Re: Logging package for Common C++ / SocketPort connecting constructor
Message-ID: <20021102203322.GA715@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: "Prochnow, Christian" <cproch@seculogix.de>,
	bug-commoncpp@gnu.org
References: <Pine.LNX.4.44.0211020925130.29866-100000@home.sys> <200211021554.34344.cproch@seculogix.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200211021554.34344.cproch@seculogix.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	If it is small, go ahead. If it is big, you can use the
Savannah patch manager, provide a temporary URI, or send it to David
(cc it to me too).

On Sat, Nov 02, 2002 at 03:54:34PM +0100, Prochnow, Christian wrote:
> 
> May i post the cclog source-tarball on the list ?
> 
> Greetings,
> Christian
> 



From dyfet@ostel.com Sat Nov 02 19:49:06 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 1888wr-0003ZG-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 19:49:05 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 1888wp-0003Y7-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 19:49:05 -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 1888wp-0003Xp-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 19:49:03 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gA31D7x30928;
	Sat, 2 Nov 2002 20:13:07 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sat, 2 Nov 2002 20:13:07 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Ari Johnson <ariston@cs.und.edu>
cc: bug-commoncpp@gnu.org
Subject: Re: FreeBSD Problems
In-Reply-To: <Pine.GSO.4.33.0211011939380.21865-100000@agassiz.cs.und.edu>
Message-ID: <Pine.LNX.4.44.0211022012370.30772-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/>

Well, let's see if we can solve the first problem immediately in the 
distrubution and then get a nice "ports" package that is current...

On Fri, 1 Nov 2002, Ari Johnson wrote:

> 
> I'd say that the native thread library is the way to go.  FreeBSD
> implements pthreads quite nicely, and I've had excellent luck using them
> with CommonC++.  The problems come in with things like friends.cpp failing
> to compile because nanosleep() isn't declared (putting an extern "C"
> declaration for it right where it's used in a macro in cc++/config.h works
> for me), and the fact that I absolutely cannot compile the library with
> GCC 3.x, due to some kind of screwy include file monkey business; although
> I can compile anything else with GCC 3.x just fine.
>  -- Ari Johnson
> 
> On Fri, 1 Nov 2002, David Sugar wrote:
> 
> >
> > I would like to see us have a clean and consistent build under FreeBSD.
> > Currently, there are two choices possible with it; one to build against
> > LinuxThreads, and one to do so with the native runtime thread library.
> > Which do you think would be better for FreeBSD?
> >
> > David
> >
> > On Fri, 1 Nov 2002, Ari Johnson wrote:
> >
> > >
> > > I think I'm going to just sit down and try to figure out what's wrong with
> > > CommonC++ (from cvs) on FreeBSD.  I keep figuring out a quick hack around
> > > things, but they are things that should be fixed.  So here's #1:
> > >
> > > friends.cpp: In function `static void ost::Thread::sleep(long unsigned int)':
> > > friends.cpp:134: implicit declaration of function `int ost::nanosleep(...)'
> > >
> > > Anyone with insight as to why this is occurring?
> > >  -- 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 Sat Nov 02 19:57:36 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 188956-00078b-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 19:57:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 188952-000757-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 19:57:35 -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 188951-00074g-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 19:57:31 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gA31LZX30988;
	Sat, 2 Nov 2002 20:21:35 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sat, 2 Nov 2002 20:21:35 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Ari Johnson <ariston@cs.und.edu>
cc: bug-commoncpp@gnu.org
Subject: Re: FreeBSD Problems
In-Reply-To: <Pine.GSO.4.33.0211010134020.20208-100000@agassiz.cs.und.edu>
Message-ID: <Pine.LNX.4.44.0211022021040.30772-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/>

Also, keep in mind that cvs -HEAD is really for a future release.  The 
current "active" releases are drawn from -rRELEASE1.

On Fri, 1 Nov 2002, Ari Johnson wrote:

> 
> I think I'm going to just sit down and try to figure out what's wrong with
> CommonC++ (from cvs) on FreeBSD.  I keep figuring out a quick hack around
> things, but they are things that should be fixed.  So here's #1:
> 
> friends.cpp: In function `static void ost::Thread::sleep(long unsigned int)':
> friends.cpp:134: implicit declaration of function `int ost::nanosleep(...)'
> 
> Anyone with insight as to why this is occurring?
>  -- Ari Johnson
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From ariston@cs.und.edu Sat Nov 02 22:49:52 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 188Blo-0003tv-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 22:49:52 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 188BlI-0003QB-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 22:49:51 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 188BlI-0003Q2-00
	for bug-commoncpp@gnu.org; Sat, 02 Nov 2002 22:49:20 -0500
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gA33s8sY004849;
	Sat, 2 Nov 2002 21:54:09 -0600
Date: Sat, 2 Nov 2002 21:50:16 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: David Sugar <dyfet@ostel.com>, <bug-commoncpp@gnu.org>
Subject: Re: Suggestion regarding header files...
In-Reply-To: <20021102150248.GA1846@risitas>
Message-ID: <Pine.GSO.4.33.0211022150120.23474-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 like that solution.

On Sat, 2 Nov 2002, Federico Montesino Pouzols wrote:

>
> 	Currently, the autoconf stuff defines two symbols:
> COMMON_XML_PARSING (A) and HAVE_LIBXML (B). Only B is used for the
> #ifdefs. Using both A and B we could do things like this:
>
> #if defined(A) && defined(B)
> 	// libxml based stuff as it is currently defined.
> #if defined(A) && !defined(B)
> 	// at present, #error "libxml not installed"
> 	// in the future, check another HAVE_... alternative xml lib.
> #if !defined(A)
> 	// put in xml.cpp something like #warning "XML support is not
> 	// being compiled, are you sure?". And put in xml.h #error
> 	// "XML support not available"
>
>
> On Sat, Nov 02, 2002 at 09:34:00AM -0500, David Sugar wrote:
> >
> > I find usually when I choose not to build Common C++ with "XML support"
> > (there is a configure option to do this implicitly), I also only link with
> > ccgnu rather than with ccext, so, in a sense it is a "build requirement"
> > to have XML support, but certainly not a runtime requirement if one builds
> > small footprint applications that only link with ccgnu.  It would also be
> > interesting if we could alternately use other xml parsers into the Common
> > C++ XML classes.  If no XML support is present at build time, however,
> > should that be an error or a warning?  I think it should be at least a
> > warning, which it isn't now.
> >
> > On Sat, 2 Nov 2002, Federico Montesino Pouzols wrote:
> >
> > >
> > > 	I see. your solution seems much better. We will also have to
> > > put the '#include <xml.h>' in common.h inside an #ifdef. And we should
> > > also apply the #error idea to ftp.h and piostream, which are optional
> > > too.
> > >
> > > 	If there is no objection, this will be done within a few days.
> > >
> > > On Fri, Nov 01, 2002 at 07:39:17PM -0600, Ari Johnson wrote:
> > > >
> > > > If you compiled without XML support, but you try to include cc++/xml.h,
> > > > you should be informed that you're trying to use a part of the library
> > > > that you didn't install.  I think that xml.h is a good place to put this,
> > > > and also that it should be an #error (just like trying to start a car
> > > > without an engine is an error and not something that can be ignored as a
> > > > warning).
> > > >  -- 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 stanton@electric-cloud.com Mon Nov 04 01:28:02 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 188aiQ-00033a-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 01:28:02 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 188aiL-00033F-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 01:28:00 -0500
Received: from [64.41.141.105] (helo=electric-cloud.com)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 188afp-0002Kr-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 01:25:21 -0500
Received: from Laddie (localhost.localdomain [127.0.0.1])
	(authenticated)
	by electric-cloud.com (8.11.6/8.11.6) with ESMTP id gA46PAW02437
	for <bug-commoncpp@gnu.org>; Sun, 3 Nov 2002 22:25:11 -0800
From: "Scott Stanton" <stanton@electric-cloud.com>
To: <bug-commoncpp@gnu.org>
Subject: Problems building 1.0.3 on win32
Date: Sun, 3 Nov 2002 22:25:03 -0800
Organization: Electric Cloud
Message-ID: <000201c283ca$e9e11530$2601a8c0@Laddie>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <20021103113352.1369.88157.Mailman@monty-python.gnu.org>
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've just downloaded the 1.0.3 tarball, and I'm trying to build it with
gcc3.2 under cygwin with little success.  I'm just trying to do a simple
configure/build and I get errors like the following:

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)

In looking at the header files, there seems to be a mess of #ifdefs
around cygwin/mingw32 and win32 that leave things in a confused state.  

Has anyone been able to make this work?   What configure flags have
people used successfully under cygwin?

--Scott





From triendl.kj@mbox.at Mon Nov 04 10:01:43 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 188ijX-0004A2-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 10:01:43 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 188ijP-00047b-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 10:01:40 -0500
Received: from viefep15-int.chello.at ([213.46.255.19])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 188iV3-0007cw-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 09:46:46 -0500
Received: from dev1xp ([80.109.135.71]) by viefep15-int.chello.at
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with SMTP
          id <20021104144642.XXIN9517.viefep15-int.chello.at@dev1xp>
          for <bug-commoncpp@gnu.org>; Mon, 4 Nov 2002 15:46:42 +0100
From: "klaus triendl \(daten unlimited\)" <triendl.kj@mbox.at>
To: <bug-commoncpp@gnu.org>
Subject: error in SocketService::run()
Date: Mon, 4 Nov 2002 15:41:07 +0100
Message-ID: <MNENKPHMOOKIHGCMGMEBEEBHCCAA.triendl.kj@mbox.at>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.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 tested the SampleSocketPort example with WinXP. i changed the example a
little - the server disconnects in the SampleSocketPort::expired() method
with disconnect(). This means that CloseSocket() is called with
m_bDoDisconnect=true and the SocketPort is deleted.
SampleSocketPort::expired() is called in SocketService::run(); after it
returns the whole starts from the beginning referring to the already deleted
object causing a segfault:


SocketService::run():

retry:
			expires = port->getTimer(); // still returns 0 if port object has been
deleted
			if(expires > 0)
				if(expires < timer)
					timer = expires;

			// if we expire, get new scheduling now

			if(!expires)
			{
				port->endTimer(); // sets active=false
				port->expired(); // segfault when it comes here the 2nd time
			//	^^^^^^^^^^^^^^^^ port object is deleted the 1st time
				goto retry;
			}

			port = port->next; // points to some address after the port object is
deleted




the funny thing is that port->getTimer() (baseclass-method of
SampleSocketPort) doesn't cause a segfault after SampleSocketPort is
deleted, but i guess this is due to how objects are stored in memory. but
this doesn't help us because after the SampleSocketPort object is deleted
port->getTimer() still returns 0 and active has probably some value
(something other than 0 or 1 - i tested it), therefore we cannot rely on
active=false. we also cannot be sure that port->next=NULL or
port->next="address of next open port".

a possibility to handle this problem would be to let expired() return false
or true according to whether the object was deleted and to have a second
port pointer pointing to port->prev which comes into play if expired()
returns false (while deleting the port it detaches itself from the service,
thus 2ndportpointer->next would point to port->next).



any comments or suggestions?




--
klaus triendl




From fedemp@wanadoo.es Mon Nov 04 14:57:56 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 188nMB-00079l-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 14:57:55 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 188nM9-00079K-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 14:57:55 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 188nM8-000796-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 14:57:52 -0500
Received: from risitas (62-36-179-200.dialup.uni2.es [62.36.179.200])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gA52t7g11658;
	Tue, 5 Nov 2002 03:55:08 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 188nMp-0000Cr-00; Mon, 04 Nov 2002 20:58:35 +0100
Date: Mon, 4 Nov 2002 20:58:35 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Scott Stanton <stanton@electric-cloud.com>
Cc: bug-commoncpp@gnu.org
Subject: Re: Problems building 1.0.3 on win32
Message-ID: <20021104195835.GA789@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Scott Stanton <stanton@electric-cloud.com>,
	bug-commoncpp@gnu.org
References: <20021103113352.1369.88157.Mailman@monty-python.gnu.org> <000201c283ca$e9e11530$2601a8c0@Laddie>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000201c283ca$e9e11530$2601a8c0@Laddie>
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, current releases do not compile on cygwin since mingw32
support was added. It must be mostly a few inconsistent #ifdefs. It
will be fixed. Note that the latest release is 1.0.5, you may have to
access the ftp server through ftp instead of http.

On Sun, Nov 03, 2002 at 10:25:03PM -0800, Scott Stanton wrote:
> I've just downloaded the 1.0.3 tarball, and I'm trying to build it with
> gcc3.2 under cygwin with little success.  I'm just trying to do a simple
> configure/build and I get errors like the following:
> 
> 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)
> 
> In looking at the header files, there seems to be a mess of #ifdefs
> around cygwin/mingw32 and win32 that leave things in a confused state.  
> 
> Has anyone been able to make this work?   What configure flags have
> people used successfully under cygwin?
> 
> --Scott
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fedemp@wanadoo.es Mon Nov 04 15:00:08 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 188nOJ-0007mT-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 15:00:07 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 188nOF-0007ls-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 15:00:06 -0500
Received: from [62.37.236.135] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 188nOD-0007lE-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 15:00:02 -0500
Received: from risitas (62-36-179-200.dialup.uni2.es [62.36.179.200])
	by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id gA4L3AJ14244
	for <bug-commoncpp@gnu.org>; Mon, 4 Nov 2002 22:03:11 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 188nP2-0000D3-00
	for <bug-commoncpp@gnu.org>; Mon, 04 Nov 2002 21:00:52 +0100
Date: Mon, 4 Nov 2002 21:00:52 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: ftp.gnu.org/pub/gnu/commoncpp/index.html outdated
Message-ID: <20021104200052.GB789@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, the index.html of cc++ is outdated. It lists only up to
1.0.3, so people accessing the server through http (which seems to be
the preferred way now) do not know there are newer releases.



From mad@brasmap.com.br Mon Nov 04 07:09:15 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 188g2d-00014Y-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 07:09:15 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 188g2Z-00013p-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 07:09:14 -0500
Received: from acate.com.br ([200.215.17.89])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 188g2X-000116-00
	for bug-commoncpp@gnu.org; Mon, 04 Nov 2002 07:09:09 -0500
Received: (qmail 10905 invoked from network); 4 Nov 2002 12:08:57 -0000
Received: from unknown (HELO cli004.brasmap) (192.168.1.13)
  by acate.com.br with SMTP; 4 Nov 2002 12:08:53 -0000
Received: from brasmap.com.br (localhost.localdomain [127.0.0.1])
	by cli004.brasmap (8.11.1/8.11.1) with SMTP id gA4C7RM09820
	for <bug-commoncpp@gnu.org>; Mon, 4 Nov 2002 10:07:28 -0200
Date: Mon, 4 Nov 2002 10:07:27 -0200
From: Marcelo Dalmas <mad@brasmap.com.br>
To: ccxx <bug-commoncpp@gnu.org>
Subject: date.cpp patch
Message-Id: <20021104100727.74ae5cab.mad@brasmap.com.br>
Organization: BRASMAP Sistemas
X-Mailer: Sylpheed version 0.8.5 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="Multipart_Mon__4_Nov_2002_10:07:27_-0200_0821f2f0"
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.

--Multipart_Mon__4_Nov_2002_10:07:27_-0200_0821f2f0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit


Hi!

A patch to date.cpp to work with daylight.

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


--Multipart_Mon__4_Nov_2002_10:07:27_-0200_0821f2f0
Content-Type: application/octet-stream;
 name="date.patch"
Content-Disposition: attachment;
 filename="date.patch"
Content-Transfer-Encoding: base64

SW5kZXg6IHNyYy9kYXRlLmNwcAo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJDUyBmaWxlOiAvdXNyL2xvY2FsL2N2c3Jv
b3QvYnJhc21hcC9jb21tb25jcHAyL3NyYy9kYXRlLmNwcCx2CnJldHJpZXZpbmcgcmV2aXNpb24g
MS41CmRpZmYgLXIxLjUgZGF0ZS5jcHAKNjg0YzY4NCw2ODUKPCAKLS0tCj4gCWR0LnRtX2lzZHN0
ID0gLTE7Cj4gCQo3MTksNzIwZDcxOQo8IAo8IAo3MzdjNzM2CjwgICAgIHRicCA9IGxvY2FsdGlt
ZSgmdCk7Ci0tLQo+ICAgICAgICAgdGJwID0gbG9jYWx0aW1lKCZ0KTsK

--Multipart_Mon__4_Nov_2002_10:07:27_-0200_0821f2f0--




From fedemp@altern.org Tue Nov 05 10:44:00 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 1895hd-000620-00
	for bug-commoncpp@gnu.org; Tue, 05 Nov 2002 10:33:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 1895hX-00060V-00
	for bug-commoncpp@gnu.org; Tue, 05 Nov 2002 10:33:15 -0500
Received: from temporaire.org ([80.67.174.11] helo=altern.org)
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 1895hX-0005zC-00
	for bug-commoncpp@gnu.org; Tue, 05 Nov 2002 10:33:11 -0500
Received: (qmail 2090 invoked by alias); 5 Nov 2002 15:28:46 -0000
Received: from unknown (HELO localhost) (127.0.0.1)
  by localhost with SMTP; 5 Nov 2002 15:28:46 -0000
Date: Tue, 5 Nov 2002 16:28:46 +0100 (CET)
From: <fedemp@altern.org>
Subject: re : Compile Error in Visual C++ on Windows 2000
To: xiaowenwu3@yahoo.com, bug-commoncpp@gnu.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Message-Id: <E1895hX-0005zC-00@monty-python.gnu.org>
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/>

   These errors were fixed for next releases. The current
release of cc++ 2 is 1.0.6. There is a problem with the
html pages, so you may have to get it from
ftp://ftp.gnu.org/pub/gnu/commoncpp/ (ftp instead
 of http://).




From fedemp@wanadoo.es Tue Nov 05 15:12:27 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 189A3n-0006yw-00
	for bug-commoncpp@gnu.org; Tue, 05 Nov 2002 15:12:27 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 189A3h-0006yV-00
	for bug-commoncpp@gnu.org; Tue, 05 Nov 2002 15:12:22 -0500
Received: from [62.37.236.136] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 189A3h-0006yO-00
	for bug-commoncpp@gnu.org; Tue, 05 Nov 2002 15:12:21 -0500
Received: from risitas (62-37-137-121.dialup.uni2.es [62.37.137.121])
	by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id gA5K1cp25614;
	Tue, 5 Nov 2002 21:01:38 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 189A44-00025f-00; Tue, 05 Nov 2002 21:12:44 +0100
Date: Tue, 5 Nov 2002 21:12:44 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Marcelo Matus <mmatus@dinha.acms.arizona.edu>
Cc: bug-commoncpp@gnu.org
Subject: Re: Compiling warnings (one error at least)
Message-ID: <20021105201244.GA662@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Marcelo Matus <mmatus@dinha.acms.arizona.edu>,
	bug-commoncpp@gnu.org
References: <3DC07EF9.2000909@acms.arizona.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DC07EF9.2000909@acms.arizona.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/>

	Fixed in CVS for next releases, thanks. Just curious, what
compiler reports these warnings?

	Umm, we should do more tests with -Wall...

On Wed, Oct 30, 2002 at 05:53:13PM -0700, Marcelo Matus wrote:
> I just compile the commoncpp2-1.0.1 version and
> I've got the following warnings:
> 
> 
> ****************
> 
> ************************
> 
> 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 fedemp@bulbasaur.rediris.es Wed Nov 06 08:30:43 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 189QGY-0001MH-00
	for bug-commoncpp@gnu.org; Wed, 06 Nov 2002 08:30:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 189QGQ-0001JM-00
	for bug-commoncpp@gnu.org; Wed, 06 Nov 2002 08:30:40 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 189QGP-0001I3-00
	for bug-commoncpp@gnu.org; Wed, 06 Nov 2002 08:30:33 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 189QH7-0005mf-00
	for <bug-commoncpp@gnu.org>; Wed, 06 Nov 2002 14:31:17 +0100
Date: Wed, 6 Nov 2002 14:31:17 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: FreeBSD Problems
Message-ID: <20021106133116.GA14059@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <Pine.GSO.4.33.0211011939380.21865-100000@agassiz.cs.und.edu> <Pine.LNX.4.44.0211022012370.30772-100000@home.sys>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0211022012370.30772-100000@home.sys>
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/>

	With the "extern" trick it seems to compile and work well. The
fix is in CVS.

	The time.h of FreeBSD does not declare nanosleep unless you
define a very peculiar symbol for posix 1003.1b.

On Sat, Nov 02, 2002 at 08:13:07PM -0500, David Sugar wrote:
> 
> Well, let's see if we can solve the first problem immediately in the 
> distrubution and then get a nice "ports" package that is current...
> 
> On Fri, 1 Nov 2002, Ari Johnson wrote:
> 
> > 
> > I'd say that the native thread library is the way to go.  FreeBSD
> > implements pthreads quite nicely, and I've had excellent luck using them
> > with CommonC++.  The problems come in with things like friends.cpp failing
> > to compile because nanosleep() isn't declared (putting an extern "C"
> > declaration for it right where it's used in a macro in cc++/config.h works
> > for me), and the fact that I absolutely cannot compile the library with
> > GCC 3.x, due to some kind of screwy include file monkey business; although
> > I can compile anything else with GCC 3.x just fine.
> >  -- Ari Johnson
> > 
> > On Fri, 1 Nov 2002, David Sugar wrote:
> > 
> > >
> > > I would like to see us have a clean and consistent build under FreeBSD.
> > > Currently, there are two choices possible with it; one to build against
> > > LinuxThreads, and one to do so with the native runtime thread library.
> > > Which do you think would be better for FreeBSD?
> > >
> > > David
> > >
> > > On Fri, 1 Nov 2002, Ari Johnson wrote:
> > >
> > > >
> > > > I think I'm going to just sit down and try to figure out what's wrong with
> > > > CommonC++ (from cvs) on FreeBSD.  I keep figuring out a quick hack around
> > > > things, but they are things that should be fixed.  So here's #1:
> > > >
> > > > friends.cpp: In function `static void ost::Thread::sleep(long unsigned int)':
> > > > friends.cpp:134: implicit declaration of function `int ost::nanosleep(...)'
> > > >
> > > > Anyone with insight as to why this is occurring?
> > > >  -- Ari Johnson
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Bug-commoncpp mailing list
> > > > Bug-commoncpp@gnu.org
> > > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > > >
> > >
> > 
> > 
> > 
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From cproch@seculogix.de Wed Nov 06 15:03:29 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 189WOe-0003Z7-00
	for bug-commoncpp@gnu.org; Wed, 06 Nov 2002 15:03:28 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 189WOY-0003Wn-00
	for bug-commoncpp@gnu.org; Wed, 06 Nov 2002 15:03:26 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 189WOX-0003W8-00
	for bug-commoncpp@gnu.org; Wed, 06 Nov 2002 15:03:21 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP id 0F4C413AC4
	for <bug-commoncpp@gnu.org>; Wed,  6 Nov 2002 21:00:52 +0100 (CET)
From: "Prochnow, Christian" <cproch@seculogix.de>
Reply-To: cproch@seculogix.de
To: bug-commoncpp@gnu.org
Subject: Patch for connecting SocketPort constructor
Date: Wed, 6 Nov 2002 21:03:20 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="------------Boundary-00=_KP76RV43ADUN6YB010OB"
Message-Id: <200211062103.20284.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/>

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

Hi,

i've patched the SocketPort class a bit to provide a non-blocking constru=
ctor=20
for outbound tcp connections.
To detect when the connection is established, overload SocketPort::output=
().
SocketPort::output()  get's called by the SocketService when the connecti=
on is=20
ready, SocketPort::disconnect() when the connect failed.=20
at the moment you should set the socket state to "CONNECTED" when=20
SocketPort::output() get's called for the first time, which i think shoul=
d=20
eventually be done in SocketService.

Regards,=20
Christian Prochnow

--------------Boundary-00=_KP76RV43ADUN6YB010OB
Content-Type: text/x-diff;
  charset="us-ascii";
  name="port.cpp.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="port.cpp.patch"

--- commoncpp2-1.0.5.orig/src/port.cpp	2002-10-05 17:43:38.000000000 +0200
+++ commoncpp2-1.0.5/src/port.cpp	2002-11-06 20:28:56.000000000 +0100
@@ -231,6 +231,67 @@
 	svc->attach(this);
 }
 
+SocketPort::SocketPort(SocketService *svc, const InetHostAddress &ih, 
+		       tpport_t port) :
+Socket(AF_INET, SOCK_STREAM, 0)
+{
+#ifdef WIN32
+	// FIXME: error handling
+	event = CreateEvent(NULL,TRUE,FALSE,NULL);
+#endif
+	struct sockaddr_in addr;
+
+	memset(&addr, 0, sizeof(addr));
+	next = prev = NULL;
+	service = NULL;
+	addr.sin_family = AF_INET;
+	addr.sin_addr = getaddress(ih);
+	addr.sin_port = htons(port);
+
+#ifndef WIN32
+	long opts = fcntl(so, F_GETFL);
+	fcntl(so, F_SETFL, opts | O_NDELAY);
+#else
+	u_long opts = 1;
+	ioctlsocket(so,FIONBIO,&opts);
+#endif
+
+	int rtn = ::connect(so, (struct sockaddr *)&addr, (socklen_t)sizeof(addr));
+
+#ifndef WIN32
+	fcntl(so, F_SETFL, opts);
+#else
+	opts = 0;
+	ioctlsocket(so,FIONBIO,&opts);
+#endif
+
+	if(!rtn)
+	{
+		state = CONNECTED;
+	}
+	else
+	{
+#ifndef WIN32
+		if(errno == EINPROGRESS)
+#else
+		if(WSAGetLastError() == WSAEINPROGRESS)
+#endif
+		{
+			state = CONNECTING;
+			setDetectOutput(true);
+		}
+		else
+		{
+			endSocket();
+			error(connectError());
+			return;
+		}
+	}
+
+	setError(false);
+	svc->attach(this);
+}
+
 SocketPort::~SocketPort()
 {
 #ifdef WIN32

--------------Boundary-00=_KP76RV43ADUN6YB010OB
Content-Type: text/x-diff;
  charset="us-ascii";
  name="socket.h.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="socket.h.patch"

--- commoncpp2-1.0.5.orig/include/cc++/socket.h	2002-08-27 04:11:07.000000000 +0200
+++ commoncpp2-1.0.5/include/cc++/socket.h	2002-11-06 19:42:06.000000000 +0100
@@ -1837,6 +1837,8 @@
 	 * @param port number to bind to.
 	 */
 	SocketPort(SocketService *svc, const InetAddress &ia, tpport_t port);
+	
+	SocketPort(SocketService *svc, const InetHostAddress &ih, tpport_t port);
 
 	/** 
 	 * Attach yourself to the service pool thread object. The later version.

--------------Boundary-00=_KP76RV43ADUN6YB010OB--




From dyfet@ostel.com Thu Nov 07 01:53:55 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 189gY7-0004i5-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 01:53:55 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 189gY4-0004hP-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 01:53:54 -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 189gY1-0004aH-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 01:53:51 -0500
Received: from home.sys (IDENT:461J4lhp5FnwW7O8T8fczeQix6Jy9mhm@home.sys [172.16.1.254])
	by home.sys (8.11.6/8.11.6) with ESMTP id gA77IAr08697;
	Thu, 7 Nov 2002 02:18:14 -0500
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>, bug-commoncpp@gnu.org
Subject: Re: FreeBSD Problems
Date: Thu, 7 Nov 2002 02:18:09 -0500
User-Agent: KMail/1.4.3
References: <Pine.GSO.4.33.0211011939380.21865-100000@agassiz.cs.und.edu> <Pine.LNX.4.44.0211022012370.30772-100000@home.sys> <20021106133116.GA14059@bulbasaur.rediris.es>
In-Reply-To: <20021106133116.GA14059@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211070218.09733.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 will need to try a full Bayonne build under FreeBSD again...

On Wednesday 06 November 2002 08:31, Federico Montesino Pouzols wrote:
> With the "extern" trick it seems to compile and work well. The
> fix is in CVS.
>
> =09The time.h of FreeBSD does not declare nanosleep unless you
> define a very peculiar symbol for posix 1003.1b.
>
> On Sat, Nov 02, 2002 at 08:13:07PM -0500, David Sugar wrote:
> > Well, let's see if we can solve the first problem immediately in the
> > distrubution and then get a nice "ports" package that is current...
> >
> > On Fri, 1 Nov 2002, Ari Johnson wrote:
> > > I'd say that the native thread library is the way to go.  FreeBSD
> > > implements pthreads quite nicely, and I've had excellent luck using
> > > them with CommonC++.  The problems come in with things like friends=
=2Ecpp
> > > failing to compile because nanosleep() isn't declared (putting an
> > > extern "C" declaration for it right where it's used in a macro in
> > > cc++/config.h works for me), and the fact that I absolutely cannot
> > > compile the library with GCC 3.x, due to some kind of screwy includ=
e
> > > file monkey business; although I can compile anything else with GCC=
 3.x
> > > just fine.
> > >  -- Ari Johnson
> > >
> > > On Fri, 1 Nov 2002, David Sugar wrote:
> > > > I would like to see us have a clean and consistent build under
> > > > FreeBSD. Currently, there are two choices possible with it; one t=
o
> > > > build against LinuxThreads, and one to do so with the native runt=
ime
> > > > thread library. Which do you think would be better for FreeBSD?
> > > >
> > > > David
> > > >
> > > > On Fri, 1 Nov 2002, Ari Johnson wrote:
> > > > > I think I'm going to just sit down and try to figure out what's
> > > > > wrong with CommonC++ (from cvs) on FreeBSD.  I keep figuring ou=
t a
> > > > > quick hack around things, but they are things that should be fi=
xed.
> > > > >  So here's #1:
> > > > >
> > > > > friends.cpp: In function `static void ost::Thread::sleep(long
> > > > > unsigned int)': friends.cpp:134: implicit declaration of functi=
on
> > > > > `int ost::nanosleep(...)'
> > > > >
> > > > > Anyone with insight as to why this is occurring?
> > > > >  -- Ari Johnson
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Bug-commoncpp mailing list
> > > > > Bug-commoncpp@gnu.org
> > > > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > >
> > > _______________________________________________
> > > Bug-commoncpp mailing list
> > > Bug-commoncpp@gnu.org
> > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From fedemp@bulbasaur.rediris.es Thu Nov 07 08:28:09 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 189mhc-0001Mq-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 08:28:08 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 189mhT-0001Kf-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 08:28:06 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 189mhS-0001KI-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 08:27:58 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 189miB-0000tq-00
	for <bug-commoncpp@gnu.org>; Thu, 07 Nov 2002 14:28:43 +0100
Date: Thu, 7 Nov 2002 14:28:42 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: Patch for connecting SocketPort constructor
Message-ID: <20021107132841.GA2573@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <200211062103.20284.cproch@seculogix.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200211062103.20284.cproch@seculogix.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	It is in CVS, for both 1.1 (HEAD) and 1.0 (-rRELEASE1). I have
also included your comments for the constructor doc.

	If you are using SocketService, it may be of interest to you
some mails that have been posted to this list very recently and at the
beginning of the past month.

On Wed, Nov 06, 2002 at 09:03:20PM +0100, Prochnow, Christian wrote:
> Hi,
> 
> i've patched the SocketPort class a bit to provide a non-blocking constructor 
> for outbound tcp connections.
> To detect when the connection is established, overload SocketPort::output().
> SocketPort::output()  get's called by the SocketService when the connection is 
> ready, SocketPort::disconnect() when the connect failed. 
> at the moment you should set the socket state to "CONNECTED" when 
> SocketPort::output() get's called for the first time, which i think should 
> eventually be done in SocketService.
> 
> Regards, 
> Christian Prochnow






From cproch@seculogix.de Thu Nov 07 17:29:33 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 189v9Y-0000tv-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 17:29:32 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 189v9W-0000sa-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 17:29:31 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 189ui1-0001fk-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 17:01:05 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP id 1D6C113ADC
	for <bug-commoncpp@gnu.org>; Thu,  7 Nov 2002 22:58:38 +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: Socket error handling
Date: Thu, 7 Nov 2002 23:01:03 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211072301.03372.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 List,

i'm wondering how one can do proper errorhandling using the throwExceptio=
n=20
error mode and the Socket class?
The SockException class which gets thrown should at least contain the err=
or=20
code which caused the throw - without it it's simply useless.=20
A textual error message retrieved from the O/S is also usefull when passi=
ng=20
error messages down to the user and should be passed on each call to=20
Socket::error().
eg.
error(errBindingFailed,strerror(errno);

Using the SocketPort class there should also a way to retrieve the error =
which=20
caused the disconnect-event.

Regards,
Christian Prochnow




From fedemp@bulbasaur.rediris.es Fri Nov 08 05:07:49 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18A63J-0005DO-00
	for bug-commoncpp@gnu.org; Fri, 08 Nov 2002 05:07:49 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18A63F-0005Cc-00
	for bug-commoncpp@gnu.org; Fri, 08 Nov 2002 05:07:48 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18A63E-0005Bk-00
	for bug-commoncpp@gnu.org; Fri, 08 Nov 2002 05:07:45 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18A63s-0000CM-00
	for <bug-commoncpp@gnu.org>; Fri, 08 Nov 2002 11:08:24 +0100
Date: Fri, 8 Nov 2002 11:08:24 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: Socket error handling
Message-ID: <20021108100824.GA255@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <200211072301.03372.cproch@seculogix.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200211072301.03372.cproch@seculogix.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	I agree, a descriptive error string should be provided to
error() and the exception object constructors. It seems that currently
there is no check for strerror_r, so it may be necessary to add a
check for that and use strerror_r whenever possible.

	Perhaps we should add a parameter to SocketPort::disconnect to
indicate the disconnection reason. Socket::error may not be the most
adequate type, since the kind of errors that can be detected is more
related to the error codes that can be retrieved from select/poll
(ERROR, HUP, CLOSE, etc.)

On Thu, Nov 07, 2002 at 11:01:03PM +0100, Prochnow, Christian wrote:
> Hi List,
> 
> i'm wondering how one can do proper errorhandling using the throwException 
> error mode and the Socket class?
> The SockException class which gets thrown should at least contain the error 
> code which caused the throw - without it it's simply useless. 
> A textual error message retrieved from the O/S is also usefull when passing 
> error messages down to the user and should be passed on each call to 
> Socket::error().
> eg.
> error(errBindingFailed,strerror(errno);
> 
> Using the SocketPort class there should also a way to retrieve the error which 
> caused the disconnect-event.
> 
> Regards,
> Christian Prochnow
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Sat Nov 09 09:35:00 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18AWhQ-0001Ai-00
	for bug-commoncpp@gnu.org; Sat, 09 Nov 2002 09:35:00 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18AWgu-000162-00
	for bug-commoncpp@gnu.org; Sat, 09 Nov 2002 09:34:59 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18AWgt-00014n-00
	for bug-commoncpp@gnu.org; Sat, 09 Nov 2002 09:34:27 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gA9ExR029060;
	Sat, 9 Nov 2002 09:59:28 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Sat, 9 Nov 2002 09:59:27 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: fedemp@altern.org
cc: bug-commoncpp@gnu.org
Subject: GNU Common C++ "2" 1.1, GNU pth, and NGPT
Message-ID: <Pine.LNX.4.44.0211090944180.28882-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/>

While there are a number of smaller issues that need to be resolved and 
finalized for a 1.1 release, including if the ccssl library will be part 
of it, if Dan's threadsafe streaming will be integrated fully, etc, there 
is one issue until now that has been left unaddressed, the question of how 
we should handle GNU pth and the NGPT thread libraries...

My thought on this is that GNU pth should be an alternate compilable 
build.  Normally one builds ccgnu2 which everything then is linked to.  In 
this scenario, an alternate ccpth2 would be created, and everything could 
alternately be linked to that.  This would allow one to have a choice of 
threading environment and characteristics (native, or portable) and to 
make that choice by which one is chosen at link time.

With the newer versions of autoconfig and automake it is possible to have
one set of sources build two or more different sets of objects since the
.o files are uniquely named by target.  However, this is not possible with
older and more common releases of automake and autoconf, however.  Hence
my proposal is to have a seperate pth subdirectory (along with src and
win32), and have the pth subdirectory build a ccpth library, often out of
the same source files as were used for ccgnu2, but with a CCXX_PTH
defined.  Assuming the base classes offer no alignment variances (and this
will be done through the headers), ccext2 and other things should then be
linkable against either ccgnu2 or ccpth2, and an option could be added to
ccgnu2-config to request linkage and compile time options for ccpth rather
than for ccgnu.

The curious question is what happens with platforms that have no native 
thread support at all, but do have a port of pth.  Should pth then become 
the ccgnu2 on those platforms?  




From danielb@obfuscation.dyndns.org Mon Nov 11 08:14:41 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18BEOm-0002hw-00
	for bug-commoncpp@gnu.org; Mon, 11 Nov 2002 08:14:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18BEOd-0002HI-00
	for bug-commoncpp@gnu.org; Mon, 11 Nov 2002 08:14:35 -0500
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 18BEOc-0002At-00
	for bug-commoncpp@gnu.org; Mon, 11 Nov 2002 08:14:30 -0500
Received: from obfuscation.dyndns.org ([192.168.1.2] ident=mail)
	by frell.dyndns.org with esmtp (Exim 3.36 #1 (Debian))
	id 18BEOX-0005zX-00
	for <bug-commoncpp@gnu.org>; Mon, 11 Nov 2002 07:14:25 -0600
Received: from danielb by obfuscation.dyndns.org with local (Exim 3.36 #1 (Debian))
	id 18BEOU-00054y-00
	for <bug-commoncpp@gnu.org>; Mon, 11 Nov 2002 07:14:22 -0600
Date: Mon, 11 Nov 2002 07:14:22 -0600
From: Daniel E Baumann <baumannd@msoe.edu>
To: bug-commoncpp@gnu.org
Subject: ost::Event and multiple wait()s
Message-ID: <20021111131421.GA19520@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/>

I was just wondering if it is possible for multiple threads to wait on
an Event and for it to pick one of them to run when calling
signal(). Looks to me that it is possible becase it uses a condition
variable. I just wanted to confirm this. I need to write a boolean
lock class and would like this capability.

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 apavloff@eason.com Tue Nov 12 20:24:14 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18BmGL-0002ap-00
	for bug-commoncpp@gnu.org; Tue, 12 Nov 2002 20:24:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18BmGJ-0002Xw-00
	for bug-commoncpp@gnu.org; Tue, 12 Nov 2002 20:24:12 -0500
Received: from b.smtp-out.sonic.net ([208.201.224.39])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 18BmGI-0002Xa-00
	for bug-commoncpp@gnu.org; Tue, 12 Nov 2002 20:24:10 -0500
Received: (qmail 32496 invoked from network); 13 Nov 2002 01:24:07 -0000
Received: from turbo.sonic.net (208.201.224.26)
  by b.smtp-out.sonic.net with SMTP; 13 Nov 2002 01:24:07 -0000
Received: from mailman.eason.com (adsl-209-204-139-80.sonic.net [209.204.139.80])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id gAD1O7F23208
	for <bug-commoncpp@gnu.org>; Tue, 12 Nov 2002 17:24:07 -0800
X-envelope-info: <apavloff@eason.com>
Received: by mailman.eason.com with Internet Mail Service (5.5.2653.19)
	id <WYSDGSM8>; Tue, 12 Nov 2002 17:24:06 -0800
Message-ID: <D3AF5F134D627243993F2F2FC32EE4D229C41E@mailman.eason.com>
From: Alex Pavloff <apavloff@eason.com>
To: bug-commoncpp@gnu.org
Subject: MappedFile constructors
Date: Tue, 12 Nov 2002 17:24:05 -0800
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/>

Both ost::MappedFile constructors take an ost::File::Access parameter.
ost::File::Access is declared protected.  The constructors are
public.Obviously, something's not right, as of course, you can't create a
MappedFile unless you derive from it.  

So:  

Are the MappedFile constructors supposed to be protected or is File::Access
supposed to be public? 

I'm guessing that File::Access needs to be fixed, because both SharedFile
and ThreadFile have public constructors that work, which I believe implies
that they're supposed to be used as is.

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



From cproch@freiverkehr.de Wed Nov 13 08:25:40 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18BxWW-000071-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 08:25:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18BxWM-0008W3-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 08:25:38 -0500
Received: from h-62.96.239.30.host.de.colt.net ([62.96.239.30] helo=mail.freiverkehr.de)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18BxUh-00086c-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 08:23:47 -0500
Received: from cproch.freiverkehr.de (CPROCH [10.100.101.37]) by mail.freiverkehr.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id WX6044L7; Wed, 13 Nov 2002 14:23:45 +0100
From: "Prochnow, Christian" <cproch@freiverkehr.de>
Organization: Berliner Freiverkehr AG
To: bug-commoncpp@gnu.org
Subject: Network Device Informations
Date: Wed, 13 Nov 2002 14:26:23 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="------------Boundary-00=_ZZNIYHZ3B9MWK85SWD0S"
Message-Id: <200211131426.23465.cproch@freiverkehr.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/>

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

Hi List,

For a networking application i needed to query a list of Network Devices =
and=20
their Broadcast addresses to ignore Broadcasts from my own. Here's the=20
solution which i think is of interest for implementing it in Common C++.

This solution is tested under Linux, but should also work under other UNI=
X=20
systems which needs to be verified. Win32 stuff is also implemented, but=20
untested. I also did'nt find a way to get the MTU under Win32 without bra=
king=20
compatibility with Win95 (with >=3D Win98 it is possible to get the MTU v=
ia MIB=20
extensions).



Regards,
Christian Prochnow


--------------Boundary-00=_ZZNIYHZ3B9MWK85SWD0S
Content-Type: text/x-chdr;
  charset="us-ascii";
  name="network.h"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="network.h"

// Copyright (C) 2002 Christian Prochnow <cproch@seculogix.de>
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation; either version 2 of the License, or
// (at your option) any later version.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software
// Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
//
// As a special exception to the GNU General Public License, permission is
// granted for additional uses of the text contained in its release
// of Common C++.
//
// The exception is that, if you link the Common C++ library with other files
// to produce an executable, this does not by itself cause the
// resulting executable to be covered by the GNU General Public License.
// Your use of that executable is in no way restricted on account of
// linking the Common C++ library code into it.
//
// This exception does not however invalidate any other reasons why
// the executable file might be covered by the GNU General Public License.
//
// This exception applies only to the code released under the
// name Common C++.  If you copy code from other releases into a copy of
// Common C++, as the General Public License permits, the exception does
// not apply to the code that you add in this way.  To avoid misleading
// anyone as to the status of such modified files, you must delete
// this exception notice from them.
//
// If you write modifications of your own for Common C++, it is your choice
// whether to permit this exception to apply to your modifications.
// If you do not wish that, delete this exception notice.

#ifndef CCXX_NETWORK_H_
#define CCXX_NETWORK_H_

#ifndef WIN32
#include <cc++/config.h>
#endif

#include <cc++/socket.h>
#include <string>
#include <vector>

#ifdef	CCXX_NAMESPACES
namespace ost {
#endif

//! Network device information class
/*!
	This class is used to hold various informations about a TCP/IP
	network device. Which can be obtained by a call to enumNetworkDevices()
	\author Christian Prochnow <cproch@seculogix.de>
*/
class CCXX_CLASS_EXPORT NetworkDeviceInfo {
	private:
		std::string _name;
		InetHostAddress _addr;
		BroadcastAddress _broadcast;
		InetMaskAddress _netmask;
		int _mtu;

	protected:
		NetworkDeviceInfo(const std::string& name, const InetHostAddress& addr,
			const BroadcastAddress& broadcast, const InetMaskAddress& netmask,
			int mtu);

	public:
		NetworkDeviceInfo(const NetworkDeviceInfo& ndi);
		~NetworkDeviceInfo();

		//! Returns the Name of the network device
		inline const std::string& name() const
		{ return _name; }

		//! Returns the Address of the network device
		inline const InetHostAddress& address() const
		{ return _addr; }

		//! Returns the Broadcast address of the network device
		inline const BroadcastAddress& broadcast() const
		{ return _broadcast; }

		//! Returns the Netmask of the network device
		inline const InetMaskAddress& netmask() const
		{ return _netmask; }

		//! Returns the MTU
		inline const int mtu() const
		{ return _mtu; }

		//! Enumerate all available network devices
		friend bool enumNetworkDevices(std::vector<NetworkDeviceInfo>& devs);

};

#ifdef	CCXX_NAMESPACES
}
#endif

#endif

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

// Copyright (C) 2002 Christian Prochnow <cproch@seculogix.de>
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation; either version 2 of the License, or
// (at your option) any later version.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software
// Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
//
// As a special exception to the GNU General Public License, permission is
// granted for additional uses of the text contained in its release
// of Common C++.
//
// The exception is that, if you link the Common C++ library with other files
// to produce an executable, this does not by itself cause the
// resulting executable to be covered by the GNU General Public License.
// Your use of that executable is in no way restricted on account of
// linking the Common C++ library code into it.
//
// This exception does not however invalidate any other reasons why
// the executable file might be covered by the GNU General Public License.
//
// This exception applies only to the code released under the
// name Common C++.  If you copy code from other releases into a copy of
// Common C++, as the General Public License permits, the exception does
// not apply to the code that you add in this way.  To avoid misleading
// anyone as to the status of such modified files, you must delete
// this exception notice from them.
//
// If you write modifications of your own for Common C++, it is your choice
// whether to permit this exception to apply to your modifications.
// If you do not wish that, delete this exception notice.

#include "network.h"

#ifndef WIN32
#include <sys/ioctl.h>
#include <net/if.h>
#else
#include <winsock2.h>
#endif

#ifdef	CCXX_NAMESPACES
namespace ost {
#endif

using namespace std;

NetworkDeviceInfo::NetworkDeviceInfo(const string& name, const InetHostAddress& addr,
	const BroadcastAddress& broadcast, const InetMaskAddress& netmask, int mtu)
: _name(name), _addr(addr), _broadcast(broadcast), _netmask(netmask), _mtu(mtu)
{}

NetworkDeviceInfo::NetworkDeviceInfo(const NetworkDeviceInfo& ndi)
: _name(ndi._name), _addr(ndi._addr), _broadcast(ndi._broadcast), _netmask(ndi._netmask), _mtu(ndi._mtu)
{}

NetworkDeviceInfo::~NetworkDeviceInfo()
{}

bool enumNetworkDevices(vector<NetworkDeviceInfo>& devs)
{
	devs.clear();

	#ifndef WIN32
	char buffer[8192];
	struct ifconf ifc;

	int fd = socket(AF_INET, SOCK_DGRAM, 0);
	if(fd == -1)
		return false;

	ifc.ifc_len = sizeof(buffer);
	ifc.ifc_buf = buffer;

	if(ioctl(fd, SIOCGIFCONF, &ifc) == -1)
		return false;

	InetHostAddress addr;
	BroadcastAddress brdaddr;
	sockaddr_in brdinaddr;
	InetMaskAddress maskaddr("255.255.255.255");
	sockaddr_in maskinaddr;
	int mtu;

	int count = ifc.ifc_len / sizeof(ifreq);
	for(int i = 0; i < count; ++i)
	{
		if(ifc.ifc_req[i].ifr_addr.sa_family != AF_INET)
			continue;

		addr = ((sockaddr_in&)ifc.ifc_req[i].ifr_addr).sin_addr;

		struct ifreq devifreq;
		strcpy(devifreq.ifr_name, ifc.ifc_req[i].ifr_name);

		if(ioctl(fd, SIOCGIFBRDADDR, &devifreq) == -1)
			(InetAddress&)brdaddr = htonl(INADDR_ANY);
		else
			(InetAddress&)brdaddr = ((sockaddr_in&)devifreq.ifr_broadaddr).sin_addr;

		if(ioctl(fd, SIOCGIFNETMASK, &devifreq) == -1)
			maskaddr = htonl(INADDR_BROADCAST);
		else
			(InetAddress&)maskaddr = ((sockaddr_in&)devifreq.ifr_netmask).sin_addr;

		if(ioctl(fd, SIOCGIFMTU, &devifreq) == -1)
			mtu = 0;
		else
			mtu = devifreq.ifr_mtu;

		devs.push_back(NetworkDeviceInfo(ifc.ifc_req[i].ifr_name, addr, brdaddr, maskaddr, mtu));
	}

  close(fd);
	#else // WIN32

	SOCKET s = WSASocket(AF_INET, SOCK_DGRAM, 0, 0, 0);
	if(s == INVALID_SOCKET)
	{
		if(WSAGetLastError() == WSANOTINITIALISED)
			WSADATA wsadata;
			WSAStartup(MAKEWORD(2,0),&wsadata);
		}
		else
			return false;
	}

	char outbuff[8192];
	DWORD outlen;
	DWORD ret = WSAIoctl(s, SIO_GET_INTERFACE_LIST, 0, 0, outbuff, sizeof(outbuff), &outlen, 0, 0);
	if(ret == SOCKET_ERROR)
		return false;

	INTERFACE_INFO* iflist = (INTERFACE_INFO*)buffer;
	int ifcount = outlen / sizeof(INTERFACE_INFO);

	InetHostAddress addr;
	BroadcastAddress brdaddr;
	InetMaskAddress maskaddr("255.255.255.255");

	for(int i = 0; i < ifcount; ++i)
	{
		addr = ((sockaddr_in&)iflist[i].iiAddress).sin_addr;
		brdaddr = ((sockaddr_in&)iflist[i].iiBroadcastAddress).sin_addr;
		maskaddr = ((sockaddr_in&)iflist[i].iiNetmask).sin_addr;

		devs.push_back(NetworkDeviceInfo("", addr, brdaddr, maskaddr, -1));
	}

	CloseHandle(s);
	#endif

	return true;
}

#ifdef	CCXX_NAMESPACES
}
#endif

--------------Boundary-00=_ZZNIYHZ3B9MWK85SWD0S--




From arunmad@fastmail.fm Wed Nov 06 21:37:50 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 189cYI-0001Z9-00
	for bug-commoncpp@gnu.org; Wed, 06 Nov 2002 21:37:50 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 189cYG-0001Yv-00
	for bug-commoncpp@gnu.org; Wed, 06 Nov 2002 21:37:49 -0500
Received: from fastmail.fm ([209.61.183.86] helo=www.fastmail.fm)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 189cYG-0001Yp-00
	for bug-commoncpp@gnu.org; Wed, 06 Nov 2002 21:37:48 -0500
Received: from www.fastmail.fm (localhost [127.0.0.1])
	by localhost.localdomain (Postfix) with ESMTP id 6FC016DAAE
	for <bug-commoncpp@gnu.org>; Wed,  6 Nov 2002 20:37:40 -0600 (CST)
Received: from server4.fastmail.fm (server4.internal [10.202.2.135])
	by www.fastmail.fm (Postfix) with ESMTP id 18C826DB5B
	for <bug-commoncpp@gnu.org>; Wed,  6 Nov 2002 20:37:40 -0600 (CST)
Received: by server4.fastmail.fm (Postfix, from userid 99)
	id CD66B2FD71; Wed,  6 Nov 2002 20:37:32 -0600 (CST)
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
X-Mailer: MIME::Lite 1.2  (F2.6; T1.001; A1.48; B2.12; Q2.03)
Date: Thu, 7 Nov 2002 02:37:35 UT
From: "Arun Madhurmohan" <arunmad@fastmail.fm>
To: bug-commoncpp@gnu.org
X-Epoch: 1036636660
X-Sasl-enc: 5hrwo6+2MHK0WFyszPPNVQ
Subject: compiling with irix CC
Message-Id: <20021107023732.CD66B2FD71@server4.fastmail.fm>
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,

Most of my work is compiled with the CC compiler on irix. So I would like
to compile common c++ with the same compiler to avoid any linking issues.
Looking at the help in the configure script I couldn't figure a way to
compile it with the native irix compiler. Is there a way to use the
native irix CC compiler to compile common c++?

thanks,
arun
-- 
http://fastmail.fm - Consolidate POP email and Hotmail in one place



From boumenot@crash.divebomb.org Fri Nov 08 13:17:37 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18ADhI-0002Vz-00
	for bug-commoncpp@gnu.org; Fri, 08 Nov 2002 13:17:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18ADhA-0002T5-00
	for bug-commoncpp@gnu.org; Fri, 08 Nov 2002 13:17:35 -0500
Received: from dsl092-068-032.bos1.dsl.speakeasy.net ([66.92.68.32] helo=crash.divebomb.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18ADZI-0000Lv-00
	for bug-commoncpp@gnu.org; Fri, 08 Nov 2002 13:09:21 -0500
Received: from crash.divebomb.org (localhost [127.0.0.1])
	by crash.divebomb.org (8.12.6/8.12.3) with ESMTP id gA8IAkNt057377
	for <bug-commoncpp@gnu.org>; Fri, 8 Nov 2002 13:10:46 -0500 (EST)
	(envelope-from boumenot@crash.divebomb.org)
Received: (from boumenot@localhost)
	by crash.divebomb.org (8.12.6/8.12.3/Submit) id gA8IAjwa057376
	for bug-commoncpp@gnu.org; Fri, 8 Nov 2002 13:10:45 -0500 (EST)
Date: Fri, 8 Nov 2002 13:10:45 -0500
From: Christopher Boumenot <boumenot@spam_bucket.divebomb.org>
To: bug-commoncpp@gnu.org
Subject: bug in unix.cpp
Message-ID: <20021108181045.GA57315@divebomb.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/>

Greetings,

I don't believe this was the intent of the author.  

--- unix.cpp.orig       Fri Nov  8 13:03:16 2002
+++ unix.cpp    Fri Nov  8 13:00:38 2002
@@ -464,7 +464,7 @@
  #ifdef WIN32
                if( WSAGetLastError() == WAEISCONN )
  #else
-               if( errno = EINPROGRESS )
+               if( errno == EINPROGRESS )
  #endif
                {
                        Socket::state = CONNECTING;

This is against Common C++ v2-1.0.3.  I found this while compiling with icc
on FreeBSD v4.7.  If you have any further questions please CC me.


Regards,
Christopher 



From alexkon@cs.huji.ac.il Thu Nov 07 09:33:18 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 189nig-0003SK-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 09:33:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 189nia-0003P5-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 09:33:15 -0500
Received: from cse.cs.huji.ac.il ([132.65.16.30] helo=cs.huji.ac.il)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 189niY-0003Nr-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 09:33:11 -0500
Received: from gx-82.cs.huji.ac.il ([132.65.180.82] ident=mail)
	by cs.huji.ac.il with esmtp
	id 189niV-000PBr-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 16:33:07 +0200
Received: from alexkon by gx-82.cs.huji.ac.il with local (Exim 3.35 #1)
	id 189niV-0001NK-00
	for bug-commoncpp@gnu.org; Thu, 07 Nov 2002 16:33:07 +0200
Content-Type: text/plain;
  charset="koi8-r"
From: Alexander Konovalenko <alexkon@cs.huji.ac.il>
To: bug-commoncpp@gnu.org
Subject: Preface to questions
Date: Thu, 7 Nov 2002 16:33:07 +0200
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211071633.07077.alexkon@cs.huji.ac.il>
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'm now going to delve in the CommonC++ code and docs and I anticipate=20
that a lot of questions will arise.

As far as I understand there is no any public mailing list for=20
CommonC++, so the questions should be sent to <bug-commoncpp@gnu.org>.

May I send them in short messages (a question per message), or do you=20
prefer to receive larger bunches of questions in one message?

Thank you in advance for your help.

 -- Alexander Konovalenko



From mikem@cyber.com.au Wed Nov 13 01:24:06 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18BqwY-0007SX-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 01:24:06 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18BqwU-0007Q5-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 01:24:05 -0500
Received: from plum.cyber.com.au ([203.7.155.24])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 18BqwS-0007Na-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 01:24:00 -0500
Received: from hard.office.cyber.com.au (hard.office.cyber.com.au [192.168.155.102]) by plum.cyber.com.au (8.6.12/8.6.6) with ESMTP id RAA02078 for <bug-commoncpp@gnu.org>; Wed, 13 Nov 2002 17:23:50 +1100
Subject: Trouble compiling 1.97
From: Mike MacCana <mikem@cyber.com.au>
To: bug-commoncpp@gnu.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 13 Nov 2002 17:25:21 +1100
Message-Id: <1037168722.16622.13550.camel@hard.office.cyber.com.au>
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/>

Hello,

I'm getting the following error when trying to compile commonc++. I'm
not sure of what other detail to provide other than the system is
generic Red Hat 8.0. Anyway, if you have any suggestions to avoid the
error I'd be most grateful.

Thanks a lot,

Mike

/bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.
-I../src -I/usr/include/libxml2    -I../src  -O2 -march=i386 -mcpu=i686
-D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -c mutex.cpp
rm -f .libs/mutex.lo
c++ -DHAVE_CONFIG_H -I. -I. -I. -I../src -I/usr/include/libxml2 -I../src
-O2 -march=i386 -mcpu=i686 -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -c
mutex.cpp  -fPIC -DPIC -o .libs/mutex.lo
In file included from config.h:449,
                 from mutex.cpp:41:
/usr/include/asm/atomic.h:40:2: warning: #warning Using kernel header in
userland program. BAD!
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:358: `atomic_add' 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.lo] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/CommonC++-1.9.7/src'
make: *** [install-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.18090 (%install)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.18090 (%install)

-- 
____________________________________________________________________________
Mike MacCana 	        Support Consultant            RHCE, MCSE, MCP+I
Cybersource: Providing Quality IT Professional Services for 11 Years
Specialists in Unix/Linux, TCP/IP and Web Application Development
Level 9, 140 Queen St, Melbourne.  Ph : 03 9642 5997 Fax: 03 9642 5998




From apavloff@eason.com Wed Nov 13 15:34:59 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C4Dy-00049n-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 15:34:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C4Dv-00049D-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 15:34:57 -0500
Received: from b.smtp-out.sonic.net ([208.201.224.39])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 18C4Dt-000490-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 15:34:54 -0500
Received: (qmail 10472 invoked from network); 13 Nov 2002 20:34:49 -0000
Received: from ultra.sonic.net (208.201.224.22)
  by b.smtp-out.sonic.net with SMTP; 13 Nov 2002 20:34:49 -0000
Received: from mailman.eason.com (adsl-209-204-139-80.sonic.net [209.204.139.80])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id gADKYng18528;
	Wed, 13 Nov 2002 12:34:49 -0800
X-envelope-info: <apavloff@eason.com>
Received: by mailman.eason.com with Internet Mail Service (5.5.2653.19)
	id <WYSDGSR5>; Wed, 13 Nov 2002 12:34:49 -0800
Message-ID: <D3AF5F134D627243993F2F2FC32EE4D229C421@mailman.eason.com>
From: Alex Pavloff <apavloff@eason.com>
To: "'Christopher Boumenot'" <boumenot@spam_bucket.divebomb.org>,
   bug-commoncpp@gnu.org
Subject: RE: bug in unix.cpp
Date: Wed, 13 Nov 2002 12:34:48 -0800
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/>

> I don't believe this was the intent of the author.  

Sure wasn't.  This was pointed out a week ago.  Seeing as how -Wall would
have caught this, should this be used on all compilations?

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



From fedemp@wanadoo.es Wed Nov 13 16:20:19 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C4vq-0000gl-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:20:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C4vk-0000ZC-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:20:15 -0500
Received: from [62.37.236.137] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C4vj-0000XF-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:20:11 -0500
Received: from risitas (62-36-186-114.dialup.uni2.es [62.36.186.114])
	by smtp.wanadoo.es (8.11.3/8.11.3) with ESMTP id gADLQF013505
	for <bug-commoncpp@gnu.org>; Wed, 13 Nov 2002 22:26:15 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18C4x1-0000Hv-00
	for <bug-commoncpp@gnu.org>; Wed, 13 Nov 2002 22:21:31 +0100
Date: Wed, 13 Nov 2002 22:21:31 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: compiling with irix CC
Message-ID: <20021113212131.GB667@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <20021107023732.CD66B2FD71@server4.fastmail.fm>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021107023732.CD66B2FD71@server4.fastmail.fm>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

On Thu, Nov 07, 2002 at 02:37:35AM +0000, Arun Madhurmohan wrote:
> Hi,
> 
> Most of my work is compiled with the CC compiler on irix. So I would like
> to compile common c++ with the same compiler to avoid any linking issues.
> Looking at the help in the configure script I couldn't figure a way to
> compile it with the native irix compiler. Is there a way to use the
> native irix CC compiler to compile common c++?
> 

	From what you say I understand you have both gcc and the
native irix CC installed and configure detects gcc? If so, you can
force the compiler to use like this:

	$ CC=c-compiler CXX=cpp-compiler ./configure ...

	for instance,

	$ CC=gcc CXX=g++ ./configure ...

> thanks,
> arun
> -- 
> http://fastmail.fm - Consolidate POP email and Hotmail in one place
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fedemp@wanadoo.es Wed Nov 13 16:26:04 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C51Q-0003xq-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:26:04 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C51N-0003x9-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:26:03 -0500
Received: from [62.37.236.135] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C51N-0003x1-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:26:01 -0500
Received: from risitas (62-36-186-114.dialup.uni2.es [62.36.186.114])
	by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id gADLeCw21014;
	Wed, 13 Nov 2002 22:40:13 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18C51p-0000IT-00; Wed, 13 Nov 2002 22:26:29 +0100
Date: Wed, 13 Nov 2002 22:26:28 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Alexander Konovalenko <alexkon@cs.huji.ac.il>
Cc: bug-commoncpp@gnu.org
Subject: Re: Preface to questions
Message-ID: <20021113212628.GD667@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Alexander Konovalenko <alexkon@cs.huji.ac.il>,
	bug-commoncpp@gnu.org
References: <200211071633.07077.alexkon@cs.huji.ac.il>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200211071633.07077.alexkon@cs.huji.ac.il>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

On Thu, Nov 07, 2002 at 04:33:07PM +0200, Alexander Konovalenko wrote:
> Hello,
> 
> I'm now going to delve in the CommonC++ code and docs and I anticipate 
> that a lot of questions will arise.
> 
> As far as I understand there is no any public mailing list for 
> CommonC++, so the questions should be sent to <bug-commoncpp@gnu.org>.
> 
	
	Well, bug-commoncpp is used for public discussions about cc++.

> May I send them in short messages (a question per message), or do you 
> prefer to receive larger bunches of questions in one message?
> 

	As you prefer.

> Thank you in advance for your help.
> 
>  -- Alexander Konovalenko
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From fedemp@wanadoo.es Wed Nov 13 16:31:11 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C56N-0005N0-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:31:11 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C56J-0005Ki-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:31:09 -0500
Received: from [62.37.236.137] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C56I-0005Ji-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:31:06 -0500
Received: from risitas (62-36-186-114.dialup.uni2.es [62.36.186.114])
	by smtp.wanadoo.es (8.11.3/8.11.3) with ESMTP id gADLb7015994;
	Wed, 13 Nov 2002 22:37:07 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18C57X-0000J4-00; Wed, 13 Nov 2002 22:32:23 +0100
Date: Wed, 13 Nov 2002 22:32:23 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Alex Pavloff <apavloff@eason.com>
Cc: "'Christopher Boumenot'" <boumenot@spam_bucket.divebomb.org>,
   bug-commoncpp@gnu.org
Subject: Re: bug in unix.cpp
Message-ID: <20021113213223.GE667@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Alex Pavloff <apavloff@eason.com>,
	'Christopher Boumenot' <boumenot@spam_bucket.divebomb.org>,
	bug-commoncpp@gnu.org
References: <D3AF5F134D627243993F2F2FC32EE4D229C421@mailman.eason.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D3AF5F134D627243993F2F2FC32EE4D229C421@mailman.eason.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, this, as well as some others bugs, is fixed in CVS. I
agree, it would be helpful to add -Wall and maybe even some other more
restrictive flags. In fact, the are some little problems in the
current code that can be detected with that flags. They will be fixed
soon.

On Wed, Nov 13, 2002 at 12:34:48PM -0800, Alex Pavloff wrote:
> 
> > I don't believe this was the intent of the author.  
> 
> Sure wasn't.  This was pointed out a week ago.  Seeing as how -Wall would
> have caught this, should this be used on all compilations?
> 
> 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 fedemp@wanadoo.es Wed Nov 13 16:37:38 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C5Cb-0007cF-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:37:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C5CX-0007YG-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:37:36 -0500
Received: from [62.37.236.137] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C5CW-0007XV-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:37:32 -0500
Received: from risitas (62-36-186-114.dialup.uni2.es [62.36.186.114])
	by smtp.wanadoo.es (8.11.3/8.11.3) with ESMTP id gADLhY017347
	for <bug-commoncpp@gnu.org>; Wed, 13 Nov 2002 22:43:34 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18C5Dn-0000JU-00
	for <bug-commoncpp@gnu.org>; Wed, 13 Nov 2002 22:38:51 +0100
Date: Wed, 13 Nov 2002 22:38:50 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: ost::Event and multiple wait()s
Message-ID: <20021113213850.GF667@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <20021111131421.GA19520@obfuscation.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021111131421.GA19520@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/>

	If you want only one thread to be picked, I think Event will
not work. Event::signal uses pthread_cond_broadcast, so all waiting
threads will be reactivated. Conditional however has a signal method
that allows to specify whether to use pthread_cond_broadcast or
pthread_cond_signal.

On Mon, Nov 11, 2002 at 07:14:22AM -0600, Daniel E Baumann wrote:
> I was just wondering if it is possible for multiple threads to wait on
> an Event and for it to pick one of them to run when calling
> signal(). Looks to me that it is possible becase it uses a condition
> variable. I just wanted to confirm this. I need to write a boolean
> lock class and would like this capability.
> 
> 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



From fedemp@wanadoo.es Wed Nov 13 16:40:36 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C5FT-0000Er-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:40:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C5FQ-0000Cl-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:40:34 -0500
Received: from [62.37.236.136] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C5FQ-0000Ch-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:40:32 -0500
Received: from risitas (62-36-186-114.dialup.uni2.es [62.36.186.114])
	by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id gADLW1923492
	for <bug-commoncpp@gnu.org>; Wed, 13 Nov 2002 22:32:01 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18C5Gl-0000Je-00
	for <bug-commoncpp@gnu.org>; Wed, 13 Nov 2002 22:41:55 +0100
Date: Wed, 13 Nov 2002 22:41:55 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: MappedFile constructors
Message-ID: <20021113214155.GG667@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <D3AF5F134D627243993F2F2FC32EE4D229C41E@mailman.eason.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D3AF5F134D627243993F2F2FC32EE4D229C41E@mailman.eason.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 also seems to me that File::Access should be public, and a
quick look makes me think that File::Error should also made
public. Any other opinion?

On Tue, Nov 12, 2002 at 05:24:05PM -0800, Alex Pavloff wrote:
> 
> Both ost::MappedFile constructors take an ost::File::Access parameter.
> ost::File::Access is declared protected.  The constructors are
> public.Obviously, something's not right, as of course, you can't create a
> MappedFile unless you derive from it.  
> 
> So:  
> 
> Are the MappedFile constructors supposed to be protected or is File::Access
> supposed to be public? 
> 
> I'm guessing that File::Access needs to be fixed, because both SharedFile
> and ThreadFile have public constructors that work, which I believe implies
> that they're supposed to be used as is.
> 
> 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 fedemp@wanadoo.es Wed Nov 13 16:45:18 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C5K1-0001nY-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:45:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C5Jy-0001mc-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:45:17 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C5Jx-0001m1-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:45:13 -0500
Received: from risitas (62-36-186-114.dialup.uni2.es [62.36.186.114])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAE4g2209326
	for <bug-commoncpp@gnu.org>; Thu, 14 Nov 2002 05:42:02 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18C5LH-0000Jx-00
	for <bug-commoncpp@gnu.org>; Wed, 13 Nov 2002 22:46:35 +0100
Date: Wed, 13 Nov 2002 22:46:35 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: Trouble compiling 1.97
Message-ID: <20021113214635.GH667@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <1037168722.16622.13550.camel@hard.office.cyber.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1037168722.16622.13550.camel@hard.office.cyber.com.au>
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 was a serious bug, it is fixed since the release 1.0.4 of
Common C++ 2. If understand that you are using 1.9.7, if so, I
recommend you to upgrade to CC++ 2. You may want to get it from
ftp://ftp.gnu.org/pub/gnu/commoncpp/ (use ftp, not http, as there are
some problems with http.)

On Wed, Nov 13, 2002 at 05:25:21PM +1100, Mike MacCana wrote:
> Hello,
> 
> I'm getting the following error when trying to compile commonc++. I'm
> not sure of what other detail to provide other than the system is
> generic Red Hat 8.0. Anyway, if you have any suggestions to avoid the
> error I'd be most grateful.
> 
> Thanks a lot,
> 
> Mike
> 



From fedemp@wanadoo.es Wed Nov 13 16:53:02 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C5RV-0004Cj-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:53:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C5RO-0004AW-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:52:59 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C5RN-0004A0-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 16:52:53 -0500
Received: from risitas (62-36-186-114.dialup.uni2.es [62.36.186.114])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAE4na213113;
	Thu, 14 Nov 2002 05:49:36 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18C5Sb-0000KJ-00; Wed, 13 Nov 2002 22:54:09 +0100
Date: Wed, 13 Nov 2002 22:54:09 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Prochnow, Christian" <cproch@freiverkehr.de>
Cc: bug-commoncpp@gnu.org
Subject: Re: Network Device Informations
Message-ID: <20021113215409.GI667@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: "Prochnow, Christian" <cproch@freiverkehr.de>,
	bug-commoncpp@gnu.org
References: <200211131426.23465.cproch@freiverkehr.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200211131426.23465.cproch@freiverkehr.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Ummm, I think this adds interesting features. I think this
should be added soon to the unstable branch, at least. I will do some
tests, tell us if you check it works on other platforms, as I believe
that some of the system calls may be problematic.

On Wed, Nov 13, 2002 at 02:26:23PM +0100, Prochnow, Christian wrote:
> Hi List,
> 
> For a networking application i needed to query a list of Network Devices and 
> their Broadcast addresses to ignore Broadcasts from my own. Here's the 
> solution which i think is of interest for implementing it in Common C++.
> 
> This solution is tested under Linux, but should also work under other UNIX 
> systems which needs to be verified. Win32 stuff is also implemented, but 
> untested. I also did'nt find a way to get the MTU under Win32 without braking 
> compatibility with Win95 (with >= Win98 it is possible to get the MTU via MIB 
> extensions).
> 
> 
> 
> Regards,
> Christian Prochnow
> 






From fedemp@wanadoo.es Wed Nov 13 17:23:34 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C5v4-0003v5-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 17:23:34 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C5v0-0003uh-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 17:23:33 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C5uz-0003uZ-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 17:23:29 -0500
Received: from risitas (62-36-186-114.dialup.uni2.es [62.36.186.114])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAE5KA231468;
	Thu, 14 Nov 2002 06:20:11 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18C5wC-0000RO-00; Wed, 13 Nov 2002 23:24:44 +0100
Date: Wed, 13 Nov 2002 23:24:43 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Cc: fedemp@altern.org, bug-commoncpp@gnu.org
Subject: Re: GNU Common C++ "2" 1.1, GNU pth, and NGPT
Message-ID: <20021113222443.GK667@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: David Sugar <dyfet@ostel.com>, fedemp@altern.org,
	bug-commoncpp@gnu.org
References: <Pine.LNX.4.44.0211090944180.28882-100000@home.sys>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0211090944180.28882-100000@home.sys>
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, Nov 09, 2002 at 09:59:27AM -0500, David Sugar wrote:
> My thought on this is that GNU pth should be an alternate compilable 
> build.  Normally one builds ccgnu2 which everything then is linked to.  In 
> this scenario, an alternate ccpth2 would be created, and everything could 
> alternately be linked to that.  This would allow one to have a choice of 
> threading environment and characteristics (native, or portable) and to 
> make that choice by which one is chosen at link time.
> 

	I recall I have read there was the intention to make cc++ work
well with pth. Having two threading environments selectable at link
time would certainly be a shocking feature.

> my proposal is to have a seperate pth subdirectory (along with src and
> win32), and have the pth subdirectory build a ccpth library, often out of
> the same source files as were used for ccgnu2, but with a CCXX_PTH
> defined.  Assuming the base classes offer no alignment variances (and this
> will be done through the headers), ccext2 and other things should then be
> linkable against either ccgnu2 or ccpth2, and an option could be added to
> ccgnu2-config to request linkage and compile time options for ccpth rather
> than for ccgnu.
> 

	I think we should also add two exclusive symbols:
COMMON_PORTABLE_THREADING and COMMON_NATIVE_THREADING. CCXX_PTH would
fall whithin COMMON_PORTALE_THREADING.

> The curious question is what happens with platforms that have no native 
> thread support at all, but do have a port of pth.  Should pth then become 
> the ccgnu2 on those platforms?  
> 

	I think it should, it is a very elegant solution.



From apavloff@eason.com Wed Nov 13 17:32:22 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C63Z-0006qB-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 17:32:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C63X-0006pT-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 17:32:20 -0500
Received: from b.smtp-out.sonic.net ([208.201.224.39])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 18C63X-0006pP-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 17:32:19 -0500
Received: (qmail 29660 invoked from network); 13 Nov 2002 22:32:18 -0000
Received: from turbo.sonic.net (208.201.224.26)
  by b.smtp-out.sonic.net with SMTP; 13 Nov 2002 22:32:18 -0000
Received: from mailman.eason.com (adsl-209-204-139-80.sonic.net [209.204.139.80])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id gADMWI431210
	for <bug-commoncpp@gnu.org>; Wed, 13 Nov 2002 14:32:18 -0800
X-envelope-info: <apavloff@eason.com>
Received: by mailman.eason.com with Internet Mail Service (5.5.2653.19)
	id <WYSDGSS7>; Wed, 13 Nov 2002 14:32:17 -0800
Message-ID: <D3AF5F134D627243993F2F2FC32EE4D229C423@mailman.eason.com>
From: Alex Pavloff <apavloff@eason.com>
To: bug-commoncpp@gnu.org
Subject: Exception documentation
Date: Wed, 13 Nov 2002 14:32:16 -0800
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/>

I'm trying to use ost::MappedFile, and I'm doing something wrong, so its
throwing exceptions.  The problem is that

1) The possible exceptions thrown by each functoin are not documented.
2) The exceptions themselves (ost::Exception,FileException, IOException...)
aren't in the documentation at all.  

This makes things harder than they have to be.

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



From fedemp@wanadoo.es Wed Nov 13 17:50:30 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C6L8-0005Zp-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 17:50:30 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C6L6-0005Yk-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 17:50:29 -0500
Received: from [62.37.236.136] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C6L5-0005Wy-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 17:50:27 -0500
Received: from risitas (62-36-186-114.dialup.uni2.es [62.36.186.114])
	by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id gADMff909870;
	Wed, 13 Nov 2002 23:41:42 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18C6MA-0002M2-00; Wed, 13 Nov 2002 23:51:34 +0100
Date: Wed, 13 Nov 2002 23:51:34 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ari Johnson <ariston@cs.und.edu>
Cc: Federico Montesino Pouzols <fedemp@altern.org>,
   David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org
Subject: Re: Suggestion regarding header files...
Message-ID: <20021113225134.GL667@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Ari Johnson <ariston@cs.und.edu>,
	Federico Montesino Pouzols <fedemp@altern.org>,
	David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org
References: <20021102150248.GA1846@risitas> <Pine.GSO.4.33.0211022150120.23474-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.0211022150120.23474-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/>

	It is in CVS for next releases.

On Sat, Nov 02, 2002 at 09:50:16PM -0600, Ari Johnson wrote:
> 
> I like that solution.
> 
> On Sat, 2 Nov 2002, Federico Montesino Pouzols wrote:
> 
> >
> > 	Currently, the autoconf stuff defines two symbols:
> > COMMON_XML_PARSING (A) and HAVE_LIBXML (B). Only B is used for the
> > #ifdefs. Using both A and B we could do things like this:
> >
> > #if defined(A) && defined(B)
> > 	// libxml based stuff as it is currently defined.
> > #if defined(A) && !defined(B)
> > 	// at present, #error "libxml not installed"
> > 	// in the future, check another HAVE_... alternative xml lib.
> > #if !defined(A)
> > 	// put in xml.cpp something like #warning "XML support is not
> > 	// being compiled, are you sure?". And put in xml.h #error
> > 	// "XML support not available"
> >



From dyfet@ostel.com Wed Nov 13 18:13:23 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C6hG-0002Js-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:13:22 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C6hF-0002Jd-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:13:22 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C6hE-0002JQ-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:13:20 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gADNcJM30943;
	Wed, 13 Nov 2002 18:38:19 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 13 Nov 2002 18:38:19 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: Alexander Konovalenko <alexkon@cs.huji.ac.il>, <bug-commoncpp@gnu.org>
Subject: Re: Preface to questions
In-Reply-To: <20021113212628.GD667@risitas>
Message-ID: <Pine.LNX.4.44.0211131837250.30932-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 subscription to this list is open, you just need to send a subscribe 
message to bug-commoncpp-request@gnu.org.

On Wed, 13 Nov 2002, Federico Montesino Pouzols wrote:

> On Thu, Nov 07, 2002 at 04:33:07PM +0200, Alexander Konovalenko wrote:
> > Hello,
> > 
> > I'm now going to delve in the CommonC++ code and docs and I anticipate 
> > that a lot of questions will arise.
> > 
> > As far as I understand there is no any public mailing list for 
> > CommonC++, so the questions should be sent to <bug-commoncpp@gnu.org>.
> > 
> 	
> 	Well, bug-commoncpp is used for public discussions about cc++.
> 
> > May I send them in short messages (a question per message), or do you 
> > prefer to receive larger bunches of questions in one message?
> > 
> 
> 	As you prefer.
> 
> > Thank you in advance for your help.
> > 
> >  -- Alexander Konovalenko
> > 
> > 
> > _______________________________________________
> > 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 Nov 13 18:14:25 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C6iH-0002e2-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:14:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C6iE-0002bv-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:14:23 -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 18C6iD-0002br-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:14:22 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gADNe1o30959;
	Wed, 13 Nov 2002 18:40:01 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 13 Nov 2002 18:40:00 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: ost::Event and multiple wait()s
In-Reply-To: <20021113213850.GF667@risitas>
Message-ID: <Pine.LNX.4.44.0211131838540.30932-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/>

"Event" is meant to simulate the behavior of win32 "event" objects, so the 
behavior is consistent with that. 

On Wed, 13 Nov 2002, Federico Montesino Pouzols wrote:

> 
> 	If you want only one thread to be picked, I think Event will
> not work. Event::signal uses pthread_cond_broadcast, so all waiting
> threads will be reactivated. Conditional however has a signal method
> that allows to specify whether to use pthread_cond_broadcast or
> pthread_cond_signal.
> 
> On Mon, Nov 11, 2002 at 07:14:22AM -0600, Daniel E Baumann wrote:
> > I was just wondering if it is possible for multiple threads to wait on
> > an Event and for it to pick one of them to run when calling
> > signal(). Looks to me that it is possible becase it uses a condition
> > variable. I just wanted to confirm this. I need to write a boolean
> > lock class and would like this capability.
> > 
> > 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
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From dyfet@ostel.com Wed Nov 13 18:17:06 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C6kr-0004ir-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:17:05 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C6kl-0004SK-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:17:03 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C6ki-0004NH-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:16:57 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gADNgX630973;
	Wed, 13 Nov 2002 18:42:33 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 13 Nov 2002 18:42:33 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: "Prochnow, Christian" <cproch@freiverkehr.de>, <bug-commoncpp@gnu.org>
Subject: Re: Network Device Informations
In-Reply-To: <20021113215409.GI667@risitas>
Message-ID: <Pine.LNX.4.44.0211131841360.30932-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 is also the kind of things Common C++ is meant to be abstracting.  I 
agree it is something we should try to add.

On Wed, 13 Nov 2002, Federico Montesino Pouzols wrote:

> 
> 	Ummm, I think this adds interesting features. I think this
> should be added soon to the unstable branch, at least. I will do some
> tests, tell us if you check it works on other platforms, as I believe
> that some of the system calls may be problematic.
> 
> On Wed, Nov 13, 2002 at 02:26:23PM +0100, Prochnow, Christian wrote:
> > Hi List,
> > 
> > For a networking application i needed to query a list of Network Devices and 
> > their Broadcast addresses to ignore Broadcasts from my own. Here's the 
> > solution which i think is of interest for implementing it in Common C++.
> > 
> > This solution is tested under Linux, but should also work under other UNIX 
> > systems which needs to be verified. Win32 stuff is also implemented, but 
> > untested. I also did'nt find a way to get the MTU under Win32 without braking 
> > compatibility with Win95 (with >= Win98 it is possible to get the MTU via MIB 
> > extensions).
> > 
> > 
> > 
> > Regards,
> > Christian Prochnow
> > 
> 
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From dyfet@ostel.com Wed Nov 13 18:18:30 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C6mE-00056D-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:18:30 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C6mA-00054H-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:18:28 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C6mA-000545-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:18:26 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gADNi6F30983;
	Wed, 13 Nov 2002 18:44:06 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 13 Nov 2002 18:44:05 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: MappedFile constructors
In-Reply-To: <20021113214155.GG667@risitas>
Message-ID: <Pine.LNX.4.44.0211131842520.30932-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/>

Originally I had thought of MappedFile and File as internal classes, and 
yes, then they should have had protected constructors as well.  However, 
if one can make use of them as is, I see no reason to put artificial 
barriers in the way, and then yes, it should be public.



On Wed, 13 Nov 2002, Federico Montesino Pouzols wrote:

> 
> 	It also seems to me that File::Access should be public, and a
> quick look makes me think that File::Error should also made
> public. Any other opinion?
> 
> On Tue, Nov 12, 2002 at 05:24:05PM -0800, Alex Pavloff wrote:
> > 
> > Both ost::MappedFile constructors take an ost::File::Access parameter.
> > ost::File::Access is declared protected.  The constructors are
> > public.Obviously, something's not right, as of course, you can't create a
> > MappedFile unless you derive from it.  
> > 
> > So:  
> > 
> > Are the MappedFile constructors supposed to be protected or is File::Access
> > supposed to be public? 
> > 
> > I'm guessing that File::Access needs to be fixed, because both SharedFile
> > and ThreadFile have public constructors that work, which I believe implies
> > that they're supposed to be used as is.
> > 
> > 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
> 




From ariston@cs.und.edu Wed Nov 13 18:19:15 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C6mx-0005kG-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:19:15 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C6mu-0005g5-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:19:14 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C6mt-0005f8-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:19:11 -0500
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gADNRXsY027769
	for <bug-commoncpp@gnu.org>; Wed, 13 Nov 2002 17:27:34 -0600
Date: Wed, 13 Nov 2002 17:20:01 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
To: <bug-commoncpp@gnu.org>
Subject: friends.cpp won't compile on FreeBSD
Message-ID: <Pine.GSO.4.33.0211131718070.23742-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 else had any problems with this?  It'd really be great to not
have to hack things to get it to compile even with my default compiler
(gcc 2.95.x); once I get that working, maybe I'll worry about getting
CommonC++ to compile with gcc 3.x. :)

Ari Johnson





From dyfet@ostel.com Wed Nov 13 18:23:48 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C6rM-00007S-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:23:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C6rJ-00006d-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:23:47 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C6rJ-0008WT-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:23:45 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gADNnOn31011;
	Wed, 13 Nov 2002 18:49:24 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 13 Nov 2002 18:49:24 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: GNU Common C++ "2" 1.1, GNU pth, and NGPT
In-Reply-To: <20021113222443.GK667@risitas>
Message-ID: <Pine.LNX.4.44.0211131844590.30932-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/>

Native threads and pth have very different behaviors and characteristics,
and depending on what one is doing, it may at times be more desirable to
use one vs the other, so I don't think of it "shocking", but simply a
question of being able to choose application behavior :).  I think most
times people will want native threading, since that spreads over SMP
systems, even if it's more complex to debug.  One could then use pth to
prototype threaded application logic.  In some cases, scaling over
multiple CPU's is not important, and pth does have less overhead
processing sychronization objects.  Of course, there are also now pth
based thread libraries that also do use true process scheduling to enable
SMP....

On Wed, 13 Nov 2002, Federico Montesino Pouzols wrote:

> On Sat, Nov 09, 2002 at 09:59:27AM -0500, David Sugar wrote:
> > My thought on this is that GNU pth should be an alternate compilable 
> > build.  Normally one builds ccgnu2 which everything then is linked to.  In 
> > this scenario, an alternate ccpth2 would be created, and everything could 
> > alternately be linked to that.  This would allow one to have a choice of 
> > threading environment and characteristics (native, or portable) and to 
> > make that choice by which one is chosen at link time.
> > 
> 
> 	I recall I have read there was the intention to make cc++ work
> well with pth. Having two threading environments selectable at link
> time would certainly be a shocking feature.
> 
> > my proposal is to have a seperate pth subdirectory (along with src and
> > win32), and have the pth subdirectory build a ccpth library, often out of
> > the same source files as were used for ccgnu2, but with a CCXX_PTH
> > defined.  Assuming the base classes offer no alignment variances (and this
> > will be done through the headers), ccext2 and other things should then be
> > linkable against either ccgnu2 or ccpth2, and an option could be added to
> > ccgnu2-config to request linkage and compile time options for ccpth rather
> > than for ccgnu.
> > 
> 
> 	I think we should also add two exclusive symbols:
> COMMON_PORTABLE_THREADING and COMMON_NATIVE_THREADING. CCXX_PTH would
> fall whithin COMMON_PORTALE_THREADING.
> 
> > The curious question is what happens with platforms that have no native 
> > thread support at all, but do have a port of pth.  Should pth then become 
> > the ccgnu2 on those platforms?  
> > 
> 
> 	I think it should, it is a very elegant solution.
> 




From dyfet@ostel.com Wed Nov 13 18:25:54 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C6tN-0001Gh-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:25:53 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C6tJ-0001CR-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:25:52 -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 18C6tJ-0001BS-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:25:49 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gADNpDT31027;
	Wed, 13 Nov 2002 18:51:13 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 13 Nov 2002 18:51:13 -0500 (EST)
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: Suggestion regarding header files...
In-Reply-To: <20021113225134.GL667@risitas>
Message-ID: <Pine.LNX.4.44.0211131849540.30932-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

I think it might also be worthwhile if we can tie a member function to the 
"html" parser in libxml2 (it has one as well as the xml parser we 
currently use).  This would allow one to automate processing of common web 
pages through Common C++...

On Wed, 13 Nov 2002, Federico Montesino Pouzols wrote:

> 
> 	It is in CVS for next releases.
> 
> On Sat, Nov 02, 2002 at 09:50:16PM -0600, Ari Johnson wrote:
> > 
> > I like that solution.
> > 
> > On Sat, 2 Nov 2002, Federico Montesino Pouzols wrote:
> > 
> > >
> > > 	Currently, the autoconf stuff defines two symbols:
> > > COMMON_XML_PARSING (A) and HAVE_LIBXML (B). Only B is used for the
> > > #ifdefs. Using both A and B we could do things like this:
> > >
> > > #if defined(A) && defined(B)
> > > 	// libxml based stuff as it is currently defined.
> > > #if defined(A) && !defined(B)
> > > 	// at present, #error "libxml not installed"
> > > 	// in the future, check another HAVE_... alternative xml lib.
> > > #if !defined(A)
> > > 	// put in xml.cpp something like #warning "XML support is not
> > > 	// being compiled, are you sure?". And put in xml.h #error
> > > 	// "XML support not available"
> > >
> 




From fedemp@wanadoo.es Wed Nov 13 18:57:57 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C7OO-0008WM-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:57:56 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C7OL-0008SH-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:57:55 -0500
Received: from [62.37.236.136] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C7OK-0008Ru-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 18:57:53 -0500
Received: from risitas (62-36-186-114.dialup.uni2.es [62.36.186.114])
	by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id gADNnG921201;
	Thu, 14 Nov 2002 00:49:16 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18C7Pa-0002UX-00; Thu, 14 Nov 2002 00:59:10 +0100
Date: Thu, 14 Nov 2002 00:59:10 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Cc: Federico Montesino Pouzols <fedemp@altern.org>, bug-commoncpp@gnu.org
Subject: Re: GNU Common C++ "2" 1.1, GNU pth, and NGPT
Message-ID: <20021113235910.GN667@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: David Sugar <dyfet@ostel.com>,
	Federico Montesino Pouzols <fedemp@altern.org>,
	bug-commoncpp@gnu.org
References: <20021113222443.GK667@risitas> <Pine.LNX.4.44.0211131844590.30932-100000@home.sys>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0211131844590.30932-100000@home.sys>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Oh well, sorry, I should check some dictionary when writing
adjectives whose meaning I am not sure of :). With "shocking" I meant
great or extraordinary.

	Yes, pth will improve the performace of many applications, and
having the possibility to choose at link time is a extremely flexible
scheme. NGPT support is also a very interesting goal. We could start
to fill in COMMON_PORTABLE_THREADING with CCXX_PTH, and then add
CCXX_NGPT :).

On Wed, Nov 13, 2002 at 06:49:24PM -0500, David Sugar wrote:
> 
> Native threads and pth have very different behaviors and characteristics,
> and depending on what one is doing, it may at times be more desirable to
> use one vs the other, so I don't think of it "shocking", but simply a
> question of being able to choose application behavior :).  I think most
> times people will want native threading, since that spreads over SMP
> systems, even if it's more complex to debug.  One could then use pth to
> prototype threaded application logic.  In some cases, scaling over
> multiple CPU's is not important, and pth does have less overhead
> processing sychronization objects.  Of course, there are also now pth
> based thread libraries that also do use true process scheduling to enable
> SMP....
> 
> On Wed, 13 Nov 2002, Federico Montesino Pouzols wrote:
> 
> > On Sat, Nov 09, 2002 at 09:59:27AM -0500, David Sugar wrote:
> > > My thought on this is that GNU pth should be an alternate compilable 
> > > build.  Normally one builds ccgnu2 which everything then is linked to.  In 
> > > this scenario, an alternate ccpth2 would be created, and everything could 
> > > alternately be linked to that.  This would allow one to have a choice of 
> > > threading environment and characteristics (native, or portable) and to 
> > > make that choice by which one is chosen at link time.
> > > 
> > 
> > 	I recall I have read there was the intention to make cc++ work
> > well with pth. Having two threading environments selectable at link
> > time would certainly be a shocking feature.
> > 
> > > my proposal is to have a seperate pth subdirectory (along with src and
> > > win32), and have the pth subdirectory build a ccpth library, often out of
> > > the same source files as were used for ccgnu2, but with a CCXX_PTH
> > > defined.  Assuming the base classes offer no alignment variances (and this
> > > will be done through the headers), ccext2 and other things should then be
> > > linkable against either ccgnu2 or ccpth2, and an option could be added to
> > > ccgnu2-config to request linkage and compile time options for ccpth rather
> > > than for ccgnu.
> > > 
> > 
> > 	I think we should also add two exclusive symbols:
> > COMMON_PORTABLE_THREADING and COMMON_NATIVE_THREADING. CCXX_PTH would
> > fall whithin COMMON_PORTALE_THREADING.
> > 
> > > The curious question is what happens with platforms that have no native 
> > > thread support at all, but do have a port of pth.  Should pth then become 
> > > the ccgnu2 on those platforms?  
> > > 
> > 
> > 	I think it should, it is a very elegant solution.
> > 
> 



From fedemp@wanadoo.es Wed Nov 13 19:03:18 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C7Ta-0001ep-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 19:03:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C7TY-0001ed-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 19:03:17 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18C7TY-0001eY-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 19:03:16 -0500
Received: from risitas (62-36-186-114.dialup.uni2.es [62.36.186.114])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAE6xi209334;
	Thu, 14 Nov 2002 07:59:47 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18C7UY-0002aT-00; Thu, 14 Nov 2002 01:04:18 +0100
Date: Thu, 14 Nov 2002 01:04:17 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Ari Johnson <ariston@cs.und.edu>
Cc: bug-commoncpp@gnu.org
Subject: Re: friends.cpp won't compile on FreeBSD
Message-ID: <20021114000417.GO667@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.0211131718070.23742-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.0211131718070.23742-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/>

	Have you tried the CVS version? I basically added the changes
you described in a previous post and was able to build cc++ 2 on a
FreeBSD 4.7 with gcc 2.95.4.

On Wed, Nov 13, 2002 at 05:20:01PM -0600, Ari Johnson wrote:
> 
> Has anyone else had any problems with this?  It'd really be great to not
> have to hack things to get it to compile even with my default compiler
> (gcc 2.95.x); once I get that working, maybe I'll worry about getting
> CommonC++ to compile with gcc 3.x. :)
> 
> Ari Johnson
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Wed Nov 13 19:29:28 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18C7su-0000PD-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 19:29:28 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18C7sr-0000Oq-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 19:29:27 -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 18C7rn-0008RP-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 19:28:20 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gAE0roc31945;
	Wed, 13 Nov 2002 19:53:50 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 13 Nov 2002 19:53:50 -0500 (EST)
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: friends.cpp won't compile on FreeBSD
In-Reply-To: <20021114000417.GO667@risitas>
Message-ID: <Pine.LNX.4.44.0211131953400.31934-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/>

And I am currently building on 4.7 as well here...

On Thu, 14 Nov 2002, Federico Montesino Pouzols wrote:

> 
> 	Have you tried the CVS version? I basically added the changes
> you described in a previous post and was able to build cc++ 2 on a
> FreeBSD 4.7 with gcc 2.95.4.
> 
> On Wed, Nov 13, 2002 at 05:20:01PM -0600, Ari Johnson wrote:
> > 
> > Has anyone else had any problems with this?  It'd really be great to not
> > have to hack things to get it to compile even with my default compiler
> > (gcc 2.95.x); once I get that working, maybe I'll worry about getting
> > CommonC++ to compile with gcc 3.x. :)
> > 
> > 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 Wed Nov 13 23:21:25 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18CBVN-0002AB-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 23:21:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18CBVK-000282-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 23:21:23 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18CBVK-00026q-00
	for bug-commoncpp@gnu.org; Wed, 13 Nov 2002 23:21:22 -0500
Received: from agassiz (agassiz [134.129.212.31])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gAE4TksY015024;
	Wed, 13 Nov 2002 22:29:51 -0600
Date: Wed, 13 Nov 2002 22:22:10 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: <bug-commoncpp@gnu.org>
Subject: Re: friends.cpp won't compile on FreeBSD
In-Reply-To: <20021114000417.GO667@risitas>
Message-ID: <Pine.GSO.4.33.0211132217010.27138-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/>

Alright, I removed my local copy of the cvs and checked it out anew, and
now everything worked fine (except piostreams, but that's probably because
I'm missing some library or something, and I don't use them anyhow, so I'm
not overly concerned).  Now, on to using gcc 3.x.  The compilation fails
when it gets to slog.cpp, which gets a ton of errors from
/usr/local/lib/gcc-lib/i386-portbld-freebsd4.7/3.3/include/g++-v3/cmath,
which is included eventually by fstream, which slog.h includes.  The
errors are all like this:
/usr/local/lib/gcc-lib/i386-portbld-freebsd4.7/3.3/include/g++-v3/cmath:
In function `float std::tanh(float)':
/usr/local/lib/gcc-lib/i386-portbld-freebsd4.7/3.3/include/g++-v3/cmath:489:
error: `::
   tanhf' undeclared (first use here)

This doesn't happen when I compile anything else that includes fstream, so
I'm thinking it's a problem with the order in which slog.cpp includes
files.  I'm running FreeBSD-STABLE, which is basically 4.7, and the
gcc-3.3 port, version string is 'gcc version 3.3 20021014 (experimental)
[FreeBSD]', with no further modifications.  I've also tried the gcc ports
for versions 3.0, 3.1, and 3.2, and all result in the same problem.  I
just can't comprehend the sheer weirdness of this error.

Ari Johnson

On Thu, 14 Nov 2002, Federico Montesino Pouzols wrote:

>
> 	Have you tried the CVS version? I basically added the changes
> you described in a previous post and was able to build cc++ 2 on a
> FreeBSD 4.7 with gcc 2.95.4.
>
> On Wed, Nov 13, 2002 at 05:20:01PM -0600, Ari Johnson wrote:
> >
> > Has anyone else had any problems with this?  It'd really be great to not
> > have to hack things to get it to compile even with my default compiler
> > (gcc 2.95.x); once I get that working, maybe I'll worry about getting
> > CommonC++ to compile with gcc 3.x. :)
> >
> > Ari Johnson
> >
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>




From dyfet@ostel.com Thu Nov 14 11:28:41 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18CMrB-0007Pd-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 11:28:41 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18CMr6-0007OO-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 11:28:40 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18CLv2-0000Yy-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 10:28:36 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by gnudist.gnu.org with esmtp (Exim 4.10)
	id 18CIws-0004J9-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 07:18:18 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gAECcS903653;
	Thu, 14 Nov 2002 07:38:28 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Thu, 14 Nov 2002 07:38:28 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: "Prochnow, Christian" <cproch@freiverkehr.de>
cc: bug-commoncpp@gnu.org, Federico Montesino Pouzols <fedemp@altern.org>
Subject: Re: Network Device Informations
In-Reply-To: <200211141149.27029.cproch@freiverkehr.de>
Message-ID: <Pine.LNX.4.44.0211140737400.3642-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

I think the -1 MTU returned from something (like win95) which cannot 
return a mtu is find...

On Thu, 14 Nov 2002, Prochnow, Christian wrote:

> Hi,
> 
> The ioctl() calls made in enumNetworkDevices() should work under Linux, 
> Solaris and FreeBSD cause this is a common UNIX ioctl. The structures used 
> are also UNIX-common. 
> ioctl() are very different between unices if we want to query IPv6 devices 
> also - but Common C++ doesnt support IPv6 at all, right ?
> So adding IPv6 support to Common C++ and to the NetworkDeviceInfo class should 
> be a TODO item for future releases.
> 
> So what dou you think of the MTU issue ?
> Does anyone know if Common C++ works under Win95 ?
> And when - do you think we should break compatibility with Win95 cause of this 
> MIB functions ? Or should the Win95 implementation simply return "-1" as MTU. 
> I think querying the MTU is a common-task for UDP-message oriented protocols. 
> 
> I'm using Common C++ to develop Finance Realtime Applications for my employer 
> (a German company) which mainly runs Linux on their Servers and Windows on 
> their Workstations.
> Cause i'm actively using Common C++ now, and also did a portable application 
> framework (P::Classes) in the past i would like to continue contributing to 
> the Common C++ Project.
> 
> Regards,
> Christian Prochnow
> 
> Am Donnerstag, 14. November 2002 00:42 schrieben Sie:
> > This is also the kind of things Common C++ is meant to be abstracting.  I
> > agree it is something we should try to add.
> >
> > On Wed, 13 Nov 2002, Federico Montesino Pouzols wrote:
> > > 	Ummm, I think this adds interesting features. I think this
> > > should be added soon to the unstable branch, at least. I will do some
> > > tests, tell us if you check it works on other platforms, as I believe
> > > that some of the system calls may be problematic.
> > >
> > > On Wed, Nov 13, 2002 at 02:26:23PM +0100, Prochnow, Christian wrote:
> > > > Hi List,
> > > >
> > > > For a networking application i needed to query a list of Network
> > > > Devices and their Broadcast addresses to ignore Broadcasts from my own.
> > > > Here's the solution which i think is of interest for implementing it in
> > > > Common C++.
> > > >
> > > > This solution is tested under Linux, but should also work under other
> > > > UNIX systems which needs to be verified. Win32 stuff is also
> > > > implemented, but untested. I also did'nt find a way to get the MTU
> > > > under Win32 without braking compatibility with Win95 (with >= Win98 it
> > > > is possible to get the MTU via MIB extensions).
> > > >
> > > >
> > > >
> > > > Regards,
> > > > Christian Prochnow
> > >
> > > _______________________________________________
> > > Bug-commoncpp mailing list
> > > Bug-commoncpp@gnu.org
> > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 
> 




From cproch@freiverkehr.de Thu Nov 14 12:20:16 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18CNf6-0003gU-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 12:20:16 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18CNey-0003eQ-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 12:20:12 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18CLxX-0001eP-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 10:31:11 -0500
Received: from h-62.96.239.30.host.de.colt.net ([62.96.239.30] helo=mail.freiverkehr.de)
	by gnudist.gnu.org with esmtp (Exim 4.10)
	id 18CHbm-0006VZ-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 05:52:26 -0500
Received: from cproch.freiverkehr.de (CPROCH [10.100.102.211]) by mail.freiverkehr.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id WX604V8Y; Thu, 14 Nov 2002 11:46:33 +0100
Content-Type: text/plain;
  charset="iso-8859-1"
From: "Prochnow, Christian" <cproch@freiverkehr.de>
Organization: Berliner Freiverkehr AG
To: bug-commoncpp@gnu.org
Subject: Re: Network Device Informations
Date: Thu, 14 Nov 2002 11:49:27 +0100
User-Agent: KMail/1.4.3
References: <Pine.LNX.4.44.0211131841360.30932-100000@home.sys>
In-Reply-To: <Pine.LNX.4.44.0211131841360.30932-100000@home.sys>
Cc: David Sugar <dyfet@ostel.com>,
 Federico Montesino Pouzols <fedemp@altern.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211141149.27029.cproch@freiverkehr.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,

The ioctl() calls made in enumNetworkDevices() should work under Linux,=20
Solaris and FreeBSD cause this is a common UNIX ioctl. The structures use=
d=20
are also UNIX-common.=20
ioctl() are very different between unices if we want to query IPv6 device=
s=20
also - but Common C++ doesnt support IPv6 at all, right ?
So adding IPv6 support to Common C++ and to the NetworkDeviceInfo class s=
hould=20
be a TODO item for future releases.

So what dou you think of the MTU issue ?
Does anyone know if Common C++ works under Win95 ?
And when - do you think we should break compatibility with Win95 cause of=
 this=20
MIB functions ? Or should the Win95 implementation simply return "-1" as =
MTU.=20
I think querying the MTU is a common-task for UDP-message oriented protoc=
ols.=20

I'm using Common C++ to develop Finance Realtime Applications for my empl=
oyer=20
(a German company) which mainly runs Linux on their Servers and Windows o=
n=20
their Workstations.
Cause i'm actively using Common C++ now, and also did a portable applicat=
ion=20
framework (P::Classes) in the past i would like to continue contributing =
to=20
the Common C++ Project.

Regards,
Christian Prochnow

Am Donnerstag, 14. November 2002 00:42 schrieben Sie:
> This is also the kind of things Common C++ is meant to be abstracting. =
 I
> agree it is something we should try to add.
>
> On Wed, 13 Nov 2002, Federico Montesino Pouzols wrote:
> > =09Ummm, I think this adds interesting features. I think this
> > should be added soon to the unstable branch, at least. I will do some
> > tests, tell us if you check it works on other platforms, as I believe
> > that some of the system calls may be problematic.
> >
> > On Wed, Nov 13, 2002 at 02:26:23PM +0100, Prochnow, Christian wrote:
> > > Hi List,
> > >
> > > For a networking application i needed to query a list of Network
> > > Devices and their Broadcast addresses to ignore Broadcasts from my =
own.
> > > Here's the solution which i think is of interest for implementing i=
t in
> > > Common C++.
> > >
> > > This solution is tested under Linux, but should also work under oth=
er
> > > UNIX systems which needs to be verified. Win32 stuff is also
> > > implemented, but untested. I also did'nt find a way to get the MTU
> > > under Win32 without braking compatibility with Win95 (with >=3D Win=
98 it
> > > is possible to get the MTU via MIB extensions).
> > >
> > >
> > >
> > > Regards,
> > > Christian Prochnow
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From fedemp@wanadoo.es Thu Nov 14 17:21:55 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18CSN1-0006gI-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 17:21:55 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18CSMx-0006fg-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 17:21:54 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18CRJx-0007vM-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 16:14:41 -0500
Received: from risitas (62-36-189-224.dialup.uni2.es [62.36.189.224])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAF4BE210185;
	Fri, 15 Nov 2002 05:11:14 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18CRL8-00040o-00; Thu, 14 Nov 2002 22:15:54 +0100
Date: Thu, 14 Nov 2002 22:15:54 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Cc: "Prochnow, Christian" <cproch@freiverkehr.de>, bug-commoncpp@gnu.org,
   Federico Montesino Pouzols <fedemp@altern.org>
Subject: Re: Network Device Informations
Message-ID: <20021114211554.GA681@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: David Sugar <dyfet@ostel.com>,
	"Prochnow, Christian" <cproch@freiverkehr.de>,
	bug-commoncpp@gnu.org,
	Federico Montesino Pouzols <fedemp@altern.org>
References: <200211141149.27029.cproch@freiverkehr.de> <Pine.LNX.4.44.0211140737400.3642-100000@home.sys>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0211140737400.3642-100000@home.sys>
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/>

	Returning -1 seems a good option. If there were another way to
fix this problem, we could always add a patch for that later.

	The new code is alreay in the 1.1 CVS branch.

	I am sure CC++ works well under Win98, and it should on Win95.

On Thu, Nov 14, 2002 at 07:38:28AM -0500, David Sugar wrote:
> 
> I think the -1 MTU returned from something (like win95) which cannot 
> return a mtu is find...
> 
> On Thu, 14 Nov 2002, Prochnow, Christian wrote:
> 
> > Hi,
> > 
> > The ioctl() calls made in enumNetworkDevices() should work under Linux, 
> > Solaris and FreeBSD cause this is a common UNIX ioctl. The structures used 
> > are also UNIX-common. 
> > ioctl() are very different between unices if we want to query IPv6 devices 
> > also - but Common C++ doesnt support IPv6 at all, right ?
> > So adding IPv6 support to Common C++ and to the NetworkDeviceInfo class should 
> > be a TODO item for future releases.
> > 
> > So what dou you think of the MTU issue ?
> > Does anyone know if Common C++ works under Win95 ?
> > And when - do you think we should break compatibility with Win95 cause of this 
> > MIB functions ? Or should the Win95 implementation simply return "-1" as MTU. 
> > I think querying the MTU is a common-task for UDP-message oriented protocols. 
> > 
> > I'm using Common C++ to develop Finance Realtime Applications for my employer 
> > (a German company) which mainly runs Linux on their Servers and Windows on 
> > their Workstations.
> > Cause i'm actively using Common C++ now, and also did a portable application 
> > framework (P::Classes) in the past i would like to continue contributing to 
> > the Common C++ Project.
> > 
> > Regards,
> > Christian Prochnow
> > 



From danielb@obfuscation.dyndns.org Thu Nov 14 22:20:39 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18CX27-0006yv-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 22:20:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18CX24-0006xf-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 22:20:38 -0500
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 18CX24-0006xP-00
	for bug-commoncpp@gnu.org; Thu, 14 Nov 2002 22:20:36 -0500
Received: from obfuscation.dyndns.org ([192.168.1.2] ident=mail)
	by frell.dyndns.org with esmtp (Exim 3.36 #1 (Debian))
	id 18CX25-0000p1-00
	for <bug-commoncpp@gnu.org>; Thu, 14 Nov 2002 21:20:37 -0600
Received: from danielb by obfuscation.dyndns.org with local (Exim 3.36 #1 (Debian))
	id 18CX21-0004eZ-00
	for <bug-commoncpp@gnu.org>; Thu, 14 Nov 2002 21:20:33 -0600
Date: Thu, 14 Nov 2002 21:20:33 -0600
From: Daniel E Baumann <baumannd@msoe.edu>
To: bug-commoncpp@gnu.org
Subject: Re: ost::Event and multiple wait()s
Message-ID: <20021115032033.GA17641@obfuscation.dyndns.org>
References: <20021111131421.GA19520@obfuscation.dyndns.org> <20021113213850.GF667@risitas>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021113213850.GF667@risitas>
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, yea, the devil is in the details ;). Hmm, alright but with a
Conditional I need to still use a Mutex to prevent the infinite wait
problem right? Which Event takes care of for me. You think it would be
wise to change the signal method of Event to take a boolean to
determine whether someone wants broadcast or not? I sorta of see Event
as encapslating both a condition variable and the atomic (locked with
a mutex) conditional test.

On Wed, Nov 13, 2002 at 10:38:50PM +0100, Federico Montesino Pouzols wrote:
> 
> 	If you want only one thread to be picked, I think Event will
> not work. Event::signal uses pthread_cond_broadcast, so all waiting
> threads will be reactivated. Conditional however has a signal method
> that allows to specify whether to use pthread_cond_broadcast or
> pthread_cond_signal.
>
> On Mon, Nov 11, 2002 at 07:14:22AM -0600, Daniel E Baumann wrote:
> > I was just wondering if it is possible for multiple threads to wait on
> > an Event and for it to pick one of them to run when calling
> > signal(). Looks to me that it is possible becase it uses a condition
> > variable. I just wanted to confirm this. I need to write a boolean
> > lock class and would like this capability.
> > 
> > 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
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 

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

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



From danielb@obfuscation.dyndns.org Fri Nov 15 00:47:54 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18CZKc-0006zm-00
	for bug-commoncpp@gnu.org; Fri, 15 Nov 2002 00:47:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18CZKa-0006yu-00
	for bug-commoncpp@gnu.org; Fri, 15 Nov 2002 00:47:53 -0500
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 18CZKZ-0006ya-00
	for bug-commoncpp@gnu.org; Fri, 15 Nov 2002 00:47:51 -0500
Received: from obfuscation.dyndns.org ([192.168.1.2] ident=mail)
	by frell.dyndns.org with esmtp (Exim 3.36 #1 (Debian))
	id 18CZKY-0000Ca-00
	for <bug-commoncpp@gnu.org>; Thu, 14 Nov 2002 23:47:50 -0600
Received: from danielb by obfuscation.dyndns.org with local (Exim 3.36 #1 (Debian))
	id 18CZKW-0004h7-00
	for <bug-commoncpp@gnu.org>; Thu, 14 Nov 2002 23:47:48 -0600
Date: Thu, 14 Nov 2002 23:47:48 -0600
From: Daniel E Baumann <baumannd@msoe.edu>
To: bug-commoncpp@gnu.org
Subject: Re: ost::Event and multiple wait()s
Message-ID: <20021115054748.GA18036@obfuscation.dyndns.org>
References: <20021113213850.GF667@risitas> <Pine.LNX.4.44.0211131838540.30932-100000@home.sys>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0211131838540.30932-100000@home.sys>
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 Wed, Nov 13, 2002 at 06:40:00PM -0500, David Sugar wrote:
> 
> "Event" is meant to simulate the behavior of win32 "event" objects, so the 
> behavior is consistent with that. 

Yea, I suppose that is the whole point of it, but what I was getting
at I suppose is having some class that abstracts condition variables
even further by already locking the conditional test with a mutex to
prevent the common race condition that can lead to the infinite wait
problem. Granted ppl can do this themselves it would be nice to just
call wait() from multiple threads and then some thread(s) can do a
notify() to wake up the waiting threads either one with plain
pthread_signal_cond or all waiting threads with
pthread_signal_broadcast. 

Where I have specifically see this type of behavior is in the Java
Object class where multiple threads can wait() on the object's monitor
and then be either notify()ed or notifyAll()ed.

At any rate, I suppose I am not going to harp much more on this ;).

Cheers,
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 dyfet@ostel.com Fri Nov 15 02:11:12 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18CadE-0005Qz-00
	for bug-commoncpp@gnu.org; Fri, 15 Nov 2002 02:11:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18Cad9-0005Jk-00
	for bug-commoncpp@gnu.org; Fri, 15 Nov 2002 02:11:11 -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 18Cad7-0005J1-00
	for bug-commoncpp@gnu.org; Fri, 15 Nov 2002 02:11:06 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gAF7aoZ32521;
	Fri, 15 Nov 2002 02:36:50 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Fri, 15 Nov 2002 02:36:50 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: "Prochnow, Christian" <cproch@freiverkehr.de>, <bug-commoncpp@gnu.org>
Subject: Re: Network Device Informations
In-Reply-To: <20021114211554.GA681@risitas>
Message-ID: <Pine.LNX.4.44.0211150236350.32454-100000@home.sys>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

I think it would be okay to also add to 1.0...



On Thu, 14 Nov 2002, Federico Montesino Pouzols wrote:

> 
> 	Returning -1 seems a good option. If there were another way to
> fix this problem, we could always add a patch for that later.
> 
> 	The new code is alreay in the 1.1 CVS branch.
> 
> 	I am sure CC++ works well under Win98, and it should on Win95.
> 
> On Thu, Nov 14, 2002 at 07:38:28AM -0500, David Sugar wrote:
> > 
> > I think the -1 MTU returned from something (like win95) which cannot 
> > return a mtu is find...
> > 
> > On Thu, 14 Nov 2002, Prochnow, Christian wrote:
> > 
> > > Hi,
> > > 
> > > The ioctl() calls made in enumNetworkDevices() should work under Linux, 
> > > Solaris and FreeBSD cause this is a common UNIX ioctl. The structures used 
> > > are also UNIX-common. 
> > > ioctl() are very different between unices if we want to query IPv6 devices 
> > > also - but Common C++ doesnt support IPv6 at all, right ?
> > > So adding IPv6 support to Common C++ and to the NetworkDeviceInfo class should 
> > > be a TODO item for future releases.
> > > 
> > > So what dou you think of the MTU issue ?
> > > Does anyone know if Common C++ works under Win95 ?
> > > And when - do you think we should break compatibility with Win95 cause of this 
> > > MIB functions ? Or should the Win95 implementation simply return "-1" as MTU. 
> > > I think querying the MTU is a common-task for UDP-message oriented protocols. 
> > > 
> > > I'm using Common C++ to develop Finance Realtime Applications for my employer 
> > > (a German company) which mainly runs Linux on their Servers and Windows on 
> > > their Workstations.
> > > Cause i'm actively using Common C++ now, and also did a portable application 
> > > framework (P::Classes) in the past i would like to continue contributing to 
> > > the Common C++ Project.
> > > 
> > > Regards,
> > > Christian Prochnow
> > > 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From fedemp@wanadoo.es Sat Nov 16 07:26:17 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18D21h-0003NA-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 07:26:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18D21d-0003Kw-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 07:26:16 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18D21c-0003Kc-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 07:26:12 -0500
Received: from risitas (62-37-68-105.dialup.uni2.es [62.37.68.105])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAGJMd228251;
	Sat, 16 Nov 2002 20:22:39 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18D22s-0000Ik-00; Sat, 16 Nov 2002 13:27:30 +0100
Date: Sat, 16 Nov 2002 13:27:29 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Arthur Kantor <akantor@uiuc.edu>
Cc: bug-commoncpp@gnu.org
Subject: Re: process.cpp:204: implicit declaration of function `int ost::snprintf(...)'
Message-ID: <20021116122729.GA670@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Arthur Kantor <akantor@uiuc.edu>, bug-commoncpp@gnu.org
References: <200210310023.ACK40103@express.cites.uiuc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200210310023.ACK40103@express.cites.uiuc.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/>

On Wed, Oct 30, 2002 at 06:23:11PM -0600, Arthur Kantor wrote:
> 
> 
> 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:

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

	Ok, fixed in cvs.

> cheers,
> -Arthur



From fedemp@wanadoo.es Sat Nov 16 08:16:07 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18D2nu-0004h4-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 08:16:06 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18D2nq-0004gN-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 08:16:06 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18D2nq-0004gG-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 08:16:02 -0500
Received: from risitas (62-37-68-105.dialup.uni2.es [62.37.68.105])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAGKCb214988;
	Sat, 16 Nov 2002 21:12:38 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18D2pE-0000QL-00; Sat, 16 Nov 2002 14:17:28 +0100
Date: Sat, 16 Nov 2002 14:17:28 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Alex Pavloff <apavloff@eason.com>
Cc: bug-commoncpp@gnu.org, dyfet@ostel.com
Subject: Re: Exception documentation
Message-ID: <20021116131728.GB670@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Alex Pavloff <apavloff@eason.com>, bug-commoncpp@gnu.org,
	dyfet@ostel.com
References: <D3AF5F134D627243993F2F2FC32EE4D229C423@mailman.eason.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D3AF5F134D627243993F2F2FC32EE4D229C423@mailman.eason.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, ost::Exception does not appear in the reference
manual. Currently, there is a specific doc/cc++/config.h for doxygen
which only defines a few configuration constants.

	With the current setting, ost::Exception is not included in
the manual because HAVE_EXCEPTION is not defined. Similarly, after the
recent changes to the xml #ifdefs, the xml classes would not be
included.  Should not we use the real config.h for Doxygen?

On Wed, Nov 13, 2002 at 02:32:16PM -0800, Alex Pavloff wrote:
> 
> I'm trying to use ost::MappedFile, and I'm doing something wrong, so its
> throwing exceptions.  The problem is that
> 
> 1) The possible exceptions thrown by each functoin are not documented.
> 2) The exceptions themselves (ost::Exception,FileException, IOException...)
> aren't in the documentation at all.  
> 
> This makes things harder than they have to be.
> 
> 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 fedemp@wanadoo.es Sat Nov 16 08:59:17 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18D3Th-0007zI-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 08:59:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18D3RZ-0006BY-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 08:57:09 -0500
Received: from [62.37.236.136] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18D3RY-00069w-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 08:57:04 -0500
Received: from risitas (62-37-68-105.dialup.uni2.es [62.37.68.105])
	by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id gAGDulC18128;
	Sat, 16 Nov 2002 14:56:48 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18D3Sm-0002Pq-00; Sat, 16 Nov 2002 14:58:20 +0100
Date: Sat, 16 Nov 2002 14:58:20 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Cc: Federico Montesino Pouzols <fedemp@altern.org>,
   "Prochnow, Christian" <cproch@freiverkehr.de>, bug-commoncpp@gnu.org
Subject: Re: Network Device Informations
Message-ID: <20021116135820.GD670@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: David Sugar <dyfet@ostel.com>,
	Federico Montesino Pouzols <fedemp@altern.org>,
	"Prochnow, Christian" <cproch@freiverkehr.de>,
	bug-commoncpp@gnu.org
References: <20021114211554.GA681@risitas> <Pine.LNX.4.44.0211150236350.32454-100000@home.sys>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0211150236350.32454-100000@home.sys>
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 is in CVS for 1.0.7. I will also add a demo for it in a
while.

On Fri, Nov 15, 2002 at 02:36:50AM -0500, David Sugar wrote:
> 
> I think it would be okay to also add to 1.0...



From cproch@seculogix.de Sat Nov 16 09:15:06 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18D3j0-00085P-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 09:15:06 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18D3it-00081u-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 09:15:03 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18D3is-00080w-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 09:14:59 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP
	id 43FAD13AE3; Sat, 16 Nov 2002 15:12:37 +0100 (CET)
Content-Type: text/plain;
  charset="iso-8859-1"
From: "Prochnow, Christian" <cproch@seculogix.de>
Reply-To: cproch@seculogix.de
To: Federico Montesino Pouzols <fedemp@altern.org>
Subject: Re: Network Device Informations
Date: Sat, 16 Nov 2002 15:14:56 +0100
User-Agent: KMail/1.4.3
References: <20021114211554.GA681@risitas> <Pine.LNX.4.44.0211150236350.32454-100000@home.sys> <20021116135820.GD670@risitas>
In-Reply-To: <20021116135820.GD670@risitas>
Cc: bug-commoncpp@gnu.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211161514.56743.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/>

Here is a little demo program:

----- cut -----
#include <cc++/network.h>
#include <iostream>

int main(int argc, char* argv[])
{
  std::vector<ost::NetworkDeviceInfo> devs;

  if(!ost::enumNetworkDevices(devs))
{
=09std::cerr << "Could not get list of network devices!" << std::endl;
=09return -1;
}

  std::cout << "Available network devices:" << std::endl;
  std::vector<ost::NetworkDeviceInfo>::const_iterator i =3D devs.begin();
  while(i !=3D devs.end())
  {
    std::cout << (*i).name() << " address: " << (*i).address()
                                      << ", brdcast: " << (*i).broadcast(=
)
                                      << ", netmask: " << (*i).netmask()
                                      << ", mtu: " << (*i).mtu() << std::=
endl;
    ++i;
  }
}
---- cut  ----

Regards,
Christian Prochnow

Am Samstag 16 November 2002 14:58 schrieb Federico Montesino Pouzols:
> Ok, it is in CVS for 1.0.7. I will also add a demo for it in a
> while.
>
> On Fri, Nov 15, 2002 at 02:36:50AM -0500, David Sugar wrote:
> > I think it would be okay to also add to 1.0...
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From fedemp@wanadoo.es Sat Nov 16 10:32:03 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18D4vT-0002WU-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 10:32:03 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18D4uv-0002LV-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 10:31:31 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18D4uu-0002LP-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 10:31:28 -0500
Received: from risitas (62-37-68-105.dialup.uni2.es [62.37.68.105])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAGMS3219277;
	Sat, 16 Nov 2002 23:28:03 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18D4wJ-0001UF-00; Sat, 16 Nov 2002 16:32:55 +0100
Date: Sat, 16 Nov 2002 16:32:54 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Prochnow, Christian" <cproch@seculogix.de>
Cc: Federico Montesino Pouzols <fedemp@altern.org>, bug-commoncpp@gnu.org
Subject: Re: Network Device Informations
Message-ID: <20021116153254.GF670@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: "Prochnow, Christian" <cproch@seculogix.de>,
	Federico Montesino Pouzols <fedemp@altern.org>,
	bug-commoncpp@gnu.org
References: <20021114211554.GA681@risitas> <Pine.LNX.4.44.0211150236350.32454-100000@home.sys> <20021116135820.GD670@risitas> <200211161514.56743.cproch@seculogix.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200211161514.56743.cproch@seculogix.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Good! It is in CVS, for next releases.

On Sat, Nov 16, 2002 at 03:14:56PM +0100, Prochnow, Christian wrote:
> Here is a little demo program:
> 



From cproch@seculogix.de Sat Nov 16 09:02:02 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18D3WM-0001wT-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 09:02:02 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18D3WH-0001vi-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 09:02:00 -0500
Received: from [212.84.242.26] (helo=steel.darklab.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18D3VY-0001XB-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 09:01:12 -0500
Received: from reliant.darklab.org (212-84-242-003.trmd.net [212.84.242.3])
	by steel.darklab.org (Postfix) with ESMTP id 68C2C13AE3
	for <bug-commoncpp@gnu.org>; Sat, 16 Nov 2002 14:58:50 +0100 (CET)
From: "Prochnow, Christian" <cproch@seculogix.de>
Reply-To: cproch@seculogix.de
To: bug-commoncpp@gnu.org
Subject: Patch for socket error/exception handling
Date: Sat, 16 Nov 2002 15:01:09 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="------------Boundary-00=_XL9OWT7NDMWKRRC41G1C"
Message-Id: <200211161501.09805.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/>

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

Hi,

this patch (against CVS head) adds more informative socket error-handling=
=20
functions to the Socket classes. It is now possible to retrieve the "real=
"=20
system error message to display more informative error messages to the us=
er.=20
Support for win32 system error messages is currently missing - i need to=20
figure out how one can retrieve them under win32 - i think FormatMessage =
or=20
something should do the job.

Regards,
Christian Prochnow


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

? autom4te-2.53.cache
? commoncpp2.kdevses
? socket_exception.patch
? 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
? ssl/.libs
? ssl/Makefile
? ssl/Makefile.in
? ssl/libccssl.la
? ssl/sslcontext.lo
? ssl/sslengine.lo
? ssl/sslsession.lo
? win32/CCXX2.rc
Index: acconfig.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/acconfig.h,v
retrieving revision 1.14
diff -r1.14 acconfig.h
79a80
> #undef HAVE_STRERROR_R
426a428,430
> #ifndef HAVE_STRERROR_R
> #define strerror_r(e, b, l) strerror(e)
> #endif
Index: demo/tcp.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/demo/tcp.cpp,v
retrieving revision 1.2
diff -r1.2 tcp.cpp
77a78,79
> 	setException(Thread::throwException);
> 
95c97
< 	catch(Socket *socket)
---
> 	catch(SockException& e)
97,110c99,100
< 		tpport_t port;
< 		InetAddress saddr = (InetAddress)socket->getPeer(&port);
< 		cerr << "socket error " << saddr << ":" << port << endl;
< 		cout << "error number " << socket->getErrorNumber() << endl;
< 		if(socket->getErrorNumber() == Socket::errResourceFailure)
< 		{
< 			cerr << "bind failed; no resources" << endl;
< 			exit(-1);
< 		}
< 		if(socket->getErrorNumber() == Socket::errBindingFailed)
< 		{
< 			cerr << "bind failed; port busy" << endl;
< 			exit(-1);
< 		}
---
> 		cout << e.getString() << ": " << e.getSystemErrorString() << endl;
> 		exit(-1);
Index: include/cc++/exception.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/exception.h,v
retrieving revision 1.4
diff -r1.4 exception.h
96a97,99
> private:
> 	long _systemError;
> 
98c101
< 	IOException(const std::string &what_arg) throw();
---
> 	IOException(const std::string &what_arg, long systemError = 0) throw();
99a103,105
> 
> 	virtual long getSystemError() const throw() { return _systemError; };
> 	virtual const char* getSystemErrorString() const throw();
Index: include/cc++/ftp.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/ftp.h,v
retrieving revision 1.4
diff -r1.4 ftp.h
323c323
< 	FTPException(string str) : SockException(str) {};                   
---
> 	FTPException(string str, Socket::Error socketError, long systemError = 0) : SockException(str,socketError,systemError) {};                   
334c334
<       FTPResponse(int c, string r) : FTPException(r), code(c) {};
---
>       FTPResponse(int c, string r) : FTPException(r,Socket::errSuccess), code(c) {};
Index: include/cc++/socket.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/socket.h,v
retrieving revision 1.17
diff -r1.17 socket.h
577a578
> 	mutable long syserr;
609a611
> 	 * @param systemError the system error# that caused the error
611c613
< 	Error error(Error error, char *errstr = NULL) const;
---
> 	Error error(Error error, char *errstr = NULL, long systemError = 0) const;
901a904,907
> 	inline long getSystemError(void) const {return syserr;}
> 
> 	const char *getSystemErrorString(void) const;
> 
2237a2244,2246
> private:
> 	Socket::Error _socketError;
> 	
2239c2248,2252
< 	SockException(std::string str) : IOException(str) {};
---
> 	SockException(std::string str, Socket::Error socketError, long systemError = 0) :
> 		IOException(str, systemError), _socketError(socketError) {};
> 
> 	inline Socket::Error getSocketError() const
> 	{ return _socketError; }
Index: m4/ost_reentrant.m4
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/m4/ost_reentrant.m4,v
retrieving revision 1.1.1.1
diff -r1.1.1.1 ost_reentrant.m4
28a29
> 		AC_CHECK_LIB(c, strerror_r, AC_DEFINE(HAVE_STRERROR_R))
35a37
> dnl #undef HAVE_STRERROR_R
50a53,56
> dnl #ifndef HAVE_STRERROR_R
> dnl #define strerror_r(e, b, s) strerror(e)
> dnl #endif
> dnl
Index: src/exception.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/exception.cpp,v
retrieving revision 1.2
diff -r1.2 exception.cpp
65,66c65,66
< IOException::IOException(const std::string &what_arg) throw() : 
<   Exception(what_arg)
---
> IOException::IOException(const std::string &what_arg, long systemError) throw() : 
>   Exception(what_arg), _systemError(systemError)
70a71,80
> 
> const char* IOException::getSystemErrorString() const throw()
> {
> 	#ifndef WIN32
> 	static char errstr[2048];
> 	return strerror_r(_systemError, errstr, sizeof(errstr));
> 	#else
> 	
> 	#endif
> }
Index: src/ftp.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/ftp.cpp,v
retrieving revision 1.4
diff -r1.4 ftp.cpp
239c239
<     	throw FTPException(buffer.str());
---
>     	throw FTPException(buffer.str(),Socket::errSuccess,0);
307c307
<     	throw FTPException( msg.str() );
---
>     	throw FTPException( msg.str(), cs->getErrorNumber());
365c365
< 	    throw FTPException("invalid response from PWD");
---
> 	    throw FTPException("invalid response from PWD",Socket::errSuccess);
378c378
< 	    throw FTPException("invalid response from PWD");
---
> 	    throw FTPException("invalid response from PWD",Socket::errSuccess);
606c606
< 	      throw FTPException("invalid response");
---
> 	      throw FTPException("invalid response",Socket::errSuccess);
618c618
< 	    throw FTPException("invalid response");
---
> 	    throw FTPException("invalid response",Socket::errSuccess);
Index: src/port.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/port.cpp,v
retrieving revision 1.7
diff -r1.7 port.cpp
46a47,49
> #define socket_errno errno
> #else
> #define socket_errno WSAGetLastError()
226c229
< 		error(errBindingFailed);
---
> 		error(errBindingFailed,"Could not bind socket",socket_errno);
286c289
< 			error(connectError());
---
> 			error(connectError(), "Could not connect", socket_errno);
Index: src/socket.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/socket.cpp,v
retrieving revision 1.13
diff -r1.13 socket.cpp
53a54
> #define socket_errno	WSAGetLastError()
56a58
> #define socket_errno errno
95c97
< 		error(errCreateFailed);
---
> 		error(errCreateFailed,"Could not create socket",socket_errno);
106c108
< 		error(errCreateFailed);
---
> 		error(errCreateFailed,"Invalid socket handle passed",0);
118c120
< 		error(errCopyFailed);
---
> 		error(errCopyFailed,"Could not duplicate socket handle",socket_errno);
138a141
> 	syserr          = 0;
161c164
< 				error(errTimeout);
---
> 				error(errTimeout,"Read timeout", 0);
168c171
< 			error(errInput);
---
> 			error(errInput,"Could not read from socket", socket_errno);
271a275
> 	char* str = "Could not connect to remote host";
275c279
< 		return error(errResourceFailure);
---
> 		return error(errResourceFailure,str,socket_errno);
277c281
< 		return error(errConnectBusy);
---
> 		return error(errConnectBusy,str,socket_errno);
279c283
< 		return error(errConnectInvalid);
---
> 		return error(errConnectInvalid,str,socket_errno);
281c285
< 		return error(errConnectRefused);
---
> 		return error(errConnectRefused,str,socket_errno);
283c287
< 		return error(errConnectNoRoute);
---
> 		return error(errConnectNoRoute,str,socket_errno);
285c289
< 		return error(errConnectFailed);
---
> 		return error(errConnectFailed,str,socket_errno);
290a295
> 	char* str = "Could not connect to remote host";
295c300
< 		return error(errConnectNoRoute);
---
> 		return error(errConnectNoRoute,str,socket_errno);
299c304
< 		return error(errConnectNoRoute);
---
> 		return error(errConnectNoRoute,str,socket_errno);
302c307
< 		return error(errConnectBusy);
---
> 		return error(errConnectBusy,str,socket_errno);
305c310
< 		return error(errConnectInvalid);
---
> 		return error(errConnectInvalid,str,socket_errno);
308c313
< 		return error(errConnectRefused);
---
> 		return error(errConnectRefused,str,socket_errno);
310c315
< 		return error(errConnectTimeout);
---
> 		return error(errConnectTimeout,str,socket_errno);
312c317
< 		return error(errConnectFailed);
---
> 		return error(errConnectFailed,str,socket_errno);
317c322
< Socket::Error Socket::error(Error err, char *errs) const
---
> Socket::Error Socket::error(Error err, char *errs, long systemError) const
320a326
> 	syserr = systemError;
339,340c345
< 			SockException ex = string(errs);
< 			throw ex;
---
> 			throw SockException(string(errs), err, systemError);
346a352,357
> const char *Socket::getSystemErrorString(void) const
> {
> 	SockException e(errstr, errid, syserr);
> 	return e.getSystemErrorString();
> }
> 
352c363
< 		return error(errBroadcastDenied);
---
> 		return error(errBroadcastDenied,"Could not set socket broadcast option",socket_errno);
363c374
< 		return error(errKeepaliveDenied);
---
> 		return error(errKeepaliveDenied,"Could not set socket keep-alive option",socket_errno);
375c386
< 	return error(errServiceUnavailable);
---
> 	return error(errServiceUnavailable,"Socket lingering not supported");
386c397
< 		return error(errRoutingDenied);
---
> 		return error(errRoutingDenied,"Could not set dont-route socket option",socket_errno);
398c409
< 		return error(errNoDelay);
---
> 		return error(errNoDelay,"Could not set tcp-nodelay socket option",socket_errno);
430c441
< 		return error(errServiceUnavailable);
---
> 		return error(errServiceUnavailable,"Unknown type-of-service");
433c444
< 		return error(errServiceDenied);
---
> 		return error(errServiceDenied,"Could not set type-of-service",socket_errno);
436c447
< 	return error(errServiceUnavailable);
---
> 	return error(errServiceUnavailable,"Socket type-of-service not supported",socket_errno);
444c455
< 		return error(errMulticastDisabled);
---
> 		return error(errMulticastDisabled,"Multicast not enabled on socket");
450c461
< 	return error(errServiceUnavailable);
---
> 	return error(errServiceUnavailable,"Multicast not supported");
460c471
< 		return error(errMulticastDisabled);
---
> 		return error(errMulticastDisabled,"Multicast not enabled on socket");
470c481
< 	return error(errServiceUnavailable);
---
> 	return error(errServiceUnavailable,"Multicast not supported");
564c575
< 		error(errCopyFailed);
---
> 		error(errCopyFailed,"Could not duplicate socket handle",socket_errno);
628c639
< 		error(errInput);
---
> 		error(errInput,"Could not read from socket",socket_errno);
633c644
< 			error(errInputInterrupt);
---
> 			error(errInputInterrupt,"Socket read interrupted",socket_errno);
636c647
< 			error(errInput);
---
> 			error(errInput,"Could not read from socket",socket_errno);
651c662
< 		error(errResourceFailure);
---
> 		error(errResourceFailure,"Could not get socket address",socket_errno);
673c684
< 			error(errNotConnected);
---
> 			error(errNotConnected,"Could not get peer address",socket_errno);
676c687
< 			error(errResourceFailure);
---
> 			error(errResourceFailure,"Could not get peer address",socket_errno);
707c718
< 	return error(errServiceUnavailable);
---
> 	return error(errServiceUnavailable,"Multicast not supported");
719c730
< 		return error(errMulticastDisabled);
---
> 		return error(errMulticastDisabled,"Multicast not enabled on socket");
727c738
< 	return error(errServiceUnavailable);
---
> 	return error(errServiceUnavailable,"Multicast not supported");
739c750
< 		return error(errMulticastDisabled);
---
> 		return error(errMulticastDisabled,"Multicast not enabled on socket");
747c758
< 	return error(errServiceUnavailable);
---
> 	return error(errServiceUnavailable,"Multicast not supported");
772c783
< 		error(errBindingFailed);
---
> 		error(errBindingFailed,"Could not bind socket",socket_errno);
856c867
< 		error(errBindingFailed);
---
> 		error(errBindingFailed,"Could not bind socket",socket_errno);
863c874
< 		error(errBindingFailed);
---
> 		error(errBindingFailed,"Could not listen on socket",socket_errno);
1059c1070
< 		error(errResourceFailure);
---
> 		error(errResourceFailure, "Could not allocate socket stream buffers");
1106c1117
<             error(errTimeout);
---
>             error(errTimeout,"Socket read timed out",socket_errno);
1116c1127
< 				error(errInput);
---
> 				error(errInput,"Could not read from socket",socket_errno);
1135c1146
< 		error(errTimeout);
---
> 		error(errTimeout,"Socket read timed out",socket_errno);
1145c1156
< 			error(errInput);
---
> 			error(errInput,"Could not read from socket",socket_errno);
1191c1202
< 				error(errOutput);
---
> 				error(errOutput,"Could not write to socket",socket_errno);
1214c1225
< 				error(errOutput);
---
> 				error(errOutput,"Could not write to socket",socket_errno);

--------------Boundary-00=_XL9OWT7NDMWKRRC41G1C--




From fedemp@wanadoo.es Sat Nov 16 17:22:17 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18DBKS-0008WQ-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 17:22:16 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18DBKO-0008Uj-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 17:22:14 -0500
Received: from [62.37.236.135] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18DBKN-0008TY-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 17:22:11 -0500
Received: from risitas (62-37-68-105.dialup.uni2.es [62.37.68.105])
	by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id gAGMb4i14160;
	Sat, 16 Nov 2002 23:37:06 +0100 (MET)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18DBLm-0005Vb-00; Sat, 16 Nov 2002 23:23:38 +0100
Date: Sat, 16 Nov 2002 23:23:37 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Prochnow, Christian" <cproch@seculogix.de>
Cc: bug-commoncpp@gnu.org
Subject: Re: Patch for socket error/exception handling
Message-ID: <20021116222337.GH670@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: "Prochnow, Christian" <cproch@seculogix.de>,
	bug-commoncpp@gnu.org
References: <200211161501.09805.cproch@seculogix.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200211161501.09805.cproch@seculogix.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Great! It is in CVS (HEAD). I have added code for win32 (based
on FormatMessage). It think that as soon as the win32 code is well
tested, we should incorporate this patch to 1.0.x as well.

On Sat, Nov 16, 2002 at 03:01:09PM +0100, Prochnow, Christian wrote:
> Hi,
> 
> this patch (against CVS head) adds more informative socket error-handling 
> functions to the Socket classes. It is now possible to retrieve the "real" 
> system error message to display more informative error messages to the user. 
> Support for win32 system error messages is currently missing - i need to 
> figure out how one can retrieve them under win32 - i think FormatMessage or 
> something should do the job.
> 
> Regards,
> Christian Prochnow
> 





From cproch@freiverkehr.de Mon Nov 18 05:50:04 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18DjTg-0007bA-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 05:50:04 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18DjTY-0007S9-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 05:50:01 -0500
Received: from h-62.96.239.30.host.de.colt.net ([62.96.239.30] helo=mail.freiverkehr.de)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18DjTX-0007Nd-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 05:49:55 -0500
Received: from cproch.freiverkehr.de (CPROCH [10.100.102.211]) by mail.freiverkehr.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W923MQWD; Mon, 18 Nov 2002 11:49:50 +0100
Content-Type: text/plain;
  charset="us-ascii"
From: "Prochnow, Christian" <cproch@freiverkehr.de>
Organization: Berliner Freiverkehr AG
To: bug-commoncpp@gnu.org
Subject: piostream's on Redhat 7.3
Date: Mon, 18 Nov 2002 11:53:51 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211181153.51339.cproch@freiverkehr.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 !

The piostream's do not compile under RedHat 7.3. The missing files are lo=
cated=20
under /usr/include/g++v3/.

g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY -=
g -O2=20
-D_GNU_SOURCE -I/usr/include/libxml2 -I../include=20
-Wp,-MD,.deps/pio_globals.pp -c pio_globals.cpp  -fPIC -DPIC -o=20
=2Elibs/pio_globals.lo
In file included from ../include/cc++/postream:49,
                 from pio_globals.cpp:46:
=2E./include/cc++/pios:46:80: bits/char_traits.h: No such file or directo=
ry
In file included from ../include/cc++/postream:49,
                 from pio_globals.cpp:46:
=2E./include/cc++/pios:48:52: bits/localefwd.h: No such file or directory
=2E./include/cc++/pios:49:62: bits/ios_base.h: No such file or directory
=2E./include/cc++/pios:51:21: streambuf: No such file or directory
=2E./include/cc++/pios:52:30: bits/basic_ios.h: No such file or directory
In file included from pio_globals.cpp:46:
=2E./include/cc++/postream:50:19: ostream: No such file or directory
In file included from ../include/cc++/postream:516,
                 from pio_globals.cpp:46:
=2E./include/cc++/postream.tcc:41:18: locale: No such file or directory
In file included from pio_globals.cpp:47:
=2E./include/cc++/pistream:50:18: limits: No such file or directory
In file included from ../include/cc++/pistream:296,
                 from pio_globals.cpp:47:
=2E./include/cc++/pistream.tcc:41:18: locale: No such file or directory
pio_globals.cpp:48:31: ext/stdio_filebuf.h: No such file or directory
make[1]: *** [pio_globals.lo] Error 1

Regards, Christian Prochnow




From fedemp@bulbasaur.rediris.es Mon Nov 18 07:16:59 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18Dkpm-0002qZ-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 07:16:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18DkHV-0004F5-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 06:41:36 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18DkHT-0004C5-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 06:41:31 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18DkHp-0000LS-00; Mon, 18 Nov 2002 12:41:53 +0100
Date: Mon, 18 Nov 2002 12:41:53 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Prochnow, Christian" <cproch@freiverkehr.de>
Cc: bug-commoncpp@gnu.org
Subject: Re: piostream's on Redhat 7.3
Message-ID: <20021118114153.GA492@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: "Prochnow, Christian" <cproch@freiverkehr.de>,
	bug-commoncpp@gnu.org
References: <200211181153.51339.cproch@freiverkehr.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200211181153.51339.cproch@freiverkehr.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Yes, the current implementation of piostremas requires a quite
updated gcc. We know it compiles well with gcc 3.2. gcc 2.x and 3.0.x
will surely not work. Curiously, I recall I was able to build cc++
piostreams with gcc 3.1 on RedHat 7.3. What version are you using?

On Mon, Nov 18, 2002 at 11:53:51AM +0100, Prochnow, Christian wrote:
> Hi !
> 
> The piostream's do not compile under RedHat 7.3. The missing files are located 
> under /usr/include/g++v3/.
> 
> g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY -g -O2 
> -D_GNU_SOURCE -I/usr/include/libxml2 -I../include 
> -Wp,-MD,.deps/pio_globals.pp -c pio_globals.cpp  -fPIC -DPIC -o 
> .libs/pio_globals.lo
> In file included from ../include/cc++/postream:49,
>                  from pio_globals.cpp:46:
> ../include/cc++/pios:46:80: bits/char_traits.h: No such file or directory
> In file included from ../include/cc++/postream:49,
>                  from pio_globals.cpp:46:
> ../include/cc++/pios:48:52: bits/localefwd.h: No such file or directory
> ../include/cc++/pios:49:62: bits/ios_base.h: No such file or directory
> ../include/cc++/pios:51:21: streambuf: No such file or directory
> ../include/cc++/pios:52:30: bits/basic_ios.h: No such file or directory
> In file included from pio_globals.cpp:46:
> ../include/cc++/postream:50:19: ostream: No such file or directory
> In file included from ../include/cc++/postream:516,
>                  from pio_globals.cpp:46:
> ../include/cc++/postream.tcc:41:18: locale: No such file or directory
> In file included from pio_globals.cpp:47:
> ../include/cc++/pistream:50:18: limits: No such file or directory
> In file included from ../include/cc++/pistream:296,
>                  from pio_globals.cpp:47:
> ../include/cc++/pistream.tcc:41:18: locale: No such file or directory
> pio_globals.cpp:48:31: ext/stdio_filebuf.h: No such file or directory
> make[1]: *** [pio_globals.lo] Error 1
> 
> Regards, Christian Prochnow
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From cproch@freiverkehr.de Mon Nov 18 10:53:01 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18DoCr-0007Mi-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 10:53:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18DoCm-0007Je-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 10:53:00 -0500
Received: from h-62.96.239.30.host.de.colt.net ([62.96.239.30] helo=mail.freiverkehr.de)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18DoCk-0007JF-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 10:52:54 -0500
Received: from cproch.freiverkehr.de (CPROCH [10.100.102.211]) by mail.freiverkehr.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W923MRQ1; Mon, 18 Nov 2002 16:52:52 +0100
Content-Type: text/plain;
  charset="us-ascii"
From: "Prochnow, Christian" <cproch@freiverkehr.de>
Organization: Berliner Freiverkehr AG
To: bug-commoncpp@gnu.org
Subject: CCXX_CLASS_EXPORT Missing in class Time/Datetim
Date: Mon, 18 Nov 2002 16:56:56 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211181656.56726.cproch@freiverkehr.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 List,

tried to compile under win32 today,=20
and found that the macro CCXX_CLASS_EXPORT is missing in numbers.h for th=
e=20
class Datetime and Time.

Regards,
Christian Prochnow




From mad@brasmap.com.br Mon Nov 18 11:32:17 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18Door-0004vF-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 11:32:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18Dool-0004si-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 11:32:15 -0500
Received: from acate.com.br ([200.215.17.89])
	by monty-python.gnu.org with smtp (Exim 4.10)
	id 18Dook-0004rE-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 11:32:10 -0500
Received: (qmail 19512 invoked from network); 18 Nov 2002 16:32:07 -0000
Received: from unknown (HELO cli004.brasmap) (192.168.1.13)
  by acate.com.br with SMTP; 18 Nov 2002 16:32:03 -0000
Received: from brasmap.com.br (localhost.localdomain [127.0.0.1])
	by cli004.brasmap (8.11.1/8.11.1) with SMTP id gAIGVpP07870
	for <bug-commoncpp@gnu.org>; Mon, 18 Nov 2002 14:31:51 -0200
Date: Mon, 18 Nov 2002 14:31:51 -0200
From: Marcelo Dalmas <mad@brasmap.com.br>
To: bug-commoncpp@gnu.org
Subject: Re: CCXX_CLASS_EXPORT Missing in class Time/Datetim
Message-Id: <20021118143151.6d8ed760.mad@brasmap.com.br>
In-Reply-To: <200211181656.56726.cproch@freiverkehr.de>
References: <200211181656.56726.cproch@freiverkehr.de>
Organization: BRASMAP Sistemas
X-Mailer: Sylpheed version 0.8.5 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="Multipart_Mon__18_Nov_2002_14:31:51_-0200_08229090"
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.

--Multipart_Mon__18_Nov_2002_14:31:51_-0200_08229090
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Really, it's missing.

On Mon, 18 Nov 2002 16:56:56 +0100
"Prochnow, Christian" <cproch@freiverkehr.de> wrote:

> Hi List,
> 
> tried to compile under win32 today, 
> and found that the macro CCXX_CLASS_EXPORT is missing in numbers.h for the 
> class Datetime and Time.
> 
> Regards,
> Christian Prochnow
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 


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


--Multipart_Mon__18_Nov_2002_14:31:51_-0200_08229090
Content-Type: application/octet-stream;
 name="date.patch.gz"
Content-Disposition: attachment;
 filename="date.patch.gz"
Content-Transfer-Encoding: base64

H4sICIoU2T0AA2RhdGUucGF0Y2gApVDLTsMwEDzHX7FHwE2dhLZQV0hBgUMlJBDtobcqcbatJceO
bKdC4ufJg4oLVAh88Ozs7FizXuoS3zhILVRTIhOCUqabqkDrxgdy9/9DXrMV7KRCDqxxlikjcsXE
0VljPCts7qq8ZsJUldGirhP2fZTRkVj0VuJR6j3YFpw0GuLxhJRyt4OwgdC2DL7Ch2H4w15BEkUJ
i+YsvoV4wq/nfBoF3VOU0rOWOO4tM55MeRSTNIUwiZLRDdAB0pQAXEHqDsZ6WGqPe7RQ5A5L8LJC
ECp3btwNMQIk7CmsW4XQoc6yzWabPd2vVtvHzcvz63pQ4Z1AbY1H4bHkBAJl2m9wKIwu3WIIMpv1
QXr4W5CH3GOvcqibQknRd0Yncj7nb8zdGvDZ4V0ZnFwX3bX14KvLBfkAf5ZjFJUCAAA=

--Multipart_Mon__18_Nov_2002_14:31:51_-0200_08229090--




From cproch@freiverkehr.de Mon Nov 18 12:38:20 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18Dpql-0003i6-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 12:38:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18Dpqh-0003hW-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 12:38:18 -0500
Received: from h-62.96.239.30.host.de.colt.net ([62.96.239.30] helo=mail.freiverkehr.de)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18Dpqg-0003hC-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 12:38:14 -0500
Received: from cproch.freiverkehr.de (CPROCH [10.100.102.211]) by mail.freiverkehr.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W923MRXY; Mon, 18 Nov 2002 18:38:13 +0100
From: "Prochnow, Christian" <cproch@freiverkehr.de>
Organization: Berliner Freiverkehr AG
To: bug-commoncpp@gnu.org
Subject: Patch for SocketPort bug and NetworkDeviceInfo
Date: Mon, 18 Nov 2002 18:42:18 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="------------Boundary-00=_I69SGJ19PMZX84G9O0TY"
Message-Id: <200211181842.18685.cproch@freiverkehr.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/>

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

Hi List,

this patch (agains CVS HEAD) fixes a SIGSEGV in the SocketPort outbound=20
tcp-constructor when connection does not complete immediatly.
It also fixes the win32 part of NetworkDeviceInfo class and adds a missin=
g=20
CCXX_EXPORT for that class.

Regards,
Christian Prochnow

--------------Boundary-00=_I69SGJ19PMZX84G9O0TY
Content-Type: text/x-diff;
  charset="us-ascii";
  name="commoncpp2.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="commoncpp2.diff"

? autom4te-2.53.cache
? doc/commoncpp2.info
? doc/commoncpp2.info-1
? doc/commoncpp2.info-2
? doc/commoncpp2.info-3
? ssl/.libs
? ssl/Makefile
? ssl/Makefile.in
? ssl/libccssl.la
? ssl/sslcontext.lo
? ssl/sslengine.lo
? ssl/sslsession.lo
? win32/CCXX2.rc
Index: include/cc++/network.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/include/cc++/network.h,v
retrieving revision 1.1
diff -r1.1 network.h
104c104
< 	friend bool enumNetworkDevices(std::vector<NetworkDeviceInfo>& devs);
---
> 	friend CCXX_EXPORT(bool) enumNetworkDevices(std::vector<NetworkDeviceInfo>& devs);
Index: src/network.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/network.cpp,v
retrieving revision 1.1
diff -r1.1 network.cpp
49a50
> #include <ws2tcpip.h>
149c150
< 	INTERFACE_INFO* iflist = (INTERFACE_INFO*)buffer;
---
> 	INTERFACE_INFO* iflist = (INTERFACE_INFO*)outbuff;
154c155
< 	InetMaskAddress maskaddr("255.255.255.255");
---
> 	InetMaskAddress maskaddr("0.0.0.0");
159,160c160,161
< 		brdaddr = ((sockaddr_in&)iflist[i].iiBroadcastAddress).sin_addr;
< 		maskaddr = ((sockaddr_in&)iflist[i].iiNetmask).sin_addr;
---
> 		(InetAddress&)brdaddr = ((sockaddr_in&)iflist[i].iiBroadcastAddress).sin_addr;
> 		(InetAddress&)maskaddr = ((sockaddr_in&)iflist[i].iiNetmask).sin_addr;
164c165
< 	CloseHandle(s);
---
> 	closesocket(s);
Index: src/port.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/port.cpp,v
retrieving revision 1.8
diff -r1.8 port.cpp
284d283
< 			setDetectOutput(true);
295a295,296
> 	if(state == CONNECTING)
> 		setDetectOutput(true);

--------------Boundary-00=_I69SGJ19PMZX84G9O0TY--




From fedemp@wanadoo.es Mon Nov 18 15:22:39 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18DsPn-0005fs-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 15:22:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18DsPh-0005eM-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 15:22:37 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18DsPf-0005dP-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 15:22:32 -0500
Received: from risitas ([80.103.115.44])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAJ3Ix205002
	for <bug-commoncpp@gnu.org>; Tue, 19 Nov 2002 04:18:59 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18DsRE-0000rh-00
	for <bug-commoncpp@gnu.org>; Mon, 18 Nov 2002 21:24:08 +0100
Date: Mon, 18 Nov 2002 21:24:08 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: CCXX_CLASS_EXPORT Missing in class Time/Datetim
Message-ID: <20021118202408.GA320@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <200211181656.56726.cproch@freiverkehr.de> <20021118143151.6d8ed760.mad@brasmap.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021118143151.6d8ed760.mad@brasmap.com.br>
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 has been fixed for next releases.

On Mon, Nov 18, 2002 at 02:31:51PM -0200, Marcelo Dalmas wrote:
> Really, it's missing.
> 
> On Mon, 18 Nov 2002 16:56:56 +0100
> "Prochnow, Christian" <cproch@freiverkehr.de> wrote:
> 
> > Hi List,
> > 
> > tried to compile under win32 today, 
> > and found that the macro CCXX_CLASS_EXPORT is missing in numbers.h for the 
> > class Datetime and Time.
> > 
> > Regards,
> > Christian Prochnow
> > 
> > 
> > 
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > 
> 
> 
> -- 
> Marcelo Dalmas
> BRASMAP Sistemas
> www.brasmap.com.br
> Fone/Fax: (48) 333-2218 ramal 2114
> 





From fedemp@wanadoo.es Mon Nov 18 15:23:19 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18DsQQ-0005tg-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 15:23:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18DsQJ-0005s3-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 15:23:15 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18DsQH-0005r1-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 15:23:10 -0500
Received: from risitas ([80.103.115.44])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAJ3Jc205197
	for <bug-commoncpp@gnu.org>; Tue, 19 Nov 2002 04:19:38 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18DsRs-0000rr-00
	for <bug-commoncpp@gnu.org>; Mon, 18 Nov 2002 21:24:48 +0100
Date: Mon, 18 Nov 2002 21:24:47 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: Patch for SocketPort bug and NetworkDeviceInfo
Message-ID: <20021118202447.GB320@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <200211181842.18685.cproch@freiverkehr.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200211181842.18685.cproch@freiverkehr.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Ok, applied to both HEAD and RELEASE1.

On Mon, Nov 18, 2002 at 06:42:18PM +0100, Prochnow, Christian wrote:
> Hi List,
> 
> this patch (agains CVS HEAD) fixes a SIGSEGV in the SocketPort outbound 
> tcp-constructor when connection does not complete immediatly.
> It also fixes the win32 part of NetworkDeviceInfo class and adds a missing 
> CCXX_EXPORT for that class.
> 
> Regards,
> Christian Prochnow





From ariston@cs.und.edu Mon Nov 18 22:47:35 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18DzMM-0004fM-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 22:47:34 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18DzMJ-0004au-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 22:47:33 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18DzMI-0004Z8-00
	for bug-commoncpp@gnu.org; Mon, 18 Nov 2002 22:47:30 -0500
Received: from penguin.cs.und.nodak.edu (penguin.cs.und.nodak.edu [134.129.212.25])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gAJ3vifX002937
	for <bug-commoncpp@gnu.org>; Mon, 18 Nov 2002 21:57:45 -0600
Date: Mon, 18 Nov 2002 21:43:44 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
X-X-Sender: <ariston@localhost.localdomain>
To: <bug-commoncpp@gnu.org>
Subject: strerror_r(3) used incorrectly
Message-ID: <Pine.LNX.4.33.0211182136180.19208-200000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-1859641577-1037677424=:19208"
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.

--8323328-1859641577-1037677424=:19208
Content-Type: TEXT/PLAIN; charset=US-ASCII


See included patch.  Note that my code assumes that that allocated
2048-byte buffer is large enough for any error string.  strerror_r(3) will
return 0 in this case, or will return ERANGE if not enough space was
available in the buffer.  As IOException::getSystemErrorString() is
declared throw(), I didn't see a better way to deal with the ERANGE
possibility other than wild assumption (although it really does seem a
valid assumption to me).

This patch is against the current CVS HEAD (21:45 CST, Nov 18)

Ari Johnson


--8323328-1859641577-1037677424=:19208
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="commoncpp2-exception.cpp-patch"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.4.33.0211182143440.19208@localhost.localdomain>
Content-Description: 
Content-Disposition: attachment; filename="commoncpp2-exception.cpp-patch"

SW5kZXg6IHNyYy9leGNlcHRpb24uY3BwDQo9PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09DQpSQ1MgZmlsZTogL2N2c3Jvb3QvY29tbW9uY3BwL2NvbW1vbmNwcDIv
c3JjL2V4Y2VwdGlvbi5jcHAsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjQN
CmRpZmYgLXIxLjQgZXhjZXB0aW9uLmNwcA0KNzljNzksODANCjwgCXJldHVy
biBzdHJlcnJvcl9yKF9zeXN0ZW1FcnJvciwgX3N5c3RlbUVycm9yU3RyaW5n
LCBlcnJTdHJTaXplKTsNCi0tLQ0KPiAJKHZvaWQpIHN0cmVycm9yX3IoX3N5
c3RlbUVycm9yLCBfc3lzdGVtRXJyb3JTdHJpbmcsIGVyclN0clNpemUpOw0K
PiAJcmV0dXJuIF9zeXN0ZW1FcnJvclN0cmluZzsNCg==
--8323328-1859641577-1037677424=:19208--



From cproch@freiverkehr.de Tue Nov 19 02:15:19 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18E2bP-0004XH-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 02:15:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18E2bL-0004TL-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 02:15:18 -0500
Received: from h-62.96.239.30.host.de.colt.net ([62.96.239.30] helo=mail.freiverkehr.de)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18E2bK-0004RR-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 02:15:14 -0500
Received: from cproch.freiverkehr.de (CPROCH [10.100.102.211]) by mail.freiverkehr.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W923MS2N; Tue, 19 Nov 2002 08:15:07 +0100
From: "Prochnow, Christian" <cproch@freiverkehr.de>
Organization: Berliner Freiverkehr AG
To: bug-commoncpp@gnu.org
Subject: Patch for Socket::getSender()
Date: Tue, 19 Nov 2002 08:19:22 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="------------Boundary-00=_A0BTRI7WTFJN6SA8N8SB"
Message-Id: <200211190819.22214.cproch@freiverkehr.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/>

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

Hi List,

Socket::getSender() crashes under Win32 (WSAEMSGSIZE) - here's a patch.

Regards,
Christian

--=20
Christian Prochnow
Berliner Freiverkehr (Aktien) AG - Kurf=FCrstendamm 117 - 10711 Berlin, G=
ermany
Fon: +49-30-89606409, Fax: +49-30-89021389 - EMail: cproch@freiverkehr.de

--------------Boundary-00=_A0BTRI7WTFJN6SA8N8SB
Content-Type: text/x-diff;
  charset="us-ascii";
  name="socket.cpp.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="socket.cpp.patch"

--- socket.cpp.orig	Sat Nov 16 20:54:00 2002
+++ socket.cpp	Tue Nov 19 08:03:22 2002
@@ -622,31 +622,29 @@
 	int rc = ::recvfrom(so, &buf, 1, MSG_PEEK,
 			    (struct sockaddr *)&from, &len);
 
-	if(rc == 1)
+#ifdef WIN32
+	if(rc < 1 && WSAGetLastError() != WSAEMSGSIZE)
 	{
 		if(port)
-			*port = ntohs(from.sin_port);
+			*port = 0;
+
+		memset((void*) &from, 0, sizeof(from));
+		error(errInput,"Could not read from socket",socket_errno);
 	}
-	else
+#else
+	if(rc < 1)
 	{
 		if(port)
 			*port = 0;
-		memset(&from.sin_addr, 0, sizeof(from.sin_addr));
-	}
-	if(rc < 0)
-	{
-#ifdef WIN32
+
+		memset((void*) &from, 0, sizeof(from));
 		error(errInput,"Could not read from socket",socket_errno);
-#else
-		switch(errno)
-		{
-		case EINTR:
-			error(errInputInterrupt,"Socket read interrupted",socket_errno);
-			break;
-		default:
-			error(errInput,"Could not read from socket",socket_errno);
-		}
+	}
 #endif
+	else
+	{
+		if(port)
+			*port = ntohs(from.sin_port);
 	}
 
 	return InetHostAddress(from.sin_addr);

--------------Boundary-00=_A0BTRI7WTFJN6SA8N8SB--




From fedemp@bulbasaur.rediris.es Tue Nov 19 05:35:30 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18E5j8-0006Dj-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 05:35:30 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18E5j5-00068I-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 05:35:29 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18E5j5-00065o-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 05:35:27 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18E5jV-0000EP-00
	for <bug-commoncpp@gnu.org>; Tue, 19 Nov 2002 11:35:53 +0100
Date: Tue, 19 Nov 2002 11:35:52 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: strerror_r(3) used incorrectly
Message-ID: <20021119103551.GA427@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <Pine.LNX.4.33.0211182136180.19208-200000@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.33.0211182136180.19208-200000@localhost.localdomain>
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/>

	Fixed. I hope 2048 bytes is enough for the error string :).

	Curiously, the strerror_r of glibc 2.2.4 returns a char*, and
recent versions of autoconf define the STRERROR_R_CHAR_P symbol if you
check for AC_FUNC_STRERROR_R and strerror_r returns char*. So, it
seems that your patch saves us a check for the strerror_r return type
:)

On Mon, Nov 18, 2002 at 09:43:44PM -0600, Ari Johnson wrote:
> 
> See included patch.  Note that my code assumes that that allocated
> 2048-byte buffer is large enough for any error string.  strerror_r(3) will
> return 0 in this case, or will return ERANGE if not enough space was
> available in the buffer.  As IOException::getSystemErrorString() is
> declared throw(), I didn't see a better way to deal with the ERANGE
> possibility other than wild assumption (although it really does seem a
> valid assumption to me).
> 
> This patch is against the current CVS HEAD (21:45 CST, Nov 18)
> 
> Ari Johnson
> 



From fedemp@bulbasaur.rediris.es Tue Nov 19 05:50:56 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18E5y4-0001oD-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 05:50:56 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18E5xy-0001ma-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 05:50:55 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18E5xy-0001mW-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 05:50:50 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18E5yR-0000FL-00
	for <bug-commoncpp@gnu.org>; Tue, 19 Nov 2002 11:51:19 +0100
Date: Tue, 19 Nov 2002 11:51:19 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: Patch for Socket::getSender()
Message-ID: <20021119105118.GB427@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <200211190819.22214.cproch@freiverkehr.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200211190819.22214.cproch@freiverkehr.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Ok, fixed in HEAD.

On Tue, Nov 19, 2002 at 08:19:22AM +0100, Prochnow, Christian wrote:
> Hi List,
> 
> Socket::getSender() crashes under Win32 (WSAEMSGSIZE) - here's a patch.
> 
> Regards,
> Christian
> 
> -- 
> Christian Prochnow
> Berliner Freiverkehr (Aktien) AG - Kurfürstendamm 117 - 10711 Berlin, Germany
> Fon: +49-30-89606409, Fax: +49-30-89021389 - EMail: cproch@freiverkehr.de





From lizzy@soggytrousers.net Tue Nov 19 16:54:58 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18EGKg-0001De-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 16:54:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18EGKd-0001BM-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 16:54:57 -0500
Received: from dc-mx13.cluster1.charter.net ([209.225.8.23])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18EGKd-0001BC-00
	for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 16:54:55 -0500
Received: from [66.190.65.189] (HELO liliwhite.renaissance.oasis)
  by dc-mx13.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9)
  with ESMTP id 7430264 for bug-commoncpp@gnu.org; Tue, 19 Nov 2002 16:54:53 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1 (Debian))
	id 18EGKX-0008T3-00
	for <bug-commoncpp@gnu.org>; Tue, 19 Nov 2002 15:54:49 -0600
To: bug-commoncpp@gnu.org
Subject: SHA1Digest and SHA256Digest
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 19 Nov 2002 15:54:49 -0600
Message-ID: <87u1idql7a.fsf@liliwhite.renaissance.oasis>
Lines: 39
X-Mailer: Gnus v5.7/Emacs 20.7
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/>

Dear Everyone on this list,

   I wrote SHA1Digest and SHA256Digest classes that interface with the
Digest class and I would like to contribute it to the library.

   If this is okay with you all, I would then like to post them onto
this mailing list, although I do have one question.

   Do you believe it is proper for the digest classes to throw
exceptions in CommonC++? There are only two instances that I would
like to add exceptions, but they are important:

   1) After calculating a Digest, the "calculating sum" is corrupted
      in that one should *not* continue to feed the object data. If
      after the sum has been made and the client tries to give the
      object data, I would like to throw a "Digest All Ready
      Calculated" exception.

      Note that this should not hinder one from copying the object and
      extracting the sum from the *copy* and then continue to use the
      original.

   2) There is a size limit as to how much data a digest may represent
      (for SHA1 and SHA256, this is 2^64). Going over this limit
      should cause a "Digest Overflow" exception.

   I currently have not implemented the exceptions except that they
are in pseudo-code just waiting to be written. Nor have I written the
copy construtors although the compiler generated ones may work fine
(this needs to be verified).

   So, provided this is something the administrators are interested in
allowing into the MAIN branch, should the exceptions be raised? (The
size currently just loops over and there is no check on a corrupted
sum.)

   Thank you,

   Elizabeth



From fedemp@bulbasaur.rediris.es Wed Nov 20 05:12:03 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18ERpy-00033v-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 05:12:02 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18ERpw-00032w-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 05:12:02 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18ERpv-00032H-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 05:11:59 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18ERqI-0000FX-00; Wed, 20 Nov 2002 11:12:22 +0100
Date: Wed, 20 Nov 2002 11:12:22 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Elizabeth Barham <lizzy@soggytrousers.net>
Cc: bug-commoncpp@gnu.org
Subject: Re: SHA1Digest and SHA256Digest
Message-ID: <20021120101221.GA543@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Elizabeth Barham <lizzy@soggytrousers.net>,
	bug-commoncpp@gnu.org
References: <87u1idql7a.fsf@liliwhite.renaissance.oasis>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87u1idql7a.fsf@liliwhite.renaissance.oasis>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Hi,

On Tue, Nov 19, 2002 at 03:54:49PM -0600, Elizabeth Barham wrote:
> Dear Everyone on this list,
> 
>    I wrote SHA1Digest and SHA256Digest classes that interface with the
> Digest class and I would like to contribute it to the library.
> 
>    If this is okay with you all, I would then like to post them onto
> this mailing list, although I do have one question.
> 

	Good. I think these classes fit perfectly with cc++.

>    Do you believe it is proper for the digest classes to throw
> exceptions in CommonC++? There are only two instances that I would
> like to add exceptions, but they are important:
> 
>    1) After calculating a Digest, the "calculating sum" is corrupted
>       in that one should *not* continue to feed the object data. If
>       after the sum has been made and the client tries to give the
>       object data, I would like to throw a "Digest All Ready
>       Calculated" exception.
> 
>       Note that this should not hinder one from copying the object and
>       extracting the sum from the *copy* and then continue to use the
>       original.
> 
>    2) There is a size limit as to how much data a digest may represent
>       (for SHA1 and SHA256, this is 2^64). Going over this limit
>       should cause a "Digest Overflow" exception.
> 
>    I currently have not implemented the exceptions except that they
> are in pseudo-code just waiting to be written. Nor have I written the
> copy construtors although the compiler generated ones may work fine
> (this needs to be verified).
> 

	Personally, I think that adding the two exception cases is ok.

>    So, provided this is something the administrators are interested in
> allowing into the MAIN branch, should the exceptions be raised? (The
> size currently just loops over and there is no check on a corrupted
> sum.)
> 

	Umm, I think these two classes are suitable for both 1.0 and
1.1 series.  I would say that they could be added along with a short
demo/test app, regardless of whether exceptions are included or not.

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



From cproch@freiverkehr.de Wed Nov 20 06:26:14 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18ESzl-00021J-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 06:26:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18ESzh-0001zq-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 06:26:12 -0500
Received: from h-62.96.239.30.host.de.colt.net ([62.96.239.30] helo=mail.freiverkehr.de)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18ESzg-0001y2-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 06:26:08 -0500
Received: from cproch.freiverkehr.de (CPROCH [10.100.102.211]) by mail.freiverkehr.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W923M4N2; Wed, 20 Nov 2002 12:26:03 +0100
From: "Prochnow, Christian" <cproch@freiverkehr.de>
Organization: Berliner Freiverkehr AG
To: bug-commoncpp@gnu.org
Subject: Patch for bug's in SocketPort and IOException
Date: Wed, 20 Nov 2002 12:30:37 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="------------Boundary-00=_1BHVFADT0TD53VVT3XQR"
Message-Id: <200211201230.37943.cproch@freiverkehr.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/>

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

Hi List,

found some problems in recently added features:

in IOException::getSystemErrorString():
- _systemErrorString must only be allocated once.

- i thought "if ( NULL =3D=3D _systemErrorString )" was not the intention=
 of the=20
programmer, instead it should be "if ( NULL !=3D _systemErrorString )"

- in IOException::~IOException():
delete _systemErrorString - simply not right - array`s are deleted with
delete[] not with delete.

SocketPort connecting constructor:
- do not restore the O_NDLAY flag when ::connect() has failed!
 this caused the connectError() to store a zero error code cause the fcnt=
l()=20
after connect() succeeded :)

Regards,
Christian

--=20
Christian Prochnow
Berliner Freiverkehr (Aktien) AG - Kurf=FCrstendamm 117 - 10711 Berlin, G=
ermany
Fon: +49-30-89606409, Fax: +49-30-89021389 - EMail: cproch@freiverkehr.de

--------------Boundary-00=_1BHVFADT0TD53VVT3XQR
Content-Type: text/x-diff;
  charset="us-ascii";
  name="commoncpp2.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="commoncpp2.diff"

? autom4te-2.53.cache
? commoncpp2.diff
? doc/commoncpp2.info
? doc/commoncpp2.info-1
? doc/commoncpp2.info-2
? doc/commoncpp2.info-3
? ssl/.libs
? ssl/Makefile
? ssl/Makefile.in
? ssl/libccssl.la
? ssl/sslcontext.lo
? ssl/sslengine.lo
? ssl/sslsession.lo
? win32/CCXX2.rc
Index: src/exception.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/exception.cpp,v
retrieving revision 1.5
diff -r1.5 exception.cpp
71c71
< 	delete _systemErrorString;
---
> 	delete[] _systemErrorString;
77c77,79
< 	_systemErrorString = new char[errStrSize];
---
> 	if(!_systemErrorString)
> 		_systemErrorString = new char[errStrSize];
> 
83c85
< 	if ( NULL == _systemErrorString ) {
---
> 	if ( NULL != _systemErrorString ) {
Index: src/port.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/port.cpp,v
retrieving revision 1.9
diff -r1.9 port.cpp
264,270d263
< #ifndef WIN32
< 	fcntl(so, F_SETFL, opts);
< #else
< 	opts = 0;
< 	ioctlsocket(so,FIONBIO,&opts);
< #endif
< 
280c273
< 		if(WSAGetLastError() == WSAEINPROGRESS)
---
> 		if(WSAGetLastError() == WSAEINPROGRESS || WSAGetLastError() == WSAEWOULDBLOCK)
288c281
< 			error(connectError(), "Could not connect", socket_errno);
---
> 			connectError();
291a285,291
> 
> #ifndef WIN32
> 	fcntl(so, F_SETFL, opts);
> #else
> 	opts = 0;
> 	ioctlsocket(so,FIONBIO,&opts);
> #endif

--------------Boundary-00=_1BHVFADT0TD53VVT3XQR--




From fedemp@bulbasaur.rediris.es Wed Nov 20 07:38:59 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18EU8B-0006by-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 07:38:59 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18EU87-0006TG-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 07:38:58 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18EU86-0006T7-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 07:38:55 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18EU8X-0000zS-00
	for <bug-commoncpp@gnu.org>; Wed, 20 Nov 2002 13:39:22 +0100
Date: Wed, 20 Nov 2002 13:39:21 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: Patch for bug's in SocketPort and IOException
Message-ID: <20021120123921.GA445@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <200211201230.37943.cproch@freiverkehr.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200211201230.37943.cproch@freiverkehr.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

On Wed, Nov 20, 2002 at 12:30:37PM +0100, Prochnow, Christian wrote:
> Hi List,
> 
> found some problems in recently added features:
> 

	Ok, fixed.

> in IOException::getSystemErrorString():
> - _systemErrorString must only be allocated once.
> 
> - i thought "if ( NULL == _systemErrorString )" was not the intention of the 
> programmer, instead it should be "if ( NULL != _systemErrorString )"
> 

	Umm, yes, I do not know why I put the if before the
FormatMessage instead of the new.

> - in IOException::~IOException():
> delete _systemErrorString - simply not right - array`s are deleted with
> delete[] not with delete.
> 
> SocketPort connecting constructor:
> - do not restore the O_NDLAY flag when ::connect() has failed!
>  this caused the connectError() to store a zero error code cause the fcntl() 
> after connect() succeeded :)
> 

	I have applied the patch section for this to both HEAD and
RELEASE1.

> Regards,
> Christian
> 
> -- 
> Christian Prochnow
> Berliner Freiverkehr (Aktien) AG - Kurfürstendamm 117 - 10711 Berlin, Germany
> Fon: +49-30-89606409, Fax: +49-30-89021389 - EMail: cproch@freiverkehr.de





From lizzy@soggytrousers.net Wed Nov 20 15:22:51 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18EbN5-0003kW-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 15:22:51 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18EbMw-0003T1-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 15:22:50 -0500
Received: from dc-mx12.cluster1.charter.net ([209.225.8.22])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18EbMv-0003Pi-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 15:22:41 -0500
Received: from [66.190.65.189] (HELO liliwhite.renaissance.oasis)
  by dc-mx12.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9)
  with ESMTP id 45050531 for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 15:22:37 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1 (Debian))
	id 18EbMq-0002nw-00
	for <bug-commoncpp@gnu.org>; Wed, 20 Nov 2002 14:22:36 -0600
To: bug-commoncpp@gnu.org
Subject: Re: SHA1Digest and SHA256Digest
References: <87u1idql7a.fsf@liliwhite.renaissance.oasis> <20021120101221.GA543@bulbasaur.rediris.es>
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 20 Nov 2002 14:22:35 -0600
In-Reply-To: Federico Montesino Pouzols's message of "Wed, 20 Nov 2002 11:12:22 +0100"
Message-ID: <87isysvvn8.fsf@liliwhite.renaissance.oasis>
Lines: 960
X-Mailer: Gnus v5.7/Emacs 20.7
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/>

Federico Montesino Pouzols <fedemp@altern.org> writes:

> 	Good. I think these classes fit perfectly with cc++.

Great!

> 	Personally, I think that adding the two exception cases is ok.

Done.

Here is the diff from anonymous CVS. Following that will be the two
files:

   src/sha.cpp
   demo/shadigest.cpp

Note that I did make some adjustments to some of the files in order to
build, most notably socket.h.

Thank you, Elizabeth

# ###################################################################### #
# diff file

? include
? lib
? demo/shadigest
? demo/shadigest.cpp
? src/sha.cpp
? tests/Makefile
? tests/Makefile.in
Index: demo/Makefile.am
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp/demo/Makefile.am,v
retrieving revision 1.20
diff -u -p -3 -r1.20 Makefile.am
--- demo/Makefile.am	3 Feb 2002 14:04:37 -0000	1.20
+++ demo/Makefile.am	20 Nov 2002 20:15:25 -0000
@@ -17,7 +17,7 @@ LDADD = $(top_srcdir)/src/libccgnu.la $(
 Z_LIBS = -lz
 
 noinst_PROGRAMS = tcp tcpthread tcpservice serial cmdlineopt \
-	urlfetch xmlfetch portsample slogTest
+	urlfetch xmlfetch portsample slogTest shadigest
 noinst_HEADERS = serialecho.h SampleSocketPort.h
 
 urlfetch_SOURCES = urlfetch.cpp
@@ -41,3 +41,7 @@ serial_LDADD = $(top_srcdir)/src/libccex
 
 cmdlineopt_SOURCES = cmdlineopt.cpp
 cmdlineopt_LDADD = $(top_srcdir)/src/libccext.la $(XML_LIBS) $(Z_LIBS) $(LDADD)
+
+shadigest_SOURCES = shadigest.cpp
+shadigest_LDADD = $(top_srcdir)/src/libccext.la $(XML_LIBS) $(Z_LIBS) $(LDADD)
+
Index: src/Makefile.am
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp/src/Makefile.am,v
retrieving revision 1.8
diff -u -p -3 -r1.8 Makefile.am
--- src/Makefile.am	4 Dec 2001 19:03:24 -0000	1.8
+++ src/Makefile.am	20 Nov 2002 20:15:25 -0000
@@ -31,7 +31,7 @@ libccgnu_la_SOURCES = thread.cpp mutex.c
 
 libccext_la_SOURCES = buffer.cpp fifo.cpp pipe.cpp numbers.cpp \
 	cmdoptns.cpp url.cpp xml.cpp persist.cpp engine.cpp digest.cpp \
-	date.cpp groups.cpp md5.cpp
+	date.cpp groups.cpp md5.cpp sha.cpp
 
 # private.h are internal headers
 # export.h are used by other library
Index: src/digest.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp/src/digest.h,v
retrieving revision 1.10
diff -u -p -3 -r1.10 digest.h
--- src/digest.h	2 Jun 2002 08:02:31 -0000	1.10
+++ src/digest.h	20 Nov 2002 20:15:26 -0000
@@ -62,6 +62,8 @@ class CCXX_CLASS_EXPORT Digest;
 class CCXX_CLASS_EXPORT ChecksumDigest;
 class CCXX_CLASS_EXPORT CRC16Digest;
 class CCXX_CLASS_EXPORT MD5Digest;
+class CCXX_CLASS_EXPORT SHA1Digest;
+class CCXX_CLASS_EXPORT SHA256Digest;
 #endif
 
 /**
@@ -245,6 +247,214 @@ public:
 
 	void putDigest(const unsigned char *buffer, unsigned len);
 };
+
+/**
+ * DigestException
+ *
+ * Exception classes that pertain to errors when making or otherwise
+ * working with digests.
+ *
+ * @author Elizabeth Barham <lizzy@soggytrousers.net>
+ * @short Exceptions involving digests.
+ */
+
+class DigestException : public Exception {
+public:
+  DigestException(const std::string & what_arg) throw();
+  virtual ~DigestException() throw();
+};
+ 
+
+/**
+ * SHATumbler
+ *
+ * Class used by the SHA Digest Classes.
+ *
+ * Represents a "tumbler" group, similar to a row in a combination
+ * lock. Each part is made to roll-over, its size dependent upon
+ * int_type.
+ *
+ * @author Elizabeth Barham <lizzy@soggytrousers.net>
+ * @short SHA Helper Class */
+
+template <class int_type>
+class SHATumbler {
+
+public:
+  SHATumbler(int);
+
+  SHATumbler(const SHATumbler&);
+  SHATumbler& operator=(const SHATumbler&);
+
+  int_type& operator[](int);
+
+  ~SHATumbler();
+  
+  SHATumbler operator+(const SHATumbler& addend) const;
+  SHATumbler& operator+=(const SHATumbler& addend);
+  std::ostream & toString(std::ostream & os);
+
+  friend std::ostream &operator<<(std::ostream &os, SHATumbler<int_type>& ia)
+  {return ia.toString(os);};
+  
+  unsigned getSize();
+  unsigned placeInBuffer(unsigned char *);
+    
+private:
+  int_type * h;
+  int size;
+};
+
+/**
+ * SHAConstant
+ *
+ * Note that this constant is set in sha.cpp and that each constant in
+ * the array is 64 bits wide. The constants themselves pertain to both
+ * SHA-256 and SHA-512, the only difference is that SHA-256 expects
+ * her constants to be 32 bits wide and only 64 are needed.
+ *
+ * @auther Elizabeth Barham <lizzy@soggytrousers.net>
+ * @short Contains SHA constants
+ */
+
+class SHAConstant {
+protected:
+  const static uint64_t K[];
+};
+
+/**
+ * SHADigest
+ *
+ * Generic Class that is the base class of the various SHA*Digest
+ * classes.
+ *
+ * uint_type == The "Unsigned Integer Type" which is large enough to
+ * hold the total length of a given message in bits. For SHA1 and
+ * SHA256, this is 64 bits, so we use "uint64_t";
+ *
+ * "blockSizeInBytes" == various SHA digests use different message
+ * size blocks - the basic units in which to split a message up in.
+ * For example, SHA1 and SHA256 use 512 bit blocks, and so in
+ * bytes this is 64.
+ *
+ * @author Elizabeth Barham <lizzy@soggytrousers.net>
+ * @short Base class for the SHA*Digests
+ */
+
+template <class uint_type, unsigned blockSizeInBytes>
+class SHADigest : public Digest {
+private:
+  uint_type totalLengthInBits;
+
+  void copyTempBlock(const SHADigest &);
+
+protected:
+  unsigned char tempBlock[blockSizeInBytes];
+  void initDigest(void);
+
+  virtual void processBlock(const unsigned char * buffer) = 0;
+  void padBuffer(unsigned char * buffer);
+
+  bool completed;
+
+  SHADigest();
+  SHADigest(const SHADigest & other);
+  SHADigest & operator=(const SHADigest & other);
+
+public:
+  unsigned getSize(void) = 0;
+  void putDigest(const unsigned char * buffer, unsigned length) throw(DigestException);
+  std::ostream & strDigest(std::ostream &os) = 0;
+
+};
+
+#define S(n,X) ( ( ( X ) << ( n ) ) | ( ( X ) >> ( 32 - n ) ) )
+
+/* ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** */
+/* RR == "right rotation by n bits" (Sn)                             */
+/* RS == "right shift by n byts"    (Rn)                             */
+/* (see p. 2, "Descriptions of SHA-256, SHA-384, SHA-512"            */
+/*   <http://csrc.nist.gov/encryption/shs/sha256-384-512.pdf>)       */
+/* ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** */
+
+#define RR(n,X) ( ( ( X ) >> n ) | ( ( X ) << ( 32 - n ) ) )
+#define RS(n,X) ( ( ( X ) >> n ) )
+
+/**
+ * SHA64DigestHelper
+ *
+ * Simply a base class for the SHA*Digest classes that share
+ * functionality after their "unsigned int" type and block size are
+ * known (uint64_t and 64)
+ *
+ * @author Elizabeth Barham <lizzy@soggytrousers.net>
+ * @short Base class for the 64-bit wide SHA*Digests.
+ */
+
+class SHA64DigestHelper: public SHADigest<uint64_t, 64> {
+protected:
+  SHATumbler<uint32_t> h;
+  SHATumbler<uint32_t> a;
+
+  SHA64DigestHelper(unsigned);
+  SHATumbler<uint32_t> getDigest();
+
+public:
+  unsigned getDigest(unsigned char * buffer) { return getDigest().placeInBuffer(buffer); }
+  std::ostream & strDigest(std::ostream & os);
+
+  SHA64DigestHelper(const SHA64DigestHelper & other);
+  SHA64DigestHelper & operator=(const SHA64DigestHelper & other);
+};
+
+/**
+ * SHA1Digest
+ *
+ * SHA1Digest proper.
+ *
+ * @author Elizabeth Barham <lizzy@soggytrousers.net>
+ * @short SHA-1 Digest Implementation
+ */
+
+class SHA1Digest : public SHA64DigestHelper {
+protected:
+  void processBlock(const unsigned char * buffer);
+
+public:
+  SHA1Digest();
+  void initDigest();
+  unsigned getSize() { return 20; }
+  SHA1Digest(const SHA1Digest & other);
+};
+
+/**
+ * SHA256Digest
+ * @author Elizabeth Barham <lizzy@soggytrousers.net>
+ * @short SHA-256 Digest Implementation
+ */
+
+class SHA256Digest : public SHA64DigestHelper, public SHAConstant {
+protected:
+  void processBlock(const unsigned char * buffer);
+
+public:
+  SHA256Digest();
+  SHA256Digest(const SHA256Digest &);
+  void initDigest();
+  unsigned getSize() { return 32; }
+};
+
+/* In case anyone is wondering why SHA-512 and SHA-384 are not
+ * implemented, it is the better way to make them is to use an 128-bit
+ * unsigned integer. To my understanding, the gcc 3.* has either
+ * introduced uint128_t or shall introduce it. When it does, something
+ * similar to SHA64DigestHelper can easily be made, perhaps:
+ *
+ * "class SHA128DigestHelper : public SHADigest<uint128_t, 128>"
+ *
+ * -- Elizabeth Barham, November 20, 2002, Fort Worth, TX, USA
+ */
+
 
 #ifdef	CCXX_NAMESPACES
 };
Index: src/socket.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp/src/socket.cpp,v
retrieving revision 1.19
diff -u -p -3 -r1.19 socket.cpp
--- src/socket.cpp	2 Jun 2002 08:50:19 -0000	1.19
+++ src/socket.cpp	20 Nov 2002 20:15:26 -0000
@@ -73,7 +73,7 @@ using namespace std;
 #endif
 
 #ifdef WIN32
-static SOCKET dupSocket(SOCKET so,enum Socket::State state)
+static SOCKET dupSocket(SOCKET so, sockstate_t state)
 {
 	if (state == Socket::STREAM)
 		return dup(so);
Index: src/socket.h
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp/src/socket.h,v
retrieving revision 1.15
diff -u -p -3 -r1.15 socket.h
--- src/socket.h	2 Jun 2002 08:50:19 -0000	1.15
+++ src/socket.h	20 Nov 2002 20:15:27 -0000
@@ -569,7 +569,7 @@ private:
 	mutable const char *errstr;
 
 	void setSocket(void);
-	friend SOCKET dupSocket(SOCKET s,Socket::State state);
+	friend SOCKET dupSocket(SOCKET s, sockstate_t state);
 
 protected:
 	mutable struct
Index: src/xml.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp/src/xml.cpp,v
retrieving revision 1.8
diff -u -p -3 -r1.8 xml.cpp
--- src/xml.cpp	29 May 2002 08:55:40 -0000	1.8
+++ src/xml.cpp	20 Nov 2002 20:15:28 -0000
@@ -51,9 +51,9 @@
 
 #ifdef	HAVE_LIBXML
 
-#include <parser.h>
-#include <parserInternals.h>
-#include <xmlIO.h>
+#include <libxml/parser.h>
+#include <libxml/parserInternals.h>
+#include <libxml/xmlIO.h>
 #include <cstdarg>
 
 #ifdef	CCXX_NAMESPACES

# ################################################################## #
# src/sha.cpp

/* -*- C++ -*- */
// Copyright (C) 1999-2002 Open Source Telecom Corporation.
//  
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation; either version 2 of the License, or
// (at your option) any later version.
// 
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
// GNU General Public License for more details.
// 
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software 
// Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
// 
// As a special exception to the GNU General Public License, permission is 
// granted for additional uses of the text contained in its release 
// of Common C++.
// 
// The exception is that, if you link the Common C++ library with other files
// to produce an executable, this does not by itself cause the
// resulting executable to be covered by the GNU General Public License.
// Your use of that executable is in no way restricted on account of
// linking the Common C++ library code into it.
// 
// This exception does not however invalidate any other reasons why
// the executable file might be covered by the GNU General Public License.
// 
// This exception applies only to the code released under the 
// name Common C++.  If you copy code from other releases into a copy of
// Common C++, as the General Public License permits, the exception does
// not apply to the code that you add in this way.  To avoid misleading
// anyone as to the status of such modified files, you must delete
// this exception notice from them.
// 
// If you write modifications of your own for Common C++, it is your choice
// whether to permit this exception to apply to your modifications.
// If you do not wish that, delete this exception notice.  

#include "config.h"
#include "export.h"
#include "strchar.h"
#include "exception.h"
#include "thread.h"
#include "digest.h"
#include <cstdio>
#include <iomanip>

#ifdef	WIN32
#include <io.h>
#endif

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

/**
 * DigestException
 */

DigestException::DigestException(const std::string & what_arg) throw() :
  Exception(what_arg)
{ }

DigestException::~DigestException() throw()
{ }


/** 
 * SHAConstant::K
 */

/* note to use K32_ADJUST when attempting to access K with a 32 bit
 * integer.
 */

#if __BYTE_ORDER == __LITTLE_ENDIAN
#define K32_ADJUST 1
#else
#define K32_ADJUST 0
#endif

const uint64_t SHAConstant::K[] = {
  0x428a2f98d728ae22LL,
  0x7137449123ef65cdLL,
  0xb5c0fbcfec4d3b2fLL,
  0xe9b5dba58189dbbcLL,
  0x3956c25bf348b538LL,
  0x59f111f1b605d019LL,
  0x923f82a4af194f9bLL,
  0xab1c5ed5da6d8118LL,
  0xd807aa98a3030242LL,
  0x12835b0145706fbeLL,
  0x243185be4ee4b28cLL,
  0x550c7dc3d5ffb4e2LL,
  0x72be5d74f27b896fLL,
  0x80deb1fe3b1696b1LL,
  0x9bdc06a725c71235LL,
  0xc19bf174cf692694LL,
  0xe49b69c19ef14ad2LL,
  0xefbe4786384f25e3LL,
  0x0fc19dc68b8cd5b5LL,
  0x240ca1cc77ac9c65LL,
  0x2de92c6f592b0275LL,
  0x4a7484aa6ea6e483LL,
  0x5cb0a9dcbd41fbd4LL,
  0x76f988da831153b5LL,
  0x983e5152ee66dfabLL,
  0xa831c66d2db43210LL,
  0xb00327c898fb213fLL,
  0xbf597fc7beef0ee4LL,
  0xc6e00bf33da88fc2LL,
  0xd5a79147930aa725LL,
  0x06ca6351e003826fLL,
  0x142929670a0e6e70LL,
  0x27b70a8546d22ffcLL,
  0x2e1b21385c26c926LL,
  0x4d2c6dfc5ac42aedLL,
  0x53380d139d95b3dfLL,
  0x650a73548baf63deLL,
  0x766a0abb3c77b2a8LL,
  0x81c2c92e47edaee6LL,
  0x92722c851482353bLL,
  0xa2bfe8a14cf10364LL,
  0xa81a664bbc423001LL,
  0xc24b8b70d0f89791LL,
  0xc76c51a30654be30LL,
  0xd192e819d6ef5218LL,
  0xd69906245565a910LL,
  0xf40e35855771202aLL,
  0x106aa07032bbd1b8LL,
  0x19a4c116b8d2d0c8LL,
  0x1e376c085141ab53LL,
  0x2748774cdf8eeb99LL,
  0x34b0bcb5e19b48a8LL,
  0x391c0cb3c5c95a63LL,
  0x4ed8aa4ae3418acbLL,
  0x5b9cca4f7763e373LL,
  0x682e6ff3d6b2b8a3LL,
  0x748f82ee5defb2fcLL,
  0x78a5636f43172f60LL,
  0x84c87814a1f0ab72LL,
  0x8cc702081a6439ecLL,
  0x90befffa23631e28LL,
  0xa4506cebde82bde9LL,
  0xbef9a3f7b2c67915LL,
  0xc67178f2e372532bLL,
  0xca273eceea26619cLL,
  0xd186b8c721c0c207LL,
  0xeada7dd6cde0eb1eLL,
  0xf57d4f7fee6ed178LL,
  0x06f067aa72176fbaLL,
  0x0a637dc5a2c898a6LL,
  0x113f9804bef90daeLL,
  0x1b710b35131c471bLL,
  0x28db77f523047d84LL,
  0x32caab7b40c72493LL,
  0x3c9ebe0a15c9bebcLL,
  0x431d67c49c100d4cLL,
  0x4cc5d4becb3e42b6LL,
  0x597f299cfc657e2aLL,
  0x5fcb6fab3ad6faecLL,
  0x6c44198c4a475817LL
};


/* *********************************************************************
   SHATumbler
   ********************************************************************* */

template <class int_type>
SHATumbler<int_type>::SHATumbler(int s): size(s) {
  h = new int_type[size];
}

template <class int_type>
SHATumbler<int_type>::SHATumbler(const SHATumbler<int_type>& copy) {
  size = copy.size;
  h = new int_type[size];
  memcpy((void*)h,(void*)copy.h,sizeof(int_type) * size);
}

template <class int_type>
SHATumbler<int_type> & SHATumbler<int_type>::operator=(const SHATumbler<int_type> & assign) {
  memcpy((void*)h,(void*)assign.h,sizeof(int_type) * size);
  return *this;
}

template <class int_type>
int_type & SHATumbler<int_type>::operator[](int x) {
  return h[x];
}

template <class int_type>
SHATumbler<int_type>::~SHATumbler() {
  delete[] h;
}

template <class int_type>
SHATumbler<int_type> SHATumbler<int_type>::operator+(const SHATumbler<int_type>& addend) const {
  SHATumbler<int_type> rv = *this;
  rv += addend;
  return(rv);
}

template <class int_type>
SHATumbler<int_type>& SHATumbler<int_type>::operator+=(const SHATumbler<int_type>& addend)  {
  for(int i = 0; i < size; i++) {
    h[i] += addend.h[i];
  }
  return(*this);
}

template <class int_type>
std::ostream & SHATumbler<int_type>::toString(std::ostream & os) {
  for(int i = 0 ; i < size ; i++) {

#ifdef DEBUG_SHATUMBLER
    if(i != 0)
      os << " ";
#endif
      
    os << std::hex << std::setw(sizeof(h[i]) * 2) << std::setfill('0') << h[i];
  }
  return(os);
}

template <class int_type>
unsigned SHATumbler<int_type>::placeInBuffer(unsigned char * buffer) {
  unsigned memsize = getSize();
  memcpy((void*) buffer, (void*) h, memsize);
  return(memsize);
}

template <class int_type>
unsigned SHATumbler<int_type>::getSize() {
  unsigned memsize = sizeof(int_type) * size;
  return(memsize);
}

/* *********************************************************************
   SHADigest
   ********************************************************************* */
template <class uint_type, unsigned blockSizeInBytes>
SHADigest<uint_type, blockSizeInBytes>::SHADigest() {
  initDigest();
}


template <class uint_type, unsigned blockSizeInBytes>
void SHADigest<uint_type, blockSizeInBytes>::padBuffer(unsigned char * buffer) {
  int lengthOfTotalLength     = blockSizeInBytes / 8;
  uint_type totalLengthInBytes = totalLengthInBits / 8;
  int remainder = totalLengthInBytes % blockSizeInBytes;

  int fillTo;

  if( (blockSizeInBytes - ( remainder + 1 )) >= lengthOfTotalLength ) {
    fillTo = (blockSizeInBytes - lengthOfTotalLength);
  } else {
    fillTo = blockSizeInBytes;
  }
  
  buffer[remainder++] = 0x80;

  do {
    bzero(buffer + remainder, fillTo - remainder);
    if(fillTo != blockSizeInBytes) {
      *((uint_type*)(buffer + fillTo)) = totalLengthInBits;
    }
    processBlock(buffer);
    remainder = 0;
    fillTo -= lengthOfTotalLength;
  } while(fillTo >= (blockSizeInBytes - lengthOfTotalLength));
  completed = true;
}

template <class uint_type, unsigned blockSizeInBytes>
void SHADigest<uint_type, blockSizeInBytes>::initDigest() {
  totalLengthInBits = 0;
  completed = false;
}

template <class uint_type, unsigned blockSizeInBytes>
void SHADigest<uint_type, blockSizeInBytes>::putDigest(const unsigned char * buffer, unsigned length) 
  throw(DigestException)
{

  if(completed) {
    throw(DigestException("Corrupted Digest!"));
  }
  
  if( length > (totalLengthInBits / 8) + length ) {
    throw(DigestException("Digest Length Overflow!"));
  }

  // fill in tempBlock if necessarry, then process it...

  uint_type bytesInTempBlock;

  if(bytesInTempBlock = (totalLengthInBits/8) % blockSizeInBytes) {
    unsigned bytesLeftInTempBlock = blockSizeInBytes - bytesInTempBlock;
    unsigned numToCopy;

    if(length < bytesLeftInTempBlock) {
      numToCopy = length;
    } else {
      numToCopy = bytesLeftInTempBlock;
    }

    memcpy(tempBlock + bytesInTempBlock, buffer, numToCopy);
    length -= numToCopy;
  }

  unsigned numBlocksToProcess = length / blockSizeInBytes;
  unsigned numBytesToStore   = length % blockSizeInBytes;

  // process incoming stream

  for(unsigned i = 0; i < numBlocksToProcess; i++) {
    processBlock(buffer + (i * blockSizeInBytes));
  }

  // place any data that could not be processed into tempBlock

  for(unsigned i = 0; i < numBytesToStore; i++) {
    tempBlock[i] = (buffer + (numBlocksToProcess * blockSizeInBytes))[i];
  }
  totalLengthInBits += 8 * (bytesInTempBlock +  (numBlocksToProcess * blockSizeInBytes) + numBytesToStore);
}

template <class uint_type, unsigned blockSizeInBytes>
SHADigest<uint_type, blockSizeInBytes>::SHADigest(const SHADigest<uint_type, blockSizeInBytes> & other) :
  totalLengthInBits(other.totalLengthInBits),
  completed(other.completed)
 {
   copyTempBlock(other);
 }

template <class uint_type, unsigned blockSizeInBytes>
SHADigest<uint_type, blockSizeInBytes> &  SHADigest<uint_type, blockSizeInBytes>::operator=(const SHADigest & other) {
  if(this == &other) {
    return *this;
  }

  this->completed = other.completed;
  this->totalLengthInBits = other.totalLengthInBits;
  copyTempBlock(other);
}

template <class uint_type, unsigned blockSizeInBytes>
void  SHADigest<uint_type, blockSizeInBytes>::copyTempBlock(const SHADigest & other) {
  if(uint_type remainder = ( (totalLengthInBits / 8) % blockSizeInBytes)) {
    memcpy( (void*)tempBlock, (void*)other.tempBlock, remainder * (sizeof(unsigned char)));
  }
}

/* *********************************************************************
   SHA64DigestHelper
   ********************************************************************* */

SHA64DigestHelper::SHA64DigestHelper(unsigned tumblerSize):
  h(SHATumbler<uint32_t>(tumblerSize)), 
  a(SHATumbler<uint32_t>(tumblerSize))
{ }

SHATumbler<uint32_t> SHA64DigestHelper::getDigest() {
  if(!completed) {
    padBuffer(tempBlock);
  }
  return h;
}

std::ostream & SHA64DigestHelper::strDigest(std::ostream & os) {
  SHATumbler<uint32_t> hCopy = getDigest();
  os << hCopy;
  return(os);
}

SHA64DigestHelper::SHA64DigestHelper(const SHA64DigestHelper & other) :
  SHADigest<uint64_t, 64>(other),
  h(other.h),
  a(other.a)
{ }

SHA64DigestHelper & SHA64DigestHelper::operator=(const SHA64DigestHelper & other)
{
  if(this == &other) {
    return(*this);
  }

  SHADigest<uint64_t, 64>::operator=(other);

  this->h = other.h;
  this->a = other.a;

  return *this;
}



/* *********************************************************************
   SHA1Digest
   ********************************************************************* */

SHA1Digest::SHA1Digest(): SHA64DigestHelper(5) {
  initDigest();
}

void SHA1Digest::initDigest() {
  h[0] = 0x67452301;
  h[1] = 0xefcdab89;
  h[2] = 0x98badcfe;
  h[3] = 0x10325476;
  h[4] = 0xc3d2e1f0;
  SHADigest<uint64_t, 64>::initDigest();
}

SHA1Digest::SHA1Digest(const SHA1Digest & other): SHA64DigestHelper(other)
{ }

void SHA1Digest::processBlock(const unsigned char * buffer) {
  uint32_t W[80];

  memcpy((void*)W, (void*)buffer, sizeof(uint32_t) * 16);
  for(int t = 16; t < 80; t++) {
    W[t] = S(1,(W[t-3] ^ W[t-8] ^ W[t-14] ^ W[t-16]));
  }
  a = h;
  uint32_t temp;
  for(int t = 0; t < 80; t++) {
    switch(t/20) {
    case(0):
      temp = ((a[1] & a[2]) | (~a[1] & a[3])) + 0x5a827999;
      break;
    case(1):
      temp = ((a[1] ^ a[2] ^ a[3]) + 0x6ed9eba1);
      break;
    case(2):
      temp = ((a[1] & a[2]) | (a[1] & a[3]) | (a[2] & a[3])) + 0x8f1bbcdc;
      break;
    default:
      temp = (a[1] ^ a[2] ^ a[3]) + 0xca62c1d6;
    }
    temp += S(5,a[0]) + a[4] + W[t];
    a[4] = a[3];
    a[3] = a[2];
    a[2] = S(30,a[1]);
    a[1] = a[0];
    a[0] = temp;

#ifdef DEBUG_SHA1
    std::cerr << std::setw(2) << std::dec << t << ": " << a << std::endl;
#endif
    
  }
  h += a;
}

/* *********************************************************************
   SHA256Digest
   ********************************************************************* */

SHA256Digest::SHA256Digest(): SHA64DigestHelper(8) {
  initDigest();
}


SHA256Digest::SHA256Digest(const SHA256Digest & other):
  SHA64DigestHelper(other)
{ }


void SHA256Digest::initDigest() {
  h[0] = 0x6a09e667;
  h[1] = 0xbb67ae85;
  h[2] = 0x3c6ef372;
  h[3] = 0xa54ff53a;
  h[4] = 0x510e527f;
  h[5] = 0x9b05688c;
  h[6] = 0x1f83d9ab;
  h[7] = 0x5be0cd19;
  SHADigest<uint64_t, 64>::initDigest();
}

#define Ch(x,y,z) ( ( ( x ) & ( y ) ) ^ (  ( ~ x  ) & ( z ) ) )
#define Maj(x,y,z) ( ( ( x ) & ( y ) ) ^ ( ( x ) & ( z ) ) ^ ( ( y ) & ( z ) ) )
#define E0(x) ( RR(2,x) ^ RR(13,x) ^ RR(22,x) )
#define E1(x) ( RR(6,x) ^ RR(11,x) ^ RR(25,x) )
#define o0(x) ( RR(7,x) ^ RR(18,x) ^ RS(3,x) )
#define o1(x) ( RR(17,x) ^ RR(19,x) ^ RS(10,x) )

void SHA256Digest::processBlock(const unsigned char * buffer) {
  uint32_t t1, t2;
  uint32_t W[64];
  uint32_t * M = (uint32_t*)buffer;
  uint32_t * K32 = (uint32_t*)SHAConstant::K;

  a = h;
  for(int j = 0; j < 64 ; j++) {
    if(j < 16) {
      W[j] = M[j];
    } else {
      W[j] = o1(W[j-2]) + W[j-7] + o0(W[j-15]) + W[j-16];
    }

    t1 = a[7] + E1(a[4]) + Ch(a[4],a[5],a[6]) + K32[(j * 2) + K32_ADJUST] + W[j];
    t2 = E0(a[0]) + Maj(a[0],a[1],a[2]);
    
    a[7] = a[6];
    a[6] = a[5];
    a[5] = a[4];
    a[4] = a[3] + t1;
    a[3] = a[2];
    a[2] = a[1];
    a[1] = a[0];
    a[0] = t1 + t2;
#ifdef DEBUG_SHA256
    std::cerr << std::setw(2) << std::dec << j << std::hex << ": " << a << std::endl;
#endif
  }
  h += a;
}


#ifdef	CCXX_NAMESPACES
};
#endif	


#ifdef TEST_SHA
#define BUFF_SIZE 1024
#include <stdio.h>

int main(int argc, char * argv[]) {
  unsigned char buff[1024];

  SHA256Digest d256;
  unsigned length;

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

    if(fp) {
      while(length = fread(buff, sizeof(unsigned char), BUFF_SIZE, fp)) {
	try {
	  d256.putDigest(buff, length);
	} catch(DigestException & d) {
	  std::cerr << "Digest Exception: " << d.getString() << std::endl;
	  fclose(fp);
	  break;
	}
      }

      std::cout << d256 << "  " << argv[i] << std::endl;

      fclose(fp);
    }

  }
}
#endif


# ###################################################################### #
# demo/shadigest.cpp

#include "config.h"
#include "strchar.h"
#include "exception.h"
#include "thread.h"
#include "digest.h"
#include <stdio.h>

#define BUFF_SIZE 1024

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

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

    if(fp) {
      while(length = fread(buff, sizeof(unsigned char), BUFF_SIZE, fp)) {
	d256.putDigest(buff, length);
      }

      std::cout << d256 << "  " << argv[i] << std::endl;

      fclose(fp);
    }
  }
}

# ##################################################################### #



From fedemp@wanadoo.es Wed Nov 20 16:23:38 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18EcJu-0001ST-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 16:23:38 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18EcJm-0001Qz-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 16:23:37 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18EcJl-0001PQ-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 16:23:30 -0500
Received: from risitas (62-36-176-30.dialup.uni2.es [62.36.176.30])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gAKLKH230221;
	Wed, 20 Nov 2002 22:20:19 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18EcKw-00033G-00; Wed, 20 Nov 2002 22:24:42 +0100
Date: Wed, 20 Nov 2002 22:24:42 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Cc: Erik Enge <eenge@prium.net>, bayonne-devel@lists.sourceforge.net,
   bug-commoncpp@gnu.org
Subject: Re: [Bayonne-devel]Compiling Bayonne 1.0.8 gives "XML support is not available".
Message-ID: <20021120212442.GA610@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: David Sugar <dyfet@ostel.com>,
	Erik Enge <eenge@prium.net>, bayonne-devel@lists.sourceforge.net,
	bug-commoncpp@gnu.org
References: <87smxwjor9.fsf@prium.net> <Pine.LNX.4.44.0211201009500.18093-100000@home.sys>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0211201009500.18093-100000@home.sys>
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/>

	From c++ 1.0.6, xml.h will give this error when you do
"#include <cc++/xml.h>" but COMMON_XML_PARSING is not defined in
cc++/config.h (xml was not compiled when building cc++). This is
because we thought that an error should be reported in order to
prevent people from including xml.h when xml related classes are not
really there.

	Unfortunately, this change may break some applications based
on cc++ when xml support is not compiled, and I am afraid that bayonne
may be one of those. From a quick look, I see that no xml related
stuff is compiled in bayonne when COMMON_XML_PARSING is not defined
(everything is inside a "#ifdef COMMON_XML_PARSING" or a "#ifdef
XML_SCRIPTS"). However, in bayonne.h, the following lines:

#ifndef __CCXX_XML_H__
#include <cc++/xml.h>
#endif

	include xml.h without checking for COMMON_XML_PARSING, which
triggers the #error.

On Wed, Nov 20, 2002 at 10:12:55AM -0500, David Sugar wrote:
> 
> This is because Common C++ was built with XML support enabled, but libxml2
> was not present when Common C++ was being built.
> 
> On 20 Nov 2002, Erik Enge wrote:
> 
> > I'm trying to compile bayonne 1.0.8 on Debian (testing/unstable).  I
> > have the libxml2 and libxml2-dev packages installed.  I'm running a
> > 2.4.18 kernel.
> > 
> > Compiling ccscript (2.3.3), ccrtp (1.0pre0), commoncpp2 (1.0.6) and
> > ccaudio (1.0.4) all succeeds.
> > 
> > However, when I try to compile Bayonne with the folling configure,
> > 
> >   ./configure --without-vpb --without-pika --without-dialogic \
> >               --without-phonedev --prefix=/share/sys/bayonne/bayonne-$ver \
> >               --without-xml
> > 
> > It fails with
> > 
> >   creating freebsd/pkg-plist
> >   creating server/bayonne_install
> >   creating server/ivrconfig.h
> >   Making all in server
> >   make[1]: Entering directory `/share/pak/bayonne/bayonne-1.0.8/server'
> >   c++ -DHAVE_CONFIG_H -I. -I. -I.     -g -O2 -I/share/sys/commoncpp2/commoncpp2-1.0.6/include/cc++2 -g -O2 -D_GNU_SOURCE -DVERPATH=\"1.0.8\"  -c wrapper.cpp
> >   In file included from bayonne.h:25,
> >                    from server.h:18,
> >                    from wrapper.cpp:23:
> >   /share/sys/commoncpp2/commoncpp2-1.0.6/include/cc++2/cc++/xml.h:323: #error "XML support is not available."
> >   make[1]: *** [wrapper.o] Error 1
> >   make[1]: Leaving directory `/share/pak/bayonne/bayonne-1.0.8/server'
> >   make: *** [all-recursive] Error 1
> > 
> > I've tried removing --without-xml but that didn't change the error
> > message.  Would anybody know what I'm missing?
> > 
> > Thanks,
> > 
> > Erik.
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by: To learn the basics of securing 
> > your web site with SSL, click here to get a FREE TRIAL of a Thawte 
> > Server Certificate: http://www.gothawte.com/rd524.html
> > _______________________________________________
> > Bayonne-devel mailing list
> > Bayonne-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bayonne-devel
> > 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: To learn the basics of securing 
> your web site with SSL, click here to get a FREE TRIAL of a Thawte 
> Server Certificate: http://www.gothawte.com/rd524.html
> _______________________________________________
> Bayonne-devel mailing list
> Bayonne-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bayonne-devel



From dyfet@ostel.com Wed Nov 20 21:36:42 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18EhCs-0005u4-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 21:36:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18EhCp-0005qu-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 21:36: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 18EhCp-0005qg-00
	for bug-commoncpp@gnu.org; Wed, 20 Nov 2002 21:36:39 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gAL33CU22235;
	Wed, 20 Nov 2002 22:03:12 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Wed, 20 Nov 2002 22:03:11 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: Erik Enge <eenge@prium.net>, <bayonne-devel@lists.sourceforge.net>,
   <bug-commoncpp@gnu.org>
Subject: Re: [Bayonne-devel]Compiling Bayonne 1.0.8 gives "XML support is
 not available".
In-Reply-To: <20021120212442.GA610@risitas>
Message-ID: <Pine.LNX.4.44.0211202203001.22200-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/>

Okay, that is easy enough to solve....you are right.

On Wed, 20 Nov 2002, Federico Montesino Pouzols wrote:

> 
> 	From c++ 1.0.6, xml.h will give this error when you do
> "#include <cc++/xml.h>" but COMMON_XML_PARSING is not defined in
> cc++/config.h (xml was not compiled when building cc++). This is
> because we thought that an error should be reported in order to
> prevent people from including xml.h when xml related classes are not
> really there.
> 
> 	Unfortunately, this change may break some applications based
> on cc++ when xml support is not compiled, and I am afraid that bayonne
> may be one of those. From a quick look, I see that no xml related
> stuff is compiled in bayonne when COMMON_XML_PARSING is not defined
> (everything is inside a "#ifdef COMMON_XML_PARSING" or a "#ifdef
> XML_SCRIPTS"). However, in bayonne.h, the following lines:
> 
> #ifndef __CCXX_XML_H__
> #include <cc++/xml.h>
> #endif
> 
> 	include xml.h without checking for COMMON_XML_PARSING, which
> triggers the #error.
> 
> On Wed, Nov 20, 2002 at 10:12:55AM -0500, David Sugar wrote:
> > 
> > This is because Common C++ was built with XML support enabled, but libxml2
> > was not present when Common C++ was being built.
> > 
> > On 20 Nov 2002, Erik Enge wrote:
> > 
> > > I'm trying to compile bayonne 1.0.8 on Debian (testing/unstable).  I
> > > have the libxml2 and libxml2-dev packages installed.  I'm running a
> > > 2.4.18 kernel.
> > > 
> > > Compiling ccscript (2.3.3), ccrtp (1.0pre0), commoncpp2 (1.0.6) and
> > > ccaudio (1.0.4) all succeeds.
> > > 
> > > However, when I try to compile Bayonne with the folling configure,
> > > 
> > >   ./configure --without-vpb --without-pika --without-dialogic \
> > >               --without-phonedev --prefix=/share/sys/bayonne/bayonne-$ver \
> > >               --without-xml
> > > 
> > > It fails with
> > > 
> > >   creating freebsd/pkg-plist
> > >   creating server/bayonne_install
> > >   creating server/ivrconfig.h
> > >   Making all in server
> > >   make[1]: Entering directory `/share/pak/bayonne/bayonne-1.0.8/server'
> > >   c++ -DHAVE_CONFIG_H -I. -I. -I.     -g -O2 -I/share/sys/commoncpp2/commoncpp2-1.0.6/include/cc++2 -g -O2 -D_GNU_SOURCE -DVERPATH=\"1.0.8\"  -c wrapper.cpp
> > >   In file included from bayonne.h:25,
> > >                    from server.h:18,
> > >                    from wrapper.cpp:23:
> > >   /share/sys/commoncpp2/commoncpp2-1.0.6/include/cc++2/cc++/xml.h:323: #error "XML support is not available."
> > >   make[1]: *** [wrapper.o] Error 1
> > >   make[1]: Leaving directory `/share/pak/bayonne/bayonne-1.0.8/server'
> > >   make: *** [all-recursive] Error 1
> > > 
> > > I've tried removing --without-xml but that didn't change the error
> > > message.  Would anybody know what I'm missing?
> > > 
> > > Thanks,
> > > 
> > > Erik.
> > > 
> > > 
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by: To learn the basics of securing 
> > > your web site with SSL, click here to get a FREE TRIAL of a Thawte 
> > > Server Certificate: http://www.gothawte.com/rd524.html
> > > _______________________________________________
> > > Bayonne-devel mailing list
> > > Bayonne-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/bayonne-devel
> > > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by: To learn the basics of securing 
> > your web site with SSL, click here to get a FREE TRIAL of a Thawte 
> > Server Certificate: http://www.gothawte.com/rd524.html
> > _______________________________________________
> > Bayonne-devel mailing list
> > Bayonne-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bayonne-devel
> 




From cproch@freiverkehr.de Thu Nov 21 05:31:15 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18Eoc7-0006zi-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 05:31:15 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18Eoc2-0006zR-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 05:31:14 -0500
Received: from h-62.96.239.30.host.de.colt.net ([62.96.239.30] helo=mail.freiverkehr.de)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18Eoc2-0006zM-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 05:31:10 -0500
Received: from cproch.freiverkehr.de (CPROCH [10.100.102.211]) by mail.freiverkehr.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W923MV7W; Thu, 21 Nov 2002 11:31:08 +0100
Content-Type: text/plain;
  charset="iso-8859-15"
From: "Prochnow, Christian" <cproch@freiverkehr.de>
Organization: Berliner Freiverkehr AG
To: bug-commoncpp@gnu.org
Subject: Serious SocketService/SocketPort problems
Date: Thu, 21 Nov 2002 11:35:59 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211211135.59040.cproch@freiverkehr.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 List,

here comes a really serious problem related to SocketService and SocketPo=
rt:

SocketPort() takes a SocketService argument, when SocketPort is created, =
it=20
attaches itself to the given SocketService. Which seems to lead to=20
synchronisation problems.=20
I have a class (say MySocketPort) that is inherited from SocketPort (with=
=20
outbound constructor). So when i create the MySocketPort object in the=20
main-thread the SocketPort() base constructor registers itself with the=20
SocketService which is then started by SocketService::attach().

So when the SocketService-thread begins to run and immediatly tries to=20
dispatch a virtual call to MySocketPort - it will be dispatched to the=20
default implementation (SocketPort::connect()) cause the vtable of=20
MySocketPort is'nt fully setup.

This seems to be timing-related, cause under Linux this works fine - unde=
r=20
Windows XP it crashes (i think new started threads in XP are immediatly=20
executed and the creator-thread gets yield).
=20
I have no idea how to solve this. Only solution would be that SocketPort(=
)=20
does not attach itself when constructing ... instead MySocketPort should=20
attach itself to the SocketService.=20

Thanks in advance,
Christian

--=20
Christian Prochnow
Berliner Freiverkehr (Aktien) AG - Kurf=FCrstendamm 117 - 10711 Berlin, G=
ermany
Fon: +49-30-89606409, Fax: +49-30-89021389 - EMail: cproch@freiverkehr.de




From lizzy@soggytrousers.net Sat Nov 16 21:15:12 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18DExr-0000Rp-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 21:15:11 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18DExl-0000Nk-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 21:15:09 -0500
Received: from dc-mx03.cluster1.charter.net ([209.225.8.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18DEx3-0008BJ-00
	for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 21:14:21 -0500
Received: from [66.190.65.189] (HELO liliwhite.renaissance.oasis)
  by dc-mx03.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9)
  with ESMTP id 44213259 for bug-commoncpp@gnu.org; Sat, 16 Nov 2002 21:14:20 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1 (Debian))
	id 18DEwz-00050Z-00
	for <bug-commoncpp@gnu.org>; Sat, 16 Nov 2002 20:14:17 -0600
To: bug-commoncpp@gnu.org
Subject: SHA1Digest
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 16 Nov 2002 20:14:17 -0600
Message-ID: <87lm3tx7ra.fsf@liliwhite.renaissance.oasis>
Lines: 332
X-Mailer: Gnus v5.7/Emacs 20.7
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/>

Dear CommonC++ Maintainers,

   I really enjoy your fine work and added an SHA1Digest
implementation that adheres to the Digest interface. I tested it and
it works. I would like to contribute it to the project. Thank you,
Elizabeth

/* $Id: sha1.cpp,v 1.6 2002/11/17 02:05:26 lizzy Exp $ */
/*
  
  Digest pseudo abstract class, Copyright (C) 1999-2002 Open Source
  Telecom Corporation

  sha1.cpp, C++ implementation of the SHA-1 digest algorithm, as
    according to FIPS 180-1, <http://www.itl.nist.gov/fipspubs/fip180-1.htm>
  Copyright (C) 2002 Elizabeth Barham

  This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by
  the Free Software Foundation; either version 2 of the License, or
  (at your option) any later version.

  This program is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License for more details.
  
  You should have received a copy of the GNU General Public License
  along with this program; if not, write to the Free Software
  Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

  As a special exception to the GNU General Public License, permission is
  granted for additional uses of the text contained in its release
  Common C++.

  The exception is that, if you link the Common C++ library with other
  files to produce an executable, this does not by itself cause the
  resulting executable to be covered by the GNU General Public
  License.  Your use of that executable is in no way restricted on
  account of linking the Common C++ library code into it.

  This exception does not however invalidate any other reasons why the
  executable file might be covered by the GNU General Public License.

  This exception applies only to the code released under the name
  Common C++.  If you copy code from other releases into a copy of
  Common C++, as the General Public License permits, the exception
  does not apply to the code that you add in this way.  To avoid
  misleading anyone as to the status of such modified files, you must
  delete this exception notice from them.

  If you write modifications of your own for Common C++, it is your
  choice whether to permit this exception to apply to your
  modifications.  If you do not wish that, delete this exception
  notice.

*/

#include <iostream>
#include <stdint.h>
#include <string.h>
#include <iomanip.h>

class Digest : protected std::streambuf, public std::ostream
{
protected:
	Digest();

	/**
	 * Reset the digest table to an initial default value.
	 */
	virtual void initDigest(void) = 0;

	/**
	 * Get the size of a digest in octets.
	 *
	 * @return number of bytes in digest.
	 */
	virtual unsigned getSize(void) = 0;

	/**
	 * Copy the binary digest buffer to user memory.
	 *
	 * @return number of bytes in digest.
	 * @param buffer to write into.
	 */
	virtual unsigned getDigest(unsigned char *buffer) = 0;

	/**
	 * Put data into the digest bypassing the stream subsystem.
	 *
	 * @param buffer to read from.
	 * @param length of data.
	 */
	virtual void putDigest(const unsigned char *buffer, unsigned length) = 0;

	/**
	 * print a digest string for export.
	 *
	 * @return string representation of digest.
	 */
         virtual std::ostream &strDigest(std::ostream &os) = 0;

         friend std::ostream &operator<<(std::ostream &os, Digest &ia)
           {return ia.strDigest(os);};

};

Digest::Digest() :
streambuf()
#ifdef	HAVE_OLD_IOSTREAM
,ostream()
#else
,ostream((streambuf *)this)
#endif
{ 
#ifdef	HAVE_OLD_IOSTREAM
	init((streambuf *)this);
#endif
}



class SHA1Digest : public Digest {
private:
  uint32_t h[5];
  uint64_t totalLength;
  unsigned char tempBuffer[64];

  enum {
    a = 0, b, c, d, e
  };

 protected:
  std::ostream &strDigest(std::ostream &os);
  void processSingleBlock(const unsigned char * buffer, uint64_t begin = 0);
  uint32_t fK(unsigned t, const uint32_t ae[]);

 public:
  SHA1Digest();

  void initDigest(void);

  inline unsigned getSize()
    { return 20; };

  unsigned getDigest(unsigned char *buffer);

  void putDigest(const unsigned char *buffer, unsigned len);

};

#define S(n,X) ( (  X  << n) | (  X  >> 32 - n) )

SHA1Digest::SHA1Digest(): Digest() {
  initDigest();
}

void SHA1Digest::initDigest(void) {
  h[0] = 0x67452301;
  h[1] = 0xefcdab89;
  h[2] = 0x98badcfe;
  h[3] = 0x10325476;
  h[4] = 0xc3d2e1f0;
  totalLength = 0;
}

uint32_t SHA1Digest::fK(unsigned t, const uint32_t ae[]) {

  if(t < 20)
    return( ( ( ae[b] & ae[c] ) | ( ~ae[b] & ae[d] )  ) + 0x5A827999);
  if(t < 40)
    return( (ae[b] ^ ae[c] ^ ae[d]) + 0x6ED9EBA1 );
  if(t < 60)
    return( ( (ae[b] & ae[c]) | (ae[b] & ae[d]) | (ae[c] & ae[d]) )+ 0x8F1BBCDC);
  return( (ae[b] ^ ae[c] ^ ae[d]) + 0xCA62C1D6);
}

#define MASK 0x0000000F

void SHA1Digest::processSingleBlock(const unsigned char * buffer, uint64_t begin) {
  uint32_t W[16];
  uint32_t temp;
  int t;
  uint32_t ae[5];

  memcpy(&W, buffer + begin, sizeof(W));
  memcpy(ae, h, sizeof(h));
  
  for(t = 0; t < 80; t++) {
    uint32_t s = t & MASK;
    if(t >= 16) {
      W[s] = S(1, (W[(s + 13) & MASK] ^  W[(s + 8) & MASK] ^  W[(s + 2) & MASK] ^  W[s]));
    }
    temp = S(5, ae[a]) + ae[e] + W[s] + fK(t, ae);

    ae[e] = ae[d];
    ae[d] = ae[c];
    ae[c] = S(30, ae[b]);
    ae[b] = ae[a];
    ae[a] = temp;

  }

  for(t = 0; t < 5; t++) {
    // h[0] += ae[a] etc...
    h[t] += ae[t];
  }
}

void SHA1Digest::putDigest(const unsigned char * buffer, unsigned len) {
  if(len == 0) {
    return;
  }

  // first check and see if this is a continuation in that there is
  // still data in tempBuffer from a previous data entry:

  int remainder;
  int pos = 0;

  if( remainder = ( totalLength % 512 ) != 0 ) {
    // this is a continuation, so we fill up tempbuff with
    // what ever is in buffer and use it first
    
    int cpyAmount = (512 - remainder) / 8;
    if(len < cpyAmount) {
      cpyAmount = len;
    }

    memcpy(tempBuffer + remainder, buffer, cpyAmount);
    totalLength += cpyAmount * 8;
    pos = cpyAmount;

    // if there is more data on the way, then we need to process
    // tempBuffer

    if( (len - pos) > 0 ) {
      processSingleBlock(tempBuffer);
    }
  }
    

  // now we just loop through the incoming stream, buffer, 64 bytes at
  // a time. Any left overs are placed into tempBuffer:
  
  while(unsigned diff = len - pos) {
    if(diff >= 64) {
      processSingleBlock(buffer, pos);
      pos += 64;
      totalLength += 512;
    } else {
      memcpy(tempBuffer, buffer + pos, diff);
      pos += diff;
      totalLength += ( diff * 8 );
    }
  }
}
	
unsigned SHA1Digest::getDigest(unsigned char * buffer) {
  unsigned char myTempBuffer[64];
  int remainder = totalLength % 512;
  int pos       = remainder / 8;
  int fillToBytes;

  memcpy((void*)myTempBuffer, tempBuffer, sizeof(tempBuffer));

  if(remainder <= 448) {
    fillToBytes = 56;
  } else {
    fillToBytes = 64;
  }

  // add the 1:

  myTempBuffer[pos++] = 0x80;
  
  do {
    bzero(myTempBuffer + pos, fillToBytes - pos);
    if(fillToBytes == 56) {
      // add the length onto the end
      memcpy((void*)(myTempBuffer + 56), (void*)&totalLength, sizeof(totalLength));
    }
    processSingleBlock(myTempBuffer);
    pos = 0;
    fillToBytes -= 8;
  } while(fillToBytes > 48);
  
  memcpy((void*)buffer, (void*)h, 20);
  return 20;
}

std::ostream & SHA1Digest::strDigest(std::ostream &os) {
  unsigned char buff[20];
  getDigest(buff);
  int tmp;

  for(int i = 0; i < 20; i++) {
    tmp = buff[i];
    os << std::setbase(16) << std::setw(2) << std::setfill('0') << tmp;
  }
  return os;
}

#ifdef TEST_SHA1

#include <stdio.h>

#define TEST_BUFFER_SIZE 1024

int main(int argc, const char * argv[]) {
  SHA1Digest digest;

  for(int i = 1 ; i < argc; i++) {
    digest.initDigest();
    FILE *fp = fopen(argv[i], "rb");
    if(fp) {
      int length;
      unsigned char buff[TEST_BUFFER_SIZE];
      while(length = fread(buff, sizeof(unsigned char), TEST_BUFFER_SIZE, fp)) {
	digest.putDigest(buff, length);
      }
      std::cout << digest << "  " << argv[i] << std::endl;
    } else {
      std::cerr << "Error reading file: " << argv[i] << std::endl;
    }
    fclose(fp);
  }
}

#endif




From lizzy@soggytrousers.net Sun Nov 17 00:08:39 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18DHfj-0006OC-00
	for bug-commoncpp@gnu.org; Sun, 17 Nov 2002 00:08:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18DHfg-0006Mt-00
	for bug-commoncpp@gnu.org; Sun, 17 Nov 2002 00:08:38 -0500
Received: from dc-mx13.cluster1.charter.net ([209.225.8.23])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18DHff-0006Jz-00
	for bug-commoncpp@gnu.org; Sun, 17 Nov 2002 00:08:35 -0500
Received: from [66.190.65.189] (HELO liliwhite.renaissance.oasis)
  by dc-mx13.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9)
  with ESMTP id 5999499 for bug-commoncpp@gnu.org; Sun, 17 Nov 2002 00:08:34 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1 (Debian))
	id 18DHfb-00056R-00
	for <bug-commoncpp@gnu.org>; Sat, 16 Nov 2002 23:08:31 -0600
To: bug-commoncpp@gnu.org
Subject: SHA1Digest Recalled
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 16 Nov 2002 23:08:31 -0600
Message-ID: <878yzsye9c.fsf@liliwhite.renaissance.oasis>
Lines: 20
X-Mailer: Gnus v5.7/Emacs 20.7
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/>

Dear CommonC++,

   After looking at the specs of SHA256, it seems wiser that the
recently submitted implementation of SHA1 *not* be added to CommonC++
because there is at least one function that is the same between the
two hash functions and it seems better for there to be, say:

   Class SHADigest : public Digest

   Class SHA1Digest : public Digest

   Class SHA256Digest : public Digest

with the common code in SHADigest.

   However, may I be added to the mailing list?

   Thank you,

   Elizabeth



From fedemp@wanadoo.es Thu Nov 21 17:27:04 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18Ezmp-00068P-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 17:27:03 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18Ezmi-0005qt-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 17:27:01 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18Ezmh-0005lL-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 17:26:56 -0500
Received: from risitas ([80.103.118.214])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gALMOB210286
	for <bug-commoncpp@gnu.org>; Thu, 21 Nov 2002 23:24:12 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18EzoS-0002Pc-00
	for <bug-commoncpp@gnu.org>; Thu, 21 Nov 2002 23:28:44 +0100
Date: Thu, 21 Nov 2002 23:28:43 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: SHA1Digest and SHA256Digest
Message-ID: <20021121222843.GA606@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <87u1idql7a.fsf@liliwhite.renaissance.oasis> <20021120101221.GA543@bulbasaur.rediris.es> <87isysvvn8.fsf@liliwhite.renaissance.oasis>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87isysvvn8.fsf@liliwhite.renaissance.oasis>
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, the two classes have been incorporated to cvs. I just did
a modification: replaced uint32_t and uint64_t with uint32 and uint64,
which are the corresponding "standard"/"portable" types in common
c++. You can have a look at config.h to see how these types are
defined.

	I noticed that you generated the diffs against the commoncpp
CVS module (/cvsroot/commoncpp/commoncpp). It currently contains the
code for the old Common C++ "1". Note that the CVS module for current
Common C++ "2" releases is commoncpp2.

	Also, I am not sure why you needed to tweak socket.h, we have
not seen any problem with that lines before. What is your system
configuration? Could you try to build the code in the current cvs or
some recent release from ftp.gnu.org/pub/gnu/commoncpp?

	Bye!

On Wed, Nov 20, 2002 at 02:22:35PM -0600, Elizabeth Barham wrote:
> Federico Montesino Pouzols <fedemp@altern.org> writes:
> 
> > 	Good. I think these classes fit perfectly with cc++.
> 
> Great!
> 
> > 	Personally, I think that adding the two exception cases is ok.
> 
> Done.
> 
> Here is the diff from anonymous CVS. Following that will be the two
> files:
> 
>    src/sha.cpp
>    demo/shadigest.cpp
> 
> Note that I did make some adjustments to some of the files in order to
> build, most notably socket.h.
> 
> Thank you, Elizabeth
> 



From fedemp@wanadoo.es Thu Nov 21 17:33:15 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18Ezso-0004wQ-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 17:33:14 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18Ezsk-0004u9-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 17:33:13 -0500
Received: from [62.37.236.142] (helo=smtp.wanadoo.es)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18Ezsk-0004tp-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 17:33:10 -0500
Received: from risitas ([80.103.118.214])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id gALMUR213069
	for <bug-commoncpp@gnu.org>; Thu, 21 Nov 2002 23:30:27 +0100
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 18EzuV-0002Pw-00
	for <bug-commoncpp@gnu.org>; Thu, 21 Nov 2002 23:34:59 +0100
Date: Thu, 21 Nov 2002 23:34:59 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: Serious SocketService/SocketPort problems
Message-ID: <20021121223459.GB606@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <200211211135.59040.cproch@freiverkehr.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <200211211135.59040.cproch@freiverkehr.de>
User-Agent: Mutt/1.4i
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.wanadoo.es id gALMUR213069
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, this is a serious problem. I also do not know how to
avoid it without moving the call to attach (or some kind of signaling
or lock/unlock to notify SocketService) to the derived classes instead
of the base SocketPort.

	Any other idea?

On Thu, Nov 21, 2002 at 11:35:59AM +0100, Prochnow, Christian wrote:
> Hi List,
>=20
> here comes a really serious problem related to SocketService and Socket=
Port:
>=20
> SocketPort() takes a SocketService argument, when SocketPort is created=
, it=20
> attaches itself to the given SocketService. Which seems to lead to=20
> synchronisation problems.=20
> I have a class (say MySocketPort) that is inherited from SocketPort (wi=
th=20
> outbound constructor). So when i create the MySocketPort object in the=20
> main-thread the SocketPort() base constructor registers itself with the=
=20
> SocketService which is then started by SocketService::attach().
>=20
> So when the SocketService-thread begins to run and immediatly tries to=20
> dispatch a virtual call to MySocketPort - it will be dispatched to the=20
> default implementation (SocketPort::connect()) cause the vtable of=20
> MySocketPort is'nt fully setup.
>=20
> This seems to be timing-related, cause under Linux this works fine - un=
der=20
> Windows XP it crashes (i think new started threads in XP are immediatly=
=20
> executed and the creator-thread gets yield).
> =20
> I have no idea how to solve this. Only solution would be that SocketPor=
t()=20
> does not attach itself when constructing ... instead MySocketPort shoul=
d=20
> attach itself to the SocketService.=20
>=20
> Thanks in advance,
> Christian
>=20
> --=20
> Christian Prochnow
> Berliner Freiverkehr (Aktien) AG - Kurf=FCrstendamm 117 - 10711 Berlin,=
 Germany
> Fon: +49-30-89606409, Fax: +49-30-89021389 - EMail: cproch@freiverkehr.=
de
>=20
>=20
>=20
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From dyfet@ostel.com Thu Nov 21 17:40:13 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18EzzZ-0008RS-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 17:40:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18EzzU-0008Qi-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 17:40:11 -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 18EzzT-0008P9-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 17:40:07 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gALN6tv03720;
	Thu, 21 Nov 2002 18:06:55 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Thu, 21 Nov 2002 18:06:55 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: SHA1Digest and SHA256Digest
In-Reply-To: <20021121222843.GA606@risitas>
Message-ID: <Pine.LNX.4.44.0211211805280.3704-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 probably could put sha in r1 as well as -HEAD...I don't see any
immediate harm that could come from it's inclusion there, and it would get
it some testing and early use.

On Thu, 21 Nov 2002, Federico Montesino Pouzols wrote:

> 
> 	Ok, the two classes have been incorporated to cvs. I just did
> a modification: replaced uint32_t and uint64_t with uint32 and uint64,
> which are the corresponding "standard"/"portable" types in common
> c++. You can have a look at config.h to see how these types are
> defined.
> 
> 	I noticed that you generated the diffs against the commoncpp
> CVS module (/cvsroot/commoncpp/commoncpp). It currently contains the
> code for the old Common C++ "1". Note that the CVS module for current
> Common C++ "2" releases is commoncpp2.
> 
> 	Also, I am not sure why you needed to tweak socket.h, we have
> not seen any problem with that lines before. What is your system
> configuration? Could you try to build the code in the current cvs or
> some recent release from ftp.gnu.org/pub/gnu/commoncpp?
> 
> 	Bye!
> 
> On Wed, Nov 20, 2002 at 02:22:35PM -0600, Elizabeth Barham wrote:
> > Federico Montesino Pouzols <fedemp@altern.org> writes:
> > 
> > > 	Good. I think these classes fit perfectly with cc++.
> > 
> > Great!
> > 
> > > 	Personally, I think that adding the two exception cases is ok.
> > 
> > Done.
> > 
> > Here is the diff from anonymous CVS. Following that will be the two
> > files:
> > 
> >    src/sha.cpp
> >    demo/shadigest.cpp
> > 
> > Note that I did make some adjustments to some of the files in order to
> > build, most notably socket.h.
> > 
> > Thank you, Elizabeth
> > 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From ariston@cs.und.edu Thu Nov 21 23:45:47 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18F5hK-0007It-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 23:45:46 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18F5hH-0007Ha-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 23:45:44 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18F5hG-00076S-00
	for bug-commoncpp@gnu.org; Thu, 21 Nov 2002 23:45:42 -0500
Received: from penguin.cs.und.nodak.edu (penguin.cs.und.nodak.edu [134.129.212.25])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gAM4jduO016438
	for <bug-commoncpp@gnu.org>; Thu, 21 Nov 2002 22:45:39 -0600
Date: Thu, 21 Nov 2002 22:41:46 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
X-X-Sender: <ariston@localhost.localdomain>
To: <bug-commoncpp@gnu.org>
Subject: tcpstream write() weirdness
Message-ID: <Pine.LNX.4.33.0211212232260.22470-100000@localhost.localdomain>
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 using tcpstream (for simplicity) in a multithreaded app, and am
protecting all read() and write() calls on it with a mutex.  I am able to
write to the tcpstream once and read the server's response, but the next
write() call simply never gets sent out to the network.  Is this a known
issue?  Many times I've banged my head off of walls trying to figure out
why something won't work for me, only to have a mailing list inform me
that I was doing something that I shouldn't, so I wonder if that's not the
case here.  Below, find a basic idea of what my class hierarchy looks
like; and thank you to any who reply.

Ari Johnson

--

class Stream : public Mutex {
private:
  tcpstream tcp;
public:
  void read(...) {
    while(!tcp.isPending(Socket::pendingInput, 1000)) {
      if(tcp.isPending(Socket::pendingError, 0))
        throw something;

      Thread::yield();
    }

    enterMutex();
    tcp.read(blah, len);
    leaveMutex();
  };

  void write(...) {
    enterMutex();
    tcp.write(blah, len);
    leaveMutex();
  };
};

class Incoming : public Thread {
private:
  Stream *stream;
public:
  void run(void) {
    while(1) {
      stream->read(somewhere);
      possibly_tell_Outgoing_to_send_something;
    }
  };
};

class Outgoing : public Thread {
private:
  Stream *stream;
public:
  void run(void) {
    while(1)
      if(feel_like_sending_something)
        stream->send(something);
  };
};

NB: Incoming and Outgoing are created in pairs, and the pair shares a
    single Stream object.




From dyfet@ostel.com Fri Nov 22 00:07:10 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18F622-00088z-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 00:07:10 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18F61z-00084g-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 00:07:09 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18F61y-0007zf-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 00:07:07 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gAM5XuC32358;
	Fri, 22 Nov 2002 00:33:56 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Fri, 22 Nov 2002 00:33:56 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Ari Johnson <ariston@cs.und.edu>
cc: bug-commoncpp@gnu.org
Subject: Re: tcpstream write() weirdness
In-Reply-To: <Pine.LNX.4.33.0211212232260.22470-100000@localhost.localdomain>
Message-ID: <Pine.LNX.4.44.0211220032590.32352-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 stream classes require implicit flushes because you are writing to the 
internal stream buffer first, and then real writes occur.  This can be 
done with << endl or by implicity calling flush().

On Thu, 21 Nov 2002, Ari Johnson wrote:

> 
> I'm using tcpstream (for simplicity) in a multithreaded app, and am
> protecting all read() and write() calls on it with a mutex.  I am able to
> write to the tcpstream once and read the server's response, but the next
> write() call simply never gets sent out to the network.  Is this a known
> issue?  Many times I've banged my head off of walls trying to figure out
> why something won't work for me, only to have a mailing list inform me
> that I was doing something that I shouldn't, so I wonder if that's not the
> case here.  Below, find a basic idea of what my class hierarchy looks
> like; and thank you to any who reply.
> 
> Ari Johnson
> 
> --
> 
> class Stream : public Mutex {
> private:
>   tcpstream tcp;
> public:
>   void read(...) {
>     while(!tcp.isPending(Socket::pendingInput, 1000)) {
>       if(tcp.isPending(Socket::pendingError, 0))
>         throw something;
> 
>       Thread::yield();
>     }
> 
>     enterMutex();
>     tcp.read(blah, len);
>     leaveMutex();
>   };
> 
>   void write(...) {
>     enterMutex();
>     tcp.write(blah, len);
>     leaveMutex();
>   };
> };
> 
> class Incoming : public Thread {
> private:
>   Stream *stream;
> public:
>   void run(void) {
>     while(1) {
>       stream->read(somewhere);
>       possibly_tell_Outgoing_to_send_something;
>     }
>   };
> };
> 
> class Outgoing : public Thread {
> private:
>   Stream *stream;
> public:
>   void run(void) {
>     while(1)
>       if(feel_like_sending_something)
>         stream->send(something);
>   };
> };
> 
> NB: Incoming and Outgoing are created in pairs, and the pair shares a
>     single Stream object.
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From ariston@cs.und.edu Fri Nov 22 01:14:09 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18F74q-0007h9-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 01:14:08 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18F74d-0007I7-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 01:14:02 -0500
Received: from betamax.aero.und.edu ([134.129.212.13])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18F74b-0007AG-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 01:13:54 -0500
Received: from penguin.cs.und.nodak.edu (penguin.cs.und.nodak.edu [134.129.212.25])
	by betamax.aero.und.edu (8.12.5/8.9.0) with ESMTP id gAM6DpuO021074;
	Fri, 22 Nov 2002 00:13:51 -0600
Date: Fri, 22 Nov 2002 00:09:58 -0600 (CST)
From: Ari Johnson <ariston@cs.und.edu>
X-X-Sender: <ariston@localhost.localdomain>
To: David Sugar <dyfet@ostel.com>
cc: <bug-commoncpp@gnu.org>
Subject: Re: tcpstream write() weirdness
In-Reply-To: <Pine.LNX.4.44.0211220032590.32352-100000@home.sys>
Message-ID: <Pine.LNX.4.33.0211220008230.24644-100000@localhost.localdomain>
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 forgot the mention that in the first message: I do a flush after the
write.  Like I said, the first thing I write (which contains a newline but
does not end with a newline) does get sent in its entirety, but the second
does not.

Ari Johnson

 --

On Fri, 22 Nov 2002, David Sugar wrote:

>
> The stream classes require implicit flushes because you are writing to the
> internal stream buffer first, and then real writes occur.  This can be
> done with << endl or by implicity calling flush().
>
> On Thu, 21 Nov 2002, Ari Johnson wrote:
>
> >
> > I'm using tcpstream (for simplicity) in a multithreaded app, and am
> > protecting all read() and write() calls on it with a mutex.  I am able to
> > write to the tcpstream once and read the server's response, but the next
> > write() call simply never gets sent out to the network.  Is this a known
> > issue?  Many times I've banged my head off of walls trying to figure out
> > why something won't work for me, only to have a mailing list inform me
> > that I was doing something that I shouldn't, so I wonder if that's not the
> > case here.  Below, find a basic idea of what my class hierarchy looks
> > like; and thank you to any who reply.
> >
> > Ari Johnson
> >
> > --
> >
> > class Stream : public Mutex {
> > private:
> >   tcpstream tcp;
> > public:
> >   void read(...) {
> >     while(!tcp.isPending(Socket::pendingInput, 1000)) {
> >       if(tcp.isPending(Socket::pendingError, 0))
> >         throw something;
> >
> >       Thread::yield();
> >     }
> >
> >     enterMutex();
> >     tcp.read(blah, len);
> >     leaveMutex();
> >   };
> >
> >   void write(...) {
> >     enterMutex();
> >     tcp.write(blah, len);
> >     leaveMutex();
> >   };
> > };
> >
> > class Incoming : public Thread {
> > private:
> >   Stream *stream;
> > public:
> >   void run(void) {
> >     while(1) {
> >       stream->read(somewhere);
> >       possibly_tell_Outgoing_to_send_something;
> >     }
> >   };
> > };
> >
> > class Outgoing : public Thread {
> > private:
> >   Stream *stream;
> > public:
> >   void run(void) {
> >     while(1)
> >       if(feel_like_sending_something)
> >         stream->send(something);
> >   };
> > };
> >
> > NB: Incoming and Outgoing are created in pairs, and the pair shares a
> >     single Stream object.
> >
> >
> >
> > _______________________________________________
> > 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 triendl.kj@aon.at Fri Nov 22 03:03:45 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18F8mv-0004u4-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 03:03:45 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18F8ms-0004qk-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 03:03:43 -0500
Received: from viefep11-int.chello.at ([213.46.255.27])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18F8mr-0004qe-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 03:03:42 -0500
Received: from dev1xp ([80.109.135.71]) by viefep11-int.chello.at
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with SMTP
          id <20021122080340.NXBD25370.viefep11-int.chello.at@dev1xp>;
          Fri, 22 Nov 2002 09:03:40 +0100
From: "Klaus Triendl" <triendl.kj@aon.at>
To: <bug-commoncpp@gnu.org>
Cc: "Ari Johnson" <ariston@cs.und.edu>
Subject: RE: tcpstream write() weirdness
Date: Fri, 22 Nov 2002 09:03:39 +0100
Message-ID: <MNENKPHMOOKIHGCMGMEBGEDECCAA.triendl.kj@aon.at>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <Pine.LNX.4.33.0211220008230.24644-100000@localhost.localdomain>
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/>

i had the same problem; i derived my own class from tcpstream with an
overloaded write() - writing worked as long as i didn't read.

try to clear() the stream before you write - this worked for me.


--
triendl klaus





-----Original Message-----
From: bug-commoncpp-admin@gnu.org [mailto:bug-commoncpp-admin@gnu.org]On
Behalf Of Ari Johnson
Sent: Friday, November 22, 2002 7:10 AM
To: David Sugar
Cc: bug-commoncpp@gnu.org
Subject: Re: tcpstream write() weirdness



I forgot the mention that in the first message: I do a flush after the
write.  Like I said, the first thing I write (which contains a newline but
does not end with a newline) does get sent in its entirety, but the second
does not.

Ari Johnson

 --

On Fri, 22 Nov 2002, David Sugar wrote:

>
> The stream classes require implicit flushes because you are writing to the
> internal stream buffer first, and then real writes occur.  This can be
> done with << endl or by implicity calling flush().
>
> On Thu, 21 Nov 2002, Ari Johnson wrote:
>
> >
> > I'm using tcpstream (for simplicity) in a multithreaded app, and am
> > protecting all read() and write() calls on it with a mutex.  I am able
to
> > write to the tcpstream once and read the server's response, but the next
> > write() call simply never gets sent out to the network.  Is this a known
> > issue?  Many times I've banged my head off of walls trying to figure out
> > why something won't work for me, only to have a mailing list inform me
> > that I was doing something that I shouldn't, so I wonder if that's not
the
> > case here.  Below, find a basic idea of what my class hierarchy looks
> > like; and thank you to any who reply.
> >
> > Ari Johnson
> >




From lizzy@soggytrousers.net Fri Nov 22 03:15:09 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18F8xw-0002jZ-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 03:15:08 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18F8xt-0002hr-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 03:15:07 -0500
Received: from [66.190.65.189] (helo=liliwhite.renaissance.oasis)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18F8xs-0002hn-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 03:15:04 -0500
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1 (Debian))
	id 18F8xm-0000R2-00; Fri, 22 Nov 2002 02:14:58 -0600
To: Federico Montesino Pouzols <fedemp@altern.org>
Cc: bug-commoncpp@gnu.org
Subject: Re: SHA1Digest and SHA256Digest
References: <87u1idql7a.fsf@liliwhite.renaissance.oasis> <20021120101221.GA543@bulbasaur.rediris.es> <87isysvvn8.fsf@liliwhite.renaissance.oasis> <20021121222843.GA606@risitas>
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 22 Nov 2002 02:14:57 -0600
In-Reply-To: Federico Montesino Pouzols's message of "Thu, 21 Nov 2002 23:28:43 +0100"
Message-ID: <8765uqrpfi.fsf@liliwhite.renaissance.oasis>
Lines: 31
X-Mailer: Gnus v5.7/Emacs 20.7
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/>

Federico Montesino Pouzols <fedemp@altern.org> writes:

> 	Ok, the two classes have been incorporated to cvs. I just did
> a modification: replaced uint32_t and uint64_t with uint32 and uint64,
> which are the corresponding "standard"/"portable" types in common
> c++. You can have a look at config.h to see how these types are
> defined.

Thank you.

> 	I noticed that you generated the diffs against the commoncpp
> CVS module (/cvsroot/commoncpp/commoncpp). It currently contains the
> code for the old Common C++ "1". Note that the CVS module for current
> Common C++ "2" releases is commoncpp2.

I didn't realize that there was a "2" release.

> 	Also, I am not sure why you needed to tweak socket.h, we have
> not seen any problem with that lines before. What is your system
> configuration? Could you try to build the code in the current cvs or
> some recent release from ftp.gnu.org/pub/gnu/commoncpp?

The latest CVS built great!

I also just uploaded a patch to Savannah that cleans digest.h up a
tad. I foolishly left some macros defined in the header file that
should have been with the source. Sorry about that.

Thank you,

Elizabeth-



From fedemp@bulbasaur.rediris.es Fri Nov 22 07:49:52 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18FDFo-0001Bu-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 07:49:52 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18FDFh-0000s7-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 07:49:51 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18FDFf-0000cm-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 07:49:44 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18FDEd-0003tR-00
	for <bug-commoncpp@gnu.org>; Fri, 22 Nov 2002 13:48:39 +0100
Date: Fri, 22 Nov 2002 13:48:39 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: SHA1Digest and SHA256Digest
Message-ID: <20021122124839.GA14955@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <20021121222843.GA606@risitas> <Pine.LNX.4.44.0211211805280.3704-100000@home.sys>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0211211805280.3704-100000@home.sys>
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 is in RELEASE1 now, including the last patch.

On Thu, Nov 21, 2002 at 06:06:55PM -0500, David Sugar wrote:
> 
> We probably could put sha in r1 as well as -HEAD...I don't see any
> immediate harm that could come from it's inclusion there, and it would get
> it some testing and early use.
> 



From fedemp@bulbasaur.rediris.es Fri Nov 22 07:59:42 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18FDPK-0003pI-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 07:59:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18FDPF-0003oI-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 07:59:41 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18FDPE-0003mz-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 07:59:37 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18FDOI-0003tt-00
	for <bug-commoncpp@gnu.org>; Fri, 22 Nov 2002 13:58:38 +0100
Date: Fri, 22 Nov 2002 13:58:38 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: bug-commoncpp@gnu.org
Subject: Re: SHA1Digest and SHA256Digest
Message-ID: <20021122125838.GB14955@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: bug-commoncpp@gnu.org
References: <87u1idql7a.fsf@liliwhite.renaissance.oasis> <20021120101221.GA543@bulbasaur.rediris.es> <87isysvvn8.fsf@liliwhite.renaissance.oasis> <20021121222843.GA606@risitas> <8765uqrpfi.fsf@liliwhite.renaissance.oasis>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8765uqrpfi.fsf@liliwhite.renaissance.oasis>
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 Fri, Nov 22, 2002 at 02:14:57AM -0600, Elizabeth Barham wrote:
> The latest CVS built great!
> 
> I also just uploaded a patch to Savannah that cleans digest.h up a
> tad. I foolishly left some macros defined in the header file that
> should have been with the source. Sorry about that.
> 

	Good, I have applied the patch and also incorporated the
SHA*Digest classes to the RELEASE1/stable branch of the CVS. Keep in
mind that the 1.0.x releases are done from the RELEASE1 branch (you
have to specify -rRELEASE1 in order to checkout it) of the commoncpp
CVS.

> Thank you,
> 
> Elizabeth-



From fedemp@bulbasaur.rediris.es Fri Nov 22 08:26:46 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18FDpW-0007lb-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 08:26:46 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18FDpO-0007Yn-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 08:26:44 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18FDpN-0007RK-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 08:26:38 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18FDoR-000455-00; Fri, 22 Nov 2002 14:25:39 +0100
Date: Fri, 22 Nov 2002 14:25:39 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: "Prochnow, Christian" <cproch@freiverkehr.de>
Cc: bug-commoncpp@gnu.org
Subject: Re: SHA1Digest and SHA256Digest
Message-ID: <20021122132539.GC14955@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: "Prochnow, Christian" <cproch@freiverkehr.de>,
	bug-commoncpp@gnu.org
References: <20021121222843.GA606@risitas> <Pine.LNX.4.44.0211211805280.3704-100000@home.sys> <20021122124839.GA14955@bulbasaur.rediris.es> <200211221417.41479.cproch@freiverkehr.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200211221417.41479.cproch@freiverkehr.de>
User-Agent: Mutt/1.4i
Sender: bug-commoncpp-admin@gnu.org
Errors-To: bug-commoncpp-admin@gnu.org
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp/>

	Hi,

On Fri, Nov 22, 2002 at 02:17:41PM +0100, Prochnow, Christian wrote:
> Hi List,
> 
> did a CVS update today and tried to compile the SHA*Digest classes.
> It compiled fine with my GCC under linux - but VC 7 .NET gives an error in 
> SHA1Digest and SHA256Digest class declarations.
> Adding the "operator=" to SHA1Digest and SHA256Digest fixed the problem for VC 
> 7 .NET.

	Does a simple declaration work? Could you provide a patch?

> There also some other problems compiling the sha.cpp file:
> - in SHAConstant .. VC.NET does not know the "LL" number suffix

	I think that using uint64 typecast instead of LL could solve
this issue. Could you test it? I do not have a VC.NET at hand.

> - Win32 does not have bzero() - why not use memset ? bzero is deprecated

	fixed in CVS.

> - sha.cpp is missing in Visual Studio project file
> 

	Also fixed.

> i think the sha.cpp stuff is not ready for release in r1 !
> 
> Regards,
> Christian
> 
> 
> Am Freitag, 22. November 2002 13:48 schrieb Federico Montesino Pouzols:
> > Ok, it is in RELEASE1 now, including the last patch.
> >
> > On Thu, Nov 21, 2002 at 06:06:55PM -0500, David Sugar wrote:
> > > We probably could put sha in r1 as well as -HEAD...I don't see any
> > > immediate harm that could come from it's inclusion there, and it would
> > > get it some testing and early use.
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > Bug-commoncpp@gnu.org
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 
> -- 
> Christian Prochnow
> Berliner Freiverkehr (Aktien) AG - Kurfürstendamm 117 - 10711 Berlin, Germany
> Fon: +49-30-89606409, Fax: +49-30-89021389 - EMail: cproch@freiverkehr.de
> 



From dyfet@ostel.com Fri Nov 22 08:41:27 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18FE3i-0003HO-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 08:41:26 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18FE3c-0003GR-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 08:41:26 -0500
Received: from dsl-65-188-113-57.telocity.com ([65.188.113.57] helo=home.sys)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18FE3b-0003G3-00
	for bug-commoncpp@gnu.org; Fri, 22 Nov 2002 08:41:19 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gAME8DI02741;
	Fri, 22 Nov 2002 09:08:13 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Fri, 22 Nov 2002 09:08:13 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: SHA1Digest and SHA256Digest
In-Reply-To: <20021122125838.GB14955@bulbasaur.rediris.es>
Message-ID: <Pine.LNX.4.44.0211220904450.2722-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/>

Generally we will move things from -HEAD to r1 if it's either a fix for a
nessisary bug, or if it's a feature we would like to see get immediate or
wider use and early testing, but that doesn't modify or effect the
stability or behavior of the library in part or as a whole.  Simply adding 
another digest class certainly doesn't put any existing code at risk, so 
it seemed a good candidate to have in the r1 branch.

On Fri, 22 Nov 2002, Federico Montesino Pouzols wrote:

> On Fri, Nov 22, 2002 at 02:14:57AM -0600, Elizabeth Barham wrote:
> > The latest CVS built great!
> > 
> > I also just uploaded a patch to Savannah that cleans digest.h up a
> > tad. I foolishly left some macros defined in the header file that
> > should have been with the source. Sorry about that.
> > 
> 
> 	Good, I have applied the patch and also incorporated the
> SHA*Digest classes to the RELEASE1/stable branch of the CVS. Keep in
> mind that the 1.0.x releases are done from the RELEASE1 branch (you
> have to specify -rRELEASE1 in order to checkout it) of the commoncpp
> CVS.
> 
> > Thank you,
> > 
> > Elizabeth-
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 




From cproch@freiverkehr.de Mon Nov 25 10:27:46 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18GL9G-0005I9-00
	for bug-commoncpp@gnu.org; Mon, 25 Nov 2002 10:27:46 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18GL9E-0005Ht-00
	for bug-commoncpp@gnu.org; Mon, 25 Nov 2002 10:27:45 -0500
Received: from h-62.96.239.30.host.de.colt.net ([62.96.239.30] helo=mail.freiverkehr.de)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18GL9E-0005Fn-00
	for bug-commoncpp@gnu.org; Mon, 25 Nov 2002 10:27:44 -0500
Received: from cproch.freiverkehr.de (CPROCH [10.100.102.211]) by mail.freiverkehr.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W923M5X1; Mon, 25 Nov 2002 16:27:41 +0100
From: "Prochnow, Christian" <cproch@freiverkehr.de>
Organization: Berliner Freiverkehr AG
To: bug-commoncpp@gnu.org
Subject: Patch for SocketPort/SocketService problem - was: Serious SocketService/SocketPort problems
Date: Mon, 25 Nov 2002 16:33:44 +0100
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="------------Boundary-00=_8W15E5NG49FNRF3URIHQ"
Message-Id: <200211251633.44294.cproch@freiverkehr.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/>

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

Hi List,

regarding the SocketPort attach issue i've developed a patch.
this patch adds the possibility to pass a SocketService NULL-ptr on Socke=
tPort=20
construction, so that the SocketPort-ctor does not attach itself.
One can then call SocketPort::attach(SocketService*) in the inherited=20
SocketPort-constructor (or later) to attach the object to a SocketService=
=2E

It seems like the initial author of SocketPort/SocketService already had =
this=20
idea, cause the SocketPort::attach() function was declared, but not=20
implemented :)

Regards,
Christian

--=20
Christian Prochnow
Berliner Freiverkehr (Aktien) AG - Kurf=FCrstendamm 117 - 10711 Berlin, G=
ermany
Fon: +49-30-89606409, Fax: +49-30-89021389 - EMail: cproch@freiverkehr.de

--------------Boundary-00=_8W15E5NG49FNRF3URIHQ
Content-Type: text/x-diff;
  charset="us-ascii";
  name="commoncpp2-port.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="commoncpp2-port.diff"

? autom4te-2.53.cache
? commoncpp2.kdevses
? doc/commoncpp2.info
? doc/commoncpp2.info-1
? doc/commoncpp2.info-2
? doc/commoncpp2.info-3
? ssl/.libs
? ssl/Makefile
? ssl/Makefile.in
? ssl/libccssl.la
? ssl/sslcontext.lo
? ssl/sslengine.lo
? ssl/sslsession.lo
? win32/CCXX2.rc
Index: src/port.cpp
===================================================================
RCS file: /cvsroot/commoncpp/commoncpp2/src/port.cpp,v
retrieving revision 1.10
diff -r1.10 port.cpp
206c206,207
< 		svc->attach(this);
---
>     if( svc )
>   		svc->attach(this);
234c235,237
< 	svc->attach(this);
---
> 
>   if(svc)
>   	svc->attach(this);
294c297,300
< 	svc->attach(this);
---
> 
>   if(svc)
>   	svc->attach(this);
> 
309a316,320
> void SocketPort::attach( SocketService* svc )
> {
>   svc->attach(this);
> }
> 
345c356,357
< 	service->update();
---
>   if( service )
>   	service->update();
351c363,364
< 	service->update();
---
>   if( service )
>   	service->update();
367c380,381
< 		service->update();
---
>     if( service )
>   		service->update();
384c398,399
< 		service->update();
---
>     if( service )
>   		service->update();

--------------Boundary-00=_8W15E5NG49FNRF3URIHQ--




From dyfet@ostel.com Mon Nov 25 15:02:26 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18GPR4-0007Ea-00
	for bug-commoncpp@gnu.org; Mon, 25 Nov 2002 15:02:26 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18GPR1-0007BS-00
	for bug-commoncpp@gnu.org; Mon, 25 Nov 2002 15:02:25 -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 18GPR1-0007BO-00
	for bug-commoncpp@gnu.org; Mon, 25 Nov 2002 15:02:23 -0500
Received: from localhost (dyfet@localhost)
	by home.sys (8.11.6/8.11.6) with ESMTP id gAPKTiN26846;
	Mon, 25 Nov 2002 15:29:44 -0500
X-Authentication-Warning: home.sys: dyfet owned process doing -bs
Date: Mon, 25 Nov 2002 15:29:44 -0500 (EST)
From: David Sugar <dyfet@ostel.com>
X-X-Sender: dyfet@home.sys
To: "Prochnow, Christian" <cproch@freiverkehr.de>
cc: bug-commoncpp@gnu.org
Subject: Re: Patch for SocketPort/SocketService problem - was: Serious
 SocketService/SocketPort problems
In-Reply-To: <200211251633.44294.cproch@freiverkehr.de>
Message-ID: <Pine.LNX.4.44.0211251527080.26831-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/>

That would be me, actually, and yes, I did...Originally, socketport and
socketservice were actually modeled on how the Bayonne channel driver
allocates threads and sessions to produce a poolable resource under a
shared service thread that is then invoked through event callback.  
SocketPort/SocketService simply represented a socket abstraction of this
device model in a different domain (sockets rather than devices).

On Mon, 25 Nov 2002, Prochnow, Christian wrote:

> Hi List,
> 
> regarding the SocketPort attach issue i've developed a patch.
> this patch adds the possibility to pass a SocketService NULL-ptr on SocketPort 
> construction, so that the SocketPort-ctor does not attach itself.
> One can then call SocketPort::attach(SocketService*) in the inherited 
> SocketPort-constructor (or later) to attach the object to a SocketService.
> 
> It seems like the initial author of SocketPort/SocketService already had this 
> idea, cause the SocketPort::attach() function was declared, but not 
> implemented :)
> 
> Regards,
> Christian
> 
> 




From fedemp@bulbasaur.rediris.es Fri Nov 29 17:14:40 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18HtPE-0007VR-00
	for bug-commoncpp@gnu.org; Fri, 29 Nov 2002 17:14:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18HtPB-0007Qv-00
	for bug-commoncpp@gnu.org; Fri, 29 Nov 2002 17:14:39 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18HtPA-0007LZ-00
	for bug-commoncpp@gnu.org; Fri, 29 Nov 2002 17:14:36 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18HtNB-00024y-00; Fri, 29 Nov 2002 23:12:33 +0100
Date: Fri, 29 Nov 2002 23:12:32 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Fred Leeflang <fredl@dutchie.org>
Cc: bayonne <bayonne-devel@lists.sourceforge.net>, bug-commoncpp@gnu.org
Subject: Re: [Bayonne-devel]commonc++
Message-ID: <20021129221231.GA7955@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Fred Leeflang <fredl@dutchie.org>,
	bayonne <bayonne-devel@lists.sourceforge.net>,
	bug-commoncpp@gnu.org
References: <1038605750.2561.32.camel@flare.dutchie.org> <1038607031.2555.38.camel@flare.dutchie.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1038607031.2555.38.camel@flare.dutchie.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/>

	What is your common c++ version, compiler, system config.,
etc? Anyway, I think that line can be safely removed. However, it is
strange that only that line makes the compiler complain, since
equivalent statements are used in the same file as well as in other
files.

On Fri, Nov 29, 2002 at 01:57:11PM -0800, Fred Leeflang wrote:
> Commenting out line 572, a result of freddy77's 'merge' fixes the
> compile problem.
> 
> On Fri, 2002-11-29 at 13:35, Fred Leeflang wrote:
> 
> > Just checked out commoncpp from CVS, ran reconfig, configure and make:
> > 
> > fredl@orion:~/commoncpp$ make
> > Making all in src
> > make[1]: Entering directory `/home/fredl/commoncpp/src'
> > /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.
> > -I../src -I/usr/include/libxml2/libxml -I/usr/include/libxml2   
> > -I../src  -g -O2 -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -c
> > inaddr.cpp
> > rm -f .libs/inaddr.lo
> > c++ -DHAVE_CONFIG_H -I. -I. -I. -I../src -I/usr/include/libxml2/libxml
> > -I/usr/include/libxml2 -I../src -g -O2 -D_GNU_SOURCE -D_REENTRANT
> > -D_THREAD_SAFE -Wp,-MD,.deps/inaddr.pp -c inaddr.cpp  -fPIC -DPIC -o
> > .libs/inaddr.lo
> > In file included from inaddr.cpp:46:
> > socket.h:572: type specifier omitted for parameter
> > socket.h:572: parse error before `)'
> > make[1]: *** [inaddr.lo] Error 1
> > make[1]: Leaving directory `/home/fredl/commoncpp/src'
> > make: *** [all-recursive] Error 1
> > 
> > 
> > -- 
> > Fred Leeflang <fredl@dutchie.org>
> 
> -- 
> Fred Leeflang <fredl@dutchie.org>
> 



From fedemp@bulbasaur.rediris.es Fri Nov 29 17:35:00 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18Htiu-0000cR-00
	for bug-commoncpp@gnu.org; Fri, 29 Nov 2002 17:35:00 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18Htiq-0000b5-00
	for bug-commoncpp@gnu.org; Fri, 29 Nov 2002 17:34:59 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18Htiq-0000ZP-00
	for bug-commoncpp@gnu.org; Fri, 29 Nov 2002 17:34:56 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18Htgr-00025l-00; Fri, 29 Nov 2002 23:32:53 +0100
Date: Fri, 29 Nov 2002 23:32:52 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Fred Leeflang <fredl@dutchie.org>
Cc: Federico Montesino Pouzols <fedemp@altern.org>,
	bayonne <bayonne-devel@lists.sourceforge.net>,
	bug-commoncpp@gnu.org
Subject: Re: [Bayonne-devel]commonc++
Message-ID: <20021129223252.GB7955@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Fred Leeflang <fredl@dutchie.org>,
	Federico Montesino Pouzols <fedemp@altern.org>,
	bayonne <bayonne-devel@lists.sourceforge.net>,
	bug-commoncpp@gnu.org
References: <1038605750.2561.32.camel@flare.dutchie.org> <1038607031.2555.38.camel@flare.dutchie.org> <20021129221231.GA7955@bulbasaur.rediris.es> <1038608437.2561.49.camel@flare.dutchie.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1038608437.2561.49.camel@flare.dutchie.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/>

	I would say you have alreay checked out cc++. Note that
currently HEAD holds the "unstable" version, which in fact is not so
unstable. 1.0.x releases come from the RELEASE1 branch (-rRELEASE1 tag
when checking out).

	The problem with ccaudio seems to be related with the
autotools you are using to build configure, I suppose you are using
the CVS version too (the configure from the "official" sources should
not give this error). Keep in mind that in Debian there are a lot of
automakex.y packages and there are also at least two autoconf
packages. The latest ones available in testing work well with these
CVS sources.

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



From fedemp@bulbasaur.rediris.es Sat Nov 30 08:11:54 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18I7PW-0001Fc-00
	for bug-commoncpp@gnu.org; Sat, 30 Nov 2002 08:11:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18I7PU-0001F1-00
	for bug-commoncpp@gnu.org; Sat, 30 Nov 2002 08:11:53 -0500
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18I7PU-0001Ei-00
	for bug-commoncpp@gnu.org; Sat, 30 Nov 2002 08:11:52 -0500
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1 (Debian))
	id 18I7NX-0002cN-00; Sat, 30 Nov 2002 14:09:51 +0100
Date: Sat, 30 Nov 2002 14:09:50 +0100
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Fred Leeflang <fredl@dutchie.org>
Cc: bayonne <bayonne-devel@lists.sourceforge.net>, bug-commoncpp@gnu.org
Subject: Re: [Bayonne-devel]commonc++
Message-ID: <20021130130949.GA10036@bulbasaur.rediris.es>
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
Mail-Followup-To: Fred Leeflang <fredl@dutchie.org>,
	bayonne <bayonne-devel@lists.sourceforge.net>,
	bug-commoncpp@gnu.org
References: <Pine.LNX.4.44.0211291840460.14944-100000@home.sys> <1038612091.2560.71.camel@flare.dutchie.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1038612091.2560.71.camel@flare.dutchie.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/>

	The man pages are generated doing 'doxygen Doxyman' under the
doc directory.

On Fri, Nov 29, 2002 at 03:21:32PM -0800, Fred Leeflang wrote:
> ah. Well I guess removing the obsolete autoconf2.13 deb fixed that
> problem somehow
> since ccaudio now built without a problem, well except the Audio.3cc
> manual page.
> Could it be that the manual pages are missing in CVS?
> 



From ljohri@sbcglobal.net Thu Nov 28 14:51:31 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18HUh8-0006Ec-00
	for bug-commoncpp@gnu.org; Thu, 28 Nov 2002 14:51:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18HUh6-0006DZ-00
	for bug-commoncpp@gnu.org; Thu, 28 Nov 2002 14:51:29 -0500
Received: from pimout2-ext.prodigy.net ([207.115.63.101])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18HUh5-0006DT-00
	for bug-commoncpp@gnu.org; Thu, 28 Nov 2002 14:51:27 -0500
Received: from ljohriw2k (h-64-105-39-220.SNVACAID.covad.net [64.105.39.220])
	by pimout2-ext.prodigy.net (8.12.3 da nor stuldap/8.12.3) with SMTP id gASJpNrr194446
	for <bug-commoncpp@gnu.org>; Thu, 28 Nov 2002 14:51:26 -0500
Reply-To: <ljohri@sbcglobal.net>
From: "Lokesh Johri" <ljohri@sbcglobal.net>
To: <bug-commoncpp@gnu.org>
Subject: What is the licensing term for Common C++
Date: Thu, 28 Nov 2002 11:44:43 -0800
Message-ID: <KMEGIIBLMCKDDHMEHHABKEKBDAAA.ljohri@sbcglobal.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00F8_01C296D3.8AEBA4C0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.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/>

This is a multi-part message in MIME format.

------=_NextPart_000_00F8_01C296D3.8AEBA4C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hello,
Could you please tell me what is the licensing term for Common C++- is it
GPL or LGPL.
Source forge labels it as LGPL , Common C++ home page labels it as GPL. The
copyright notice with the package is GPL while the readme mentions it as
LGPL.

Could you please clarify.
Thanks,
Lokesh
________________________________________________________

Lokesh Johri

Software Engineering, Probe Systems, NP Test Inc.

150, Baytech Drive                 Work: (408) 586 6482

San Jose CA 95132                Mobile: (408) 887-7338

                                                  Fax: (408) 586-4662

                                                  ljohri@nptest.com





------=_NextPart_000_00F8_01C296D3.8AEBA4C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D325142519-28112002>Hello,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D325142519-28112002>Could =
you please=20
tell me what is the licensing term for Common C++- is it GPL or=20
LGPL.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D325142519-28112002>Source =
forge labels=20
it as LGPL , Common C++ home page labels it as GPL. The copyright notice =
with=20
the package is GPL while the readme mentions it as =
LGPL.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D325142519-28112002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D325142519-28112002>Could =
you please=20
clarify.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D325142519-28112002>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D325142519-28112002>Lokesh</SPAN></FONT></DIV>
<DIV><FONT face=3DArial>
<P><FONT face=3D"Times New Roman"=20
size=3D2>________________________________________________________</FONT><=
/P>
<P><FONT face=3D"Times New Roman" size=3D2>Lokesh Johri</FONT></P>
<P><FONT face=3D"Times New Roman" size=3D2>Software Engineering, Probe =
Systems, NP=20
Test Inc.</FONT></P>
<P><FONT face=3D"Times New Roman" size=3D2>150, Baytech=20
Drive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Work: (408) 586 6482</FONT></P>
<P><FONT face=3D"Times New Roman" size=3D2>San Jose CA=20
95132&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;Mobile:=20
(408) 887-7338</FONT></P>
<P><FONT face=3D"Times New Roman"=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
Fax: (408) 586-4662</FONT></P>
<P><FONT face=3D"Times New Roman"=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
</FONT><A href=3D"mailto:ljohri@nptest.com"><FONT face=3D"Times New =
Roman"=20
size=3D2>ljohri@nptest.com</FONT></A></P>
<P><FONT size=3D2></FONT>&nbsp;</P></FONT></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_00F8_01C296D3.8AEBA4C0--




From fredl@dutchie.org Fri Nov 29 17:21:45 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 18HtW5-0003hf-00
	for bug-commoncpp@gnu.org; Fri, 29 Nov 2002 17:21:45 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 18HtW2-0003fi-00
	for bug-commoncpp@gnu.org; Fri, 29 Nov 2002 17:21:44 -0500
Received: from adsl-64-162-167-150.dsl.lsan03.pacbell.net ([64.162.167.150] helo=orion.dutchie.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 18HtW2-0003eC-00
	for bug-commoncpp@gnu.org; Fri, 29 Nov 2002 17:21:42 -0500
Received: from flare.dutchie.org ([192.168.1.2])
	by orion.dutchie.org with esmtp (Exim 3.36 #1 (Debian))
	id 18HtUz-0001mt-00; Fri, 29 Nov 2002 14:20:37 -0800
Subject: Re: [Bayonne-devel]commonc++
From: Fred Leeflang <fredl@dutchie.org>
To: Federico Montesino Pouzols <fedemp@altern.org>
Cc: bayonne <bayonne-devel@lists.sourceforge.net>, bug-commoncpp@gnu.org
In-Reply-To: <20021129221231.GA7955@bulbasaur.rediris.es>
References: <1038605750.2561.32.camel@flare.dutchie.org>
	 <1038607031.2555.38.camel@flare.dutchie.org>
	 <20021129221231.GA7955@bulbasaur.rediris.es>
Content-Type: multipart/alternative; boundary="=-ziC5LEg0NR2OPvumCaz4"
Organization: 
Message-Id: <1038608437.2561.49.camel@flare.dutchie.org>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.0 
Date: 29 Nov 2002 14:20:37 -0800
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/>

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

I just checked out commoncpp2 from CVS. Should I have 
CVSROOT=fleeflang@subversions.gnu.org:/cvsroot/commoncpp
and then cvs co commoncpp2?

commoncpp2 compiles without a problem if I do it the above way,
yet ccaudio still complaints: 
./configure: line 5727: syntax error near unexpected token `$REQUIRES'
./configure: line 5727: `OST_CCXX2_VERSION($REQUIRES)'

I have Debian unstable, gcc version 2.95.4 20011002 (Debian prerelease)
kernel 2.4.19

I noticed a  /usr/local/share/aclocal/ost_check.m4 gets installed

I have the ccgnu2-config script


On Fri, 2002-11-29 at 14:12, Federico Montesino Pouzols wrote:

> 	What is your common c++ version, compiler, system config.,
> etc? Anyway, I think that line can be safely removed. However, it is
> strange that only that line makes the compiler complain, since
> equivalent statements are used in the same file as well as in other
> files.
> 
> On Fri, Nov 29, 2002 at 01:57:11PM -0800, Fred Leeflang wrote:
> > Commenting out line 572, a result of freddy77's 'merge' fixes the
> > compile problem.
> > 
> > On Fri, 2002-11-29 at 13:35, Fred Leeflang wrote:
> > 
> > > Just checked out commoncpp from CVS, ran reconfig, configure and make:
> > > 
> > > fredl@orion:~/commoncpp$ make
> > > Making all in src
> > > make[1]: Entering directory `/home/fredl/commoncpp/src'
> > > /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.
> > > -I../src -I/usr/include/libxml2/libxml -I/usr/include/libxml2   
> > > -I../src  -g -O2 -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -c
> > > inaddr.cpp
> > > rm -f .libs/inaddr.lo
> > > c++ -DHAVE_CONFIG_H -I. -I. -I. -I../src -I/usr/include/libxml2/libxml
> > > -I/usr/include/libxml2 -I../src -g -O2 -D_GNU_SOURCE -D_REENTRANT
> > > -D_THREAD_SAFE -Wp,-MD,.deps/inaddr.pp -c inaddr.cpp  -fPIC -DPIC -o
> > > .libs/inaddr.lo
> > > In file included from inaddr.cpp:46:
> > > socket.h:572: type specifier omitted for parameter
> > > socket.h:572: parse error before `)'
> > > make[1]: *** [inaddr.lo] Error 1
> > > make[1]: Leaving directory `/home/fredl/commoncpp/src'
> > > make: *** [all-recursive] Error 1
> > > 
> > > 
> > > -- 
> > > Fred Leeflang <fredl@dutchie.org>
> > 
> > -- 
> > Fred Leeflang <fredl@dutchie.org>
> > 

-- 
Fred Leeflang <fredl@dutchie.org>

--=-ziC5LEg0NR2OPvumCaz4
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/1.1.6">
</HEAD>
<BODY>
I just checked out commoncpp2 from CVS. Should I have <BR>
CVSROOT=<A HREF="mailto:fleeflang@subversions.gnu.org">fleeflang@subversions.gnu.org</A>:/cvsroot/commoncpp<BR>
and then cvs co commoncpp2?<BR>
<BR>
commoncpp2 compiles without a problem if I do it the above way,<BR>
yet ccaudio still complaints: <BR>
./configure: line 5727: syntax error near unexpected token `$REQUIRES'<BR>
./configure: line 5727: `OST_CCXX2_VERSION($REQUIRES)'<BR>
<BR>
I have Debian unstable, gcc version 2.95.4 20011002 (Debian prerelease)<BR>
kernel 2.4.19<BR>
<BR>
I noticed a&nbsp; /usr/local/share/aclocal/ost_check.m4 gets installed<BR>
<BR>
I have the ccgnu2-config script<BR>
<BR>
<BR>
On Fri, 2002-11-29 at 14:12, Federico Montesino Pouzols wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE><FONT COLOR="#737373" SIZE="3"><I>	What is your common c++ version, compiler, system config.,
etc? Anyway, I think that line can be safely removed. However, it is
strange that only that line makes the compiler complain, since
equivalent statements are used in the same file as well as in other
files.

On Fri, Nov 29, 2002 at 01:57:11PM -0800, Fred Leeflang wrote:
&gt; Commenting out line 572, a result of freddy77's 'merge' fixes the
&gt; compile problem.
&gt; 
&gt; On Fri, 2002-11-29 at 13:35, Fred Leeflang wrote:
&gt; 
&gt; &gt; Just checked out commoncpp from CVS, ran reconfig, configure and make:
&gt; &gt; 
&gt; &gt; fredl@orion:~/commoncpp$ make
&gt; &gt; Making all in src
&gt; &gt; make[1]: Entering directory `/home/fredl/commoncpp/src'
&gt; &gt; /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.
&gt; &gt; -I../src -I/usr/include/libxml2/libxml -I/usr/include/libxml2   
&gt; &gt; -I../src  -g -O2 -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -c
&gt; &gt; inaddr.cpp
&gt; &gt; rm -f .libs/inaddr.lo
&gt; &gt; c++ -DHAVE_CONFIG_H -I. -I. -I. -I../src -I/usr/include/libxml2/libxml
&gt; &gt; -I/usr/include/libxml2 -I../src -g -O2 -D_GNU_SOURCE -D_REENTRANT
&gt; &gt; -D_THREAD_SAFE -Wp,-MD,.deps/inaddr.pp -c inaddr.cpp  -fPIC -DPIC -o
&gt; &gt; .libs/inaddr.lo
&gt; &gt; In file included from inaddr.cpp:46:
&gt; &gt; socket.h:572: type specifier omitted for parameter
&gt; &gt; socket.h:572: parse error before `)'
&gt; &gt; make[1]: *** [inaddr.lo] Error 1
&gt; &gt; make[1]: Leaving directory `/home/fredl/commoncpp/src'
&gt; &gt; make: *** [all-recursive] Error 1
&gt; &gt; 
&gt; &gt; 
&gt; &gt; -- 
&gt; &gt; Fred Leeflang &lt;fredl@dutchie.org&gt;
&gt; 
&gt; -- 
&gt; Fred Leeflang &lt;fredl@dutchie.org&gt;
&gt; </I></FONT></PRE>
</BLOCKQUOTE>
<PRE><TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
Fred Leeflang &lt;<A HREF="mailto:fredl@dutchie.org">fredl@dutchie.org</A>&gt;
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-ziC5LEg0NR2OPvumCaz4--




