Anthony Ferrara wrote:
Since you asked me for feedback on how I would suggest improving the
RFC, so here it goes...
Silly question time ...
If I am reading all this correctly we are talking about how something is found
if I have not directly identified that I want to use it?
So if my base fr
David
Sorry, I just RE read your reply. that's basically what you said, so in
essence I agree...
Anthony
On Nov 10, 2011 6:29 PM, "Anthony Ferrara" wrote:
> Well, the problem with adding methods later is that it will fatal any
> class that implements the old one. A big no no.
>
> You could g
Well, the problem with adding methods later is that it will fatal any class
that implements the old one. A big no no.
You could get around that by doing something like traversable. Provide an
empty and non usable core SplAutoloader interface which is typehintable.
Then add a child SplClassAutolo
Surprised to say that I agree on just about everything you mentioned. I
would however love to see a useful autoloader included in core. I have
only one comment below.
> 4. The RFC should avoid implementing any pattern or style that may
> make future feature addition difficult or pose risks towards
2011/11/10 Pierre Joye :
> On Thu, Nov 10, 2011 at 11:13 AM, Patrick ALLAERT
>> Some are blocking because they kinda feel forced if this is introduced.
>> Ignore those, PHP wouldn't have bundled ext/mysql for the same reasons
>> about 15 years ago.
>>
>> I guess that some voted "No" because of lack
On 11/10/11 8:19 AM, Pierre Joye wrote:
What amazes me is this exact argument. We never had, in the whole PHP
history, so many leading projects agreeing on something, together and
propose it to the core. I, for one, have been waiting for that to
happen for years (PEAR, etc.), and now that it is
> 2) This isn't a "bunch" of developers, this is a bunch of the largest> used
> PHP libraries in the world (ZF, Symfony, Doctrine, PPI, Drupal),
Ok, I have to say it... You're a group of people who have done great
things. Good for you. Get over it. Stop trying to use that as a
justification or
Comments are inline.
On Thu, Nov 10, 2011 at 2:19 PM, Pierre Joye wrote:
> On Thu, Nov 10, 2011 at 11:13 AM, Patrick ALLAERT
> wrote:
>
>> You're mixing stuff here.
>> "RFC on PSR-0 support into PHP status" != "PSR-0 status"
>
> I do not. But we are confusing our old vision and what users are lo
Guilherme et al,
Since you asked me for feedback on how I would suggest improving the
RFC, so here it goes...
I think I need to make one thing clear first. I don't think that I
can vote yes for this RFC in principle (I just don't agree this
belongs in core). However, with that said if the RFC w
On Thu, Nov 10, 2011 at 11:13 AM, Patrick ALLAERT
wrote:
> You're mixing stuff here.
> "RFC on PSR-0 support into PHP status" != "PSR-0 status"
I do not. But we are confusing our old vision and what users are looking for.
> However, *how* PSR-0 might be introduced into PHP, for those who uses
>
On Thu, Nov 10, 2011 at 11:00 AM, Stas Malyshev wrote:
> Nobody's blocking anything.
See the votes, that's pretty much us vs the rest. And it is not the
1st time (happened already in the past before we had the RFC process,
so it will become more and more visible.
>> And as far as I can see, the
2011/11/10 Pierre Joye :
> hi Stas,
>
> On Thu, Nov 10, 2011 at 8:17 AM, Stas Malyshev wrote:
>> Hi!
>>
>>> This attitude only makes me lose a lot of time answering questions
>>> instead of focusing on actual RFC stability. I want to propose
>>> something stable, I do not want to be pressured abou
Hi!
But blocking the only thing so many PHP projects have ever agreed on
is a major mistake. And it is a political and religious choice
(religious as in "php does not enforce standard"). Even for something
that does not enforce anything if not used.
Nobody's blocking anything. I don't understa
On Thu, Nov 10, 2011 at 10:36 AM, Pierre Joye wrote:
> hi Stas,
>
> On Thu, Nov 10, 2011 at 8:17 AM, Stas Malyshev
> wrote:
> > Hi!
> >
> >> This attitude only makes me lose a lot of time answering questions
> >> instead of focusing on actual RFC stability. I want to propose
> >> something stabl
hi Stas,
On Thu, Nov 10, 2011 at 8:17 AM, Stas Malyshev wrote:
> Hi!
>
>> This attitude only makes me lose a lot of time answering questions
>> instead of focusing on actual RFC stability. I want to propose
>> something stable, I do not want to be pressured about should the RFC
>> exist or not. I
Hi!
This attitude only makes me lose a lot of time answering questions
instead of focusing on actual RFC stability. I want to propose
something stable, I do not want to be pressured about should the RFC
exist or not. It only delays the real voting results. What I can do to
address this?
I woul
Hi,
@RDohms
What you said is pretty valid. If you're not going to use it, you vote
against it?
You may not use it, but many others can. It's a true state.
@Anthony
I already heard your points many times. I know you're against it.
I also know the voting should be reset, but before the reset, I w
On Wed, Nov 9, 2011 at 8:49 PM, Anthony Ferrara wrote:
> On Wed, Nov 9, 2011 at 5:16 PM, Rafael Dohms
> wrote:
>> On Wed, Nov 9, 2011 at 2:03 PM, Anthony Ferrara wrote:
>
> I am not PSR compliant in either autoloader implementation or class
> implementation. The reason is that over time I have
On Wed, Nov 9, 2011 at 5:16 PM, Rafael Dohms wrote:
> On Wed, Nov 9, 2011 at 2:03 PM, Anthony Ferrara wrote:
>
> You sort of prove my point here, as you actually have your own
> autoloader, which in case you are PSR compliant, you would not need,
> you can still use your bootstrap but no longer
On Wed, Nov 9, 2011 at 2:03 PM, Anthony Ferrara wrote:
> Rafael
>
>> This makes life as a PHP developer much easier and having the standard>
>> "valued" by PHP by having a SplClassLoader that allows any library to> not
>> need to implement a autolaoder if no framework is present allows> for much
On Tue, Nov 8, 2011 at 6:55 PM, guilhermebla...@gmail.com <
guilhermebla...@gmail.com> wrote:
> Hi Nikita,
>
> Thanks.
> It's your option and I won't fight. But it seems my proposal is not yet
> 100%.
> Some things I have either identified or people have reported.
>
> 1- Remove ->register() and ->
Hi!
- I think it's too late in PHP 5.4's release cycle to be proposing
anything for 5.4.
Not talking about the merits of the loader, if it comes into 5.4, that
won't be 5.4.0. Unless we discover some very bad problem, 5.4 is going
into RC tomorrow, which means I will be extremely reluctant t
On 9 November 2011 22:44, Peter Cowburn wrote:
> I am removing my vote due to a particularly annoying aspect of this
> whole RFC/voting structure: the RFC is still in flux!
This is one of the reasons why I've voted -1: there's no way an RFC
should be changing this much (or at all, really) while v
Rafael
> This makes life as a PHP developer much easier and having the standard>
> "valued" by PHP by having a SplClassLoader that allows any library to> not
> need to implement a autolaoder if no framework is present allows> for much
> nicer "plug and play" interaction of libraries, less work
On Wed, Nov 9, 2011 at 12:04 AM, Will Fitch wrote:
> ...
> I have to say, I've never heard the argument, "man, if there's one
> thing I'd like to standardize in PHP, it'd definitely be autoloading
> classes." No, indeed I believe this is a group of frameworks trying
> to implement a standard into
Hi guys,
I am removing my vote due to a particularly annoying aspect of this
whole RFC/voting structure: the RFC is still in flux!
How on earth are we supposed to be able to vote yay/nay on something
if that something keeps changing, or is very poorly defined? I request
that the RFC itself be dis
On 09/11/11 11:24, Christian Kaps wrote:
Hi,
Hi Christian :-),
I'm fine with the most of the implementation. But I have some
suggestions to optimize it.
1. The interface should be named SplClassLoader and the register and
unregister methods should be removed.
It should be possible to de
On 08/11/11 18:39, Nikita Popov wrote:
On Tue, Nov 8, 2011 at 6:28 PM, guilhermebla...@gmail.com
wrote:
Because there's no need to bring to C a single foreach.
Also, if you re-read the RFC, you'll see that SplClassLoader is
extendable for personalized developer needs, such as an addAll or an
A
Hi,
I'm fine with the most of the implementation. But I have some
suggestions to optimize it.
1. The interface should be named SplClassLoader and the register and
unregister methods should be removed.
It should be possible to define class loader implementations without
registering them as
2011/11/8 guilhermebla...@gmail.com :
> Ok... I promised to complete the RFC and here I am.
>
> I wrapped the entire idea, PHP implementation of what I'm proposing all in
> RFC.
> If you're interested, feel free to review the document, highlight if I
> missed something and update/add your votes.
>
I don't argue with your logic and want for standards. I do question
this implementation. This is will not enforce any standards whatsoever
and I feel it serves the need for existing frameworks and
standardizing them.
I have to say, I've never heard the argument, "man, if there's one
thing I'd like
PS: I'd love to point you all this article... this is something that
motivates me to push this RFC forward. =)
http://phpmaster.com/the-importance-of-standards/
Cheers,
On Tue, Nov 8, 2011 at 11:23 PM, guilhermebla...@gmail.com
wrote:
> For all those interested, I implemented what I referred as
For all those interested, I implemented what I referred as item 2:
After some thought it makes sense, but only if interface then defines
the setMode prototype.
The background for this is supported if the user decides to enhance
the base class to support caching, requiring the injection of the
Cac
Hi Nikita,
Thanks.
It's your option and I won't fight. But it seems my proposal is not yet 100%.
Some things I have either identified or people have reported.
1- Remove ->register() and ->unregister(), and make the
spl_autoload_register to support SplClassLoader.
I'm really +0 on this one.
But s
On Tue, Nov 8, 2011 at 6:28 PM, guilhermebla...@gmail.com
wrote:
> Because there's no need to bring to C a single foreach.
> Also, if you re-read the RFC, you'll see that SplClassLoader is
> extendable for personalized developer needs, such as an addAll or an
> APC lookup.
After your changes the R
Hi Nikita,
Because there's no need to bring to C a single foreach.
Also, if you re-read the RFC, you'll see that SplClassLoader is
extendable for personalized developer needs, such as an addAll or an
APC lookup.
Cheers,
On Tue, Nov 8, 2011 at 3:25 PM, Nikita Popov wrote:
> On Tue, Nov 8, 2011 a
On Tue, Nov 8, 2011 at 6:17 PM, guilhermebla...@gmail.com
wrote:
> Remove is useless. conditionally add loaders and you're done.
> AddAll is ok for user land, but we focus on basic stuff, not fluffy
> implementations. It can be easily done in userland.
... Just like the whole rest of the class: al
Ok... I promised to complete the RFC and here I am.
I wrapped the entire idea, PHP implementation of what I'm proposing all in RFC.
If you're interested, feel free to review the document, highlight if I
missed something and update/add your votes.
http://wiki.php.net/rfc/splclassloader
Answering
On 11/07/2011 07:04 PM, Larry Garfield wrote:
> If anything, the low degree of communication between "people who write
> PHP" and "people who write in PHP" is, and has long been, one of PHP's
> great weaknesses. I think this entire thread has shown that very well.
> That is something that needs
On 11/07/2011 01:42 PM, Ferenc Kovacs wrote:
On Mon, Nov 7, 2011 at 7:26 PM, Ivan Enderlin @ Hoa<
ivan.ender...@hoa-project.net> wrote:
On 07/11/11 19:17, Lester Caine wrote:
guilhermebla...@gmail.com wrote:
To participate of php-standards group, feel free to join here:
http://groups.goo
> I updated the RFC a few hours ago based on a lengthy discussion in>
> php-standards.
Point of order. Discussions on RFCs are supposed to happen on the
internals list. That's the point of an open RFC process, so that the
discussion and justification can be made public for all to see. The
RFCs
On Mon, Nov 7, 2011 at 7:26 PM, Ivan Enderlin @ Hoa <
ivan.ender...@hoa-project.net> wrote:
>
>
> On 07/11/11 19:17, Lester Caine wrote:
>
>> guilhermebla...@gmail.com wrote:
>>
>>> To participate of php-standards group, feel free to join here:
>>> http://groups.google.com/**group/php-standards
On 07/11/11 19:17, Lester Caine wrote:
guilhermebla...@gmail.com wrote:
To participate of php-standards group, feel free to join here:
http://groups.google.com/group/php-standards
Not while it's not a php list ...
+1. It would be great if PHP could host this mailing-list. It would be
an ac
guilhermebla...@gmail.com wrote:
To participate of php-standards group, feel free to join here:
http://groups.google.com/group/php-standards
Not while it's not a php list ...
--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electro
guilhermebla...@gmail.com wrote:
Hi Anthony,
On Mon, Nov 7, 2011 at 3:43 PM, Anthony Ferrara wrote:
Actually, I just re-read the RFC again and I noticed something that's
really irksome to me:
Implementation extension
According to new threads in php-standards list, it seems all derived
im
On 07/11/11 19:05, guilhermebla...@gmail.com wrote:
Hi Ivan,
Hi :-),
The PSR-0 went to Final Release 2 years ago.
It's not possible to change it anymore. If you find relevant items,
you can open another PSR for discussion. But be aware that autoloading
ones would be likely rejected since we al
Am 07.11.2011 18:36, schrieb guilhermebla...@gmail.com:
> Point #4 would probably turn ClassLoader useless
... which it is in my opinion hence my request to include that option
in the voting process.
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-
Hi Ivan,
On Mon, Nov 7, 2011 at 3:59 PM, Ivan Enderlin @ Hoa
wrote:
>
>
> On 07/11/11 18:41, guilhermebla...@gmail.com wrote:
>>
>> Hi Ivan,
>
> Hi,
>
>>
>> I updated the RFC a few hours ago based on a lengthy discussion in
>> php-standards.
>> It seems after these 2 years of PSR-0, all the rules
Hi Anthony,
On Mon, Nov 7, 2011 at 3:43 PM, Anthony Ferrara wrote:
> Actually, I just re-read the RFC again and I noticed something that's
> really irksome to me:
>
>> Implementation extension
>
>> According to new threads in php-standards list, it seems all derived
>> implementations have inclu
On 07/11/11 18:41, guilhermebla...@gmail.com wrote:
Hi Ivan,
Hi,
I updated the RFC a few hours ago based on a lengthy discussion in
php-standards.
It seems after these 2 years of PSR-0, all the rules are kept, but
some changes were made to the original code (the one in RFC) to
enhance the s
I don't disagree with your assessment. I would like to add that the
framework standards group, in this case, should consider standardizing
the frameworks rather than PHP based on their needs.
There's no reason the members of your group can't reach a consensus to
develop a loader that is distribute
Actually, I just re-read the RFC again and I noticed something that's
really irksome to me:
> Implementation extension
> According to new threads in php-standards list, it seems all derived
> implementations have included these extensions to original support:
> Multiple paths per namespace
> Si
Hi Ivan,
I updated the RFC a few hours ago based on a lengthy discussion in
php-standards.
It seems after these 2 years of PSR-0, all the rules are kept, but
some changes were made to the original code (the one in RFC) to
enhance the support. They are:
- Multiple paths per namespace
- Silent mode
Hi,
It seems we would never reach some consensus, so I prefer to stick to
the voting process.
Looks like it's another battle between core developers and framework
core developers, where the first ones don't see a benefit at all and
have to opt for a side while the other side is eagerly requesting
On 07/11/11 14:41, David Coallier wrote:
Hey everyone,
Hi David,
After lengthy discussions and various opinion, we believe this issue
has been discussed at length and the PSR-0 has had this standard
effective for the past 1.5 year.
The SplClassLoader RFC has moved to "voting" stage. Please ca
Well, with respect to that, are there any examples of where PHP
currently "reserves the namespace"? I can declare functions/classes
for every single disablable/PECL extension right now. So is there
even a method to "reserve a namespace", yet alone enforce that in
core?
And with respect to the re
Anthony Ferrara wrote:
Lester,
I think he was referring to something like the MySQL/bcmath/etc
extension where it ships in core, but is disabled by default (requires
a compile-time option).
I think what you interpreted it as is basically just what PECL is for
and how it works? Considering that
I know this topic has been discussed enough, but I think one argument
was not brought up yet. The proposed solution has a bad OO design
because it violates against the "Single responsibility principle".
Another issue is that the proposed class is only one possible solution
to load PSR-0 conform
Lester,
I think he was referring to something like the MySQL/bcmath/etc
extension where it ships in core, but is disabled by default (requires
a compile-time option).
I think what you interpreted it as is basically just what PECL is for
and how it works? Considering that it would basically be ju
Sebastian Bergmann wrote:
1- The same as you wrote. Having it in SPL and in PHP 5.4
> 2- Have it in PHP 5.4 as an external extension (FIG, PSR or PSG),
> enabled by default.
> 3- As an external extension, disabled by default. This would require
> PHP core to reserve the namespace for us.
Y
That would be even better
On Nov 7, 2011, at 10:59 AM, Sebastian Bergmann wrote:
> Am 07.11.2011 15:29, schrieb guilhermebla...@gmail.com:
>> 1- The same as you wrote. Having it in SPL and in PHP 5.4
>> 2- Have it in PHP 5.4 as an external extension (FIG, PSR or PSG),
>> enabled by default.
>
Am 07.11.2011 15:29, schrieb guilhermebla...@gmail.com:
> 1- The same as you wrote. Having it in SPL and in PHP 5.4
> 2- Have it in PHP 5.4 as an external extension (FIG, PSR or PSG),
> enabled by default.
> 3- As an external extension, disabled by default. This would require
> PHP core to reserve
On Nov 7, 2011, at 10:50 AM, Anthony Ferrara wrote:
> Well, my only concern with splitting it into the three questions is
> that the RFC specifically mentioned putting it in SPL.
>
> So there wasn't really any discussion or RFC of either of the other
> two points. While it's not really a big de
Well, my only concern with splitting it into the three questions is
that the RFC specifically mentioned putting it in SPL.
So there wasn't really any discussion or RFC of either of the other
two points. While it's not really a big deal, I think that #3 at
least requires some more discussion as it
I agree with Guilherme on this one. The voting objective seems very vague
currently.
On Mon, Nov 7, 2011 at 12:29 PM, guilhermebla...@gmail.com <
guilhermebla...@gmail.com> wrote:
> I'd rather suggest to split this poll into 3 questions:
>
> 1- The same as you wrote. Having it in SPL and in PHP 5
I'd rather suggest to split this poll into 3 questions:
1- The same as you wrote. Having it in SPL and in PHP 5.4
2- Have it in PHP 5.4 as an external extension (FIG, PSR or PSG),
enabled by default.
3- As an external extension, disabled by default. This would require
PHP core to reserve the names
Hey everyone,
After lengthy discussions and various opinion, we believe this issue
has been discussed at length and the PSR-0 has had this standard
effective for the past 1.5 year.
The SplClassLoader RFC has moved to "voting" stage. Please cast your
votes at https://wiki.php.net/rfc/splclassloade
my comments are also inline
> > did you read the blogpost? most of your replies were cowered there.
> >
>
> Yes.
you mean you or André?
>
> "If you use lowerCamelCase on the class names or your namespace, it will
> > (/should) be exactly like on disk as well."
> >
>
> So as previously said,
Guilherme,
> The language is problematic, FIG/PSG are just trying to have zillions
> different implementations. Everyone would expect that language to set
> the standards, avoiding millions of weird pieces of code out there.
Actually, I'd argue that what you're saying here is the exact opposite
o
Guilherme,
What's the status regarding the finalised PSR-0 implementation so we
can hand it over to DavidC to finish the C implementation and apply
this to 5.4 branch.
Cheers,
- Paul
On Fri, Nov 4, 2011 at 5:27 PM, guilhermebla...@gmail.com
wrote:
> Hi Tyra3l,
>
> Comments are inline.
>
> On Fr
Hi Tyra3l,
Comments are inline.
On Fri, Nov 4, 2011 at 8:35 AM, Ferenc Kovacs wrote:
> On Fri, Nov 4, 2011 at 10:33 AM, André Rømcke wrote:
>
>> On Thu, Nov 3, 2011 at 7:30 PM, Anthony Ferrara
>> wrote:
>>
>> > Paul,
>> >
>> > I wasn't saying whether it should be included or not. I was saying
On Nov 4, 2011, at 7:19 AM, Anthony Ferrara wrote:
> Jonathan,
>
>> The problem with spl_autoload_register() is it isn't clear what the
>> autoloading function is supposed to do if the class if not found.
>
> Then that's a documentation problem. If you throw an exception in
> yours, sure that's
Jonathan,
> The problem with spl_autoload_register() is it isn't clear what the
> autoloading function is supposed to do if the class if not found.
Then that's a documentation problem. If you throw an exception in
yours, sure that's going to cause problems for anyone else. It's 100%
possible (a
On Thu Nov 3 03:06 PM, Will Fitch wrote:
> Wouldn't you consider spl_autoload_register an interoperability
> solution? Only your defined autoloading function would then need to
> know how your file system is structured, there'd be no need for
> include_path declarations and you wouldn't have to
On Fri, Nov 4, 2011 at 10:33 AM, André Rømcke wrote:
> On Thu, Nov 3, 2011 at 7:30 PM, Anthony Ferrara
> wrote:
>
> > Paul,
> >
> > I wasn't saying whether it should be included or not. I was saying
> > that performance should not be a justification for it being included.
> > It may be a benefi
On Thu, Nov 3, 2011 at 7:30 PM, Anthony Ferrara wrote:
> Paul,
>
> I wasn't saying whether it should be included or not. I was saying
> that performance should not be a justification for it being included.
> It may be a benefit, but it's a very small side benefit as opposed to
> a primary one.
>
2011/6/27 guilhermebla...@gmail.com :
> Hannes,
>
> There's a RFC covering this. There's a patch also.
>
> https://wiki.php.net/rfc/splclassloader
I do have a few remarks:
1. That is not a *class* loader, that is a loader (also for
interfaces), hence my suggestion s/SplClassLoader/SplLoader/
2. PS
Wouldn't you consider spl_autoload_register an interoperability solution? Only
your defined autoloading function would then need to know how your file system
is structured, there'd be no need for include_path declarations and you
wouldn't have to explicitly declare paths for each class.
On Nov
On Thu Nov 3 11:19 AM, Anthony Ferrara wrote:
>
> But that's besides the point. I just want to emphasize the point that
> performance should not be a criteria for justifying it going into the
> core...
>
There also seems to be the perception among some php devs that autoloading
is now the pre
Paul,
I wasn't saying whether it should be included or not. I was saying
that performance should not be a justification for it being included.
It may be a benefit, but it's a very small side benefit as opposed to
a primary one.
Additionally, I wholeheartedly disagree with one of your points ther
On Thu, Nov 3, 2011 at 3:19 PM, Anthony Ferrara wrote:
> Can I make a point here.
>
> Why the heck are we caring about the performance of the autoloader at
> all here? The filesystem operations necessary (at least the stat()
> call) will greatly dominate any string function. And considering that
On Thu, Nov 3, 2011 at 4:19 PM, Anthony Ferrara wrote:
> Can I make a point here.
>
> Why the heck are we caring about the performance of the autoloader at
> all here? The filesystem operations necessary (at least the stat()
> call) will greatly dominate any string function. And considering tha
I couldn't agree more with Anthony. In conjunction with that, I would continue
to question the full benefit to the community. How many existing code
bases/frameworks out there would implement this in favor of their existing
solution?
Will
On Nov 3, 2011, at 11:19 AM, Anthony Ferrara wrote:
Can I make a point here.
Why the heck are we caring about the performance of the autoloader at
all here? The filesystem operations necessary (at least the stat()
call) will greatly dominate any string function. And considering that
even the biggest framework only has perhaps a few hundred classe
On Thu, Oct 27, 2011 at 4:30 AM, Laruence wrote:
> 2011/10/26 André Rømcke :
> > On Tue, Oct 25, 2011 at 4:39 AM, guilhermebla...@gmail.com <
> > guilhermebla...@gmail.com> wrote:
> >
> >> Hi internals,
> >>
> >> For all those interested, I have updated the RFC with better
> >> explanation, inclu
On 2011-10-28, Nicolas Grekas wrote:
> About PSR-0 and applying the same reasoning, I don't understand why
> the underscore in the namespace part is not replaced by a directory
> separator: because of it's class to path transformation, PSR-0 forbids
> having two different classes named A\B_C and
To me, the interface found at https://wiki.php.net/rfc/splclassloader is
strange :
first, to be consistent with PSR-0, why allow changing the extension where
PSR-0 states that the only valid one is ".php"?
Why also have an interface to change the namespace separator?
Concerning userland specializ
Hello,
> Already answered before. Performance is important. A native C
> > implementation is much faster than a PHP code implementation.
>
> Well, that's always a safe assumption. But a shiny benchmark would be
> useful in this review.
> Interesting hard fact would to be know if -for the overall f
Hello Guilherme,
2011/10/27 guilhermebla...@gmail.com :
>
> PHP-Standard list is also opened.
... since a few days.
But I'll happily take the discussion there. As I feel it doesn't belong here.
Discussing PSR-0 or how it came to be is entirely off-topic (and would be
rude).
We are just discussin
On 2011-10-26, Pierre Joye wrote:
> On Thu, Oct 27, 2011 at 1:07 AM, wrote:
> > 2011/10/26 Matthew Weier O'Phinney :
> > > My main point, however, is that the standard was ratified quite some
> > > time ago already -- we just now have parties interested in creating a
> > > C-level implementation
Hi Mario,
On Wed, Oct 26, 2011 at 9:07 PM, wrote:
> 2011/10/26 Matthew Weier O'Phinney :
>>
>> My main point, however, is that the standard was ratified quite some
>> time ago already -- we just now have parties interested in creating a
>> C-level implementation compatible with the standard to (
2011/10/26 André Rømcke :
> On Tue, Oct 25, 2011 at 4:39 AM, guilhermebla...@gmail.com <
> guilhermebla...@gmail.com> wrote:
>
>> Hi internals,
>>
>> For all those interested, I have updated the RFC with better
>> explanation, included example implementation and also example usage.
>> If you have a
On Thu, Oct 27, 2011 at 1:07 AM, wrote:
> 2011/10/26 Matthew Weier O'Phinney :
>>
>> My main point, however, is that the standard was ratified quite some
>> time ago already -- we just now have parties interested in creating a
>> C-level implementation compatible with the standard to (a) make usa
2011/10/26 Matthew Weier O'Phinney :
>
> My main point, however, is that the standard was ratified quite some
> time ago already -- we just now have parties interested in creating a
> C-level implementation compatible with the standard to (a) make usage
> simpler, and (b) better optimize performanc
On 2011-10-26, André Rømcke wrote:
> --bcaec5216025460b0e04b031fc2a
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> On Tue, Oct 25, 2011 at 4:39 AM, guilhermebla...@gmail.com <
> guilhermebla...@gmail.com> wrote:
>
> > For all those interested, I have up
On Tue, Oct 25, 2011 at 12:49 PM, Benjamin Eberlei wrote:
> I think the following two requirements should be covered by configuration
> aswell:
>
> 1. Have the autoloader be silent, i.e. doing a file_exists() check. API
> idea
> $loader = new SplClassLoader(..., SplClassLoader::SILENT);
> 2. Have
On Tue, Oct 25, 2011 at 4:39 AM, guilhermebla...@gmail.com <
guilhermebla...@gmail.com> wrote:
> Hi internals,
>
> For all those interested, I have updated the RFC with better
> explanation, included example implementation and also example usage.
> If you have any other wishes, doubts, etc, feel f
I think the following two requirements should be covered by configuration
aswell:
1. Have the autoloader be silent, i.e. doing a file_exists() check. API idea
$loader = new SplClassLoader(..., SplClassLoader::SILENT);
2. Have a ASSERT_CLASS_EXISTS mode, i.e. after the require an
"if(!class_exists(
Hi internals,
For all those interested, I have updated the RFC with better
explanation, included example implementation and also example usage.
If you have any other wishes, doubts, etc, feel free to ask on this
thread and I'll quickly answer here and also update the RFC
accordingly.
The url for
>
> Could you open a FR at bugs.php.net and attach the patch to it please?
> Could be easier to track (and the # to the RFC too :)
>
Yeah I'll do that once I have the tests adjusted and once I know the
patch actually works as expected.
--
David Coallier
--
PHP Internals - PHP Runtime Developme
1 - 100 of 119 matches
Mail list logo