fopen return NULL when passing first parameter with “*” character
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
0
I have to use fopen() function to create file and write something.But when i pass first parameter using "*" character; fopen() returns NULL always.
Example:
FILE *fp
const std::string sympath ="c:\SysData/NonStandart/SUP*------*****.png"
fp = fopen(sympath.c_str(), "wb+");
fp returns NULL always.
I have to use "*" character. How can i fix this problem?
OS = windows 10 and Centos7
c++ null stream fopen
asked Nov 22 '18 at 16:32
cevapsızcagricevapsızcagri
35
add a comment |
0
I have to use fopen() function to create file and write something.But when i pass first parameter using "*" character; fopen() returns NULL always.
Example:
FILE *fp
const std::string sympath ="c:\SysData/NonStandart/SUP*------*****.png"
fp = fopen(sympath.c_str(), "wb+");
fp returns NULL always.
I have to use "*" character. How can i fix this problem?
OS = windows 10 and Centos7
c++ null stream fopen
asked Nov 22 '18 at 16:32
cevapsızcagricevapsızcagri
35
2
If your OS or file system forbids the character, there is nothing you can do.
– user2486888
Nov 22 '18 at 16:35
1
Do you try to use*as place-holder, or does your file name really contain these*s? This won't work in either case. There are no place-holders supported infopen(), and*is (at least on Windows) a reserved character which shouldn't be used in file names. (Naming Files, Paths, and Namespaces)
– Scheff
Nov 22 '18 at 16:37
@Scheff It is NATO joint standard symbology SID code. Hmm i suppose, i have to replace '*' character with something else.
– cevapsızcagri
Nov 22 '18 at 16:44
Do these military guys work with *ix systems exclusively? (In *ix systems/andare the only excluded characters - I just recalled.) I first thought you are joking but, out of curiosity, I googled and found NATO Joint Military Symbology with e.g.***Platoon, etc. Centos: that's a Linux - hence, the"c:\"probably won't work. On Windows,*is prohibited - how about replacing with'u2731'(the unicode point for✱)? (Most people will probably not realize the difference.) ;-)
– Scheff
Nov 22 '18 at 17:07
For Windows, see Naming Files, Paths, and Namespaces, and in particular Naming Conventions. Amongst several others, the*character is reserved and cannot be used in folder names or file names.
– Remy Lebeau
Nov 22 '18 at 22:27
add a comment |
0
0
0
I have to use fopen() function to create file and write something.But when i pass first parameter using "*" character; fopen() returns NULL always.
Example:
FILE *fp
const std::string sympath ="c:\SysData/NonStandart/SUP*------*****.png"
fp = fopen(sympath.c_str(), "wb+");
fp returns NULL always.
I have to use "*" character. How can i fix this problem?
OS = windows 10 and Centos7
c++ null stream fopen
asked Nov 22 '18 at 16:32
cevapsızcagricevapsızcagri
35
I have to use fopen() function to create file and write something.But when i pass first parameter using "*" character; fopen() returns NULL always.
Example:
FILE *fp
const std::string sympath ="c:\SysData/NonStandart/SUP*------*****.png"
fp = fopen(sympath.c_str(), "wb+");
fp returns NULL always.
I have to use "*" character. How can i fix this problem?
OS = windows 10 and Centos7
c++ null stream fopen
c++ null stream fopen
asked Nov 22 '18 at 16:32
cevapsızcagricevapsızcagri
35
asked Nov 22 '18 at 16:32
cevapsızcagricevapsızcagri
35
edited Nov 22 '18 at 16:40
cevapsızcagri
asked Nov 22 '18 at 16:32
cevapsızcagricevapsızcagri
35
asked Nov 22 '18 at 16:32
cevapsızcagricevapsızcagri
35
asked Nov 22 '18 at 16:32
cevapsızcagricevapsızcagri
35
35
2
If your OS or file system forbids the character, there is nothing you can do.
– user2486888
Nov 22 '18 at 16:35
1
Do you try to use*as place-holder, or does your file name really contain these*s? This won't work in either case. There are no place-holders supported infopen(), and*is (at least on Windows) a reserved character which shouldn't be used in file names. (Naming Files, Paths, and Namespaces)
– Scheff
Nov 22 '18 at 16:37
@Scheff It is NATO joint standard symbology SID code. Hmm i suppose, i have to replace '*' character with something else.
– cevapsızcagri
Nov 22 '18 at 16:44
Do these military guys work with *ix systems exclusively? (In *ix systems/andare the only excluded characters - I just recalled.) I first thought you are joking but, out of curiosity, I googled and found NATO Joint Military Symbology with e.g.***Platoon, etc. Centos: that's a Linux - hence, the"c:\"probably won't work. On Windows,*is prohibited - how about replacing with'u2731'(the unicode point for✱)? (Most people will probably not realize the difference.) ;-)
– Scheff
Nov 22 '18 at 17:07
For Windows, see Naming Files, Paths, and Namespaces, and in particular Naming Conventions. Amongst several others, the*character is reserved and cannot be used in folder names or file names.
– Remy Lebeau
Nov 22 '18 at 22:27
add a comment |
2
If your OS or file system forbids the character, there is nothing you can do.
– user2486888
Nov 22 '18 at 16:35
1
Do you try to use*as place-holder, or does your file name really contain these*s? This won't work in either case. There are no place-holders supported infopen(), and*is (at least on Windows) a reserved character which shouldn't be used in file names. (Naming Files, Paths, and Namespaces)
– Scheff
Nov 22 '18 at 16:37
@Scheff It is NATO joint standard symbology SID code. Hmm i suppose, i have to replace '*' character with something else.
– cevapsızcagri
Nov 22 '18 at 16:44
Do these military guys work with *ix systems exclusively? (In *ix systems/andare the only excluded characters - I just recalled.) I first thought you are joking but, out of curiosity, I googled and found NATO Joint Military Symbology with e.g.***Platoon, etc. Centos: that's a Linux - hence, the"c:\"probably won't work. On Windows,*is prohibited - how about replacing with'u2731'(the unicode point for✱)? (Most people will probably not realize the difference.) ;-)
– Scheff
Nov 22 '18 at 17:07
For Windows, see Naming Files, Paths, and Namespaces, and in particular Naming Conventions. Amongst several others, the*character is reserved and cannot be used in folder names or file names.
– Remy Lebeau
Nov 22 '18 at 22:27
2
2
If your OS or file system forbids the character, there is nothing you can do.
– user2486888
Nov 22 '18 at 16:35
If your OS or file system forbids the character, there is nothing you can do.
– user2486888
Nov 22 '18 at 16:35
1
1
Do you try to use
* as place-holder, or does your file name really contain these *s? This won't work in either case. There are no place-holders supported in fopen(), and * is (at least on Windows) a reserved character which shouldn't be used in file names. (Naming Files, Paths, and Namespaces)– Scheff
Nov 22 '18 at 16:37
Do you try to use
* as place-holder, or does your file name really contain these *s? This won't work in either case. There are no place-holders supported in fopen(), and * is (at least on Windows) a reserved character which shouldn't be used in file names. (Naming Files, Paths, and Namespaces)– Scheff
Nov 22 '18 at 16:37
@Scheff It is NATO joint standard symbology SID code. Hmm i suppose, i have to replace '*' character with something else.
– cevapsızcagri
Nov 22 '18 at 16:44
@Scheff It is NATO joint standard symbology SID code. Hmm i suppose, i have to replace '*' character with something else.
– cevapsızcagri
Nov 22 '18 at 16:44
Do these military guys work with *ix systems exclusively? (In *ix systems
/ and *** Platoon, etc. Centos: that's a Linux - hence, the "c:\" probably won't work. On Windows, * is prohibited - how about replacing with 'u2731' (the unicode point for ✱)? (Most people will probably not realize the difference.) ;-)– Scheff
Nov 22 '18 at 17:07
Do these military guys work with *ix systems exclusively? (In *ix systems
/ and *** Platoon, etc. Centos: that's a Linux - hence, the "c:\" probably won't work. On Windows, * is prohibited - how about replacing with 'u2731' (the unicode point for ✱)? (Most people will probably not realize the difference.) ;-)– Scheff
Nov 22 '18 at 17:07
For Windows, see Naming Files, Paths, and Namespaces, and in particular Naming Conventions. Amongst several others, the
* character is reserved and cannot be used in folder names or file names.– Remy Lebeau
Nov 22 '18 at 22:27
For Windows, see Naming Files, Paths, and Namespaces, and in particular Naming Conventions. Amongst several others, the
* character is reserved and cannot be used in folder names or file names.– Remy Lebeau
Nov 22 '18 at 22:27
add a comment |
0
active
oldest
votes
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
});
}
});
draft saved
draft discarded
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%2f53435070%2ffopen-return-null-when-passing-first-parameter-with-character%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53435070%2ffopen-return-null-when-passing-first-parameter-with-character%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
2
If your OS or file system forbids the character, there is nothing you can do.
– user2486888
Nov 22 '18 at 16:35
1
Do you try to use
*as place-holder, or does your file name really contain these*s? This won't work in either case. There are no place-holders supported infopen(), and*is (at least on Windows) a reserved character which shouldn't be used in file names. (Naming Files, Paths, and Namespaces)– Scheff
Nov 22 '18 at 16:37
@Scheff It is NATO joint standard symbology SID code. Hmm i suppose, i have to replace '*' character with something else.
– cevapsızcagri
Nov 22 '18 at 16:44
Do these military guys work with *ix systems exclusively? (In *ix systems
/andare the only excluded characters - I just recalled.) I first thought you are joking but, out of curiosity, I googled and found NATO Joint Military Symbology with e.g.***Platoon, etc. Centos: that's a Linux - hence, the"c:\"probably won't work. On Windows,*is prohibited - how about replacing with'u2731'(the unicode point for✱)? (Most people will probably not realize the difference.) ;-)– Scheff
Nov 22 '18 at 17:07
For Windows, see Naming Files, Paths, and Namespaces, and in particular Naming Conventions. Amongst several others, the
*character is reserved and cannot be used in folder names or file names.– Remy Lebeau
Nov 22 '18 at 22:27