> So, that actually "destroys" the reason to use studlyCaps at all, so why
> not do the right thing and make PHP consistent with itself, ie. use
> under_scores for ALL functions and methods? I'm willing to prepare a
> patch to the source AND documentation to make that happen. And
> because I'm sur
The final release is identical to 4.3.5RC4 (other then the version numbers).
Ilia
On March 26, 2004 02:58 pm, Thomas Seifert wrote:
> Hi folks,
>
> thanks for another great php-release.
>
> Are there any important changes since the last RC?
>
>
> TIA,
>
> thomas
--
PHP Internals - PHP Runtime D
Hi folks,
thanks for another great php-release.
Are there any important changes since the last RC?
TIA,
thomas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello Ilia,
Friday, March 26, 2004, 3:38:35 PM, you wrote:
> On March 26, 2004 09:35 am, you wrote:
>> So one would inherit from/extend a native class and then use studlyCaps and
>> call underscore style methods from parent class. Can you imagine how ugly
>> would this look?
> It may look ugly,
On Fri, Mar 26, 2004 at 01:47:52PM -0500, Ilia Alshanetsky wrote:
> Can you please to compile PHP without any options to see if the problem
> persists. If it does not try removing the --without-libmbfl option (not
> needed).
>
> Ilia
General Configure gives me:
Script started on Fri Mar 26 12
Can you please to compile PHP without any options to see if the problem
persists. If it does not try removing the --without-libmbfl option (not
needed).
Ilia
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Fri, Mar 26, 2004 at 08:55:52AM -0500, Ilia Alshanetsky wrote:
> PHP Development Team is proud to announce the release of PHP 4.3.5. This is
> primarily a bug fix release, without any new features or additions.PHP 4.3.5
> is by far the most stable release of PHP to date and it is recommended tha
On Friday 26 March 2004 16:54, Andi Gutmans wrote:
> At 04:50 PM 3/26/2004 +0100, Edin Kadribasic wrote:
> >On Friday 26 March 2004 16:43, Andi Gutmans wrote:
> > > I meant "A bad decision is better than no decision".
> >
> >So this bad decision is to have a standard that everybody is free to
> > i
At 04:50 PM 3/26/2004 +0100, Edin Kadribasic wrote:
On Friday 26 March 2004 16:43, Andi Gutmans wrote:
> I meant "A bad decision is better than no decision".
So this bad decision is to have a standard that everybody is free to ignore?
It means that we change whatever extensions aren't studlyCaps to
On Friday 26 March 2004 16:43, Andi Gutmans wrote:
> I meant "A bad decision is better than no decision".
So this bad decision is to have a standard that everybody is free to ignore?
Edin
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I meant "A bad decision is better than no decision".
Date: Fri, 26 Mar 2004 17:32:13 +0200
To: "Wez Furlong" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
From: Andi Gutmans <[EMAIL PROTECTED]>
Subject: Re: [PHP-DEV] studlyCaps conclusion
I pretty much agree with Wez. A bad decision is worse than no de
On Mar 26, 2004, at 10:30 AM, Stefan Walk wrote:
On Fri, Mar 26, 2004 at 07:05:15AM -0800, Rasmus Lerdorf wrote:
On Fri, 26 Mar 2004, Stefan Walk wrote:
Oh, and the strpos/str_repeat inconsistency should be 'fixed' too,
maybe
make strpos an alias to str_pos or alike...
So you are saying strlen()
I pretty much agree with Wez. A bad decision is worse than no decision :)
The way I see it, studlyCaps has been in the CODING_STANDARDS *and*
precisely because people and PEAR use them for method names we should go
with studlyCaps. It would suck to have user-land and internal methods look
differ
On Fri, Mar 26, 2004 at 07:05:15AM -0800, Rasmus Lerdorf wrote:
> On Fri, 26 Mar 2004, Stefan Walk wrote:
> > Oh, and the strpos/str_repeat inconsistency should be 'fixed' too, maybe
> > make strpos an alias to str_pos or alike...
>
> So you are saying strlen() should be str_len() as well? If I e
On Fri, 26 Mar 2004, Stefan Walk wrote:
> Oh, and the strpos/str_repeat inconsistency should be 'fixed' too, maybe
> make strpos an alias to str_pos or alike...
So you are saying strlen() should be str_len() as well? If I ever see a
patch to change that I'll hunt the person down and make them sw
Lets create an engine level option, lets calls it "coding_convention".
The default is "studlyCaps".
Consider the following code:
$foo->fooBarBaz();
When coding_convention=studlyCaps, the engine will resolve the method
thus (psuedo code):
if (!method_exists($obj, $methodname)) {
$tmp_method
On Fri, Mar 26, 2004 at 09:53:28AM -0500, George Schlossnagle wrote:
> As Edin and Lukas have both pointed out, one of the major precepts of
> OO programming is that you can (and often do) overload methods in your
> parent. Adopting two different styles really doesn't work if you ever
> want to
Yes it is very strange. Sometimes apache starts with no error, but that
is almost an exception...
Path is set as follows:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program\PHP\php5-win32;C:\Program\mysql\bin
Andi Gutmans wrote:
Sounds strange.
Have you made sure that php
On Mar 26, 2004, at 9:38 AM, Ilia Alshanetsky wrote:
On March 26, 2004 09:35 am, you wrote:
So one would inherit from/extend a native class and then use
studlyCaps and
call underscore style methods from parent class. Can you imagine how
ugly
would this look?
It may look ugly, but without a doubt
On March 26, 2004 09:35 am, you wrote:
> So one would inherit from/extend a native class and then use studlyCaps and
> call underscore style methods from parent class. Can you imagine how ugly
> would this look?
It may look ugly, but without a doubt it would be very clear which code is
'user' and
I don't normally go in for big arrays in PHP, but I've had the
"opportunity" to write a script that grabs a couple of thousand rows
from a database, each row having ~120 small fields, and serialize it
for consumption elsewhere.
I didn't benchmark it, but it takes a good few seconds to serialize.
I
Edin Kadribasic wrote:
On Friday 26 March 2004 15:27, Ilia Alshanetsky wrote:
Not entirely true, since PHP5 has quite a bit of native OO code, it would
prevent people from easily making a distinction between native and user
created classes/interfaces. It is by no means a deciding problem, but ye
On Friday 26 March 2004 15:27, Ilia Alshanetsky wrote:
> Not entirely true, since PHP5 has quite a bit of native OO code, it would
> prevent people from easily making a distinction between native and user
> created classes/interfaces. It is by no means a deciding problem, but yet
> another reason
On March 26, 2004 09:23 am, George Schlossnagle wrote:
> The StudlyCaps standard only applies inside OO code, so I see this as
> much less of an issue (certainly no worries of conflicts).
Not entirely true, since PHP5 has quite a bit of native OO code, it would
prevent people from easily making a
On Mar 26, 2004, at 9:16 AM, Ilia Alshanetsky wrote:
I should also mention that majority, if not all of the users whom I
spoke to
at the Montreal conference seem to prefer to have PHP stick to a single
naming convention that they are familiar with rather then use 2
distinct
naming conventions. T
I should also mention that majority, if not all of the users whom I spoke to
at the Montreal conference seem to prefer to have PHP stick to a single
naming convention that they are familiar with rather then use 2 distinct
naming conventions. They were even able to raise some valid points we had
Quoting Derick Rethans <[EMAIL PROTECTED]>:
> On Thu, 25 Mar 2004, Andi Gutmans wrote:
>
> > OK Guys. It's decision time. I suggested to move to studlyCaps and keep
> > consistency with the new PHP 5 changes.
> > If we go with this, I think we should make these changes ASAP and try and
> > aim fo
PHP Development Team is proud to announce the release of PHP 4.3.5. This is
primarily a bug fix release, without any new features or additions.PHP 4.3.5
is by far the most stable release of PHP to date and it is recommended that
all users upgrade to this release whenever possible.
The major fixes
On Thu, 25 Mar 2004, Andi Gutmans wrote:
> OK Guys. It's decision time. I suggested to move to studlyCaps and keep
> consistency with the new PHP 5 changes.
> If we go with this, I think we should make these changes ASAP and try and
> aim for RC2 within two weeks.
Isn't the largest concern consis
Sounds strange.
Have you made sure that php5ts.dll is in your system path?
At 11:03 AM 3/26/2004 +0100, Erik Franzén wrote:
I still have a problem when starting apache 1.3.29 with PHP5 on Windows XP
Pro. I have tried two different Win installations with no success.
I am getting the following erro
This is a patch to add an informational header to messages sent from PHP
via the mail() function. This can help to track which script on a server
was used to send a message, and which client caused it to be sent.
The header added has the form:
X-PHP-Script: for
For example:
X
It seems to have something to do with path in php.ini
When I remarks the folling line it works
include_path=".;C:/Program/PHP/PEAR/pear;C:/Program/PHP/Smarty/libs"
And sometimes I also need to remark the extension path
extension_dir = "C:/Program/PHP/php5-win32/ext"
I still have a problem whe
I still have a problem when starting apache 1.3.29 with PHP5 on Windows
XP Pro. I have tried two different Win installations with no success.
I am getting the following error:
SzAppName: apache.exe szAppver: 0.0.0.0 SzModName: php5ts.dll
sZModVer: 5.0.0.0 offset: 0003d0c3
For more debug informat
33 matches
Mail list logo
