C++: Built-in arrays
-2
I thought that built-in arrays in C++ are statically allocated. But the following code works:
//...
int x;
std::cin >> x;
const int cx = x;
int array[cx];
//...
Why does it?
c++
edited Nov 20 '18 at 19:49
Fei Xiang
2,0614621
asked Nov 20 '18 at 19:17
Glech
6
add a comment |
-2
I thought that built-in arrays in C++ are statically allocated. But the following code works:
//...
int x;
std::cin >> x;
const int cx = x;
int array[cx];
//...
Why does it?
c++
edited Nov 20 '18 at 19:49
Fei Xiang
2,0614621
asked Nov 20 '18 at 19:17
Glech
6
8
That code works on some compilers that offer default-on extensions for variable length array. It doesn't work on other compilers and is not portable c++. You're being tricked by your compiler into thinking your code is valid c++. Another example of why you can't learn c++ by trial and error.
– François Andrieux
Nov 20 '18 at 19:18
One reason Variable Length Arrays are bad:xcan support numbers that are very big. Bigger than the amount of Automatic storage available to that array. Now multiply that large number by the size of anint. Using an array of that size will commonly manifest as a stack overflow and much debugging can ensue as a result.
– user4581301
Nov 20 '18 at 19:58
add a comment |
-2
-2
-2
I thought that built-in arrays in C++ are statically allocated. But the following code works:
//...
int x;
std::cin >> x;
const int cx = x;
int array[cx];
//...
Why does it?
c++
edited Nov 20 '18 at 19:49
Fei Xiang
2,0614621
asked Nov 20 '18 at 19:17
Glech
6
I thought that built-in arrays in C++ are statically allocated. But the following code works:
//...
int x;
std::cin >> x;
const int cx = x;
int array[cx];
//...
Why does it?
c++
c++
edited Nov 20 '18 at 19:49
Fei Xiang
2,0614621
asked Nov 20 '18 at 19:17
Glech
6
edited Nov 20 '18 at 19:49
Fei Xiang
2,0614621
asked Nov 20 '18 at 19:17
Glech
6
edited Nov 20 '18 at 19:49
Fei Xiang
2,0614621
edited Nov 20 '18 at 19:49
Fei Xiang
2,0614621
edited Nov 20 '18 at 19:49
Fei Xiang
2,0614621
2,0614621
asked Nov 20 '18 at 19:17
Glech
6
asked Nov 20 '18 at 19:17
Glech
6
asked Nov 20 '18 at 19:17
Glech
6
6
8
That code works on some compilers that offer default-on extensions for variable length array. It doesn't work on other compilers and is not portable c++. You're being tricked by your compiler into thinking your code is valid c++. Another example of why you can't learn c++ by trial and error.
– François Andrieux
Nov 20 '18 at 19:18
One reason Variable Length Arrays are bad:xcan support numbers that are very big. Bigger than the amount of Automatic storage available to that array. Now multiply that large number by the size of anint. Using an array of that size will commonly manifest as a stack overflow and much debugging can ensue as a result.
– user4581301
Nov 20 '18 at 19:58
add a comment |
8
That code works on some compilers that offer default-on extensions for variable length array. It doesn't work on other compilers and is not portable c++. You're being tricked by your compiler into thinking your code is valid c++. Another example of why you can't learn c++ by trial and error.
– François Andrieux
Nov 20 '18 at 19:18
One reason Variable Length Arrays are bad:xcan support numbers that are very big. Bigger than the amount of Automatic storage available to that array. Now multiply that large number by the size of anint. Using an array of that size will commonly manifest as a stack overflow and much debugging can ensue as a result.
– user4581301
Nov 20 '18 at 19:58
8
8
That code works on some compilers that offer default-on extensions for variable length array. It doesn't work on other compilers and is not portable c++. You're being tricked by your compiler into thinking your code is valid c++. Another example of why you can't learn c++ by trial and error.
– François Andrieux
Nov 20 '18 at 19:18
That code works on some compilers that offer default-on extensions for variable length array. It doesn't work on other compilers and is not portable c++. You're being tricked by your compiler into thinking your code is valid c++. Another example of why you can't learn c++ by trial and error.
– François Andrieux
Nov 20 '18 at 19:18
One reason Variable Length Arrays are bad:
x can support numbers that are very big. Bigger than the amount of Automatic storage available to that array. Now multiply that large number by the size of an int. Using an array of that size will commonly manifest as a stack overflow and much debugging can ensue as a result.– user4581301
Nov 20 '18 at 19:58
One reason Variable Length Arrays are bad:
x can support numbers that are very big. Bigger than the amount of Automatic storage available to that array. Now multiply that large number by the size of an int. Using an array of that size will commonly manifest as a stack overflow and much debugging can ensue as a result.– user4581301
Nov 20 '18 at 19:58
add a comment |
1 Answer
1
active
oldest
votes
3
Variable length arrays are not part of the C++ standard, however your compiler allows it. If you use the -pedantic-errors option with your compiler (assuming g++), this will throw an error as that option strictly enforces the standard.
answered Nov 20 '18 at 19:40
jdrd
1297
1
-pedanticcauses the compiler to emit warnings, not errors. You need to add on-Werroror-pedantic-errorsto get an compilation-halting error. That said,-Werroris something I recommend to anyone learning C++. Warnings are the first line of defense against logic errors and you should not ignore them.
– user4581301
Nov 20 '18 at 19:47
thanks, edited my answer to reflect that
– jdrd
Nov 20 '18 at 19:51
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
});
}
});
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%2f53400033%2fc-built-in-arrays%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
3
Variable length arrays are not part of the C++ standard, however your compiler allows it. If you use the -pedantic-errors option with your compiler (assuming g++), this will throw an error as that option strictly enforces the standard.
answered Nov 20 '18 at 19:40
jdrd
1297
1
-pedanticcauses the compiler to emit warnings, not errors. You need to add on-Werroror-pedantic-errorsto get an compilation-halting error. That said,-Werroris something I recommend to anyone learning C++. Warnings are the first line of defense against logic errors and you should not ignore them.
– user4581301
Nov 20 '18 at 19:47
thanks, edited my answer to reflect that
– jdrd
Nov 20 '18 at 19:51
add a comment |
3
Variable length arrays are not part of the C++ standard, however your compiler allows it. If you use the -pedantic-errors option with your compiler (assuming g++), this will throw an error as that option strictly enforces the standard.
answered Nov 20 '18 at 19:40
jdrd
1297
1
-pedanticcauses the compiler to emit warnings, not errors. You need to add on-Werroror-pedantic-errorsto get an compilation-halting error. That said,-Werroris something I recommend to anyone learning C++. Warnings are the first line of defense against logic errors and you should not ignore them.
– user4581301
Nov 20 '18 at 19:47
thanks, edited my answer to reflect that
– jdrd
Nov 20 '18 at 19:51
add a comment |
3
3
3
Variable length arrays are not part of the C++ standard, however your compiler allows it. If you use the -pedantic-errors option with your compiler (assuming g++), this will throw an error as that option strictly enforces the standard.
answered Nov 20 '18 at 19:40
jdrd
1297
Variable length arrays are not part of the C++ standard, however your compiler allows it. If you use the -pedantic-errors option with your compiler (assuming g++), this will throw an error as that option strictly enforces the standard.
answered Nov 20 '18 at 19:40
jdrd
1297
edited Nov 20 '18 at 19:50
answered Nov 20 '18 at 19:40
jdrd
1297
answered Nov 20 '18 at 19:40
jdrd
1297
answered Nov 20 '18 at 19:40
jdrd
1297
1297
1
-pedanticcauses the compiler to emit warnings, not errors. You need to add on-Werroror-pedantic-errorsto get an compilation-halting error. That said,-Werroris something I recommend to anyone learning C++. Warnings are the first line of defense against logic errors and you should not ignore them.
– user4581301
Nov 20 '18 at 19:47
thanks, edited my answer to reflect that
– jdrd
Nov 20 '18 at 19:51
add a comment |
1
-pedanticcauses the compiler to emit warnings, not errors. You need to add on-Werroror-pedantic-errorsto get an compilation-halting error. That said,-Werroris something I recommend to anyone learning C++. Warnings are the first line of defense against logic errors and you should not ignore them.
– user4581301
Nov 20 '18 at 19:47
thanks, edited my answer to reflect that
– jdrd
Nov 20 '18 at 19:51
1
1
-pedantic causes the compiler to emit warnings, not errors. You need to add on -Werror or -pedantic-errors to get an compilation-halting error. That said, -Werror is something I recommend to anyone learning C++. Warnings are the first line of defense against logic errors and you should not ignore them.– user4581301
Nov 20 '18 at 19:47
-pedantic causes the compiler to emit warnings, not errors. You need to add on -Werror or -pedantic-errors to get an compilation-halting error. That said, -Werror is something I recommend to anyone learning C++. Warnings are the first line of defense against logic errors and you should not ignore them.– user4581301
Nov 20 '18 at 19:47
thanks, edited my answer to reflect that
– jdrd
Nov 20 '18 at 19:51
thanks, edited my answer to reflect that
– jdrd
Nov 20 '18 at 19:51
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53400033%2fc-built-in-arrays%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
8
That code works on some compilers that offer default-on extensions for variable length array. It doesn't work on other compilers and is not portable c++. You're being tricked by your compiler into thinking your code is valid c++. Another example of why you can't learn c++ by trial and error.
– François Andrieux
Nov 20 '18 at 19:18
One reason Variable Length Arrays are bad:
xcan support numbers that are very big. Bigger than the amount of Automatic storage available to that array. Now multiply that large number by the size of anint. Using an array of that size will commonly manifest as a stack overflow and much debugging can ensue as a result.– user4581301
Nov 20 '18 at 19:58