Michael Aivaliotis Posted August 26, 2006 Report Posted August 26, 2006 Here is a revised poll to reflect the recent release of LV8.20 Quote
Jacemdom Posted August 26, 2006 Report Posted August 26, 2006 Here is a revised poll to reflect the recent release of LV8.20 I suggest that you add "planning to investigate LVOOP 8.20 version" in the second question... Quote
crelf Posted August 27, 2006 Report Posted August 27, 2006 Here is a revised poll to reflect the recent release of LV8.20 Pitty I can't select more than one option... Quote
Jim Kring Posted August 27, 2006 Report Posted August 27, 2006 Pitty I can't select more than one option... Yeah, I use a lot of different GOOP styles, too. Which one I use depends on the requirements and my mood. I am not sure how to answer the question of what percentage of my total development uses GOOP, but nearly every non-trivial application employs some OOP analysis, design, and implementation. Quote
Michael Aivaliotis Posted August 27, 2006 Author Report Posted August 27, 2006 I am not sure how to answer the question of what percentage of my total development uses GOOP, but nearly every non-trivial application employs some OOP analysis, design, and implementation.So I guess the answer is 100%Pitty I can't select more than one option...Yes, but that's not my fault. It's a limitation in the polling system. Quote
Jim Kring Posted August 27, 2006 Report Posted August 27, 2006 So I guess the answer is 100% Well, that still depends on the original question -- is the question what percentage of projects use OOP or is the question what percentage of your programming is OOP? My point is that there is a time and a place for OOP. I do not use OOP for every problem. For example, if I have to add two numbers together, I will not create a class called Numeric and implement an Add method. This is just too much effort for too little return. Quote
crelf Posted August 28, 2006 Report Posted August 28, 2006 Yes, but that's not my fault. It's a limitation in the polling system. Bugger ...there is a time and a place for OOP. I don't think that can be stressed enough, so let me reiterate Jim: THERE IS A TIME AND A PLACE FOR OOP. OOP is a tool, and just like how you can drive nails with the end of a wrench, a hammer is a much better idea. A word from the wise: please don't overuse OO - if you are considering using it, make sure you take the time to plan the architecture first, and then take the time to confirm it's still the most appropriate model. Quote
Aristos Queue Posted August 29, 2006 Report Posted August 29, 2006 THERE IS A TIME AND A PLACE FOR OOP The time is now? The place is your harddrive? Seriously though -- as much of an OOP advocate as I am, I agree. If you're building an app that isn't going to be used but once, or if you're just setting up to take a quick DAQ measurement, or any of a number of low level function VIs, you shouldn't be setting up a class. Too much work for too little return. OOP comes into play when: * the app will be maintained and revised over time * multiple developers are working concurrently on the app * one developer develops, then hands off ownership to another developer * the app is going to be bigger than some threshold, probably somewhere around 10 VIs, or whatever point it is that you can't hold the whole app in your mind simultaneously and need some structure to keep it together. That having been said... OO Programming is not the same as OO Design. And OO Design is eternal and universal. Quote
crelf Posted August 29, 2006 Report Posted August 29, 2006 OO Programming is not the same as OO Design. And OO Design is eternal and universal. Well said! Quote
Jim Kring Posted August 29, 2006 Report Posted August 29, 2006 The time is now? The place is your harddrive? Seriously though -- as much of an OOP advocate as I am, I agree. If you're building an app that isn't going to be used but once, or if you're just setting up to take a quick DAQ measurement, or any of a number of low level function VIs, you shouldn't be setting up a class. Too much work for too little return. OOP comes into play when: * the app will be maintained and revised over time * multiple developers are working concurrently on the app * one developer develops, then hands off ownership to another developer * the app is going to be bigger than some threshold, probably somewhere around 10 VIs, or whatever point it is that you can't hold the whole app in your mind simultaneously and need some structure to keep it together. That having been said... OO Programming is not the same as OO Design. And OO Design is eternal and universal. I feel that the decision of whether to employ OOP is mostly a matter of balancing effort with result. As the OOP tools continue to improve, I will be using OOP more often :-) Quote
Jacemdom Posted August 29, 2006 Report Posted August 29, 2006 OO Design is eternal and universal. Did you forget omnipotent and ominipresent? :worship: Quote
crelf Posted August 29, 2006 Report Posted August 29, 2006 Did you forget omnipotent and ominipresent? :worship: <insert Gregorian chant here> Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.