RE: [PHP-DEV] Fwd: [PHP-CVS] cvs: php4 /ext/bcmath bcmath.c/ext/bcmath/libbcmath/src bcmath.h init.c output.c raise.c raisemod.c recmul.csqrt.c str2num.c zero.c

PROTECTED]] > Sent: Wednesday, November 20, 2002 8:14 PM > To: [EMAIL PROTECTED] > Subject: Re: [PHP-DEV] Fwd: [PHP-CVS] cvs: php4 /ext/bcmath bcmath.c > /ext/bcmath/libbcmath/src bcmath.h init.c output.c raise.c raisemod.c > recmul.c sqrt.c str2num.c zero.c > > > I have backups

RE: [PHP-DEV] Fwd: [PHP-CVS] cvs: php4 /ext/bcmath bcmath.c /ext/bcmath/libbcmath/src bcmath.h init.c output.c raise.c raisemod.c recmul.c sqrt.c str2num.c zero.c

more reason to look for an alternative. -- james > -Original Message- > From: Andi Gutmans [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 20, 2002 8:14 PM > To: [EMAIL PROTECTED] > Subject: Re: [PHP-DEV] Fwd: [PHP-CVS] cvs: php4 /ext/bcmath bcmath.c > /ext/bcma

Re: [PHP-DEV] Fwd: [PHP-CVS] cvs: php4 /ext/bcmath bcmath.c/ext/bcmath/libbcmath/src bcmath.h init.c output.c raise.c raisemod.c recmul.csqrt.c str2num.c zero.c

I have backups of number.c and number.h but I see them in Attic/ so it might be better to restore them so that we keep the history. Anyone know how to do it? mv Attic/number* . doesn't seem to work. Andi At 10:08 PM 11/20/2002 +0200, Andi Gutmans wrote: There seems to be some bug in CVS. After

Re: [PHP-DEV] Fwd: PHP-QA Test Failed for 20021027

Hi, Can I see the log (bug16069.out) and the output of phpinfo() generated by the cli binary he built? I guess ICONV library identification was failed since FreeBSD version was also installed, and then preferred to libiconv by configure. Anyway I cannot confirm it now as I have no FreeBSD-instal

Re: [PHP-DEV] Fwd: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_execute.c phpdoc/scripts revcheck.php

Nothign to worry, you triggered a race condition of the script which generates this messages. We've seen this not the first time. Actually, someone else commited something the very same moment it seems: 2002-10-23 22:26 tom * revcheck.php: added file-sizes to fi

Re: [PHP-DEV] Fwd: Re: [sab-php] sablotron instalation

On Tue, 8 Oct 2002, Melvyn Sopacua wrote: > By the way: > > what about nuking ext/sablot? [derick@kossu php-4.3.0dev]$ ls -l ext/sablot ls: ext/sablot: No such file or directory It's already nuked :) Derick -- --- Deri

Re: [PHP-DEV] [Fwd: PHP fopen() CRLF Injection]

On Thu, Sep 12, 2002 at 10:47:12AM +0100, James Cox wrote: > Stefan, > > is this really worth it? I think this will break too many scripts. > > -- james My change only changes parse_url() to remove characters that are invalid in urls. If such characters occur in an url that is passed to parse_

Re: [PHP-DEV] [Fwd: PHP fopen() CRLF Injection]

Hi, > We got close one that Jani mentioned in bug db :) > > It's user's problem, but I'm sure there are many > scripts do not check user input enough. > > We're probably better to mention security risks more > in the manual... I fixed this issue in CVS in the way that parse_url() removes cont

Re: [PHP-DEV] [Fwd: PHP fopen() CRLF Injection]

Hey, AFAIK Stefan already took care of this. Stefan? Derick On Thu, 12 Sep 2002, Yasuo Ohgaki wrote: > FYI > > We got close one that Jani mentioned in bug db :) > > It's user's problem, but I'm sure there are many > scripts do not check user input enough. > > We're probably better to menti

[PHP-DEV] Re: Sorry! Re: [PHP-DEV] Fwd: REJECTED: <5.1.0.14.2.20020607225328.03df2740@127.0.0.1>

Richard S. Blake <[EMAIL PROTECTED]> wrote: > sorry abt that .. an overzealous SPAM filter triggered on your three > exclamation points . in your SUBJECT > > should be fixed now :-S you should further fix your spam system to bounce to the SMTP envelope sender instead of whatever broken

