<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[MISRA Discussion Forums - MISRA AC SLSF discussions]]></title>
		<link>https://forum.misra.org.uk/</link>
		<description><![CDATA[MISRA Discussion Forums - https://forum.misra.org.uk]]></description>
		<pubDate>Thu, 05 Nov 2026 13:03:13 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[MISRA AC SLSF 2025 review]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1756</link>
			<pubDate>Mon, 27 Oct 2025 09:04:42 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=4">david ward</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1756</guid>
			<description><![CDATA[The MISRA AC working group is pleased to announce that updated drafts of its documents MISRA AC GMG and MISRA AC SLSF have been prepared. We will be conducting a public review of these drafts.<br />
<br />
Review sign-up is now closed and we will be in touch shortly with those who have responded.]]></description>
			<content:encoded><![CDATA[The MISRA AC working group is pleased to announce that updated drafts of its documents MISRA AC GMG and MISRA AC SLSF have been prepared. We will be conducting a public review of these drafts.<br />
<br />
Review sign-up is now closed and we will be in touch shortly with those who have responded.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[MATLAB R2025b]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1753</link>
			<pubDate>Wed, 08 Oct 2025 10:49:53 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=6287">misra-ac</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1753</guid>
			<description><![CDATA[No new Amendment to MISRA AC SLSF:2023 will be published in connection with <span style="font-family: 'Open Sans', sans-serif;" class="mycode_font">MATLAB release R2025b.</span><br />
<br />
Amendment 4 (MISRA AC SLSF:2023 AMD4, <span style="font-style: italic;" class="mycode_i">Revisions for MATLAB Release R2025a</span>) is applicable also to R2025b.  This <span style="font-family: 'Open Sans', sans-serif;" class="mycode_font">is available as a free download from the "MISRA AC resources" section of this Bulletin Board.</span>]]></description>
			<content:encoded><![CDATA[No new Amendment to MISRA AC SLSF:2023 will be published in connection with <span style="font-family: 'Open Sans', sans-serif;" class="mycode_font">MATLAB release R2025b.</span><br />
<br />
Amendment 4 (MISRA AC SLSF:2023 AMD4, <span style="font-style: italic;" class="mycode_i">Revisions for MATLAB Release R2025a</span>) is applicable also to R2025b.  This <span style="font-family: 'Open Sans', sans-serif;" class="mycode_font">is available as a free download from the "MISRA AC resources" section of this Bulletin Board.</span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[MISRA AC SLSF:2023 AMD4 available]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1744</link>
			<pubDate>Tue, 29 Jul 2025 08:34:36 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=6287">misra-ac</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1744</guid>
			<description><![CDATA[<span style="font-family: 'Open Sans', sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">MISRA AC SLSF:2023 Amendment 4</span> (which contains modifications that bring the guidelines up to date for MATLAB release R2025a) is now available as a free download from the "MISRA AC resources" section of this Bulletin Board.</span>]]></description>
			<content:encoded><![CDATA[<span style="font-family: 'Open Sans', sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">MISRA AC SLSF:2023 Amendment 4</span> (which contains modifications that bring the guidelines up to date for MATLAB release R2025a) is now available as a free download from the "MISRA AC resources" section of this Bulletin Board.</span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[MISRA AC SLSF:2023 AMD3]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1722</link>
			<pubDate>Mon, 13 Jan 2025 10:58:59 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=6287">misra-ac</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1722</guid>
			<description><![CDATA[This Amendment to MISRA AC SLSF:2023 contains modifications that bring the guidelines up to date for MATLAB release R2024b. It also includes revisions to the required statuses of some diagnostics and to the statuses of some library blocks and configurations.<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.misra.org.uk/images/attachtypes/pdf.png" title="Adobe Acrobat PDF" border="0" alt=".pdf" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=30" target="_blank" title="">MISRA AC SLSF 2023 AMD 3.pdf</a> (Size: 564.32 KB / Downloads: 2)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[This Amendment to MISRA AC SLSF:2023 contains modifications that bring the guidelines up to date for MATLAB release R2024b. It also includes revisions to the required statuses of some diagnostics and to the statuses of some library blocks and configurations.<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.misra.org.uk/images/attachtypes/pdf.png" title="Adobe Acrobat PDF" border="0" alt=".pdf" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=30" target="_blank" title="">MISRA AC SLSF 2023 AMD 3.pdf</a> (Size: 564.32 KB / Downloads: 2)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[MISRA AC SLSF:2023 AMD1 and AMD2 available]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1688</link>
			<pubDate>Wed, 05 Jun 2024 15:45:17 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=6287">misra-ac</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1688</guid>
			<description><![CDATA[<span style="font-family: 'Open Sans', sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">MISRA AC SLSF:2023 Amendment 1</span> and <span style="font-style: italic;" class="mycode_i">MISRA AC SLSF:2023 Amendment 2</span> (which contains modifications that bring the guidelines up to date for MATLAB releases R2023b and R2024a, respectively) are now available as free downloads from the "MISRA AC resources" section of this Bulletin Board.</span>]]></description>
			<content:encoded><![CDATA[<span style="font-family: 'Open Sans', sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">MISRA AC SLSF:2023 Amendment 1</span> and <span style="font-style: italic;" class="mycode_i">MISRA AC SLSF:2023 Amendment 2</span> (which contains modifications that bring the guidelines up to date for MATLAB releases R2023b and R2024a, respectively) are now available as free downloads from the "MISRA AC resources" section of this Bulletin Board.</span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[MISRA AC SLSF:2023 released]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1653</link>
			<pubDate>Wed, 09 Aug 2023 16:24:40 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=4">david ward</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1653</guid>
			<description><![CDATA[We are pleased to announce a new version of MISRA AC GMG has been released.<br />
<br />
The MISRA Autocode (AC) family of documents deals with the application of language subsets for automatic code generation purposes. This document, MISRA AC SLSF, contains the best practices, captured as a set of design and style guidelines, for the use of The Mathworks® Simulink® and Stateflow® tools for producing models that will be used for simulation and automatic code generation. Updated in June 2023, this second edition is the current version of MISRA AC SLSF. This document supersedes the first edition (published in 2009).<br />
<br />
The MISRA webstore provides single-user PDFs and you can purchase a hardcopy via a "print on demand" service at the following link. Please be sure to select the most appropriate “marketplace” for your location to expedite delivery. <a href="https://www.amazon.co.uk/dp/1911700065" target="_blank" rel="noopener" class="mycode_url">MISRA AC SLSF:2023 hardcopy</a>]]></description>
			<content:encoded><![CDATA[We are pleased to announce a new version of MISRA AC GMG has been released.<br />
<br />
The MISRA Autocode (AC) family of documents deals with the application of language subsets for automatic code generation purposes. This document, MISRA AC SLSF, contains the best practices, captured as a set of design and style guidelines, for the use of The Mathworks® Simulink® and Stateflow® tools for producing models that will be used for simulation and automatic code generation. Updated in June 2023, this second edition is the current version of MISRA AC SLSF. This document supersedes the first edition (published in 2009).<br />
<br />
The MISRA webstore provides single-user PDFs and you can purchase a hardcopy via a "print on demand" service at the following link. Please be sure to select the most appropriate “marketplace” for your location to expedite delivery. <a href="https://www.amazon.co.uk/dp/1911700065" target="_blank" rel="noopener" class="mycode_url">MISRA AC SLSF:2023 hardcopy</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Signal naming convention in MISRA guidelines]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1523</link>
			<pubDate>Tue, 21 Jan 2020 09:31:38 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=5395">ikostas_arrival</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1523</guid>
			<description><![CDATA[Hi,<br />
<br />
That is my first message on this bulletin, so I am not sure whether this is the right place for my question. If not please direct me to the right thread.<br />
<br />
I work in the automotive sector and more specifically in safety critical automotive control design with Simulink etc. So far in my team, we haven't started using an established signal name convention in Simulink that complies with a standard like MISRA. My question is, do you know if there is any of the MISRA documents that provides signal name convention for automotive systems?<br />
<br />
In Autosar there is such a keyword list as you can see in the end of this document <a href="https://www.autosar.org/fileadmin/user_upload/standards/classic/3-0/AUTOSAR_SWC_System_Modeling.pdf" target="_blank" rel="noopener" class="mycode_url">https://www.autosar.org/fileadmin/user_u...deling.pdf</a> <br />
<br />
For example if I want to name a signal with the name vehicle longitudinal velocity. Should it be vhllongvel or vehlngvl or vehllongvel etc. You get the picture.<br />
<br />
thanks in advance,<br />
<br />
ILIAS]]></description>
			<content:encoded><![CDATA[Hi,<br />
<br />
That is my first message on this bulletin, so I am not sure whether this is the right place for my question. If not please direct me to the right thread.<br />
<br />
I work in the automotive sector and more specifically in safety critical automotive control design with Simulink etc. So far in my team, we haven't started using an established signal name convention in Simulink that complies with a standard like MISRA. My question is, do you know if there is any of the MISRA documents that provides signal name convention for automotive systems?<br />
<br />
In Autosar there is such a keyword list as you can see in the end of this document <a href="https://www.autosar.org/fileadmin/user_upload/standards/classic/3-0/AUTOSAR_SWC_System_Modeling.pdf" target="_blank" rel="noopener" class="mycode_url">https://www.autosar.org/fileadmin/user_u...deling.pdf</a> <br />
<br />
For example if I want to name a signal with the name vehicle longitudinal velocity. Should it be vhllongvel or vehlngvl or vehllongvel etc. You get the picture.<br />
<br />
thanks in advance,<br />
<br />
ILIAS]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[News on future releases]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1406</link>
			<pubDate>Thu, 15 Mar 2018 14:32:32 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=4993">pdrudi</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1406</guid>
			<description><![CDATA[Hi,<br />
will MISRA AC SLSF guideline be updated?<br />
If yes, is there a planned release date?<br />
<br />
Thank you in advance,<br />
Paolo Drudi]]></description>
			<content:encoded><![CDATA[Hi,<br />
will MISRA AC SLSF guideline be updated?<br />
If yes, is there a planned release date?<br />
<br />
Thank you in advance,<br />
Paolo Drudi]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[model information blocks in virtual subsystems (rule 022)]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1404</link>
			<pubDate>Tue, 06 Mar 2018 18:55:34 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=3833">ben.call</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1404</guid>
			<description><![CDATA[MISRA AC SLSF 022 states that a model information block is required for every subsystem. Does application of this rule include virtual subsystems, or only "true" (i.e., atomic or nonvirtual) subsystems?<br />
Stated differently: Virtual subsystems should share the identity and origin of the parent model, atomic subsystem, or library to which they belong (the rationale for rule 022), so do they need that information reiterated in their own model information block?<br />
I would appreciate knowing what the community consensus is on this topic.<br />
~Ben]]></description>
			<content:encoded><![CDATA[MISRA AC SLSF 022 states that a model information block is required for every subsystem. Does application of this rule include virtual subsystems, or only "true" (i.e., atomic or nonvirtual) subsystems?<br />
Stated differently: Virtual subsystems should share the identity and origin of the parent model, atomic subsystem, or library to which they belong (the rationale for rule 022), so do they need that information reiterated in their own model information block?<br />
I would appreciate knowing what the community consensus is on this topic.<br />
~Ben]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Meaning of MISRA AC SLSF 045B (par. 3.6.11)]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1103</link>
			<pubDate>Fri, 29 Aug 2014 15:08:37 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=3493">neffnan</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1103</guid>
			<description><![CDATA[I can't make sense of the wording of 045B.  I think there may be a copy-&amp;-paste problem--the English seems garbled--but I'm not sure enough of my understanding of Stateflow yet to figure out what the 'correct' and 'incorrect' examples are meant to convey, so I'm not comfortable assuming how the rule should read. Could someone perhaps explain this rule for me or tell me how the rule should read?  Thanks.]]></description>
			<content:encoded><![CDATA[I can't make sense of the wording of 045B.  I think there may be a copy-&amp;-paste problem--the English seems garbled--but I'm not sure enough of my understanding of Stateflow yet to figure out what the 'correct' and 'incorrect' examples are meant to convey, so I'm not comfortable assuming how the rule should read. Could someone perhaps explain this rule for me or tell me how the rule should read?  Thanks.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[action language expression]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1065</link>
			<pubDate>Thu, 12 Jun 2014 17:22:02 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=918">ggentile</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1065</guid>
			<description><![CDATA[Why in SLSF there are no role to garantee that expression in acgtion and condition are written in such a way the C code is portable from 32 and 16 bit microcontroller ?<br />
<br />
GG]]></description>
			<content:encoded><![CDATA[Why in SLSF there are no role to garantee that expression in acgtion and condition are written in such a way the C code is portable from 32 and 16 bit microcontroller ?<br />
<br />
GG]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Status of MISRA AC documents March 2014]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=1035</link>
			<pubDate>Tue, 11 Mar 2014 12:03:57 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=4">david ward</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=1035</guid>
			<description><![CDATA[The MISRA Autocode (AC) suite of documents will be undergoing a refresh in the near future to bring them up to date and align them with the new MISRA branding and other MISRA documents. MISRA AC GMG and MISRA AC SLSF will be reviewed and updated.<br />
<br />
Based on the experience of MISRA AC contributors in using the current documents, the number and organization of documents is also up for consideration.  In particular, it is believed that the code generation specific layer of guideline documents, where MISRA AC TL sits and where a MISRA AC EC offering could sit, is better supported by tool vendors themselves; the frequency of updates to auto-code generation tools has proved too high for a user-based body such as MISRA to keep track of, and it is in the interest of the tool vendors to provide guidelines directly to support their customers in meeting their respective industry software development standards.<br />
<br />
MISRA AC TL is now seven years old and far removed from the current version of the tool offered by its vendor.  This document will be deprecated and no longer supported by MISRA from 1 June 2014.<br />
<br />
MISRA AC AGC will remain available and supported for legacy users of MISRA C:2004.  It should be noted that the current version MISRA C:2012 integrates requirement for automatically-generated C code.]]></description>
			<content:encoded><![CDATA[The MISRA Autocode (AC) suite of documents will be undergoing a refresh in the near future to bring them up to date and align them with the new MISRA branding and other MISRA documents. MISRA AC GMG and MISRA AC SLSF will be reviewed and updated.<br />
<br />
Based on the experience of MISRA AC contributors in using the current documents, the number and organization of documents is also up for consideration.  In particular, it is believed that the code generation specific layer of guideline documents, where MISRA AC TL sits and where a MISRA AC EC offering could sit, is better supported by tool vendors themselves; the frequency of updates to auto-code generation tools has proved too high for a user-based body such as MISRA to keep track of, and it is in the interest of the tool vendors to provide guidelines directly to support their customers in meeting their respective industry software development standards.<br />
<br />
MISRA AC TL is now seven years old and far removed from the current version of the tool offered by its vendor.  This document will be deprecated and no longer supported by MISRA from 1 June 2014.<br />
<br />
MISRA AC AGC will remain available and supported for legacy users of MISRA C:2004.  It should be noted that the current version MISRA C:2012 integrates requirement for automatically-generated C code.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[meaning of 045G MISRA AC SLSF]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=896</link>
			<pubDate>Tue, 08 May 2012 07:25:59 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=1941">stefania.botta</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=896</guid>
			<description><![CDATA[Hi,<br />
<br />
I write you, because I can not understand the meaning of 045G MISRA AC SLSF. The doubt is this: the rule want there are no variables written when transitioning between any states, in any case (I think it is very strong as assertion). Or the rule is specific when you are using condition-action and transition-action (deviation from 043A MISRA AC SLSF) when transitioning between any states. Or is there another meaning for understanding this rule?<br />
Could you give me more details about this rule?<br />
<br />
Kind regards,<br />
Stefania Botta.]]></description>
			<content:encoded><![CDATA[Hi,<br />
<br />
I write you, because I can not understand the meaning of 045G MISRA AC SLSF. The doubt is this: the rule want there are no variables written when transitioning between any states, in any case (I think it is very strong as assertion). Or the rule is specific when you are using condition-action and transition-action (deviation from 043A MISRA AC SLSF) when transitioning between any states. Or is there another meaning for understanding this rule?<br />
Could you give me more details about this rule?<br />
<br />
Kind regards,<br />
Stefania Botta.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[regarding 38b and 48a]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=886</link>
			<pubDate>Fri, 02 Mar 2012 15:26:53 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=1941">stefania.botta</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=886</guid>
			<description><![CDATA[Hi,<br />
<br />
I have some doubt about the use in stateflow of matlab functions as min or max. The tools for autocoding haven't limitation to use in this way these matlab functions.<br />
<br />
So, why it is wrong to use these functions in stateflow?<br />
<br />
Thanks a lot,<br />
Stefania Botta.]]></description>
			<content:encoded><![CDATA[Hi,<br />
<br />
I have some doubt about the use in stateflow of matlab functions as min or max. The tools for autocoding haven't limitation to use in this way these matlab functions.<br />
<br />
So, why it is wrong to use these functions in stateflow?<br />
<br />
Thanks a lot,<br />
Stefania Botta.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[MISRA AC EC guidelines]]></title>
			<link>https://forum.misra.org.uk/showthread.php?tid=848</link>
			<pubDate>Fri, 16 Sep 2011 13:50:27 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.misra.org.uk/member.php?action=profile&uid=1749">alexandru.mihal</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.misra.org.uk/showthread.php?tid=848</guid>
			<description><![CDATA[Hello,<br />
Can you tell me if the document MISRA AC EC is available? I saw in the MISRA AC INT a picture in which this document is present.<br />
<br />
Thanks,<br />
Alexandru Mihal]]></description>
			<content:encoded><![CDATA[Hello,<br />
Can you tell me if the document MISRA AC EC is available? I saw in the MISRA AC INT a picture in which this document is present.<br />
<br />
Thanks,<br />
Alexandru Mihal]]></content:encoded>
		</item>
	</channel>
</rss>