I didn't know that in year 2003 standard C++ library was not supported in
all common platforms and compilers. (Since the Standard was published in
1998 and it's supported by all win32 compilers for several years)

I can imagine how the library could be optimized both in speed and in size
if it would be compiled with the standard library and template.

Will Xerces always be compiled only for Standard C or I could hope a step
ahead?

- Sebastien


----- Original Message ----- 
From: "Neil Graham" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, August 30, 2003 4:55 PM
Subject: Re: posting code



Hi Sebastien,

If you want to post proposals to modify the sources, you'll need to get to
know the diff utility.  Using it's -u option is the best way of describing
the delta between your modified file and the original source.  You'll also
want to use sources from CVS for this, rather than what was originally
distributed, since it's difficult to apply patches once the source against
which the patch was made changes.

As to this modification specifically:  I think the general direction of the
project is to rely less, rather than more, on standard C++ routines.
Remember that we need to run on many many different platforms, and standard
C++ tends to be rather less portable than standard C.  (And on many
platforms it's not as efficient either).  So I'm not sure we'd want to make
modifications of this sort.

Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone:  905-413-3519, T/L 969-3519
E-mail:  [EMAIL PROTECTED]




|---------+---------------------------->
|         |           Sébastien Demers |
|         |           <[EMAIL PROTECTED]|
|         |           utions.com>      |
|         |                            |
|         |           08/28/2003 04:35 |
|         |           PM               |
|         |           Please respond to|
|         |           xerces-c-dev     |
|         |                            |
|---------+---------------------------->

>---------------------------------------------------------------------------
------------------------------------------------------------------|
  |
|
  |       To:       <[EMAIL PROTECTED]>
|
  |       cc:
|
  |       Subject:  posting code
|
  |
|
  |
|

>---------------------------------------------------------------------------
------------------------------------------------------------------|



<
Hi Sebastien,

This has been fixed for quite a while in CVS.  It'll definitely be in the
next release (schedule for a little less than 2 months from now).
>

cool.

I dont know if I'm in the good place for posting suggestion of code (not
really bugs) like the following code in the file \util\XMLString.cpp

unsigned int XMLString::stringLen(const XMLCh* const src)
{
    if (src == 0 || *src == 0)
    {
        return 0;
   }
    else
   {
        return std::char_traits<XMLCh>::length(src);
   }
}

This small modification will accelerate considerably general parsing of
large input stream.

I have modified several files in library for this kind of problem and each
time a new library revision is posted, I have to update my files.

- Sebastien

----- Original Message -----
From: "Neil Graham" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 28, 2003 3:52 PM
Subject: Re: mess with <iostream.h>


Hi Sebastien,

This has been fixed for quite a while in CVS.  It'll definitely be in the
next release (schedule for a little less than 2 months from now).

Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone:  905-413-3519, T/L 969-3519
E-mail:  [EMAIL PROTECTED]




|---------+---------------------------->
|         |           Sébastien Demers |
|         |           <[EMAIL PROTECTED]|
|         |           utions.com>      |
|         |                            |
|         |           08/28/2003 03:46 |
|         |           PM               |
|         |           Please respond to|
|         |           xerces-c-dev     |
|         |                            |
|---------+---------------------------->

>
---------------------------------------------------------------------------
------------------------------------------------------------------|
  |
|
  |       To:       <[EMAIL PROTECTED]>
|
  |       cc:
|
  |       Subject:  mess with <iostream.h>
|
  |
|
  |
|

>
---------------------------------------------------------------------------
------------------------------------------------------------------|



In several files iostream.h, is still used in favor of iostream

Since the file iostream.h is obsolate. Why new revisions still using this
file instead of using iostream with a small using std::cout; ????

Please have a look in the file
xerces/c/src/xercesc/framework/StdOutFormatTarget.cpp for a party of mess.

- Sebastien



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to