[PHP-DEV] Sorry! Re: [PHP-DEV] Fwd: REJECTED:<5.1.0.14.2.20020607225328.03df2740@127.0.0.1>

sorry abt that .. an overzealous SPAM filter triggered on your three exclamation points . in your SUBJECT should be fixed now :-S --On Friday, June 7, 2002 10:58 PM +0300 Andi Gutmans <[EMAIL PROTECTED]> wrote: > Any idea why I got this when posting to php-dev? > > Andi > >> Delivered-

Re: [PHP-DEV] Fwd: REJECTED: <5.1.0.14.2.20020607225328.03df2740@127.0.0.1>

I got it too.. - brad --- Andi Gutmans <[EMAIL PROTECTED]> wrote: > Any idea why I got this when posting to php-dev? > > Andi > > >Delivered-To: [EMAIL PROTECTED] > >Sender: <[EMAIL PROTECTED]> (reject) > >Date: Thu, 06 Jun 2002 08:50:05 -0700 > >X-Autogenerated: Reply > >To: Andi Gutmans <[EM

Re: [PHP-DEV] Fwd: REJECTED:<5.1.0.14.2.20020607225328.03df2740@127.0.0.1>

Somebody from PRESENCE-GROUP.COM is subscribed to php-dev list and is filtering mail through spamcop or something program. I am getting them to. Brian At 10:58 PM +0300 6/7/02, Andi Gutmans wrote: >Any idea why I got this when posting to php-dev? > >Andi > >>Delivered-To: [EMAIL PROTECTED] >>Se

Re: [PHP-DEV] Fwd: Re: libxml2 - php

Hello, as you see he also gave the good reasons why NOT bundling it with PHP for which I am too. - Markus On Wed, May 29, 2002 at 04:53:48PM -0700, brad lafountain wrote : > > --- Daniel Veillard <[EMAIL PROTECTED]> wrote: > > Date: Wed, 29 May 2002 23:28:11 +0200 > > From: Da

Re: [PHP-DEV] [Fwd: new dns function, gethostent]

> Hi everyone, > > I have a need not fullfilled by the current short set of dns functions > (no way to retrieve aliases), so I wrote a 'gethostent' function, which > accepts either hostname or ip, and returns a hash equivelant of the C > hostent struct. patch is attached, if no objections in the

Re: [PHP-DEV] [Fwd: new dns function, gethostent]

At 23:13 18.04.2002, Shane Caraveo wrote: >Hi everyone, > >I have a need not fullfilled by the current short set of dns functions >(no way to retrieve aliases), so I wrote a 'gethostent' function, which >accepts either hostname or ip, and returns a hash equivelant of the C >hostent struct. patch

Re: [PHP-DEV] [Fwd: posix_uname another bug @^|[@#\@^#~@{[?]

Vergoz Michael wrote: > have you reveiv the pgsql.c optimization code ? > (is nothing to fix le utsname ;)) No. I didn't get any patch. Could mail me. > > another question : how to become a php developer ? Submit sevral patches? then apply CVS account? -- Yasuo Ohgaki -- PHP Development Ma

Re: [PHP-DEV] [Fwd: posix_uname another bug @^|[@#\@^#~@{[?]

<[EMAIL PROTECTED]> Sent: Sunday, March 24, 2002 12:51 PM Subject: Re: [PHP-DEV] [Fwd: posix_uname another bug @^|[@#\@^#~@{[?] > Why do you think apache gets a segfault? sorry not segfault but compilation problem ;) > The only thing is the the 'domainname' key is

Re: [PHP-DEV] [Fwd: posix_uname another bug @^|[@#\@^#~@{[?]

Why do you think apache gets a segfault? The only thing is the the 'domainname' key is missing from the hash although it should display the content of __domainname (on non-bsd systems) I'm willing to fix it if someone comes up with a proper patch that also honors BSD. It'

Re: [PHP-DEV] [Fwd: [PATCH] add appname argument to sybase_connect]

[EMAIL PROTECTED] wrote: > Hello, > > I applied it. Can you also write some documentation about it? > Thanks. At least, i can try... : int sybase_connect ( string servername, string username, string password [, string charset [, string appname]]) int sybase_pconnect ( string servername, strin

Re: [PHP-DEV] [Fwd: [PATCH] add appname argument to sybase_connect]

Hello, I applied it. Can you also write some documentation about it? regards, Derick On Wed, 6 Mar 2002, Christophe Sollet wrote: > Hello, > > I resubmit this patch again since i didn't get any reply from my > previous post. > Please get a look at it and, at least, let me know if you think th

Re: [PHP-DEV] [Fwd: [PHP-CVS] cvs: php4 /ext/mcve mcve.c]

Sebastian Bergmann wrote: >> First of all, why does this not belong in ext/ >> as CCVS/CyberCash/etc does ? The extensions you mention will be moved to PEAR / PECL in due time. At the moment we would like to see no new extensions added to /php4/ext/. -- Sebastian Bergmann http://sebasti

Re: [PHP-DEV] [Fwd: [PHP-CVS] cvs: php4 /ext/mcve mcve.c]

Hi, On Thu, 28 Feb 2002 17:48:57 +0100 Sebastian Bergmann <[EMAIL PROTECTED]> wrote: > > Next, we heavily support the MacOS X community, > > but last I checked, PEAR wouldn't even compile > > on OS X, so this would inhibit OS X users from > > using our module. PEAR is a repository, it is not sup

Re: [PHP-DEV] Fwd: Zend debug server trouble

On Thu, 2002-02-21 at 11:17, Zeev Suraski wrote: > At 16:37 21/02/2002, [EMAIL PROTECTED] wrote: > >Hey, > > > >Wrong list again... call/write Zend for support. Zend's commercial > >products have nothing to do with PHP. > > They have everything to do with PHP, but they're not a part of the PHP

Re: [PHP-DEV] Fwd: Zend debug server trouble

At 16:37 21/02/2002, [EMAIL PROTECTED] wrote: >Hey, > >Wrong list again... call/write Zend for support. Zend's commercial >products have nothing to do with PHP. They have everything to do with PHP, but they're not a part of the PHP project :) Zeev -- PHP Development Mailing List

Re: [PHP-DEV] Fwd: Zend debug server trouble

Hey, Wrong list again... call/write Zend for support. Zend's commercial products have nothing to do with PHP. Derick On Thu, 21 Feb 2002, bvr wrote: > > I tried and posted this on php-general first, but didn't get a reply. > > If anyone can help me out, please reply to my private address for i

Re: [PHP-DEV] FWD: possible bug in date() function

with me :) I guess Jim already clarified about these in the manual. -- Yasuo Ohgaki > > >>-Original Message- >>From: Yasuo Ohgaki [mailto:[EMAIL PROTECTED]] >>Sent: Monday, February 11, 2002 9:26 PM >>To: [EMAIL PROTECTED]; [EMAIL PROTECTED] >>Cc:

RE: [PHP-DEV] FWD: possible bug in date() function

ent: Monday, February 11, 2002 9:26 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: 'Chris Newbill' > Subject: Re: [PHP-DEV] FWD: possible bug in date() function > > > Sean R. Bright wrote: > > What? The original format string was: > > > > &qu

Re: [PHP-DEV] FWD: possible bug in date() function

t; > >>-Original Message- >>From: Yasuo Ohgaki [mailto:[EMAIL PROTECTED]] >>Sent: Monday, February 11, 2002 8:21 PM >>To: Chris Newbill >>Cc: [EMAIL PROTECTED] >>Subject: Re: [PHP-DEV] FWD: possible bug in date() function >> >> >>Chris

RE: [PHP-DEV] FWD: possible bug in date() function

:[EMAIL PROTECTED]] > Sent: Monday, February 11, 2002 8:21 PM > To: Chris Newbill > Cc: [EMAIL PROTECTED] > Subject: Re: [PHP-DEV] FWD: possible bug in date() function > > > Chris Newbill wrote: > > Ehh...from manual > > > > n - month without leading zeros; i

Re: [PHP-DEV] FWD: possible bug in date() function

Yasuo Ohgaki <[EMAIL PROTECTED]> wrote: > Chris Newbill wrote: >> Ehh...from manual >> >> n - month without leading zeros; i.e. "1" to "12" >> >> So yeah it would print 2th. Cause today is the 10"th". > > The format does not make sense much, though. sure it does. the 'bug' reporter had a bogu

Re: [PHP-DEV] FWD: possible bug in date() function

Chris Newbill wrote: > Ehh...from manual > > n - month without leading zeros; i.e. "1" to "12" > > So yeah it would print 2th. Cause today is the 10"th". The format does not make sense much, though. I guess 1th, 2th are correct English now, instead of 1st, 2nd. ;) -- Yasuo Ohgaki > > -Chr

RE: [PHP-DEV] FWD: possible bug in date() function

Ehh...from manual n - month without leading zeros; i.e. "1" to "12" So yeah it would print 2th. Cause today is the 10"th". -Chris -Original Message- From: Yasuo Ohgaki [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 10, 2002 12:47 PM To: [EMAIL PROTECTED] Subject: [PHP-DEV] FWD: po

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity:

Stig S. Bakken wrote: > Because PHP has gotten about a million more users since then? > Good point. I also think less number of impacts for existing code is preferred. Since many people believe ini option for case sensitivity will lead bad compatibility problem like register_globals, I might wr

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

On Wed, 2002-02-06 at 22:36, Jani Taskinen wrote: > > Many scripts will break anyway if you update to PHP 5.. > > +1 (still) for case-sensitivity which would make the language > more conistent. Or if this is ruled out, then let's make all > variables and constants case-insensitive too. It is so

[PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Casesensitivity: Conclusion(?)]

Yes, this is going to be a problem. I have thought one a way of dealing with it. Let people declare in their code that major version of PHP they have written their code for, and issue "possible ambigous context" warnings unless it's declared written for PHP 5. For example, the code: function b

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity:Conclusion(?)]

Because PHP has gotten about a million more users since then? - Stig On Thu, 2002-02-07 at 00:57, Jason Greene wrote: > If everyone has been able to adapt to case sensitive variable names, why > can they not adapt to case sensitive function names? > > -Jason > > On Wed, 2002-02-06 at 09:01, J

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity:Conclusion(?)]

After careful consideration on the CS issue I must say I agree with John here. The _only_ case where I feel CS is a problem, is when dealing with other environments. But the price for changing this today is simply too high. It should have been done in PHP 3.0. We have other BC issues to soak o

[PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

Andi Gutmans wrote: > At 07:58 AM 2/7/2002 +0100, Stig S. Bakken wrote: *SNIP* > > I agree and I'll try and check if pretty names can be handled. > Errors with case senstive names are intuitive to fix. While errors with name space change is _not_ intuitive to where and what is wrong. If we did

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

At 07:58 AM 2/7/2002 +0100, Stig S. Bakken wrote: >After careful consideration on the CS issue I must say I agree with John >here. The _only_ case where I feel CS is a problem, is when dealing >with other environments. But the price for changing this today is >simply too high. It should have be

[PHP-DEV] RE: [Zend Engine 2] Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity:Conclusion(?)]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > After careful consideration on the CS issue I must say I > agree with John here. The _only_ case where I feel CS is a > problem, is when dealing with other environments. But the > price for changing this today is simply too high. It should

Re: [PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

Yasuo Ohgaki wrote: > Case of names can be easily converted by program. do you think it will be easy in this situation?: and, by the way: what kind of a program is going to convert this? a shell script? what about windows users? a php script? what about users that just want to install a prod

[PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

To upgrade from PHP4 to PHP5, most users should carefully change/test existing script unless their scripts are completely OO or non-OO. This BC problem is worse than case sensitive names, IMHO. (BTW, I like ZE2 way than ZE1 way) PHP5 may call wrong function unless user change their code ;) Case

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

At 06:04 PM 2/6/2002 -0600, Jason Greene wrote: >On Wed, 2002-02-06 at 10:13, Zeev Suraski wrote: > > While I agree with Marko's vote (I'm also very much against it), I derive > > my conclusion from a whole different perspective. > > > > Guys, we are not next to the drawing board right now. The

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

Hi, > Even with the whole new object API, most of the code would work without > modifications (at least mostly all of the PHP object code I got to take a > look at). And if it doesn't - turning on PHP 4 compatibility should bridge > the gap... Glad to hear that :) I have been thinking, and bre

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

At 02:04 AM 2/7/2002, Jason Greene wrote: >You left off language consistency between variable names, and function >names. I consider that the 'warm fuzzy feeling' of purity, which I can totally understand and sympathize with. However, this sort of consistency between variables and function nam

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

No need to vote, it won't change anyways :) Derick On 6 Feb 2002, Jason Greene wrote: > +1 for case sensitivity > > On Wed, 2002-02-06 at 15:36, Jani Taskinen wrote: > > > > Many scripts will break anyway if you update to PHP 5.. > > > > +1 (still) for case-sensitivity which would make the lang

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

+1 for case sensitivity On Wed, 2002-02-06 at 15:36, Jani Taskinen wrote: > > Many scripts will break anyway if you update to PHP 5.. > > +1 (still) for case-sensitivity which would make the language > more conistent. Or if this is ruled out, then let's make all > variables and constants case-i

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

On Wed, 2002-02-06 at 10:13, Zeev Suraski wrote: > While I agree with Marko's vote (I'm also very much against it), I derive > my conclusion from a whole different perspective. > > Guys, we are not next to the drawing board right now. The specs were > defined and the layout was laid years ago

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity:Conclusion(?)]

If everyone has been able to adapt to case sensitive variable names, why can they not adapt to case sensitive function names? -Jason On Wed, 2002-02-06 at 09:01, John Lim wrote: > Thanks for posting this request for comments, Yasuo. > > I think from a C developer's point of view, it makes perfe

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

On Wed, 2002-02-06 at 05:37, Marko Karppinen wrote: > Markus: > > You have the wrong book then. Painless integration with other > > technologies is the main argument (.NET, SOAP, SRM [didn't > > forget it this time, Derick ;)]) > > I have some trouble believing that this is a real-world problem.

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

Many scripts will break anyway if you update to PHP 5.. +1 (still) for case-sensitivity which would make the language more conistent. Or if this is ruled out, then let's make all variables and constants case-insensitive too. It is so confusing for all the newbies when $FOO isn't same as $foo. -

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

Hi, IMHO making PHP case sensitive after being case-INsensitive for so many years is a very bad idea. The reasons are already mentioned on the list. For us (ISP in The Netherlands) the most important one is BC. We would not be able to upgrade any of our servers when this would go into PHP5. A lot

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

I very much agree with this Email and am -1. Andi At 11:01 PM 2/6/2002 +0800, John Lim wrote: >Thanks for posting this request for comments, Yasuo. > >I think from a C developer's point of view, it makes perfect >sense to have case-sensitivity. From a scripting point-of-view, >I think it is a st

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

While I agree with Marko's vote (I'm also very much against it), I derive my conclusion from a whole different perspective. Guys, we are not next to the drawing board right now. The specs were defined and the layout was laid years ago. At this point in time we're only supposed to change some

RE: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

Title: RE: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)] Thies C. Arntzen writes: > On Wed, Feb 06, 2002 at 07:40:18PM +0900, Yasuo Ohgaki wrote: > > Hi all, > > > > I'm posting this for those who are not subscribing > > Zend

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

Thanks for posting this request for comments, Yasuo. I think from a C developer's point of view, it makes perfect sense to have case-sensitivity. From a scripting point-of-view, I think it is a step backward. Studies by the Python group have shown that case-sensitivity is a serious barrier for be

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

On Wed, 6 Feb 2002, Brent R. Matzelle wrote: > --- Marko Karppinen <[EMAIL PROTECTED]> wrote: > > > > >> However, we need vote for if PHP5 will have case > > >> sensitive class/function/constant names. > > > > > > +1 for case-sensitive everything > > > > -1. Differentiating two objects only b

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

--- Marko Karppinen <[EMAIL PROTECTED]> wrote: > > >> However, we need vote for if PHP5 will have case > >> sensitive class/function/constant names. > > > > +1 for case-sensitive everything > > -1. Differentiating two objects only by the case of their names > seems absurd to me. This is not how

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

On Wed, Feb 06, 2002 at 07:40:18PM +0900, Yasuo Ohgaki wrote: > Hi all, > > I'm posting this for those who are not subscribing > Zend Engine 2 list. > > Many of developers seems to have case sensitivity for > class/function names. > However, we need vote for if PHP5 will have case > sensitive cl

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

Yasuo Ohgaki wrote: > Andrei has been wrote conversion program. > I don't know the details, but it may do better job > than making all to lowercase (?) will it also detect and rewrite the usage of function/method names in strings used for eg. callback handlers? -- Hartmut Holzgraefe [EMAIL P

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

Hartmut Holzgraefe wrote: > Marc Boeren wrote: > >> +1 for case-sensitive everything > > > so you volunter to rewrite all the code that uses oci or gd > extension now but uses it all lowercase? ;) > > Andrei has been wrote conversion program. I don't know the details, but it may do better jo

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

