Menu
Community /Pin to ProfileBookmark
@NogDogFeb 27.2010 — #While it's unclear to me exactly what you want to do, perhaps throwing an exception could be what you need?
Though one could argue that every call to any method should be checking the return value, and every method should return something. (I try to always follow this rule, though admittedly sometimes I get lazy with regard to checking the result.)@NogDogFeb 27.2010 — #
There are always gray areas and [non-programmatic] exceptions to every rule, but I try to have every method (except constructors and such that cannot) return something, even if it's just boolean true/false to indicate its completion status. I'm of the school that exceptions are for programmer or system errors, but not for expected results -- which include things like user errors, no matching record in the DB, etc.
So for my personal programming style, if the case in question here deals with some sort situation that I would consider an exception, then throwing an exception would make sense. If not, I would have the method in question return false (or whatever makes sense in its case, such as 0 or an empty array/string) and leave it to the calling code to decide what to do.
But I'm not going to claim it's the only way or the best way, just my way. ?@NogDogFeb 27.2010 — #
Hmm...I'd be curious to know what those cases are. (Not wanting to type some more code does not count. ? :p )@NogDogFeb 27.2010 — #
Yes, I try to have every function at a minimum return a boolean. Maybe I don't care right now whether it returned anything, but I think it makes it more re-usable for future enhancements or porting to other applications.
(Hope we're not veering too far off-topic, DK, but I enjoy these discussions more than the "why am I getting an unexpected $end error?". ? )@NogDogFeb 27.2010 — #
Sometimes that's the best result of this sort of discussion, it makes you define the problem more carefully, and then that helps you see a better solution. ? Let us know if you come up with something good.
Exit class, don’t kill the page
I was wondering if there is a way to exit a class object without killing the rest of the page.
the exit and die commands kills everything.
One could use return in the methods, but this wont work since some of the methods are called within other methods, and I want a more automatic way of exiting the class without having to make tons of return value checks in every single method.
So what I need is some kind of exit_class command?
Sign in
to post a comment11 Comments(s) ↴
0
@NogDogFeb 27.2010 — #While it's unclear to me exactly what you want to do, perhaps throwing an exception could be what you need?One could use return in the methods, but this wont work since some of the methods are called within other methods, and I want a more automatic way of exiting the class without having to make tons of return value checks in every single method.[/quote]
Though one could argue that every call to any method should be checking the return value, and every method should return something. (I try to always follow this rule, though admittedly sometimes I get lazy with regard to checking the result.)
0
@NogDogFeb 27.2010 — #Yes sounds like throwing an Exception and using a try/catch block might be your best bet. Personally I don't like to make my methods all return something just for the sake of it - I prefer to use exceptions and keep the return value free of pollution, especially in the case of public methods where it is really the job of the client code to be looking for exceptions and dealing with them.[/QUOTE]
There are always gray areas and [non-programmatic] exceptions to every rule, but I try to have every method (except constructors and such that cannot) return something, even if it's just boolean true/false to indicate its completion status. I'm of the school that exceptions are for programmer or system errors, but not for expected results -- which include things like user errors, no matching record in the DB, etc.
So for my personal programming style, if the case in question here deals with some sort situation that I would consider an exception, then throwing an exception would make sense. If not, I would have the method in question return false (or whatever makes sense in its case, such as 0 or an empty array/string) and leave it to the calling code to decide what to do.
But I'm not going to claim it's the only way or the best way, just my way. ?
0
@NogDogFeb 27.2010 — #True, but that isn't possible in all cases.
...[/QUOTE]
Hmm...I'd be curious to know what those cases are. (Not wanting to type some more code does not count. ? :p )
0
@NogDogFeb 27.2010 — #...Though I suppose your point is that void functions are not helpful in the first place![/QUOTE]
Yes, I try to have every function at a minimum return a boolean. Maybe I don't care right now whether it returned anything, but I think it makes it more re-usable for future enhancements or porting to other applications.
(Hope we're not veering too far off-topic, DK, but I enjoy these discussions more than the "why am I getting an unexpected $end error?". ? )
0
@NogDogFeb 27.2010 — #...
But thx, trying to come up with a special case for this reply, just gave me an idea that might work.
...[/QUOTE]
Sometimes that's the best result of this sort of discussion, it makes you define the problem more carefully, and then that helps you see a better solution. ? Let us know if you come up with something good.