• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Object Oriented Development vs Practicality

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    #11
    notepad is for noobs - real pros' use edlin...

    Comment


      #12
      You're all wooses - I use VS 1978 Punch Card version!
      If you think my attitude stinks, you should smell my fingers.

      Comment


        #13
        Use I do turn it off because I always get the cranky workstations to work with which lag seriously the moment you hit ".".

        Atw: I can remember the members, properties and methods. And you shouldn't be using globals!
        Serving religion with the contempt it deserves...

        Comment


          #14
          All of them in the whole .net Framework?

          Comment


            #15
            Originally posted by Diestl
            All of them in the whole .net Framework?
            About 80% - SDK documentation for the rest
            Serving religion with the contempt it deserves...

            Comment


              #16
              Originally posted by TheMonkey
              Atw: I can remember the members, properties and methods. And you shouldn't be using globals!
              Why is that? Are you aware of the kind of performance penalty you get if you use property accessors rather than global variable (in a class)?

              Comment


                #17
                Originally posted by AtW
                Why is that? Are you aware of the kind of performance penalty you get if you use property accessors rather than global variable (in a class)?
                Yeah. Performance isn't always key though...
                Serving religion with the contempt it deserves...

                Comment


                  #18
                  Originally posted by TheMonkey
                  Yeah. Performance isn't always key though...
                  A lot of properties are just read/write without any modifications and checks (like ranges etc), ie:

                  class foo
                  {

                  public int property
                  {
                  get { return _property; }
                  set { _property=value; }
                  }

                  int _property=0;

                  }

                  In such case there is absolutely no need to have property.

                  Accessing value via accessor rather than directly is (I think) over 10 (!) times slower - performance killer in tight loops.

                  Comment


                    #19
                    Originally posted by AtW
                    A lot of properties are just read/write without any modifications and checks (like ranges etc), ie:

                    class foo
                    {

                    public int property
                    {
                    get { return _property; }
                    set { _property=value; }
                    }

                    int _property=0;

                    }

                    In such case there is absolutely no need to have property.

                    Accessing value via accessor rather than directly is (I think) over 10 (!) times slower - performance killer in tight loops.
                    Yeah true but most business tier stuff has validation in it anyway. In the case above just having a public member variable will do.

                    Killer is:

                    object.Property += 1;

                    Kills the thing quite badly.
                    Serving religion with the contempt it deserves...

                    Comment


                      #20
                      Originally posted by TheMonkey
                      object.Property += 1;
                      Surely this won't cause endless recursion?

                      Comment

                      Working...
                      X