[Kde-pim] Re: KMime bug with Message-ID with two "at" signs.

Ingo Klöcker kloecker at kde.org
Wed Dec 1 23:17:42 GMT 2010


On Tuesday 30 November 2010, Andras Mantia wrote:
> Gregory Schlomoff wrote:
> > Option 1: Ident could derive directly from Structured, skipping
> > Address 
> > Option 2: Ident could derive from another class that
> > derives from Structured, like, I don't know, maybe Token
> > Option 3: Ident could derive from a new class that would derive
> > from Structured.

I'm not sure what the best option is. It depends on what Ident is used 
for apart from Message-Id, In-Reply-To and References.


> Without looking at the code, I'd like just to raise the binary
> compatibility issue here, changing the inheritance tree will most
> likely be NOT binary compatible with previous versions.

Well, I suppose we'd have to keep the old Ident class as-is but only use 
a new class for our purposes.


Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20101202/3d0f6c19/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


More information about the kde-pim mailing list