A class is a component, by definition.Jcart wrote:I've actually never even considered doing it this way. However, I would vote against doing so, considering the exceptions are a subset of the component, and are not components themselves.
Consistent naming conventions aid further development and code readability.
I impose very strict naming conventions on myself when developing applications. For instance, in a database, every single field has a unique name throughout the entire database, and strictly follows a standard, e.g. s_id (table prefix underscore field name).
Can you tell me where in the hierarchy of exceptions does BadMethodCallException sit?
And what is the difference between Swift_Exception and Swift_SwiftException?