15

I have some concepts about the VLA and its behavior that I need to clarify.

AFIK since C99 it's possible to declare VLA into local scopes:

int main(int argc, char **argv)
{
    // function 'main' scope
    int size = 100;
    int array[size];
    return 0;
}

But it is forbidden in global scopes:

const int global_size = 100;
int global_array[global_size]; // forbidden in C99, allowed in C++

int main(int argc, char **argv)
{
    int local_size = 100;
    int local_array[local_size];
    return 0;
}

The code above declares a VLA in C99 because the const modifier doesn't create a compile-time value. In C++ global_size is a compile-time value so, global_array doesn't become a VLA.

What I need to know is: Is my reasoning correct? Is the behaviour that I've described correct?

I also want to know: Why are the VLA not allowed in global scope? are they forbidden both in C and C++? Why is the behavior of arrays into global and local scope different?

Improve this question
10
  • 6
    Let's suppose global VLAs are allowed. When is their (variable) size actually defined ? Commented Dec 28, 2012 at 20:17
  • 2
    @cnicutar well... like all the VLA, in execution time, like the other scopes. I know that this isn't the answer, but I want to know WHY. Commented Dec 28, 2012 at 20:19
  • 1
    stackoverflow.com/a/5052083/174605 Commented Dec 28, 2012 at 20:20
  • 3
    Yes, so a global VLA, how would you know when the value is defined? To make it meaningful, it requires that you can set the value of the size before the array is built - and the size needs to be known at compile time to tell the system how much space the OS needs to give the executable when it gets loaded. Commented Dec 28, 2012 at 20:23
  • 3
    Voting to reopen as this is NOT a duplicate of the linked "duplicate". The linked question asks how to avoid the error that VLAs are not permitted at file scope; this question asks why VLAs are not permitted at file scope. Commented Sep 30, 2014 at 4:22

5 Answers 5

Reset to default
17

Yes your reasoning is correct, that is how these different forms of array declarations and definitions are viewed by C and C++.

As others already stated, VLA with a veritable variable length (non-const) in global scope is difficult to make sense. What would the evaluation order be, e.g if the the length expression would refer to an object of a different compilation unit? C++ doesn't have VLA, but it has dynamic initialization of objects at file scope. And already this gives you quite a head ache, if you have to rely on evaluation order.

This leaves the small gap for C concerning length expressions that contain a const qualified object, which isn't allowed. This comes from the fact that such objects are not considered "integer constant expressions" by the C standard. This could perhaps change in future versions, but up to now the C committee didn't find it necessary to allow for such a thing: there are enum constants that play that role in C. Their only limitation is that they are limited to int in C, it would be nice to also have them size_t.

Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

Finally someone proves to have read the whole question! (+1 for this) IMHO this question isn't duplicate because I'm focusing in other facts. Thanks for the explanation and thanks for answering almost all my questions.
I’m not a C person, but looking over the C23 proposed features table, it seems that N3008 adds constexpr to C. It does not explicitly say that a constexpr variable in an array bound is an “integer constant expression”, maybe that follows from what is in N3008 and the current C standard.
@Bolpat Indeed, things are going to change here with C23. As you say there are constexpr that allow to define constant expressions of almost arbitrary type (and yes these are suitable for array bounds if they have integer type) and there are also generalizations for enumerations that allow to have other types then just int for the constants.
5

C++ doesn't support VLAs, period. The reason the second code snippet works in C++ is that the const keyword creates a compile-time constant in C++; in C, it doesn't.

C99 doesn't support VLAs outside of block scope, period, regardless of how you declare the size variable. Note that C2011 makes VLA support optional.

Improve this answer

1 Comment

Yes, I know that const keyword creates a compile-time constant in C++ and in C it doesn't, I've commented this on the question.
4

I think the fundamental reason is a global variable has linkage, its size has to be known at compile time. If not, how could one link the program?

local variables have no linkage and the VLAs are allocated on the stack, which grows dynamically as the program runs.

Improve this answer

Comments

3

There is a difference between being forbidden and not being allowed. ;-)

The VLA feature is designed to allow the use of stack space for a local array, to avoid the use of malloc for heap allocation. It is mostly a speed optimization.

Now you want to use VLAs outside of functions. Why? There is not much to win speedwise in avoiding a single malloc call during program start. And what stack space are we supposed to use for variables with a static life time?

Improve this answer

Comments

1

So, for global VLA's, one of the issues (there are many variants on the theme) can be shown here:

int size;
int a;
int v[size];
int b;

.... in another file:

extern int a;
extern int b;

The linker will have to know where a and be are in relation to each other at link time, or it won't be able to fix them up correctly at load-time.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.