| 1994 1995 1996 1997 1998 1999 2000 2001 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 | 1994 1995 1996 1997 1998 1999 2000 2001 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: a question for msi |
| From: | Bruce Hill <[email protected]> |
| To: | <[email protected]> |
| Date: | Tue, 31 Jul 2018 17:04:26 -0700 |
I'd be in favor of removing them unless the -V flag was set. Most of our msi use is intended to be loaded w/ macro definitions in our st.cmd file, so it's just annoying to see ",undefined" in files we've built up from templates when we know we'll define those macros later. We set the -V flag only for those few msi uses where the files need to have all macros expanded. For those cases it would still be helpful to see the ",undefined" or ",recursive" warning text in the msi output file as we do now. Cheers, - Bruce On 07/31/2018 02:57 PM, Andrew Johnson wrote:
If there is a consensus that they are not useful I have a modification that removes the ",undefined" error indicator from the output generated by macLib (and hence the output from msi as long as the -V flag is used) when it encounters a $(macro) that it doesn't have a value for. There is also a ",recursive" marker for macros that are defined in a substitution file using themselves. As Bruce said, these markers don't change how a file is interpreted by an IOC when they are present, but if you feed the output into some other tool that doesn't understand them they might be annoying. Please discuss here if you particularly like or dislike these markers. - Andrew On 07/30/2018 04:23 PM, Jeong Han Lee wrote:Hi, Is there any other way to suppress or omit (,undefined) in the output file by using MSI? Thanks, Han
-- Bruce Hill Member Technical Staff SLAC National Accelerator Lab 2575 Sand Hill Road M/S 10 Menlo Park, CA 94025