I'm -1 for removing constants and functions from the namespaces. As I
wrote already in another thread, is it possible to have a fatal error thrown
when the engine detects an ambiguity situation? Are there any logical (i
mean from OOP point of view) or internals (performance and so on) problems
Vesselin Kenashkov wrote:
I'm -1 for removing constants and functions from the namespaces. As I
wrote already in another thread, is it possible to have a fatal error thrown
when the engine detects an ambiguity situation? Are there any logical (i
mean from OOP point of view) or internals
Hi Brain,
A little bit different patch committed into PHP_5_3 and HEAD.
I don't think it's allowed to commit it into PHP_5_2.
Please verify, if it works for you.
Thanks. Dmitry.
Brian J. France wrote:
After some more testing I needed to tweak the patch and the example,
here is version 2.
Hi all
It looks like [DOC] has failed miserably, it is of no use if only few
people use it for few commits.
Adding to the fact there is almost no activity in the documentations
we really need to find a better way to organize things.
Currently we have [DOC], (closed) bug reports, NEWS and wiki all
On Wed, Oct 1, 2008 at 10:39 AM, Hannes Magnusson
[EMAIL PROTECTED] wrote:
Hi all
It looks like [DOC] has failed miserably, it is of no use if only few
people use it for few commits.
Adding to the fact there is almost no activity in the documentations
we really need to find a better way to
On Fri, 19 Sep 2008, Greg Beaver wrote:
Hi all,
There is a problem in the namespace implementation. This code demonstrates
the issue:
code.inc:
?php
namespace foo;
class test {
const my = 1;
static function bar(){}
}
namespace foo::test;
const my = 2;
function bar(){}
?
Derick Rethans schreef:
On Fri, 19 Sep 2008, Greg Beaver wrote:
Hi all,
There is a problem in the namespace implementation. This code demonstrates
the issue:
code.inc:
?php
namespace foo;
class test {
const my = 1;
static function bar(){}
}
namespace foo::test;
const my = 2;
[snip]
Many of us - 'documentors' - (if not all) are programmers and used to use
CVS and other versioning system. But this takes some extra time that IMHO it
shouldn't. If you want to spread the word and get lots of people to help
in docs, I believe this kind of thing that Launchpad uses is
Hannes,
I think both Thiago and Elizabeth are correct. Call me old-hat: I
prefer CVS but I'm well aware that it's a daunting task to learn
that new technology for people who would otherwise not use it. In
fact, most projects - including PHP - are moving away from CVS, in
favor of
Hi!
tools). Writing in XML is not a natural thing. An online interface
where people can edit docs would seriously boost people helping out.
Why do you think there are so many user notes in the PHP manual ;)
I think a web-based tool that would allow to generate standard docbook
pages (at
Elizabeth M Smith wrote:
[snip]
Many of us - 'documentors' - (if not all) are programmers and used to use
CVS and other versioning system. But this takes some extra time that IMHO it
shouldn't. If you want to spread the word and get lots of people to help
in docs, I believe this kind of
On Wed, Oct 1, 2008 at 20:03, Stanislav Malyshev [EMAIL PROTECTED] wrote:
On Wed, Oct 1, 2008 at 19:17, Elizabeth M Smith [EMAIL PROTECTED] wrote:
tools). Writing in XML is not a natural thing. An online interface
where people can edit docs would seriously boost people helping out.
Why do
All,
I am what I guess you'd call a newbie - Elizabeth got me on this list
during ZendCon and though I've been following it I still have no idea how
the doc editing process works. I'm exactly who you want this kind of tool
for - a new contributor who is eager to contribute but unsure about how to
On Wed, Oct 1, 2008 at 21:27, Brandon Savage [EMAIL PROTECTED] wrote:
All,
I am what I guess you'd call a newbie - Elizabeth got me on this list
during ZendCon and though I've been following it I still have no idea how
the doc editing process works. I'm exactly who you want this kind of tool
I'd be happy to serve as your test subject. I'll post back here when I've
done it (sometime this evening once I'm home from the office).
Brandon
On Wed, Oct 1, 2008 at 4:01 PM, Hannes Magnusson [EMAIL PROTECTED]
wrote:
On Wed, Oct 1, 2008 at 21:27, Brandon Savage [EMAIL PROTECTED]
wrote:
On Wed, Oct 1, 2008 at 22:30, Ilia Alshanetsky [EMAIL PROTECTED] wrote:
iliaa Wed Oct 1 20:30:24 2008 UTC
Modified files: (Branch: PHP_5_3)
/php-src/ext/pgsql pgsql.c
/php-srcNEWS
Log:
Fixed bug #46206 (pg_query_params/pg_execute convert passed values
Hi Hannes
2008/10/1 Hannes Magnusson [EMAIL PROTECTED]:
On Wed, Oct 1, 2008 at 20:03, Stanislav Malyshev [EMAIL PROTECTED] wrote:
On Wed, Oct 1, 2008 at 19:17, Elizabeth M Smith [EMAIL PROTECTED] wrote:
tools). Writing in XML is not a natural thing. An online interface
where people can
Stanislav Malyshev wrote:
Hi!
On the ZendCon, we (Marcus, Elizabeth, Andi and myself) had a talk about
what we'd like to do with namespaces, and we arrived at the following
conclusions, which we propose to implement in 5.3:
1. Allow braces for namespaces. So, the syntax for namespaces will
3. Functions will not be allowed inside namespaces. We arrived to
conclusion that they are much more trouble than they're worth, and
summarily we would be better off without them. Most of the
functionality could be easily achieved using static class methods, and
the rest may be emulated with
Brian Moon wrote:
3. Functions will not be allowed inside namespaces. We arrived to
conclusion that they are much more trouble than they're worth, and
summarily we would be better off without them. Most of the
functionality could be easily achieved using static class methods, and
the rest may be
20 matches
Mail list logo
