>
> Perhaps this could be done in userland by throwing an exception in a
> user error_handler... did not test it though...
>
It seems that works! At least for E_WARNING:
class MyException extends Exception
{
function __construct($errno, $errstr, $errfile, $errline)
{
parent::__construct($errst
After I posted my initial message, I thought about references in the
code with "=&". So, I went through looking for them, but I didn't find
any at a quick glance. Still, they could've been in there. I'll check
it out again and see what I can find.
-Ben
Todd Ruth wrote:
I have a feeling tha
> > I have a feeling that PHP has a memory problem somewhere :/.
I'm not sure if it caused any of the issues either of you spoke of,
but I can report that PHP does have some pointer problems. I've
been putting off this email until I had written up something nicer,
but it's probably better to just
Just curious - Did you completely eliminate the Access Violation errors? Or
just make them appear less frequently?
To my knowledge, they're completely eliminated. Previously, I could not
use the PEAR::Mail::smtp class more than once or twice without seeing
the error, and then the error sometimes
I've been told by someone here to pare down my code and submit a bug
report. However, paring down my code corrected the problem, so I'm
still not sure what a PHP Access Violation error is. Following is the
post I made to php-general with my "solution." Am I on the right track
with my guess a
One more release candidate prior to the final release. This RC addresses yet
another ZTS bug that may have resulted in crashes on Win32 (IIS) and Apache 2
while using the worker model. If you are using PHP in those environments,
please try RC3 and see if any problems still occur.
Additionally a
[EMAIL PROTECTED]
From: "Jochem Maas" <[EMAIL PROTECTED]>
> apologies if this is misplaced.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
consider this if you will:
echo <<< ___THEEND
EXPECT:
isset(): true;
is_null(): true;
REALITY:
___THEEND;
$varIsSet = null;
var_dump( isset($varIsSet) );
var_dump( is_null($varIsSet) );
?>
I would have thought that having set the variable to something even if
its 'nothing' would mean it is set
On Thursday 08 April 2004 19.14, Andi Gutmans wrote:
> Was this broken by my latest fix/patch or did it break before that? (I
> commited something yesterday).
It was broken before.
To be honest.. I have no idea when it worked as it should last time. I noticed
it a few days ago (3 or 4 maybe).
>
Andi Gutmans wrote:
Was this broken by my latest fix/patch or did it break before that? (I
commited something yesterday).
This is broken at least since beta 2 or 3, I don't remember when I first
noticed.
Patrick
--
use the source, luke
--
PHP Internals - PHP Runtime Development Mailing List
To
Was this broken by my latest fix/patch or did it break before that? (I
commited something yesterday).
At 11:43 AM 4/8/2004 -0400, Adam Maccabee Trachtenberg wrote:
On Thu, 8 Apr 2004, Magnus [iso-8859-15] Määttä wrote:
> debug_backtrace() used to print out arguments to functions, but does not
>
Does anyone mind if I change the prototypes of
ibase_user_add|modify|delete() to use service resources instead of the
current db/dba_name/dba_password style prototypes ?
I would like to do it before PHP 5.0.0 because it's a BC break.
--
Ard
--
PHP Internals - PHP Runtime Development Mailing Lis
This was changed in PHP 5. Take a look at one of the new PHP 5
OO extensions; sqlite, com_dotnet, mysqli etc. for more hints.
There is no documentation yet.
--Wez.
- Original Message -
From: "Ananth Kesari" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 08, 2004 4:05
On Thu, 8 Apr 2004, Magnus [iso-8859-15] Määttä wrote:
> debug_backtrace() used to print out arguments to functions, but does not
> anymore. Is this desired behavior ?
I discovered this least night and it is already filed as a bug:
http://bugs.php.net/bug.php?id=27397
I'm hoping it's a bug, not
Hi,
I am writing my own PHP Extension called php2ucs to PHP 5.0.
In PHP 4.2.x, we had the following definitions in _zend_class_entry
in zend.h file:
1. Method call:
void (*handle_function_call)(INTERNAL_FUNCTION_PARAMETERS,
zend_property_reference *property_reference);
2. Proper
Firman Wandayandi wrote:
1. I plan to constributing to PHP and PEAR
2. I want to donating my intellectual for the people
3. I want reporting bugs, if I found it.
appearently not needed anymore
regards,
Lukas Smith
[EMAIL PROTECTED]
___
BackendMedia
www.backendmedia
Firman Wandayandi wrote:
Maintaining a package at PEAR
appearently not needed anymore
regards,
Lukas Smith
[EMAIL PROTECTED]
___
BackendMedia
www.backendmedia.com
[EMAIL PROTECTED]
Linn Zwoch Smith GbR
Pariser Str. 44
D-10707 Berlin
Tel +49 30 83 22 50 00
I don't bite, weah!
password -- 78333
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 8 Apr 2004 at 12:18, Wez Furlong wrote:
> > On 8 Apr 2004 at 13:07, Derick Rethans wrote:
> > > NO!
> >
> > That's all, just 'NO!'? :-P
>
> "NO!" is a shortcut for "Read the annoyingly long thread about
> this subject in the archives, please don't start another annoyingly
> long thread about it
Hello
debug_backtrace() used to print out arguments to functions, but does not
anymore. Is this desired behavior ?
Output:
array(1) {
[0]=>
array(3) {
["file"]=>
string(36) "/home/magnus/Projects/base/test4.php"
["line"]=>
int(8)
["function"]=>
string(3) "foo"
}
> On 8 Apr 2004 at 13:07, Derick Rethans wrote:
> > NO!
>
> That's all, just 'NO!'? :-P
>
> Perhaps this could be done in userland by throwing an exception in a
> user error_handler... did not test it though...
"NO!" is a shortcut for "Read the annoyingly long thread about
this subject in the
On 8 Apr 2004 at 13:07, Derick Rethans wrote:
> NO!
>
> Derick
That's all, just 'NO!'? :-P
Perhaps this could be done in userland by throwing an exception in a
user error_handler... did not test it though...
--
Ferdinand Beyer
<[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Development
On Thu, 8 Apr 2004, Tumurbaatar S. wrote:
> Is it not what I'm talking about?
This document is outdated in much more things then only this. Forget
about it.
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, 8 Apr 2004, Ferdinand Beyer wrote:
> On 8 Apr 2004 at 12:45, Derick Rethans wrote:
>
> > > I want to write:
> > > ...
> > > $res = some_builtin_func(); // func raises exception on error
> > > // so I don't need to write additional lines
> > > ...
> > >
> > > So will PHP5 (or futu
"Derick Rethans" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Thu, 8 Apr 2004, Tumurbaatar S. wrote:
>
> > > news:[EMAIL PROTECTED]
> > > > > If I understand right, PHP5 has an exception
> > > > > handling mechanism but it is only for "manual" using, i.e.
> > > > > a programmer
On 8 Apr 2004 at 12:45, Derick Rethans wrote:
> > I want to write:
> > ...
> > $res = some_builtin_func(); // func raises exception on error
> > // so I don't need to write additional lines
> > ...
> >
> > So will PHP5 (or future versions) work as in my 2nd example?
>
> No
It would be
On Thu, 8 Apr 2004, Tumurbaatar S. wrote:
> > news:[EMAIL PROTECTED]
> > > > If I understand right, PHP5 has an exception
> > > > handling mechanism but it is only for "manual" using, i.e.
> > > > a programmer can use try/catch but only for own code.
> > > > PHP's built-in functions and functions
- Original Message -
From: "Tumurbaatar S." <[EMAIL PROTECTED]>
Newsgroups: php.general
Sent: Thursday, April 08, 2004 17:44
Subject: Re: [PHP] Exceptions and builtin functions in PHP5
>
> <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > > If I understand right, PHP5 ha
I'm going to do some win32 build stuff today; it's not urgent, except for
that mbregex thing I mentioned in the past.
--Wez.
- Original Message -
From: "Andi Gutmans" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 08, 2004 10:01 AM
Subject: [PHP-DEV] Rolling RC2RC1
>
Hey,
I'd like to roll . Is there anyone working on something and wants
me to wait?
Andi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
It is obvious my proposal is considered as a very bad idea to most of view
;-)
But my goal is not to ask for a definitive patch for PHP, so I probably made
a mistake by posting the initial message in this mailing list...
I just offer this patch for admins who manage applications developped by
oth
If you want to preserve CVS history, I can do some magic on the CVS machine.
Also note that you need to create a PECL_4_3 branch from the PHP_4_3 branch
of that extension.
Let me know when you're ready.
--Wez.
- Original Message -
From: "Adam Dickmeiss" <[EMAIL PROTECTED]>
To: <[EMAIL P
Hello Christian,
Thursday, April 8, 2004, 8:09:20 AM, you wrote:
> Jochem Maas wrote:
>> I'm happy to just remove the P and add it again if ever that becomes an
>> option.
> Or go for the simpler option: Just don't use P.
> An addition to the documentation of __call saying that it has to be
>
Oops. I'll remove that line again.
- Frank
> Frank M. Kromann wrote:
> > + WScript.StdOut.WriteLine(fc.item());
>
> This looks like debugging code to me. Shouldn't it be removed?
>
> --
> Sebastian Bergmann
> http://sebastian-bergmann.de/
http://phpOpenTracker.de/
34 matches
Mail list logo
