From quanta  Sun Apr 15 06:59:44 2007
From: Andras Mantia <amantia () kde ! org>
Date: Sun, 15 Apr 2007 06:59:44 +0000
To: quanta
Subject: Re: [Quanta] Help with Quanta+ code
Message-Id: <200704150959.51620.amantia () kde ! org>
X-MARC-Message: https://marc.info/?l=quanta&m=117662391727689
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1339699646=="

--===============1339699646==
Content-Type: multipart/signed;
  boundary="nextPart1537468.XeBi2henqM";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1537468.XeBi2henqM
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

On Saturday 14 April 2007, Munawar Hafiz wrote:
> I need some help understanding the Quanta+ codebase. In particular I
> have three questions.
>
> 1. Does the C/C++ code use the string library functions (strcpy,
> strcat, gets etc)?

No, they are generally avoided in favor of the QString class, which is=20
safer, easier to use and works with unicode internally.

> 2. Or does it use some sort of buffer bounds checking, either by
> rewriting the string library, or checking before every buffer
> operation?

See above.

> 3. Is the bounds checking available from the first release, or it has
> been included in a subsequent release? How did the development team
> go about making this change in the code?

QString was there since always, provided by the Qt library.
Generally when coding in C++ using the Qt and KDE libraries you don't=20
really have to think about boundary checking. Sure, there are cases=20
when it's not a good idea to access the n+1'd element of an array, but=20
this usually doesn't result in memory corruption, only in an error from=20
the framework (or in certain cases the n+1 element is added to the=20
array).
=46or strings there are only a few cases when you have to think about the=20
length of the string.

Andras

=2D-=20
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org

--nextPart1537468.XeBi2henqM
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iD8DBQBGIc1nTQdfac6L/08RAu/5AKDii9z09AKH4J7qgA4angTNPiRuxQCeNTCR
5pf1QSRbktEuc40gzEQcMJ8=
=JVFx
-----END PGP SIGNATURE-----

--nextPart1537468.XeBi2henqM--

--===============1339699646==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Quanta mailing list
Quanta@mail.kde.org
https://mail.kde.org/mailman/listinfo/quanta

--===============1339699646==--