[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r12919 - in trunk/subversion: include libsvn_subr mod_dav_svn tests/clients/cmdline

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-02-10 20:04:59 CET

Julian Foad <julianfoad@btopenworld.com> wrote on 02/10/2005 09:30:27 AM:

> Mark Phippard wrote:
> > The way we are handling it in the EBCDIC port is to do exactly what
> > suggested. We defne character constants that escape the literal to
> > and then modified the code to use the constants.
> How extensive is this? Did you just need to do this for a few odd
> here and there, or does this involve replacing hundreds of literal
strings and
> characters all over the code base? Bear in mind that I don't know
> EBCDIC has any overlap with ASCII, or what your other options are (such
> controls to make certain parts be compiled with ASCII as the execution
> character set).
> Could you show us a patch for this, or is it all mixed up with lots of
> changes? Could you show us an example of exactly what you did? I'm
> to see whether it is something that we could reasonably maintain in the
> Subversion code base, or far too disruptive for that. It would also be
> interesting to see what macro names you use, what header files, and so
on, so
> that we don't needlessly conflict with you.

It is pretty extensive, EBCDIC and ASCII do not overlap at all. I am
going to send a separate post with detailed information on where we are
with the EBCDIC port.



Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 10 20:06:17 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.