Peer pressure? :)
Steph doesn't want to be left out :) Just kidding...
Andi
> -Original Message-
> From: Steph Fox [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 19, 2006 1:26 PM
> To: Marcus Boerger; Edin Kadribasic
> Cc: Ilia Alshanetsky; PHP Internals
> Subject: Re: [PHP-DEV] Date
We were considering supporting a __getRef() method. You could implement
either or both of them and then the right thing would happen.
Dmitry, Marcus - Besides having to come to a decision about this, is there
any situation you guys discussed for which this would not work?
Thx.
Andi
> -Origi
Jason Sweat wrote:
On 7/19/06, Alan Knowles <[EMAIL PROTECTED]> wrote:
+1 for adding the namespace patch in :) - oh well I can always dream...
Regards
Alan
+1 dreamer ( and +1 annoying de-lurker voting because he thinks it is
american idol ;)
Regards,
Jason
Why ?
I got schoked when I saw
Pierre wrote:
> Please note that it intoduces a new class called Zip, but I never saw a
> php zip implementation named Zip.
Uh, well this already was on thedailywtf...
See here, http://thedailywtf.com/forums/thread/80949.aspx
Rainer
--
PHP Internals - PHP Runtime Development Mailing List
To uns
I was having some problems testing in native mode when my ini file had
unicode enabled.
It appears that it must be explicitly disabled in the script with the
passing -N flag (make ntest). Otherwise it is picking up the ini setting
and running the tests in unicode mode. Patch is attached just in
On 7/19/06, Alan Knowles <[EMAIL PROTECTED]> wrote:
+1 for adding the namespace patch in :) - oh well I can always dream...
Regards
Alan
+1 dreamer ( and +1 annoying de-lurker voting because he thinks it is
american idol ;)
Regards,
Jason
http://blog.casey-sweat.us/
--
PHP Internals - PHP Ru
+1 for adding the namespace patch in :) - oh well I can always dream...
Regards
Alan
Ilia Alshanetsky wrote:
Now that everyone had their say (I hope) I've made a quick tally of
the votes so far:
Rename date & timezone classes to DateTime and DateTimeZone respectively
Tony
Derick
Mi
Pierre wrote:
> Hello,
>
>
> Many people (incl. php devs) asked me if I can include zip in 5.2.0.
> Ilia thought it was too late in the game and planed to do it in 5.2.1.
>
> I like to have it in, as experimental.
>
> Please note that it intoduces a new class called Zip, but I never saw a
> php
Jani Taskinen wrote:
> On Wed, 19 Jul 2006, Pierre wrote:
>
>> Please note that it intoduces a new class called Zip, but I never saw a
>> php zip implementation named Zip.
>>
>> +1/-1/0?
>
>
> -1 in core, PECL is the place for this.
> -100 for class called Zip for the same reasons why we
On 7/20/06, Jani Taskinen <[EMAIL PROTECTED]> wrote:
On Wed, 19 Jul 2006, Pierre wrote:
> Please note that it intoduces a new class called Zip, but I never saw a
> php zip implementation named Zip.
>
> +1/-1/0?
-1 in core, PECL is the place for this.
-100 for class called Zip for the
Sean Coates wrote:
From my experiences the problem with this is many shared hosts wont install
non core modules, so the more modules moved from core to pecl the less
flexible php will be and the less use it will be.
I understand the need to keep the core code maintained and as clean and
lean
as
On Wed, 19 Jul 2006, Pierre wrote:
Please note that it intoduces a new class called Zip, but I never saw a
php zip implementation named Zip.
+1/-1/0?
-1 in core, PECL is the place for this.
-100 for class called Zip for the same reasons why we can not have
Date and TimeZone classe
Ilia Alshanetsky wrote:
Now that everyone had their say (I hope) I've made a quick tally of
the votes so far:
Rename date & timezone classes to DateTime and DateTimeZone respectively
Tony
Derick
Mike
Rasmus
Andi
Ilia
Don't do anything and wait till 5.3/6.0 etc..
Pier
Hello Edin,
Wednesday, July 19, 2006, 5:23:00 PM, you wrote:
> I'm OK with DateTime and DateTimeZone too.
> Edin
> Ilia Alshanetsky wrote:
>> Now that everyone had their say (I hope) I've made a quick tally of
>> the votes so far:
>>
>> Rename date & timezone classes to DateTime and DateTimeZon
Hello Greg,
this whole thread unfortunatley shows that nobody is reading our
provided documentation, see excerpt from CODING_STANDARDS:
[7] Classes should be given descriptive names. Avoid using abbreviations where
possible. Each word in the class name should start with a capital letter,
Hello Pierre,
Wednesday, July 19, 2006, 3:56:15 PM, you wrote:
> On Wed, 19 Jul 2006 15:32:42 +0200
> [EMAIL PROTECTED] (Christian Stocker) wrote:
>>
>>
>> On 19.7.2006 15:24 Uhr, Richard Quadling wrote:
>> > For PHP 5.2.0-dev (cli) (built: Jul 12 2006 12:20:25), I get ...
>> >
>> > Fatal err
Steph Fox wrote:
>> Please, just make a clear decision, stick to it, and tell us what it is,
>> we will adapt our coding standards to whatever is decided.
>
>
>> Either:
>>
>> 1) internals declares all top-level classes, use an unprefixed name (no
>> _) at your own risk
>> 2) internals grabs PHP
Hello Pierre,
Wednesday, July 19, 2006, 9:42:54 PM, you wrote:
> On 7/19/06, Marcus Boerger <[EMAIL PROTECTED]> wrote:
>> Hello Pierre,
>>
>> Wednesday, July 19, 2006, 3:56:15 PM, you wrote:
>>
>> > On Wed, 19 Jul 2006 15:32:42 +0200
>> > [EMAIL PROTECTED] (Christian Stocker) wrote:
>>
>> >>
>> >
On Wed, 19 Jul 2006 14:02:56 -0400
[EMAIL PROTECTED] (John Coggeshall) wrote:
On Wed, 2006-07-19 at 09:40 +0200, Marcus Boerger wrote:
> A single alpha released pecl extension has a problem, well that imo
> is not that bad conflict and can be solved before it is being
> released.
I wonder if Th
On 7/19/06, Marcus Boerger <[EMAIL PROTECTED]> wrote:
Hello Pierre,
Wednesday, July 19, 2006, 3:56:15 PM, you wrote:
> On Wed, 19 Jul 2006 15:32:42 +0200
> [EMAIL PROTECTED] (Christian Stocker) wrote:
>>
>>
>> On 19.7.2006 15:24 Uhr, Richard Quadling wrote:
>> > For PHP 5.2.0-dev (cli) (built:
Now that everyone had their say (I hope) I've made a quick tally of
the votes so far:
My $0.02USD;
Most Ideal: Grant the 'Date' namespace to Internals (Not going to happen for
the volume of reasons already discussed.) DO NOT REPLY WITH ALL THE REASONS
I AM WRONG FOR HAVING THIS OPINION. I A
Hello Andrei,
the problem is not the 'as' part, the problem is accessing the array and
that currently must be a write context. Maybe we can work around tha at some
point i dunno.
best regards
marcus
Wednesday, July 19, 2006, 6:24:02 PM, you wrote:
> But how is foreach() a write context? Unles
On Wed, 19 Jul 2006 14:02:56 -0400
[EMAIL PROTECTED] (John Coggeshall) wrote:
> On Wed, 2006-07-19 at 09:40 +0200, Marcus Boerger wrote:
> > A single alpha released pecl extension has a problem, well that imo
> > is not that bad conflict and can be solved before it is being
> > released.
>
> I wo
Andrei Zmievski wrote:
Rob,
I have not tested the patch, but it looks good to me on cursory
overview. I assume it passes your tests?
The only comment I have is regarding the usage of 't' and 'T'
specifiers. Since you always have to pass binary UTF-8 strings to
libxml, we should always use 's'
On Wed, 19 Jul 2006, Lukas Smith wrote:
> Ilia Alshanetsky wrote:
> > Class names are not case sensitive, so it does not matter if it is FooBar or
> > fooBar or even FoObAR.
>
> Ilia, since PHP5 we are case preserving. So it does matter, though only
> stylistically, not technically.
DateTimeZone
On Wed, 2006-07-19 at 09:40 +0200, Marcus Boerger wrote:
> A single alpha released pecl extension has a problem, well that imo is
> not that bad conflict and can be solved before it is being released.
I wonder if The Perl guys check every single CPAN extension before
introducing a new keyword or i
On Wed, 2006-07-19 at 17:34 +0200, Pierre wrote:
> +1/-1/0?
+1 from me, I still to this day get people pestering me about my article
on creating .zip files from pure PHP -- a real extension is clearly
useful.
John
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: ht
On Wed, 2006-07-19 at 16:23 +0100, Edin Kadribasic wrote:
> > Rename date & timezone classes to DateTime and DateTimeZone respectively
> > Tony
> > Derick
> > Mike
> > Rasmus
> > Andi
> > Ilia
> >
+ > > John
+1
John
--
PHP Internals - PHP Runtime Development Mailin
On Wed, 2006-07-19 at 10:49 +0200, Lukas Smith wrote:
> > +1 for DateTime and DateTimezone; the flame was funny, but let's move
> > on, please.
+1 from me.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, 2006-07-19 at 10:35 +0200, Marcus Boerger wrote:
> where is the problem in having it as 'DateTime' or 'Date' in namespace
> 'PHP' and as 'PHPDateTime' or 'PHPDate' in the global namespace? We do
> not have namespaces now but there is no technical reason to prevent that
> from the beginnin
+1
I wish to see Zip in PHP, it's a popular archive and plus used in .jar
implementation and .jar in its turn is used in other file formats, for
example OpenDocument one..
On 7/19/06, Pierre <[EMAIL PROTECTED]> wrote:
Hello,
Many people (incl. php devs) asked me if I can include zip in 5.2.0.
Shared hosts are used to deploying PHP Proper and ignoring PECL, because
in the past, core was the only repository for everything.
As PECL grows in popularity (and as users demand more PECL
installations), we can hope this these hosts become more flexible.
I agree and I also hope this is the c
> From my experiences the problem with this is many shared hosts wont install
> non core modules, so the more modules moved from core to pecl the less
> flexible php will be and the less use it will be.
>
> I understand the need to keep the core code maintained and as clean and
> lean
> as possibl
:) 'do nothing' just sounds like 'let's ignore this whole thing', and that's
_really_ not what I meant there! But nm. It looks like DateTime/DateTimeZone
has the majority vote by a long chalk anyway, so be it.
- Steph
am I quote
I already agreed with Pierre over this, and offere
am I quote
I already agreed with Pierre over this, and offered to support him in
giving PEAR support for upgrading. So long as it goes in from the
start of 5_3 branch, why not? (Like it should've done at the start of
5_2 already.) I think it's worth holding out for a few more m
I already agreed with Pierre over this, and offered to support him in
giving PEAR support for upgrading. So long as it goes in from the start
of 5_3 branch, why not? (Like it should've done at the start of 5_2
already.) I think it's worth holding out for a few more months to get
sane names in t
I don't recall saying 'don't do anything' at any stage...
- Original Message -
From: "Ilia Alshanetsky" <[EMAIL PROTECTED]>
To: "PHP Internals"
Sent: Wednesday, July 19, 2006 5:15 PM
Subject: [PHP-DEV] Date flamewar summary
Now that everyone had their say (I hope) I've made a quick t
Of course we can.
I'll look into the problem.
Dmitry.
> -Original Message-
> From: Andrei Zmievski [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 19, 2006 8:24 PM
> To: Dmitry Stogov
> Cc: Marcus Boerger; internals@lists.php.net; Andi Gutmans
> Subject: Re: [PHP-DEV] PHP 5.2-dev "Cann
Rename it to DateTime and DateTimeZone.
On Jul 19, 2006, at 8:15 AM, Ilia Alshanetsky wrote:
Now that everyone had their say (I hope) I've made a quick tally of
the votes so far:
Rename date & timezone classes to DateTime and DateTimeZone
respectively
Tony
Derick
Mik
I would rather move more extensions from core to PECL, than from PECL to
core.
From my experiences the problem with this is many shared hosts wont install
non core modules, so the more modules moved from core to pecl the less
flexible php will be and the less use it will be.
I understand t
But how is foreach() a write context? Unless you mean that someone uses
foreach($f->bar as &$val) { .. }. Can we detect that though?
-Andrei
On Jul 19, 2006, at 8:22 AM, Dmitry Stogov wrote:
__get() never worked in write context proper.
It just CAN NOT work proper, because __get() returns by
Actually, TextIterator a PHP 6-only class so it will be inside a
namespace anyway.
-Andrei
On Jul 19, 2006, at 12:13 AM, Derick Rethans wrote:
Well, we already use prefixes for extensions, such as Soap* and DOM*
and
Spl*... so I don't see anything inheritly wrong with "DateTime" and
"DateTim
Hello,
On 7/19/06, Sean Coates <[EMAIL PROTECTED]> wrote:
Tony mentioned another issue: the headache of maintaining PECL code
between PHP versions. This is a valid point (and he can elaborate if he
likes), but is a separate issue.
I'm very aware of the PECL issues and that's irrelevant in thi
> Many people (incl. php devs) asked me if I can include zip in 5.2.0.
> Ilia thought it was too late in the game and planed to do it in 5.2.1.
I don't remember seeing a discussion on including Zip in core (perhaps I
just missed it, but a quick search didn't turn it up). I think Zip is
better suit
On 19.7.2006 17:59 Uhr, Pierre wrote:
On Wed, 19 Jul 2006 19:22:47 +0400
[EMAIL PROTECTED] ("Dmitry Stogov") wrote:
__get() never worked in write context proper.
It just CAN NOT work proper, because __get() returns by value
(zval*), but modification requires address (zval**).
We have a lot of
On Wed, 19 Jul 2006 19:22:47 +0400
[EMAIL PROTECTED] ("Dmitry Stogov") wrote:
> __get() never worked in write context proper.
> It just CAN NOT work proper, because __get() returns by value
> (zval*), but modification requires address (zval**).
> We have a lot of __get() related bugs because of th
On 19.07.2006 18:34, Pierre wrote:
Hello,
Many people (incl. php devs) asked me if I can include zip in 5.2.0.
Ilia thought it was too late in the game and planed to do it in 5.2.1.
I like to have it in, as experimental.
Please note that it intoduces a new class called Zip, but I never saw a
> Now that everyone had their say (I hope) I've made a quick tally of the
> votes so far:
>
> Rename date & timezone classes to DateTime and DateTimeZone respectively
FWIW, add me to this.
S
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.
Ilia Alshanetsky wrote:
Class names are not case sensitive, so it does not matter if it is
FooBar or fooBar or even FoObAR.
Ilia, since PHP5 we are case preserving. So it does matter, though only
stylistically, not technically.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Maili
On Wed, 19 Jul 2006 14:52:13 +0200
[EMAIL PROTECTED] (Pierre) wrote:
> Hi,
>
> Is it possible to symlink JSON as soon as possible? It would be nice
> if you don't forget it before the first RC.
Someone did it, thanks.
I just created the PHP_5_2 branche, cvs upd -dP and ./buildconf to get
it wor
Class names are not case sensitive, so it does not matter if it is
FooBar or fooBar or even FoObAR.
On 19-Jul-06, at 11:31 AM, Ron Korving wrote:
I don't wanna be a nitpicker here, but I've seen DateTimeZone and
DateTimezone both used in the discussion. I'm not sure which would
be the
pop
On 19.7.2006 17:22 Uhr, Dmitry Stogov wrote:
__get() never worked in write context proper.
It just CAN NOT work proper, because __get() returns by value (zval*), but
modification requires address (zval**).
We have a lot of __get() related bugs because of this situation in
bugs.php.net.
Fine,
Greg Beaver wrote:
> The solution I've found for pharring things has involved clever use of
> str_replace(). I pharred up phpMyAdmin and it works just great using this
> technique. This removes the need for an include_path hack.
phpMyAdmin is an interesting test case because every file access
Hello,
Many people (incl. php devs) asked me if I can include zip in 5.2.0.
Ilia thought it was too late in the game and planed to do it in 5.2.1.
I like to have it in, as experimental.
Please note that it intoduces a new class called Zip, but I never saw a
php zip implementation named Zip.
+1
On Wed, 19 Jul 2006, Ilia Alshanetsky wrote:
Now that everyone had their say (I hope) I've made a quick tally of the votes
so far:
Rename date & timezone classes to DateTime and DateTimeZone respectively
Tony
Derick
Mike
Rasmus
Andi
Ilia
Jani
I don't wanna be a nitpicker here, but I've seen DateTimeZone and
DateTimezone both used in the discussion. I'm not sure which would be the
popular one.
- Ron
PS: shake hands and make up.. group hug everyone? :)
"Ilia Alshanetsky" <[EMAIL PROTECTED]> schreef in bericht
news:[EMAIL PROTECTED]
>
On Tuesday 18 July 2006 12:25, Derick Rethans wrote:
> On Tue, 18 Jul 2006, Matt Sicker wrote:
> > Maybe you might not want to include that class until PHP6. Or, how
> > about for backwards compatibility, you do prefix the class name
> > with PHP, but when namespaces come into play, using the php
Dmitry Stogov wrote:
__get() never worked in write context proper. It just CAN NOT work
proper, because __get() returns by value (zval*), but modification
requires address (zval**). We have a lot of __get() related bugs
because of this situation in bugs.php.net.
Month ago Marcus disabled usage o
I'm OK with DateTime and DateTimeZone too.
Edin
Ilia Alshanetsky wrote:
> Now that everyone had their say (I hope) I've made a quick tally of
> the votes so far:
>
> Rename date & timezone classes to DateTime and DateTimeZone respectively
> Tony
> Derick
> Mike
> Rasmus
> Andi
__get() never worked in write context proper.
It just CAN NOT work proper, because __get() returns by value (zval*), but
modification requires address (zval**).
We have a lot of __get() related bugs because of this situation in
bugs.php.net.
Month ago Marcus disabled usage of __get() in write cont
Now that everyone had their say (I hope) I've made a quick tally of
the votes so far:
Rename date & timezone classes to DateTime and DateTimeZone respectively
Tony
Derick
Mike
Rasmus
Andi
Ilia
Don't do anything and wait till 5.3/6.0 etc..
On Wed, 19 Jul 2006 15:32:42 +0200
[EMAIL PROTECTED] (Christian Stocker) wrote:
>
>
> On 19.7.2006 15:24 Uhr, Richard Quadling wrote:
> > For PHP 5.2.0-dev (cli) (built: Jul 12 2006 12:20:25), I get ...
> >
> > Fatal error: Cannot use array returned from foo::__get('bar') in
> > write context i
I guess this is associated with bug #36647 (
http://bugs.php.net/bug.php?id=36647 ) and I do not think that this
makes a lot sense for the applications outside and will break them. For
my company I decided that __get handlers really suck and I do not
encourage our developers to use it anymore.
I
On 19.7.2006 15:24 Uhr, Richard Quadling wrote:
For PHP 5.2.0-dev (cli) (built: Jul 12 2006 12:20:25), I get ...
Fatal error: Cannot use array returned from foo::__get('bar') in write
context in C:\- on line 16
But only once, not 1 per line.
$f = new foo();
$a = $f->bar;
foreach($a as $key =
For PHP 5.2.0-dev (cli) (built: Jul 12 2006 12:20:25), I get ...
Fatal error: Cannot use array returned from foo::__get('bar') in write
context in C:\- on line 16
But only once, not 1 per line.
$f = new foo();
$a = $f->bar;
foreach($a as $key => $value)
fixes the code.
On 19/07/06, Christia
Hi,
Is it possible to symlink JSON as soon as possible? It would be nice if
you don't forget it before the first RC.
Cheers,
-- Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Just updated to the latest PHP 5.2-dev from CVS and now I get an Fatal
error with the following code
***
"bar","bar"=>"foo");
}
}
$f = new foo();
//error
foreach($f->bar as $key => $value) {
print "$key => $value";
}
?>
***
It throws a
"Fatal error: Cannot use array returned from foo
On 7/19/06, Jani Taskinen <[EMAIL PROTECTED]> wrote:
On Wed, 19 Jul 2006, Michael Wallner wrote:
> Andi Gutmans wrote:
>> I agree completely. Can't we just call the damn thing DateTime stick it into
>> RC1 of PHP 5.2, and move on?
>
> +1 for DateTime and DateTimezone; the flame was funny, but le
On Wed, 19 Jul 2006, Michael Wallner wrote:
Andi Gutmans wrote:
I agree completely. Can't we just call the damn thing DateTime stick it into
RC1 of PHP 5.2, and move on?
+1 for DateTime and DateTimezone; the flame was funny, but let's move on,
please.
I thought this was already agreed
> -Original Message-
> From: Lester Caine [mailto:[EMAIL PROTECTED]
> Sent: 19 July 2006 09:53
> To: Derick Rethans
> Cc: internals@lists.php.net
> Subject: Re: [PHP-DEV] Re: PEAR::Date broken (Was: [PHP-CVS]
> cvs: php-src(PHP_5_2) /ext/date php_date.c php_date.h)
>
> Derick Rethans
On Thu, 13 Jul 2006, Lukas Smith wrote:
> Lukas Smith wrote:
>
> Ok I see 2 options:
>
> 1)
> > Obviously one solution would be to disallow making anything an E_STRICT
> > notice that is not available since the first release of the given major
> > version.
>
> Pierre and Anthony seem to favor t
On Fri, 14 Jul 2006, Greg Beaver wrote:
> Sean Coates wrote:
> > Ilia Alshanetsky wrote:
> >
> >>Why not just define your own custom error handler and have it filter out
> >>the error messages that you don't want to see... To me this would seem
> >>like a easier approach, i would be against addin
Hi,
There are a couple things I don't like about how number_format() works
currently, so I'm hoping the functionality changes this patch provides can
be added. :-)
First is that when you're working with whole numbers and/or don't want any
decimal places, both decimal-related parameters are needed
Derick Rethans wrote:
( Now we just need browsers to return REAL timezone data ;) )
http://talks.php.net/show/time-phptek6/30 works pretty well... (but
talks.php.net doesn't have it so the example doesn't work there)
Not sure, but I think that still has the same problem with not knowing the
On 19.07.2006 01:31, Andi Gutmans wrote:
There's also a build error in ZTS in ext/filter and warnings in ext/date.
Can someone take a look?
I've just fixed several problems in ext/filter, but those weren't the problems
you mentioned.
Also, I don't see any warnings in ext/date either (only a co
On 19.07.2006 11:46, Michael Wallner wrote:
Andi Gutmans wrote:
I agree completely. Can't we just call the damn thing DateTime stick it into
RC1 of PHP 5.2, and move on?
+1 for DateTime and DateTimezone;
+1
the flame was funny, but let's move on, please.
Yes, please.
--
Wbr,
Antony Do
On Wed, 19 Jul 2006, Lester Caine wrote:
> Derick Rethans wrote:
>
> > On Wed, 19 Jul 2006, Lester Caine wrote:
> >
> > >Andi Gutmans wrote:
> > >
> > > >I agree completely. Can't we just call the damn thing DateTime stick it
> > > >into
> > > >RC1 of PHP 5.2, and move on?
> > >
> > >Gets my vot
Derick Rethans wrote:
On Wed, 19 Jul 2006, Lester Caine wrote:
Andi Gutmans wrote:
I agree completely. Can't we just call the damn thing DateTime stick it into
RC1 of PHP 5.2, and move on?
Gets my vote
( Now we just need browsers to return REAL timezone data ;) )
http://talks.php.net/sh
Michael Wallner wrote:
Andi Gutmans wrote:
I agree completely. Can't we just call the damn thing DateTime stick
it into
RC1 of PHP 5.2, and move on?
+1 for DateTime and DateTimezone; the flame was funny, but let's move
on, please.
+1
regards,
Lukas
--
PHP Internals - PHP Runtime Developm
Andi Gutmans wrote:
I agree completely. Can't we just call the damn thing DateTime stick it into
RC1 of PHP 5.2, and move on?
+1 for DateTime and DateTimezone; the flame was funny, but let's move on,
please.
--
Michael
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, v
On Wed, 19 Jul 2006, Lester Caine wrote:
> Andi Gutmans wrote:
>
> > I agree completely. Can't we just call the damn thing DateTime stick it into
> > RC1 of PHP 5.2, and move on?
>
> Gets my vote
>
> ( Now we just need browsers to return REAL timezone data ;) )
http://talks.php.net/show/time-p
Hello John,
where is the problem in having it as 'DateTime' or 'Date' in namespace
'PHP' and as 'PHPDateTime' or 'PHPDate' in the global namespace? We do
not have namespaces now but there is no technical reason to prevent that
from the beginning. So there is no preoblem here move a long forget a
On Wed, 19 Jul 2006, Steph Fox wrote:
> Sorry to be a pain Andi, but...
>
> >I agree completely. Can't we just call the damn thing DateTime stick it into
> > RC1 of PHP 5.2, and move on?
>
> It doesn't entirely resolve the problem. There's another class in there too.
>
> Do you really want Date
Hello Andrei,
we don't use '_' in class and method names. That said you must have
looked wrong:
[EMAIL PROTECTED] /usr/src/php-cvs $ php -r 'print_r(spl_classes());'|grep Spl
[SplFileInfo] => SplFileInfo
[SplFileObject] => SplFileObject
[SplObjectStorage] => SplObjectStorage
[Sp
Andi Gutmans wrote:
I agree completely. Can't we just call the damn thing DateTime stick it into
RC1 of PHP 5.2, and move on?
Gets my vote
( Now we just need browsers to return REAL timezone data ;) )
--
Lester Caine - G8HFL
-
L.S.Caine Electronic Services - http:
Derick Rethans wrote:
On Tue, 18 Jul 2006, Ilia Alshanetsky wrote:
And we need to get a bit on track as well. Let's outline possible options for
names, vote on them and move on to more important things.
The two naming options available so far are:
Option A: DateTime & DateTimeZone
That one
Hello Derick,
actually one of the reasons i pushed hard to get the exception hirarchy
in is the current acceptance of 'the early bird catches the fish'. We
should do somethign against it. Naming your classes no 'DateTime' and
'DateTimeZone' is pretty fair to me as it will also follow the current
n
I, as a mere PHP user really suggest you guys stick with DateTime and
TimeZone. If it's so core, you won't need to prefix TimeZone. It would feel
very natural to me without a DateTime_ prefix. Looking at this with a long
term view, I think prefixing it with PHP is a very bad idea. PHP6 is the
main
Steph Fox wrote:
Rasmus, I'm sorry but I can't agree with you. When we get namespacing
it'll make perfect sense to have PHP::Foo(). Until then, it makes no
sense whatsoever to me to mess about with plain names for root classes.
Since the early days of PHP4 everybody is using the plain names f
On Tue, 18 Jul 2006, John Coggeshall wrote:
> On Wed, 2006-07-19 at 03:29 +0200, Steph Fox wrote:
> > Rasmus, I'm sorry but I can't agree with you. When we get namespacing it'll
> > make perfect sense to have PHP::Foo(). Until then, it makes no sense
> > whatsoever to me to mess about with plain
Seems a little excessive to me!
On 18/07/06, Andrei Zmievski <[EMAIL PROTECTED]> wrote:
I just realized that it's the first time I used a quadruple pointer.
Must celebrate.
-Andrei
On Jul 18, 2006, at 3:07 PM, Andrei Zmievski wrote:
> + zval varargs = NULL;
> + int *n_varargs = N
On Wed, 19 Jul 2006, Steph Fox wrote:
> I don't think DateTime's more descriptive, I think it's a cop-out. And it's
> also longer to type :)
It describes it better than just Date though.
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/un
On Wed, 19 Jul 2006, Michael Gall wrote:
> On 7/19/06, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> >
> >
> > Because there is absolutely no reason to deliberately break our
> > installed base for a single version when it is quite arbitrary what we
> > call this class. We know for a fact that call
On Tue, 18 Jul 2006, Andrei Zmievski wrote:
> I am not sure I like this idea of prefixing all the classes with PHP_. Having
> PHP_TextIterator seems kind of wonky to me. Besides, I don't really see any
> SPL_ prefixed classes, they are all either *Iterator or *Object.
See:
http://www.php.net/~hel
On Wed, 19 Jul 2006, Lukas Smith wrote:
> Rasmus Lerdorf wrote:
>
> > I can see Andrei's argument for the iterator stuff where you do actually
> > have to type it often, but his identifiers are already unlikely to clash and
> > we could probably make an exception there.
>
> Well then we need to
On Tue, 18 Jul 2006, Rasmus Lerdorf wrote:
> But having PHPFoo does not in any way prevent PHP::Foo() in a future version.
Maybe not, but you're already trying to find workaround for a problem
that isn't even there yet...
> Not namespacing it in 5.2 and then namespacing it in 6 means we break
96 matches
Mail list logo
