-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add proposal for protected attribute in derived types #31
Conversation
@aradi, thanks for submitting this. I have a few questions. Wouldn't your example work with current Fortran already? I would like to see an example which does not work with current Fortran, and shows how the "protected" attribute improves things. |
Ah I see --- it's something like |
I added some more explanation. The case presented would be only possible, if the component were made |
Yes, it was meant like |
I've wanted this for a long time. Writing a ton of getter methods is a pain in the ass and a waste of time. An attribute that would only allow modification by TBPs would be really nice, and would allow for direct reading of UDT components. |
@aradi I did not forget about this PR --- I first want to figure out a workflow with the committee how to consider proposals such as this one. Things will start moving in the next few weeks. |
All fine, thanks in advance and especially thanks for all your efforts into involving the community! |
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.
This is something I frequently wish we had in Fortran. I'd like to submit this proposal for the meeting next week, and I think it's in pretty good shape. There hasn't been much discussion--is there anything we should iron out first?
@zjibben Thanks! I think, the proposal is trivial enough not to have side effects or unwanted implications, this is why there was not much discussion about it. |
Thanks for this proposal. It is something I tried intuitively once (without success of course ;) ), before reading one more time the documentation of |
I assigned to @zjibben to merge when he thinks it's ready. |
I went ahead and merged. I agree, I think this is straightforward enough to not need more clarification, but if anyone thinks of something please leave a comment or submit a PR! I’ll submit this weekend otherwise. Thanks for the proposal @aradi ! |
No description provided.