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
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes