Printable View
why do sometimes people need to understand what type of the object they are dealing with ? i am a professional programmer for over 20 years and has finished over 16 big projects for Australian army but I have never done anything relating to object types.
Thankyou
Regards,
Deniel Walker
( Dr Walker )
From the coder's viewpoint, it is for the substitution mechanisms to be much easier...Quote:
Originally Posted by Onlyone5
Now if you can explain what "substitution mechanism" is supposed to mean, everyone will be grateful.Quote:
Originally Posted by Emiene
Regards,
Paul McKenzie
Most of the time, it's because the programmer has designed their classes poorly, or they are not aware of virtual functions and polymorphism.Quote:
Originally Posted by Onlyone5
Regards,
Paul McKenzie
You mean non-typed languages?Quote:
Originally Posted by Onlyone5
Yes, I mean non-typed languages, and I am already 71 years old :(
There're good discussions about that at artima.
http://www.artima.com/forums/flat.js...t=0&msRange=15
http://www.artima.com/forums/flat.js...t=0&msRange=15
http://www.artima.com/forums/flat.js...t=0&msRange=15
Personally I see static typing as documentation and tests. As documentation, type system is understandable by automatic tools which enables some good magic. As static tests, it prevents many errors at compile time. Such tests are better defined then it'd be possible for dynamic types and enable quick (local) reanalysis. Both points make programmer more productive.
On the other side, static typing makes code more verbose, and it lowers productivity. So decision depends on type of project. I think projects with non-trivial structure benefit from static typing.