U9 "secure code" pattern conflicts with new inheritance
Author: email@example.com (ulrich-merkel)
as announced in http://unifaceinfo.com/uniface-10-code-containers-code-inheritance-and-default-behavior/ Changing the rules of the game for inheritance and code overwriting will cause sever desaster for existing applications and utilities implementing "secure codes". Each modeled entity has a last hidden nondb field "for secure code" where all the must-not-be-modified entries are implemented. Because of the sequence of objects in the compile, even adding the same entry in the LPMX or LPME in the form would not change this code. Transfering this to U10 (I just tested it with a small demo) will sabotage this protection pattern: now the local modified code will supersede the coded on always. Perhaps some Preferences like "$U9_CODE_INHERITANCE" would help in this case.