I'm not sure which issue you are referring to.
For the first one, the problem I have is that the use of sequential
task (or any task with subtasks) means the preprocessor forgets the
index of the subtask and thus always generates dynamic values that
match only the first task. Maybe my description in the issue is not
clear enough.
For the second one, it matches the $[] construct, but when it
generates the dynamic values, it starts their indexing at 1 instead of
0. For instance, let's say I have this:
<DumpValue>
<xmlFileName>somefile.xml</xmlFileName>
<values>
<namedValue name="MyFirstValue" value="$[Something]" />
<namedValue name="MySecondValue" value="$[SomeOtherThing]" />
</values>
</DumpValue>
Then I get a crash at runtime (index out of bounds) and if I look at
the "processed" tab in CCValidator, I get generated dynamic values for
values[1].value and values[2].value instead of 0 and 1
Do not hesitate to ask if you need more details
Regards
Olivier
On 29 sep, 16:18, Jeremy Lew <[email protected]> wrote:
> Are you saying that the preprocessor matches $[xxx] and converts it to
> an empty string? The preprocessor uses a regular expression to match
> symbol references, which doesn't include square brackets, so I'm not
> sure how it would. I'll try it out in 1.6 though.
>
> On Sep 29, 4:10 am, OBones <[email protected]> wrote:
>
> > On 28 sep, 17:25, Jeremy Lew <[email protected]> wrote:
>
> > > I wrote nearly all of the preprocessor code, which explains my
> > > familiarity with its nasty failure modes ;)
>
> > Sorry to barge in like that, but if you're going to look at the
> > preprocessor, could you look at the issues I had with it?
>
> > They are in CCNET-1956 and CCNET-1943 (my third comment on that issue)
>
> > Thanks
> > Olivier
