2009/10/8 Malcolm J. Currie <[log in to unmask]>:
>>> What could work though, is if kpg1_grgrp was to store the concatenated
>>> list of elements using a different parameter. So if kpg1_gtgrp is
>>> called to get a value for parameter "CONFIG" (for instance), it could
>>> store the list of group elements as the current value for parameter
>>> "CONFIG_V". It would need to create an IFL entry for each such "_V"
>>> parameter. Presumably it could call PARSECON_NEWPAR to do this, like
>>> you did for MSG_FILTER etc. When the NDF is closed, the NDF library
>>> would store values for both CONFIG and CONFIG_V in the history record.
>
> Will the default HISTORY-record buffer accommodate the expected long
> command-line strings, or is there no limit?
>
> How big are the parameter-system buffers these days? There used to be a
> document that included their values such as parameter-system maximum
> character length. Browsing documentation and include files I couldn't find
> that statistic.
>
> I'm wondering for verbose lists (say a list of filenames including long
> paths) whether the current limits will be adequate for the new _V
> parameter, and hence whether or not an array is needed.
It will all no doubt come out in the wash.
David
|