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
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
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
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
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,
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
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
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
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
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
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
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
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
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
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
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,
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
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
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
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
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,
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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,#
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
+++
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
41 matches
Mail list logo
