liboctave/kpse.cc

[CdeMills]

While looking at warnings produced when configures with
--enable-strict-warnings, I had a lool at kpse.cc. It seems this file came
from kpathsea, the copyright is from 1998. It received a c++ suit, and
various corrections have been brought over the time. But kpathsea is still
under development, and there is a risk of divergences. Morevoer, there are a
few c++ structs defined, not classes, with pointer data members. This means
that there are potential problems of memory leakage and dangling pointers.

What should be do with respect to this ? The kpathsea lib is not distributed
separatelly. It's a component of tex-live, programmed in pure C. 
- have a kpathsea dir, like gnulib, with periodic updates from upstream, and
have an octave-specific C++ wrapper ?
- try to have more interactions with kpathsea maintainers ?
- try to have better merge of modifications in upstream with the
octave-specific kpse.cc ?

Regards

Pascal
-- 
View this message in context: 
http://octave.1599824.n4.nabble.com/liboctave-kpse-cc-tp3231287p3231287.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.