note 126868 deleted from language.oop5.constants by cmb

Note Submitter: Patanjali ---- To the commenter who wrote: 'Also I don't understand which are the advantages of modifying the class scope of a constant because constant couldn't be change at runtime.' Any public member of a class invites users of that class to create dependencies on it in their code. If a class constant -- or any member -- is only required internally to that class, then external dependencies on it need to be prevented by using using the 'private' modifier, because a class creator doesn't want to be constrained by the past if they don't need to, especially if the constant value might change with class version. This is part of the encapsulation purpose for classes. Otherwise, a public class constant is a effectively a public constant name-spaced by the class name, which may be useful for grouping related constants which are only available if the class file is included.