http://bugzilla.moblin.org/show_bug.cgi?id=3604
--- Comment #22 from pohly <[email protected]> 2009-09-08 05:23:58 --- (In reply to comment #21) [...] > > Therefore I prefer the struct approach after all. Thoughts? > Good, I also like this idea. > Besides, I'd like to add some padding fields for future expansion to avoid > re-compile if needing a new field in the future. Please don't bother. We don't have a stable ABI anywhere else either, so UIs and backends which link with SyncEvolution directly must be recompiled on each version change, at least to be on the save side. Introducing such a stable ABI is a major task by itself and should be done in a consistent way, which will revisit this particular aspect of the API if we ever attack this problem. Besides, if we add new key fields, implementors of the calls *have* to be recompiled. Otherwise they ignore relevant keys and access the underlying keyring incorrectly. If the new key field is somehow optional, then there's no need to add it. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
