Steven Giesel • 4/21/2022

Is public const bad?

Read Original

This technical article analyzes the use of 'public const' in C# programming. It explains how constants are compile-time replacements, leading to versioning problems when referenced across assemblies. The author demonstrates the issue with code examples and recommends using 'static readonly' fields for better maintainability and to avoid hard-coded values in dependent code.

0 comments
#software design #c #compilation
Is public const bad?

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes