| ??? 01/06/11 17:42 Read: times Msg Score: +1 +1 Good Answer/Helpful |
#180463 - Always give enough context to statements Responding to: ???'s previous message |
No, I don't want any "food fights".
But there is a huge difference between writing something on a forum somewhere on the net, and talking with someone in the same room. People randomly comes and visit forum threads. That means that it is vital to always try to bracket all statements. Statements made should not be general, assuming that a reader have followed whatever you may have posted for a great many years, just to be able to guess within what specific situations your claims may be valid. So whenever you do make a wildcard statement, without supplying any required background information, I will jump in and say that the statement is not generally true. If you post that you don't think 8051 is a good target architecture for C++ programs, you sepcifically tells a reader that it is your view. And specific to the 8051 architecture. When you do say that C++ isn't good for microcontrollers, you are making a statement that the world have many times over shown isn't true. Whenever you do post something on a public forum - do read through the text one more time and check that you have added enough context for the text to be meaningful to other people and not just to you. It is exactly the same problem/error to write general statements without supplying the required context, as it is when "noobs" comes visiting forums and forgots to tell what processor they are using, what compiler, what the error messages they get are etc. Not only people who ask questions must spend extra time making sure that they supply enough context for the question to be meaningful. People trying to help must also make sure to always give enough context. Remember that many readers will pick up threads totally out-of-context and take text they read at face value. In this specific thread, I do not see discussions about C++ as off-topic. The OP is wondering about what path to take. That means that answers can walk quite a distance in different directions, when it comes to mentioning different programming languages that have relations to embedded use, or to beginning developers. In the end, there are no "best" or "correct" choice. All we can do is show different aspects/views. In some situations, we might bring in a bit too much information, but even if too much information may make it harder to decide, it is better to have and ignore information than to have to decide without sufficient information. With insufficient information, the error is on our side for not helping enough. With too much information, it's up to the OP to decide what to prune until the decision tree gets manageable. |
