Why aren't variable-length arrays part of the C++ standard?
There recently was a discussion about this kicked off in usenet: Why no VLAs in C++0x.
I agree with those people that seem to agree that having to create a potential large array on the stack, which usually has only little space available, isn't good. The argument is, if you know the size beforehand, you can use a static array. And if you don't know the size beforehand, you will write unsafe code.
C99 VLAs could provide a small benefit of being able to create small arrays without wasting space or calling constructors for unused elements, but they will introduce rather large changes to the type system (you need to be able to specify types depending on runtime values - this does not yet exist in current C++, except for
new operator type-specifiers, but they are treated specially, so that the runtime-ness doesn't escape the scope of the
You can use
std::vector, but it is not quite the same, as it uses dynamic memory, and making it use one's own stack-allocator isn't exactly easy (alignment is an issue, too). It also doesn't solve the same problem, because a vector is a resizable container, whereas VLAs are fixed-size. The C++ Dynamic Array proposal is intended to introduce a library based solution, as alternative to a language based VLA. However, it's not going to be part of C++0x, as far as I know.
Are variable length arrays there in c++?
The current C++ standard does not require that compilers support VLAs. However, compiler vendors are permitted to support VLAs as an extension. GCC >= 4.7, for example, does.
It was originally proposed that VLAs would appear in C++14, however the proposal did not succeed. They also, ultimately, did not appear in C++17.
Variable Length array forbidden in ISO C++ error in sublime text 3
Replace the VLA with a std::vector:
std::vector<int> a(n); // was VLA: int a[n];
what happens if you create a variable length array and compile using g++
GCC documents its support of VLAs here (emphasis mine)
Variable-length automatic arrays are allowed in ISO C99, and as an
extension GCC accepts them in C90 mode and in C++.
CLANG documentation too follows suit but mentions clearly that the standard doesn't accept (emphasis mine)
GCC and C99 allow an array's size to be determined at run time. This
extension is not permitted in standard C++. However, Clang supports
such variable length arrays for compatibility with GNU C and C99
If you would prefer not to use this extension, you can always disable it with
-Werror=vla to disallow compilation.
Why is this VLA (variable-length array) definition unreliable?
In the code in the question, the variable
n is uninitialized when it is used in the definition of
vla. Indeed, with GCC set fussy, the code shown produces a compilation error (it'll give a warning if you are careless enough to omit
-Werror from your compilation options — don't do that!):
$ gcc -std=c11 -O3 -g -Wall -Wextra -Werror -Wstrict-prototypes -Wmissing-prototypes -Wshadow -pedantic-errors vla37.c -o vla37
vla37.c: In function ‘main’:
vla37.c:6:5: error: ‘n’ is used uninitialized [-Werror=uninitialized]
6 | double vla[n];
vla37.c:5:9: note: ‘n’ declared here
5 | int n;
cc1: all warnings being treated as errors
(That's from GCC 11.2.0 on a machine running RedHat RHEL 7.4.)
The trouble is that the compiler must know the size of the array when it is declared, but the value in
n is undefined (indeterminate) because it is uninitialized. It could be huge; it could be zero; it could be negative.
The cure for the problem is simple — make sure the size is known and sane before it is used to declare the VLA:
if (scanf("%d", &n) != 1)
for (int i = 0; i < n; i++)
if (scanf("%lf", &vla[i]) != 1)
for (int i = 0; i < n; i++)
printf("[%d] = %.2f\n", i, vla[i]);
Now you can run the result:
$ vla41 <<<'9 2.34 3.45 6.12 8.12 99.60 -12.31 1 2 3'
 = 2.34
 = 3.45
 = 6.12
 = 8.12
 = 99.60
 = -12.31
 = 1.00
 = 2.00
 = 3.00
(That assumes your shell is Bash or compatible with Bash and supports 'here strings' (the
The code shown in the question and in this answer is barely adequate in handling I/O errors; it detects input problems but doesn't provide useful feedback to the user.
The code shown does not validate the value of
n for plausibility. You should ensure that the size is larger than zero and less than some upper bound. The maximum size depends on the size of the data being stored in the VLA and the platform you're on.
If you're on a Unix-like machine, you probably have 8 MiB of stack; if you're on a Windows machine, you probably have 1 MiB of stack; if you're on an embedded system, you may have much less stack available to you. You need to leave some stack space for other code too, so you should probably check that the array size is not more than, for sake of discussion, 1024 — that would be 8 KiB of stack for an array of
double, which is not huge at all but it provides plenty of space for most homework programs. Tweak the number larger to suit your purposes, but when the number grows, you should use
malloc() et al to dynamically allocate the array instead of using an on-stack VLA. For example, on a Windows machine, if you use a VLA of type
int, setting the size above 262,144 (256 * 1024) almost guarantees that your program will crash, and it may crash at somewhat smaller sizes than that.
Lessons to learn
- Compile with stringent warning options.
- Compile with
-Werroror its equivalent so warnings are treated as errors.
- Make sure the variable defining the size of a VLA is initialized before defining the array.
- Not too small (not zero, not negative).
- Not too big (not using more than 1 megabyte on Windows, 8 megabytes on Unix).
- Leave a decent margin for other code to use as well.
Note that all compilers that support VLAs also support variables defined at arbitrary points within a function. Both features were added in C99. VLAs were made optional in C11 — and a compiler should define
__STDC_NO_VLA__ if it does not support VLAs at all but claims conformance with C11 or later.
C++ and variable-length arrays
Standard C++ does not support C-style VLAs. However, GCC (
g++) does support them by default as an extension. This can cause confusion.
Dynamic memory allocation in C for variable length arrays
Automatic storage duration objects including VLAs are (by most modern implementations) allocated on the stack. There are some problems with the larger objects if they are allocated on the stack (three most important ones):
- There is no allocation control unless your program fails when you overflow the stack
- Stack is usually much much smaller than the heap. So the size of the array is limited
- The lifetime of the array is limited to the lifetime of the enclosing block. You can't return the reference to this array on the function return.
Pass Parameter to Base Class Constructor While Creating Derived Class Object
Difference Between Function Overloading and Template Function Which Is More Appropriate
Why Isn't Sizeof For a Struct Equal to the Sum of Sizeof of Each Member
What Are C++ Functors and Their Uses
What Is the Curiously Recurring Template Pattern (Crtp)
How to Read an Entire File into a Std::String in C++
Meaning of Acronym Sso in the Context of Std::String
How to Print a List of Elements Separated by Commas
Is Local Static Variable Initialization Thread-Safe in C++11
Given an Integer N. What Is the Smallest Integer Greater Than N That Only Has 0 or 1 as Its Digits
How to Print Current Time (With Milliseconds) Using C++/C++11
What Is This Weird Colon-Member (": ") Syntax in the Constructor
Definitive List of Common Reasons For Segmentation Faults
How to Find the Length of an Array
What Are the Evaluation Order Guarantees Introduced by C++17
Why Do I Get the Same Sequence For Every Run With Std::Random_Device With Mingw Gcc4.8.1