Should exceptions ever be thrown with optional second argument for code?

[NotionCommotion]

http://php.net/manual/en/class.pdoexception.php will also include an extra code in the exception, and this code can be retrieved using http://php.net/manual/en/exception.getcode.php (and http://php.net/manual/en/throwable.getcode.php but I don't know what the difference is).

 

I can also throw my own exception with a code as follows:

throw new MyException("My message", 1234);

Unless one is building some huge class such as PDO, are there any good reasons to include the code?

[requinix]

Throwable is an interface with a getCode method. Exception implements Throwable. That's why there are two.

 

If you have a numeric code to include there then you should use it. Personally I've haven't found it to be useful.

[NotionCommotion]

How did you know it was an interface?  Just because the header: PHP Manual > Language Reference > Predefined Interfaces and Classes > Throwable?

 

Yeah, I started using them, but then came to the same conclusion that they are personally not useful for me.

[requinix]

How did you know it was an interface?  Just because the header: PHP Manual > Language Reference > Predefined Interfaces and Classes > Throwable?

You mean did I RTFM?

[NotionCommotion]

You mean did I RTFM?

 

Maybe I am reading the wrong f'n manual?  Where does it say this is an interface?

 

 

 

[requinix]

I just go to php.net + / + whatever thing I'm thinking about. So http://php.net/throwable.

[Jacques1]

Where does it say this is an interface?

 

The name alone tells you that. When it ends with “able”, it's safe to assume that you're dealing with an interface.