Re: Re: [UnixOS2] libc

On Mon, 23 Jun 2003, Andreas Buening wrote:

> b) Functions with new behaviour (like set/getuid):
>    - Old programs (binaries): Not effected if we keep the old
>      ordinal number and the broken old function together (the
>      new implementation of the function gets a new ordinal number).
> 
> c) Functions that change its declaration (like fseek if we change
>    to 64 bit by default; how many of them are there?):
>    - Old programs (binaries): If we want to keep binary compatibility
>      the old function must keep its ordinal (but may get a new name
>      -> fseek32)

However, as Ilya pointed out, this doesn't solve the problems for old
libraries (binaries), which don't reference the ordinal, just the function
name...

	Regards,
		Stefan