![]() once you decide on your problem, you'll be able to better decide which technology fits for developing a solution. A GUI desktop app, a web server, a game, a cmd line utility. Decide what problem you're going to solve. I'd suggest you use the best tools at your disposal that fit the problems you're trying to solve. On the other hand, if you're looking to become the next design patterns master web developer, it's probably not the best approach, you may consider other languages that are more focused toward that area. Give it a shot, maybe throw together some GUI applications in GTK+. You read the book, so I assume you have some affinity to C and interest in OOP. It's great to see a language that wasn't designed for OOP support OOP. ![]() I'd never advocate not learning anything - it's great to get exposure to how, why and when to use it. That really depends on what you plan to do with it. With the footnote that you shouldn't stick 100 lines of OOP code in a 15000 line project, just because it's "kewl"! :) You should use OOP whenever your problem has a beautiful OOP solution. GUIs, for example, are often designed with inheritance between window types, using polymorphism to override and specialize behavior. Some problems are very well modeled by OOP. Yes, it's really used, but unsurprisingly, it's not as common as OOP in languages that were designed for it.Īre their any existing C projects that use OOP? Implementing OOP in C, is it really used? Or its just for mental exercise? Become familiar with how one does OO in C, the best way would be to do some C++, or examine any good project that uses a little C-style OO. Use it when it seems the right thing to do.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |