<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Advanced Policy Functional</title><link>https://sourceforge.net/p/splitcode/blog/2014/01/advanced-policy-functional/</link><description>Recent changes to Advanced Policy Functional</description><atom:link href="https://sourceforge.net/p/splitcode/blog/2014/01/advanced-policy-functional/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 31 Jan 2014 01:32:36 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/splitcode/blog/2014/01/advanced-policy-functional/feed.rss" rel="self" type="application/rss+xml"/><item><title>Advanced Policy Functional</title><link>https://sourceforge.net/p/splitcode/blog/2014/01/advanced-policy-functional/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I am currently trying to finish "Advanced" policy but the endeavor occurred really time-consuming. As for &lt;span&gt;[c153580]&lt;/span&gt; it is functional, comes with following limitations:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Only the content of ./Evolving and ./Stable is partitioned.&lt;/li&gt;
&lt;li&gt;Vague evolving symbols are not partitioned yet.&lt;/li&gt;
&lt;li&gt;no decent info on sizes of RAM and ROM sections yet.&lt;/li&gt;
&lt;li&gt;no explicit hints during build of why SplitCode performance degrades and uC requires reflashing.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The core of the idea is functional and there are no limitations on which resource references which - SplitCode manages that part as expected!&lt;br /&gt;
This was the hardest part of all.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brutte</dc:creator><pubDate>Fri, 31 Jan 2014 01:32:36 -0000</pubDate><guid>https://sourceforge.netdadb93abe5e559816adafb0ef169df4f9cb62112</guid></item></channel></rss>