Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

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.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6695373
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T06:12:51+00:00 2026-05-26T06:12:51+00:00

Is it bad practice to put most variables at class level in a Form?

  • 0

Is it bad practice to put most variables at class level in a Form? Would these be considered global variables?

public partial class Form1 : Form
{
    private string mode;
    private int x, y;

    public Form1()
    {
        InitializeComponent();
    }
}

I’m using the variables in multiple controls when I declare them at class level.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T06:12:52+00:00Added an answer on May 26, 2026 at 6:12 am

    Those would be considered class-level globals (to distinguish from application globals.) The more important distinction in this case is that they are private to the class.

    Class-level globals have their uses, so I definitely wouldn’t call it a bad practice. A very good use for private class globals is when you plan to expose them through property accessors. For example:

    • public readonly properties whose values are controlled by logic internal to your class.

    • public properties with both set and get accessors (enabling custom validation logic in setter.)

    However, I would say it’s a good practice to make things local unless otherwise necessary. The reason is that you have less mutable state belonging to a class instance, so there is less potential for bugs like this:

    private int EvilMethod1() {  
        x = (int) Math.Pow((double) y, 2);
        return x;
    } 
    
    private int EvilMethod2() {  
        y = (x + y) * 2;                    
        return y;
    }
    
    // Assignments depend on the current values of x and y, 
    // as well as yielding unexpected side effects.
    private void PureEvil()
    {
        // Return value depends on current y; has side effect on x while assigning y.
        y = EvilMethod1();  
    
        // Return value depends on current x and y; has side effect on y while assigning x.
        x = EvilMethod2(); 
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Is it considered bad practice to use colons to put two statements on the
Why is it bad practice to declare variables on one line? e.g. private String
Is type checking considered bad practice even if you are checking against an interface?
Would you consider it bad practice to store various user data in a database
Is it considered bad practice to have multiple try's in one method and structure
Is it considered bad practice to have multiple views for same URL in MVC,
Is it generally considered bad practice to provide Iterator implementations that are infinite; i.e.
I know this is really bad practice, but it's already been put in place
To put it simply as an example, public abstract class AbstractFellow { protected Thing
I know its bad practice to put error handling in properties I just want

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.