A couple of points. mysqli doesn't have persistent connections because
the authors of that particular extension don't think it is a good idea.
It's not a PHP-wide thing, PDO and others do have it.
If you are going to FastCGI for performance and scalability reasons
because you don't want a heavyw
Christopher Jones wrote:
steve wrote:
> Oh, and allow persistent connections in db apis again (like mysqli).
It might happen. Wez Furlong was contemplating a persistent
connection implementation for the generic PDO interface following
on from the persistent connection model in the oci8 extensi
Gregory Beaver wrote:
> __COMPILER_HALT_OFFSET__. This does change behavior in that
> __COMPILER_HALT_OFFSET__ can only be used within the same file that it
> is defined. However, this is extremely unlikely to break any existing
> scripts since it was designed for self-contained installers, and t
Hi,
With the first release of pecl/phar, I have started thinking about the
implementation of __HALT_COMPILER();
Currently, this code results in a fatal error:
file1.php:
file2.php:
file3.php:
The current implementation simply defines __COMPILER_HALT_OFFSET__ as
the first __HALT_COMPILER();
Hey everyone,
I was just curious if there were any known issues with the PHP6 builds
on Windows. I've been trying to set a build up in my local environment
and Apache keeps throwing this error at me:
Syntax error on line 173 of C:/Apache2/conf/httpd.conf: Can't locate API
module structure `p
steve wrote:
> Oh, and allow persistent connections in db apis again (like mysqli).
It might happen. Wez Furlong was contemplating a persistent
connection implementation for the generic PDO interface following
on from the persistent connection model in the oci8 extension for
Oracle.
> As an exa
From my experience with PHP over the years, in setups with both low
and high traffic, I'd like to humbly put out a suggestion: have PHP
include its own FastCGI SAPI in PHP 5.x and make it the
default/recommended in PHP 6. Oh, and allow persistent connections in
db apis again (like mysqli).
The c
On Tue, February 6, 2007 8:17 am, LAUPRETRE François (P) wrote:
>> From: Richard Lynch
>>
>> How many newbies will be trying:
>> array[1, 2, 3];
>> and left scratching their heads when it doesn't work?
>
> Yes, even if I am in favor of the [] syntax, it is a good argument:
> 'array[ 1, 2, 3]' can
>
Actually, this one was prompted by seeing a bug fix or changelog about
requiring { } and : endif; to match up, rather than accepting
either/or in balance.
Synchronicity that I even saw that item, but there it is.
I would HOPE that they'd have to balance, but if they don't for the
long block synta
On Tue, February 6, 2007 11:26 am, Andrei Zmievski wrote:
> On Feb 5, 2007, at 3:37 PM, Richard Lynch wrote:
>
>> Yes, and it makes life miserable for some of us...
>>
>> Is that a good reason to extend that misery to yet another operator?
>
> Richard, please. This is not advanced OO stuff or anyth
Yeah but process limits are inherited after fork().
> -Original Message-
> From: Reinis Rozitis [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 06, 2007 3:28 AM
> To: internals@lists.php.net
> Subject: Re: [PHP-DEV] FastCGI limit memory
>
> Andi Gutmans wrote:
> > Don't the FastCGI
On Tue, 2007-02-06 at 15:41 +, Ford, Mike wrote:
> On 06 February 2007 14:42, Robert Cummings wrote:
>
> > On Tue, 2007-02-06 at 14:08 +, Ford, Mike wrote:
> > > On 05 February 2007 17:29, Brian Moon wrote:
> > > > That is why you have coding standards. Our doucment states that
> > > > th
Now you're just grandstanding.
-Andrei
On Feb 5, 2007, at 3:55 PM, Richard Lynch wrote:
More edge cases:
$foo = array(1, 2, 3];
$bar = [1, 2, 3);
Syntax error because it's unbalancedO
Or kosher, because the choice of start/end delimiters should be up to
the user?
Should it match whatever
That's because you wouldn't be using those words with a newbie, if
you are smart. You'd simply say "it works like list() here" and "it
works like array()" here.
-Andrei
On Feb 5, 2007, at 3:41 PM, Richard Lynch wrote:
On Mon, February 5, 2007 12:06 pm, Andrei Zmievski wrote:
On Feb 4, 20
On Feb 5, 2007, at 3:37 PM, Richard Lynch wrote:
Yes, and it makes life miserable for some of us...
Is that a good reason to extend that misery to yet another operator?
Richard, please. This is not advanced OO stuff or anything close.
It's an operator. Give PHP users (even newbies) some cre
On 06 February 2007 14:42, Robert Cummings wrote:
> On Tue, 2007-02-06 at 14:08 +, Ford, Mike wrote:
> > On 05 February 2007 17:29, Brian Moon wrote:
> > > That is why you have coding standards. Our doucment states that
> > > this should be written as:
> > >
> > > $a = array(
> > > 1 => a
Hi.
Our 'newbie' at least has a good chance of figuring out
$a = [1,2,3] vs.$a = array(1,2,3)
is different than
$a = foobar(1,2,3)
I am probably out of my depth here...but I actually find the argument
about wether to introduce this syntax or not, very entertaining...it'
how it is different? How explaining array written as [] so much harder
that explaining array written as ()? What exactly constitutes the
problem?
Here's the difference:
You can Google for 'array' and learn a lot.
If you try to Google for [] you don't learn squat.
Try it and see.
So our 'newb
On Tue, Feb 06, 2007 at 04:16:28PM +0100, Christian Schneider wrote:
> Alain Williams wrote:
> > Anyway: it makes php look like perl -- and that would never do :-)
>
> Can we please stop that FUD? (even if it is meant as a joke)
No: it was NOT a serious point. What is wrong with the occasional gr
Alain Williams wrote:
> Anyway: it makes php look like perl -- and that would never do :-)
Can we please stop that FUD? (even if it is meant as a joke)
... if at all then you might say it looks like Javascript, Python or
Ruby. Perl uses an ugly mix of () and [] to emulate multi-dimensional
arrays
On Tue, Feb 06, 2007 at 09:41:34AM -0500, Robert Cummings wrote:
> On Tue, 2007-02-06 at 14:08 +, Ford, Mike wrote:
> > On 05 February 2007 17:29, Brian Moon wrote:
> > > That is why you have coding standards. Our doucment states that this
> > > should be written as:
> > >
> > > $a = array(
On Tue, 2007-02-06 at 14:08 +, Ford, Mike wrote:
> On 05 February 2007 17:29, Brian Moon wrote:
> > That is why you have coding standards. Our doucment states that this
> > should be written as:
> >
> > $a = array(
> > 1 => array('pears', 'apples'),
> > 2 => array('juice', 'oranges')
On 05 February 2007 17:32, Brian Moon wrote:
> Reading the array thread, someone mentioned having several ways of
> doing things. One of their examples was the if: endif; syntax.
> Forgive me if this has been discussed, but has anyone proposed
> removing that for PHP6? Seems like the perfect ti
> From: Richard Lynch
>
> How many newbies will be trying:
> array[1, 2, 3];
> and left scratching their heads when it doesn't work?
Yes, even if I am in favor of the [] syntax, it is a good argument: 'array[ 1,
2, 3]' can
become a very common error, and not especially among newbies!
Maybe I a
On 05 February 2007 17:29, Brian Moon wrote:
> Ford, Mike wrote:
> > > I don't find:
> > >
> > > $a = [1 => ['pears', 'apples'], 2 => ['juice', 'oranges']];
> > >
> > > any less readable than:
> > >
> > > $a = array(1 => array('pears', 'apples'), 2 => array('juice',
> > > 'oranges'));
> > >
>
Andi Gutmans wrote:
Don't the FastCGI processes inherit memory limits from their parent? (assuming
you're not running standalone FastCGI which almost
noone does).
Nope, the parent (master) process only keeps the track of active childs
(usually I spawn like 250 of them) and distributes the in
26 matches
Mail list logo
