Code Complete, Second Edition

按有用程度 按页码先后 最新笔记

• 

  第141页

  GoneChaosGone (埋头做一只伪造猫)

  Encapusulation Avoid friend classes I have no real experience in C++, so just have no idea what a "friend class" is. Ref to wikipedia, A friend class in C++, can access the "private" and "protected" members of the class in which it is declared as a friend. On declaration of friend class all member function of the friend class become friend of the class in whic... (更多)

  Encapusulation Avoid friend classes

  I have no real experience in C++, so just have no idea what a "friend class" is.

  Ref to wikipedia, A friend class in C++, can access the "private" and "protected" members of the class in which it is declared as a friend. On declaration of friend class all member function of the friend class become friend of the class in which the friend class was declared. Friend status is not inherited; every friendship has to be explicitly declared. Friend classes can help in improving encapsulation if used wisely.

  But why I wont see it in a modern OO language like Java and C#?

  Let me clarify how the friend keyword undermines OOP.

  Private and protected variables and methods are perhaps one of the most important part of OOP. The idea that objects can hold data or logic that only they can use allows you to write your implementation of functionality independent of your environment - and that your environment cannot alter state information that it is not suited to handle. By using friend you are coupling two classes' implementations together - which is much worse then if you just coupled their interface. http://stackoverflow.com/questions/203616/why-does-c-sharp-not-provide-the-c-style-friend-keyword

  (收起)

  2012-02-05 23:24:41   回应

  收藏

  推荐
• 

  第143页

  GoneChaosGone (埋头做一只伪造猫)

  coupling goes hand in glove with abstraction adn encapsulation.Tight coupling occurs when an abstractions is leaky,or when encapsulation is broken.If a class offers an incomplete set of service ,other routines might find they need to read or write its internal data directly. That opens up the class ,making it a glass box instead of a black box, and it virtually eliminates the class' encapsulation.... (更多)

  coupling goes hand in glove with abstraction adn encapsulation.Tight coupling occurs when an abstractions is leaky,or when encapsulation is broken.If a class offers an incomplete set of service ,other routines might find they need to read or write its internal data directly. That opens up the class ,making it a glass box instead of a black box, and it virtually eliminates the class' encapsulation.

  I agree with the point here. But in my general pratice, especially against some colleagues' work, if a routine or attribute does not work as my expection, i will dive deep into the glass box if I can, to find out whether I am wrong or it is a bug. I wont go to my colleague's desk and tell him, "hi, your code is not written in a proper abstract way, please correct it." It is just rude, and will result in some issues in your relationship with your work mates. An alternative way is to do some explanation to some code but without naming the code's auther.

  Anyway, if someone in the work tell me my work is bad, i will happy to listen to his idea, but it just me. (收起)

  2012-02-05 22:59:41   回应

  收藏

  推荐
• 

  第26页

  GoneChaosGone (埋头做一只伪造猫)

  Steve is right, prerequisites is totally depending on your boss's mind, if he wants you begin code asap, then you have to find a way to pretend you've followed his very "correct" decision. (更多)

  Steve is right, prerequisites is totally depending on your boss's mind, if he wants you begin code asap, then you have to find a way to pretend you've followed his very "correct" decision. (收起)

  2012-01-20 06:32:10   回应

  收藏

  推荐

• 

  第5页

  可爱的肖恩 (经过涅槃的凤凰会重生)

  软件的实现为什么重要？ 1、Construction is a large part of software development. 2、Construction is the central activity in software development. 3、With a focus on construction, the individual programmer's productivity can improve enormously. 4、Construction's product, the source code, is often the only accurate description of the software. 5、Construction is the only activity that's guar... (更多)

  软件的实现为什么重要？

  1、Construction is a large part of software development. 2、Construction is the central activity in software development. 3、With a focus on construction, the individual programmer's productivity can improve enormously. 4、Construction's product, the source code, is often the only accurate description of the software. 5、Construction is the only activity that's guaranteed to be done.

  (收起)

  2011-12-29 01:17:26   回应

  收藏

  推荐
