-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
changes made in response to Richard's first set of comments #1145
Conversation
Ada, just as the use of the *public*, *private*, and *protected* parts of | ||
classes is fundamental to creating abstractions in class-oriented | ||
languages. Not every type can be private, as illustrated by the client | ||
expectation for array indexing in Ada prior to Ada 2012. Not every type |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding "prior to Ada 2012" here makes the uninformed reader wonder why is it now different in Ada 2012... Maybe we should come up with better examples of the necessity of non-private types.
Now, here's the rub. | ||
|
||
Constructor functions require that same compile-time visibility so the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now, here's the rub. | |
Constructor functions require that same compile-time visibility so the | |
Now, here's the problem: | |
constructor functions require that same compile-time visibility so the |
Improving comparison with the original version.
Improving comparison with the original version.
No description provided.