A P is a P. If you don't use all the properties of a P, that doesn't change what it is. Don't use inheritance, don't use multiple versions, just use a single P class, and use what pieces you need from it for each task.
cheers, barneyb On 9/15/05, Douglas Knudsen <[EMAIL PROTECTED]> wrote: > say teh properties of P are > m = username > n = userid > o = List of HR actions > > No, sometimes I I want to just build a report involving Ps and only > need username and userid. Other times I may need one instance of P > that has the list of HR actions. > In short, I;m wondering if I can avoid having multiple objects thate > are all just variations of P. I suupos I can use some inheritance > with P. Have P be the parent with teh common properties, then extend > P to P1, P2, or P3 as needed adding teh other properties. > > being a little new to the full blown OOP stuffs, just wondering about > an approach. > > DK > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
