[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: none
From: |
Ingo Ruhnke |
Subject: |
Re: none |
Date: |
08 Oct 2002 13:32:43 +0200 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
David Philippi <address@hidden> writes:
> On Tuesday 08 October 2002 01:09, address@hidden wrote:
>> +#define COLMAP_WITH_MEMORY_HOLE 1
>
> Could you explain to the list what those memory holes are? I've seen
> much to much code like this for my liking. It seems to me that this
> is related to a ClanLib bug?
No, its not a ClanLib bug, its simply like this:
If you want to access the data from a surface provider you have to
lock() it, once done you should unlock() it, since it will load and
unload the data from file if necesarry. Since loading it can/could be
a performance issue, the data stays lock() for all the time. Which is
not a memory hole, but not really nice programming praxis either.
Well, if this lock() thing really brings anything or not has to be
tested.
--
WWW: http://pingus.seul.org/~grumbel/
Games: http://pingus.seul.org/~grumbel/gamedesigns/
JabberID: address@hidden
ICQ: 59461927
- Re: [Pingus-CVS] CVS: Games/Pingus/src col_map.cxx,1.12,1.13 col_map.hxx,1.9,1.10 smallmap.cxx,1.21,1.22 smallmap.hxx,1.12,1.13, David Philippi, 2002/10/08