<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/ucgn/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/ucgn/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/ucgn/bugs/</id><updated>2011-06-07T20:12:03Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>execution order of during actions incorrect</title><link href="https://sourceforge.net/p/ucgn/bugs/5/" rel="alternate"/><published>2011-06-07T20:12:03Z</published><updated>2011-06-07T20:12:03Z</updated><author><name>Kai Harth</name><uri>https://sourceforge.net/u/kharth/</uri></author><id>https://sourceforge.netcd5c9bf987e824f9f52a3d4bcb5f1dda0396c2e3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;in case of nested states with the top-states having no own exiting transitions Simulink seems to want the top-states during action executed before the sub-states' transitions are tested.&lt;br /&gt;
This is different from what is implemented in the code generator right now...&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>update to stateflow transition label notation</title><link href="https://sourceforge.net/p/ucgn/bugs/4/" rel="alternate"/><published>2010-10-04T20:41:32Z</published><updated>2010-10-04T20:41:32Z</updated><author><name>Kai Harth</name><uri>https://sourceforge.net/u/kharth/</uri></author><id>https://sourceforge.net8e15dfd3a1fe6df5ff3b323b6b798720a15b63d7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;An update to the parsing of Stateflow transition labels is required, because Mathworks changed the syntax:&lt;/p&gt;
&lt;p&gt;Originally the syntax was:&lt;br /&gt;
[condition]{condition_action}/{transition_action}&lt;/p&gt;
&lt;p&gt;Now the new syntax is:&lt;br /&gt;
[condition]{condition_action}/transition_action&lt;br /&gt;
(no curly brackets around the transition action)&lt;/p&gt;
&lt;p&gt;Stateflow seems to tolerate the old notation.&lt;/p&gt;
&lt;p&gt;The UCGN parser won't recognize the new notation.&lt;/p&gt;
&lt;p&gt;(As a workaround, the old notation can be used until a fix/update is provided)&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>relational expression parsing error</title><link href="https://sourceforge.net/p/ucgn/bugs/3/" rel="alternate"/><published>2010-07-18T19:57:43Z</published><updated>2010-07-18T19:57:43Z</updated><author><name>Kai Harth</name><uri>https://sourceforge.net/u/kharth/</uri></author><id>https://sourceforge.neteb9b84e05dbf2fd7f09da3a24b4ea5d180e25c7f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;the "not equal" expression in the non-matlab notation "!=" (legal in Stateflow) is not parsed correctly, leading to a fatal parsin error&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Expression precedence error</title><link href="https://sourceforge.net/p/ucgn/bugs/2/" rel="alternate"/><published>2010-06-24T19:59:43Z</published><updated>2010-06-24T19:59:43Z</updated><author><name>Kai Harth</name><uri>https://sourceforge.net/u/kharth/</uri></author><id>https://sourceforge.net6cfce9578122788228b10868df075353dbef0923</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The expression parser (for stateflow) parses binary expressions combining logical and addition/subtraction expressions in the wrong order of precedence:&lt;/p&gt;
&lt;p&gt;a &amp;lt; b - 5&lt;br /&gt;
is evaluated as &lt;br /&gt;
(a &amp;lt; b) - 5... resulting in "logical - 5"&lt;br /&gt;
instead of&lt;br /&gt;
a &amp;lt; (b -5)&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Replication of array indices in Stateflow code</title><link href="https://sourceforge.net/p/ucgn/bugs/1/" rel="alternate"/><published>2010-06-23T22:33:40Z</published><updated>2010-06-23T22:33:40Z</updated><author><name>Kai Harth</name><uri>https://sourceforge.net/u/kharth/</uri></author><id>https://sourceforge.net2e13f1843094c87579a420ef63bbbc4201355ae4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;/* Assignment of StateFlow chart inputs */&lt;/p&gt;
&lt;p&gt;for (Idx1 = 0u; Idx1 &amp;lt; 512u; Idx1++) {&lt;/p&gt;
&lt;p&gt;UpdateStateSfFcnScopeInst-&amp;gt;NewBytesBuffer[Idx1][Idx1] = NewBytesBuffer[Idx1][Idx1];&lt;/p&gt;
&lt;p&gt;} /* end of for */&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>