[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KFileDialog patch - request for comments
From:       Trevor Harmon <trevor () vocaro ! com>
Date:       2002-06-28 2:30:48
[Download RAW message or body]

On Friday 28 June 2002 4:28 am, Waldo Bastian wrote:
> > Something else I just thought of...I had to add a new data member to a
> > dynamically allocated struct (KFileDialogPrivate) in order to save a copy
> > of the QWidget pointer. But according to the following, adding data
> > members to non-static structs breaks binary compatibility:
>
> Yes, but since these private structs are not part of the API it is not a
> problem since they are not used outside the kfiledialo implementation
> itself.
>
> In fact, that's the reason why we use FooBarPrivate *d; all over the place.

Hmm...so that document is wrong or, at best, misleading, since it says "You 
cannot add new data members to a class except static ones." It does not 
explicitly mention structs, but because internally structs are almost 
identical to classes, I figured it held for structs as well. Does the 
document need to be changed?

http://developer.kde.org/documentation/library/kdeqt/kde3arch/devel-binarycompatibility.html

Trevor


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]