mmit break 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
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
To
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/D
On 15.05.2009, at 19:14, Michael Shadle wrote:
On Fri, May 15, 2009 at 1:32 AM, Lukas Kahwe Smith
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 frustration for everyone
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,
hear from 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
org/2008/10/01/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/unsub.php
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 Ma
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/D
On 08.05.2009, at 10:31, Lukas Kahwe Smith wrote:
1. fix open PHP 5.3 bugs
To spare us surprises so late in the game, please only commit bug
fixes with accompanying tests. Again as Johannes mentioned, tests in
the testfest repo do not count. They should go into php-src along with
the
resolution. That is not to say of course that getting them resolved is
not important. However only if they are low risk changes. Most of the
other issues are minor and should get fixed for RC3.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
[1] http://wiki.php.net/todo/php53#rc3
--
PHP Internals
On 28.04.2009, at 12:51, Lukas Kahwe Smith wrote:
Aloha,
So seriously .. Thursday next week we will release RC2. This means a
commit freeze for all but build fixes and README commits starting
Monday evening. Also with RC2 any feature additions, regardless of
how small, will no longer be
the right decisions.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
and a new release out. this might require reducing the bus
factor on re2c. so anyone interested please get in contact with Nuno
as Marcus is understandably quite busy with private matters atm.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing
On 28.04.2009, at 12:51, Lukas Kahwe Smith wrote:
So seriously .. Thursday next week we will release RC2. This means a
commit freeze for all but build fixes and README commits starting
Monday evening. Also with RC2 any feature additions, regardless of
how small, will no longer be allowed
rds,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
addition or a bug fix, ask one of the RMs). We are looking to
really wrap things up quickly now. So if necessary expect an RC3
within 2 weeks after RC2. And we will continue with this cycle until
we have a final release.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP
On 31.03.2009, at 08:51, Hannes Magnusson wrote:
On Tue, Mar 31, 2009 at 04:47, Greg Beaver
wrote:
Lukas Kahwe Smith wrote:
So where are we at here?
If nobody proposes something, this will just slide by ..
I propose reserving PHP. extensions can be PHP\extname (i.e. class
PHP\Phar, or
uch a
feature before, but imho before we start adding arrays as a poor mans
named parameter support, we might want to open that pandoras box
again. Again nothing for 5.3 .. HEAD is where its at.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development
. But
surely the week after that at the latest ..
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
all ..
work on this in HEAD.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
@Matt: thx for getting back to me on this.
In general all the technical details are way over my head. What
worries me is that we are going back and forth with these changes. It
seems there is a pretty large "trail and error" part to these changes.
So for the most part at this stage I d
this one of the "don't go there" ideas I sometimes get?
I guess its a dont go there thing, as you also run into trouble with
"use"-d variables.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe,
On 31.03.2009, at 00:32, Lukas Kahwe Smith wrote:
On 31.03.2009, at 00:27, Pierre Joye wrote:
On Tue, Mar 31, 2009 at 12:09 AM, Lukas Kahwe Smith > wrote:
Hi guys,
Just wanted to know if those issues are resolved?
I rather not have a flow of changes in this area just before the
next
On 31.03.2009, at 18:22, Hannes Magnusson wrote:
On Wed, Mar 25, 2009 at 20:59, Lukas Kahwe Smith
wrote:
Hi,
Whats the status here?
I would say it does not sound like something we need to add now,
but maybe
for 5.3.1?
So in that light I would say please file a feature request with the
t FYI ... seems like Pierre fixed that one.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
define a
sensible standard?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 31.03.2009, at 00:27, Pierre Joye wrote:
On Tue, Mar 31, 2009 at 12:09 AM, Lukas Kahwe Smith > wrote:
Hi guys,
Just wanted to know if those issues are resolved?
I rather not have a flow of changes in this area just before the
next RC2.
As a matter of fact this is the main thing t
mind being able to release RC Thursday next week. Which
would mean commit freeze starting Monday next week. So how are things
looking?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Bringing this back to the list since its still relevant apparently.
On 26.03.2009, at 19:43, shire wrote:
Lukas Kahwe Smith wrote:
Also Marcus had some comments about your
"ZendEngine2/zend_language_scanner.c" change:
" thanks for looking into this. The patch looks pretty good
On 26.03.2009, at 01:30, Arnaud Le Blanc wrote:
On Wed, 2009-03-25 at 20:05 +0100, Lukas Kahwe Smith wrote:
On 19.03.2009, at 14:32, Arnaud Le Blanc wrote:
Hi,
After having seen some complaints about ticks being deprecated I'm
wondering if they could be un-deprecated for now.
Tick
t was deprecated?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
iling 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
/* delete buffer */
--
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
al (something that Steph afaik also
raised her hand).
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello!
Johannes has packaged PHP 5.3.0RC1, which you can find here:
http://downloads.php.net/johannes/
Windows binaries are available here:
http://windows.php.net/qa/
This release candidate makes us feature complete and we hope to only
require minimal changes ahead of the next release. Many,
d to change the behavior).
If someone can summarize the current state of things I would
appreciate it.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hey Matteo,
Based on the feedback I got there is no reason why your PDO patches
have to be applied by anyone but yourself. So if you are still
interested go ahead and submit a cvs account request.
Thx for looking after PDO bugs .. we dearly need your help!
regards,
Lukas Kahwe Smith
m
le can now rely on things being fixed,
which is why this is an RC and not a beta2 after all [3].
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
[1] This Friday thing is an attempt to keep the commit freeze periods
as small as possible, while still ensuring that those testing less
used platf
s notes (is
there a ticket for this one already)?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 20.03.2009, at 12:37, Ferenc Kovacs wrote:
On Fri, Mar 20, 2009 at 12:01 PM, Lukas Kahwe Smith >wrote:
Hello,
We are not in a commit freeze on the 5_3 branch. For today for any
commit
not just affecting README's (as in anything affecting buolding or
build
testing), please g
ranch. Please keep track of any HEAD commits that need merging or let
me know about them so I can keep track of them (dunno if it makes
sense to just write a note in the HEAD commit that this changes needs
merging into 5_3).
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals
On 18.03.2009, at 11:06, Lukas Kahwe Smith wrote:
On 17.03.2009, at 10:59, Lukas Kahwe Smith wrote:
On 10.03.2009, at 17:04, Johannes Schlüter wrote:
Hi,
I wrote a mail last Friday about this but it seems like it got
lost. I
wanted to go RC on Thursday, as this now would be a rather
On 17.03.2009, at 10:59, Lukas Kahwe Smith wrote:
On 10.03.2009, at 17:04, Johannes Schlüter wrote:
Hi,
I wrote a mail last Friday about this but it seems like it got
lost. I
wanted to go RC on Thursday, as this now would be a rather short-time
announcement (while quite a few devs
rather than rushing features in now, that take away the focus
from bug fixing and worse yet could add new bugs.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ension name) as your prefix.
Then again for classes we say that the prefix should be prepended with
an underscore as the separator as the ultimate protection. That of
course does not seem feasible for namespaces.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime
On 11.03.2009, at 20:58, shire wrote:
Lukas Kahwe Smith wrote:
Can we get this patch to release quality by this weekend?
So that people can test it on Monday/Tuesday ahead of RC1?
I don't see this being a problem, I do have a few items I'd like to
point out for feedback/sugges
On 11.03.2009, at 19:55, Marcus Boerger wrote:
Last but not least, Lukas, what happened, to putting APC into core?
That was planned for PHP 6.0.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
atch to release quality by this weekend?
So that people can test it on Monday/Tuesday ahead of RC1?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
thread. As things are close to RC
state in 5.3, I would prefer to not do any non bug fixes at this
stage. Then again if the benefits are huge and the risk is low it can
be considered of course ..
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Ma
.
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.02.2009, at 17:18, Marcus Boerger wrote:
Hello Stanislav,
Friday, February 13, 2009, 7:03:30 AM, you wrote:
Hi!
it should actually be a hard error. As we always claim PHP
follows pure
IS-A relation ships.
I feel very uneasy with hard errors on something that is not indeed
an
ticket for this with the patch attached (or
with an url to the patch).
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.02.2009, at 21:59, Arnaud Le Blanc wrote:
On Wed, 2009-02-11 at 18:07 +0100, Lukas Kahwe Smith wrote:
- pcntl_signal needs declare(ticks) which is deprecated since 5.3
I marked this as a documentation issue. This has been discussed when
it
was decided to deprecate ticks. Although
Hey Steph,
Personally I think we should list all changes. For certain changes we
should devote some explanations (like E_DEPRECATED). For the most part
I see this document as a place where we provide an overview of things
which then gives them the right key word to look in the documentation
are taking over any of the above
items so that I can update the wiki. Speaking of wiki, Pierre also has
admin rights on the wiki and of course root access to the box.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit
indicate a problem that
needs fixing.
I think in dev environment it makes sense to set error reporting
level to E_ALL | E_STRICT
Right. Currently E_DEPRECATED is also part of E_ALL. Maybe it should
not. In dev env it should of course be enabled.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
l
not force a rewrite if you have coded yourself into a corner.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 07.02.2009, at 03:12, Andi Gutmans wrote:
-Original Message-
From: Lukas Kahwe Smith [mailto:m...@pooteeweet.org]
Sent: Tuesday, February 03, 2009 5:42 AM
To: php-dev List
Subject: [PHP-DEV] towards the next 5.3 release
--snip--
5) upgrading guide
--snip--
RC really signifies a
warranting E_STRICT.
I agree. If $y were optional, the LSP is no longer violated, and the
E_STRICT disappears, as expected.
Opn->Bgs
I agree. This is exactly what we have E_STRICT for ..
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing L
Hi,
I also just reopened:
http://bugs.php.net/bug.php?id=46026
Not sure if Greg has time ..
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
bugs are assigned to andrey/mysql, derick,
pierre, dmitry, scott. i assume you guys will let us know if you need
help, cannot fix the issue etc.
So I am sure there are still things off in other places too. Please
speak up what you feel needs to be addressed.
regards,
Lukas Kahwe
case.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
a 1.
thx for this summary and proposal .. its important that we continuesly
seek ways to optimize this often asynchronous development sprints by
the various people across the world .. since I do not have the
expertise to comment I will leave it to others to reply.
regards,
Lukas K
is for the greater good (as defined by the
RMs). So in other words if you feel this is bad, blame the RMs .. but
the decision still stands (I hope we RMs have enough credit to make
such a decision).
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Maili
Hey,
Just FYI .. today is the last day for feature changes ahead of 5.3.0
beta1. The big change I am waiting on for today is the removal of the
OO specific features in closures. Tomorrow will be dedicated to build
only fixes, Johannes/Pierre will then handle the packaging some time
on Wed
onstant in new context:
I agree that there should be an easy way to get a fully qualified name
from an identifier. Not sure what the best approach would be though ..
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, v
ich
will be a BC break, so I'm not sure if it's worth changing.
Hmm, maybe still worthwhile to classify it as a bug fix? :)
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ource! =)
Even if you are not keen on getting into phpdoc .. maybe writing some
docs and sending them to the phpdoc team list so that they can
integrate them might be a good idea.
regards,
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing Li
ually if we havent made the migration to SVN at that point, we
should at least use SVN for the GSoC projects.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
, the solution would need to be super duper
rock solid. But it could make the life of the RM's a lot easier.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
x27;s going to administer this kicking?
I think the decision was to not yet bother with reserving namespaces
or starting to namespace-ify extensions. We might however want to put
out a naming guide for namespaces.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Ru
o do to at
this point.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
delaying a few weeks here and there, we will do PHP a
greater disservice. as johannes has pointed out we have delayed some
features because we wanted to focus on getting 5.3 out. if necessary
we can always have a PHP 5.4 just as well.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
-
On 21.01.2009, at 12:00, Karsten Dambekalns wrote:
Hi.
On 21.01.2009 11:44 Uhr, Kenan R Sulayman wrote:
I did propose the function because the construction in user-land is
quite
expensive;
Reflection is expensive, indeed. The way we solved it for FLOW3 is
to create a ReflectionService t
On 21.01.2009, at 10:04, David Zülke wrote:
Am 20.01.2009 um 18:41 schrieb Christian Seiler:
Hi,
maybe an IRC meeting is the easiest way to come to an agreement. How
about tomorrow evening 21:00 CEST in #php.closures on freenode?
Just for clarification: I assume you mean Wednesday, Januar
Hi,
maybe an IRC meeting is the easiest way to come to an agreement. How
about tomorrow evening 21:00 CEST in #php.closures on freenode?
regards.
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 19.01.2009, at 22:54, Lukas Kahwe Smith wrote:
Hi,
Given the on going discussions especially about Closures it seems
pointless to move towards beta1 this week. Therefore we are delaying
beta1 to Feb. 29th. This means we will be freezing for non build/
critical fixes next Monday
Hi,
Given the on going discussions especially about Closures it seems
pointless to move towards beta1 this week. Therefore we are delaying
beta1 to Feb. 29th. This means we will be freezing for non build/
critical fixes next Monday. Packaging will be the following Wednesday.
In order to ma
On 17.01.2009, at 18:06, Nathan Rixham wrote:
a: Optional Static Typing
I'm finding an ever increasingly need to be able to staticly type
properties, parameters, return types etc (in classes) I know there
is type hinting but it's just not enough to do what one needs.
Additionally support
Hi,
Ok, my proposal to drop OO support from Closures was exactly embraced.
All I want you guys to think about is how you want to deal with this
in terms of the PHP 5.3 release. If no decision is found and
implemented over the weekend, this topic will essentially cement the
need for an add
Hi
I have tried to catch up to the discussion yesterday evening. I must
admit its not very trivial for me to understand the entire scope of
the issues. I am especially worried about things becoming too magical
(although in general I am pro giving end users all the power in the
world). At
Hello all,
Expected to be done for beta1:
- Eric and Nathan: new php.ini files
- Steph: Upgrading Guide
- Scott/Pierre: making the dsn functions available on OSX/FreeBSD/
Windows
- Pierre: bundling ext/enchant as an ext/pspell replacement
- Ettienne/Lars/Guilherme: patch for spl_object_id()/spl
On 14.01.2009, at 23:22, Stanislav Malyshev wrote:
Hi!
As many of you know, one can build PHP engine in a number of ways
which are binary-incompatible - debug/no debug, thread-safe/not
thread safe, etc. Also, for windows we have now anther dimension -
we could build with VC6, VC8, VC9, e
On 14.01.2009, at 23:22, Stanislav Malyshev wrote:
Hi!
As many of you know, one can build PHP engine in a number of ways
which are binary-incompatible - debug/no debug, thread-safe/not
thread safe, etc. Also, for windows we have now anther dimension -
we could build with VC6, VC8, VC9, e
On 12.01.2009, at 23:04, Marcus Boerger wrote:
Hello Lukas,
it appears Dmitry and Stas are against that, so I let it for you to
decide whetehr you want me to drop all of it or continue workig on it
to make all I can ready for 5.3.0.
Just to clarify my role again. I am not the head decider.
On 12.01.2009, at 16:59, Ilia Alshanetsky wrote:
On 12-Jan-09, at 5:56 AM, Lukas Kahwe Smith wrote:
- First line of included files not output if they begin with #
A patch for this already went in on Friday.
was this the one where Nuno raised some BC concerns?
regards,
Lukas
--
PHP
On 12.01.2009, at 14:56, Hannes Magnusson wrote:
Why did the LFS patch never get committed?
LFS = large file support?
AFAIK there is no patch to commit at this point.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello all,
Just wanted to get a status update on the work going on:
- Eric and Nathan are working on new php.ini files and I guess they
will soon post their proposals to the list
- @Steph: have you begun work on the Upgrading Guide? I would really
like to have something for beta1. The scratch
On 07.01.2009, at 21:07, Eric Stewart wrote:
This sounds interesting. I'd would like to take this on.
Nathan was also interested.
Maybe you two can collaborate on this?
Thanks so much for stepping up!
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Ru
it ..
good chance for a non C expert to give back ..
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
depend on how
large the differences are)
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
i envision
there will be a bit of a need for discussion (especially from the side
of the end users).
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello,
I have updated the todo with the information provided by Ilia,
Guilherme and Steph:
http://wiki.php.net/todo/php53#beta1
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
with it now
either.
ok great.
feel free to delegate small chunks at a time to me ..
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
hanges, we really need to
focus on getting the current features out the door, rather than risk
wasting time on minor changes that introduce regressions and other
issues that delay the final release.
Thanks!
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime D
. So I guess file a feature request, ideally with a
solid proposal for an API for this.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 05.01.2009, at 15:52, Richard Quadling wrote:
2009/1/5 Lukas Kahwe Smith :
On 31.12.2008, at 11:11, Richard Quadling wrote:
With Microsoft having their own PHP extension for talking to MSSQL
(http://www.microsoft.com/sqlserver/2005/en/us/PHP-Driver.aspx -
though documented to only
On 05.01.2009, at 15:36, Lukas Kahwe Smith wrote:
target OS in practice for deployment) for an RDBMS that is also
quite a niche solution for PHP. Actually the only RDBMS where I am
willing to currently consider a new non PDO extension sqlite.
Just to make it clear what I was talking
quite a niche solution for PHP.
Actually the only RDBMS where I am willing to currently consider a new
non PDO extension sqlite.
As such I do not think we should consider bundling this extension, let
alone have it replace the php_mssql.dll.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
201 - 300 of 900 matches
Mail list logo
