Mark, just a quick Q: are you really sure you want to extend CFC's? inheritance has some really good uses but can be easily over-used and tie the framework in knots (extend->extend->extend...etc). just because you can doesn't mean you should, although (of course) it's perfect for some designs
Is there a particular design pattern you want to follow? or problem to solve? just a thought cheers barry.b -----Original Message----- From: Mark Mandel [mailto:[EMAIL PROTECTED] Sent: Tuesday, 27 July 2004 3:35 PM To: CFAussie Mailing List Subject: [cfaussie] RE: CFC Abstract Base Class yeah - seems that the best way is to implement abstract methods within the cfc, rather than attempt to make the CFC abstract in an of itself (Without developing some sort of kernal). Thanks guys, Mark On Tue, 27 Jul 2004 15:21:56 +1000, Barry Beattie <[EMAIL PROTECTED]> wrote: > >> Just having empty methods that only throw an exception upon being > called is most likely all you'll really need--and probably the most > practical. > > agreed: > > this example (below) is from > http://www.sys-con.com/coldfusion/article.cfm?id=606 > > and shows the empty method in a base class > > <cfcomponent displayname="abstractStrategy"> > <cffunction name="Execute" access="public"> > > <cfabort showerror="This Method is Abstract and needs to be > overridden"> > > </cffunction> > </cfcomponent> > > just my 2c worth > barry.b -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
