On 11.11.2009, at 11:44, Mikko Koppanen wrote:
On Wed, Nov 11, 2009 at 10:00 AM, Lukas Kahwe Smith m...@pooteeweet.org
wrote:
On 11.11.2009, at 01:50, Greg Beaver wrote:
if (can_include($file)) {
include $file;
}
I am sure you focused on the technical aspects. Just wanted to say
On 11.11.2009, at 14:50, Greg Beaver wrote:
Lukas Kahwe Smith wrote:
On 11.11.2009, at 11:44, Mikko Koppanen wrote:
On Wed, Nov 11, 2009 at 10:00 AM, Lukas Kahwe Smith
so a byte code cache should cache the resolution of the path thereby
speeding up the subsequent call to include
be found on the wiki:
http://wiki.php.net/rfc/autoload_include
As stated in the RFC, I am not happy with the name autoload_include.
Suggestions welcome!
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
On 10.11.2009, at 18:40, Mark Skilbeck markskilb...@gmail.com wrote:
What's the problem with file_exists() ?
i have explained this in the RFC. for one it does not support the
include path setting. furthermore this does not solve the race
condition and requires more FS operations than my
.
that being said, i brought up adding such a flag to file_exists() a
few times before and each attempt has been shot down saying that fopen
() should have never gotten this flag and this portion of the code
should not mess with the include path.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
of the most vocal against adding this to
file_exists() and complaining about the fact that its even available
for fopen().
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Anyways, lets see if there are other comments in the coming days. I
think you have made your priorities clear. At least I understand them,
but do not share them.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
for now it was decided to only use exception for constructor errors in
core php.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I do not share your concern that tomorrow we will need yet
another different magic method to handle includes.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Perhaps better would be to introduce a function:
if (can_include($file)) {
include $file;
}
opcode caches could easily snag this, as we could provide a simple
hook the way we do with stream_resolve_path(). That would actually
make a 0-stat smart autoloader a possibility. Just in case
on this list. ideally they
are based on an RFC that is then updated according to the discussions
and decisions on this list. and even then decisions at times will be
reversed too. so it goes.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
PS: I do however agree that in the future notes from
.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 15.10.2009, at 19:40, Samuel ROZE wrote:
Le jeudi 15 octobre 2009 à 11:08 +0200, Lukas Kahwe Smith a écrit :
On 13.10.2009, at 10:34, Samuel ROZE wrote:
http://wiki.php.net/rfc/pdonotices
I assume that calling noticeInfo() will also purge all currently
stored notices (maybe
To unsubscribe, visit: http://www.php.net/unsub.php
DJ Suicide Dive
d...@ifnotwhynot.me
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
on the list of
what people want and therefore i wanted to get this discussion going,
so that after its concluded traits can be commited to HEAD.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
.
and of course links to proposed patches.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
no sense to start a php.net
plea for help to get something ported to PHP6, where we will have a
perfectly fine alternative.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
beginning. Writing an RFC is not about
making your life miserable .. and its not about stalling your request
either.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
, it would be nice of someone would
document the points raised by with sides about the deprecation of
ereg in 5.3 and the removal in 6.0.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
[1] http://pooteeweet.org/blog/1200
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit
that
we can spare us starting this discussion at zero again in the future.
Thanks and have a nice day.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 12.10.2009, at 20:34, Tomas Kuliavas wrote:
2009.10.12 20:55 Carl P. Corliss rašė:
Lukas Kahwe Smith wrote:
[snip]
On 12.10.2009, at 18:57, Mark Krenz wrote:
On Mon, Oct 12, 2009 at 04:27:02PM GMT, Pierre Joye
[pierre@gmail.com] said the following:
[snip]
But I'm willing to bet
.$pattern.$d, $string, $matches)) return
strlen($string);
return false;
}
}
Much the same could be done for split(), ereg_replace(), and so on.
Feel free to collaborate with the authors of PHP_Compat [1].
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
[1] http
result set at a time, so
you cant check the notices until you have fetched the result set ..
then again notices are usually only for insert/delete/update ..
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
..
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
worthy, and they should
obviously not return false either.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
might want to interpret as an error whatever, then it seems to make
sense to unify this under a common API .. so the key test is not to
unify messaging API's but more unify things that are semantically
similar.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP
boils down to having developers care. It mostly works
for MySQL and SQLite I guess. PostgreSQL has seem some love recently.
IBM seems to not care anymore. Oracle certainly doesnt. Microsoft
never did. A really bad situation for such a core technology.
regards,
Lukas Kahwe Smith
m
it easier to avoid those reports to begin with, though yes there
are cases where there is simply no way to avoid them.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
the real issues. That certain
errors in certain parts of your code are unavoidable and known and
that certain pieces of code will raise errors to the global error
handler even though you have all the code in place to handle the issue
locally.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
be totally ignored in production. however E_NOTICE should not
occur in production and we shouldnt encourage people to make them
disappear entirely.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
On 24.08.2009, at 23:59, Rasmus Lerdorf wrote:
Lukas Kahwe Smith wrote:
On 24.08.2009, at 23:42, Stanislav Malyshev wrote:
Hi!
Quite boring to read this thread where two persons argue about
something abstract. Stas, can you give a real life example where
your
patch is necessary
/handle locally.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
.. and that
time is always!
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
form at pecl.php.net
the sources have been moved out of core and into the pecl repo.
however nobody made a release or even registered the extension on the
pecl site. this is the case with a few other extensions.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP
extension, so this is also not
really feasible.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
not really have a good solution, just
trying to define the problem at hand a bit more and the some of
options on the table.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
would be copied as is and might lead to
wrong assumptions (like that a newer version was included) meaning we
make the tagging more complex or avoiding confusion.
if you svn copy .. it will copy the externals ..
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime
use it .. they first have to figure out which
things have not been merged via svn merge, as svn merge updates its
metadata. when merging you can either mark an entire range of
versisions as merged .. or just individually.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals
for packaging.
If needed I can help with it once the whole process is defined.
err .. of course you need to either point to a specific revision .. or
better yet to a tag.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit
.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 10.07.2009, at 17:16, Alain Williams a...@phcomp.co.uk wrote:
On Fri, Jul 10, 2009 at 10:57:22AM -0400, Alban wrote:
Le Fri, 10 Jul 2009 14:23:24 +0100, Alain Williams a écrit
And Exception is better than an Error because this give one chance to
programmer for resolving the
robustness (in case you forget to do the
necessary checks).
+1 ... this is one of the key points i tried to make in my RFC.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
most of their time talking to data stores and not type checking).
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
suffer of BC
problems while still providing the feature to a restricted set of
users.
thats a no go, since this would lead to incompatible PHP code. we have
had various php.ini settings that have caused this and we do not want
to pile onto this.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
was specifically talking about strict type checking.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
that a fair number only voted for
the expansion of type hinting to scalar datatypes and did not really
look into the entire strict vs. weak hinting stuff.
regards
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
decisions. As such I am stepping down to avoid the confusion
that people keep thinking of me as someone who can actually review
patches. I will of course continue to do my best to track todo items
for the various branches.
Go Johannes! :)
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
rejected feature such as strict
type hints, has everyone turning 180 degrees and putting it in a
minor release in the course of a week.
amen to that.
regards
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
(including
what we currently already have) to type checking or something other
than hint in the documentation.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I want to use it if we
did have one. One job is to keep things focused and appeal to the
general sanity if we feel that things are going off track. I would
want to appeal to the general sanity on this one though :)
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP
On 04.07.2009, at 22:08, Lukas Kahwe Smith wrote:
On 04.07.2009, at 21:10, Paul Biggar paul.big...@gmail.com wrote:
On Sat, Jul 4, 2009 at 7:12 PM, Lukas Kahwe
Smithm...@pooteeweet.org wrote:
I can't see the difference between your proposal and the
conclusion I
reached yesterday
not be validated.
regards
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 04.07.2009, at 16:05, Paul Biggar paul.big...@gmail.com wrote:
Hi Lukas,
On Sat, Jul 4, 2009 at 7:20 AM, Lukas Kahwe
Smithm...@pooteeweet.org wrote:
Last evening I put together a quick proposal for a weak and strict
checking
approach, since I felt that things were being concluded a bit
On 04.07.2009, at 21:10, Paul Biggar paul.big...@gmail.com wrote:
On Sat, Jul 4, 2009 at 7:12 PM, Lukas Kahwe
Smithm...@pooteeweet.org wrote:
I can't see the difference between your proposal and the
conclusion I
reached yesterday?
(which was that there is a near consensus around strict
. But maybe you are not implying that and I am just getting
confused by the syntax.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
serve as a starting point:
http://wiki.php.net/rfc/typehint
Remember anyone can request a wiki account and do this.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
, but I believe that the overuse of private
that I am seeing has a lot to do with the fact that its shorter than
protected.
I have not really made up my mind about Paul's proposal, but I just
wanted to make the above points.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals
Hi,
I recommend that you sign up on the wiki and publish your proposal on
wiki.php.net/rfc
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
is to prevent confusion.
I do not see the risk for confusion as being high.
Like I said, I havent made up my mind on this proposal, however for
now Paul mainly asked for feedback in the general concept, not
necessarily on the syntax.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP
On 26.06.2009, at 17:26, Lukas Kahwe Smith wrote:
After this period bug fixes can be applied again. However feature
additions should wait until after 5.3.1, which we expect to be
released within a month or two. As always if you are unsure, ask
Johannes. And also as always
Hello!
The PHP Development Team would like to announce the immediate release
of PHP 5.3.0. This release is a major improvement in the 5.X series,
which includes a large number of new features and bug fixes.
Release Announcement: http://www.php.net/release/5_3_0.php
Downloads:
function be
eval_stringL instead and add macros for compatibility?
[1] http://lxr.php.net/ident?i=zend_eval_string
should this be applied now as it hasnt been applied yet, afaik?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
Aloha,
So the last fix is just being prepared for a commit and so we will be
tagging 5.3.0 soon.
We would like to up hold the commit freeze until 5.3.0 is announced
next Tuesday.
After this period bug fixes can be applied again. However feature
additions should wait until after 5.3.1,
On 26.06.2009, at 20:26, Pierre Joye pierre@gmail.com wrote:
On Fri, Jun 26, 2009 at 7:30 PM, Scott MacVicarsc...@macvicar.net
wrote:
On 26 Jun 2009, at 16:26, Lukas Kahwe Smith wrote:
Aloha,
So the last fix is just being prepared for a commit and so we will
be
tagging 5.3.0
Aloha,
As most of you following this list have noticed, alot of last minute
stuff has been brought up. So it goes.
Johannes and Pierre have put in extra time in trying to still make it
for a release tomorrow, however as the stream of patches and open
issues has continued even today, we
?) when make tried to run non-existing system's pear.
if someone has a safe looking patch to improve this, we can consider
including it in 5.3.0
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
). (Scott)
Actually .. most likely this issue will be first fixed in 5.3.0
stable, before we will see a 5.2.11 stable. So where should this be
listed in?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
can alert either your own team, or the project who's code you
are using and move on. It simply tells you that the code will break
with the next major version. This is not an end of world fatal error.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development
On 21.06.2009, at 10:24, Lester Caine wrote:
Lukas Kahwe Smith wrote:
On 21.06.2009, at 09:51, Lester Caine wrote:
Johannes Schlüter wrote:
On Sat, 2009-06-20 at 07:49 +0100, Lester Caine wrote:
While I know that ...
- All ereg functions are deprecated and emit E_DEPRECATED errors.
Use
On 21.06.2009, at 10:29, Lukas Kahwe Smith wrote:
On 21.06.2009, at 10:24, Lester Caine wrote:
Lukas Kahwe Smith wrote:
On 21.06.2009, at 09:51, Lester Caine wrote:
Johannes Schlüter wrote:
On Sat, 2009-06-20 at 07:49 +0100, Lester Caine wrote:
While I know that ...
- All ereg functions
Hi,
It looks like nothing critical has popped up since RC4.
So it looks like we will be sending the final stable release to the
mirrors next Wednesday and announce the release on Thursday barring
any critical issues emerging in the next days. In the mean time test
test test. If issues are
Hello!
we have packaged PHP 5.3.0RC4, which you can find here:
http://downloads.php.net/johannes/
Windows binaries are available here:
http://windows.php.net/qa/
This this release candidate focused on bug fixes and stability
improvements and we hope to only require minimal changes ahead
of the
On 19.06.2009, at 10:50, Lukas Kahwe Smith wrote:
Hello!
we have packaged PHP 5.3.0RC4, which you can find here:
http://downloads.php.net/johannes/
Windows binaries are available here:
http://windows.php.net/qa/
This this release candidate focused on bug fixes and stability
improvements
) is working with the official build.
is this fixed? and if not .. is there a bug ticket open?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
anything (or even raises an error) when set_magic_quotes_runtime(1)
is called, but silently continues when set_magic_quotes_runtime(0)
is called, then it should be changed as per Greg's request.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing
of the 21st without any further changes so we can test the
packages. In case something critical, unexpected, pops up please
notify us asap.
June 25th 2009
Release PHP 5.3.0 final.
We are still on track for this one.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP
). Attached patch should fix it.
Please tell if there's some objection to it, otherwise I'll commit
it tomorrow.
So whats going on here?
I noticed that the bug report hasn't been reopened .. but I think
there was also not commit yet .. ?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
message.
So lets delay fixing this issue until 5.3.1? Of course it can be fixed
in HEAD right now :)
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
reason to delay 5.3 from where i
stand.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
off in both of the php.ini's we will ship with 5.3
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 16.06.2009, at 20:59, Greg Beaver wrote:
Lukas Kahwe Smith wrote:
1) its not about punishing, its about alerting people that they are
relying on stuff that will go away
2) E_DEPRECATE is for development only and only as a check you enable
now and then
3) its off in both of the php.ini's we
.
If no one else speaks up I would tend to leave as is and fix it in
5.3.1 (and HEAD asap) and simply make sure that we put it in bold
letters in the UPGRADING guide that you really should set the timezone.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime
Hi,
This seems like a trivial change from the implementation side, so I am
not worried about changing this for the better even after RC4 (given
proper documentation.
So here are the choices I see:
1) stay as is .. aka defaults to on while not emiting an E_DEPRECATED,
do emit
past adding new features.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
is really necessary
@Andrey: I guess you will/have talked to Johannes about your patches
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
into 5.3.1.
Again a commit freeze means no commits to any part unless its clearly
a build fix or just touches README's. When in doubt ask Johannes (who
should be available again some time tonight).
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development
.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
things. It will result in either the
release date for RC3 slipping or having to do an RC4, both resulting
in a delayed final release.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
will be 6.0, there
might be a 5.4 after 6.0 that back ports some stuff and more
importantly adds soem forwards compatibility. but for now lets focus
on 6.0 (well after relasing 5.3).
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
On 12.05.2009, at 04:20, Matt Wilmas wrote:
Hi Lukas,
- Original Message -
From: Lukas Kahwe Smith
Sent: Monday, May 11, 2009
[...]
Critical issues:
1) I assume the issues with rounding are resolved. If any issues
pop up again, please let the list know.
@Matt/Dmitry: Can you
/php-53-and-delayed-cross-site-request-forgerieshijacking/
Also a lot of work was put into restructuring the php.ini files we
ship with PHP.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
Steph in a while and when I
last inquired about this guide a few days ago.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
to Johannes and he agree's with me that this changes to
sorting should not happen in 5.x, so we would also like to see this
reverted in 5.3 if it gets reverted in 5.2.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit
On 15.05.2009, at 19:14, Michael Shadle wrote:
On Fri, May 15, 2009 at 1:32 AM, Lukas Kahwe Smith
m...@pooteeweet.org wrote:
The more stuff like this we remove, the harder it becomes for
people to
quickly move to newer, faster and more secure versions of PHP. That
causes way more
, then there is no reason
from an RM perspective to stop this change, if you guys feel its the
right choice.
If tests need fixing and you dont have the time for this, I am sure we
will find people that do.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing
On 12.05.2009, at 04:20, Matt Wilmas wrote:
Hi Lukas,
- Original Message -
From: Lukas Kahwe Smith
Sent: Monday, May 11, 2009
[...]
Critical issues:
1) I assume the issues with rounding are resolved. If any issues
pop up again, please let the list know.
@Matt/Dmitry: Can you
101 - 200 of 846 matches
Mail list logo
