[Kde-pim] Coding-style and tests

[Ingo Klöcker]

On Friday 08 March 2013, guy-kde wrote:
> Hello!
> 
> After any change(s) on the source(s) it is better to make some
> test(s). All will think that.
> But: do we have any tests, that test all the code? I think: not
> really.
> 
> My proposal:
> - *BEFORE* making a change, one save the object, ie.
> 
> kdepimlibs/build/akonadi/CMakeFiles/akonadi-kde.dir/entitytreeview.cp
> p.o - make the change
> - compile the new source
> - compare the old and the new object.
> If no difference is shown, one may consider the change as "save".

I'm not sure the object code will be identical. Using ccache might be a 
better alternative, i.e. if with ccache nothing is re-compiled after 
changing the source code then the change is safe.


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/20130308/a91ab663/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/