return a string. What's the deal here?
I think the return values really should be true and false for this class,
as expected by session_set_save_handler()
Regards,
Drak
Forcing pushes to
one's own topic branches in one's own fork can be acceptable providing
upstream maintainers know before merging (for example squashing some work
after peer review), but not to the central repo without some exceptional
reason - it could cause chaos otherwise.
Regards,
Drak
On 7 March 2012 11:54, Kiall Mac Innes wrote:
> On Wed, Mar 7, 2012 at 6:03 AM, Drak wrote:
>
>> [snip]
>> Forcing pushes to one's own topic branches in one's own fork can be
>> acceptable providing
>> upstream maintainers know before merging (for e
If a commit blob (on the file-system) was altered
manually, your git repo would simply fail to validate the next time you use
it. In every scenario you'd know immediately something was wrong and not
have to go looking for it commit by commit.
Something to consider again in the future at least.
Regards,
Drak
toolsets and services like github.com have made the
entire experience very easy and social.
My main point is, if you want to use DVCS, there is nothing stopping you
doing right now, without asking the PHP team to change the VCS (although I
would hope one day they do).
Regards,
Drak
hing that contribution and making sure it provides a robust
solution to this feature than trying to postpone or find reasons to put this
off.
Regards,
Drak
is
http://ideas.joomla.org makes it very clear what is important to the
wider community or not.
Regards,
Drak
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
icks it up and runs with it ...
> including type hinting ...
If PHP releases new syntax of course the IDE vendors will release
support pronto for it.
Drak
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
or it. I feel like I am stating the obvious :)
If PHP accept the patch (in it's current or a modified form) it should
be feature complete. There is no point neutering a perfectly good
feature at it's inception. Whether it's in the docblock, or as
Guilherme's designed in the
e PHP core? I remember this being discussed at some point.
Drak
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
something like this
http://www.jcp.org/en/jsr/detail?id=250 and possibly others like JSR
175 and 308
There are a few others (google: JSR annotations).
Regards,
Drak
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
to know what
the intention, pros and cons of these methodologies are from an
official internals point of view and if anything has been changed to
over time to make these methodologies more efficient.
Regards,
Drak
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: h
Beans and Eclipse - and already way ahead of the pack is phpStorm
for VCS integration, but it's not free.
Regards,
Drak
Have you guys considered doodle.com? I think you are all stressing way too
much over the voting process. When a vote is closed you can then transfer
the decision to the RFC.
Drak
On 3 June 2011 14:12, Pierre Joye wrote:
> On Fri, Jun 3, 2011 at 10:22 AM, Derick Rethans wrote:
> >
14 matches
Mail list logo
