On Fri, Jul 29, 2016 at 3:02 PM, Théo FIDRY <theo.fi...@gmail.com> wrote: > Although it's not proper english, "Wither" has the advantage to be 1. simple > (with -> wither) and in line with "getter" and "setter". There may be a > better word to describe those non-static factories, but "wither" is good > enough IMO.
As a native English speaker, "wither" has another meaning entirely: to shrivel and die. I'm personally +1 for Evolvable: - EvolvableLinkInterface - EvolvableLinkCollectionInterface > Le mercredi 27 juillet 2016 15:00:29 UTC+1, Woody Gilk a écrit : >> >> Daniel, that's a great list for thought. I particularly like Evolvable. >> >> Maybe the term idempotent fits in here somewhere as well? Calling with* >> methods do not change the underlying object, but return a different >> instance? >> >> I wish there was a well-defined term for "Copy on Write" because that's >> the simplest way I've found to describe how with* methods work. >> >> -- >> Woody Gilk >> http://about.me/shadowhand >> >> On Tue, Jul 26, 2016 at 7:32 PM, Daniel Hunsaker <danhu...@gmail.com> >> wrote: >>> >>> 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+u...@googlegroups.com. >>> To post to this group, send email to php...@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. >> >> > -- > 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/8e9a6492-ddff-40c7-977b-da7666bea139%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- Matthew Weier O'Phinney mweierophin...@gmail.com https://mwop.net/ -- 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/CAJp_myUgeh_g%3DO-bKswG3vNeeC_%3Dwe%2ByY13Za_cuOK-JwCkL-Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
