www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amir Kolsky" <akol...@mobilespear.com>
Subject general/9207
Date Sat, 22 Dec 2001 18:10:00 GMT
The following reply was made to PR general/9207; it has been noted by GNATS.

From: "Amir Kolsky" <akolsky@mobilespear.com>
To: <apbugs@apache.org>
Cc:  
Subject: general/9207
Date: Sat, 22 Dec 2001 20:03:39 +0200

 This is a multi-part message in MIME format.
 
 ------_=_NextPart_001_01C18B12.FBD8BB9C
 Content-Type: text/plain;
 	charset="us-ascii"
 Content-Transfer-Encoding: quoted-printable
 
 I find your comment disturbing.
 
 =20
 
 It will take some time until 2.0 will be released. Hence 1.3 is still
 important..
 
 =20
 
 Secondly, I have gone through the warnings, and save for a few socket
 issues, most of these warning can go away in a manner that is portable.
 For example, there are quite a few
 
 =20
 
 Int < size_t problems, where the int is just an iteration variable.
 Making it a size_t too will make the problem go away in a totally
 portable manner.
 
 =20
 
 Amir
 
 =20
 
 
 ------_=_NextPart_001_01C18B12.FBD8BB9C
 Content-Type: text/html;
 	charset="us-ascii"
 Content-Transfer-Encoding: quoted-printable
 
 <html>
 
 <head>
 <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
 charset=3Dus-ascii">
 
 
 <meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">
 
 <style>
 <!--
  /* Style Definitions */
  p.MsoNormal, li.MsoNormal, div.MsoNormal
 	{margin:0cm;
 	margin-bottom:.0001pt;
 	font-size:12.0pt;
 	font-family:Arial;}
 a:link, span.MsoHyperlink
 	{color:blue;
 	text-decoration:underline;}
 a:visited, span.MsoHyperlinkFollowed
 	{color:purple;
 	text-decoration:underline;}
 span.EmailStyle17
 	{font-family:Arial;
 	color:windowtext;}
 @page Section1
 	{size:595.3pt 841.9pt;
 	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
 div.Section1
 	{page:Section1;}
 -->
 </style>
 
 </head>
 
 <body lang=3DEN-US link=3Dblue vlink=3Dpurple>
 
 <div class=3DSection1>
 
 <p class=3DMsoNormal><font size=3D2 face=3DArial><span =
 style=3D'font-size:10.0pt'>I
 find your comment disturbing.</span></font></p>
 
 <p class=3DMsoNormal><font size=3D2 face=3DArial><span =
 style=3D'font-size:10.0pt'>&nbsp;</span></font></p>
 
 <p class=3DMsoNormal><font size=3D2 face=3DArial><span =
 style=3D'font-size:10.0pt'>It
 will take some time until 2.0 will be released. Hence 1.3 is still =
 important..</span></font></p>
 
 <p class=3DMsoNormal><font size=3D2 face=3DArial><span =
 style=3D'font-size:10.0pt'>&nbsp;</span></font></p>
 
 <p class=3DMsoNormal><font size=3D2 face=3DArial><span =
 style=3D'font-size:10.0pt'>Secondly,
 I have gone through the warnings, and save for a few socket issues, most =
 of
 these warning can go away in a manner that is portable. For example, =
 there are
 quite a few</span></font></p>
 
 <p class=3DMsoNormal><font size=3D2 face=3DArial><span =
 style=3D'font-size:10.0pt'>&nbsp;</span></font></p>
 
 <p class=3DMsoNormal><font size=3D2 face=3DArial><span =
 style=3D'font-size:10.0pt'>Int &lt;
 size_t problems, where the int is just an iteration variable. Making it =
 a size_t
 too will make the problem go away in a totally portable =
 manner.</span></font></p>
 
 <p class=3DMsoNormal><font size=3D2 face=3DArial><span =
 style=3D'font-size:10.0pt'>&nbsp;</span></font></p>
 
 <p class=3DMsoNormal align=3Dright dir=3DRTL =
 style=3D'text-align:left;direction:rtl;
 unicode-bidi:embed'><font size=3D2 face=3DArial><span dir=3DLTR =
 style=3D'font-size:
 10.0pt'>Amir</span></font></p>
 
 <p class=3DMsoNormal><font size=3D3 face=3DArial><span =
 style=3D'font-size:12.0pt'>&nbsp;</span></font></p>
 
 </div>
 
 </body>
 
 </html>
 =00
 ------_=_NextPart_001_01C18B12.FBD8BB9C--

Mime
View raw message