[Baypiggies] Python way to avoid usage of raise

[Zachary Collins]

I know.  You should devise a way for your f1_caller to be able to
determine if there's an issue inside of f1, and have it just
automatically back out of f1_caller itself, and then inform the caller
of f1_caller.  Something that you could just add inside of f1 in one
place, that informed as far back in the stack as is responsible for
the data issue in f1.  Something that maybe allowed you to make caller
functions aware of an error, elegantly... hmmmmmmmm

2010/10/5 Daniel González Gasull <daniel at djansoft.com>:
> I agree.  That's an anti-pattern:
>
> http://today.java.net/article/2006/04/04/exception-handling-antipatterns
>
> The article is about Java, but it applies anyway.  See where it says
> "Log and Return Null".
>
>
> On Tue, Oct 5, 2010 at 7:27 PM, Glen Jarvis <glen at glenjarvis.com> wrote:
>>
>>> My work place has imposed a rules for no use of exception (catching is allowed).
>>
>> What?!?
>>
>> Forgive my reaction, I'm just very surprised. Why has your workplace implemented this policy? Has anyone else on BayPIGgies seen a  policy like this? What's the rationale?  Am I a Luddite for not hearing on this?
>>
>> I'm sorry. I know you asked a genuine question and I haven't answered it. I just found this very odd and am first getting my head around the question.
>>
>> Cheers,
>>
>>
>> Glen
>>
>> _______________________________________________
>> Baypiggies mailing list
>> Baypiggies at python.org
>> To change your subscription options or unsubscribe:
>> http://mail.python.org/mailman/listinfo/baypiggies
>>
>
>
>
> --
> http://DjanSoft.com :: Agile Application Development with Python
> _______________________________________________
> Baypiggies mailing list
> Baypiggies at python.org
> To change your subscription options or unsubscribe:
> http://mail.python.org/mailman/listinfo/baypiggies
>