> > >> I'd expect an object implementing a CollectionInterface to be iterable > and > >> to already contain the items in question. The current implementation of > the > >> LinkCollectionInterface though looks more like a CollectorInterface. > >> Something that collects linkInterfaces and can return a > >> LinkCollectionInterface.
> Matthew and I brainstormed a bit more. The only other word we could > come up with that we didn't hate even more than "Collection" was > "Catalog". Which would then result in: > Not against Catalog, personally. However, Andreas did mention Collector as an alternate; is that one of the more-hated designators that were considered? That wasn't clear from the above paragraph... -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/bdf9e79e-c872-4540-bc15-476c2d188725%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
