Why Are C References Non-Resetable?

Un-resetability of References in C

In C , references exhibit two defining characteristics: they consistently refer to the same object and cannot be null. This contrasts with pointers, which can switch object targets and be set to null.

The Rationale for Non-Resetable References

Despite the perceived benefits of resetable references, C lacks such a feature. As stated by Bjarne Stroustrup in "Design and Evolution of C ":

"It is not possible to change what a reference refers to after initialization. Once a reference is initialized, it cannot be made to refer to a different object later; it cannot be re-bound."

Avoiding Ambiguity

Stroustrup's decision stemmed from his experience with Algol68, where references could be reassigned, either through the reference itself or by changing its reference value. This ambiguity could lead to programming errors.

In C , references consistently point to the same object, eliminating the potential for such confusion. By enforcing this restriction, code clarity and maintainability are enhanced.

Preserving Object Identity

References maintain a strong association with their target objects. This unyielding connection ensures the validity of the referred object. By prohibiting reassignment, C prevents dangling references, situations where a reference points to an invalid memory location.

Why Not a Constant, Resetable Option?

Some argue that a constant, resetable reference option could provide the best of both worlds. However, this concept would introduce additional complexity and potential ambiguity into the language.

The current behavior, where references are non-resetable, ensures that developers can rely on references to always point to the same object. This simplicity and predictability outweigh the perceived benefits of a potentially more flexible reference system.

The above is the detailed content of Why Are C References Non-Resetable?. For more information, please follow other related articles on the PHP Chinese website!