On 04/08/2015 07:44 AM, Ralph Lange wrote:
> On 08/04/2015 14:13, Michael Davidsaver wrote:
>> On 04/08/2015 08:02 AM, Ralph Lange wrote:
>>> ...
>>> So - what to do with 3.15?
>>> (I'm afraid waiting for 3.16 is not short-term enough.)
>>>
>>> I would opt for the simple version: make the buffer statically length
>>> 256.
>> Or malloc() for a temporary buffer when the static buffer is too short?
>
> I'd rather waste 180 bytes on the stack (no performance impact) than
> doing a malloc()/free() for every long INP/OUT instance on the IOC.
Agreed, just wind the stack buffer length up to 256 for now.
- Andrew
--
Light thinks it travels faster than anything but it is wrong.
No matter how fast light travels, it finds the darkness has
always got there first, and is waiting for it.
-- Terry Pratchett, Reaper Man
- References:
- Raising the 80 char limit on INP/OUT strings? Ralph Lange
- Re: Raising the 80 char limit on INP/OUT strings? Ralph Lange
- Re: Raising the 80 char limit on INP/OUT strings? Michael Davidsaver
- Re: Raising the 80 char limit on INP/OUT strings? Ralph Lange
- Navigate by Date:
- Prev:
Re: Raising the 80 char limit on INP/OUT strings? Ralph Lange
- Next:
Build failed in Jenkins: epics-base-3.15-win64s #147 APS Jenkins
- 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: Raising the 80 char limit on INP/OUT strings? Ralph Lange
- Next:
Re: dbd question Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
|