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

Re: small issue with svn_client_statusx

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2005-04-23 05:06:50 CEST

Greg Hudson <ghudson@mit.edu> writes:

> On Thu, 2005-04-21 at 18:52, Philip Martin wrote:
>> I'm not sure that has any bearing on whether types are "compatible",
>> which is a term defined by the standard.
>
> Do we care whether the types are "compatible" according to the ANSI C
> standard? I'm not sure whether that term has any bearing on ABI
> compatibility, which is not (according to my best understanding) a
> concept addressed by the ANSI C standard.

The standard doesn't address dynamic linking, it restricts itself to
static linking so ABI compatibility doesn't really come up.

Look at it this way: the following is a compile error with gcc and, as
far as I know, there is no compiler option to work around it:

$ echo "void f(char *p);void f(const char *p){}" | gcc -xc -
<stdin>:1: error: conflicting types for 'f'
<stdin>:1: error: previous declaration of 'f' was here

The change that is proposed effectively splits that in half, compiles
it twice and then links the two bits together at runtime to achieve
what would be undefined behaviour if it were linked statically.

In practice I think it will work on all the systems I have used.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 23 05:07:35 2005

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