agentgen handling of AUGMENTS clause

[Frank Fock]

Alex,

The ilen bug will be fixed in the next update of AgentGen Pro.
Thanks for reporting it!

Best regards,
Frank

Alex Finogenov wrote:

> Frank,
>
> You are right. In the paragraph 7.8 SMIv2 indeed says that "AUGMENTS clause
> names the object corresponding to the base conceptual row".
>
> Since we are discussing the AUGMENTS clause, I also noticed that agentgen
> generated the ilen value of 1 (the last argument to table entry's
> constructor in .cpp files) when, according to my understanding of the
> agentgen, it should have generated a larger value reflecting the number of
> indexes for the tables and the size of the index_info array. At the same
> time it generated the index_info arrays of the correct sizes and with the
> correct number of entries in each case.
>
> All of the entries in question contain AUGMENTS clause that refers to a base
> entry that contains a few INDEX entries. In every case one of the INDEX
> entries is local to the table and the rest are not local to it, i.e. either
> imported from other modules or are defined in other tables of the same
> module. For example, when an entry AUGMENTS a base entry with  one INDEX
> defined in that table, two INDEXes imported from two different modules, and
> one INDEX defined in the considered module in some other table, the agentgen
> generated the ilen value of 1, index_info array of size 4 that contained 4
> entries.