This is a followup to Larry's message here: https://groups.google.com/d/msg/php-fig/L8rDUwRFsOU/AmNE1PlFBgAJ
The spec says: *While ContainerInterface only defines one mandatory parameter in get(), implementations MAY accept additional optional parameters.* Larry says: ** The allowance for additional parameters on get() is worrisome. That implies ANY use of a second or further parameter sets me up for an incompatibility, but implementations are free to add those implementation-specific hooks that I can couple to. I would much prefer to omit that allowance entirely. (Technically optional parameters cannot be prevented, but we shouldn't encourage it.) * When we first released container-interop, we wrote this to tell it was ok to add support for ContainerInterface to already existing containers that did accept more than one parameter for the "get" method (for instance: http://api.symfony.com/2.3/Symfony/Component/DependencyInjection/ContainerInterface.html) Yet, I do agree with Larry. This does not belong to a PSR. Maybe we can simply add a comment about this in the META doc and completely get rid of this sentence. I'm +1 to remove the whole sentence. Anyone has any objection? If not, I'll write a PR. ++ David. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/fd152b09-c31c-4b1a-9e2b-c443ce726acc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
