Home/ Questions/Q 940969
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T22:02:38+00:00

I have the following code: … int n; cin >> n; int numbers[n]; …

  • 0

I have the following code:

...
int n;
cin >> n;
int numbers[n];
...

It compiled with NetBeans on Mac using g++ (I think) and it didn’t compile using VS2008 on Windows. Why is it so hard to make it work with every compiler? The size of the array is known before allocating it.

EDIT: I know about std::vector. Actually this was part of a homework assignment and I started it at work on a mac, then got home and was surprised that it didn’t work on VS2008. Thanks for all the answers. But I still find it logical that if the compiler can generate some code like alloc(123) where the value 123 is hardcoded, why can’t it generate something like alloc(n) where you get n from a memory address that holds an int n or something. It just seems more logical to allow something like this by default.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Although the size of the array is known before it is allocated, it’s still not known until runtime. This is known as variable length array (VLA) and is a C99ism, supported in g++ by an extension that is enabled by default. To be explicit, this is not conformant C++ 98/03, and thus Visual C++ is well within its right to reject it.

    If you really want runtime dynamic sizing, allocate on the heap (via new[]). That will work everywhere, and as a bonus, protect you from stack overflows.

    • 0