The point is that it's your choice what to do. Using Either does not mean you have to write lots of if statements, though you can if you like.
On Wed, Sep 22, 2010 at 12:22 PM, Miroslav Pokorny < [email protected]> wrote: > How is either any better than letting catching an exception or letting the > code continue in the original spot. One gets a split off into a everythings > ok here a file, or jump to there and process the problem ? Using Either ends > up being "more" code because we get the branch for free with > exceptions...And given FileCreation failed is an exception the flow will be > most likely at least a bit different. Continuing on and checking later does > not seem to make much sense most of the time. > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
