Hello everybody,
Am Dienstag, den 12.08.2008, 03:04 +0200 schrieb Etienne Kneuss:
[...]
> To me
>
> namespace A {
>code
> }
>
> namespace B {
>code
> }
>
> code
>
> seems equivalent to
>
> namespace A;
> code
> namespace B;
> code
> namespace ;
> code
>
> Only nicer. And I can hardly
Hello,
On Tue, Aug 12, 2008 at 2:39 AM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Hi!
>
>> but if the {} syntax is introduced, it will be made to affect only the
>> code inside it, right? If so, I fail to see your point, since the new
>> syntax will solve that problem.
>
> While introducing
Hi!
3. You want another namespace, just write namespace again.
No, that's not for kids to play with. That's grown-up stuff. Rated X.
4. You got lost after the 10th namespace? Welcome to if-else nesting
Get your hands away from the keyboard and re-read the part about "not
using multiple na
Hi!
"triskaidekaphobia" - oh and there was that very polemic pythin argument.
Dude I am sorry but ther is no argument at all. Unless your long mail is
Please ask you sysadmin to fix your mail system, you seem to be losing
emails. The email I was referring to please read here:
http://news.php
Hi!
but if the {} syntax is introduced, it will be made to affect only the
code inside it, right? If so, I fail to see your point, since the new
syntax will solve that problem.
While introducing a whole collection of new problems - such as that we
will have now split scope, that you can get i
Hello Stanislav,
Tuesday, August 12, 2008, 1:34:49 AM, you wrote:
> Hi!
>> "I don't want braces because people would think it acts like C++" is as
>> silly as saying "I don't want the current namespace Foo; syntax because
>> people will think it acts like python"
> Errr... as far as I know Pyth
Hello Stanislav,
Tuesday, August 12, 2008, 1:41:08 AM, you wrote:
> Hi!
>> Sorry but you never ever provided any logical reasoning for the current
>> way. The reasons that were brought up were:
> It would help the discussion a lot if you actually read my emails.
> Unfortunately, by now it's cl
Hello,
On Tue, Aug 12, 2008 at 2:12 AM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Hi!
>
>> I fail to see why { } meaning a different level of hierarchy is a
>> problem here, that's exactly what it's supposed to mean: "code in that
>> block is affected by that namespace."
>
> Exactly. The thi
Hi!
I fail to see why { } meaning a different level of hierarchy is a
problem here, that's exactly what it's supposed to mean: "code in that
block is affected by that namespace."
Exactly. The thing is that there can be no code that is not affected (at
least not in this file) for namespaces -
Hello,
On Tue, Aug 12, 2008 at 12:58 AM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Hi!
>
>> So why the $%#$%& can't we use "package" if the implementation has
>> nothing incommon with namespaces in c++ (your example, not mine)?
>
> We could use "package" or we could use "hexaflexagon" or we
Hi!
Sorry but you never ever provided any logical reasoning for the current
way. The reasons that were brought up were:
It would help the discussion a lot if you actually read my emails.
Unfortunately, by now it's clear that you do not. I just wrote a long
email outlining the reasons, but I
Hi!
"I don't want braces because people would think it acts like C++" is as
silly as saying "I don't want the current namespace Foo; syntax because
people will think it acts like python"
Errr... as far as I know Python has no "namespace Foo;" syntax. And as I
repeated numerous times, the synt
Hello Stanislav,
Tuesday, August 12, 2008, 12:58:29 AM, you wrote:
> Hi!
>> So why the $%#$%& can't we use "package" if the implementation has
>> nothing incommon with namespaces in c++ (your example, not mine)?
> We could use "package" or we could use "hexaflexagon" or we could use
> "triskai
Hello Christian,
Tuesday, August 12, 2008, 12:34:41 AM, you wrote:
> Hi Marcus,
>> Account approved and access granted.
> Thanks!
>> Please provide the function copying in a function next to _free_function()
> I just committed that (and included some tests). I hope I didn't do
> anything wron
Hi!
So why the $%#$%& can't we use "package" if the implementation has
nothing incommon with namespaces in c++ (your example, not mine)?
We could use "package" or we could use "hexaflexagon" or we could use
"triskaidekaphobia" or any other word. But if we have namespace
implementation in PHP
Hi Marcus,
Account approved and access granted.
Thanks!
Please provide the function copying in a function next to _free_function()
I just committed that (and included some tests). I hope I didn't do
anything wrong in the process, if so, feel free to do so.
and care for parameter info as
Welcome aboard (soon), and congrats for your patchs.
--
Cordialement.
--
Nicolas Chaillan | GROUPAKT.fr | UIN : 16549830
[EMAIL PROTECTED] | [EMAIL PROTECTED] | http://www.groupakt.fr
http://www.fmsakt.fr | http://www.prospecttel.com
Directeur général.
""Christian Seiler"" <[EMAIL PROTECTED]>
Dmitry Stogov wrote:
This behavior is already implemented in "improved" patch that I sent on
Saturday.
Thanks. Dmitry.
[snip]
What I mean is:
fopen("this_is_not_a_dir_but_a_file/../../../../../../../../etc/passwd",
"r");
works because of realpath() and PHP's wrapper.
[snip]
Does this c
[EMAIL PROTECTED] escreveu:
On 11/08/2008, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
Hi!
Ideally someone would summarize the discussion (or maybe two people, one
from each "camp") and then we can have a vote. Make it an RFC or
OK, here it goes again:
When we adopt some syntax, especially
Stanislav Malyshev wrote:
> When we adopt some syntax, especially syntax matching some other
> language, we do not just introduce an otherwise meaningless sequence of
> symbols to be learned by users. We introduce concepts, and we create
> associative links with other languages. So, if we introduce
On 11/08/2008, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Hi!
>
>> Ideally someone would summarize the discussion (or maybe two people, one
>> from each "camp") and then we can have a vote. Make it an RFC or
>
> OK, here it goes again:
>
> When we adopt some syntax, especially syntax matching
Hi!
Ideally someone would summarize the discussion (or maybe two people, one
from each "camp") and then we can have a vote. Make it an RFC or
OK, here it goes again:
When we adopt some syntax, especially syntax matching some other
language, we do not just introduce an otherwise meaningless
Hello Christian,
Monday, August 11, 2008, 8:43:31 PM, you wrote:
> Hi,
>> all submitted now. Thanks everyone for their help and especially
>> Christian for getting this started.
> Thanks for making my patch work after the modifications in
> zend_closures.c. I'm sorry I couldn't do it myself
Maintaining closures, see http://news.php.net/php.internals/39835
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello Christian,
Monday, August 11, 2008, 8:43:31 PM, you wrote:
> Hi,
>> all submitted now. Thanks everyone for their help and especially
>> Christian for getting this started.
> Thanks for making my patch work after the modifications in
> zend_closures.c. I'm sorry I couldn't do it myself
Hi,
all submitted now. Thanks everyone for their help and especially
Christian for getting this started.
Thanks for making my patch work after the modifications in
zend_closures.c. I'm sorry I couldn't do it myself but I was kind of
busy the last few days and the "simple fix" created memor
Was running pspell through g++ and found that a couple of error conditions
segments in pspell.c
are using the wrong cleanup methods. delete_pspell_manager() should be
delete_pspell_can_have_error()
-Phil.
--- pspell.c16 Jul 2008 18:35:41 - 1.61
+++ pspell.c11 Aug 20
I'll try to review it on Tuesday/Wednesday.
Thanks. Dmitry.
Lukas Kahwe Smith wrote:
On 09.08.2008, at 17:42, Arnaud Le Blanc wrote:
Hi,
As Lucas said the patch seems ready now, could someone please review
the patch
for inclusion ?
http://wiki.php.net/rfc/zendsignals
Changes that have b
On 09.08.2008, at 17:42, Arnaud Le Blanc wrote:
Hi,
As Lucas said the patch seems ready now, could someone please review
the patch
for inclusion ?
http://wiki.php.net/rfc/zendsignals
Changes that have been made:
- The patch has been ported to HEAD
- The patch now supports multithreaded e
Hello guys,
all submitted now. Thanks everyone for their help and especially
Christian for getting this started.
marcus
Monday, August 11, 2008, 12:23:57 PM, you wrote:
> Hello Dmitry,
> Monday, August 11, 2008, 10:51:44 AM, you wrote:
>> Hi Marcus,
>> I committed the ZE part of your pat
On 03.08.2008, at 14:26, Marcus Boerger wrote:
1) new keyword 'use'. Semantically it is the same as 'static' or
'global'
so it should be used in the same location.
2) namespaces, either use 'package' and only one per file, or use
'namespace' with curly braces. Read this as be consistent with
Hello Dmitry,
Monday, August 11, 2008, 10:51:44 AM, you wrote:
> Hi Marcus,
> I committed the ZE part of your patch with exception for
> zend_error(E_ERROR, "Cannot destroy active lambda function");
> Catching this error may cause memory corruption and crash.
Alright, didn't see that immediat
hi,
On Mon, Aug 11, 2008 at 11:11 AM, Richard Quadling
<[EMAIL PROTECTED]> wrote:
> Hi.
>
> Whilst you can download the most recent file from snaps.php.net, the
> latest file has always been named as php5.3-win32-latest.zip. Which
> means you don't need to know when the latest build was. Recently
hi,
On Mon, Aug 11, 2008 at 10:59 AM, Richard Quadling
<[EMAIL PROTECTED]> wrote:
> Hi.
>
> It may be known or not, but the Win32 PECL snapshots was last
> successfully built on (as at 2008/08/11 10:00 AM GMT)
>
> pecl5.3-win32-latest.zip07-Aug-2008 08:45 4.1M
> pecl5.3-win
PHP 6 Bug Database summary - http://bugs.php.net/
Num Status Summary (67 total -- which includes 26 feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
===
Hi.
Whilst you can download the most recent file from snaps.php.net, the
latest file has always been named as php5.3-win32-latest.zip. Which
means you don't need to know when the latest build was. Recently the
latest file is missing. The filename appears in the list at
http://snaps.php.net/win32,
Hi
PHP 5.2 DEV Win - 06-Aug-2008 04:20 UTC
best regards
holo
""Richard Quadling"" <[EMAIL PROTECTED]> escreveu na mensagem
news:[EMAIL PROTECTED]
> Hi.
>
> It may be known or not, but the Win32 PECL snapshots was last
> successfully built on (as at 2008/08/11 10:00 AM GMT)
>
> pecl5.3-win32-la
Hi.
It may be known or not, but the Win32 PECL snapshots was last
successfully built on (as at 2008/08/11 10:00 AM GMT)
pecl5.3-win32-latest.zip07-Aug-2008 08:45 4.1M
pecl5.3-win32-200808070430.zip 07-Aug-2008 08:45 4.1M
Regards,
Richard.
--
-
Richard
Hi Marcus,
I committed the ZE part of your patch with exception for
zend_error(E_ERROR, "Cannot destroy active lambda function");
Catching this error may cause memory corruption and crash.
Thanks. Dmitry.
Marcus Boerger wrote:
Hello Johannes, Christian, Felipe,
and here 5.3 and 6.0 versio
On 11.08.2008, at 09:31, Dmitry Stogov wrote:
The failure of realpath_basic-win32.phpt is expected, as behavior of
realpath() became the same as on Linux (slashes after regular file
name are not allowed).
Lets make extra sure that when you commit these kinds of platform
unifications, th
Hi Pierre,
Thank you for feedback.
You are definitely right about FindClose().
The failure of realpath_basic-win32.phpt is expected, as behavior of
realpath() became the same as on Linux (slashes after regular file name
are not allowed).
I wasn't able to reproduce realpath_basic2.phpt failure (
41 matches
Mail list logo