Marc wrote: > I don't think people should write code that differentiates by case, but > case-sensitive coding leads to consistency in naming, so you will not read > MySQL_ConneCt somewhere and mysql_connect somewhere else, while it means the > same thing... If you just want to promote case-accura

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

Markus: > You have the wrong book then. Painless integration with other > technologies is the main argument (.NET, SOAP, SRM [didn't > forget it this time, Derick ;)]) I have some trouble believing that this is a real-world problem. Interfacing with a case-sensitive system is troublesome only whe

RE: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

> oci and gd extensions had mixed-case names for ages, > but you see both mixed- and all-lower case usage > all over the place now OK, I see your point. I'll start writing a little shellscript that recursively crawls through your filesystem, updating every text-file against a list of function-na

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

On Wed, Feb 06, 2002 at 11:01:21AM +, Marko Karppinen wrote : > > >> However, we need vote for if PHP5 will have case > >> sensitive class/function/constant names. > > > > +1 for case-sensitive everything > > -1. Differentiating two objects only by the case of their names > seems absurd to

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

Marc Boeren wrote: >>>+1 for case-sensitive everything >>> >>so you volunter to rewrite all the code that uses oci or gd >>extension now but uses it all lowercase? ;) >> > > I didn't say +1 for lower-case everything! (although that is my preference, > for functionnames at least ;-) oci and gd e

RE: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

> > +1 for case-sensitive everything > > -1. Differentiating two objects only by the case of their names > seems absurd to me. This is not how humans function. I don't think people should write code that differentiates by case, but case-sensitive coding leads to consistency in naming, so you w

RE: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

> > +1 for case-sensitive everything > > so you volunter to rewrite all the code that uses oci or gd > extension now but uses it all lowercase? ;) I didn't say +1 for lower-case everything! (although that is my preference, for functionnames at least ;-) Cheerio, Marc. -- PHP Development Mai

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

