Re: SDL XS fixes

[email protected] (David Goehrig)
Newsgroups perl.sdl.devel
Message-ID <[email protected]>
The answer is use DESTROY. And there was at one point a SDL::free  
method, but who knows if is still around.

Best advice on mem leaks is stop doing that. And by that I mean what  
your doing. You should never assume that it is safe to free anything  
when dealing with complex systems.

Typically in my apps I load everything at once and keep it around for  
the life of the app. I tend to prefer scratch buffers over relying an  
dynamic memory.

Dave

-=-=- [email protected] -=-=-

On Aug 29, 2009, at 9:49 AM, Kartik Thakore <[email protected]>  
wrote:

> Morning (from Canada)
>
> This is in regards to nothingmuch's advice on fixing memleaks. (
> http://yapgh.blogspot.com/2009/08/catching-memory-leaks-in-xs.html#comments 
> ).
>
>
> Thanks for the advice. I am currently working on separating the XS  
> name
> spaces in SDL.xs. This is the link I am using as a guide
> http://www.perl.com/doc/manual/html/pod/perlxs.html#Perl_Objects_And_C_Structures 
> .
> Hopefully I can put out a test soon. nothingmuch, if you can join us  
> on the
> mailing list or the irc channel #sdl irc.perl.org it would be much
> appreciated.
>
> Thanks
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.