| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Fixes for yacc code in Base?! |
| From: | Michael Davidsaver via Core-talk <core-talk at aps.anl.gov> |
| To: | Ralph Lange <ralph.lange at gmx.de> |
| Cc: | EPICS Core Talk <core-talk at aps.anl.gov> |
| Date: | Thu, 25 May 2023 13:53:01 -0700 |
On 5/25/23 08:42, Ralph Lange via Core-talk wrote:
Recently activated new rules in our ITER software QA system have me go through EPICS modules once again, trying to make them pass quality gates. Is it worth fixing smallish things in the yacc sources inside libCom, or should I just tag them as 'won't fix' in our static analysis application? I'm happy to provide pull requests, but only if they have a chance to be approved.
In the past I know that I have pushed against spending time on this antique code. On the other hand, the most recent change to yacc/ was me quieting a UBSan warning. Which I suspect is the kind of issue your QA tools will flag. So I guess I can't honestly object to your making similar "non-functional" changes.