On 04/11/02, "Darren McPhee" <[EMAIL PROTECTED]> wrote:
> I have spent the last 3 days trying to figure this out. And will probably
> give up very soon. I have written 2 programs (which are very common PHP
Then please spend the extra couple of minutes to read php.net/support.php
and find the cor
I have spent the last 3 days trying to figure this out. And will probably
give up very soon. I have written 2 programs (which are very common PHP
programs) that A) Allows me to upload image files into a MYSQL database
using a simple form. And B) Allows me to retrieve and display the image
using
Hi,
> To php-dev: I feel that Robert has had a bit of a cool reception;
> opensource development relies on positive feedback to make progress.
Sorry that I'm late :)
I too think this is a very nice extension!!! We (nederland.net, hosting
provider in The Netherlands) don't need this yet, but I ex
> So far 3 people have shown interest in ODBTP, however, it is the weekend. I
> am currently working on packaging it in a tar.gz file. If the response is
> low I will only release it to those who have shown an interest, and if it
> becomes higher than I will release it to the list. It is very im
Hi Bob,
I'm interested in this becoming more mainstream, although I personally
dislike mssql; the only current alternative that works in a similar way
is one of the packages that Dan mentioned (I forget which) - it was
difficult to configure as it required quite a large amount of fiddling
around o
Melvyn Sopacua <[EMAIL PROTECTED]> wrote:
> At 19:02 1-11-2002, John Coggeshall wrote:
>
>>I haven't looked at the patch in great detail, can someone forward me
>>The commitlog?
>
> It hasn't been committed yet, as we agreed that only persons in 'Authors'
> should do that and agree, otherwise it'
Yes please commit
At 21:21 03.11.2002, Moriyoshi Koizumi wrote:
The attached patch is a fix for misbehaviour of
OnUpdate_zlib_output_compression. Without this patch, test cases always
fail complaining "Cannot use both zlib.output_compression and
output_handler together!!" when output_handler is u
The attached patch is a fix for misbehaviour of
OnUpdate_zlib_output_compression. Without this patch, test cases always
fail complaining "Cannot use both zlib.output_compression and
output_handler together!!" when output_handler is used.
Any objections?
Moriyoshi
Index: zlib.c
=
> > * Designed to be as easy as possible to use with
> PHP
>
> How committed is your organization to supporting your
> selection of PHP? Have you been involved in any open
> source coding efforts?
>
My organization's committment to PHP is primarily determined by me. I am
the software development
+1
Moriyoshi
[EMAIL PROTECTED] (Marcus Boerger) wrote:
> Maybe we should add those two settings also to the default overwrites
> since you can easily fail all tests by this simple settings and mbstring
> module as well as output buffering are checked elsewhere.
>
> marcus
>
> Index: run-tests.
As i wrote already in another mail nearly all tests are affected by this.
Try a php.ini with
output_handler=mb_string
mbstring.http_output=UCS-2LE
marcus
At 09:42 03.11.2002, Moriyoshi Koizumi wrote:
Forgot to send CC to dev list...
>
Maybe we should add those two settings also to the default overwrites
since you can easily fail all tests by this simple settings and mbstring
module as well as output buffering are checked elsewhere.
marcus
Index: run-tests.php
===
At 09:52 03.11.2002, Edin Kadribasic wrote:
On Saturday 02 November 2002 23:58, Rasmus Lerdorf wrote:
> What do you think would be the best way to make the apache_hooks code more
> accessible to people? A tarball with the relevant files that overwrites
> the standard files, or perhaps it is time
On Saturday 02 November 2002 23:58, Rasmus Lerdorf wrote:
> What do you think would be the best way to make the apache_hooks code more
> accessible to people? A tarball with the relevant files that overwrites
> the standard files, or perhaps it is time to #ifdef it into the main
> branch?
I would
Well, since 99% of the code is the same, I'd be worried about people
remembering to merge fixes across. At least if it is ifdef'ed people see
the code. But yes, I agree, that's not pretty either.
-R
On Sun, 3 Nov 2002, George Schlossnagle wrote:
> Either way works for me. Psychologically, I t
Forgot to send CC to dev list...
> =
> FAILED TEST SUMMARY
> -
> mb_strtoupper() / mb_strtolower() [ext/mbstring/tests/casefold.phpt]
> mb_convert_encoding() [ext
Either way works for me. Psychologically, I think it may get higher
exposure if it is #ifdef'd, but I have style reservations about doing
that. How has this sort of thing been done in the past? Is it
undesirable to fork the apache sapi into a new 'apache_hooks' sapi?
That may be easiest.
G
17 matches
Mail list logo