[Kde-pim] Coding-style and tests

[Guy Maurel]

On Thursday 14 March 2013 00:07:02 David Faure wrote:
> 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.
> 
> In release mode it should be.
My proposal is to make the test AT LEAST in the release mode.

> In debug mode there could be a difference due to line numbers in the debug
> info for gdb, indeed. Not sure exactly how this gets encoded, but surely it
> must be somewhere.
In this 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/