Re: [Announce] Amaya 10 .1-pre snapshot

<[email protected]> <1210062028.26174.11.camel@localhost>
Message-ID: <82545ab208b937a892393e68d5564b44@localhost>
X-Sender: [email protected]
Received: from 195.224.154.166 [195.224.154.166] with HTTP/1.1 (POST); Tue, 06
	May 2008 10:33:54 +0200
User-Agent: RoundCube Webmail/0.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit


Yes, the warnings definitely appeared with gcc 4.2, my patches precisely
correct
them. When I started doing this there was some 5000 of them...

TtaSetEnvString and friends are other funtions I spotted, but they go down
to
other functions doing nasty things and changing characters in what should
be set
a constant strings, with some fairly annoying bits.

Fixing what FindCompleteName() in thotlib/base/fileaccess.c does to
fileName so
it can be set to a const would allow a few more fixes.

Thanks

Regis

On Tue, 06 May 2008 10:20:28 +0200, Émilien Kia <[email protected]>
wrote:
> In fact, your patches dont generate directly hundred of warnings but, we
> must changes some other function prototypes (char* to const char* like
> TtaSetEnvString or TtaSetTextContent ...) which generate other warnings
> (and so on in cascade).
> I also have upgraded my gcc to a recent version (4.2.3) which is more
> strict than before, so perhaps some warnings are due to gcc upgrade.
>