Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[YAGNI] get rid of unuseful exceptions #36

Closed
garak opened this issue Jun 1, 2013 · 4 comments
Closed

[YAGNI] get rid of unuseful exceptions #36

garak opened this issue Jun 1, 2013 · 4 comments

Comments

@garak
Copy link
Member

garak commented Jun 1, 2013

Just use PHP ones.

@leopro
Copy link
Member

leopro commented Jun 1, 2013

@liuggio I agree

@liuggio
Copy link
Member

liuggio commented Jun 1, 2013

"While it is most beneficial to get a standard specialized exception type
like InvalidArgumentException or RuntimeException, it would also be useful
to catch component level exceptions. You can read a more in-depth
discussion of the concepts on the ZF2
wikihttp://framework.zend.com/wiki/display/ZFDEV2/Proposal+for+Exceptions+in+ZF2?showComments=falseor
the PEAR2
wiki http://wiki.php.net/pear/rfc/pear2_exception_policy."

But is OK if you think that is too much

On Sat, Jun 1, 2013 at 4:02 PM, Leonardo Proietti
notifications@github.comwrote:

@liuggio https://github.com/liuggio I agree


Reply to this email directly or view it on GitHubhttps://github.com//issues/36#issuecomment-18789867
.

liuggio_______________

/|_ We reject kings, presidents and voting.
/o ) / We believe in rough consensus
)
v _/\ and running code (I.E.T.F. credo)


@leopro
Copy link
Member

leopro commented Jun 1, 2013

Imho we don't need specialized exception, at least for now.
The advantages that you have in a framework, they are useless in a project like this.

@leopro
Copy link
Member

leopro commented Jun 6, 2013

closed by #56

@leopro leopro closed this as completed Jun 6, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants