On Mon, 2006-07-10 at 16:38 +0300, Tommi Komulainen wrote:
> On Mon, 2006-07-10 at 09:15 -0300, ext Gustavo Sverzut Barbieri wrote:
> > On 7/10/06, Tommi Komulainen <[EMAIL PROTECTED]> wrote:
> > > 2. memory consumption
> > > 4. run-time speed?
> >
> > These are not an issue, really. Since python does garbage collect, in
> > the long run it may show even more memory efficient than pure C, which
> > may leak.
>
> Memory leaks in C are fixable, just takes some effort. OTOH the python
> interpreter / wrapper overhead are not. I've also been told that python
> never releases memory back to the system, though that ought to be
> fixable. Whether those are significant issues I haven't measured, just
> some rough edges to keep in mind.
PyGTK also initialises every type in GTK+ at startup instead of
on-demand (as with C applications), which is part of the slow
startup/high memory usage problem.
Ross
--
Ross Burton mail: [EMAIL PROTECTED]
jabber: [EMAIL PROTECTED]
www: http://www.burtonini.com./
PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF
_______________________________________________
maemo-developers mailing list
[email protected]
https://maemo.org/mailman/listinfo/maemo-developers
