thanks for the explanation Sara, :-), as always your manner and ideas
are an example to the 'php core', 'we' (they) are lucky to have you :-)
Sara Golemon wrote:
what happens when I want to place a 'goto' label just before a while
or foreach
loop (upon which I haven't put a label)? I ask because
On Wed, 30 Nov 2005, Andi Gutmans wrote:
Is our confidence level on xmlwriter high? Just asking as I'm not sure how
It's very high. I need it too. :)
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, 30 Nov 2005, Ilia Alshanetsky wrote:
* Enable xmlreader extension by default, as we do for all XML
extensions.
Done. Also made it use the right configure option.
* Introduce xmlwriter extension via a symlink from pecl into core and as
other XML extension enable it by default.
Jani Taskinen wrote:
On Wed, 30 Nov 2005, Ilia Alshanetsky wrote:
* Enable xmlreader extension by default, as we do for all XML
extensions.
Done. Also made it use the right configure option.
* Introduce xmlwriter extension via a symlink from pecl into core and as
other XML extension e
You forgot one thing: pecl/filter !
It definately should be included, with the EXPERIMENTAL flag of course.
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, 1 Dec 2005, Rasmus Lerdorf wrote:
Jani Taskinen wrote:
On Wed, 30 Nov 2005, Ilia Alshanetsky wrote:
* Enable xmlreader extension by default, as we do for all XML
extensions.
Done. Also made it use the right configure option.
* Introduce xmlwriter extension via a symlink from
Jani Taskinen wrote:
Isn't that solved by just simply changing the license by the author?
Sure, but until that happens I don't think it should be included.
-Rasmus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello Rasmus,
Thursday, December 1, 2005, 10:08:41 AM, you wrote:
> Jani Taskinen wrote:
>> Isn't that solved by just simply changing the license by the author?
> Sure, but until that happens I don't think it should be included.
Same here. The discussion was on IRC and between Rob & Pierre
Hi Sara,
I made another patch that is based on your ideas.
1) It uses "right" syntax:
LABEL: while(1) {
break LABEL;
}
2) It doesn't allow usage of same label for different loops
L1: while(1) {...}
L1: while(1) {...}
3) It doesn't use executor data structures
4) It allows reuse of sa
Marcus Boerger wrote:
Sure, but until that happens I don't think it should be included.
Same here. The discussion was on IRC and between Rob & Pierre and i thought
they changed back but didn't do so yet.
The license is changing. It was actually supposed to have changed
yesterday. Pierre
On Thu, 01 Dec 2005 14:30:07 +0530
[EMAIL PROTECTED] (Rasmus Lerdorf) wrote:
> Jani Taskinen wrote:
> > On Wed, 30 Nov 2005, Ilia Alshanetsky wrote:
> >
> >> * Enable xmlreader extension by default, as we do for all XML
> >> extensions.
> >
> > Done. Also made it use the right configure opt
Of course it is meaningful for PHP as well.
On 12/1/05, Bart de Boer <[EMAIL PROTECTED]> wrote:
> But that whitespace is meaningfull at XML level and not at PHP level.
>
> Processing Instruction: phpecho
>
>
> Sean Coates wrote:
> > Sara Golemon wrote:
> >
> >>> oh, that's easy to solve ' >>>
> >>
I will help on Validate_ptBR.
I am in contact with Silvano.
His CVS id is: silvano
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, 1 Dec 2005 05:05:40 -0800
[EMAIL PROTECTED] ("Marcelo Santos Araujo") wrote:
> I will help on Validate_ptBR.
> I am in contact with Silvano.
> His CVS id is: silvano
Confirmed, pear account. I will set his karma once the account is
opened.
--Pierre
--
PHP Internals - PHP Runtime Develo
> Of course it is meaningful for PHP as well.
>
We're talking about the PHP language. Not the PHP engine. You're right that
the PHP engine needs to be capable of finding its processing instructions.
So it's capable of doing a little XML. Thus it needs to understand the
meaning of whitespace in XM
Ron Korving wrote:
Named parameter example:
Your example misses the main advantage of named parameters IMHO: Sets of
parameters you don't want to or can't explicitely list because they are
not know yet.
function adduser($params)
{
if (!is_array($params)) throw new Exception('No nam
>> I already brought this up once: How difficult is it to introduce an
>> option to php.ini which has its standard setting in such a way that
>> every encountered namespace is automagically translated into "classic
>> prefixing" style?
Language behaviour should absolutely NOT depend on an .ini se
On 11/30/05 3:38 AM, Jani Taskinen wrote:
On Wed, 30 Nov 2005, Lukas Smith wrote:
In what form would it be added to core? I presume it would be marked as
As what it is in pecl/filter right now..or what did you mean?
experimental? Has the doc team jumped on it yet?
Definately exper
Ben Ramsey wrote:
> Are there any other known issues besides this one that continue to
> render this extension as experimental?
It is new and therefor experimental, the experimental flag usually
sticks around for about a year since the release. At which point the
state of the extension is reconsid
If Mike doesn't want to use namespaces, then Mike shouldn't use Jessies
package.
Bob
> -Original Message-
> From: Bart de Boer [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 30, 2005 11:45 PM
> To: internals@lists.php.net
> Subject: [PHP-DEV] Re: Desired namespace behavoir
>
> >>
We're definately on the same page as far as implementation goals, but I
can't help but notice one problem:
* labels aren't scoped to functions. The break container checks prevent
casual jumping, but:
FOO: do { } while (0);
function bar() {
do { break FOO; } while (0);
}
Actually compiles l
Rasmus Lerdorf wrote:
> One of the reasons is that this would be the first extension we bundle
> which isn't under the PHP license.
Not a question about xmlwriter specifically, but licensing policy in
general. Does your comment imply that only and only extension released
under the PHP license are
Bart de Boer schrieb:
> So, if namespace JessieStuff contains multiple classes. They would all
> become JessieStuff_ClassName.
>
> Assuming the package relies on its own classes, it wouldn't be able to
> call them anymore because all their names have changed.
First of all, everything INSIDE a n
l0t3k schrieb:
> Language behaviour should absolutely NOT depend on an .ini setting.
Using an .ini setting was just an idea so there would be a possibility
to have namespaces totally "hidden" from the beginning programmer. This
honors the KISS priciple: You require() some package and don't even n
Thanks to several people, the phpnamespaces.org site is up and contains the
latest namespace patch, pre-patched tarballs and Win32 zip, example scripts,
and links to namespace-related news! If you are interested in seeing
namespaces in PHP, or are curious to see the progress of this development,
th
> /*
> * this encounters a namespace. The auto-prefix-import option
> * is active so EVERYTHING is inside the namespace is imported
> * with a prefix of "JessieStuff_".
> */
> require 'JessiePackage.php';
> $x=new JessieStuff_SimpleClass();
So let's say we've got a package like this:
namesp
SG>>* labels aren't scoped to functions. The break container checks prevent
SG>>casual jumping, but:
SG>>
SG>>FOO: do { } while (0);
SG>>function bar() {
SG>> do { break FOO; } while (0);
SG>>}
This shouldn't work, of course.
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http
Good catch. Thanks. I'll fix this and send a new patch.
Dmitry.
> -Original Message-
> From: Sara Golemon [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 01, 2005 7:03 PM
> To: Dmitry Stogov; internals@lists.php.net
> Cc: Zeev Suraski; Stanislav Malyshev
> Subject: Re: [PHP-DEV] Lab
Development of the new pear-module text_wiki_mediawiki (mediawiki-parser for
text_wiki). Pierre agreed on requesting the account.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
""Jessie Hernandez"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> 2) How will symbols be resolved inside namespaces? If a class "A" exists
> in
> namespace "N", and a global class "A" also exists, then by referencing
> "A",
> what should happen? Should the namespaced "A" be u
Hi l0t3k,
Yes, this is how it's done in C++, but do we want to allow this syntax for
PHP? If so,
it'll either be :::A, ::A (can be used, but might be inconsistent as ":::"
is used everywhere else), or \A, depending on the final separator...
Regards,
Jessie
""l0t3k"" <[EMAIL PROTECTED]> wrote
Hi Anthony:
On Thu, Dec 01, 2005 at 02:45:28AM +0300, Antony Dovgal wrote:
> Remove ext/pcre/config.m4 and run ./cvsclean && ./buildconf
Thanks. Did the trick.
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
Bart de Boer schrieb:
> namespace JessieStuff {
> class FirstClass { ... }
> class SecondClass {
> public $obj;
> function __construct() {
> $this->obj = new FirstClass();
> }
> }
> }
>
> Now we'd import this with prefixing everything and the
> result would be something tha
On Thu, 1 Dec 2005, Ben Ramsey wrote:
Definately experimental. It still crashes for me when
I pass something like ?foo= in either POST or GET. :)
I've submitted a patch for this problem here:
http://pecl.php.net/bugs/bug.php?id=6124
And patch applied, thanks.
Are there any other
I hope now I didn't making idiot's mistake.
Dmitry.
> -Original Message-
> From: Sara Golemon [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 01, 2005 7:03 PM
> To: Dmitry Stogov; internals@lists.php.net
> Cc: Zeev Suraski; Stanislav Malyshev
> Subject: Re: [PHP-DEV] Labeled Break (
> I made another patch that is based on your ideas.
>
> 1) It uses "right" syntax:
>
> LABEL: while(1) {
> break LABEL;
> }
>
> 2) It doesn't allow usage of same label for different loops
>
> L1: while(1) {...}
> L1: while(1) {...}
>
> 3) It doesn't use executor data structures
>
> 4) It allows reu
On Dec 1, 2005, at 6:59 AM, Christian Schneider wrote:
Ron Korving wrote:
Named parameter example:
Your example misses the main advantage of named parameters IMHO:
Sets of parameters you don't want to or can't explicitely list
because they are not know yet.
function adduser($params)
Surely it ought to care iff trying to look like a processing
instruction. But we digress...
On 12/1/05, Bart de Boer <[EMAIL PROTECTED]> wrote:
> So, that whitespace is meaningfull for XML. Not for PHP. PHP couldn't care
> less how processing instructions are defined in XML.
>
--
PHP Internals -
Ilia Alshanetsky wrote:
First the release plan, my idea is to allow minor features with
accompanying tests that do not introduce any BC issues or functionality
regressions till the 10th of December.
Bug #35510
add gmp_nextprime function to ext/gmp
http://bugs.php.net/bug.php?id=35510
Pretty pl
On Dec 1, 2005, at 11:16 AM, Sebastian Kugler wrote:
On 12/1/05, Jared White <[EMAIL PROTECTED]> wrote:
I still say its main selling point is
that the calling code is its own API documentation.
why don't you just write something like
cycle(/* name: */ "myCycle", /* values: */ "#ee;#d0d0d
Hello Ilia,
i prefer only allowing PHP License in 'stock PHP'.
marcus
Thursday, December 1, 2005, 5:01:07 PM, you wrote:
> Rasmus Lerdorf wrote:
>> One of the reasons is that this would be the first extension we bundle
>> which isn't under the PHP license.
> Not a question about xmlwriter sp
On Thu, 1 Dec 2005 20:52:32 +0100
[EMAIL PROTECTED] (Marcus Boerger) wrote:
> Hello Ilia,
>
> i prefer only allowing PHP License in 'stock PHP'.
The question was not what "we" prefer but what is allowed or not, and
why.
To be a little more precised, I see no reason to not allow BSD-like or
ot
On 12/1/05, Jared White <[EMAIL PROTECTED]> wrote:
> I still say its main selling point is
> that the calling code is its own API documentation.
why don't you just write something like
cycle(/* name: */ "myCycle", /* values: */ "#ee;#d0d0d0", /*
print: */ false,
/* reset: */ true, /* delimite
As per the notes at http://www.php.net/~derick/meeting-notes.html,
section 2.4.2: 'We make "var" an alias for "public" and remove the
warning for it.'
Could something like the attached patch be included as part of 5.1.2?
Michel Sisolak
[EMAIL PROTECTED]
___
This is part of the definition of namespaces.
And yes, I want the INI option to just provide aliases.
If these are implemented by injecting
class a_A2 extends a::A2 {}
as interface classes or by internally providing a hash table alias is
only different from a technical point of view. The resul
hi,
personally, I find :::A, ::A and such constructs *extremely* ugly. Might
I suggest using a special keyword to denote global scoped classes?
eg:
global:::A and such. global already is a keyword, but I'm pretty sure it
could be reused in this context. Plus, it clearly shows where you're
get
Here's a patch for bug #35512. I'm hoping that this can be included
in PHP 5.1.2
Thanks,
Ryan Dingman
[EMAIL PROTECTED]
Next Online Mortgage Technologies, Inc.
Index: ZendEngine2/zend.c
===
RCS file: /repository/ZendEngine2/z
I hate the idea of voting for features, but since it might have some
affect on the language, I will add my opinion to the heap.
::: - Bad, because it's three characters.
: - Good, because it's one character, and it does not look like
something else.
\ - It's one character, but it looks like div
Roman Ivanov schrieb:
> Radical idea:
> 1) Use :.
> 2) Make : to work like ::.
> 3) Make : to work like ->.
> 4) But no one will agree to it anyway, so I stop here.
Nope. I agree ;-)
But that train has already left.
(although I still think : could be made to work for the namespaces)
OLLi
--
PHP
Oliver,
Like I mentioned in another thread, ":" cannot be used, even if only
classes are allowed in namespaces. Look at this example:
$x = $y?a:b::c();
The above can be parsed either as the first argument being "the result
of method c of class b in namespace a" or the first argument being "t
PHP6 is about to make OPCode caching mechanism build into Zend
Engine,without question this will improve PHP dramatically.But I have a
radical thought: why not to directly run ZIC(Zend Intermediate Code) files
that have been compiled instead of handling PHP source scripts. Just like a
execrutab
On 01/12/05, Michael Walter <[EMAIL PROTECTED]> wrote:
> Surely it ought to care iff trying to look like a processing
> instruction. But we digress...
>
> On 12/1/05, Bart de Boer <[EMAIL PROTECTED]> wrote:
> > So, that whitespace is meaningfull for XML. Not for PHP. PHP couldn't care
> > less how
First I must say - a nice job:)
The namespaced version works fine.
I found just 3 problems (things I don't like):
1.Import statements are allowed only in the beginning of the script.
2.Global function calls are not allowed in a namespace.
3.The example below does not work.
Anyway, the patch see
I assume ::: is being used because it simply works and the discussion on
which seperator to use might still go on for some time ;). You have a point
about import statements being allowed only in the beginning. This would be
nice:
class X
{
public function foo()
{
import class bar:::MyCl
What was the argument against '::' again?
Jessie Hernandez wrote:
Oliver,
Like I mentioned in another thread, ":" cannot be used, even if only
classes are allowed in namespaces. Look at this example:
$x = $y?a:b::c();
The above can be parsed either as the first argument being "the result
55 matches
Mail list logo
