Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Frederik Schwarzer
Am Sonntag, 28. Februar 2016, 20:18:22 schrieb Nick Shaforostoff: > > > Let us know in this thread if code you're interested in isn't > > > there.> > > Could we have kdegames there? > > ok, i'll include them in the next build (in a week or so) Thank you.

Re[2]: Static code analysis - the easiest way to improve

2016-02-28 Thread Nick Shaforostoff
> To be honest, I've tried to use it many times, but I always seem to > end up diving in warnings in other projects. It's hard to filter for > projects I have a grasp on. > > How do you deal with this? i just sort by filepath/name (the column is on the right, you need to scroll horizontally to g

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Jaroslaw Staniek
On 28 February 2016 at 20:21, Aleix Pol wrote: > On Sun, Feb 28, 2016 at 3:59 PM, Jaroslaw Staniek wrote: > > Hi, > > Just to remind. If someone has some time to fix bugs, KDE > > apps/Calligra/Frameworks static analysis is the easiest way to improve > > Calligra. > > Code defects are well expla

Re: Segmentation fault in sample code

2016-02-28 Thread Albert Astals Cid
El Sunday 28 February 2016, a les 16:56:35, Alexander Semke va escriure: > > I reproduced the code from [1] to learn how to create KF5 applications. > > The > > application runs fine but if I first open some file and then quit through > > the quit action i get a segmentation fault. > > > > I ran t

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Aleix Pol
On Sun, Feb 28, 2016 at 3:59 PM, Jaroslaw Staniek wrote: > Hi, > Just to remind. If someone has some time to fix bugs, KDE > apps/Calligra/Frameworks static analysis is the easiest way to improve > Calligra. > Code defects are well explained (like uninitialized variables or > NULL-related failures

Re[2]: Static code analysis - the easiest way to improve

2016-02-28 Thread Nick Shaforostoff
> > Let us know in this thread if code you're interested in isn't there. > Could we have kdegames there? ok, i'll include them in the next build (in a week or so)

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Jaroslaw Staniek
On 28 February 2016 at 16:21, Frederik Schwarzer wrote: > Am Sonntag, 28. Februar 2016, 15:59:46 schrieb Jaroslaw Staniek: > > Hi, > > > Let us know in this thread if code you're interested in isn't there. > > Could we have > ​​ > kdegames there? > > ​Good idea, CC'd Nick as he updates the builds

Re: Segmentation fault in sample code

2016-02-28 Thread Alexander Semke
> I reproduced the code from [1] to learn how to create KF5 applications. The > application runs fine but if I first open some file and then quit through > the quit action i get a segmentation fault. > > I ran the application in GDB and created this backtrace: > > #0 0x74335b44 in () at

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Jaroslaw Staniek
On 28 February 2016 at 16:26, Tomas Mecir < ​​ mec...@gmail.com> wrote: > Well, I'd like to, but when I log in and try to access the KDE stuff, > I can see the summary, but accessing the actual defect list gives me a > red box with this: > > It may take a few minutes before you can view your defec

Segmentation fault in sample code

2016-02-28 Thread Christian Kalkhoff
Hi, I reproduced the code from [1] to learn how to create KF5 applications. The application runs fine but if I first open some file and then quit through the quit action i get a segmentation fault. I ran the application in GDB and created this backtrace: > #0 0x74335b44 in () at /usr

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Frederik Schwarzer
Am Sonntag, 28. Februar 2016, 15:59:46 schrieb Jaroslaw Staniek: Hi, > Let us know in this thread if code you're interested in isn't there. Could we have kdegames there? Regards, Frederik

Static code analysis - the easiest way to improve

2016-02-28 Thread Jaroslaw Staniek
Hi, Just to remind. If someone has some time to fix bugs, KDE apps/Calligra/Frameworks static analysis is the easiest way to improve Calligra. Code defects are well explained (like uninitialized variables or NULL-related failures). Much easier than actually reading that bug reports, analysing them

Re: Review Request 127178: Added writer plugin support

2016-02-28 Thread Varun Joshi
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127178/ --- (Updated Feb. 28, 2016, 2:17 p.m.) Status -- This change has been ma

Re: Review Request 127178: Added writer plugin support

2016-02-28 Thread Boudhayan Gupta
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127178/#review92850 --- Ship it! I still have reservations about the direct use of

Re: Review Request 127178: Added writer plugin support

2016-02-28 Thread Varun Joshi
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127178/ --- (Updated Feb. 28, 2016, 1:52 p.m.) Review request for Baloo, Boudhayan Gu

Re: MediaWiki syntax highlight plugin broken in Techbase?

2016-02-28 Thread Christian Kalkhoff
Am Sonntag, 28. Februar 2016, 12:12:51 CET schrieb Andreas Cord-Landwehr: > > > Is the installation broken? I read about some problems in another > > > thread. > > > > Seems someone already fixed it? > > Yes, Ingo already fixed it yesterday. Great! Thanks! Best, Christian -- Christian Kalkhoff

Re: MediaWiki syntax highlight plugin broken in Techbase?

2016-02-28 Thread Andreas Cord-Landwehr
On Sunday, February 28, 2016 11:25:23 AM CET Albert Astals Cid wrote: > El Saturday 27 February 2016, a les 14:26:14, Christian Kalkhoff va escriure: > > Hi, > > > > I just read the now current version of the "First program" tutorial [1] > > and > > discovered that the source code examples are no

Re: MediaWiki syntax highlight plugin broken in Techbase?

2016-02-28 Thread Albert Astals Cid
El Saturday 27 February 2016, a les 14:26:14, Christian Kalkhoff va escriure: > Hi, > > I just read the now current version of the "First program" tutorial [1] and > discovered that the source code examples are not properly formatted. There > is a tag visible in the output and the code > is split