<div dir="ltr"><div>Jay,</div><div><br></div><div>I'd be interested in hearing more about this. I haven't been on the tangerine calls (I'm usually on the HamSCI ones), though I'm planning to start joining if I have the time.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 12, 2020 at 10:35 PM Jay Schwartz <<a href="mailto:wb8sbi@gmail.com">wb8sbi@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Hello all,<div><br></div><div>Please allow me to introduce myself. I'm a retired automotive embedded software engineer, BSEE, BSCS, licensed since 1974, Extra Class, and Life Member of ARRL, AMSAT, and QCWA.</div><div><br></div><div>In the auto industry code reviews are mandatory, and misery unto those who do not do one. Part of this code review is to make sure the code complies with the Motor Industry Software Reliability Association (MISRA) standard. This is a coding standard that started in the auto industry and has gone worldwide in many other industries. The standard can be purchased for 10 British Pounds from <a href="https://www.misra.org.uk/Publications/tabid/57/Default.aspx" target="_blank">https://www.misra.org.uk/</a></div><div><br></div><div>Many software compilers have incorporated this standard into their tools. They will automatically check the source code at compile time and report any non-complicenses. I.e. your code compile and link, but may not run the way you think it will. By complying with this document you greatly reduce the chances of something undesirable happening.</div><div><br></div><div>This document is easy to comply with, and contains a lot of common sense do / do nots. By complying with it also makes your code more readable and better able to be updated. However, it is not friendly to spaghetti code.</div><div><br></div><div>If the code is written to comply with it then many preventable bugs can be avoided. I.e. it reduces the need to patch by not having the bug in the code to begin with.</div><div><br></div><div>I have a copy of the standard and would be happy to explain it to the group at the next regularly scheduled video meeting.</div><div><br></div><div>73, Jay</div><div>WB8SBI</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 12, 2020 at 6:00 PM Aidan Montare via TangerineSDR <<a href="mailto:tangerinesdr@lists.tapr.org" target="_blank">tangerinesdr@lists.tapr.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">For those not on the HamSCI mailing list:<br><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">Aidan Montare</b> <span dir="auto"><<a href="mailto:aam141@case.edu" target="_blank">aam141@case.edu</a>></span><br>Date: Wed, Aug 12, 2020 at 5:00 PM<br>Subject: Proposal: HamSCI Code Review<br>To: <<a href="mailto:hamsci@googlegroups.com" target="_blank">hamsci@googlegroups.com</a>><br></div><br><br><div dir="ltr"><div></div><div>Dear all,<br></div><div><br></div><div>I'd like to propose a regular code review session for the HamSCI community, and get your feedback on the idea.<br><br>If you are interested, please fill out the following short survey to help me pick a time to hold code review sessions:
<a href="https://forms.gle/uiEHCqMG9v1BaQiW7" target="_blank">https://forms.gle/uiEHCqMG9v1BaQiW7</a>. I think the schedule can be informal; I'd be happy to meet at different times on occasion to accommodate different people, etc.<br><br>I've also created a page at <a href="http://hamsci.org" target="_blank">hamsci.org</a> (<a href="https://hamsci.org/code-review" target="_blank">https://hamsci.org/code-review</a>) for the project with some general thoughts on how the sessions might run. If you have any ideas or suggestions, please let me know as well (either via email or the form linked above).<br><br>Best wishes,<br><br>Aidan KB3UMD<br></div></div>
</div><br clear="all"><br>-- <br><div dir="ltr"><div dir="ltr">Sincerely,<br><br>Aidan Montare<br>CWRU Class of 2021</div></div></div></div>
-- <br>
TangerineSDR mailing list<br>
<a href="mailto:TangerineSDR@lists.tapr.org" target="_blank">TangerineSDR@lists.tapr.org</a><br>
<a href="http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org</a><br>
</blockquote></div>
</div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Sincerely,<br><br>Aidan Montare<br>CWRU Class of 2021</div></div>