Re: [Gimp-developer] Testing on NULL an unitialized values

2010-04-23 Thread Oliver Bandel
Zitat von Sven Neumann s...@gimp.org: On Wed, 2010-04-21 at 18:30 +0200, Martin Nordholts wrote: On 04/21/2010 01:58 PM, Oliver Bandel wrote: Even only temporarily valies, if set to a certain value, like 0 or NULL, will help in finding problems. I agree, and I try to initialize all local

Re: [Gimp-developer] Testing on NULL an unitialized values

2010-04-23 Thread Oliver Bandel
Hi Frederik, my main attend was to mention the problem of pointers, regarding uninitialized values. That's why I insisted on Null, and it makes sense often to use 0 or 0.0 for other values. As strings are char*, NULL should be used, not . You are right, that in some seldom situations it

Re: [Gimp-developer] Testing on NULL an unitialized values

2010-04-23 Thread Oliver Bandel
Zitat von Sven Neumann s...@gimp.org: Hi, On Thu, 2010-04-22 at 14:38 +0200, Fredrik Alströmer wrote: For the record, I'm not necessarily against setting a predefined value to variables sometimes. I'm just against doing it for the wrong reasons, and I'd much rather have the compiler say

Re: [Gimp-developer] Testing on NULL an unitialized values

2010-04-23 Thread Tor Lillqvist
You are right, that in some seldom situations it might make sense to initialize values to other start values. But they should always be predictable. You didn't get the reasoning about letting the compiler, or valgrind, catch use of uninitialized variables, did you? The same is here:  a

Re: [Gimp-developer] Testing on NULL an unitialized values

2010-04-23 Thread Tor Lillqvist
Will the compiler stop execution on any warning? It should, and not compile any code that gives warnings, otherwise your attempt will not work. People will ignore it just for testing. That depends on the project. Many projects do use flags like -Werror, although that is not always possible.

Re: [Gimp-developer] project gimp on sourceforge

2010-04-23 Thread Michael Schumacher
Von: Liam R E Quin l...@holoweb.net Someone has registered gimp on souceforge - http://gimp.sourceforge.net/ I see there's a Donate Money link, and a non-working download link, both of which may be harmful; maybe it's worth asking sourceforge for this not-gimp project to be deleted? For

Re: [Gimp-developer] Testing on NULL an unitialized values

2010-04-23 Thread Torsten Neuer
Am Freitag, 23. April 2010 08:39:52 schrieb Oliver Bandel: Zitat von Sven Neumann s...@gimp.org: Hi, On Thu, 2010-04-22 at 14:38 +0200, Fredrik Alströmer wrote: For the record, I'm not necessarily against setting a predefined value to variables sometimes. I'm just against doing it for

Re: [Gimp-developer] GSoc - Brush Selector Widget

2010-04-23 Thread Cédric Gémy
when you talk, I guess you have to diffenriate the brish list in any tool option and the brush window. many thing you describe can be used in the first way. THis is somewhat a pity, since : - it is boring to have hundreds of window open - since the brush options have been enhanced, the use of the

Re: [Gimp-developer] Testing on NULL an unitialized values

2010-04-23 Thread Oliver Bandel
Zitat von Tor Lillqvist t...@iki.fi: You are right, that in some seldom situations it might make sense to initialize values to other start values. But they should always be predictable. You didn't get the reasoning about letting the compiler, or valgrind, catch use of uninitialized

Re: [Gimp-developer] Testing on NULL an unitialized values

2010-04-23 Thread Oliver Bandel
Zitat von Torsten Neuer tne...@inwise.de: Am Freitag, 23. April 2010 08:39:52 schrieb Oliver Bandel: Zitat von Sven Neumann s...@gimp.org: Hi, On Thu, 2010-04-22 at 14:38 +0200, Fredrik Alströmer wrote: For the record, I'm not necessarily against setting a predefined value to

Re: [Gimp-developer] Testing on NULL an unitialized values

2010-04-23 Thread Oliver Bandel
Zitat von Tor Lillqvist t...@iki.fi: You are right, that in some seldom situations it might make sense to initialize values to other start values. But they should always be predictable. You didn't get the reasoning about letting the compiler, or valgrind, catch use of uninitialized variables,

Re: [Gimp-developer] Testing on NULL an unitialized values

2010-04-23 Thread Tobias Ellinghaus
Am Freitag, 23. April 2010 schrub Oliver Bandel: Zitat von Tor Lillqvist t...@iki.fi: You are right, that in some seldom situations it might make sense to initialize values to other start values. But they should always be predictable. You didn't get the reasoning about letting the

Re: [Gimp-developer] Testing on NULL an unitialized values

2010-04-23 Thread Oliver Bandel
hehe, the segfault did not came from the char* mytext, but from wrong indexing in the vector. :( my fault :( Heheh... nevertheless valgrind is on my side ;-) Somehow I got no crash from the uninitialized char*, but that might only happen after release at the user's computer: It's

Re: [Gimp-developer] project gimp on sourceforge

2010-04-23 Thread gg
On 04/23/10 10:36, Michael Schumacher wrote: Von: Liam R E Quinl...@holoweb.net Someone has registered gimp on souceforge - http://gimp.sourceforge.net/ I see there's a Donate Money link, and a non-working download link, both of which may be harmful; maybe it's worth asking sourceforge for

Re: [Gimp-developer] Trying to Make a Plug-In

2010-04-23 Thread Akkana Peck
Callie writes: Hey guys, I have very limited experience in programming, and none at all with making plugins, but I want to make a plugin that would make my life a whole lot easier. Unfortunately, it seems that all the information regarding this process is written for people who are