+0 Joomla
Am Montag, 31. Oktober 2016 22:15:59 UTC+1 schrieb Matthew Weier O'Phinney:
>
> Per the by-laws, the required review period has passed for the
> proposed standard PSR-13 (Link Definition Interfaces). No changes have
> been made in the past two weeks since re-opening the review period.
+1 PyroCMS
On Monday, October 31, 2016 at 4:15:59 PM UTC-5, Matthew Weier O'Phinney
wrote:
>
> Per the by-laws, the required review period has passed for the
> proposed standard PSR-13 (Link Definition Interfaces). No changes have
> been made in the past two weeks since re-opening the review
+1 Zikula
--
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
+1 Stormpath PHP SDK
On Monday, October 31, 2016 at 5:15:59 PM UTC-4, Matthew Weier O'Phinney
wrote:
>
> Per the by-laws, the required review period has passed for the
> proposed standard PSR-13 (Link Definition Interfaces). No changes have
> been made in the past two weeks since re-opening
Hi,
I kind of agree with @GeeH here.
> 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
+1 from Phalcon
On Monday, 31 October 2016 16:15:59 UTC-5, Matthew Weier O'Phinney wrote:
>
> Per the by-laws, the required review period has passed for the
> proposed standard PSR-13 (Link Definition Interfaces). No changes have
> been made in the past two weeks since re-opening the review
Sorry, reading that back (which I should have done before posting) I
realise I worded that incredibly badly. Let me rephrase.
> 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
I'm worried by this suggested change. We tried doing something similar in
Zend ServiceManager 2.0 and had to wait until 3.0 to be able to fix the
mistake. I don't understand why any legal string in PHP can't be a
container key. Limiting the range of characters in a legal key is an
