2008/4/28 Rails Trac <[EMAIL PROTECTED]>: > #11481: [PATCH] [TEST] Constructor wrapper should return value > ---------------------------------------------------+------------------------ > Reporter: cch1 | Owner: sam > Type: defect | Status: closed > > Priority: normal | Milestone: 2.x > Component: Prototype | Version: edge > Severity: normal | Resolution: wontfix > > Keywords: TRIVIAL constructor initialize return | > ---------------------------------------------------+------------------------ > Changes (by jdalton): > > * status: new => closed > * resolution: => wontfix > > Comment: > > After some discussions I don't believe this will ever make it into the > core. > > -- > Ticket URL: <http://dev.rubyonrails.org/ticket/11481#comment:9>
In general, having class X being able to return class Y can be very useful (implementing a factory for example). I'm not saying that this SHOULD go in, but what are the primary reasons for NOT putting it in? Thanks. Richard Quadling. -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
