SCF (or least my understanding of it) is a quasi-dependency injection framework that allows you to decouple module dependencies from your code. The idea here is to make your code not dependent on a specific implementation, in such a way where you can swap implementations when you need to. For example, you might have a set of default implementations that your program uses when it's ran, and when you run unit tests you might swap those out with custom mock implementations that return dummy data. It's a known fact that dependencies slow down unit testing (especially those that do I/O), and you'd be more interested in testing the functionality of your own classes instead of everything it depends on.
On Thu, Oct 14, 2010 at 4:21 PM, Denis Washington <[email protected]> wrote: > Hi, > > Being relatively new to CrystalSpace, I digged a bit deeper into the User's > Manual again and came across the chapter about SCF. While having read it > from beginning to end, I still don't have any clue about what this mechanism > does bring to the table. I mean, what is the benefit to just declaring the > implementing class itself and using that instead of an extra SCF interface? ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[email protected]?subject=unsubscribe
