8... just something to think about.
Regarding Rasmus' first post, I am:
+1 removal of register globals
+1 removal of magic_quotes
+1 removal of really old deprecated functions
and have nutral feelings about the rest. I'm happy with whichever
provides the most simplicity and best perfo
sson
from Perl on this one. Here is how we turn on/off warnings, lexically:
use warnings;
- sebastian
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Wow, it'll be just like perl! this is so great.
On 10/28/05, James Crumpton <[EMAIL PROTECTED]> wrote:
> Andi Gutmans wrote:
> > I don't think it's a matter of giving the engine a try. I think we first
> need
> > to make a decision what the best way to go is and then we can discuss
> > impleme
Lexical variables would be nice.
On 10/28/05, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> Hi Cristiano,
>
> Alex sent a patch to the list a while ago which forces the memory
> allocator to return memory to the system. However, in your case, I
> think you might be just having PHP variables "leaking".
Gutmans <[EMAIL PROTECTED]> wrote:
> What do you mean?
>
> At 06:50 PM 10/28/2005, Sebastian wrote:
> >Lexical variables would be nice.
> >
> >On 10/28/05, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> > > Hi Cristiano,
> > >
> > > Ale
I still think // and //= would be the most reasonable. They involve
the least amount of syntax and // looks similar to ||
On 10/29/05, Greg Beaver <[EMAIL PROTECTED]> wrote:
> Sara Golemon wrote:
> >>> Evaluating an idea based on it's syntactic similarities to other
> >>> languages is complete and
whoops, forgot about comments.
On 10/29/05, David Zülke <[EMAIL PROTECTED]> wrote:
> You are joking, aren't you?
>
> - David
>
>
> > -Original Message-
> > From: Sebastian [mailto:[EMAIL PROTECTED]
> > Sent: Sunday, October 30, 2005 12
Given that // is not acceptable, as others sarcastically reminded me,
and that this introduces new sytax, I think it might be best just to
add more functions. I don't think something like
> $d = first-existing: $a, $b, $c;
is any better than first_existing($a, $b, $c), and the former happens
at t
But what about the use of ? as an infix operator? that wouldn't work
out so well because of the ternary ?:
On 10/29/05, Arpad Ray <[EMAIL PROTECTED]> wrote:
> For the assign-if-not-set operator, I like the idea of:
>
> $foo ?= 'bar';
>
> ? implies a condition, and the = immediately following will
What about a similar construct for checking truth? eg,
$foo = first_true($bar, $baz, $bang);
returns the value of the first variable that passes the if(isset($var)
&& !empty($var)) test.
On 10/31/05, Ford, Mike <[EMAIL PROTECTED]> wrote:
> On 29 October 2005 22:56, Greg Beaver wrote:
>
> > For
It's used for shell execution stuff.
Perl did something similar and quickly regretted it
On 11/28/05, Marian Kostadinov <[EMAIL PROTECTED]> wrote:
> Is ` (back quote) suitable for namespace separator? I cannot remember
> just now if it was used somewhere.
>
> 2005/11/28, Ron Korving <[EMAIL PROTE
ew
On 11/28/05, Bart de Boer <[EMAIL PROTECTED]> wrote:
> I'm sorry if I say stupid stuff. My previous post actually was the first
> post I've ever made to a newsgroup! Please bare with me while I adjust
> to the etiquettes. :)
>
> Anyway. Somebody has probably already suggested this. But how abou
ss->do();
---
could be made easier and more readable:
---
$class=new class;
with($class)
{
do_something();
do_more();
do();
}
---
greetings
Sebastian
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://ww
h Schindler" <[EMAIL PROTECTED]>
To: "Sebastian" <[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, October 10, 2007 6:08 PM
Subject: Re: [PHP-DEV] new feature -> with()
>
>> ---
>> $class=new class;
>>
>> with($class)
>&g
it would be better to remove the Boolean check feature and
make it a simple ifsetor() without the E_NOTICE again.
For those of you who have not heard of it heres an example:
Greetings
Sebastian
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
Plus as it is a constant it's value cannot be changed in the context of the
object.
However you could implement a method for this, e.g. get_status(); which then
returns an array. But the final keyword would be more comfortable....
"Sebastian Schneider" <[EMAIL PROT
hi,
why isn't it possible to assign class constants like this:
class test
{
const
DIR='dirname'.DIRECTORY_SEPARATOR.'anotherdirname'.DIRECTORY_SEPARATOR;
}
is there some performance issue?
anyone ever tried this or was there a discussion about it? i would find this
very useful.
hi,
PHP6 still replaces "." with an underscore in variables from outside. this
is an old behavior forced by register globals so i would say its a bug since
"." is valid in array keys.
for sample:
call a script like http://www.example.com/?my.var=1
now $_GET will look like this:
Array ( [my_v
Hi,
i just found it's really annoying that you can't throw exception in the
context of __toString(). This makes it nealy impossible to work with
__toString() because you'll have to watch not to throw exceptions (which is
even more annoying..). Could this be adressed?
Greetings
--
PHP Inte
new features its "just" an
rewrite of version 1. alas, an exception is a direct break of code
execution, so i actually cant understand the limitations. it should at least
go to next years "summer of code" of google. would be interesting.
thanks.
Sebastian
""Guilhe
> The PHP soap implementation is very fast by the way ... my benchmarks
> indicated 3-4ms request times on the LAN (without doing anything useful
> inside the request). This compares to over 30ms for the
> mod_perl/Soap::Lite implementation (and I haven't tested Java or .Net)
Can you provide code
On 02/06/2015 10:22 PM, Nikita Popov wrote:
> After much initial reluctance, I've voted in favor of this RFC.
After reading your email, Nikita, I deleted my vote (it was no before).
I will review the RFC again, with your arguments (and others) in mind
and maybe I'll come to a different conclusi
Am 07.02.2015 um 02:08 schrieb Sebastian Bergmann:
> After reading your email, Nikita, I deleted my vote (it was no before).
> I will review the RFC again, with your arguments (and others) in mind
> and maybe I'll come to a different conclusion.
I have voted (no) again.
I still
Am 09.02.2015 um 15:50 schrieb Pierre Joye:
> Not strict? You loose me here.
I want support for scalar types in signatures. I want these type
declarations to be strictly enforced. This is not wanted and not
proposed by the RFC. Hence my vote.
--
PHP Internals - PHP Runtime Development Mailing
Am 17.02.2015 um 10:51 schrieb Lester Caine:
> It seems not even running distclean clears down everything that needs
> removing for some of the changes currently going through. ./vcsclean
I stopped using distclean / vcsclean a while ago. "git clean -xdf"
does the trick for me.
--
PHP Internals
While working on PHPUnit today I noticed one test of its own test
suite failing on PHP 5.6.6 that passes on PHP 5.6.5. The details of
this can be found at
https://github.com/sebastianbergmann/phpunit/issues/1630
Florian Margaine reduced the problem to the following minimal,
self-contained
Am 27.02.2015 um 09:14 schrieb Remi Collet:
> Hmmm http://3v4l.org/QST64
No clue why PHP 5.6.5 seems to have worked for that reproducing script
here earlier. Tried it again and, of course, it also fails with "my"
PHP 5.6.5.
Looks the like the reproducing script was not the right one. :-/
--
Am 27.02.2015 um 09:30 schrieb Xinchen Hui:
> maybe related to your own build?
The test in the PHPUnit test suite fails with
PHP 5.6.6 (cli) (built: Feb 19 2015 09:44:29)
Copyright (c) 1997-2015 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2015 Zend Technologies
with Xdeb
Am 27.02.2015 um 09:53 schrieb Xinchen Hui:
> I noticed different version of xdebug, could you try without it?
Thank you for bringing Xdebug to my attention. You are right, it
appears to be related to Xdebug.
Without Xdebug
$ php -v
PHP 5.6.6 (cli) (built: Feb 19 2015 09:44:29)
Copyr
Am 23.02.2015 um 19:15 schrieb Nikita Popov:
> Voting on the engine exceptions RFC, which proposes to convert existing
> fatal and recoverable fatal errors into exceptions, has opened:
>
> https://wiki.php.net/rfc/engine_exceptions_for_php7#vote
>
> The primary vote requires a 2/3 majority, a
Am 27.02.2015 um 16:12 schrieb Anthony Ferrara:
> Thank you for sharing your code. I look forward to playing with it.
>
> Perhaps after 7 stabilizes (and ships) you could write up your
> thoughts around it? Why decisions were made and the findings that you
> have?
What Joe and Anthony said :-) T
Am 27.02.2015 um 01:29 schrieb Matthew Weier O'Phinney:
> - PHPUnit passes a boolean false to `debug_backtrace()`... which is documented
> as expecting an integer! (There are actually several constant values it
> accepts, all of which are integer values.) In this case, PHPUnit is relying
> on
Am 28.02.2015 um 01:57 schrieb Larry Garfield:
> The RFC is currently in voting, so editing it directly is a no-no. A new,
> short RFC, please. (Exception implements Throwable, Error implements
> Throwable sounds good to me. Should we ask about SomeUserspaceClass
> implements Throwable, or will
Am 04.03.2015 um 09:52 schrieb Nikita Popov:
> So, tl;dr: I think the patch is too risky. Even if we can make sure that
> we've covered all the current edge-cases and don't regress anything, I'm
> afraid that this will cause complications with future changes. This ends up
> replicating too many par
Am 23.02.2015 um 19:15 schrieb Nikita Popov:
> Voting is open until 2015-03-08.
Voting ends today and it looks like the RFC will be accepted. How
should we proceed with regards to the comments I made in
Message-ID: <54f07fc7.8050...@php.net>
Date: Fri, 27 Feb 2015 15:31:35 +0100
Guilher
Am 09.03.2015 um 09:44 schrieb Matteo Beccati:
> I like the approach. I'm no lexer expert but the new PR seems much nicer.
> Moreover, I like the feature itself but previously voted no on the
> implementation. I've therefore switched my vote to a "yes".
Dito.
--
PHP Internals - PHP Runtime Deve
Am 09.03.2015 um 12:40 schrieb Dan Ackroyd:
> So even though I hope we can clean up the exception hierarchy, merging
> the engine exceptions is the right choice imo.
Sounds reasonable to me. I'm wondering, though, whether we really need
an additional RFC for the change I suggested as nobody spok
Am 27.02.2015 um 15:47 schrieb Jordi Boggiano:
> quickly draft another RFC to amend that part
So who will draft the RFC for
* Introduce a Throwable interface
* Let Exception implement the Throwable interface
* Introduce an Error class that implements the Throwable interface
* Use Err
Am 15.03.2015 um 08:07 schrieb Sebastian Bergmann:
> So who will draft the RFC for
>
>* Introduce a Throwable interface
>* Let Exception implement the Throwable interface
>* Introduce an Error class that implements the Throwable interface
>* Use Error class
What is the minimum version of GCC required to build PHP?
I am asking because using GCC 2.95.3 and GCC 3.4.0 I get errors related
to the usage of intptr_t (see http://pastebin.com/9Gn0AAXA).
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsu
Am 15.03.2015 um 15:34 schrieb Sebastian Bergmann:
> I am asking because using GCC 2.95.3 and GCC 3.4.0 I get errors related
> to the usage of intptr_t (see http://pastebin.com/9Gn0AAXA).
Over in Room 11, Michael just pointed out that this could be related
to php_stdint.h.
--
PHP Int
Am 15.03.2015 um 16:36 schrieb Sebastian Bergmann:
> Over in Room 11, Michael just pointed out that this could be related
> to php_stdint.h.
Okay, this does not seem to be related to the GCC version but rather
to the fact that some int types etc. are not defined on/for my platform.
If
Am 16.03.2015 um 07:41 schrieb Xinchen Hui:
> what is the link problems?
http://pastebin.com/Tk1kaipQ
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Am 15.03.2015 um 09:24 schrieb Pavel Kouřil:
why global namespace?
Because that is where, as of today, built-in classes, interfaces,
functions, etc. go.
The introduction of a PHP namespace, for instance, would be the topic
of a separate RFC.
--
PHP Internals - PHP Runtime Development Mai
Am 15.03.2015 um 08:27 schrieb Sebastian Bergmann:
It was my idea, after all, only fair that I invest the time to make
it into an RFC: https://wiki.php.net/rfc/throwable
The vote for this missed the boat for the PHP 7 deadline. However, if
we really want to do this we should do it in PHP 7
Am 21.03.2015 um 18:05 schrieb Sebastian Bergmann:
> The vote for this missed the boat for the PHP 7 deadline. However, if
> we really want to do this we should do it in PHP 7 or not at all (at
> least not for a long time) due to BC breaks.
>
> Thoughts?
ping
--
PHP Internal
Am 30.04.2015 um 02:50 schrieb Stanislav Malyshev:
> I like the idea, however we do have the deadline and the
> deadline has been passed. So I wonder if we can't keep it for 7.1
That means introducing a change in 7.0, changing it and deprecating
part of it in 7.1, and removing said part in 7.2/8
Am 30.04.2015 um 14:30 schrieb Julien Pauli:
> We could make an exception (sic !) and add the Throwable interface to PHP7,
> even after feature freeze, because it is an easy pick and having a clear
> Exception model for 7.0 is to my opinion very important.
+1, couldn't agree more.
--
PHP Intern
Am 01.05.2015 um 07:08 schrieb Pierre Joye:
> Let do a rfc to accept to post pone features freeze with a list or a single
> RFC.
Do you volunteer to draft that RFC?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Am 09.05.2015 um 06:38 schrieb Stanislav Malyshev:
> OK, if there's consensus we can go forward with this, then let's just do
> that ASAP.
Can you implement this? Thanks!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Am 13.05.2015 um 07:40 schrieb Stanislav Malyshev:
> I can, except that I'm pretty busy right now. But probably will have
> some time on the weekend, so I've put it on my todo list.
Thanks!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.p
Am 13.05.2015 um 08:30 schrieb Pierre Joye:
> Why don't you do it? You have access and you are a very good writer.
> No big C knowledge required either in this case :)
TBH, until know I did not think I would be capable of doing it
myself. I'll look into it now.
--
PHP Internals - PHP Runtime D
Am 13.05.2015 um 08:30 schrieb Pierre Joye:
> Why don't you do it? You have access and you are a very good writer.
> No big C knowledge required either in this case :)
There was/is consensus on what I proposed back in February:
* Introduce a Throwable interface
* Let Exception implement th
On 05/16/2015 10:57 PM, Stanislav Malyshev wrote:
> I am assuming we have broad consensus about the move from BaseException
> to Throwable. I've looked at the patch at
> https://github.com/php/php-src/pull/1282 and it seems pretty close to
> what we want to me. The only difference is that
> https:/
On 05/17/2015 12:15 AM, Stanislav Malyshev wrote:
> Where is it? I'd like to see it.
https://github.com/php/php-src/pull/1284
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Would be nice if somebody could have a look at
https://bugs.php.net/bug.php?id=69180 -- thanks!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 05/29/2015 08:59 AM, Xinchen Hui wrote:
> Actually, I had looked it, but there is no such Infos can be
> used after compiling is done in current traits design, so
But calling C::bar() works, so PHP knows that there is a method named
"bar". Yet the Reflection API says that two methods nam
Am 31.05.2015 um 13:02 schrieb Xinchen Hui:
> yeah, PHP knows, but only in lowercase
> it's not the right thing we need..
Better the right name in lowercase than the wrong name, no? :)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.p
7773f0 in php_execute_script ()
#31 0x00868751 in do_cli ()
#32 0x00440d9b in main ()
$ /home/sb/php-7-debug phpunit
PHPUnit 5.0-gabce26e by Sebastian Bergmann and contributors.
Runtime: PHP 7.0.0-dev
Configuration: /usr/local/src/ph
Am 14.06.2015 um 07:29 schrieb Sebastian Bergmann:
> I have run across a weird segfault with the current master when trying
> to run PHPUnit (using PHPUnit's own test suite). Weird because I get a
> segfault immediately on startup with a release build and a segfault much
> later w
Am 14.06.2015 um 07:55 schrieb Xinchen Hui:
> maybe related to this : 3cfa58367b1b85d346d9be6cf9ae116c63571247
Yes, reverting that commit fixes it. Thanks for the pointer!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Am 16.06.2015 um 18:10 schrieb Ferenc Kovacs:
> did not have more time to test though, so any feedback is appreciated.
I still think that the right solution would be to simply not bundle /
install PEAR anymore.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
Am 17.06.2015 um 23:30 schrieb Anthony Ferrara:
> Instead, I think we should solve the problem with education. Perhaps
> the documentation can better detail out why devs shouldn't directly
> throw exception but instead use typed exceptions...?
I remember "all hell breaking lose" when I disallowed
PHP-FPM / FastCGI processes to clear
the realpath cache? If not, I think this should be added :-)
Thanks!
Sebastian
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 06/19/2015 05:46 PM, Rasmus Lerdorf wrote:
> I think this is a symptom of doing deploys incorrectly.
You are right, of course. Thank you for pointing out this layer 8
problem :-) No clue why I did it different (read: stupid) for a
private project when I know better. Oh, well.
--
PHP Intern
Am 11.07.2015 um 19:53 schrieb S.A.N:
> It will be useful for autocomplete in IDE
That argument is bogus since proper IDEs (PhpStorm, fex.) leverage
docblock annotations for that already.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.ph
On 07/28/2015 04:45 PM, Johannes Schlüter wrote:
> (and yes - developers doing this might be an interesting targeted
> attack vector. Malicious code there knows where the developer keeps
> the source tree and might inject bad code into the codebase which we
> notice only with good review of commits
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/28/2015 05:22 PM, Johannes Schlüter wrote:
> An approach might be to remove the automatic download and
> instructing the user to put the file there manually if this is seen
> as important.
+1
--
PHP Internals - PHP Runtime Development Maili
Am 17.08.2015 um 16:00 schrieb Derick Rethans:
> Actually, I don't call this intended. This is just as much as a BC break
> as the original implementation where Errors where also Exceptions. IMO,
> set_exception_handler() should be changed - with my preference it not
> capturing Error, and inste
Am 18.08.2015 um 16:06 schrieb Anatol Belski:
> Diff:
> diff --git a/configure.in b/configure.in
> index 8907852..033c754 100644
> --- a/configure.in
> +++ b/configure.in
> @@ -120,7 +120,7 @@ int zend_sprintf(char *buffer, const char *format, ...);
> PHP_MAJOR_VERSION=7
> PHP_MINOR_VERSION=0
>
Am 18.08.2015 um 19:07 schrieb Anatol Belski:
> Do you have some impregnable issue in mind preventing to do this?
No, I was just surprised. Must have missed the announcement.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Am 18.08.2015 um 19:07 schrieb Anatol Belski:
> Do you have some impregnable issue in mind preventing to do this?
Hm, maybe: what about the need for set_throwable_handler() that was
recently raised as a topic?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http:
Am 19.08.2015 um 16:09 schrieb Niklas Keller:
> TBH, I'd rather take the time and have a delayed release without a hurry
> than shipping a final version with unresolved problems. Having a schedule
> to follow is nice, but you should rethink the schedule when problems arise
> instead of following it
Hi
2011/12/6 Rasmus Schultz
> On Tue, Dec 6, 2011 at 3:45 AM, Christian Kaps >wrote:
>
> > Hi,
> >
> > I also find this syntax confusing and I think it has a huge WTF factor.
> >
> > Some thoughts about the syntax:
> > - At the first glance, it isn't clear which visibility the getter or
> > set
for an
example of how this affects PHPUnit.
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
2011/12/22 Dmitri Snytkine
> The return type hinting is probably the biggest thing happening in php in a
> long time.
> Is this too good to be true?
>
> With return type hinting I can see a huge improvenets in php IDEs in
> spotting errors. Also it will be much easier to auto generate wsdl files
the above code, the caller needs to cast and the writer of the
age_check() function has to copy/paste/adapt these checks to all the
correct places ...
I am not advocating type hints for scalars, I am just saying that this
argument is not really a good one against it.
--
Sebastian Bergmann
too, like
> fedora 14 and ubuntu 11
> This fixes build failures for ext/intl and several pecl exts
>
> Changed paths:
> U php/php-src/branches/PHP_5_4/NEWS
> U php/php-src/branches/PHP_5_4/acinclude.m4
> U php/php-src/trunk/acinclude.m4
And PHP
Am 27.12.2011 16:36, schrieb Sebastian Bergmann:
> And PHP_5_3 does not need this?
I am asking because I cannot build PHP_5_3 with ext/intl on Fedora 16.
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ h
_COMPILE_ERROR, "Cannot use $this as lexical
variable");
return;
}
is still in zend_compile.c. IIRC, this code was added in PHP 5.3 to
prevent $this from being used as a lexical variable. It should no
longer be required in PHP 5.4. Right?
--
Sebastia
wanted to make sure that it was not an oversight to not remove
the error message.
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/
--
PHP Internals - PHP Runtime Development Mailing L
Am 08.01.2012 13:37, schrieb Pierre Joye:
> As far as I know, the only BC so far is the request time float
> addition to restore the previous behavior. I will do it this afternoon
> if nobody catches up with it before :)
That was already restored (in r321828).
--
Sebastian
2.2-dev, and traits without problems.
Xdebug's code coverage functionality "just works" with PHPUnit.
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/
--
PHP Internals - PHP Runt
tures that
facilitates the separation of concerns and the decomposition of
software.
Of course we also need to add a function that allows developers to check
which syntax features are enabled in the PHP interpreter that is
executing their code ...
--
Sebastian BergmannCo-Fo
On 01/13/2012 11:51 AM, Lester Caine wrote:
why would I not put this code into a base class and simply extend
from that.
Could you please refrain from asking questions such as this BEFORE you
even bothered to research the topic? Thank you very much.
--
Sebastian Bergmann
.com/1621839#file_final_test.php and wrote a
> short article explaining it:
> http://blog.juzna.cz/2012/01/mock-vs-final-fights-in-testing/.
+1 from me for the idea. Implementation looks good at first glance as
well, but I let more knowledgable C developers be the judge of that.
--
Am 17.01.2012 11:34, schrieb Pierre Joye:
> Patch looks good, but coding standard.
If there are no objections, I can fix the CS issue and commit the patch
to trunk.
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann
Am 17.01.2012 12:00, schrieb jpauli:
> How didn't we think about that earlier... ?
I have had this on a TODO list at the back of my head for a long time;
at least since we added setAccessible().
--
Sebastian BergmannCo-Founder and Principal Consultant
http://s
tFinal)
+/* {{{ proto public void ReflectionClass::setFinal([bool isFinal = true])
+ Sets/unsets class as final */
+ZEND_METHOD(reflection_class, setFinal)
TL;DR: All is well :)
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergm
Hi,
Am 04.02.2012 19:13, schrieb Clint M Priest:
-Original Message-
From: Rasmus Schultz [mailto:ras...@mindplay.dk]
Sent: Saturday, February 04, 2012 10:01 AM
To: internals@lists.php.net
Subject: [PHP-DEV] Re: internals Digest 4 Feb 2012 09:08:29 - Issue 2549
Why can't the read-
2.25Mb
phpDox, cached run for Zend Framework 2
PHP 5.4: Time: 14 seconds, Memory: 4.75Mb
PHP 5.3: Time: 19 seconds, Memory: 7.50Mb
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/
-
2012/2/22 Charlie Somerville
> Right, but enums could possibly be a lot richer than class constants are
> now.
>
> They could be a type where the only values are what's defined in the enum.
> This could be used with type hinting:
>
>enum Foo {
>A,
>B,
>C
>}
>
>
Hi,
Am 22.02.2012 20:04, schrieb Larry Garfield:
On 2/22/12 12:37 PM, Peter Lind wrote:
I would also support this. There's a myriad reasons why something may
return NULL or FALSE when you expect it to return an object, some of them
even legitimate. Any function/method whose documentation line
Am 22.02.2012 22:22, schrieb Ángel González:
On 22/02/12 09:37, Sebastian Krebs wrote:
class MyEnum {
const FOO = 'foo';
const BAR = 'bar';
private $value;
public function __construct ($value) {
if (!in_array($value, array(self::FOO, s
Am 23.02.2012 20:01, schrieb Ángel González:
On 23/02/12 00:09, Stas Malyshev wrote:
Hi!
Sidenote, according your examples above on how you want call
functions: Considered using normal constants?
How can I do type hinting with them?
You should not. PHP is not a strictly typed language, so i
Am 23.02.2012 21:21, schrieb Ángel González:
I don't see your point, Sebastian.
And
| $studipNamedVariable = Databases::Mysql;
| // ... much code
| database_select($stupidNamedVariable, $sql);
is better? The problem here seems to be more the developer, that
avoids the use of constants,
.
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 02/28/2012 02:44 PM, Christopher Jones wrote:
Build PHP with ZTS enabled by default. Allow it to be explicitly
disabled during 'configure'
Why punish everyone by default because of Apache? Does not make sense to
me.
--
Sebastian BergmannCo-Founder and
.
2) What you want to achieve is already possible through docblocks.
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe,
gling".
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
1 - 100 of 1550 matches
Mail list logo
