When using module variables as input variables, is there a way to specify intent(in) property as we do for a...
To remind me that a variable from a module used in a subroutine is an input rather than an output, I usually add comments to indicate this, which provides nothing to compilers.
module fortran
asked Nov 13 '18 at 23:43
Youjun HuYoujun Hu
538
add a comment |
To remind me that a variable from a module used in a subroutine is an input rather than an output, I usually add comments to indicate this, which provides nothing to compilers.
module fortran
asked Nov 13 '18 at 23:43
Youjun HuYoujun Hu
538
4
Maybe use "protected"? (like "val" in this page ibm.com/support/knowledgecenter/SSGH4D_14.1.0/…) (but this may be not helpful when viewed from the caller side, as compared to intent(in))
– roygvib
Nov 14 '18 at 1:03
add a comment |
To remind me that a variable from a module used in a subroutine is an input rather than an output, I usually add comments to indicate this, which provides nothing to compilers.
module fortran
asked Nov 13 '18 at 23:43
Youjun HuYoujun Hu
538
To remind me that a variable from a module used in a subroutine is an input rather than an output, I usually add comments to indicate this, which provides nothing to compilers.
module fortran
module fortran
asked Nov 13 '18 at 23:43
Youjun HuYoujun Hu
538
asked Nov 13 '18 at 23:43
Youjun HuYoujun Hu
538
edited Nov 14 '18 at 5:44
Youjun Hu
asked Nov 13 '18 at 23:43
Youjun HuYoujun Hu
538
asked Nov 13 '18 at 23:43
Youjun HuYoujun Hu
538
asked Nov 13 '18 at 23:43
Youjun HuYoujun Hu
538
538
4
Maybe use "protected"? (like "val" in this page ibm.com/support/knowledgecenter/SSGH4D_14.1.0/…) (but this may be not helpful when viewed from the caller side, as compared to intent(in))
– roygvib
Nov 14 '18 at 1:03
add a comment |
4
Maybe use "protected"? (like "val" in this page ibm.com/support/knowledgecenter/SSGH4D_14.1.0/…) (but this may be not helpful when viewed from the caller side, as compared to intent(in))
– roygvib
Nov 14 '18 at 1:03
4
4
Maybe use "protected"? (like "val" in this page ibm.com/support/knowledgecenter/SSGH4D_14.1.0/…) (but this may be not helpful when viewed from the caller side, as compared to intent(in))
– roygvib
Nov 14 '18 at 1:03
Maybe use "protected"? (like "val" in this page ibm.com/support/knowledgecenter/SSGH4D_14.1.0/…) (but this may be not helpful when viewed from the caller side, as compared to intent(in))
– roygvib
Nov 14 '18 at 1:03
add a comment |
1 Answer
1
active
oldest
votes
There is no such thing in Fortran that would import a module variable as a constant. As roygvib mentioned, you can declare a variable protected inside the module to make it read only for all other modules. But you cannot import a non-protected variable as read-only in Fortran.
I recommend not to treat module variables, which are really just better global variables, as input or output. If something is clearly an input or output of your subroutine, make it an argument explicitly and call it in such a way that is clear what you are doing - with the global variable as an actual argument.
answered Nov 14 '18 at 9:10
Vladimir FVladimir F
40.3k44071
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53291101%2fwhen-using-module-variables-as-input-variables-is-there-a-way-to-specify-intent%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is no such thing in Fortran that would import a module variable as a constant. As roygvib mentioned, you can declare a variable protected inside the module to make it read only for all other modules. But you cannot import a non-protected variable as read-only in Fortran.
I recommend not to treat module variables, which are really just better global variables, as input or output. If something is clearly an input or output of your subroutine, make it an argument explicitly and call it in such a way that is clear what you are doing - with the global variable as an actual argument.
answered Nov 14 '18 at 9:10
Vladimir FVladimir F
40.3k44071
add a comment |
There is no such thing in Fortran that would import a module variable as a constant. As roygvib mentioned, you can declare a variable protected inside the module to make it read only for all other modules. But you cannot import a non-protected variable as read-only in Fortran.
I recommend not to treat module variables, which are really just better global variables, as input or output. If something is clearly an input or output of your subroutine, make it an argument explicitly and call it in such a way that is clear what you are doing - with the global variable as an actual argument.
answered Nov 14 '18 at 9:10
Vladimir FVladimir F
40.3k44071
add a comment |
There is no such thing in Fortran that would import a module variable as a constant. As roygvib mentioned, you can declare a variable protected inside the module to make it read only for all other modules. But you cannot import a non-protected variable as read-only in Fortran.
I recommend not to treat module variables, which are really just better global variables, as input or output. If something is clearly an input or output of your subroutine, make it an argument explicitly and call it in such a way that is clear what you are doing - with the global variable as an actual argument.
answered Nov 14 '18 at 9:10
Vladimir FVladimir F
40.3k44071
There is no such thing in Fortran that would import a module variable as a constant. As roygvib mentioned, you can declare a variable protected inside the module to make it read only for all other modules. But you cannot import a non-protected variable as read-only in Fortran.
I recommend not to treat module variables, which are really just better global variables, as input or output. If something is clearly an input or output of your subroutine, make it an argument explicitly and call it in such a way that is clear what you are doing - with the global variable as an actual argument.
answered Nov 14 '18 at 9:10
Vladimir FVladimir F
40.3k44071
answered Nov 14 '18 at 9:10
Vladimir FVladimir F
40.3k44071
answered Nov 14 '18 at 9:10
Vladimir FVladimir F
40.3k44071
answered Nov 14 '18 at 9:10
Vladimir FVladimir F
40.3k44071
40.3k44071
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53291101%2fwhen-using-module-variables-as-input-variables-is-there-a-way-to-specify-intent%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
4
Maybe use "protected"? (like "val" in this page ibm.com/support/knowledgecenter/SSGH4D_14.1.0/…) (but this may be not helpful when viewed from the caller side, as compared to intent(in))
– roygvib
Nov 14 '18 at 1:03