Component setting parameter parsing

[g5t]

Not all setting parameter types supported by McCode are fully implemented or tested in mccode_antlr.

The list of types includes

• double
• int
• string
• vector
• symbol
• double *
• int *

Of which, at least symbol and int * are not implemented or not implemented correctly.
By utilizing the InMemoryRegistry a few contrived component unit tests should be able to exercise all of the supported types.

[g5t]

The only mention I can find of symbol in the set of McStas and McXtrace component files is in Monitor_Sqw.comp, which does not mention the parameter in its documentation and has an accompanying test instr file which does not set the parameter.
The component sets a symbol setting parameter to FLT_MAX then assigns that to a char [128] inside of a Monitor_nd struct.

The code generator sets symbol parameters to a literal '\0'
https://github.com/mccode-dev/McCode/blob/257a00817f23eaf4b3096ca41bcf60c4e976b4f0/mccode/src/cogen.c.in#L616-L618
then adds a comment in the trace section
https://github.com/mccode-dev/McCode/blob/257a00817f23eaf4b3096ca41bcf60c4e976b4f0/mccode/src/cogen.c.in#L858-L863

@willend Could you help me understand the symbol type? Maybe over coffee?

[willend]

@g5t yes and yes. ☕ (As usual I will probably need to 1. look through the code base before and 2. talk to you as I think my way through it... :-) )