I'm working on some C++ code, and I just realized that the keywords 'private', 'protected' and 'public' really miss the boat. Instead of talking to who can use the elements of the class by access, they should be named 'expert', 'competent', and 'dips**t'.
This will, of course, make the compiler's job a bit harder, but think of the savings in man hours when it comes time to integrate the efforts of large teams!
-- Tim Wescott Wescott Design Services http://www.wescottdesign.com Do you need to implement control loops in software? "Applied Control Theory for Embedded Systems" was written for you. See details at http://www.wescottdesign.com/actfes/actfes.html
Sounds like an excellent macro addition to the coding standards suggested by Jean L. in May Embedded Systems.
Personally, I'll skip both ;-)
See ya, Dave
Please learn to use newsgroups properly - a post like this with no context quotations and broken threading is totally pointless.
mvh.,
David
But the biggest dips**ts are the ones who think they are the top dog experts!
That's why you need a compiler smart enough to figure out who's the real expert and who's not. The business world needs WYGIWYT compilers -- What You Get Is What You Thought.
-- Tim Wescott Wescott Design Services http://www.wescottdesign.com Do you need to implement control loops in software? "Applied Control Theory for Embedded Systems" was written for you. See details at http://www.wescottdesign.com/actfes/actfes.html
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.