On 10/4/07, Brian Kotek <[EMAIL PROTECTED]> wrote: > > ]when you make the constructor private (which, in Java, is almost always a > smart design decision because it allows you to encapsulate the creation of > the object and maintain control over what happens during instantiation).
Would you mind explaining that some more? In particular, what about making a constructor private prevents or impedes those goals? Have I taken it out of context? (I did not re-read the entire thread, so please forgive if that is the case) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
