Greetings,
I am trying to transition from procedural development to OO development.
I'm curious, in the example given is there anything 'wrong' with adding a
parameter to GetGasLeft()? It would have to be optional and default to the
original unit of measurement so as not to break existing code.
getGasLeft("GALLONS")
getGasLeft("METERS")
Thanks,
John
> Note that I said "deprecate", not "remove", so the interface is not
> really changing (in the sense that existing applications won't
> suddenly break), just some new methods are added to deal with an
> ambiguity that has cropped up since design time. So apps could
> continue to call getGasLeft(), but they should be changed to call
> getGasLeftGallons() (which is the same thing), to avoid the ambiguity.
> At some point, the getGasLeft() method might actually be removed (at
> which point non-updated apps would flat-out break), but that's often
> not the way deprecation works.
>
----------------------------------------------------------
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]
