One of the biggest difficulties here is that most of the synonyms for "can be changed" already have meanings in programming contexts... Meanings we'd want to avoid implying, here. That means many otherwise-great options risk too much confusion to be useful. Even Fractal's choice to use 'include' instead of 'with' isn't necessarily all that helpful here. Even so, not proposing options in a brainstorm is how we get deadlock, so here you go:
- Appendable - Combinable - Revisable - Alterable - Assignable - Updatable - Variable - Extensible - Expandable - Embracing - Composable - Evolving (or Evolvable) - Adoptable (or Adoptive) - Insertable - Inductable - Annexible - Coupled My personal favorite, though, is to actually use a suffix instead: LinkWithInterface extends LinkInterface LinkCollectionWithInterface extends LinkCollectionInterface This does have the side effect of diminishing the focus on the key difference between the interfaces, though, by "burying" it in the interface name. So it may not be ideal. Just some thoughts (provided mostly by burying my head in an online thesaurus). - Daniel Hunsaker -- 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/239b7c02-9661-462b-af5f-7da233ce884f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
