On Wed, 9 Jan 2008, Larry Garfield wrote:
On Wed, 9 Jan 2008 17:14:29 -0300, Cristian Rodriguez [EMAIL PROTECTED]
wrote:
2008/1/9, Derick Rethans [EMAIL PROTECTED]:
Why do you need this?
It is simple, even releasing an update for a particular extension,
trigger the whole
On Thu, 10 Jan 2008, sean finney wrote:
On Wednesday 09 January 2008 08:50:59 pm Ilia Alshanetsky wrote:
The reason we do not use the system database is because it is
inconsistent and likely is updated less frequently then the one
included with PHP.
Personally I think this patch would
use ProjectA; is equivalent of use ProjectA as ProjectA;
if you want to use something from namespace you should use that something.
for example: use ProjectA::BOOK;
On 1/10/08, Tomi Kaistila [EMAIL PROTECTED] wrote:
Sorry for the ambiguous subject line, but I could not find a better wording
Hello, lists,
I'm tired to type array() many times. And I want to
declare arrays more easily. So I wrote the patch for
zend_language_parser.y which enables to declare arrays
with square brackets like some other languages.
Stanislav,
Sorry, I'm new in this list and I didn't know about past
Hello, lists,
We have discussed about implementing anonymous functions and
closures in PHP.
However, I consider that implementing anonymous functions and
implementing lexical scopes should be discussed separately.
# Even though I like closure. ;-)
So I wrote anonymous function patch for PHP 5.3
Hello Ryusuke,
I like b) !
marcus
Thursday, January 10, 2008, 11:07:36 AM, you wrote:
Hello, lists,
I'm tired to type array() many times. And I want to
declare arrays more easily. So I wrote the patch for
zend_language_parser.y which enables to declare arrays
with square brackets like
Hello Ryusuke,
+1, looks pretty nice, makes my life easier in some cases and is closer to
other languages like pythin so i can transfer concepts easily which is a
big plus for me.
marcus
Thursday, January 10, 2008, 11:09:26 AM, you wrote:
Hello, lists,
We have discussed about
Hi Sean,
On Jan 10, 2008 5:10 AM, sean finney [EMAIL PROTECTED] wrote:
Hi Ilia, Joe,
On Wednesday 09 January 2008 08:50:59 pm Ilia Alshanetsky wrote:
The reason we do not use the system database is because it is
inconsistent and likely is updated less frequently then the one
included
Yes, I know. My suggestion/inquiry was about changing this behavior. So
instead of use ProjectA; being equivalent to use ProjectA as ProjectA; by
leaving the as Something out the default namespace would be changed.
So by calling use ProjectA; the default namespace would change from global
to
On 10/01/2008, Marcus Boerger [EMAIL PROTECTED] wrote:
Hello Ryusuke,
+1, looks pretty nice, makes my life easier in some cases and is closer to
other languages like pythin so i can transfer concepts easily which is a
big plus for me.
marcus
Thursday, January 10, 2008, 11:09:26 AM,
Thanks for all the feedback.
On Wed, Jan 09, 2008 at 09:03:02PM +0100, Derick Rethans wrote:
On Wed, 9 Jan 2008, Joe Orton wrote:
It's a bit of a maintenance headache for distributions when
packages include their own copy of the timezone database, since this
needs to be updated
If we are going to implement this, I think we should use the (b) syntax
since its how you define array elements today
On Jan 10, 2008 8:19 AM, Marcus Boerger [EMAIL PROTECTED] wrote:
Hello Ryusuke,
I like b) !
marcus
Thursday, January 10, 2008, 11:07:36 AM, you wrote:
Hello, lists,
On Jan 10, 2008, at 1:05 PM, Joe Orton wrote:
I'm not sure I find the logic of the but the system-provided data
will
become stale arguments convincing; systems which are left
unmaintained
by the administrators will have old versions of software on; that's a
given. I can't see why adding
So you reject scalar type hinting because it isn't type casting and
can therefor confuses newbies - but scattering seemingly random
brackets around your code (to safe 5 key strokes) is obvious to users?
Noone would confuse this with named arguments?
Why can't I do function foo([] $array) {} ?
Hi,
On Jan 10, 2008 3:56 PM, Hannes Magnusson [EMAIL PROTECTED] wrote:
So you reject scalar type hinting because it isn't type casting and
can therefor confuses newbies - but scattering seemingly random
brackets around your code (to safe 5 key strokes) is obvious to users?
Noone would
I like b.
On Thu, 2008-01-10 at 19:07 +0900, Ryusuke SEKIYAMA wrote:
Hello, lists,
I'm tired to type array() many times. And I want to
declare arrays more easily. So I wrote the patch for
zend_language_parser.y which enables to declare arrays
with square brackets like some other languages.
On Jan 10, 2008, at 3:12 PM, Tomi Kaistila wrote:
Well if confusing is the goal, then yes, since this is classic Perl.
I started using PHP, instead of Perl, just so that I would not need
play
around with confusing syntax.
Right, PHP was always about making it easy to see whats going on
Well if confusing is the goal, then yes, since this is classic Perl.
I started using PHP, instead of Perl, just so that I would not need play
around with confusing syntax.
Tomi Kaistila
PHP Developer
On Thursday 10 January 2008 15:56:54 Hannes Magnusson wrote:
So you reject scalar type
On Thu, 2008-01-10 at 14:56 +0100, Hannes Magnusson wrote:
So you reject scalar type hinting because it isn't type casting and
can therefor confuses newbies - but scattering seemingly random
brackets around your code (to safe 5 key strokes) is obvious to users?
Noone would confuse this with
On Thu, 2008-01-10 at 16:18 +0200, Giedrius D wrote:
Hi,
On Jan 10, 2008 3:56 PM, Hannes Magnusson [EMAIL PROTECTED] wrote:
So you reject scalar type hinting because it isn't type casting and
can therefor confuses newbies - but scattering seemingly random
brackets around your code (to
I just tried this out using option b, and I really like it.
$var = [1, 6, 434] ;
I think it looks good and helps code readability alot.
On Thu, 2008-01-10 at 19:07 +0900, Ryusuke SEKIYAMA wrote:
Hello, lists,
I'm tired to type array() many times. And I want to
declare arrays more easily.
Did you know that you don't have to reply multiple times to the same post?
And even though Stas replies to every single post, you don't have to do it too.
Please read Andis checklist again;
http://news.php.net/php.internals/34494 - same rules apply to all
threads.
-Hannes
On Jan 10, 2008 3:37
On Jan 10, 2008 9:39 AM, Sam Barrow [EMAIL PROTECTED] wrote:
On Thu, 2008-01-10 at 14:56 +0100, Hannes Magnusson wrote:
So you reject scalar type hinting because it isn't type casting and
can therefor confuses newbies - but scattering seemingly random
brackets around your code (to safe 5
On Thu, 13 Dec 2007, Gregory Beaver wrote:
We don't need moderation, we don't need read-only. We need people to
follow a simple common-sense checklist.
It's either that nobody saw this mail, or chose to ignore it. Obviously,
nothing changed and I'm getting sick and tired of all this crap on
On 10-Jan-08, at 10:33 AM, Derick Rethans wrote:
On Thu, 13 Dec 2007, Gregory Beaver wrote:
We don't need moderation, we don't need read-only. We need people to
follow a simple common-sense checklist.
It's either that nobody saw this mail, or chose to ignore it.
Obviously,
nothing
On 10.01.2008 18:33, Derick Rethans wrote:
On Thu, 13 Dec 2007, Gregory Beaver wrote:
We don't need moderation, we don't need read-only. We need people to
follow a simple common-sense checklist.
It's either that nobody saw this mail, or chose to ignore it. Obviously,
nothing changed and
On 10-Jan-08, at 10:58 AM, Lukas Kahwe Smith wrote:
I know that PHP has so far stayed clear of processes and I am fine
with keeping it this way. But I really think that some of these
flames should best be taken off list into some work group that
provides summaries at semi regular
Lukas Kahwe Smith wrote:
On Jan 10, 2008, at 1:05 PM, Joe Orton wrote:
I'm not sure I find the logic of the but the system-provided data will
become stale arguments convincing; systems which are left unmaintained
by the administrators will have old versions of software on; that's a
given. I
On Sun, 16 Dec 2007, Derick Rethans wrote:
On Wed, 5 Dec 2007, Derick Rethans wrote:
On Tue, 27 Nov 2007, Wez Furlong wrote:
All will be revealed soon.
Just wondering what sort of timeframe you mean with soon... any idea?
We're atleast another week futher along without any
On Jan 10, 2008, at 4:51 PM, Ilia Alshanetsky wrote:
On 10-Jan-08, at 10:33 AM, Derick Rethans wrote:
On Thu, 13 Dec 2007, Gregory Beaver wrote:
We don't need moderation, we don't need read-only. We need people
to
follow a simple common-sense checklist.
It's either that nobody saw
hi derick,
On Thursday 10 January 2008 09:50:14 am Derick Rethans wrote:
Personally I think this patch would be great, and I will recommend it to
the other debian php maintainers for review.
Let me just remind you:
This patch BREAKS functionality.
which of course should be avoided if at
hey pierre,
(removed some folks from the cc)
On Thursday 10 January 2008 11:22:52 am Pierre wrote:
Besides the issues listed by Derick, there is two problems with these
choices (distro making design changes to upstream software). First it
that's sort of the point of open-source software,
Could someone please commit this? I just hit the same issue again.
Thanks,
- Steph
- Original Message -
From: Steph Fox [EMAIL PROTECTED]
To: internals internals@lists.php.net
Sent: Friday, December 14, 2007 9:40 AM
Subject: [PHP-DEV] Extension dependencies in win32 build
Hi all,
I recommended (b) a few months back and got shot down :)
I still like it :)
Andi
-Original Message-
From: Ryusuke SEKIYAMA [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 10, 2008 2:08 AM
To: internals@lists.php.net
Cc: Marcus Boerger; Stas Malyshev
Subject: [PHP-DEV] [RFC]
I think next time Sam has three consecutive responses to the same thread
then he loses access to the list for a week :) (same rule for anyone
else). Tweaking the 'Subject' won't count as a different thread :)
Andi
-Original Message-
From: Hannes Magnusson [mailto:[EMAIL PROTECTED]
Hi,
On Jan 10, 2008 11:07 AM, Ryusuke SEKIYAMA [EMAIL PROTECTED] wrote:
b) Commit square bracket array shortcut patch
keys and values are separated by double arrows.
( http://www.opendogs.org/pub/php-5.3dev-080109-sbar2.patch )
e.g.
$a = [1, 2, 3];
$b = ['foo' =
On Jan 10, 2008, at 4:55 PM, Antony Dovgal wrote:
On 10.01.2008 18:33, Derick Rethans wrote:
On Thu, 13 Dec 2007, Gregory Beaver wrote:
We don't need moderation, we don't need read-only. We need people
to
follow a simple common-sense checklist.
It's either that nobody saw this mail, or
On Thu, 10 Jan 2008, Hannes Magnusson wrote:
So you reject scalar type hinting because it isn't type casting and
can therefor confuses newbies - but scattering seemingly random
brackets around your code (to safe 5 key strokes) is obvious to users?
Noone would confuse this with named
Marco Tabini wrote:
On 10-Jan-08, at 10:58 AM, Lukas Kahwe Smith wrote:
I know that PHP has so far stayed clear of processes and I am fine
with keeping it this way. But I really think that some of these flames
should best be taken off list into some work group that provides
summaries at
On Thu, Jan 10, 2008 at 04:14:46PM -0600, Gregory Beaver wrote:
At the very least, some kind of centralized RFC tracker (like PEAR's
PEPr for package proposals) would be a potential way to track features
that would introduce slightly more work (another thing to maintain at
php.net for web
On Jan 10, 2008 2:40 PM, Andi Gutmans [EMAIL PROTECTED] wrote:
I think next time Sam has three consecutive responses to the same thread
then he loses access to the list for a week :) (same rule for anyone
else). Tweaking the 'Subject' won't count as a different thread :)
Andi
An example assignment such as:
$x = 10;
doesn't seem to get handled as a simple ref-count incrementing
assignment (in zend_assign_to_variable()). Instead, $x ends up getting a
new zval into which a
copy of the RHS (10) is made.
This seems to be because the zval/znode corresponding to
At the very least, some kind of centralized RFC tracker (like PEAR's
PEPr for package proposals) would be a potential way to track features
Maybe just for the start create a wiki or something that people could
put their RFCs to and edit them, and then hopefully somebody would step
up to
Op arrays are read-only. This is a design goal and is especially
important for byte code caches where several processes are looking at
the same op array. Therefore setting IS_CONST to is_ref=1/refcount=2 we
are ensuring that they will not be changed.
The copy happens only the first time and
Andi 2003:
http://www.mail-archive.com/internals@lists.php.net/msg03896.html
Andi's brain evolves 2007:
http://marc.info/?l=php-internalsm=117057393530217w=2
And today I'm still +1.
I really think by looking at some of the examples I worked through with
my original posting in February
2008/1/10, Pierre [EMAIL PROTECTED]:
Besides the issues listed by Derick, there is two problems with these
choices (distro making design changes to upstream software).
Please don't add the timezone to the list
of troubles.
The vast mayority of PHP users obtain it via their OS vendor, isnt
On Thursday 10 January 2008, Tomi Kaistila wrote:
Well if confusing is the goal, then yes, since this is classic Perl.
I started using PHP, instead of Perl, just so that I would not need play
around with confusing syntax.
Tomi Kaistila
PHP Developer
The [] array literal syntax is also used
And my stance hasn't changed either:
http://marc.info/?l=php-internalsm=117060700805108w=2
Andi Gutmans wrote:
Andi 2003:
http://www.mail-archive.com/internals@lists.php.net/msg03896.html
Andi's brain evolves 2007:
http://marc.info/?l=php-internalsm=117057393530217w=2
And today I'm
Thanks, that helps.
#1. In my case, I don't have op_arrays that are shared by multiple
threads/processes. So I attempted to comment out the IS_CONST patching
(is_ref=1/refcount=2) that happens in pass_two() in the hope of
assigning constants by simple reference-count increments. While my basic
Hello all,
The array() syntax to me screams function call, something that, in my
mind, did not intuitively mean assign an array to a plain ole
variable.
If I can:
$var1 = 5;
why would I need a special function call array() to create and
assign an array?
An array is just like any other
The [] array literal syntax is also used by Javascript, and there's even an
object literal syntax, {}, which is quite nice. Does that mean Javascript
is classic Perl?
Yes, the first thing that comes to mind from this syntax is Perl.
(1, 2, 3, 4, 5)
(dharma, wilma, greg, mina)
qw{ wilhelm
Hi, I hope this is the appropriate list. I have been banging on this issue
for quite some time. Basically, I have an intermittent problem with
various stream calls.
Essentially, I see massive CPU utilization while waiting to get data from
some http locations, under some circumstances.
This is
2008/1/10, Rasmus Lerdorf [EMAIL PROTECTED]:
Making this an option for the distros is something we pretty much have
to do.
Yes, or otherwise distros will simple implement their own options. ;-)
And yes, I know it makes life harder for people writing portable
apps, but that's just the way it
53 matches
Mail list logo
