Re: [PHP-DEV] Unsigned Problems Revisited

On Tuesday 22 October 2002 19:23, Jason T. Greene wrote: > If for some reason we HAVE to have a symmetrical bogus unsigned left > shift operator, and we completely disagree with my arguments on > overloading the HEREDOC operator, then we can implement , =, > . = as the unsigned shif

Re: [PHP-DEV] Re: RFC: CLI behave like SH or PERL/RUBY/PYTHON?

Alan Knowles wrote: (B> To try and clarify... (B> (B> #!/usr/bin/php -q (B> (B> echo "please enter a word"; (B (Bflush(); // is needed here, since above line does not have newline. (B (B> $fh = fopen('php://stdin') (B> $s = fgets($fh,100); (B> echo "you entered $s" ; (B> (B> ?> (B

Re: [PHP-DEV] RFC: CLI behave like SH or PERL/RUBY/PYTHON?

That statement about character devices being line bufffered isn't quite true, but otherwise I would say +0. Line buffering stdout and unbuffering stderr seems to be the default of most languages. On Wednesday, October 23, 2002, at 02:45 AM, Yasuo Ohgaki wrote: George Schlossnagle wrote: No

Re: [PHP-DEV] RFC: CLI behave like SH or PERL/RUBY/PYTHON?

On Wed, Oct 23, 2002 at 03:45:42PM +0900, Yasuo Ohgaki wrote : > Oops. Sorry, I forgot. > It's about flushing output every output statement. > > SH and current CLI does fflush() on stdout with > echo "A" > > while others don't. > And this setting cannot be changed by php.ini. > > User has to pa

Re: [PHP-DEV] RFC: CLI behave like SH or PERL/RUBY/PYTHON?

George Schlossnagle wrote: Not to be snarky, but I for one would prefer PHP to behave like PHP. ;) Without having to make everyone here sort through the commit messages, can you briefly list out the proposed changes? Oops. Sorry, I forgot. It's about flushing output every output statement. S

Re: [PHP-DEV] Re: RFC: CLI behave like SH or PERL/RUBY/PYTHON?

To try and clarify... (B (B#!/usr/bin/php -q (B (B (BWould this be affected by the change? - eg. would you need to flush(); (Bbefore the prompt appeared? (B (BRegards (BAlan (B (B (B (BYasuo Ohgaki wrote: (B (B>BTW, this is 2nd time (B> (B>http://marc.theaimsgroup.com/?l=php-dev&m=

[PHP-DEV] Re: RFC: CLI behave like SH or PERL/RUBY/PYTHON?

BTW, this is 2nd time (B (Bhttp://marc.theaimsgroup.com/?l=php-dev&m=103525481227249&w=2 (B (BYasuo Ohgaki wrote: (B> I thought it's obvious choice, but it seems it's not. (B> (B> Which one you prefer CLI behave like (B> (B> SH (B> (B> or (B> (B> PERL/RUBY/PYTHON (B> (B> -- (B>

Re: [PHP-DEV] RFC: CLI behave like SH or PERL/RUBY/PYTHON?

Not to be snarky, but I for one would prefer PHP to behave like PHP. ;) Without having to make everyone here sort through the commit messages, can you briefly list out the proposed changes? George On Wednesday, October 23, 2002, at 02:26 AM, Yasuo Ohgaki wrote: I thought it's obvious choice,

[PHP-DEV] RFC: CLI behave like SH or PERL/RUBY/PYTHON?

I thought it's obvious choice, but it seems it's not. (B (BWhich one you prefer CLI behave like (B (BSH (B (Bor (B (BPERL/RUBY/PYTHON (B (B-- (BYasuo Ohgaki (B (B (B-- (BPHP Development Mailing List (BTo unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /sapi/cli php_cli.c

Yasuo Ohgaki wrote: Derick Rethans wrote: On Wed, 23 Oct 2002, Yasuo Ohgaki wrote: Jani Taskinen wrote: Again..was this agreed upon? I suppose so. I didn't get any more objections. You got atleast one, and that was mine. I didn't see people agree either. BTW, you haven't repl

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /sapi/cli php_cli.c

Derick Rethans wrote: On Wed, 23 Oct 2002, Yasuo Ohgaki wrote: Jani Taskinen wrote: Again..was this agreed upon? I suppose so. I didn't get any more objections. You got atleast one, and that was mine. I didn't see people agree either. The line was bogus with the current code. D

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /sapi/cli php_cli.c

Andi Gutmans wrote: At 12:20 PM 10/23/2002 +0900, Yasuo Ohgaki wrote: Jani Taskinen wrote: Again..was this agreed upon? I suppose so. I didn't get any more objections. It's not a big deal to me but I don't understand why this should need changing. Who cares what perl does? I don't t

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /sapi/cli php_cli.c

On Wed, 23 Oct 2002, Yasuo Ohgaki wrote: > Jani Taskinen wrote: > > Again..was this agreed upon? > > > > I suppose so. > I didn't get any more objections. You got atleast one, and that was mine. I didn't see people agree either. Derick -- --

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /sapi/cli php_cli.c

Andi Gutmans wrote: At 12:20 PM 10/23/2002 +0900, Yasuo Ohgaki wrote: Jani Taskinen wrote: Again..was this agreed upon? I suppose so. I didn't get any more objections. It's not a big deal to me but I don't understand why this should need changing. Who cares what perl does? I don't t

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /sapi/cli php_cli.c

At 12:20 PM 10/23/2002 +0900, Yasuo Ohgaki wrote: Jani Taskinen wrote: Again..was this agreed upon? I suppose so. I didn't get any more objections. It's not a big deal to me but I don't understand why this should need changing. Who cares what perl does? I don't think there's a right or w

[PHP-DEV] Re: [PHP-CVS] cvs: php4 /sapi/cli php_cli.c

Jani Taskinen wrote: Again..was this agreed upon? I suppose so. I didn't get any more objections. -- Yasuo Ohgaki --Jani On Wed, 23 Oct 2002, Yasuo Ohgaki wrote: yohgaki Tue Oct 22 21:21:40 2002 EDT Modified files: /php4/sapi/cli php_cli.c Log: Make CL

[PHP-DEV] Re: [PHP-CVS] cvs: php4 /sapi/cli php_cli.c

Again..was this agreed upon? --Jani On Wed, 23 Oct 2002, Yasuo Ohgaki wrote: >yohgakiTue Oct 22 21:21:40 2002 EDT > > Modified files: >/php4/sapi/cli php_cli.c > Log: > Make CLI behave like other moder scripting languages. > > >In

[PHP-DEV] Re: Returning non-references still allows access to membervariables?

Regarding the earlier behavior I noticed regarding references: now I've come across something REALLY weird. Check this out: myString = 'hello'; // Test function function testObject() { global $object; // Make a copy of the member variable (no '&') $newStri

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

Jani Taskinen wrote: You propably didn't notice, but this extension is actually deprecated..you should use DBA instead. --Jani Move to PECL or remove? I think move to PECL make sense, since there should be users of db extension. -- Yasuo Ohgaki -- PHP Development Mailing Lis

Re: [PHP-DEV] short_open_tag

At 09:36 22/10/2002, Terence Kearns wrote: Andi Gutmans wrote: At 03:33 PM 10/22/2002 +1000, Terence Kearns wrote: Agreed. If short tags were disabled in v5, then there would be no such need for a hack like this. They won't be disabled. They won't be disabled. They won't be disabled. They

Re: [PHP-DEV] short_open_tag

At 07:33 22/10/2002, Terence Kearns wrote: Agreed. If short tags were disabled in v5, then there would be no such need for a hack like this. Right, we might as well switch to Wake up people, not only are we not going to abandon short tags, we're also not going to change their defaults. We'

Re: [PHP-DEV] short_open_tag

Terence Kearns <[EMAIL PROTECTED]> wrote... : > > > Andi Gutmans wrote: > > > At 03:33 PM 10/22/2002 +1000, Terence Kearns wrote: > > > >> Agreed. > >> > >> If short tags were disabled in v5, then there would be no such need > >> for a hack like this. > > > > > > They won't be disabled. > >

Re: [PHP-DEV] short_open_tag

Terence Kearns <[EMAIL PROTECTED]> wrote... : > >I can see how short_open_tag enabled makes life harder than it should be > >for the XML-using PHP-developer. I fail to see how this can happen in a > >situation where this developer has no control over the appropriate php.ini > >setting, though. >

Re: [PHP-DEV] short_open_tag

Terence Kearns <[EMAIL PROTECTED]> wrote... : > Removing support for the short tag all > tegether would be one major step in making the life of the sys-admin a > whole lot easier. Isn't it just easier to disable short-tags within the .htaccess file if that is really a paranoia of a programmer

Re: [PHP-DEV] Idea to extend language: Explicitly setting variable scope inside user defined function (longer)

Le Lundi 21 Octobre 2002 18:14, NTPT a écrit : > so it have a lot of glue code, that do nothing but only glue together > twoo parts of the program . > if you write a big application, with a lot of queries and function calls, > a lot of the glue code is nedded, that need to be executed, look ug

RE: [PHP-DEV] php_value vs. php_admin_value

> -Original Message- > From: Rasmus Lerdorf [mailto:rasmus@;php.net] > Sent: 21 October 2002 05:49 > > admin directives can only be used in the httpd.conf file. > Non-admins can > be used in both httpd.conf and .htaccess. ie. directives > that end-users > should not be able to change t

[PHP-DEV] Need write access into Zend and TSRM work areas.

Hi, I am working on porting PHP for NetWare. In that process I need to also write into Zend and TSRM work areas. And so, I need write access to these areas. I can write to other areas except these two. Can you give me the write access at the earliest? I need to check-in files soon. I had asked

Re: [PHP-DEV] short_open_tag

Terence Kearns <[EMAIL PROTECTED]> wrote... : > OK, after having read the threads, I know I'm gonna get blasted/flamed, > but I have to say this cos I've spent a lot of time trying to develop > "elegent" XML based solutions in PHP and this issue kills it for me > every time. So let me appolog

Re: [PHP-DEV] short_open_tag

On Tue, 22 Oct 2002, Terence Kearns wrote: > OK, after having read the threads, I know I'm gonna get blasted/flamed, > but I have to say this cos I've spent a lot of time trying to develop > "elegent" XML based solutions in PHP and this issue kills it for me > every time. So let me appologise i

Re: [PHP-DEV] 4.2.3pre1

On 21 Oct 2002, Tony Bibbs wrote: > All this on a Dell Inspiron 5000 running RH7.3. I compiled PHP apache > module just fine. Compiling it as a CGI I get: > > gcc: sapi/cli/php_cli.o: No such file or directory > gcc: sapi/cli/getopt.o: No such file or directory > > This a bug or did I miss som

[PHP-DEV] Re: [PHP-CVS] cvs: php4 / README.TESTING /ext/skeleton/tests 001.phpt

Shouldn't we remove tests/Readme? The documentation is done in README.TESTING now. marcus At 11:00 22.10.2002, Marcus Börger wrote: helly Tue Oct 22 05:00:53 2002 EDT Modified files: /php4 README.TESTING /php4/ext/skeleton/tests001.phpt Log: Update documentatio

Re: [PHP-DEV] short_open_tag

Kristian Koehntopp wrote: On Tuesday 22 October 2002 09:17, Terence Kearns wrote: Ideally this is true, but as so many poeple have pointed out, not every developer has access to the ini file on their ISPs server. Indeed, maintaining a php.ini file is already a nightmare for ISP hosting to un

Re: [PHP-DEV] short_open_tag

On Tuesday 22 October 2002 09:17, Terence Kearns wrote: > Ideally this is true, but as so many poeple have pointed out, not every > developer has access to the ini file on their ISPs server. Indeed, > maintaining a php.ini file is already a nightmare for ISP hosting to > unspecified groups PHP user

Re: [PHP-DEV] Work is beginning on cURL and PHP again

At 07:14 10/22/2002 +0200, Andi Gutmans wrote: Well, the reason for the generator, is it will build an extension that mimics the current version of cURL installed which will allow the cURL extension to support multiple versions of the library without a lot of maintanence and stuff :) Don't forg

Re: [PHP-DEV] short_open_tag

Shane Caraveo wrote: Brad LaFountain wrote: It would be very bad for php if short tags were disabled. I 100% agree with andi. There are ways of dealing with xml and php without pissing off the WHOLE php user world. I don't even use long tags EVER, nor will I want to start. - Brad Damn, that

Re: [PHP-DEV] PHP 5.0 + XML

Guenther Roith wrote: Hello! I'm new to this list, so I don't know if the topic has already be discussed. A big problem for me is, that many ISPs have the XML extension not installed, preventing me from using it. If you don't have you're own server you never can be sure if XML works or not.

Re: [PHP-DEV] inplicit_flush off

Yasuo Ohgaki wrote: Derick Rethans wrote: On Tue, 22 Oct 2002, Yasuo Ohgaki wrote: CLI should behave like other *modern* scripting language. i.e. behave like perl, ruby, python. Currently it behaves like sh. i.e. flushing stdout for every output. Like it *should*. Please don't start agai

Re: [PHP-DEV] short_open_tag

Andi Gutmans wrote: At 03:33 PM 10/22/2002 +1000, Terence Kearns wrote: Agreed. If short tags were disabled in v5, then there would be no such need for a hack like this. They won't be disabled. They won't be disabled. They won't be disabled. They won't be disabled. They won't be disabled.

[PHP-DEV] CVS Account Request: fanatik

Hi friends ! What about a Slovak version of PHP documentation ? I am ready for translation, when it is possible ... -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] CVS Account Request: thekid

Maintain ext/sybase_ct/ - see http://bugs.php.net/bug.php?id=16960 and mails on php-dev. The patches made have been running since Sept. 27th 2002 on three Debian boxes w/ PHP4.2.2, serving a total of 70 million HTTP requests and approx. 100'000 SQL queries without any problem. I guess you could

Re: [PHP-DEV] inplicit_flush off

Derick Rethans wrote: On Tue, 22 Oct 2002, Yasuo Ohgaki wrote: CLI should behave like other *modern* scripting language. i.e. behave like perl, ruby, python. Currently it behaves like sh. i.e. flushing stdout for every output. Like it *should*. Please don't start again on this issue, it is