Looking at the Scala & Have MoneyTransfer, I find the code odd in that the source Role withdraw function also knows about the destination. I'd have wanted that up another level of abstraction in purely Context code. Just saying I think maybe it could be a road bump for some readers potentially.
Den 30/04/2016 kl. 17.15 skrev Raoul Duke <rao...@gmail.com>:
Looking at the Scala & Have MoneyTransfer, I find the code odd in that the source Role withdraw function also knows about the destination. I'd have wanted that up another level of abstraction in purely Context code. Just saying I think maybe it could be a road bump for some readers potentially.
--
You received this message because you are subscribed to the Google Groups "object-composition" group.
To unsubscribe from this group and stop receiving emails from it, send an email to object-composit...@googlegroups.com.
To post to this group, send email to object-co...@googlegroups.com.
Visit this group at https://groups.google.com/group/object-composition.
For more options, visit https://groups.google.com/d/optout.
Hi Raoul,
I agree with Cope, but I also realize it's possible you missed
some recent discussions about this that were buried in other
threads. Here are some relatively recent posts where I gave my two
cents:
https://groups.google.com/d/msg/object-composition/ABXXVbyOk10/cJE-ZZNkCAAJ
https://groups.google.com/d/msg/object-composition/nnxDYYMC5qc/poosyPCTVcYJ
Looking at the Scala & Have MoneyTransfer, I find the code odd in that the source Role withdraw function also knows about the destination. I'd have wanted that up another level of abstraction in purely Context code. Just saying I think maybe it could be a road bump for some readers potentially.
--