Title: Re: [CFCDev] More CFMX Excellence with Component Inheritance
|
Amen!
Sean showed
an interface enforcement mechanism a while back at BACFUG using meta data.
But, the problem is that the overhead of the runtime checking was so high that
it was almost never worth it. Or, did you have something else in
mind?
So, this is getting pretty old...
Can we just say that CFInclude in CF6.1 needs better docs and move
on? Some of us don't think that using includes as a way of chunking code
is good practice, others think it is essential but I think we all agree that
it would be good if the way it was written up included both its within-CFC
behaviour and an explanation of why it is that way (such as that provided by
Sean earlier). Those that are motivated, write down what you want in the next
rev of the docs and submit it to MM...
Other than that, this really isn't going anywhere. Anyone wanna talk about
building a framework so that we can enforce interfaces for
components?
|
<<attachment: winmail.dat>>