>> However, we need vote for if PHP5 will have case >> sensitive class/function/constant names. > > +1 for case-sensitive everything -1. Differentiating two objects only by the case of their names seems absurd to me. This is not how humans function. Ease of implementation is the only thing spe

Re: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclus ion(?)]

Marc Boeren wrote: > +1 for case-sensitive everything so you volunter to rewrite all the code that uses oci or gd extension now but uses it all lowercase? ;) -- Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77 Wir stellen für Sie aus auf der CeBIT 2002 und freuen uns

RE: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]

> However, we need vote for if PHP5 will have case > sensitive class/function/constant names. +1 for case-sensitive everything Cheerio, Marc. -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] [Fwd: PHP and MySQL 4.0.0]

On Fri, 2 Nov 2001, Jani Taskinen wrote: > > I have committed a fix for all this. > Please check it out, especially the thread-safe stuff. In any case, note, that by default, MySQL is compiled without old-style functions in libs, but references to such functions in all headers are OK, that make

Re: [PHP-DEV] [Fwd: PHP and MySQL 4.0.0]

Jani Taskinen wrote: > I have committed a fix for all this. > Please check it out, especially the thread-safe stuff. Works fine with * PHP built as CGI, Apache 2.0.28-dev and MySQL 3.23.41 with bundled libmysql on Windows * PHP with Apache2Filter SAPI, Apache 2.0.28-dev and

