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

Hi.

I have commited a (long long) modif including your patches (and many
others) about char*/const char*.

Some warnings remain, including libwww function bad prototypes.
I will look to them later.

Regards
Emilien


Le mardi 06 mai 2008 à 10:33 +0200, Regis Boudin a écrit :
> <[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.
> > 
> 
> 
> 
-- 
Émilien Kia <[email protected]>
INRIA Rhône-Alpes - WAM

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIIbaV/Yh544hmYFARAqDRAJ4632AGQ+09v24k4/kkmNwWMa+juQCdGJNf
/j21ZoPHwXtDVu7Wt9uKqak=
=26vU
-----END PGP SIGNATURE-----