On 14/11/2016 17:50, David Négrier wrote:
Implementing libraries MUST support identifiers consisting of the
characters A-Z, a-z, 0-9, _, and . in any order in UTF-8 encoding and a
length of up to 64 characters.
If I read this sentence correctly, this means that one should be able to
*set* in a container any possible identifier from the proposed set of
characters.
Before replying, I'd like to say that I agree that containers should
allow any UTF8 character in keys, of any length.
I simply see no reason to limit them.
If a container uses MongoDB (which doesn't allow `.`) as a backend, for
example, it will be the container's responsibility to encode/decode the
keys.
Of course, since this container only exposes environment variables, and
since environment variables cannot contain ".", it does not fulfill the
criteria to be an eligible PSR-11 container (which makes me sad because
in my opinion, this is a legit use case).
It's the opposite, IMHO. The container supports them (there is no `if`
that checks that). If you decide to put only ASCII keys in there it's
not the container's fault, so it's PSR-11 compatible.
Or maybe I misunderstood your sentence. :)
Bye.
--
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/1db80f11-a9a6-30e5-c347-ae7def19e4fb%40amiran.it.
For more options, visit https://groups.google.com/d/optout.
