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

List:       kde-devel
Subject:    Re: About memory allocation failures....
From:       Rodolfo Conde Martinez <rcm () gmx ! co ! uk>
Date:       2002-01-29 0:14:09
[Download RAW message or body]

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

On Monday 28 January 2002 23:02, Carsten Pfeiffer wrote:
> On Montag, 28. Januar 2002 18:53, Schmidt, John wrote:
> > Testing the return on malloc SHOULD be a given.
> > Here's something good to dump (or NOT)... the amount of memory allocated
> > by the KDE process(es)...
>
> AFAIK, the C++ standard says that new should never return 0L, instead it
> should throw a bad_alloc exception. So checking for 0L might work on some
> compilers, but is hardly reliable.
>

	mmmhh.....havent check all the kde code....but isnt it free of exception 
checking (as it does code bigger and slower doesnt it ?? )....and i guess not 
all compilers have the -fno-check-new and -fno-exceptions like g++, so if 
there isnt exception checking what happens ? the program just crashes ???
wouldnt be a good idea to set a function handler in the kdelibs maybe or a 
handler apropiated for each app ??

	Greetings....

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8VelRx2Sktruwba0RAhLfAKDVR1LHRoCXn+WY9lhvSZwCgAzxzQCaA80K
1t4I8dDvQCfz4EL/iHLWaco=
=j6m9
-----END PGP SIGNATURE-----


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]