Re: [PHP-DEV] please apply ext/java fix for sapi/servlet build onUnix
Committed. --Jani On Thu, 6 Feb 2003, Giuseppe Tanzilli - CSF wrote: ciao, as from subject, please apply this patch to PHP_4_3 branch. It is needed to complete the fix to build sapi/servlet on Unix bye Giuseppe -- - For Sale! - -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] please apply to PHP_4_3 branch: servlet build fix
Hi, Where's the patch? Perhaps the attachment was eliminated by the list program. Try suffixing it with .txt or inlining it. Thanks Moriyoshi Giuseppe Tanzilli - CSF [EMAIL PROTECTED] wrote: hi, committed some fixes to build the servlet sapi, but have no permission to commit this small fix, please apply to 4_3 branch thanks a log Giuseppe -- --- Giuseppe Tanzilli [EMAIL PROTECTED] CSF Sistemi srl phone ++39 0775 7771 Via del Ciavattino Anagni FR Italy -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please help document headers_sent()
Hi Philip,
I think the idea is that you do this:
if (headers_sent($file, $line)) {
echo headers were sent by $file:$line;
}
Both $file and $line are optional.
--Wez.
On 06/11/02, Philip Olson [EMAIL PROTECTED] wrote:
Hello-
headers_sent() has two new parameters as of PHP
4.3.0, these are passed in by reference. I see
no need to have to do:
$file = 'file.php';
$line = 4;
headers_sent($file, $line);
When one could simply do this:
headers_sent('file.php', 4);
But we can't, we get this error:
Fatal error: Only variables can be passed by reference
This doesn't seem important, forcing one to use
variables here seems odd, why? Yes is in the
proto but afaict it shouldn't be.
On a related note, I tried and failed to return
anything other then 1 while using these optional
parameters. I can't even tell if it's reading
the file. If someone could explain a little more
that would be very cool.
Regards,
Philip
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please help document headers_sent()
On Wed, 6 Nov 2002, Wez Furlong wrote:
if (headers_sent($file, $line)) {
echo headers were sent by $file:$line;
}
[snip]
Hello Wez-
Ahh, that makes sense. I was a little off
base on that one! :) Will add an example now.
Regards,
Philip
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please help document headers_sent()
I get a Segmentation fault with this script using
PHP CLI:
?php
headers_sent($file, $line);
?
philiprock:~$ php test.php
Segmentation fault
That's when no headers are sent before the call. But if
headers are sent beforehand, it works:
?php
print foo\n;
headers_sent($file, $line);
print $file : $line\n;
?
philiprock:~$ php test.php
foo
test.php : 2
With a fairly (a few weeks old) version of PHP CLI.
I am unable to do further tests at this time, in fact,
I am unable to build HEAD (it dies). Only CLI seems
to be affected, CGI works either way. Haven't
tested mod.
Regards,
Philip Olson
P.s. If no headers were sent, in CGI, $line gets
the value int 0. $file is an empty string.
On Wed, 6 Nov 2002, Philip Olson wrote:
On Wed, 6 Nov 2002, Wez Furlong wrote:
if (headers_sent($file, $line)) {
echo headers were sent by $file:$line;
}
[snip]
Hello Wez-
Ahh, that makes sense. I was a little off
base on that one! :) Will add an example now.
Regards,
Philip
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please help document headers_sent()
Anyway to get a gdb backtrace please?
--
M.CHAILLAN Nicolas
[EMAIL PROTECTED]
www.WorldAKT.com Hébergement de sites internets.
Philip Olson [EMAIL PROTECTED] a écrit dans le message de news:
[EMAIL PROTECTED]
I get a Segmentation fault with this script using
PHP CLI:
?php
headers_sent($file, $line);
?
philip@rock:~$ php test.php
Segmentation fault
That's when no headers are sent before the call. But if
headers are sent beforehand, it works:
?php
print foo\n;
headers_sent($file, $line);
print $file : $line\n;
?
philip@rock:~$ php test.php
foo
test.php : 2
With a fairly (a few weeks old) version of PHP CLI.
I am unable to do further tests at this time, in fact,
I am unable to build HEAD (it dies). Only CLI seems
to be affected, CGI works either way. Haven't
tested mod.
Regards,
Philip Olson
P.s. If no headers were sent, in CGI, $line gets
the value int 0. $file is an empty string.
On Wed, 6 Nov 2002, Philip Olson wrote:
On Wed, 6 Nov 2002, Wez Furlong wrote:
if (headers_sent($file, $line)) {
echo headers were sent by $file:$line;
}
[snip]
Hello Wez-
Ahh, that makes sense. I was a little off
base on that one! :) Will add an example now.
Regards,
Philip
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please help document headers_sent()
On November 6, 2002 07:10 pm, Philip Olson wrote:
I get a Segmentation fault with this script using
PHP CLI:
?php
headers_sent($file, $line);
?
philiprock:~$ php test.php
Segmentation fault
That's when no headers are sent before the call. But if
headers are sent beforehand, it works:
The crash has been fixed in the CVS. PHP CLI cannot send any headers because
it is not ment for a webserver enviroment. While CGI, is mostly geared
towards web servers and by default will try to send headers.
Ilia
?php
print foo\n;
headers_sent($file, $line);
print $file : $line\n;
?
philiprock:~$ php test.php
foo
test.php : 2
With a fairly (a few weeks old) version of PHP CLI.
I am unable to do further tests at this time, in fact,
I am unable to build HEAD (it dies). Only CLI seems
to be affected, CGI works either way. Haven't
tested mod.
Regards,
Philip Olson
P.s. If no headers were sent, in CGI, $line gets
the value int 0. $file is an empty string.
On Wed, 6 Nov 2002, Philip Olson wrote:
On Wed, 6 Nov 2002, Wez Furlong wrote:
if (headers_sent($file, $line)) {
echo headers were sent by $file:$line;
}
[snip]
Hello Wez-
Ahh, that makes sense. I was a little off
base on that one! :) Will add an example now.
Regards,
Philip
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please help document headers_sent()
On Wed, 6 Nov 2002, Ilia A. wrote: On November 6, 2002 07:10 pm, Philip Olson wrote: I get a Segmentation fault with this script using PHP CLI: ?php headers_sent($file, $line); ? philiprock:~$ php test.php Segmentation fault That's when no headers are sent before the call. But if headers are sent beforehand, it works: The crash has been fixed in the CVS. PHP CLI cannot send any headers because it is not ment for a webserver enviroment. While CGI, is mostly geared towards web servers and by default will try to send headers. Okay cool. I just built from CVS and can confirm it has been fixed :) This time I used --enable-debug too ;) I couldn't build from HEAD yesterday but it's okay today. Regards, Philip -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please forward to the list, I'm not a member anymore... (fwd)
On Tue, Apr 16, 2002 at 02:07:01PM +0200, Derick Rethans wrote: -- Forwarded message -- The homepage of Panda PDF is: http://www.stillhq.com/cgi-bin/getpage?area=pandapage=index.htm It offers a spec, the features are reasonable, the license is: ? It is GPL Uwe -- MMK GmbH, Hagen [EMAIL PROTECTED] Tel: +2331 987 4528Fax: +2331 987 375 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please forward to the list, I'm not a member anymore...(fwd)
On Tue, 16 Apr 2002, Uwe Steinmann wrote: On Tue, Apr 16, 2002 at 02:07:01PM +0200, Derick Rethans wrote: -- Forwarded message -- The homepage of Panda PDF is: http://www.stillhq.com/cgi-bin/getpage?area=pandapage=index.htm It offers a spec, the features are reasonable, the license is: ? It is GPL Then we can't use it with PHP... -\- David Eriksson -/- I personally refuse to use inferior tools because of ideology. - Linus Torvalds -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please forward to the list, I'm not a member anymore... (fwd)
Morning, It is GPL Then we can't use it with PHP... sorry, but I do not see your point. How can optional support for a GPL library in PHP violate the GPL? Stefan Esser -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please forward to the list, I'm not a member anymore... (fwd)
I don't know if it's so much a violation of the GPL as it is a clash with PHP's license, which is basically BSD-like. The whole point of the PHP license is that you can basically use PHP without restriction, commercial or otherwise. The GPL doesn't allow that. But I'm just guessing here. It feels kind of like when OpenBSD removed it's ipf code because it wasn't under an OpenBSD-ish license. J Stefan Esser wrote: Morning, It is GPL Then we can't use it with PHP... sorry, but I do not see your point. How can optional support for a GPL library in PHP violate the GPL? Stefan Esser -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please Add my Patch: ext/xslt/sablot.c
Applied, thx. -- Please always Cc to me when replying to me on the lists. GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Please check this one for math.c -Protos/ BUG or FEATURES?
From: Wolfgang Drews [EMAIL PROTECTED]
tonight i read some math.c-source, and stumbled over some things,
that appeared a little strange to me. Please have a look at the
following list. If you are the opinion, that i should make a bug-
report for this ones, i will do. If you can fix it without a
report,
i will be even more happy (will save my time :))I have tested the
described behavior on a redhat 7.1 with php-4.2.0 dev.
- PROTO-change:abs():
-- /* {{{ proto int abs(int number)
++ /* {{{ proto mixed abs(mixed number)
There have been a discussion which return type is correct. IMHO it
should be the main return type. But for abs() mixed is correct,
because you can calculate abs from int and floats.
There should be more explanations in CODING_STANDARDS.
-Egon
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] Please check this one for math.c -Protos/ BUG or FEATURES?
There have been a discussion which return type is correct. IMHO it should be the main return type. But for abs() mixed is correct, because you can calculate abs from int and floats. There should be more explanations in CODING_STANDARDS. hehe, is this a wish or ... ? Btw. CODING_STANDARDS ... is that the file where no coder ever reads the documentation-part?? *g* I just would like to point you to an email of mine, that noone really took care of, or (Yes Markus, please do not reply to this one, i do not want to read any jokes from you now): http://marc.theaimsgroup.com/?l=php-devm=100964700118393w=2 Anyway, i know, you all have lot of stuff to do ;) with best regards, -Wolfgang -- Deutscher PHP-Knotenpunkt Dynamic Web Pages: http://www.dynamicwebpages.de Scripte, Tutorials, Installation, Bücher, BestofGML, Manual, Links uvm. PHP 4: Dynamische Webauftritte professionell realisieren: http://php-buch.de -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] Please..
As I wrote in my last email, what are those issues -- it would be nice to have them outlined in a comprehensible manner instead of, as now, they being implicitly refered to in various snide comments. A lot of people may have an opinion on these issues, and unless they know what they are, there cannot be a semi-democratic, let alone open way to discuss them. +1. True. This old chestnut's been going on for so long it would be nice to see a clear, concise, opinion free and inflammatory remark free description of the issues involved. Hopefully this wouldn't stir things up *again* and might even result in some sort of positive(ish) step forward. Ugh, I'm beginning to sound like a marriage counsellor or something... JP. -- John Parker email: [EMAIL PROTECTED] Internet Project Manager/Software Engineer web:www.itchannel.net itCHANNEL International Ltd. tel: +44 (0) 1202 291939 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
David Hjortsoe wrote: Hi, I'm more than welcome to accomidate you, and Zend, so we can get these issues resolved instead of having these constant bad feelings. As I wrote in my last email, what are those issues -- it would be nice to have them outlined in a comprehensible manner instead of, as now, they being implicitly refered to in various snide comments. What I would like to know, (even though I've been trying to play it cool since my MySQL rant, and getting into it with Zend and sas a bit back...) 1. If the relationship between Zend Tech and PHP becomes irreconcilable, can PHP and Zend fork and/or recover in some other means? Is there an 'escape plan', or is this a death-spiral, where degrading communications could actually kill one or both? 2. If all of the current PHP and Zend core developers die in a fire at a convention, can the codebase continue, or will the ZE possibly become the property of somebody who could demand $1,500 (USD) per server for licensing, and lock down the source, thus killing PHP and Zend? 3. Is the Zend license preventing useful submissions from people who write damn good code, but are FSF believers/zealots, so they refuse to contribute, because it doesn't have the RMS seal of approval? 4. If an alternate engine was written, would it be possible to use with PHP? Could an engine be written from Zend code, or would it have to be clean-room code, and if so, from what version of PHP? 5. If, say, Microsoft beats Zeev and Andi in a Redmond basement for three weeks, until they sign away all rights with bloody, mangled hands, can PHP go forward, or does it have to back up? (See the tim robbins antitrust movie... he becomes a software giant through artful purchasing, and the occasional assasination...) 6. If a core member goes insane, can they damage PHP without being held in check somehow? If half the core dies, is it distributed enough that the other half can continue? Core to the license debate: 7. Can the Q license currently used be adapted to meet the needs/fears of GPL/BSD and similar folks, without compromising the Zend Tech needs for having a saleable product? (there's quite a few licenses out there...) from what I understand, Stallman's complaint are the credits clauses, others are worried about selling closed source (ironically, isn't a Zend package designed specifically for this pupose?) Core to the debate debate: 8. Do some people just need to shoot off some steam, and accomodate others who do? I get 1000+ emails a day, this is nothing in comparison. Of course, I also go days without reading certain lists, which helps. :-) Rasmus, Zeev and Andi are not eternal, neither is PHP or Zend. Planning now, however, makes the future easier. Some folks live in volatile parts of the world about to go to war, :-) , some do not. Some take breathers when they are angered, some do not. So I'm interested in how PHP survives everything from worst case to best case... it seems bulletproof, in code terms, because the Q license allows at least one form of forking, if not several. Having now re-read the Q license a few times, the PHP license a few times, this seems unrelated to licensing, and more related to mindshare or the power fluctuations of a given group, or reactionary impulse to Zend being part commercial, part free. Even in worst case, PHP could recover in months to a year or so, with the hardest part being the social damage of bitter debate, or a focus entirely on an engine rewrite. I dunno. ANy lawyers on the list? Anyways, I'm off to go play in the SF bay now. Have fun, folks! -Bop -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
As you know, most of your questions were hypothetical. I tried to answer them and take them seriously, even if they weren't very likely or serious :) At 11:05 16-08-01, Ron Chmara wrote: 1. If the relationship between Zend Tech and PHP becomes irreconcilable, can PHP and Zend fork and/or recover in some other means? Yes. 2. If all of the current PHP and Zend core developers die in a fire at a convention, can the codebase continue, or will the ZE possibly become the property of somebody who could demand $1,500 (USD) per server for licensing, and lock down the source, thus killing PHP and Zend? No. 3. Is the Zend license preventing useful submissions from people who write damn good code, but are FSF believers/zealots, so they refuse to contribute, because it doesn't have the RMS seal of approval? Yes. So does the PHP license, though, and many other licenses, like the ASF license. 4. If an alternate engine was written, would it be possible to use with PHP? Could an engine be written from Zend code, or would it have to be clean-room code, and if so, from what version of PHP? Obviously, other engines can be written. I was involved in writing two such engines in the past. Because parts in PHP are very tightly coupled with the engine infrastructure, it would have to be very similar to the existing engine, to a degree that makes it kind-of dumb to do in the first place. I'm not a lawyer, but I guess that if you were to call it your own, and release it under a different license, you would have to write it from scratch. 5. If, say, Microsoft beats Zeev and Andi in a Redmond basement for three weeks, until they sign away all rights with bloody, mangled hands, can PHP go forward, or does it have to back up? (See the tim robbins antitrust movie... he becomes a software giant through artful purchasing, and the occasional assasination...) They tried to, but we fought back bravely ;) What you make of this question depends on what you think our contribution is to the project. From a legal standpoint, it can go on just fine, we just won't be in the work force. 6. If a core member goes insane, can they damage PHP without being held in check somehow? If half the core dies, is it distributed enough that the other half can continue? Being a member of the PHP Group doesn't buy you too much nowadays. Core to the license debate: 7. Can the Q license currently used be adapted to meet the needs/fears of GPL/BSD and similar folks, without compromising the Zend Tech needs for having a saleable product? (there's quite a few licenses out there...) from what I understand, Stallman's complaint are the credits clauses, others are worried about selling closed source (ironically, isn't a Zend package designed specifically for this pupose?) I *really* don't care about Stallman specifically, or about GPL compatibility. I'm a strong supporter of the BSD style license, and if the Zend Engine license changes, chances are it will be to a BSD license, like PHP's. Core to the debate debate: 8. Do some people just need to shoot off some steam, and accomodate others who do? I get 1000+ emails a day, this is nothing in comparison. Of course, I also go days without reading certain lists, which helps. :-) I'll leave that one to somebody else :) Rasmus, Zeev and Andi are not eternal, neither is PHP or Zend. Planning now, however, makes the future easier. Some folks live in volatile parts of the world about to go to war, :-) , some do not. Some take breathers when they are angered, some do not. So I'm interested in how PHP survives everything from worst case to best case... it seems bulletproof, in code terms, because the Q license allows at least one form of forking, if not several. Right. Having now re-read the Q license a few times, the PHP license a few times, this seems unrelated to licensing, and more related to mindshare or the power fluctuations of a given group, or reactionary impulse to Zend being part commercial, part free. Even in worst case, PHP could recover in months to a year or so, with the hardest part being the social damage of bitter debate, or a focus entirely on an engine rewrite. I dunno. ANy lawyers on the list? At least you read it and tried to understood it, which is more than what the average person does... Anyways, I'm off to go play in the SF bay now. Have fun, folks! Have fun, Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
Having now re-read the Q license a few times, the PHP license a few times, this seems unrelated to licensing, and more related to You might want to reread the QPL then. The important point is clause 3 which prohibits distributing changes, unless they are provided as patches. This is highly unpractical, because it even does not permit you to run a CVS server where something simple as browsing the CVS using Chora or doing a checkout would already constitute distributing the changes. So, any source-code which is under the QPL will hardly become a source for further external development, because the changes are unmaintainable. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
2. If all of the current PHP and Zend core developers die in a fire at a convention, can the codebase continue, or will the ZE possibly become the property of somebody who could demand $1,500 (USD) per server for licensing, and lock down the source, thus killing PHP and Zend? .oO(what is your plan? ;) well, since the rights of use of the zend engine are allready there, no one could say now you have to pay 1,500 U$. 3. Is the Zend license preventing useful submissions from people who write damn good code, but are FSF believers/zealots, so they refuse to contribute, because it doesn't have the RMS seal of approval? yes 4. If an alternate engine was written, would it be possible to use with PHP? Could an engine be written from Zend code, or would it have to be clean-room code, and if so, from what version of PHP? yes it could be used, and no, you couldnt use Zend Engine as Base for that. 5. If, say, Microsoft beats Zeev and Andi in a Redmond basement for three weeks, until they sign away all rights with bloody, mangled hands, can PHP go forward, or does it have to back up? (See the tim robbins antitrust movie... he becomes a software giant through artful purchasing, and the occasional assasination...) the license for the of ZE with PHP is giving rights to the community, noone is able to take them away, if ZE would be sold bei Zend, the new owner could make a license wich gives more rights to community, but not one which gives less... 6. If a core member goes insane, can they damage PHP without being held in check somehow? If half the core dies, is it distributed enough that the other half can continue? if someone where able to erase all copys of the CVS and the PHP Source and... see every CD where PHP is on, every copy of the source that is anywhere is a backup copy of PHP... Core to the license debate: 7. Can the Q license currently used be adapted to meet the needs/fears of GPL/BSD and similar folks, without compromising the Zend Tech needs for having a saleable product? (there's quite a few licenses out there...) from what I understand, Stallman's complaint are the credits clauses, others are worried about selling closed source (ironically, isn't a Zend package designed specifically for this pupose?) there are more reasons like this, there have a lot of discussions here, on meetings, and on LinuxTag in Stuttgart. the License will not change right now, maybe in Future.. but, we should give some time to Zend to think about. If every day (and by now it is nearly everyday) there is a discussion about i wouldnt change the license too. hey, give them some time.. btw: Zeev? what License will ZE2.. ;) Core to the debate debate: 8. Do some people just need to shoot off some steam, and accomodate others who do? I get 1000+ emails a day, this is nothing in comparison. Of course, I also go days without reading certain lists, which helps. if some discussions get this hot like the discussions here, it is just natural that there is a lot of steam ;) Peter Petermann -- *ZIMT - where PHP meets needs* www.cyberfly.net - [EMAIL PROTECTED] www.phpug.de - [EMAIL PROTECTED] www.php-center.de - [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
At 13:19 16-08-01, Sascha Schumann wrote: Having now re-read the Q license a few times, the PHP license a few times, this seems unrelated to licensing, and more related to You might want to reread the QPL then. The important point is clause 3 which prohibits distributing changes, unless they are provided as patches. This is highly unpractical, because it even does not permit you to run a CVS server where something simple as browsing the CVS using Chora or doing a checkout would already constitute distributing the changes. So, any source-code which is under the QPL will hardly become a source for further external development, because the changes are unmaintainable. From the annotated license: Any technique is acceptable for keeping changes separate - generally, you would have to mark changes very clearly for them to be separate. We don't want to hard-code the idea that the form must be patches. http://www.trolltech.com/products/download/freelicense/annotated.html (this is not an encouragement to make you fork, just pointing out that you're wrong). Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
From the annotated license: Any technique is acceptable for keeping changes separate - generally, you would have to mark changes very clearly for them to be separate. We don't want to hard-code the idea that the form must be patches. And that is exactly what they did. They explicitly suggest using patches. You are not safe to use anything else, because the interpretation of 'separateness' can differ from court to court. While courts usually listen to a license author's interpretation, the wording here needs improvements in order to meet the meaning of the Annotated License..As Applied To The Qt Free Edition Version 2.0. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
At 13:39 16-08-01, Sascha Schumann wrote: From the annotated license: Any technique is acceptable for keeping changes separate - generally, you would have to mark changes very clearly for them to be separate. We don't want to hard-code the idea that the form must be patches. And that is exactly what they did. They explicitly suggest using patches. You are not safe to use anything else, because the interpretation of 'separateness' can differ from court to court. While courts usually listen to a license author's interpretation, the wording here needs improvements in order to meet the meaning of the Annotated License..As Applied To The Qt Free Edition Version 2.0. Could be. Chances are that with the company who wrote the license explaining what it meant the way it did, it'll be an uphill battle to fight against it. Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
ZS Any technique is acceptable for keeping changes separate - generally, you ZS would have to mark changes very clearly for them to be separate. We don't ZS want to hard-code the idea that the form must be patches. ZS ZS http://www.trolltech.com/products/download/freelicense/annotated.html Actually, CVS branch fits rather nicely here, if one was talking about CVS. -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
On Wed, 15 Aug 2001, Jani Taskinen wrote: Can you guys give up these childish fights and just code? Telling people to just shut up will not resolve the issues which many of us think have to be addressed (regardless of how profane your language becomes). It is very unlikely that the bickering will stop, if a single company continues to exercise so much control over the future of an open system such as PHP. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
At 13:06 15-08-01, Jani Taskinen wrote: p.s. Zeev, did you forget to tag the Zend / TSRM for 4.0.7 ?? Nah, I even did that last night at 2am... But I got a bug report in the CGI that required fixing, and there's some COM patch that should go in before RC1, so RC1 will be delayed in a few hours... Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
At 13:13 15-08-01, Sascha Schumann wrote: On Wed, 15 Aug 2001, Jani Taskinen wrote: Can you guys give up these childish fights and just code? Telling people to just shut up will not resolve the issues which many of us think have to be addressed (regardless of how profane your language becomes). It is very unlikely that the bickering will stop, if a single company continues to exercise so much control over the future of an open system such as PHP. If you feel like bickering, go on bicker and make populist statements as much as you'd like, just let the rest of us do what we're good at, which is developing PHP. Perhaps setting up a separate mailing list like Sterling suggested, a-la [EMAIL PROTECTED] isn't such a bad idea. Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
On Wed, 15 Aug 2001, Jani Taskinen wrote: Instead of continuing this endless thread, do something useful once and go fix some bugs.. Jani, try to chill.. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
If you feel like bickering, go on bicker and make populist statements as much as you'd like, just let the rest of us do what we're good at, which is developing PHP. Perhaps setting up a separate mailing list like Sterling suggested, a-la [EMAIL PROTECTED] isn't such a bad idea. Thanks for proving that you are not interested in a dialogue. That is the usual problem of people who are in charge and who just get too used to their power that the concept of releasing some of their power is too remote to be even considerable. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
Jani Taskinen wrote: Can you guys give up these childish fights and just code? These are not childish fights. And I assume there are some people out there, just like Sascha and Thies, who are waiting to code and contribute the Zend Engine, once the license gets changed. But chaning the license is only one step that Andi and Zeev need to take, IMHO. A second one would be documenting the Zend Engine's internals. And this can only be done properly by Andi and Zeev, since they planned and coded it. Looking at zend_compile.c and zend_execute.c today just gives me the creeps, from a software developer's view: nearly no comments. Of course, I can guess what is done where, since I know a bit on compiler theory. But with a proper documentation, people like Sascha and Thies could start with their work on the engine right away -- without learning (by guessing) how the Zend Engine actually does what it does. While the Zend API could easily be documented, or updated from what's in ZendAPI on cvs.zend.com, from any developer who wrote some PHP extensions, the documentation of the Zend Engine itself and its internals can IMHO only be done by its creators. Haven't you get any pussy lately or what? And this isn't childish now, is it? -- Sebastian Bergmann Measure Traffic Usability http://sebastian-bergmann.de/http://phpOpenTracker.de/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] Please..
Hi, First of all, in the last couple of days I have seen a number of very unconstructive mails being fired off, these simply seem to be people bitching rather than trying to write in a precise and concise way, what their problem is. It is correct that telling people to shut up won't resolve the issue, but apparently theres no agreement on what the issue is. Within the last couple of days there has been a number of different issues all being related to some people fearing that Zend controlling the engine being used in PHP will mean the end of PHP (or something). Does Zend really have control over PHP, and thereby the PHP core language. According to the grant that Zend gave to the PHP Group [1] it says that if PHP decides to modify the ZendEngine (ZE), it has to be done under the QPL 1.0 -- this means that (AFAIK and I am NOT a lawyer) IF there are modifications to the ZE, these MAY be freely distributed as long as the patch/modifications are available to Zend (which they would be anyway since PHP is governed by the PHP OSL) and that we do not modify the license that the ZE is released under. For me this means that no matter what happens to Zend, the PHP Group can, if it wishes to do so, continue to develop the ZE without any restrictions except to keep the ZE under the license that it is currently under, am I missing something? Besides the QPL is (again AFAIK) defined as OpenSource, which garantees us that we can continue to work on it, no matter what Zend decides in the future [2]. So what control does Zend really have? They contribute to the development of PHP with the engine, freely, and generally have also made some of the modules for PHP, and under their license we can still modifyredistribute ZE, and if this is not in PHPs interest then frankly, I don't know what is. Is ZE not an integral part of PHP, because if it isn't, then we have a problem because PHP relies on it, now on the other hand if ZE is a part of PHP why do we need an abstraction layer, doesn't that just tell the folks over at Zend, that: 1) we don't like them. 2) we'd rather have someone else make the engine because we are troubled by license/control/... And if its 2), then let us write exactly what the problem is. Now what is really the issue? HTH. Kind regards, David. [1] Zend Grant: http://www.php.net/license/ZendGrant [2] OSD Definition: http://www.opensource.org/docs/definition_plain.html -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
At 13:43 15-08-01, Sebastian Bergmann wrote: Jani Taskinen wrote: Can you guys give up these childish fights and just code? These are not childish fights. Yes they are. They are on childish topics, lead nowhere and consume lots of our time. And I assume there are some people out there, just like Sascha and Thies, who are waiting to code and contribute the Zend Engine, once the license gets changed. You have absolutely no reason to assume that this is the case, except for the license noise that was spawned by the same people who spawn these pointless threads on php-dev. I believe Hartmut will help documenting the API, but that's about it. But chaning the license is only one step that Andi and Zeev need to take, IMHO. A second one would be documenting the Zend Engine's internals. And this can only be done properly by Andi and Zeev, since they planned and coded it. Looking at zend_compile.c and zend_execute.c today just gives me the creeps, from a software developer's view: nearly no comments. Of course, I can guess what is done where, since I know a bit on compiler theory. But with a proper documentation, people like Sascha and Thies could start with their work on the engine right away -- without learning (by guessing) how the Zend Engine actually does what it does. While the Zend API could easily be documented, or updated from what's in ZendAPI on cvs.zend.com, from any developer who wrote some PHP extensions, the documentation of the Zend Engine itself and its internals can IMHO only be done by its creators. With all due respect, 'you get what you pay for' works as far as documentation goes in open source. Fact is, we don't *need* to do *anything*. Nobody in an opensource project does. What we do we do because it's fun (which these threads do a good job of ruining) and because it's interesting. Not because we have to do it. I never liked writing documentation. I don't think that developers in most other opensource projects are significantly different, neither are most of the other developers in the PHP circle (it's not as if the rest of PHP is too documented... Where are the SAPI docs, or the fopen wrappers docs, or the session docs?). Try to understand the Perl source code, for example. For me, things work just fine the way they are, and I'm not searching for extra stuff to do. If somebody finds the entry level too steep to contribute to the engine, by all means, either try to document it, or go away. Don't say that I *have* to do it, because I don't. Sorry for the somewhat aggressive tone, but it's kind of annoying to see people demanding things from you, when you're a volunteer. Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
At 13:41 15-08-01, Sascha Schumann wrote: If you feel like bickering, go on bicker and make populist statements as much as you'd like, just let the rest of us do what we're good at, which is developing PHP. Perhaps setting up a separate mailing list like Sterling suggested, a-la [EMAIL PROTECTED] isn't such a bad idea. Thanks for proving that you are not interested in a dialogue. If bickering is your definition of dialogue then all I can say is - you're quite welcome! Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] Please..
At 13:53 15-08-01, David Hjortsoe wrote: For me this means that no matter what happens to Zend, the PHP Group can, if it wishes to do so, continue to develop the ZE without any restrictions except to keep the ZE under the license that it is currently under, am I missing something? The only thing you're missing is the point of these threads. They have very little to do with the situation itself, and everything to do with politics. If, God forbid, you only look at the facts - then you're not missing anything. Thanks for providing a rational look! Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
Zeev Suraski wrote: Don't say that I *have* to do it, because I don't. I didn't say that you have to do it. What I meant to make clean was that the best choice of authors for a documentation of a piece of software like the Zend Engine are its inventors. With the Zend Engine this happens to be you and Andi. I did not _demand_ this from you. -- Sebastian Bergmann Measure Traffic Usability http://sebastian-bergmann.de/http://phpOpenTracker.de/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Please..
On Wed, 15 Aug 2001, Zeev Suraski wrote: At 13:41 15-08-01, Sascha Schumann wrote: If you feel like bickering, go on bicker and make populist statements as much as you'd like, just let the rest of us do what we're good at, which is developing PHP. Perhaps setting up a separate mailing list like Sterling suggested, a-la [EMAIL PROTECTED] isn't such a bad idea. Thanks for proving that you are not interested in a dialogue. If bickering is your definition of dialogue then all I can say is - you're quite welcome! What's your definition of dialogue? I'm more than welcome to accomidate you, and Zend, so we can get these issues resolved instead of having these constant bad feelings. The reason I'm speaking out is that its beginning to make PHP something that is no longer enjoyable to develop for -- and the project is important enough to me -- that I'd rather see this resolved to some level than just forget it all together. I would be happy to talk on a temporary list, which could perhaps contain all interested parties -- or all effected parties (invite only, to make it a smaller group). -Sterling Ps: Jani sometimes I feel the same way, but ignore this problem is just going to make it bigger, its been ignored for awhile now, and is slowly causing an explosion. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] Please..
Hi, I'm more than welcome to accomidate you, and Zend, so we can get these issues resolved instead of having these constant bad feelings. As I wrote in my last email, what are those issues -- it would be nice to have them outlined in a comprehensible manner instead of, as now, they being implicitly refered to in various snide comments. A lot of people may have an opinion on these issues, and unless they know what they are, there cannot be a semi-democratic, let alone open way to discuss them. Kind regards, David. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] please remove pgsql warning on fetch_row - includes diff
Heya,
Using your example...
while (@pg_fetch_row()) {
...
}
will suppress the warnings just for the call to pg_fetch_row.
adamw
- Original Message -
From: "Marc Boeren" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, March 26, 2001 10:47 AM
Subject: [PHP-DEV] please remove pgsql warning on fetch_row - includes diff
Hi!
The PostgreSQL module issues a warning when trying to fetch a row with an
invalid rownumber. pg_fetch_row also returns false.
I would ask if someone could remove the warning that is issued. The docs
says the function returns false, this should be enough, I think.
I would really like to construct a while-loop
while (pg_fetch_row()) {
...
}
In fact, in the dbx-module I am doing exactly that, and the postgresql
addition generates the warning even though the loop is ended
successfully...
To make it easier, I attached a diff that removes said warning. I'm not
really sure if this is how a patch is submitted (do you need a diff for
that?), but if I'm doing something wrong maybe anyone can show me how it's
done.
Cheerio, Marc.
pgsql.c.diff
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] please patch for dbmaker
Sorry, some incorrect word wrap in my patch.
Please use the attachment instead.
Thanks.
begin 666 patch.txt
M9EF9B M=7(@AP+30N,"XTPQ;VQD+V5X="]O9)C+V-O;F9I9RYM-"!P
M:' M-"XP+C1P;#$O97AT+V]D8F,O8V]N9FEG+FTT#0HM+2T@AP+30N,"XT
MPQ;VQD+V5X="]O9)C+V-O;F9I9RYM- E7960@3F]V(#(R(#(S.C,Q.C T
M(#(P,# -"BLK*R!P:' M-"XP+C1P;#$O97AT+V]D8F,O8V]N9FEG+FTT"5=E
M9"!96(@,C$@,3(Z,C Z,#$@,C P,0T*0$ @+30P-RPX("LT,#L."! 0 T*
M(" @(" C(-H96-K($1"36%K97(@=F5RVEO;B H9G)O;2 U+C @=\@,BXP
M*0T*(" @("!$0DU!2T527U9%4E-)3TX]-2XP#0H@#0HM(" @('=H:6QE(%M;
M('1EW0@(2 M9" D1$)-04M%4E](3TU%+R1$0DU!2T527U9%4E-)3TX@+6$@
M7 T*+2 @(" @(" @(" @(" @(" @(B1$0DU!2T527U9%4E-)3TXB("$]("(R
M+CDB(%U=.R!D;PT**R @("!W:EL92!T97-T("$@+60@)$1"34%+15)?2$]-
M12\D1$)-04M%4E]615)324].("UA(%P-"BL@(" @(" @(" @(" @(" @("(D
M1$)-04M%4E]615)324].(B A/2 B,BXY(CL@9\-"B @(" @(" @($1-7U9%
M4CU@96-H;R D1$)-04M%4E]615)324].('P@V5D("UE("=S+UPN+R\G('P@
M87=K("=[('!R:6YT("0Q+3$[?2=@#0H@(" @(" @("!-04I/4E]6/6!E8VAO
M("1$35]615(@?"!A=VL@)WL@')I;G0@)#$O,3 [('TG(%P-"B @(" @(" @
M(" @(" @(" @('P@87=K(" M1BX@)WL@')I;G0@)#$[('TG8 T*0$ @+30Q
M-BPW("LT,38L-R! 0 T*(" @(" @(" @1$)-04M%4E]615)324]./21-04I/
M4E]6+B1-24Y/4E]6#0H@(" @(1O;F4-"B -"BT@(" @:68@6UL@(B1$0DU!
M2T527U9%4E-)3TXB(#T@(C(N.2(@75T[('1H96X-"BL@(" @:68@=5S=" B
M)$1"34%+15)?5D524TE/3B(@/2 B,BXY(CL@=AE;@T*(" @(" @(" @=VET
M:'9A;#TD1$)-04M%4E](3TU%#0H@(" @(5LV4-"B @(" @(" @($1"34%+
H15)?4$%42#TD1$)-04M%4E](3TU%+R1$0DU!2T527U9%4E-)3TX-"@``
`
end
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] please patch for dbmaker
The original patch has some incorrect word wrap,
let me post it once again.
Sorry!!
BEGIN PATCH
diff -ur php-4.0.4pl1old/ext/odbc/config.m4 php-4.0.4pl1/ext/odbc/config.m4
--- php-4.0.4pl1old/ext/odbc/config.m4 Wed Nov 22 23:31:04 2000
+++ php-4.0.4pl1/ext/odbc/config.m4 Wed Feb 21 12:20:01 2001
@@ -407,8 +407,8 @@
# check DBMaker version (from 5.0 to 2.0)
DBMAKER_VERSION=5.0
-while [[ test ! -d $DBMAKER_HOME/$DBMAKER_VERSION -a \
- "$DBMAKER_VERSION" != "2.9" ]]; do
+while test ! -d $DBMAKER_HOME/$DBMAKER_VERSION -a \
+ "$DBMAKER_VERSION" != "2.9"; do
DM_VER=`echo $DBMAKER_VERSION | sed -e 's/\.//' | awk '{ print
$1-1;}'`
MAJOR_V=`echo $DM_VER | awk '{ print $1/10; }' \
| awk -F. '{ print $1; }'`
@@ -416,7 +416,7 @@
DBMAKER_VERSION=$MAJOR_V.$MINOR_V
done
-if [[ "$DBMAKER_VERSION" = "2.9" ]]; then
+if test "$DBMAKER_VERSION" = "2.9"; then
withval=$DBMAKER_HOME
else
DBMAKER_PATH=$DBMAKER_HOME/$DBMAKER_VERSION
END PATCH
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] please patch for dbmaker
Jeffrey Lin wrote: Hey, there: We just added some patch to php CVS specifically for our database driver - DBMaker. Please file a bug (http://bugs.php.net) and copy your patch into it to ensure that it does not get overlooked. Thanks. -- Andr Langhorstt: +49 331 5811560 [EMAIL PROTECTED] m: +49 173 9558736 * PHP Quality Assurance http://qa.php.net * -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
