Using newly declared variable in initialization (int x = x+1)?

by

With the expression:

int x = x + 1;

the variable x comes into existence at the = sign, which is why you can use it on the right hand side. By “comes into existence”, I mean the variable exists but has yet to be assigned a value by the initialiser part.

However, unless you’re initialising a variable with static storage duration (e.g., outside of a function), it’s undefined behaviour since the x that comes into existence has an arbitrary value.

C++03 has this to say:

The point of declaration for a name is immediately after its complete declarator (clause 8) and before its initializer (if any) …

Example:
int x = 12;
{ int x = x; }
Here the second x is initialized with its own (indeterminate) value.

That second case there is pretty much what you have in your question.

More Related Contents:

  1. Does initialization entail lvalue-to-rvalue conversion? Is `int x = x;` UB?
  2. Uninitialized variable behaviour in C++
  3. Why is initialization of a new variable by itself valid? [duplicate]
  4. Is reading an indeterminate value undefined behavior?
  5. Fun with uninitialized variables and compiler (GCC)
  6. (Why) is using an uninitialized variable undefined behavior?
  7. Is there a difference between copy initialization and direct initialization?
  8. What are all the common undefined behaviours that a C++ programmer should know about? [closed]
  9. Accessing inactive union member and undefined behavior?
  10. How could pairing new[] with delete possibly lead to memory leak only?
  11. Why aren’t pointers initialized with NULL by default?
  12. How do C++ class members get initialized if I don’t do it explicitly?
  13. Why are my struct’s members not properly initialised using `{}`? [duplicate]
  14. memset() or value initialization to zero out a struct?
  15. Are function static variables thread-safe in GCC?
  16. Are multiple mutations within initializer lists undefined behavior?
  17. C++ where to initialize static const
  18. A C++ implementation that detects undefined behavior?
  19. Why does the enhanced GCC 6 optimizer break practical C++ code?
  20. Why is it that we can write outside of bounds in C?
  21. Initializing container of unique_ptrs from initializer list fails with GCC 4.7
  22. Is infinite loop still undefined behavior in C++ if it calls shared library?
  23. Value initialization and Non POD types
  24. Mixing class and struct
  25. Is it allowed to cast away const on a const-defined object as long as it is not actually modified?
  26. Member fields, order of construction
  27. Can branches with undefined behavior be assumed unreachable and optimized as dead code?
  28. How to initialize a struct to 0 in C++
  29. Is there a way to statically-initialize a dynamically-allocated array in C++?
  30. C++ Member Initializer List

Leave a Comment