+3Nice warning in UnifAce 10 :-)
[ 1] variables
[ 2] string DE0110_ALT
Note DCLC, which is the declaration trigger for component locale variables.
UnifAce seems to be a little overcautious here, as this variable can only be used with the syntax $ENTITY$.
+1Nice warning in UnifAce 10 :-)
[ 1] variables
[ 2] string DE0110_ALT
Note DCLC, which is the declaration trigger for component locale variables.
UnifAce seems to be a little overcautious here, as this variable can only be used with the syntax $ENTITY$.
Hi Inigo,
I encountered this a while ago, and logged it, (Case 00942890). I got this back.
We've been able to reproduce and the lab has also analyzed the behavior.
At this point it appears that the warnings are a side effect of previous kernel changes, which need to be corrected.
That means that for the moment there are two options; You can safely ignore this particular warning and carry on using this patch but with annoying compile warnings or revert to your previous working version 10.4.2.37.
We'll work to revert the change on the short notice for which I've created the appropriate paperwork to have this added to the backlog, so I expect more information on possible solution and timeline later this week.
Please note that I did get some signals from the lab that entity *might* be added to the compiler warning/error list in the not too distant future as 'entity' is technically a datatype, so perhaps good to keep that in mind.
I did a full source dump, and a global search and replace for $entity$ and "string entity", and a recompile. There may have been a couple of compile failures where the declaration did not match the search/replace pattern, but it was relatively painless to remove.
Regards,
Iain
+1Hi Inigo,
I encountered this a while ago, and logged it, (Case 00942890). I got this back.
We've been able to reproduce and the lab has also analyzed the behavior.
At this point it appears that the warnings are a side effect of previous kernel changes, which need to be corrected.
That means that for the moment there are two options; You can safely ignore this particular warning and carry on using this patch but with annoying compile warnings or revert to your previous working version 10.4.2.37.
We'll work to revert the change on the short notice for which I've created the appropriate paperwork to have this added to the backlog, so I expect more information on possible solution and timeline later this week.
Please note that I did get some signals from the lab that entity *might* be added to the compiler warning/error list in the not too distant future as 'entity' is technically a datatype, so perhaps good to keep that in mind.
I did a full source dump, and a global search and replace for $entity$ and "string entity", and a recompile. There may have been a couple of compile failures where the declaration did not match the search/replace pattern, but it was relatively painless to remove.
Regards,
Iain
That was back in February, so assuming you're on a later patch, they haven't gotten to it yet.
+3That was back in February, so assuming you're on a later patch, they haven't gotten to it yet.
Hi Iain
I did install 10.4.3.23 last week so: No it's not yet solved :-)
However, since it is only a warning and does no harm, we will probably leave it as it is.
Ingo
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
