Melchior FRANZ writes:

>There has at least 
>to be a "suppression" rule for every such C++ violation. I've
>already added some entries in my plib.supp file, because the 
>plib developers
>don't seem to be keen to fix it. 

Hey that's completely unfair !

You have made exactly 2 posts to the PLib list, both yesterday
I'll agree that you got 'one' rather curt reply from a 'self appointed' 
'overseer' of the project who FWIW IMHO generates a lot of noise 
on the list but that is another story

>(And they have a lot of such sloppy code.)  
Without examples that is IMHO completely out of line and as is the case
with most Open Source projects 'worthy' patches are usually accepted  :-)

>BTW: one real bug was already fixed in plib thanks to my
>valgrind tests on fgfs.  :-)

Which for the record was the only 'actual' patch you have submitted 
and was 'speedily' incorporated as it was as you say an actual bug,
albeit a harmless one for the current FGFS code tree.

Cheers

Norman

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to