On Fri, Jun 1, 2012 at 12:51 PM, Marco Behnke wrote:
Ah, I guess that is the problem. Your application framework uses namespaces.
> I guess you should try
>
> catch (\Exception $e)
>
> instead of
>
> catch (Exception $e)
>
> :-)
>
Ah, that was probably it. Will try it out tonight to confirm. T
Am 01.06.12 17:08, schrieb James Colannino:
>
> Hey Marco,
>
> Thanks for the reply! That was the first thing I checked.
>
> class Database_Exception extends \FuelException {}
> class Fuel_Exception extends \Exception {}
>
> It's extending Exception, as expected. Also, can you throw classes
> tha
Maybe "catch(Exception $e)" should be "catch(\Exception $e)"?
On Fri, Jun 1, 2012 at 5:25 PM, James Colannino wrote:
> Hey guys,
>
> Haven't posted in a long time... Happy Memorial Day! I have an issue with
> exception handling. I'm using a framework that throws a
> "Database_Exception" object
-Original Message-
From: James Colannino [mailto:crankycycl...@gmail.com]
Sent: Friday, June 01, 2012 11:14 AM
To: PHP-General List
Subject: Re: [PHP] Exception Handling
Hey Mike,
Thanks for the reply! I saw this comment in the documentation
(http://www.php.net/manual/en
On 06/01/12 07:32, Mackintosh, Mike wrote:
Hi James,
You would have to catch Database_Exception. It is also good practice to
also always catch exception afterwards.
Hey Mike,
Thanks for the reply! I saw this comment in the documentation
(http://www.php.net/manual/en/language.exceptions.ext
On 06/01/12 08:08, James Colannino wrote:
On 06/01/12 07:30, ma...@behnke.biz wrote:
James Colannino hat am 1. Juni 2012 um 16:25
geschrieben:
Hey guys,
Haven't posted in a long time... Happy Memorial Day! I have an issue
with exception handling. I'm using a framework that throws a
"Databa
On 06/01/12 07:30, ma...@behnke.biz wrote:
James Colannino hat am 1. Juni 2012 um 16:25
geschrieben:
Hey guys,
Haven't posted in a long time... Happy Memorial Day! I have an issue
with exception handling. I'm using a framework that throws a
"Database_Exception" object. I was expecting catc
-Original Message-
From: James Colannino [mailto:crankycycl...@gmail.com]
Sent: Friday, June 01, 2012 10:25 AM
To: PHP-General List
Subject: [PHP] Exception Handling
Hey guys,
Haven't posted in a long time... Happy Memorial Day! I have an issue
with exception handling. I'
James Colannino hat am 1. Juni 2012 um 16:25
geschrieben:
> Hey guys,
>
> Haven't posted in a long time... Happy Memorial Day! I have an issue
> with exception handling. I'm using a framework that throws a
> "Database_Exception" object. I was expecting catch (Exception $var) to
> be sufficie
Hey guys,
Haven't posted in a long time... Happy Memorial Day! I have an issue
with exception handling. I'm using a framework that throws a
"Database_Exception" object. I was expecting catch (Exception $var) to
be sufficient to catch this, but it doesn't. I have to do catch
(Database_Exc
Hi all and thanks for Ryan,
I apologize ! !
I have missed out the small class_exists call before it.
Thanks.
Regards,
Eric,
2010/1/29 Ryan
> 于 2010-1-29 13:19, Ashley Sheridan 写道:
> > On Fri, 2010-01-29 at 13:02 +0800, Eric Lee wrote:
> >
> >
> >> Hi php-dev pros,
> >>
> >> I got an issue
On Fri, Jan 29, 2010 at 1:19 PM, Ashley Sheridan
wrote:
> On Fri, 2010-01-29 at 13:02 +0800, Eric Lee wrote:
>
> Hi php-dev pros,
>
> I got an issue about catching exception throw from __autoload on php 5.3.1.
>
> The manual state that exception throw from __autoload could be catched with
> try..
于 2010-1-29 13:19, Ashley Sheridan 写道:
> On Fri, 2010-01-29 at 13:02 +0800, Eric Lee wrote:
>
>
>> Hi php-dev pros,
>>
>> I got an issue about catching exception throw from __autoload on php 5.3.1.
>>
>> The manual state that exception throw from __autoload could be catched with
>> try.. catch s
On Fri, 2010-01-29 at 13:02 +0800, Eric Lee wrote:
> Hi php-dev pros,
>
> I got an issue about catching exception throw from __autoload on php 5.3.1.
>
> The manual state that exception throw from __autoload could be catched with
> try.. catch statement same as the normal flow.
>
> But I'can ar
On Fri, 2010-01-29 at 13:02 +0800, Eric Lee wrote:
> Hi php-dev pros,
>
> I got an issue about catching exception throw from __autoload on php 5.3.1.
>
> The manual state that exception throw from __autoload could be catched with
> try.. catch statement same as the normal flow.
>
> But I'can ar
Hi php-dev pros,
I got an issue about catching exception throw from __autoload on php 5.3.1.
The manual state that exception throw from __autoload could be catched with
try.. catch statement same as the normal flow.
But I'can archive that even I have copied the same sample code from the
manual.
cant http://us3.php.net/manual/en/function.set-exception-handler.php be used ?
getMessage());
}
set_exception_handler('exception_handler');
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Lars Nielsen wrote:
Hi,
I am trying to make an exception class that emails the errors to myself.
I have started by using the example by ask at nilpo dot com on
http://dk2.php.net/manual/en/language.exceptions.php.
It work ok but i want it NOT to show the errors on the php-page but only
show t
On Sunday 11 October 2009 6:09:46 pm Tommy Pham wrote:
> Lars,
>
> Here's a pseudo code:
>
> try {
> if (!$valid) {
> throw new Exception("Test failed.");
> } else {
>// do something
> }
> } catch (Exception $e) {
> // set/print a user friendly message to send to output
>
> // se
- Original Message
> From: Lars Nielsen
> To: php-general@lists.php.net
> Sent: Sun, October 11, 2009 2:18:03 PM
> Subject: [PHP] php exception handling
>
> Hi,
>
> I am trying to make an exception class that emails the errors to myself.
> I have started by
Hi,
I am trying to make an exception class that emails the errors to myself.
I have started by using the example by ask at nilpo dot com on
http://dk2.php.net/manual/en/language.exceptions.php.
It work ok but i want it NOT to show the errors on the php-page but only
show the details in the email
On Thu, Jul 16, 2009 at 7:42 AM, David
Otton wrote:
>> If it's catchable, why isn't it caught in my example?
>
> It's not an exception, it's a "fatal error". Fatal errors are caught
> by error handling functions, not by catch blocks.
>
> Consequence of having (at least) two separate error handling
There are many examples of error_handlers at
http://ar.php.net/manual/es/function.set-error-handler.php
The handler only have to cast the error to exception.
YOu can write a simple handler or a fully featured one, but the essence is
the same...
function errorHandler(/*args*/)
{
$e = new Exce
2009/7/15 Weston C :
>
> class A { }
>
> $a = new A(); // Ayn would be proud, right?
>
> try {
> echo "a is ",$a,"\n";
> } catch(Exception $e) {
> echo "\nException Caught: ";
> echo $e, $n;
> }
>
> ?>
>
> This does not run as expected. I'd think that when the i
So, I've got a little piece of code designed to play with catching the
exception that's thrown when an object doesn't have a __toString
method.
This does not run as expected. I'd think that when the implicit string
conversion in the try block hits, the exception would be thrown,
caught by the ca
But it's give a many information using $e->getTrace()
is this correct. If there are several mysql_query then
I can put it as bunch within try block and catch
exception easily.
No, it doesn't give any such information.
1 :
In second approach for every query I have to write
throw new MySQLExcep
On Thu, 2008-02-21 at 21:01 -0800, Prabath Kumarasinghe wrote:
> In second approach for every query I have to write
> throw new MySQLException("My Message"). It's very time
> consuming isn't it?
In order to *be* lazy, you have to *think* lazy...
Don't go and define every single query with an exc
--- Chris <[EMAIL PROTECTED]> wrote:
> Prabath Kumarasinghe wrote:
> > Hi All
> >
> > Recently I'm came across following code snippet
> > regarding exceptions there I'm executing invalid
> query
> > and catch the exception as follows.
> >
> > First Approach
> > -
> -Original Message-
> From: Prabath Kumarasinghe [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 21, 2008 11:19 PM
> To: php-general@lists.php.net
> Subject: [PHP] Exception vs exception
>
> Hi All
>
> Recently I'm came across following code snippet
Prabath Kumarasinghe wrote:
Hi All
Recently I'm came across following code snippet
regarding exceptions there I'm executing invalid query
and catch the exception as follows.
First Approach
---
try{
$result = mysql_query('SELECT * from unknowntable');
}c
Hi All
Recently I'm came across following code snippet
regarding exceptions there I'm executing invalid query
and catch the exception as follows.
First Approach
---
try{
$result = mysql_query('SELECT * from unknowntable');
}catch(exception $e){
echo $e-
On Mon, February 11, 2008 6:34 am, John Papas wrote:
> I need to open a remote file with file() and I would like to put it
> inside a try-catch but as far as I can tell file() does not raise an
> exception if it fails. The following code:
>
> try {
> $data = file('http://myserver.com
2008. 02. 11, hétfő keltezéssel 14.34-kor John Papas ezt írta:
> I need to open a remote file with file() and I would like to put it
> inside a try-catch but as far as I can tell file() does not raise an
> exception if it fails. The following code:
>
> try {
> $data = file('http://m
I need to open a remote file with file() and I would like to put it
inside a try-catch but as far as I can tell file() does not raise an
exception if it fails. The following code:
try {
$data = file('http://myserver.com/myfile.txt');
$date = substr($data, 0);
// ...
That's from memory, so there may be a few errors.
Seems there was. Try this:
class DBException extends Exception {}
try {
$connection = mysql_connect(...);
if (!$connection) {
throw new DBException('Failed to connect to database');
}
// Database exception handling
Does that mean for every exception do we have to write
our custom exception and describe it from our own
message
If you mean "Do I have to write custom exception classes?", the no. You
could just use the PHP Exception class.
Eg.
class DBException extends Exception {}
try {
$
On Thu, 2008-02-07 at 00:20 -0800, Prabath Kumarasinghe wrote:
> Understood, Thanks Paul
>
Pleasure, but please don't top post, it makes it really hard to follow a
thread easily. Most people on this list take time out from their really
busy day jobs to help out, and the more time that everyone
Understood, Thanks Paul
Cheers
Prabath
--- Paul Scott <[EMAIL PROTECTED]> wrote:
>
> On Wed, 2008-02-06 at 23:37 -0800, Prabath
> Kumarasinghe wrote:
> > Does that mean for every exception do we have to
> write
> > our custom exception and describe it from our own
> > message
> >
>
> No, it me
On Wed, 2008-02-06 at 23:37 -0800, Prabath Kumarasinghe wrote:
> Does that mean for every exception do we have to write
> our custom exception and describe it from our own
> message
>
No, it means that when you want to throw a meaningful exception, you
need to type in a message. I mentioned cust
Does that mean for every exception do we have to write
our custom exception and describe it from our own
message
Cheers
Prabath
--- Paul Scott <[EMAIL PROTECTED]> wrote:
>
> On Wed, 2008-02-06 at 23:10 -0800, Prabath
> Kumarasinghe wrote:
> > Is this following code work in PHP if
> mysql_conne
On Wed, 2008-02-06 at 23:10 -0800, Prabath Kumarasinghe wrote:
> Is this following code work in PHP if mysql_connect
> fails.
>
> try{
> mysql_connect('localhost','user','');
>
> }catch(Exception $e){
> echo $e->getMessage();
>
Probably not. I don't think that the mysql functions throw excep
at 22:52 -0800, Prabath
> Kumarasinghe wrote:
> > Hi All
> >
> > I'm little bit confusing with PHP exception
> handling.
> > Could you able to explain how to put try{} and
> > catch(){} in a proper way in PHP. I had already
> read
> > php exception man
On Wed, 2008-02-06 at 22:52 -0800, Prabath Kumarasinghe wrote:
> Hi All
>
> I'm little bit confusing with PHP exception handling.
> Could you able to explain how to put try{} and
> catch(){} in a proper way in PHP. I had already read
> php exception manual but it didn&#
Hi All
I'm little bit confusing with PHP exception handling.
Could you able to explain how to put try{} and
catch(){} in a proper way in PHP. I had already read
php exception manual but it didn't help me to get
exact idea about exception handling in php.
Cheer
On Sat, January 26, 2008 2:43 am, Nathan Rixham wrote:
> way offf topic-ish here..
>
> class destructors, surely they differ from the
> register_shutdown_function in execution style? seeing as one can echo
> /
> do a bit of jiggery pokery before the buffers close.
>
> what exactly is the differ
Nathan Rixham schreef:
way offf topic-ish here..
class destructors, surely they differ from the
register_shutdown_function in execution style? seeing as one can echo /
do a bit of jiggery pokery before the buffers close.
what exactly is the difference?
the problem with destructors is t
way offf topic-ish here..
class destructors, surely they differ from the
register_shutdown_function in execution style? seeing as one can echo /
do a bit of jiggery pokery before the buffers close.
what exactly is the difference?
Richard Lynch wrote:
On Fri, January 25, 2008 1:31 pm, Jo
On Fri, January 25, 2008 1:31 pm, Jochem Maas wrote:
> setup as via register_shutdown_function().
I missed that bit.
Sorry for the noise.
shutdown functions are run outside the normal context of PHP, and need
special care.
Output won't go anywhere, and try/catch won't work, as the bulk of the
P
Richard Lynch schreef:
On Fri, January 25, 2008 4:37 am, Jochem Maas wrote:
I'm getting exceptions thrown without a stackframe. I understand what
this
means but not how it can happen given the following:
I wonder if you can wrap a try/catch around the loading of the
constants and class definit
On Fri, January 25, 2008 4:37 am, Jochem Maas wrote:
> I'm getting exceptions thrown without a stackframe. I understand what
> this
> means but not how it can happen given the following:
I wonder if you can wrap a try/catch around the loading of the
constants and class definitions?
Or you already
Peter Ford schreef:
Jochem Maas wrote:
Jochem Maas schreef:
I'm getting exceptions thrown without a stackframe. I understand what
this
means but not how it can happen given the following:
1. *every* frontend script on the site is wrapped in a try/catch block
2. I have set an exception handler
On Jan 25, 2008 8:43 AM, Jochem Maas <[EMAIL PROTECTED]> wrote:
> Eric Butera schreef:
>
> > On Jan 25, 2008 5:37 AM, Jochem Maas <[EMAIL PROTECTED]> wrote:
> >> I'm getting exceptions thrown without a stackframe. I understand what this
> >> means but not how it can happen given the following:
> >>
Eric Butera schreef:
On Jan 25, 2008 5:37 AM, Jochem Maas <[EMAIL PROTECTED]> wrote:
I'm getting exceptions thrown without a stackframe. I understand what this
means but not how it can happen given the following:
1. *every* frontend script on the site is wrapped in a try/catch block
2. I have s
Jochem Maas wrote:
> Jochem Maas schreef:
>> I'm getting exceptions thrown without a stackframe. I understand what
>> this
>> means but not how it can happen given the following:
>>
>> 1. *every* frontend script on the site is wrapped in a try/catch block
>> 2. I have set an exception handler to du
On Jan 25, 2008 5:37 AM, Jochem Maas <[EMAIL PROTECTED]> wrote:
> I'm getting exceptions thrown without a stackframe. I understand what this
> means but not how it can happen given the following:
>
> 1. *every* frontend script on the site is wrapped in a try/catch block
> 2. I have set an exception
Jochem Maas schreef:
I'm getting exceptions thrown without a stackframe. I understand what this
means but not how it can happen given the following:
1. *every* frontend script on the site is wrapped in a try/catch block
2. I have set an exception handler to dump these so-called uncaught
excepti
I'm getting exceptions thrown without a stackframe. I understand what this
means but not how it can happen given the following:
1. *every* frontend script on the site is wrapped in a try/catch block
2. I have set an exception handler to dump these so-called uncaught exceptions
in the error log
I
On Sun, Dec 04, 2005 at 08:07:48PM +0330, mr php wrote:
> Hello
> Is it good to use exception handling for error handling or I should use only
> for exceptions?
> For example:
> Is it good to throwing user input errors with throw new Exception().
I'm not sure if I understand how you mean by this b
I would recommend keeping error handling and exceptions separate.
On 12/4/05, mr php <[EMAIL PROTECTED]> wrote:
>
> Hello
> Is it good to use exception handling for error handling or I should use
> only
> for exceptions?
> For example:
> Is it good to throwing user input errors with throw new E
Hello
Is it good to use exception handling for error handling or I should use only
for exceptions?
For example:
Is it good to throwing user input errors with throw new Exception().
Thanks
Konference wrote:
> is here somebody who works with PostgreSQL in PHP?
Yes. :-)
> I have a PL/SQL
> function, which can raise an exception. I am not able to catch _only_
> exception error message in PHP. I can parse "Warning: pg_query():
> Query failed: ERROR: Exception error string. in..." but I
Hello,
is here somebody who works with PostgreSQL in PHP? I have a PL/SQL
function, which can raise an exception. I am not able to catch _only_
exception error message in PHP. I can parse "Warning: pg_query():
Query failed: ERROR: Exception error string. in..." but I think, it is
not "clear" solut
Hi,
PHP 5 stable is not on the horizon yet. Someone have any idea how to
emulate (or to be more precise, simulate), this feature in PHP 4 (I
could do it if PHP4 would support macros and "goto", but there are no
such).
Thanks in advance for any suggestion(s).
**
[snip]
I have 4.3.5-dev (Build Dec-22-2003) installed on a W2K Dell Inspiron
7500
and I am getting an error which I don't get with 4.1.1 and 4.3.4. Would
like
to learn how to debug things like that. Here is a dump of Dr. Watson:
[/snip]
You will probably want to send this to the PHP developers lis
Hello Gunter,
Saturday, January 10, 2004, 10:06:03 PM, you wrote:
GS> I have 4.3.5-dev (Build Dec-22-2003) installed on a W2K Dell Inspiron 7500
GS> and I am getting an error which I don't get with 4.1.1 and 4.3.4. Would like
GS> to learn how to debug things like that. Here is a dump of Dr. Watso
Usually under Windows when you get a Memory Access Violation its a good indication that your power supply or RAM is on its way out. Is this happening to all apps or only PHP ?
Unfortunately I don't know how to debug using a Dr. Watson dump but I do know of a free memory testing utility cal
I have 4.3.5-dev (Build Dec-22-2003) installed on a W2K Dell Inspiron 7500
and I am getting an error which I don't get with 4.1.1 and 4.3.4. Would like
to learn how to debug things like that. Here is a dump of Dr. Watson:
Application exception occurred:
App: (pid=2228)
When: 1/10/
I think that would be nice to have a try-catch to better control of the
code.
Ovidiu
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 27, 2001 9:09 PM
> To: kevin1; [EMAIL PROTECTED]
> Subject: Re: [PHP] Exception
Addressed to: kevin1 <[EMAIL PROTECTED]>
[EMAIL PROTECTED]
** Reply to note from kevin1 <[EMAIL PROTECTED]> Tue, 27 Feb 2001 08:10:05 -0500
>
> Is there any equivalent to Java's try-catch or Perl's eval{BLOCK}if($@)
> structure in PHP?
No.
There has been some discussion about addi
Is there any equivalent to Java's try-catch or Perl's eval{BLOCK}if($@)
structure in PHP?
--
PHP General 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
Hello,
Is it impolite to ask about when approximately PHP will support Exception
handling ? :)
Thanks !
--
PHP General 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: [
I just compiled apache_1.3.17, mod_perl-1.25 and php-4.0.4pl1.
However, now when I try to start apache, I get the following error:
Fatal System Error: Raise at top of Exception Stack
Where might this error be coming from? Apache? PHP? Some other
PHP extension I might have compile
72 matches
Mail list logo
