Experimental Physics and
| |||||||||||||||||
|
No I don't actually see an error at the moment and things work. I really wanted to make sure I understood any limitations of this sort that exist and would limit the combined length of the DEVICE and port strings in my case. You seem to be saying that the INP string needs to be less than 80 characters. Would that be before or after macro expansion? For now I don't think either cause me a problem with a limit of 80. Regards Steve ----- Original Message ----- From: "Davidsaver, Michael" <[email protected]> To: "Andrew Johnson" <[email protected]>; "Steve Kinder" <[email protected]> Cc: <[email protected]> Sent: Monday, March 15, 2010 4:29 PM Subject: RE: INP field length Steve, One of the limitations on the length of INP or OUT is dbPutString in dbStaticLib.c (search for 'string[80]'). When you reach this limit you will see the message "dbPutString received a string that is too long". Do you see this? Michael my-----Original Message----- From: [email protected] [mailto:tech-talk- [email protected]] On Behalf Of Andrew Johnson Sent: Monday, March 15, 2010 12:12 PM To: Steve Kinder Cc: [email protected] Subject: Re: INP field length > specific case. I'm using StreamDevice2 and have a INP field as follows with > template/substitution. > > field(INP, "@TEST.protocol getCs($(DEVICE),C2,C3,C4) $(port) 0") > > If I understand things correctly, whatever the length of DEVICE and port I > shouldn't encounter problems. Well due to the length of the field at least.
| ||||||||||||||||
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |