Download the PHP package qubus/error without Composer
On this page you can find all versions of the php package qubus/error. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package error
Short Description Package for Error handling.
License MIT
Homepage https://github.com/QubusPHP/error
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package error
Error Handler
Error handling with PSR-3 logging for catching exceptions as well as errors. There is also an error class to use as an alternative to throwing an exception.
Example
Requirements
- PHP 8.2+
Installation
Exceptions vs. Errors
There is a healthy discussion among developers whether to use exceptions or error return codes. There are pros and cons to both sides. No matter what side you fall on, the articles below are a great read with a dose of great examples as to the proper use of exceptions.
- Exception Handling Considered Harmful
- Why is exception handling bad?
- "The rule of thumb is that exceptions should flag exceptional conditions, and that you should not use them for control of program flow."
- Why I Hate Exceptions
- Structured Exception Handling Considered Harmful
- Exceptions
- Why You Should Avoid Using Exceptions as the Control Flow in Java
- Exceptional Exceptions, Demystified - Part 1
- Exceptional Exceptions, Demystified - Part 2
- Exceptional Exceptions Demystified - Part 3
Author Statement
I am of the mind that if a function is to return something, then it should return, not throw. If an exception is exceptional, it should be caught and logged. I know that I don't do this perfectly, but it is my goal to go through all of my code and make sure that exceptions are exceptional and not unexceptional.
