[Kde-pim] Coding-style and tests

[Guy Maurel]

On Friday 08 March 2013 20:09:13 Ingo Klöcker wrote:
> 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.
ccache is used to speed-up the building of software.
My proposal provides as a first approach, a 100% testing of the binary code.
In this case, the change(s) of the source(s) don't produce any binary change.
They may be distributed. This is what I wanted to do now.

In other case, the binary code must be examined in detail. It should start a
new discussion by looking at the ASM code.
-- 
guy
_______________________________________________
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/