<?xml version="1.0"?>
<rss version="2.0">
	<channel>
		<title>why should I use al_malloc() over malloc()?</title>
		<link>http://www.allegro.cc/forums/view/612517</link>
		<description>Allegro.cc Forum Thread</description>
		<webMaster>matthew@allegro.cc (Matthew Leverton)</webMaster>
		<lastBuildDate>Fri, 03 May 2013 08:30:01 +0000</lastBuildDate>
	</channel>
	<item>
		<description><![CDATA[<div class="mockup v2"><p>The manual says that al_malloc is</p><div class="quote_container"><div class="title"><a href="https://www.allegro.cc/manual/5/al_malloc">manual</a> said:</div><div class="quote"><p>Like malloc() in the C standard library, but the implementation may be overridden.</p></div></div><p>

what does that mean? Overriding the implementation with what? Is there a reason I should be using al_malloc? And most importantly, should I be using the al_ memory functions differently from how I use malloc() and friends?
</p></div>]]>
		</description>
		<author>no-reply@allegro.cc (gentix)</author>
		<pubDate>Thu, 02 May 2013 18:46:12 +0000</pubDate>
	</item>
	<item>
		<description><![CDATA[<div class="mockup v2"><p><span class="source-code"><a href="http://www.allegro.cc/manual/al_malloc"><span class="a">al_malloc</span></a><span class="k2">(</span><span class="k2">)</span></span> calls <span class="source-code"><a href="http://www.delorie.com/djgpp/doc/libc/libc_551.html" target="_blank">malloc</a><span class="k2">(</span><span class="k2">)</span></span> unless you override the memory management functions with <span class="source-code"><a href="http://www.allegro.cc/manual/al_set_memory_interface"><span class="a">al_set_memory_interface</span></a><span class="k2">(</span><span class="k2">)</span></span>.
</p></div>]]>
		</description>
		<author>no-reply@allegro.cc (Jeff Bernard)</author>
		<pubDate>Fri, 03 May 2013 01:22:04 +0000</pubDate>
	</item>
	<item>
		<description><![CDATA[<div class="mockup v2"><p>Going out on a limb (or boxing glove), I&#39;m betting gentix is more confused now than pre-post. <img src="http://www.allegro.cc/forums/smileys/kiss.gif" alt=":-*" />
</p></div>]]>
		</description>
		<author>no-reply@allegro.cc (Dizzy Egg)</author>
		<pubDate>Fri, 03 May 2013 04:12:36 +0000</pubDate>
	</item>
	<item>
		<description><![CDATA[<div class="mockup v2"><p>It&#39;s just that you can override al_malloc and friends with versions that log memory allocations for debugging purposes. In short, it probably doesn&#39;t matter either way which you use <img src="http://www.allegro.cc/forums/smileys/wink.gif" alt=";)" /></p><p>If you are curious you can read memory.c and memory.h in Allegro&#39;s source, they are short and easy to understand.
</p></div>]]>
		</description>
		<author>no-reply@allegro.cc (torhu)</author>
		<pubDate>Fri, 03 May 2013 05:53:21 +0000</pubDate>
	</item>
	<item>
		<description><![CDATA[<div class="mockup v2"><p>A few functions <b>require</b> you to use al_malloc or al_free. This will be mentioned in the documentation. Apart from being overridable, the version of malloc/free that Allegro sees may not necessarily match the malloc/free that your program sees.
</p></div>]]>
		</description>
		<author>no-reply@allegro.cc (Peter Wang)</author>
		<pubDate>Fri, 03 May 2013 08:30:01 +0000</pubDate>
	</item>
</rss>
