Martin Kalen wrote:
>
> Martin Kalen: NO/-1
>
> We use Xerces-C on Windows NT4/2000, HP-UX, Linux, Solaris, AIX,
> OpenServer, UnixWare and Tru64 so I am neither pro-UNIX or pro-Windows.
>
> We have numerous hours invested in integrating the Xerces-C directory- and
> make-structure into our own automated make- and regression-test
> environment. Any change to the directory names would be a major setback for
> us.
1.
Your environment should be able to cope with minor directory renames. If
not, then I don't think that we should all be punished for your
mistakes.
2.
You should expect far more major changes to libraries at certain
intervals. A properly maintained library would keep a stable API for a
long time, and occasionally make large incompatible changes. If you say
that no incompatible changes should ever be made then you are opting for
stagnation. However, I repeat that this particular change should require
only minimal changes to existing builds.
>
> I think Peter Volchek et. al. summarised this very good - there are other
> issues that need to be dealt with before doing this. (The different ports
> are hopelessly out of synch with regards to the "main"/samples/tests
> directories, for one...)
>
> If there were no Murphy's law about diskcrashes and that autoconf-work had
> been saved, I would have voted differently. Now, it's just not worth it.
>
> Keep up the good work with Xerces-C!
>
> --
> Martin Kalen
> Software Engineer
> TODAY Systems, Inc.
> http://www.todaysystems.com.au/
> Tel +61-3-9536 3900 - Fax +61-3-9536 3901
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
Murray Cumming
www.murrayc.com
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
