Why does `int ;` compile fine in C, but not in C++?

by

The C standard says

A declaration other than a static_assert declaration shall declare at least a declarator (other than the parameters of a function or the members of a structure or union), a tag, or the members of an enumeration.

C++ says

In a simple-declaration, the optional init-declarator-list can be omitted only when declaring a class (Clause 9) or enumeration.

A violation of this in either language requires a diagnostic. The standards do not talk about compiler errors or warnings. A warning is a diagnostic.

More Related Contents:

  1. trap representation
  2. Is it a conforming compiler extension to treat non-constexpr standard library functions as constexpr?
  3. Is the compiler allowed to optimize out heap memory allocations?
  4. Explicit specialization in non-namespace scope does not compile in GCC
  5. Class type non-type template parameter initialization does not compile
  6. What is the purpose of a declaration like int (x); or int (x) = 10;
  7. Does C have One Definition Rule like C++?
  8. Calling an explicit constructor with a braced-init list: ambiguous or not?
  9. Injected class name compiler discrepancy
  10. Why is GCC saying multiple definitions of main? I have one main [closed]
  11. When to use extern in C++
  12. Implementation C++14 make_integer_sequence
  13. reinterpret_cast creating a trivially default-constructible object
  14. GCC -fPIC option
  15. __builtin_prefetch, How much does it read?
  16. Why is initialization of a new variable by itself valid? [duplicate]
  17. Template partial ordering – why does partial deduction succeed here
  18. Does the behavior of guaranteed copy elision depend on existence of user-defined copy constructor?
  19. How Switch case Statement Implemented or works internally?
  20. how to use std::filesystem on gcc 8?
  21. Does accessing the first field of a struct via a C cast violate strict aliasing?
  22. Is there a compiler bug exposed by my implementation of an is_complete type trait?
  23. Undefined reference to google::protobuf::internal::empty_string_[abi:cxx11]
  24. Dangling references and undefined behavior
  25. Why do the usual access control checking applies to names used to specify explicit instantiation when accessed through template parameters?
  26. The proper way of forcing a 32-bit compile using CMake
  27. Linking C++ code with ‘gcc’ (without g++)
  28. Returning struct containing array
  29. What standard clause mandates this lvalue-to-rvalue conversion?
  30. What information does GCC Profile Guided Optimization (PGO) collect and which optimizations use it?

Leave a Comment