From my current tests I get the following stack:
[23-Dec-2003 01:55:10] PHP Fatal error: Uncaught exception 'exception' with message
'Unable to connect to database; mysql_error = Unknown MySQL Server Host 'bla' (4)' in
/home/mfischer/php/System.php:12
Stack trace:
#0 /home/mfischer/php/Data
I'v wrote a PECL extension with my friend which is wrapper for FreeImage library,
so I need a CVS account and karma for pecl/freeimage.
For more infomation about FreeImage, please visit http://freeimage.sf.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
Hello,
First of all I would like to appologise for possibly being too pedantic, but I
have spotted some typos that might be considered to be fixed.
I was reading http://qa.php.net/write-test.php and I saw that the filename
REATME.TESTING was mentioned in all of the test code examples. I believe
=> /dev/null
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi -
We're using the Reflection API in a project for which I'm lead developer.
Seems to be something changed between beta-2 and beta-3. We're now
getting the following exception when calling getClass() on a class hint:
exception 'reflection_exception' with message 'Class FileSet does not
exist'
On Mon, Dec 22, 2003 at 09:34:38AM -0500, Hans Lellelid wrote:
> This was AFAIK the way to invoke methods in a static class. Perhaps we
> now need to specify classname rather than 'self'.
Just use __CLASS__.
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Developmen
> On Mon, Dec 22, 2003 at 05:32:53AM -0800, David Giffin wrote:
>> I wanted to check if something changed in the preg_replace_callback()
>> function. After going to beta3 we are now not able to make static
>> object/method calls, that were working on beta2. Here is the error
>> message:
>>
>> Warni
On Mon, Dec 22, 2003 at 05:32:53AM -0800, David Giffin wrote:
> I wanted to check if something changed in the preg_replace_callback()
> function. After going to beta3 we are now not able to make static
> object/method calls, that were working on beta2. Here is the error
> message:
>
> Warning: pre
Hi All,
I wanted to check if something changed in the preg_replace_callback()
function. After going to beta3 we are now not able to make static
object/method calls, that were working on beta2. Here is the error
message:
Warning: preg_replace_callback(): requires argument 2,
'self::replacePropert
PHP 5.0 Beta 3 rc 1
new Reflection_Method('','') causes apache2 on windows to crash
szAppName : Apache.exe szAppVer : 2.0.48.0 szModName : php4ts.dll
szModVer : 5.0.0.0 offset : 000c351b
Christian Schneider <[EMAIL PROTECTED]> wrote:
> Moriyoshi Koizumi wrote:
> >> 1) Leave things they way they are now, giving everyone a partial
> >> support for
> >> multibyte string in fgetcsv() and 2-3 performance decrease in all
> >> instances.
> >
> > Of course this is my choice.
>
> I'm n
Dear PHP users,
PHP 5.0.0 Beta 3 has been released. Many bugs have been fixed since Beta 2,
some of which aren't mentioned in the NEWS file (which you can find at the
end of this email).
The PHP 5.0 source tree will now enter a feature freeze and we are moving
into bug fixing mode, therefore, w
At 11:01 AM 12/22/2003 +0100, Christian Schneider wrote:
Andi Gutmans wrote:
Why not make the default catch-all as E_ALL and add to the documentation
that the new E_STRICT option needs to be turned on explicitly?
Just using E_ALL would match error_reporting where the default E_ALL does
not includ
Hello!
Some characters (like [, ], {, } and backslash sequences) in double
quote strings are highlighted as keywords even on places where they
don't have any special meaning (like [] in "foo[] $a"). I mean
highlighted by `php -s` and highlight_* functions.
These characters are not highlighted in
Moriyoshi Koizumi wrote:
1) Leave things they way they are now, giving everyone a partial
support for
multibyte string in fgetcsv() and 2-3 performance decrease in all
instances.
Of course this is my choice.
I'm not sure this is what you want because the words "_partial_ support"
seem to be the
Andi Gutmans wrote:
Why not make the default catch-all as E_ALL and add to the documentation
that the new E_STRICT option needs to be turned on explicitly?
Just using E_ALL would match error_reporting where the default E_ALL
does not include E_STRICT. Including E_STRICT would match the old
docum
development
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
17 matches
Mail list logo