Re: Overwritte Class Variables | ExitApp, __Delete & Static Variables
Posted: 14 May 2019, 20:43
I will probably do this, or make #Warn ClassOverwrite the default, or make it mandatory behaviour, to be reimplemented later as constants.
Objects may have the provision for read-only value properties, which will make it easy for nested classes.I wrote:I might consider making class names read-only identifiers (not variable) in v2. It would not reduce flexibility much since one can still clone the class and modify the original object as needed. However, the current framework has no provision for constants, [...]. Also, consider the fact that nested classes are (in current versions of the language) simply assigned to array elements, and a constant array element doesn't make much sense.