Hi!
> note that we have this functionality already:
>
> $ php -r 'class A { const C = FOO; } define("FOO", 23); echo A::C;'
> 23
>
> The first fetch will resolve that.
This is true, but what happens is that "FOO" is stored and then resolved
on fetch with direct lookup. Now, if C = M_PI/2, what
On Fri, Aug 16, 2013 at 1:00 AM, Sara Golemon wrote:
> I wasn't going to bring this up, but an intersectional idea I had a few
> years ago Static Constructor. Just like an instance constructor, but
> called on initial load.
>
> class Foo {
> public static __static_construct(/* no args all
if(true) return;
> class Foo {
> const halfpie = M_PI/2;
> }
>
> Oooh, excellent point. Wave a finger and tell the user not to do that?
I wasn't going to bring this up, but an intersectional idea I had a few
years ago Static Constructor. Just like an instance constructor, but
called on init
On Thu, 2013-08-15 at 16:42 -0700, Stas Malyshev wrote:
> Hi!
>
> > Though obv, in reality we wouldn't use runkit_constant_add(), it'd be a
> > new opcode which had the same effect. This is basically transparent to
> > opcode caches, allows the constant to actually change based on runtime
>
> If
Hi!
> Though obv, in reality we wouldn't use runkit_constant_add(), it'd be a
> new opcode which had the same effect. This is basically transparent to
> opcode caches, allows the constant to actually change based on runtime
If the class definition can actually change at runtime, I think it'd
mak
I have mixed emotions on the yes/no side of things, but on the "how" side,
I think we can do this fairly easily.
During parse, when a non-scalar const expression is encountered, the actual
binding to the class is deferred, and bytecodes are emitted in the "(main)"
function. To put it in psuedo-co
On Thu, August 15, 2013 20:45, Johannes Schlüter wrote:
> On Thu, 2013-08-15 at 20:19 +0200, Jordi Boggiano wrote:
>
>>
>> And to ensure you never push garbage by accident, run this to tell git
>> to always only push the branch you're on when you run `git push`:
>>
>> git config --global push.defau
On Thu, 2013-08-15 at 20:19 +0200, Jordi Boggiano wrote:
>
> And to ensure you never push garbage by accident, run this to tell git
> to always only push the branch you're on when you run `git push`:
>
> git config --global push.default current
Good tip. I wasn't aware of that setting. Mind
On 15.08.2013 19:55, Johannes Schlüter wrote:
> Important: To ensure you don't push them by accident please run this
> command to delete them from your local clone:
>
> $ git branch -d 5.3 5.4 5.5
> Deleted branch 5.3 (was 15b554c).
> Deleted branch 5.4 (was bcdac75).
> Deleted branch 5.5 (was 4c7
Hi,
there were branches with the names
5.3
5.4
5.5
in our main repository. This was confusing with PHP-5.x which we use. As
those where full merged they were most likely pushed by accident. I have
deleted them from the repo.
Important: To ensure you don't push them by accident please run
Hello internals,
About 3 weeks have passed since I announced the use_function RFC. A number of
issues were raised, and I believe all of them have been resolved at this point.
I would like to initiate the voting phase.
RFC: https://wiki.php.net/rfc/use_function
Patch: https://github.com/php/php-
On 15 August 2013 15:23, Igor Wiedler wrote:
> Hi Peter,
>
> This *is* the [VOTE] thread. Am I missing something? :)
>
Stupid Gmail! :)
>
> Regards,
>
> Igor
>
> On Aug 15, 2013, at 4:20 PM, Peter Cowburn wrote:
>
> > Don't forget to create a new [VOTE] thread (unless you already have, and
>
On 15 August 2013 15:23, Igor Wiedler wrote:
> Hi Peter,
>
> This *is* the [VOTE] thread. Am I missing something? :)
>
The vote is announced on the mailing list in a separate thread by sending
an email with the subject *[VOTE]*. It should reference the RFCs being
voted on and if there are differ
Hi Peter,
This *is* the [VOTE] thread. Am I missing something? :)
Regards,
Igor
On Aug 15, 2013, at 4:20 PM, Peter Cowburn wrote:
> Don't forget to create a new [VOTE] thread (unless you already have, and my
> inbox is just being slow today).
--
PHP Internals - PHP Runtime Development Mai
On 15 August 2013 15:08, Igor Wiedler wrote:
> Hello internals,
>
> About 3 weeks have passed since I announced the use_function RFC. A number
> of issues were raised, and I believe all of them have been resolved at this
> point. I would like to initiate the voting phase.
>
> RFC: https://wiki.ph
Hello internals,
About 3 weeks have passed since I announced the use_function RFC. A number of
issues were raised, and I believe all of them have been resolved at this point.
I would like to initiate the voting phase.
RFC: https://wiki.php.net/rfc/use_function
Patch: https://github.com/php/php-
I was about to make the same point as Johannes. Trying all possible variants in
the autoloader is simply too slow (and in fact the main reason why we don't
have function autoloading). On the flip-side, the current proposal would allow
adding function autoloading more easily in the future.
Anoth
On Thu, 2013-08-15 at 14:11 +0100, Marcello Duarte wrote:
> Hi,
>
> Are there any thoughts regarding importing multiple functions of a
> namespace with a wildcard?
>
> A use case being, for example, assertions from a testing framework.
>
> use (or use function) TestingFramework\Assertions\ here>
On Thu, Aug 15, 2013 at 3:11 PM, Marcello Duarte
wrote:
> Hi,
>
> Are there any thoughts regarding importing multiple functions of a
> namespace with a wildcard?
>
> A use case being, for example, assertions from a testing framework.
>
> use (or use function) TestingFramework\Assertions\;
> // in
Hi,
Are there any thoughts regarding importing multiple functions of a namespace
with a wildcard?
A use case being, for example, assertions from a testing framework.
use (or use function) TestingFramework\Assertions\; // in
java * is used for wildcard
Regards,
Marcello
On 15 Aug 2013, at 14:
Hi Daniel,
Thanks for the suggestion. Since it is less straight-forward I would rather
just move forward with the current syntax. I'd hate to see the proposal
rejected because people did not like the syntax.
Regards,
Igor
On Aug 8, 2013, at 10:30 PM, Daniel Bingham wrote:
> Hey Igor,
>
> I
Apologies this appears to have double postedSent from Yahoo! Mail for
iPhone
https://bugs.php.net/bug.php?id=62853
"A Virtual List View control response includes the total number of entries in
the virtual list view used.
An additional function is needed to get to that response, and be able to
efficiently list a properly paginated ($1 to $2 entries of $3 total) LDAP
dir
https://bugs.php.net/bug.php?id=62853
Originally produced and submitted by vanmeeuwen
Can we have this patch checked for inclusion?
We cannot do paginated responses properly without it.
Kind Regards,
Henry Fallon
On Tue, Aug 13, 2013 at 6:15 PM, Matthieu Napoli wrote:
> array_unique() is perfect for removing duplicates in a string array, but
> not so great for an array of objects.
>
> SORT_REGULAR was added to compare items without casting them to string.
> However it uses the "==" comparison operator.
>
25 matches
Mail list logo
