🚀 go-pugleaf

Andy Bulka wrote:
> I've just been using the "Change Unidirectional Association to
> Bidirectional" on p199 of M. Fowler's Refactoring book.
[snip]
> So anyway, turning our attention back to the ONE-to-many (which ends up not
> being so elegant, once you flesh it all out - that's my claim...)   I went
> ahead and invented/implemented the 'missing' removeOrder() method  thus: 

[minor corrections to the example method]
> class Customer ...
>  void removeOrder( Order arg ) {
>   _orders.remove( arg );
>   arg._customer = null;
> }

actually you should be able to do the above with:
    void removeOrder( Order order ) {
        order.setCustomer(null);
    }

which would keep all the association-controlling logic in the
'setCustomer' method.  Since this is a nice simple one-liner, it would
be good if it was in the book, but it was 430 pages as is :-) and he may
have thought the one-liner was apparent.

--Mark
mark.fussell@chimu.com

  i   ChiMu Corporation      Architectures for Information
 h M   info@chimu.com         Object-Oriented Information Systems
C   u    www.chimu.com         Architecture, Frameworks, and Mentoring