From MAILER-DAEMON Mon Jun 02 08:33:27 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19MoUy-0005jI-P4
	for mharc-bug-commoncpp@gnu.org; Mon, 02 Jun 2003 08:33:12 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19MiMa-00054z-6s
	for bug-commoncpp@gnu.org; Mon, 02 Jun 2003 02:00:08 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19MiL1-0004bv-87
	for bug-commoncpp@gnu.org; Mon, 02 Jun 2003 01:58:35 -0400
Received: from torme.siteprotect.com ([64.26.0.66])
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19MiGe-0003dK-Rj
	for bug-commoncpp@gnu.org; Mon, 02 Jun 2003 01:54:00 -0400
Received: from D2WPHV11 (ool-18bbfa84.dyn.optonline.net [24.187.250.132])
	by torme.siteprotect.com (8.11.6/8.11.6) with SMTP id h525rww15647
	for <bug-commoncpp@gnu.org>; Mon, 2 Jun 2003 00:53:58 -0500
Message-ID: <000201c328cb$55d32940$6400a8c0@D2WPHV11>
From: "Joe Pendergast" <Joe@opencagesoftware.com>
To: <bug-commoncpp@gnu.org>
Date: Mon, 2 Jun 2003 01:08:16 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0005_01C328A3.72C06EA0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailman-Approved-At: Mon, 02 Jun 2003 08:33:10 -0400
Subject: comment on the adoption (or lack thereof) of these common frameworks.
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 02 Jun 2003 06:01:53 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01C328A3.72C06EA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This just a philosophical comment that I have on the choices one =
frquently encounters in supporting portability. My comment speciifically =
is in reference to the Semaphore class but it is precisely a comment in =
the class documentation that caused me to write.

In particular in supporting and driving towards portability the drive =
towards absolute functional compatibility/portability drives the =
implementations towards least common denominator implementations.=20
An example of this is the lack of timeout functionality in:

      void Semaphore::wait  (  void     )  =20
         Wait is used to keep a thread held until the semaphore counter =
is greater than 0.=20

      If the current thread is held, then another thread must increment =
the semaphore. Once the thread is accepted, the semaphore is =
automatically decremented, and the thread continues execution.=20

      The pthread semaphore object does not support a timed "wait", and =
hence to maintain consistancy, neither the posix nor win32 source trees =
support "timed" semaphore objects.=20




    =20

My objection to this sort of least common denominator guiding philosophy =
is that many potential users will NOT adopt the frame work because of =
the loss of functionality - thus in some sense a least common =
denominator philosophy is contradictory to the goal popular adoption of =
a common framework. (We technicians sometimes tend to ignore such =
realities in our efforts.)=20

Wouldn't it be better provide the functionality in the interface and

