-
Notifications
You must be signed in to change notification settings - Fork 2
RFC: Visibility #19
Comments
Method VisibilityWorking proposalNote: scope and visibility are synonymous in this instance Variables, structs, enum, and type definitions placed inside of methods should only have an accessible scope/visibility from inside the enclosing method. Methods in the same file have visibility to all other methods inside the enclosing file. Structs, vars, enums, and type definitions placed inside the enclosing file's scope can be accessed from other files, methods, enums, and structs.
Public/Protected/Private VisibilityA note on visibility: private until made public by pub. Don't think protected-type visibility will be necessary. Haven't decided yet. - Qix- PublicPublic is defined as accessible and/or modifiable from all scopes. ProtectedProtected is defined as accessible only the current item or sub-elements (extended or implemented) PrivatePrivate is defined as accessible only from the current scope [or file] or friend elements Examples:
|
A note on visibility: private until made public by |
Looks okay for the moment @PolyGN. I think |
@Qix- sweet!
Preprocessor commands and macros not going to be implemented |
Thought on
Note! Or maybe we use symbol implementations... I'm against this in my opinion as symbolic parsing of visibility could prove to be troublesome. |
TODOBoth method visibility as well as unit visibilityThe text was updated successfully, but these errors were encountered: