Re: gec catcall warnings, how to read them?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Eric" == Eric Bezault <ericb-D6Qt/9opevxWk0Htik3J/[email protected]> writes:

    >> gelint doesn't help.

    Eric> In fact it does. If you use the --cat option, it will give
    Eric> you for each CAT-call error all the paths in the code that
    Eric> lead from the creation of the involved argument and target
    Eric> to their usage in the call reported in the error.

Yep, 4247 lines of output :-)

But thanks for the tips and I'll study the gelint output more closely.

- -- 
Live long and prosper,

Berend de Boer


PS: This email has been digitally signed if you wonder what the strange
characters are that your email client displays.
PGP public key: http://www.pobox.com/~berend/berend-public-key.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFG4PaKIyuuaiRyjTYRAqj7AJoCrdde22edr7wLwFKtkFOpo0+ucwCg3dEX
j98IAbFpPYUAASIybN9SGDw=
=B//i
-----END PGP SIGNATURE-----