Re: [PHP-DEV] [Fwd: PHP and MySQL 4.0.0]

I have committed a fix for all this. Please check it out, especially the thread-safe stuff. This diff shows why the HAVE_MYSQL_REAL_CONNECT broke things: http://cvs.php.net/diff.php/php4/ext/mysql/php_mysql.c?r1=1.37&r2=1.38&f=h :) --Jani On Fri, 2 Nov 2001, Sebastian Bergmann wrote: >Timot

Re: [PHP-DEV] fwd: buildconf troubles

On Mon, 17 Sep 2001, Hartmut Holzgraefe wrote: > on one of the boxes everything worked fine again after > commenting out the DLOPEN_SELF stuff in Zend/Zend.m4 > while the other one still gives lots of "undefined macros" i tried this, all "undefined macros" go away and php is building for me agai

Re: [PHP-DEV] fwd: buildconf troubles

well, the aclocal.m4 problem was related to me setting the clock back by several month to get going with my SAP R/3 demo system without getting another key (no email access by that time), thus confusing make another possible cause is the dlsym() check in Zend/Zend.m4, line 61ff

Re: [PHP-DEV] fwd: buildconf troubles

Doug MacEachern wrote: > > still stuck on this with current cvs, anybody else seeing this? > > From [EMAIL PROTECTED] Thu Aug 30 09:47:20 2001 -0700 > Status: > X-Status: > X-Keywords: > Date: Thu, 30 Aug 2001 09:47:20 -0700 (PDT) > From: Doug MacEachern <[EMAIL PROTECTED]> > To: [EMAIL PROTECTE

Re: [PHP-DEV] fwd: buildconf troubles

same problem on two SuSE 7.0 boxes here this week while an older one running SuSE 6.3 and a manually updated libtool 1.4 did work fine (same version numbers of auto* on both of them) on one of the boxes everything worked fine again after commenting out the DLOPEN_SELF stuff in Zend/Zend.m4 while

Re: [PHP-DEV] fwd: buildconf troubles

i had the same effect last week on two SuSE 7.0 systems while a 6.3 with manualy updated libtool worked fine (all with the same autoconf and automake versions) on one of the boxes it helped to comment out the DLOPEN_SELF stuff in Zend/Zend.m4, but the other one is still giving me undefined macro

Re: [PHP-DEV] Fwd: Bug id #12378 2000 is not a leapyear!

Read ext/calendar/gregor.c and you will see that: $leap = $year % 4 == 0; // centennials are only leap years if they are multiples of 400 if ($year % 100 == 0 && $year % 400 != 0) $leap = false; (that boils down to somthing simpler) 2000 was definitely a leap year. --Wez. On 26/07/01, "An

Re: [PHP-DEV] Fwd: [PHP-CVS] cvs: php4(PHP_4_0_5) /ext/standard array.c

I see it in RC7. On Tue, 24 Apr 2001, Andi Gutmans wrote: > Looks like it got merged before RC7. > Can you check if your source includes this fix? > > >From: "Andrei Zmievski" <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Date: Mon, 02 Apr 2001 16:12:07 - > >Subject: [PHP-CVS] cvs: php4(PH

Re: [PHP-DEV] [Fwd: [PHP-QA] security patches against 4_0_5]

It made it into RC3 (looked ok to me) At 19:24 28/3/2001, André Langhorst wrote: >Does anyone see a problem with this patch? >-- >· André Langhorstt: +49 331 5811560 · >· [EMAIL PROTECTED] m: +49 173 9558736 · >* PHP Quality Assurance http://qa.php.net * > > >X-Mozilla-Status2:

RE: [PHP-DEV] Fwd

Well, maybe someone could deny access to mailing list for his email adress? the only thinks he postet has been this letter... (in php-dev and php-pear) Peter Petermann >-Original Message- >From: Taylor Silvers [mailto:[EMAIL PROTECTED]] >Sent: Friday, February 23, 2001 3:30 AM >To: [EMAI

Re: [PHP-DEV] [Fwd: Re: [PHP] Howto return multidimensional arraysfrom a PHP module]

I had the same problem. This is, how I managed to do this: extern "C" int fun1(pval** array) { //this is in c++ //here you generate subarrays - alements are added to the parameter array //this generates an array of strings ... int count=; for (int i=0;ivalue.ht,&arr_el,sizeof(zval**),N

RE: [PHP-DEV] [Fwd: Re: [PHP] Howto return multidimensional arrays from a PHP module]

>I were refered to this list... >I found an old entry in the dev archive, explaining that I could achieve >my goals, by "for each inner array you >allocate a zval*, initialize it, add data to it, and add it to the >return value." >But how exactly do I add a zval? >My guess is add_assoc_resource b

Re: [PHP-DEV] [Fwd: Re: [PHP] Howto return multidimensional arrays from a PHP module]

Hmmm... Can anybody tell me why this mail ended up in this list and not the devel list?? Thomas Wentzel wrote: > > Hi, > > I were refered to this list... > I found an old entry in the dev archive, explaining that I could achieve > my goals, by "for each inner array you > allocate a zval*, init