votes in all cases regardless),
usually because of lack of strong knowledge of the subject matter.
-- Gwynne Raskind
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
($a,$b) = str_split([“ab”][0]); if
someone was actually using it.
-- Gwynne Raskind
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
($a,$b) = str_split([“ab”][0]); if
someone was actually using it.
-- Gwynne Raskind
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
think the point has been missed.
-- Gwynne Raskind
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
.
?? is standard in both .NET and Apple’s Swift language - Apple added it to
Swift (including the chaining behavior) early during the beta cycle due to user
demand for exactly this kind of logic, and it’s been part of C# for a long time.
-- Gwynne Raskind
--
PHP Internals - PHP Runtime Development
participate in discussions, but I always read them before
voting. As you say, it's just common sense.
-- Gwynne Raskind
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Sun, Aug 26, 2012 at 9:22 PM, Rasmus Lerdorf ras...@lerdorf.com wrote:
On 08/26/2012 06:18 PM, Kris Craig wrote:
Short of killing ourselves rewriting it in C++, I'm not sure there
is an ideal solution to this problem.
Because you think more people can grok C++ than C? That's not my
On Wed, Jun 13, 2012 at 5:31 PM, Nikita Popov nikita@googlemail.com wrote:
Hi internals!
Recent incidents have shown that even very large websites still don't
get how to do password hashing properly. The sha1 hashes used by
Linkedin et al can be easily cracked even by amateurs without
a pretty good chance of crashing. Image unloading simply didn't exist
at all in any useful form before Leopard.)
-- Gwynne Raskind
/* dylib.c - clang dylib.c -o dylib.dylib -dynamiclib */
static int var = 0;
extern int getVar(void);
extern void setVar(int value);
int getVar(void) { return var
On Sun, Feb 5, 2012 at 17:08, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
Another thing - is there any way to give CLANG some hints about some
functions - such as the fact that zend_error(E_ERROR) does not return or
just make some exceptions when we know some situation that it thinks can
On Sun, Feb 5, 2012 at 19:32, Adam Harvey ahar...@php.net wrote:
On 6 February 2012 04:37, Tom Boutell t...@punkave.com wrote:
Deprecate and then remove, or just leave it in. Make it optional
forever just generates more nonportable PHP code. Ick.
Huge +1 to that.
Given the existence of
On Wed, Jan 25, 2012 at 04:23, Pierre Joye pierre@gmail.com wrote:
hi Justin,
I'm totally for that, has been asked it for years.
Let see what other nicer status we need as wel :)
Cheers,
On Wed, Jan 25, 2012 at 12:11 AM, Justin Martin frozenf...@php.net wrote:
Hello,
With some
2011/10/22 Johannes Schlüter johan...@schlueters.de:
There is also a lot to be said for going with what is known to be stable
for
an LTS release.
Please do not begin with this discussion again. It is confusing for
the readers and totally unrelated. There is no LTS in the release
process
On Sun, Aug 28, 2011 at 04:00, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
On 8/27/11 1:49 AM, Sebastian Bergmann wrote:
note: '__gxx_personality_v0@@CXXABI_1.3' is defined in DSO
Judging from a quick search this is caused by libstdc++ missing from link
line, and can be fixed by adding
On Wed, Aug 24, 2011 at 19:03, David Soria Parra d...@php.net wrote:
Those wanting to use git and git workflows have a disadvantage when we stay
with SVN.
Choosing a VCS happens from time to time and sometimes your favorit is not
the winner.
I personally would love to see PHP moving to hg,
On Sun, Aug 14, 2011 at 04:18, Lester Caine les...@lsces.co.uk wrote:
The only real disadvantage to hg is having to handle python code to maintain
it, people might start converting from PHP ;) Although phphgadmin is a start
to improving the php interface support and could be a good start at a
On Fri, Aug 12, 2011 at 07:54, Kalle Sommer Nielsen ka...@php.net wrote:
2011/8/12 Sebastian Bergmann sebast...@php.net:
I never understood why we chose a legacy technology when we migrated
from CVS.
Well I'm sure if there were raised bigger concerns or more attention
headed towards
I've just created a new RFC, https://wiki.php.net/rfc/linecontrol ,
regarding adding cpp(1)'s linemarkers to PHP. Discussion is invited.
-- Gwynne
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
There's bug in LLVM 2.9's assembler which causes the build to fail on
the inline assembly, specifically the fsubp instruction. The bug is
LLVM #9164 (http://llvm.org/bugs/show_bug.cgi?id=9164). As I lack Zend
karma, I've attached a patch to fix this issue for affected Clang
builds. I've tested it
On Thu, Aug 4, 2011 at 09:12, Antony Dovgal t...@daylessday.org wrote:
Btw, am I the only one to whom the proposed syntax seems kinda
hieroglyphic?
No. I don't see at all why we need this, just like I don't see why we
needed an alternative (short) syntax for arrays. This kind of syntax
:
On 07/23/2011 04:07 PM, Gwynne Raskind wrote:
Here's my question - if I made some smaller commits here and there to
fix warnings in core, would that be accepted? I don't have time to do
sweeping changes, but fixing one file today, a couple the next day,
etc., is within my abilities (including
In my experience, 100% warnings free is only practical in two cases:
1) When the project is built with that policy from day one.
2) When someone takes the (I'd estimate) two weeks solid work
necessary to eliminate every existing warning from the current trunk,
AND a strict policy of maintaining
Here's my question - if I made some smaller commits here and there to
fix warnings in core, would that be accepted? I don't have time to do
sweeping changes, but fixing one file today, a couple the next day,
etc., is within my abilities (including making sure no regressions are
introduced, of
+1 to E_CORE.
-- Gwynne
On Thu, Jul 21, 2011 at 06:28, Pierrick Charron pierr...@webstart.fr wrote:
I'm also ok with E_CORE.
Pierrick
On 21 July 2011 05:19, Pierre Joye pierre@gmail.com wrote:
hi Pierrick!
Thanks for the updated patch :)
Now the only question remaining is which
On Jun 1, 2011, at 7:35 AM, Derick Rethans wrote:
But only if you keep it consistent, PHP has always been using = for
key/val association, I don't see any reason to suddenly provide key:
val, unless what you want is to confuse people.
Yes, definitely = vs. : in any case.
+1 to this.
--
+1
On May 31, 2011, at 2:42 PM, Brian Moon wrote:
https://wiki.php.net/rfc/shortsyntaxforarrays
Since this was brought again recently by Rasmus
(http://markmail.org/message/fx3brcm4ekh645se) and on Twitter where several
people including Andi chimed in on it and Ilia seemed to reverse his
On May 29, 2011, at 2:24 AM, Stas Malyshev wrote:
- I immediately had to write an extension to give me access to
several missing APIs (clock_gettime() and a number of ncurses
functions not implemented in the ncurses extension).
So the problem with PHP is that it doesn't include support for any
On May 28, 2011, at 10:55 PM, Martin Scotta wrote:
I really dont like to move away from PHP, but compared to others... it's
just a template language with steroids.
and please dont get me wrong, I love PHP, it's is still my favourite but...
This has been exactly my experience when trying to
On Dec 31, 2010, at 6:54 AM, Enrico Weigelt wrote:
After enviously looking at pythons grammar
(http://docs.python.org/dev/reference/grammar.html) I keep feeling
that PHP is missing out on a lot of interesting meta projects by not
having an official EBNF.
ACK. PHP also misses a lot of other
On Dec 22, 2010, at 4:38 PM, Mathias Grimm wrote:
People always will want more, but some features are nice.
for C/C++ programmers, macro is on of the best things to make thing work
every where.
its possible to create a IDE macro, but the native php feature will be good.
template engines can
On Nov 29, 2010, at 4:19 AM, Lester Caine wrote:
I've not used git or hg much at all, but bzr has always satisfied my
needs for DVCS, and has recently gotten much faster and more space
efficient than it was in the past.
Sorry, but I think bzr is not a good fit. It's numerous changes to the
On Nov 30, 2010, at 4:24 AM, Arvids Godjuks wrote:
Personally, as a user-land developer, I'm against it, so -1.
function keyword is the only sane way to quickly find a function
definition in lots of code. Not always IDE's are able to fully
understand the interconnections in frameworks and
On Nov 30, 2010, at 5:10 AM, Ferenc Kovacs wrote:
I just wish I didn't have to also admit that Trac is a really great project
management system. Unless things have changed drastically since I was last
active, PHP still needs one. ^^;
just a little comment on the last statement:
do you know
On May 28, 2010, at 7:43 PM, Pierre Joye wrote:
Is anybody using this file? If this is thee case could somebody then
make sure it's being updated (and maybe take care of
ChangeLog-200[6-9].gz being created) else I'd suggest dropping them. An
outdated file might be confusing for users expecting
On Apr 29, 2010, at 10:05 AM, Lukas Kahwe Smith wrote:
-Original Message-
From: Johannes Schlüter [mailto:johan...@schlueters.de]
Sent: Tuesday, April 27, 2010 9:40 AM
To: Pierre Joye
Cc: Gwynne Raskind; Ilia Alshanetsky; Kalle Sommer Nielsen; Lukas Kahwe
Smith; Andi Gutmans; Derick
+1 for Derick and Kalle, and +1 for alpha by Q4.
On Apr 27, 2010, at 8:53 AM, Ilia Alshanetsky wrote:
+1 for a co-RM of Derick and Kalle
On Tue, Apr 27, 2010 at 12:33 AM, Kalle Sommer Nielsen ka...@php.netwrote:
Hi
2010/3/24 Lukas Kahwe Smith m...@pooteeweet.org:
Yeah, lets get that
On Mar 30, 2010, at 11:41 PM, Philip Olson wrote:
It's awesome that PHP has so many great options for the next Release Manager
because all of the proposed people would do great. However, I'd like to see
Rasmus become RM. Not sure about the co-RM topic but Chris Jones comes to
mind. I love
On Mar 14, 2010, at 12:58 PM, David Soria Parra wrote:
I would also like to bring up another point. Since we are now on SVN (and
there are nice bridges to DVCS for those that want to use them), we can now
also more easily enable developers to work on complex or risky features in a
branch
On Mar 12, 2010, at 5:33 AM, Pierre Joye wrote:
Having tests in multiple branches is PITA. Hasn't anyone considered that the
best way would be to move all tests into their own repository
(directory..whatever :) in SVN..? Considering they are supposed to be used
for testing against regressions
On Mar 12, 2010, at 9:28 PM, Chris Trahey wrote:
The old class is still there, think of it as if the inserted (overloading)
class extends the base (overloaded) class and any classes the were extending
the base now extend the inserted class. So as far as the runtime, it's
run-of-the-meill
On Jan 19, 2010, at 5:54 PM, Alain Williams wrote:
$eep-oop()-ork()-ah()-ah();
the newcomer will have to spend significant time rummaging around the
source code to figure out what classes are involved.
As opposed to:
$oop = $eep-oop();
$ork = $oop-ork();
$ah = $ork-ah();
$ah2 = $ah-ah();
On Jan 18, 2010, at 3:51 AM, Jani Taskinen wrote:
Can you tell me what exactly we are breaking? divert calls should only be
used internally by autoconf and the, apparently useless, usage of them in
php makes it fail to build with any other autoconf.
If you remove them, things break. I don't
On Jan 16, 2010, at 4:18 PM, Jani Taskinen wrote:
115-autoconf_ftbfs.patch
Hell no. You're breaking the configure again with this crap. I already
reverted the idiocy once, don't even think about doing this shit again. PHP
configure works properly only with autoconf-2.13 which was the last
Some while ago, I committed a patch to trunk which adds the shell_bypass option
to proc_open() on UNIX. I'd like to backport that patch to 5.3.2, along with
posix_pipe(), which helps quite a bit in using it. The patch can be found at
http://pastebin.ca/raw/1691644. It's been tested and run
On Sep 3, 2009, at 8:56 AM, Richard Quadling wrote:
2009/9/3 techtonik techto...@php.net:
Greeetings to php-core developers,
Am I right that there is no https:// and svn+ssh:// access to
svn.php.net repositories?
If that's the case - how do you feel about sniffing developer's
passwords?
I'm the wrong person to send this email to. Forwarding to internals.
-- Gwynne
Begin forwarded message:
From: Cristian Rodríguez c...@cristianrodriguez.net
Date: August 10, 2009 12:14:08 PM EDT
To: gwy...@php.net
Subject: [PATCH] php bugtracker should set Precendence: bulk header
php bug
On Aug 7, 2009, at 11:39 AM, Lewis Wright wrote:
http://bugs.php.net/bug.php?id=48880 is reason enough to want a
release soon - PHP 5.3 died a very fast death in production here.
for me too. this bug makes 5.3.0 unusable for me. svn is not an
option for
production environment.
Thanks,
Andre
On Jul 30, 2009, at 7:12 AM, Alexey Zakhlestin wrote:
Implemented functions:
- mb_ereg()
- mb_ereg_replace()
as ereg functions are deprecated in 5.3, are these still needed?
these have nothing in common with those ereg functions. these are
based on onuguruma regex library
On Jul 30, 2009, at 11:27 AM, Stefan Walk wrote:
and that there's nothing you can do with Oniguruma that you can't
also practically do with PCRE (to the best of my knowledge),
http://www.geocities.jp/kosako3/oniguruma/doc/RE.txt - Paragraph 8,
example 2 - specifying the nest level for
On Jul 27, 2009, at 4:22 PM, Kenan Sulayman wrote:
Regarding:42194 Open $argc/$argv[] won't work when .php
extension is assigned to php.exe
Hi Folks!
Isn't it supposed to NOT pass the parameters when a script is called
passively?
For instance, we assume I'd call:
| script.php abc
On Jul 27, 2009, at 6:31 PM, Takeshi Abe wrote:
Just to be sure, is there any consensus on this? I thought I should
use svn merge.
README.SVN-RULES says
1. All changes should first go to trunk and then get merged from
trunk
(aka MFH'ed) to all other relevant branches.
which I've
For the sake of the heck of it, I'm gonna offer up this tiny patch I'm
using in one of my projects. I don't really care if it gets included
in anything or not, just thought it might interest someone.
Effect: Adds a ?php= syntax which behaves identically to ?=, but
works without the use of
that was actually compliant, but:
?php. - is not visually distinctive
?php- - same
?php.e - saves very little typing and is ugly
?phpe - mucks with the entire idea of being namespaced
?php e - visually confusing and saves little typing
And so forth.
Gwynne Raskind wrote
On Jul 23, 2009, at 9:21 PM, Gwynne Raskind wrote:
Today, I just release a new version of the Log package, and I
attempted to tag this release in the same way. Unfortunately, I ran
into this error:
$ svn copy \
http://svn.php.net/repository/pear/packages/Log/trunk \
http://svn.php.net
On Jul 20, 2009, at 6:40 AM, Jani Taskinen wrote:
Can I suggest you not to suggest any other VCS from now on?
If you like some VCS better, just keep that info to yourself, no
need to spam the mailing lists about it.
More to the point, there was a considerable amount of controversey
over
is already
initialized to NULL
I think that's it :) It's only minor things, I guess.
As soon as you fix these things, please go ahead and commit the
patch, or mail it back to the ML in case you need me to do it.
Nuno
- Original Message - From: Gwynne Raskind gwy...@darkrainfall.org
On Jul 16, 2009, at 6:19 PM, Jani Taskinen wrote:
Or just to something more generic like php-commits@ ? The same with
zend-commits?
Only php-commits@ is necessary since there is no separate Zend stuff
anymore..?
Zend commits are still sent separately. From commit-email.php:
On Jul 14, 2009, at 4:36 PM, Knut Urdalen wrote:
Any other issues, please bring them to my attention. Preferably via
email, not IRC :).
Are we going to have a similar page like the one for Anonymous CVS
Access [1] for svn.php.net?
Please in the future avoid cross-posting to seven lists;
On Jul 13, 2009, at 12:51 PM, Pierre Joye wrote:
pajoye Mon, 13 Jul 2009 16:11:45 +
ViewVC URL: http://svn.php.net/viewvc?view=revisionrevision=284019
Changed paths:
A php/php-src/trunk/win32/build/svnclean.js
Log:
- rename to svn
Copied:
As of right now, I'm declaring SVN open to full time use. Commit away,
everyone!
There are still a number of issues to resolve, but development's been
held up too long. We'll fix the issues as we go. Some known issues:
- Rsync is still down. Derick's working on this.
- SVN access over HTTP
The conversion from CVS to SVN is complete. CVS read AND write access
has been completely disabled. SVN is now up and running, however *we
remain in commit freeze* until Monday. Commits to SVN in order to fix
critical problems (such as all those scripts which should have been
made ready a
On Jul 7, 2009, at 1:17 PM, Andrei Zmievski wrote:
I would like to ask all developers to voice their opinions of
whether it makes sense to add this to 5.3 or to throw it away
(either one is fine btw). To keep the process simple flamewar
free, please restrict yourself to +/- (1/0), next
I apologize for the top-quoting, but it seemed appropriate here.
It seems the language of the documentation is unclear. It is not that
the CGI SAPI (now called the CGI-FCGI SAPI) is always built, in the
fashion of CLI. It is, precisely, that the FastCGI support within the
CGI SAPI can no
In Ilia's type hinting patch, on line 255, is the line:
+ST_IN_SCRIPTINGstring|binary|unicode {
This failed for me. I fixed it by changing it to:
+ST_IN_SCRIPTING(string|binary|unicode) {
Which matches all the other lexing rules for type hints. My
understanding of the lexer is insufficient
On Jul 1, 2009, at 12:59 PM, Ilia Alshanetsky wrote:
There has been quite a bit of discussion on this list, IRC,
developer meetings, etc... about introduction of type hinting to
PHP. Most people appear to think that this would be a good idea, but
there is a reason why it is not in PHP
On Jul 1, 2009, at 2:37 PM, Gelu Kelunden wrote:
I think that the official FastCGI implementation will eventually
evolve into something like PHP-FPM, if not even more.
What I'm saying is that code that handles daemonization (uid/gid/
chroot/log), workers mgmt (spawing/safe-shutdown), daemon
On Jun 26, 2009, at 2:22 PM, Hannes Magnusson wrote:
We would like to up hold the commit freeze until 5.3.0 is announced
next
Tuesday.
And the move to SVN? It'll require a complete cvs.php.net freeze for
couple of days, I think?
Yes, but it's not ready for that yet; an unfreeze after 5.3's
I've just finished making this patch for my own use (diffed against
5.3 CVS):
http://darkrainfall.org/php-5.3-shellbypass.patch
In short, what it does is make proc_open()'s shell_bypass option
available to UNIX systems. This is accomplished by allowing the
command parameter to proc_open()
On Jun 25, 2009, at 11:41 AM, Joe Stump wrote:
Once we're using GitHub, what are the benefits?
For me, they are as follows:
1. Built in bug tracking and wiki.
2. Fork Queue. I can't even begin to express the awesomesauce that
is the Fork Queue. Ever get a patch to your project as an
On Jun 23, 2009, at 3:49 PM, Johannes Schlüter wrote:
While documenting header_remove() I was experimenting a little bit..
If an empty argument is passed to the function (empty string, null,
false,..) the function doesn't do anything, as it checks for
ZEND_NUM_ARGS() rather then the length of
In the last two days I've made some significant improvements to the
migration process for CVS - SVN. I know many have been proponents of
Git, but SVN is closer to being viable at this point. Crossposting to
internals@ so that more people have a chance to look into it, I'm
calling for
I ran the entire PHP testsuite (as compiled on my system) under
valgrind for Darwin and came up with quite a mess of leaks and a
couple of crashes.
The results file is quite ginormous, so I uploaded it to my site for
the morbidly curious to have a look at:
On Jun 21, 2009, at 6:23 AM, zoe wrote:
Guys and gals, in the old days we had a very close tie between the
code
and the documentation. As the project has grown the two have drifted
apart. I think this is mostly because the phpdoc team has done an
amazing job keeping up with the code changes
Here is a nice simple patch for #48575 which rips out the mach-o/
dyld.h functionality in Zend (as suggested by the original reporter
and the Apple comment). According to my testing this not only doesn't
break anything, but actually doesn't change anything either except
removing some dead
On Jun 18, 2009, at 10:46 AM, Gwynne Raskind wrote:
Here is a nice simple patch for #48575 which rips out the mach-o/
dyld.h functionality in Zend (as suggested by the original reporter
and the Apple comment). According to my testing this not only
doesn't break anything, but actually doesn't
On Jun 18, 2009, at 10:55 AM, Scott MacVicar wrote:
Here is a nice simple patch for #48575 which rips out the
mach-o/dyld.h functionality in Zend (as suggested by the original
reporter and the Apple comment). According to my testing this not
only
doesn't break anything, but actually doesn't
On Jun 18, 2009, at 1:09 PM, jvlad wrote:
If the bug #48583 can't be accepted through bugs.php.net, I think it
makes
sense to discuss it here.
It's not a bug but chicken'n'egg' issue. Errors are displayed by
default
(IIRC) so if the ini file does not get parsed an error is outputted
which
http://svn.php.net/
This URL, accessible both by web browser and Subversion clients, now
contains the current revision of the converted CVS repository.
At the moment there is NO authorization or authentication scheme in
place; the repository is limited to read-only access. I would like to
On Jul 25, 2008, at 6:34 AM, Hannes Magnusson wrote:
At this point it's clear that moving from CVS to SVN for PHP has
become a
more or less official project.
Has the phpdoc revision/translation problem been looked into/fixed?
No, not yet, but it will have to be. I intend for discussion on
On Jul 24, 2008, at 8:05 PM, Rasmus Lerdorf wrote:
Now that Subversion 1.5 has been out for a little while and it is at
the point where it might actually have some benefit to us, do we
have some volunteers who have some time to try converting over the
repository and all the post-commit and
On Jul 24, 2008, at 8:23 PM, Rasmus Lerdorf wrote:
Now that Subversion 1.5 has been out for a little while and it is at
the point where it might actually have some benefit to us, do we
have
some volunteers who have some time to try converting over the
repository and all the post-commit and
At this point it's clear that moving from CVS to SVN for PHP has
become a more or less official project. As such, there is a new
mailing list [EMAIL PROTECTED] for anyone who wants to
help with the move. If you're familiar with what I've already done so
far
On Jul 24, 2008, at 10:14 PM, Sean Coates wrote:
Do we have a preference of Apache's SVN or svnserve?
The former requires Apache 2+, AFAIK.
I'd like to kick this discussion over to the svn-migration@ list;
there are a lot of points to consider in this question and internals@
has enough
On Jul 19, 2008, at 6:55 AM, Lars Strojny wrote:
Hi everbody,
regarding my mail from yesterday, I've also created an RFC for the new
error level.
http://wiki.php.net/rfc/e-user-deprecated-warning
cu, Lars
A large +1 from me too.
-- Gwynne, Daughter of the Code
This whole world is an asylum
On Jul 3, 2008, at 4:41 AM, Lukas Kahwe Smith wrote:
Absolutely agree.
I don't see any reason for 5.4. We don't plan any significant new
features.
You guys are scaring me ..
I was hoping to evade such discussions. PHP 5.3 is probably the
minor version release with the most major changes
On Jun 26, 2008, at 4:06 AM, Lukas Kahwe Smith wrote:
Now, upon execution of the code containing the closure, the new
opcode
just copies the zend_function structure into a copy, registers that
copy
as a resource and returns that resource. As soon as the resource is
garbage collected (or
On Jun 18, 2008, at 2:36 AM, Alexey Zakhlestin wrote:
1) I am not sure that the current semantics of the lexical
keyword is great in all cases. Is the reason why you don't allow by-
value binding so that we don't have to manage more than one lambda
instance per declaration?
by-reference
On Jun 18, 2008, at 11:01 AM, Stanislav Malyshev wrote:
The Lua interpreter handles this by resolving variable references
as they're made; someVariable1 is looked up in the closure's
scope and not found, so the interpreter steps out one scope and
looks for it
You may get into a problem here
On Apr 24, 2008, at 3:19 AM, Antony Dovgal wrote:
On 08.03.2008 02:20, Gwynne Raskind wrote:
gwynne Fri Mar 7 23:20:32 2008 UTC
Modified files: (Branch: PHP_5_3)
/php-src/ext/session mod_user.c mod_user.h php_session.h
session.c Log:
MFH: fix bug #32330
On Apr 11, 2008, at 8:29 AM, Ilia Alshanetsky wrote:
Edin, our previous Win32 build master appears to be indisposed at
the moment hence lack of win32 binaries. If someone else wants to
produce them great, if not, we'll go on without them.
I'd be willing to take a bash at it. What's
On Apr 1, 2008, at 4:45 PM, Johannes Schlüter wrote:
-O2 is prepended to CFLAGS; with GCC the *last* -O option specified
takes precedence. Anything specified by the user will thus override
the default -O2. I admit this isn't the cleanest possible solution,
but it works, and I don't understand
On Mar 31, 2008, at 5:41 PM, Benjamin Schulz wrote:
This commit is responsible for the bad performance:
http://cvs.php.net/viewvc.cgi/php-src/configure.in?r1=1.579.2.52.2.77.2.11r2=1.579.2.52.2.77.2.12diff_format=u
-gstabs versus -g should have no effect on production performance.
Ok, maybe i
On Mar 24, 2008, at 8:59 AM, Marcus Boerger wrote:
Hello Lars,
to me this makes pretty much sense on a second glance as it perfectly
reflects what our string would do. And for someone learning 'NOWDOC',
using HEREDOC seems just natural.
So I am all +1
Consistency and satisfying expectations
I'd be in favor of this idea because it sounds cool, but it has some
crippling drawbacks:
- There isn't really a homogenous way to build PHP without OS-
specific checks. There's just too much that even the most minimal
build needs to know about its host system.
- configure.php wouldn't be
My two US cents :).
On Mar 19, 2008, at 9:17 PM, Jani Taskinen wrote:
Here is a quick run down of some of the features of CMake and tools
associated with it:
• A single configure script that would be used regardless of the OS
• A much simpler scripting language
m4 is simple. :-p
Since
On Mar 5, 2008, at 9:52 PM, David Coallier wrote:
I'm talking about extension developers. We will all have to add yet
another #ifdef for this function, in the implementation or to
define
php_dirname to keep the implementation clean(er). As it is good to
clean up codes, I'm not sure to remove
I've created a patch, including a new test, for bug #32330
(session_destroy, Failed to initialize storage module, custom
session handler). There are three versions of the patch (for PHP_5_2,
PHP_5_3, and HEAD):
http://www.wanderingknights.org/maryoku/bug32330-PHP_5_2.diff
On Jan 22, 2008, at 5:29 AM, Pierre wrote:
On Jan 21, 2008 3:38 PM, Antony Dovgal [EMAIL PROTECTED] wrote:
6 reasons why we must to get rid of The Switch ASAP
I was +1 months ago, I'm still +1 now :)
I'll throw in my +1 too. That's right, I'm still alive! :)
-- Gwynne, Daughter of the Code
The attached patch adds basic support for storing properly-typed
integer and boolean data in SQLite3 databases. I don't really
understand why this kind of support has been so consistently lacking
in PHP database driver implementations. Similar problems have plagued
the MySQL and MySQLi
On Aug 15, 2007, at 2:00 PM, Christopher Jones wrote:
Did you get any further with merging this? It would help users of
the XQuery language.
If I understand your intent, I would be able to change the code
fragment
below to use a nowdoc, and not have to escape the XQuery $i variables.
Chris
1 - 100 of 112 matches
Mail list logo
