Experimental Physics and
Industrial Control System
| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Raising the 80 char limit on INP/OUT strings? |
| From: | Ralph Lange <[email protected]> |
| To: | EPICS Core-Talk <[email protected]> |
| Date: | Wed, 08 Apr 2015 10:46:11 +0200 |
|
Dear all, I have a request to raise the current limit of 80 chars on INP/OUT fields. Some device supports (e.g. OPC, SNMP) use device-side names in that field to map signals, and names in those systems might be long. Internally, these strings are stored in their natural length - it is just the code in dbPutString() (dbStaticLib.c 2029ff.) that sets and enforces the limit. However, having a limit makes sense to detect runaway strings (missing quotes etc.) I see two easy feasible options: 1. Statically raise the limit (e.g. to 256). 2. Add an IOC variable, make the buffer static, and alloc it once (in the function). What do you think? Cheers, ~Ralph |
- Replies:
- Re: Raising the 80 char limit on INP/OUT strings? Ralph Lange
- Navigate by Date:
- Prev: Re: include valgrind.h in Base? Michael Davidsaver
- Next: Re: Raising the 80 char limit on INP/OUT strings? Ralph Lange
- Index: 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024
- Navigate by Thread:
- Prev: Re: include valgrind.h in Base? Michael Davidsaver
- Next: Re: Raising the 80 char limit on INP/OUT strings? Ralph Lange
- Index: 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·