I'm not familiar with Erlang, but a quick Google tells me Erlang uses single-assignment; so that would be a tentative yes.Originally Posted by Elysia
I never claimed that type safety is an ultimate tool that solves every problem, i claimed that more type safety is always better than less type safety. If a very type safe environment is making it harder to make your program do what you want, it is only because it is forcing you to do it in a way that prevents type errors. I maintain that is always a good thing. I suppose Phantomotap will have something to say about type safety 'getting in the way' at this point, but if it is getting in the way of the programmer making type errors then that is fine by me.That is not always true. Type safety comes at a price: it becomes more difficult to make the program do what you want. The tradeoff is, of course, that the compiler catches more bugs at compile time. To some applications, type safety is a large hindrance. It's not an ultimate tool that solves every problem.
I can agree that there might be many different reasons for sticking to C as a newcomer to C++, if you can agree that if C was not present, no such thing would be possible.Not true. People write C in C++ because they are mostly either more comfortable with it or don't know any better alternatives, or simply don't want to learn.
Hence, it is the fault of their education or because they are in a transition phase or because they are simply more comfortable with some paradigm (when you learn another language with a completely different paradigm, you tend to fight against it instead of learning it).
