[Michael Cardenas]
Isn't it true that you can only safely add onto the end of a struct
on i386? Since the stack is allocated backwards on ppc, wouldn't
adding to the end of the struct still break old clients?
No. If the library clients never allocates or uses the struct content
directly, and
On Tue, Nov 19, 2002 at 11:51:35PM +0100, Petter Reinholdtsen wrote:
[Junichi Uekawa]
You can add members at the end of struct if and only if any other
application does not try to malloc it.
Both malloc and static variables will be a problem. Examples of bad
interface:
Isn't it true
[Junichi Uekawa]
You can add members at the end of struct if and only if any other
application does not try to malloc it.
Both malloc and static variables will be a problem. Examples of bad
interface:
/* library */
typedef struct { int a; } foo;
void use_foo(foo *f) { ... }
/* client
tis 2002-11-05 klockan 03.18 skrev Junichi Uekawa:
But surely adding stuff to a data structure is a backward-incompatible
change?
It depends on the way you do it.
You can add stuff to a data structure without breaking backwards compatibility.
I'm considering adding more stuff to struct
At 14 Nov 2002 00:10:32 +0100,
Martin Sj�gren wrote:
[1 text/plain (quoted-printable)]
tis 2002-11-05 klockan 03.18 skrev Junichi Uekawa:
But surely adding stuff to a data structure is a backward-incompatible
change?
It depends on the way you do it.
You can add stuff to a data
we don't need to bump soversion at all, unless we make
backward-incompatible changes. just bump minor (and don't change the
packaging name). Also, fix shlibs to depend on that version or
later.
But surely adding stuff to a data structure is a backward-incompatible
change?
It
* Martin Sjögren
| I've added priority parsing to libd-i, which is yet another
| interface-changing addition, but since libd-i2 hasn't been uploaded yet,
| and neither have the packages that depend on it, I haven't increased the
| soversion.
|
| This will probably break some things, but I
sön 2002-11-03 klockan 15.36 skrev Tollef Fog Heen:
we don't need to bump soversion at all, unless we make
backward-incompatible changes. just bump minor (and don't change the
packaging name). Also, fix shlibs to depend on that version or
later.
But surely adding stuff to a data structure
I've added priority parsing to libd-i, which is yet another
interface-changing addition, but since libd-i2 hasn't been uploaded yet,
and neither have the packages that depend on it, I haven't increased the
soversion.
This will probably break some things, but I intend to have as policy not
to
9 matches
Mail list logo
