Re: RE: How to generally decide between FACTORY and constructor?
Caleb Cushing <[email protected]>
| Newsgroups | gmane.comp.programming.domain-driven-design |
|---|---|
| Message-ID | <CAAHKNREem3sw_rCQAGeq=F7E2CZLLUa+wSDk69ujj0KiF+E+DA@mail.gmail.com> |
maybe I'm missing something in the factory conversation, and my naivety of JPA, but how does a factory help me in cases where JPA is constructing the class? On Fri, Feb 14, 2014 at 2:25 PM, Raoul Duke <[email protected]> wrote: >> From my point of view, constructors should be dead simple. As soon as they do more than just initializing members, it is time to apply some kind of creational pattern like a dedicated factory. > > i kinda wish there were a language that was like: sorry you cannot > have constructors, you can only have factories, to force us all to > factor the creation stuff out from the get-go. now, what *kind* of > factories is another thing, but at least we'd not have yukky > constructor stuff. :-) > > > ------------------------------------ > > Yahoo Groups Links > > > -- Caleb Cushing http://xenoterracide.com Calendar: https://www.google.com/calendar/embed?src=xenoterracide%40gmail.com&ctz=America/Chicago ------------------------------------ Yahoo Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/domaindrivendesign/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/domaindrivendesign/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo Groups is subject to: http://info.yahoo.com/legal/us/yahoo/utos/terms/