1) throw an unsupported operation exception=20
or
2)quietly discard the timeout functionality in those implementations =
that do not support it (This I will grant to be problematic as Servers =
that use the timeout functionality as a method of breaking their "wait =
for work" primitive (implemented with a timed semaphore P operation) in =
order to poll a shutdown request variable or the like would not work. =
But they would not be portable in any case.........

In any case this is meant more to discuss the "least common denominator =
philosophy" rather than this specific example.=20

I just wanted to raise this philosophical point and find out where the =
developers stood on this issue. (As obviously in the limiitng case of an =
OS or implementing API set not supporting semaphores at all probably =
would have been grounds for ignoring such an underlying implementation =
environment I wondered where the line was drawn.......

Best wishes in your efforts though.
------=_NextPart_000_0005_01C328A3.72C06EA0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>This just a philosophical comment that =
I have on=20
the choices one frquently encounters in supporting portability. My =
comment=20
speciifically is in reference to the Semaphore class but it is precisely =
a=20
comment in the class documentation that caused me to write.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>In particular in supporting and driving =
towards=20
portability the drive towards absolute functional =
compatibility/portability=20
drives the implementations towards least common denominator =
implementations.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>An example of this is the lack of =
timeout=20
functionality in:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>
<TABLE cellSpacing=3D0 cellPadding=3D0 border=3D0>
  <TBODY>
  <TR>
    <TD class=3Dmd vAlign=3Dtop noWrap><FONT face=3DArial>void =
Semaphore::wait=20
      </FONT></TD>
    <TD class=3Dmd vAlign=3Dtop><FONT face=3DArial>(&nbsp;</FONT></TD>
    <TD class=3Dmd vAlign=3Dtop noWrap><FONT =
face=3DArial>void&nbsp;</FONT></TD>
    <TD class=3Dmdname1 vAlign=3Dtop noWrap><FONT face=3DArial>&nbsp; =
</FONT></TD>
    <TD class=3Dmd vAlign=3Dtop><FONT face=3DArial>)&nbsp;</FONT></TD>
    <TD class=3Dmd noWrap><FONT =
face=3DArial></FONT></TD></TR></TBODY></TABLE>
<TABLE cellSpacing=3D5 cellPadding=3D0 border=3D0>
  <TBODY>
  <TR>
    <TD><FONT face=3DArial>&nbsp; </FONT></TD>
    <TD>
      <P><FONT face=3DArial>Wait is used to keep a thread held until the =
semaphore=20
      counter is greater than 0. </FONT>
      <P><FONT face=3DArial>If the current thread is held, then another =
thread=20
      must increment the semaphore. Once the thread is accepted, the =
semaphore=20
      is automatically decremented, and the thread continues execution. =
</FONT>
      <P><FONT face=3DArial><FONT color=3D#800000>The pthread semaphore =
object does=20
      not support a timed "wait", and hence to maintain consistancy, =
neither the=20
      posix nor win32 source trees support "timed" semaphore =
objects.</FONT>=20
      </FONT></P>
      <P><FONT face=3DArial></FONT>&nbsp;</P>
      <P><FONT face=3DArial=20
size=3D2></FONT>&nbsp;</P></TD></TR></TBODY></TABLE></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>My objection to this sort of least =
common=20
denominator guiding philosophy is that many potential users will NOT =
adopt the=20
frame work because of the loss of functionality&nbsp;- thus&nbsp;in some =
sense a=20
least common denominator philosophy is&nbsp;contradictory to the goal =
popular=20
adoption of a common framework.&nbsp;(We technicians sometimes tend to =
ignore=20
such realities in our efforts.) </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Wouldn't it be better provide the =
functionality in=20
the interface and</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>1) throw an unsupported operation =
exception=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>or</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2)quietly discard the timeout =
functionality in=20
those implementations that do not support it (This I will grant to be=20
problematic as Servers that use the </FONT><FONT face=3DArial =
size=3D2>timeout=20
functionality as a method of&nbsp;breaking their "wait for work" =
primitive=20
(implemented with a timed semaphore P operation) in order to poll a =
shutdown=20
request variable&nbsp;or the like would not work. But they would not be =
portable=20
in any case.........</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>In any case this is meant more to =
discuss the=20
"least common denominator philosophy" rather than this specific example. =

</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I&nbsp;just wanted to raise this =
philosophical=20
point and find out where the developers stood on this issue. (As =
obviously in=20
the limiitng case of an OS or implementing API set not supporting =
semaphores at=20
all probably would have been&nbsp;grounds for ignoring such =
an&nbsp;underlying=20
implementation environment I wondered where the line was=20
drawn.......</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Best wishes in your efforts=20
though.</FONT></DIV></BODY></HTML>

------=_NextPart_000_0005_01C328A3.72C06EA0--





From MAILER-DAEMON Wed Jun 04 10:11:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19NYxh-00041a-Pl
	for mharc-bug-commoncpp@gnu.org; Wed, 04 Jun 2003 10:09:57 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19NYww-0003aa-1U
	for bug-commoncpp@gnu.org; Wed, 04 Jun 2003 10:09:10 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19NYsQ-00023v-Ny
	for bug-commoncpp@gnu.org; Wed, 04 Jun 2003 10:04:33 -0400
Received: from [194.67.67.195] (helo=trinity)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19NYrL-0001MI-Ks
	for bug-commoncpp@gnu.org; Wed, 04 Jun 2003 10:03:24 -0400
Received: from [194.67.66.158] (helo=dezcom.mephi.ru)
	by trinity with asmtp (Exim 3.35 #1 (Debian))
	id 19NYsM-0004s5-00
	for <bug-commoncpp@gnu.org>; Wed, 04 Jun 2003 18:04:26 +0400
Message-ID: <3EDDFB85.8060907@dezcom.mephi.ru>
Date: Wed, 04 Jun 2003 18:00:37 +0400
From: andy Tatarinov <at@dezcom.mephi.ru>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4b) Gecko/20030603 Thunderbird/0.1a
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner: Found to be clean
Subject: SocketPort::disconnect
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 04 Jun 2003 14:09:56 -0000

Hello All!

I`m beginning to use CommonC++ ad tried to test examples.
In tcpservice.cpp example ChatterSession::disconnect is never called 
though the client disconnects correctly.

I use MS Visual C++ 6.0.




From MAILER-DAEMON Tue Jun 10 12:35:23 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19Pm41-00088C-62
	for mharc-bug-commoncpp@gnu.org; Tue, 10 Jun 2003 12:33:37 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19PlJF-0004vJ-SX
	for bug-commoncpp@gnu.org; Tue, 10 Jun 2003 11:45:17 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19PlJD-0004uy-Bm
	for bug-commoncpp@gnu.org; Tue, 10 Jun 2003 11:45:16 -0400
Received: from [216.5.183.2] (helo=mail1.interfacecontrol.com)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19PlHU-0004A0-Fw
	for bug-commoncpp@gnu.org; Tue, 10 Jun 2003 11:43:28 -0400
Received: from starfish (starfish.interfacecontrol.com [216.5.183.34])
	by mail1.interfacecontrol.com (8.9.1a/8.9.1) with ESMTP id LAA16542
	for <bug-commoncpp@gnu.org>; Tue, 10 Jun 2003 11:42:09 -0400 (EDT)
From: "Brian Gregory" <briang@interfacecontrol.com>
To: <bug-commoncpp@gnu.org>
Date: Tue, 10 Jun 2003 11:42:55 -0400
Message-ID: <000401c32f66$fde2e160$22b705d8@starfish>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 10 Jun 2003 12:33:29 -0400
Subject: RedHat 7.3 - gcc 2.95.3 - persist.h:304: 'int64' was not declared
 in this scope
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 10 Jun 2003 15:45:18 -0000

I=92ve just downloaded commoncpp2-1.0.12.tar.gz and I=92m having =
difficulty
building.

Red Hat Linux 7.3
gcc 2.95.3

configure =96without-xml =96prefix=3D/home/briang/commoncpp2

After running make it builds a number of files successfully and then =
reaches
the following:

c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY
-I/usr/local/include -D_GNU_SOURCE -I../include -Wp,-MD,.deps/persist.pp =
-c
persist.cpp   -fPIC -DPIC -o .libs/persist.lo
In file included from persist.cpp:43:
../include/cc++/persist.h:304: `int64' was not declared in this scope
../include/cc++/persist.h:304: parse error before `)'
../include/cc++/persist.h:305: `uint64' was not declared in this scope
../include/cc++/persist.h:305: parse error before `)'
../include/cc++/persist.h:305: `ost::Engine::write(...)' has already =
been
declared in `ost::Engine'
../include/cc++/persist.h:336: `int64' was not declared in this scope
../include/cc++/persist.h:336: `i' was not declared in this scope
../include/cc++/persist.h:336: variable or field `read' declared void
../include/cc++/persist.h:336: syntax error before `{'
../include/cc++/persist.h:337: semicolon missing after declaration of
`ost::Engine'
../include/cc++/persist.h: In method `void ost::Engine::write(...)':
../include/cc++/persist.h:304: `i' undeclared (first use this function)
../include/cc++/persist.h:304: (Each undeclared identifier is reported =
only
once
../include/cc++/persist.h:304: for each function it appears in.)
../include/cc++/persist.h: In method `void ost::Engine::read(int8 &)':
../include/cc++/persist.h:330: implicit declaration of function `int
ost::readBinary(...)'
../include/cc++/persist.h: At top level:
../include/cc++/persist.h:337: `uint64' was not declared in this scope
../include/cc++/persist.h:337: parse error before `)'
../include/cc++/persist.h:338: parse error before `)'
../include/cc++/persist.h:339: parse error before `)'
../include/cc++/persist.h:342: parse error before `)'
../include/cc++/persist.h:345: parse error before `)'
../include/cc++/persist.h:363: `myUnderlyingStream' declared as =
reference
but not initialized
../include/cc++/persist.h:368: syntax error before `;'
../include/cc++/persist.h:373: `BaseObject' was not declared in this =
scope
../include/cc++/persist.h:373: parse error before `>'
../include/cc++/persist.h:374: `BaseObject' was not declared in this =
scope
../include/cc++/persist.h:374: parse error before `const'
../include/cc++/persist.h:378: syntax error before `;'
../include/cc++/persist.h:379: syntax error before `;'
../include/cc++/persist.h:390: parse error before `}'
../include/cc++/persist.h:394: syntax error before `&'
../include/cc++/persist.h:396: syntax error before `&'
../include/cc++/persist.h:398: syntax error before `&'
../include/cc++/persist.h:400: syntax error before `&'
../include/cc++/persist.h:403: syntax error before `&'
../include/cc++/persist.h:405: syntax error before `&'
../include/cc++/persist.h:408: syntax error before `&'
../include/cc++/persist.h:410: syntax error before `&'
../include/cc++/persist.h:413: syntax error before `&'
../include/cc++/persist.h:415: syntax error before `&'
../include/cc++/persist.h:418: syntax error before `&'
../include/cc++/persist.h:420: syntax error before `&'
../include/cc++/persist.h:423: syntax error before `&'
../include/cc++/persist.h:425: syntax error before `&'
../include/cc++/persist.h:428: syntax error before `&'
../include/cc++/persist.h:430: syntax error before `&'
../include/cc++/persist.h:433: syntax error before `&'
../include/cc++/persist.h:435: syntax error before `&'
../include/cc++/persist.h:438: syntax error before `&'
../include/cc++/persist.h:440: syntax error before `&'
../include/cc++/persist.h:443: syntax error before `&'
../include/cc++/persist.h:445: syntax error before `&'
../include/cc++/persist.h:448: syntax error before `&'
../include/cc++/persist.h:450: syntax error before `&'
../include/cc++/persist.h:453: syntax error before `&'
../include/cc++/persist.h:455: syntax error before `&'
../include/cc++/persist.h:458: syntax error before `&'
../include/cc++/persist.h:460: syntax error before `&'
../include/cc++/persist.h:472: syntax error before `&'
../include/cc++/persist.h:472: `Engine' was not declared in this scope
../include/cc++/persist.h:472: `ar' was not declared in this scope
../include/cc++/persist.h:472: `T' was not declared in this scope
../include/cc++/persist.h:472: template argument 1 is invalid
../include/cc++/persist.h:472: template argument 1 is invalid
../include/cc++/persist.h:472: template argument 2 is invalid
../include/cc++/persist.h:472: using `typename' outside of template
../include/cc++/persist.h:472: parse error before `const'
../include/cc++/persist.h:472: parse error before `::'
../include/cc++/persist.h:475: `ob' was not declared in this scope
../include/cc++/persist.h:475: parse error before `;'
../include/cc++/persist.h:486: syntax error before `&'
../include/cc++/persist.h:486: `Engine' was not declared in this scope
../include/cc++/persist.h:486: `ar' was not declared in this scope
../include/cc++/persist.h:486: `T' was not declared in this scope
../include/cc++/persist.h:486: template argument 1 is invalid
../include/cc++/persist.h:486: template argument 1 is invalid
../include/cc++/persist.h:486: template argument 2 is invalid
../include/cc++/persist.h:486: using `typename' outside of template
../include/cc++/persist.h:486: parse error before `&'
../include/cc++/persist.h:486: parse error before `::'
../include/cc++/persist.h:490: syntax error before `>'
../include/cc++/persist.h:491: syntax error before `.'
../include/cc++/persist.h:492: parse error before `;'
../include/cc++/persist.h:503: syntax error before `&'
../include/cc++/persist.h:503: `Engine' was not declared in this scope
../include/cc++/persist.h:503: `ar' was not declared in this scope
../include/cc++/persist.h:503: `T' was not declared in this scope
../include/cc++/persist.h:503: template argument 1 is invalid
../include/cc++/persist.h:503: template argument 1 is invalid
../include/cc++/persist.h:503: template argument 2 is invalid
../include/cc++/persist.h:503: using `typename' outside of template
../include/cc++/persist.h:503: parse error before `const'
../include/cc++/persist.h:503: parse error before `::'
../include/cc++/persist.h:506: syntax error before `!=3D'
../include/cc++/persist.h:517: syntax error before `&'
../include/cc++/persist.h:517: `Engine' was not declared in this scope
../include/cc++/persist.h:517: `ar' was not declared in this scope
../include/cc++/persist.h:517: `T' was not declared in this scope
../include/cc++/persist.h:517: template argument 1 is invalid
../include/cc++/persist.h:517: template argument 1 is invalid
../include/cc++/persist.h:517: template argument 2 is invalid
../include/cc++/persist.h:517: using `typename' outside of template
../include/cc++/persist.h:517: parse error before `&'
../include/cc++/persist.h:517: parse error before `::'
../include/cc++/persist.h:520: redefinition of `uint32 siz'
../include/cc++/persist.h:489: `uint32 siz' previously declared here
../include/cc++/persist.h:521: syntax error before `>'
../include/cc++/persist.h:523: parse error before `;'
../include/cc++/persist.h:526: syntax error before `>'
../include/cc++/persist.h:527: syntax error before `.'
../include/cc++/persist.h:539: syntax error before `&'
../include/cc++/persist.h:539: `Engine' was not declared in this scope
../include/cc++/persist.h:539: `ar' was not declared in this scope
../include/cc++/persist.h:539: `Key' was not declared in this scope
../include/cc++/persist.h:539: `Value' was not declared in this scope
../include/cc++/persist.h:539: template argument 1 is invalid
../include/cc++/persist.h:539: template argument 2 is invalid
../include/cc++/persist.h:539: template argument 1 is invalid
../include/cc++/persist.h:539: template argument 3 is invalid
../include/cc++/persist.h:539: template argument 1 is invalid
../include/cc++/persist.h:539: template argument 4 is invalid
../include/cc++/persist.h:539: using `typename' outside of template
../include/cc++/persist.h:539: parse error before `const'
../include/cc++/persist.h:539: parse error before `::'
../include/cc++/persist.h:542: syntax error before `!=3D'
../include/cc++/persist.h:553: syntax error before `&'
../include/cc++/persist.h:553: `Engine' was not declared in this scope
../include/cc++/persist.h:553: `ar' was not declared in this scope
../include/cc++/persist.h:553: `Key' was not declared in this scope
../include/cc++/persist.h:553: `Value' was not declared in this scope
../include/cc++/persist.h:553: template argument 1 is invalid
../include/cc++/persist.h:553: template argument 2 is invalid
../include/cc++/persist.h:553: template argument 1 is invalid
../include/cc++/persist.h:553: template argument 3 is invalid
../include/cc++/persist.h:553: template argument 1 is invalid
../include/cc++/persist.h:553: template argument 4 is invalid
../include/cc++/persist.h:553: using `typename' outside of template
../include/cc++/persist.h:553: parse error before `&'
../include/cc++/persist.h:553: parse error before `::'
../include/cc++/persist.h:556: redefinition of `uint32 siz'
../include/cc++/persist.h:520: `uint32 siz' previously declared here
../include/cc++/persist.h:557: syntax error before `>'
../include/cc++/persist.h:558: parse error before `;'
../include/cc++/persist.h:560: syntax error before `>'
../include/cc++/persist.h:561: syntax error before `>'
make[1]: *** [persist.lo] Error 1
make[1]: Leaving directory `/home/briang/commoncpp2-1.0.12/src'
make: *** [all-recursive] Error 1


It seems to have a problem with int64 and uint64 in both persist.h and
digest.h. I can force it to build properly if I insert the following
typedefs in both files:

typedef int64_t int64;
typedef uint64_t uint64;




Brian Gregory
Software Engineer
Interface & Control Systems Inc.=20
8945 Guilford Road Suite120 Columbia, MD 21046
Voice: 410.290.7600=A0=A0=A0 Fax: 410.290.7737
Advance the "state of the art" of Command and Control Systems=20
http://www.interfacecontrol.com=20






From MAILER-DAEMON Mon Jun 16 11:52:39 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19RwHX-0002xs-AO
	for mharc-bug-commoncpp@gnu.org; Mon, 16 Jun 2003 11:52:31 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19RwH2-0002Hn-Sq
	for bug-commoncpp@gnu.org; Mon, 16 Jun 2003 11:52:00 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19RwG6-00014v-AG
	for bug-commoncpp@gnu.org; Mon, 16 Jun 2003 11:51:02 -0400
Received: from smtp2.home.se ([213.214.194.102])
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19RwEs-0000Nd-5G
	for bug-commoncpp@gnu.org; Mon, 16 Jun 2003 11:49:46 -0400
Received: from bart opera@home.se [217.211.246.37]Novell NetWare;
	Mon, 16 Jun 2003 16:08:39 +0200
From: =?iso-8859-1?Q?Gustaf_R=E4ntil=E4?= <opera@home.se>
To: <bug-commoncpp@gnu.org>
Date: Mon, 16 Jun 2003 16:09:16 +0200
Message-ID: <000001c33410$e339c140$1401300a@bart>
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, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: Use of Common C++
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 16 Jun 2003 15:52:29 -0000

Hello all,

I have ran into a few problems. When I first looked att cc++ I thought
Wow - a package with file, thread and socket classes that I don't have
to write myself! Now I'm not that amused any more.
What I'm writing is a server for windows and linux. SocketService seems
nice. It says it can act as a single-threaded server, the problem is
that I don't know how. I looked at the example of this server, that had
strange lists and itemlists and weird stuff. It said it was
"single-threaded" but used subclassed Thread classes etc... I just Don't
want that. Q1; Is there a SIMPLE example of a SIMPLE single-threaded
socket server somewhere out there? If the classes are well written, such
examples whouldn't need to be many lines and wouldn't need to subclass
dozens of classes.
About the File classes - Q2; Is there one class that handles files and
Nothing else? I don't need threaded file classes nor mapped things or
such. Just (again) a Simple class that I don't want to (since there
shouldn't be no reason to) subclass?
This lib seems to include many useful things, but now I'm only confused
with everything, and reference-dox that usually is all I need won't help
me. Hopefully one of you can :-)

/Gustaf





From MAILER-DAEMON Wed Jun 18 08:38:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ScBB-0003Cw-VY
	for mharc-bug-commoncpp@gnu.org; Wed, 18 Jun 2003 08:36:45 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19SGPP-0006xg-Mp
	for bug-commoncpp@gnu.org; Tue, 17 Jun 2003 09:21:59 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19SGPJ-0006mm-70
	for bug-commoncpp@gnu.org; Tue, 17 Jun 2003 09:21:55 -0400
Received: from mail3.band-x.net ([213.232.68.12])
	by monty-python.gnu.org with smtp (Exim 4.20)
	id 19SGOZ-0006Ro-VJ
	for bug-commoncpp@gnu.org; Tue, 17 Jun 2003 09:21:08 -0400
Received: (qmail 6303 invoked from network); 17 Jun 2003 13:20:47 -0000
Received: from watchguard.band-x.net (HELO hermes.band-x.com) (213.166.3.58)
  by 0 with SMTP; 17 Jun 2003 13:20:47 -0000
Received: by hermes.band-x.com with Internet Mail Service (5.5.2656.59)
	id <LB6A4PA3>; Tue, 17 Jun 2003 14:16:18 +0100
Message-ID: <A5E33C0DF95BCA40A0BC0F16E5E34023817E4B@hermes.band-x.com>
From: Ian Campbell <Ian.Campbell@band-x.com>
To: "'bug-commoncpp@gnu.org'" <bug-commoncpp@gnu.org>
Date: Tue, 17 Jun 2003 14:16:16 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailman-Approved-At: Wed, 18 Jun 2003 08:36:43 -0400
Subject: Thread memory leak
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 17 Jun 2003 13:22:29 -0000

David et al,

I have recently ported my code to version 2 of the library (latest version
commoncpp2-1.0.12) and have come up with a memory leak in the Thread class.
When a subclass that extends Thread is created but not started, the memory
associated with the "priv" member is not deleted (this is the ThreadImpl
data) when the thread is deleted, the following simple code illustrates the
situation:

#include <cc++/thread.h>
#include <mpatrol.h> /* Leak tracer include */

using namespace ost;

class TestThread : public Thread {

	public:
		void run() {
			while (1 == 1) {
				this->sleep(1000);
			}
		}

};


int main () {

	TestThread *a, *b, *c;

	a = new TestThread();
	b = new TestThread();
	c = new TestThread();

	a->start();

	delete a;
	delete b;
	delete c;

}

Here all data associated with "a" is deleted but not "b" and "c".
 
Using my favourite memory checker (www.cbmamiga.demon.co.uk/mpatrol) I get
the following leaked memory as you can see below:

top 5 unfreed memory entries in leak table:

       bytes   count  location
    --------  ------  --------
        8160       1  __pthread_initialize_manager
         424       2  __Q23ost6ThreadiUi			<-------
ThreadImpl data * 2
         212       1  __Q23ost6Threadb
         128       1  pthread_setspecific
          24       1  __9streambufi
        8948       6  total

Any thoughts on how to avoid this, without the naive solution (starting
every thread)? I occasionally create thread objects without starting them in
some of my code for house keeping purposes, for example with STL containers
of threads.

Ian Campbell
Band-X Ltd.



From MAILER-DAEMON Wed Jun 18 19:05:34 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19SlxI-0005nf-4H
	for mharc-bug-commoncpp@gnu.org; Wed, 18 Jun 2003 19:03:04 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19SlEg-0001fd-CF
	for bug-commoncpp@gnu.org; Wed, 18 Jun 2003 18:16:58 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19SlCV-00010b-4i
	for bug-commoncpp@gnu.org; Wed, 18 Jun 2003 18:14:43 -0400
Received: from mail3.ca.com ([208.232.182.10] helo=uslims56.ca.com)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19Sl1P-0004lE-Vp
	for bug-commoncpp@gnu.org; Wed, 18 Jun 2003 18:03:16 -0400
Received: from usilms25.ca.com ([141.202.201.25]) by uslims56.ca.com with
	Microsoft SMTPSVC(5.0.2195.5329);	 Wed, 18 Jun 2003 17:03:14 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C335E5.69FF2A72"
Date: Wed, 18 Jun 2003 18:03:13 -0400
Message-ID: <233D82105D12C34297AC84B8041712F9024B7B84@usilms25.ca.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: win32 static lib option gone
Thread-Index: AcM15SYGJZ75L4SMRWGS2+5RUzlILQAADbmg
From: "Kubena, Trey" <Trey.Kubena@ca.com>
To: <bug-commoncpp@gnu.org>
X-OriginalArrivalTime: 18 Jun 2003 22:03:14.0247 (UTC)
	FILETIME=[6A39ED70:01C335E5]
X-Mailman-Approved-At: Wed, 18 Jun 2003 19:03:01 -0400
Subject: FW: win32 static lib option gone
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 18 Jun 2003 22:17:22 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C335E5.69FF2A72
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
Why are we now being limited after 1.9.0 to ccxxgnu2 being only built in
dll context?  Why not offer it in a static form as well?  We are now
being forced to distribute this dll instead of the ability to static
link it in to our applications.

------_=_NextPart_001_01C335E5.69FF2A72
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C335AA.BD115CD0">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Why are we now being limited after 1.9.0 to ccxxgnu2 =
being
only built in dll context?<span style=3D'mso-spacerun:yes'>&nbsp; =
</span>Why not
offer it in a static form as well?<span =
style=3D'mso-spacerun:yes'>&nbsp;
</span>We are now being forced to distribute this dll instead of the =
ability to
static link it in to our applications.<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C335E5.69FF2A72--



From MAILER-DAEMON Mon Jun 23 08:09:13 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19UQ7H-0003hd-SK
	for mharc-bug-commoncpp@gnu.org; Mon, 23 Jun 2003 08:08:11 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19UQ6l-0003Jf-5S
	for bug-commoncpp@gnu.org; Mon, 23 Jun 2003 08:07:39 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19UQ6O-0002Hq-L5
	for bug-commoncpp@gnu.org; Mon, 23 Jun 2003 08:07:18 -0400
Received: from gw.ukmail.org ([195.112.37.194] helo=jolt)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19UQ6D-0001gr-IV
	for bug-commoncpp@gnu.org; Mon, 23 Jun 2003 08:07:05 -0400
Received: from jolt ([127.0.0.1] helo=acid)
	by jolt with smtp (Exim 3.35 #1 (Debian))
	id 19UQ9A-0000oS-00
	for <bug-commoncpp@gnu.org>; Mon, 23 Jun 2003 13:10:08 +0100
Message-ID: <003e01c3397f$efb93cb0$147ba8c0@acid>
From: "Nick Liebmann" <nick@ukmail.org>
To: <bug-commoncpp@gnu.org>
Date: Mon, 23 Jun 2003 13:06:50 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: Build Problems
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 23 Jun 2003 12:08:10 -0000

Hi,

I had a couple of problems with this version

Version 2-1.0.12:
System Linux..

1) URLStream.cpp was not included in src/Makefile, so the URLStream classes
were missing
2) The library, when built calls itself  libccgnu2-1.0.so.0.0.10 (I would
expect it to end with .12)

regards

Nick




