[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: new widgets...
From:       Pupeno <pupeno () pupeno ! com>
Date:       2002-09-26 13:19:00
[Download RAW message or body]

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

On Thursday 26 September 2002 05:23, Thomas Zander wrote:
> > - KPasswordEdit: the api of this widget is rather poor returning a const
> > char* of the typed password (should it be a QString or something like
> > that ?) and there's not setPassword function.
>
> Returning a pointer to the string as typed by the user is the only way to
> make sure minimal copying and therefor maximum security can be reached.
> Please don't change that.
I imagined that the use of a char was for security reasons... but, what would 
happen with passwords containing unicode chars ?
Is still a setPassword(const char*?) method a bad idea ?
- -- 
Pupeno: pupeno@pupeno.com
http://www.pupeno.com
- ---
Help the hungry children of Argentina, 
please go to (and make it your homepage):
http://www.porloschicos.com/servlet/PorLosChicos?comando=donar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9kwlGLr8z5XzmSDQRAueUAJ9Ptqxo0IkRVgQXeQoVbtblRLAizQCgkwfQ
BQKx76sxF2bG6/utZM9ax+Y=
=P0ey
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]