Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was under the impression that singleton is the proper design pattern which adds the flexibility for the design to evolve, extend, etc. , where globals are just a workaround. But in a question asked in this forum I was told try to avoid singleton pattern and go for global non-member functions. What is the reason for this?
Here is a reference page: Global vs Singleton in .NET
In my understanding, with singleton, I can control when the object is initialized. But with globals, it’s a little difficult to do it.