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.
- References:
- Fixes for yacc code in Base?! Ralph Lange via Core-talk
- Navigate by Date:
- Prev:
Fixes for yacc code in Base?! Ralph Lange via Core-talk
- Next:
Re: Fixes for yacc code in Base?! Andrew Johnson via Core-talk
- 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
- Navigate by Thread:
- Prev:
Fixes for yacc code in Base?! Ralph Lange via Core-talk
- Next:
Re: Fixes for yacc code in Base?! Andrew Johnson via Core-talk
- 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
|