• 

  第21页

  GoneChaosGone (埋头做一只伪造猫)

  Meaphors are heurristics, so even using "Building Construction" is still weak. Because in today's "posh" agile way,everything is keeping changing. Software is delievered frequently (weeks instead of months). Cannot image constructors keep changing their work week by week in the reallife. Software development is a unique process, as no metaphor can be used to describe it. ... (更多)

  Meaphors are heurristics, so even using "Building Construction" is still weak.

  Because in today's "posh" agile way,everything is keeping changing. Software is delievered frequently (weeks instead of months). Cannot image constructors keep changing their work week by week in the reallife. Software development is a unique process, as no metaphor can be used to describe it.

  Metaphors are for rookie :)

  Experience is not the triky things learned from a IDE, a languge,a framework. It is kind of thing tell you how to make a right decistion to every job. (收起)

  2012-01-20 05:39:25   回应

  收藏

  推荐
• 

  第26页

  GoneChaosGone (埋头做一只伪造猫)

  Steve is right, prerequisites is totally depending on your boss's mind, if he wants you begin code asap, then you have to find a way to pretend you've followed his very "correct" decision. (更多)

  Steve is right, prerequisites is totally depending on your boss's mind, if he wants you begin code asap, then you have to find a way to pretend you've followed his very "correct" decision. (收起)

  2012-01-20 06:32:10   回应

  收藏

  推荐

• 

  第141页

  GoneChaosGone (埋头做一只伪造猫)

  Encapusulation Avoid friend classes I have no real experience in C++, so just have no idea what a "friend class" is. Ref to wikipedia, A friend class in C++, can access the "private" and "protected" members of the class in which it is declared as a friend. On declaration of friend class all member function of the friend class become friend of the class in whic... (更多)

  Encapusulation Avoid friend classes

  I have no real experience in C++, so just have no idea what a "friend class" is.

  Ref to wikipedia, A friend class in C++, can access the "private" and "protected" members of the class in which it is declared as a friend. On declaration of friend class all member function of the friend class become friend of the class in which the friend class was declared. Friend status is not inherited; every friendship has to be explicitly declared. Friend classes can help in improving encapsulation if used wisely.

  But why I wont see it in a modern OO language like Java and C#?

  Let me clarify how the friend keyword undermines OOP.

  Private and protected variables and methods are perhaps one of the most important part of OOP. The idea that objects can hold data or logic that only they can use allows you to write your implementation of functionality independent of your environment - and that your environment cannot alter state information that it is not suited to handle. By using friend you are coupling two classes' implementations together - which is much worse then if you just coupled their interface. http://stackoverflow.com/questions/203616/why-does-c-sharp-not-provide-the-c-style-friend-keyword

  (收起)

  2012-02-05 23:24:41   回应

  收藏

  推荐
• 

  第143页

  GoneChaosGone (埋头做一只伪造猫)

  coupling goes hand in glove with abstraction adn encapsulation.Tight coupling occurs when an abstractions is leaky,or when encapsulation is broken.If a class offers an incomplete set of service ,other routines might find they need to read or write its internal data directly. That opens up the class ,making it a glass box instead of a black box, and it virtually eliminates the class' encapsulation.... (更多)

  coupling goes hand in glove with abstraction adn encapsulation.Tight coupling occurs when an abstractions is leaky,or when encapsulation is broken.If a class offers an incomplete set of service ,other routines might find they need to read or write its internal data directly. That opens up the class ,making it a glass box instead of a black box, and it virtually eliminates the class' encapsulation.

  I agree with the point here. But in my general pratice, especially against some colleagues' work, if a routine or attribute does not work as my expection, i will dive deep into the glass box if I can, to find out whether I am wrong or it is a bug. I wont go to my colleague's desk and tell him, "hi, your code is not written in a proper abstract way, please correct it." It is just rude, and will result in some issues in your relationship with your work mates. An alternative way is to do some explanation to some code but without naming the code's auther.

  Anyway, if someone in the work tell me my work is bad, i will happy to listen to his idea, but it just me. (收起)

  2012-02-05 22:59:41   回应

  收藏

  推荐
• 

  第26页

  GoneChaosGone (埋头做一只伪造猫)

  Steve is right, prerequisites is totally depending on your boss's mind, if he wants you begin code asap, then you have to find a way to pretend you've followed his very "correct" decision. (更多)

  Steve is right, prerequisites is totally depending on your boss's mind, if he wants you begin code asap, then you have to find a way to pretend you've followed his very "correct" decision. (收起)

  2012-01-20 06:32:10   回应

  收藏

  推荐