Am 15.04.2009 15:37 Uhr schrieb "Albrecht Schlosser" unter
<[email protected]>:
> Albrecht Schlosser wrote:
>> MacArthur, Ian (SELEX GALILEO, UK) wrote:
>>
>>> It in the OksiD 1.1.6-utf patches, so I guess it was current back in the
>>> 2005 timeframe. It may well be the case that things have been fixed in
>>> the meantime.
>>
>> If it is really that old, then IMHO our best bet is to remove the
>> comment and see what happens. If anybody reports crashes, then we
>> can track it down.
>>
>> No risk, no fun ... ;-)
>
> Today Grigoriy (the OP of STR 2185) asked in fltk.bugs:
>
>> Hi. So when this fix will go to svn?
>> I'm just thinking of making separate patch and include it into ebuild or
>> if it will be fixed in repo soon I'll just wait for it.
>> Thanks.
>
> Should we remove the comment and see what happens, as I proposed
> above two weeks ago?
Yes. We can't leave te software with a huge memory leak. If we then get
crashes on outdated servers, we may have to find a run-time test and warn,
or disable that particular feature on those platforms. Or, as a last resort,
pop up a dialog that informs the end user to upgrade their X11 server... .
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
