Polymorphic return values are really useful. Often, we just want to know if
authoradrianp <adrianp>
Sun, 29 Jul 2007 11:45:15 +0000 (11:45 +0000)
committeradrianp <adrianp>
Sun, 29 Jul 2007 11:45:15 +0000 (11:45 +0000)
commitff698e89f95d9325c21f53fd605056225beee39d
tree7062b2723a96f2e400b58f95dc696ce45eaac916
parent90dd7f9cc54515d9dbb488dc0ad95561fa0f4c36
Polymorphic return values are really useful. Often, we just want to know if
something worked or not. Other times, we'd like to know what the error text
was. Still others, we may want to know what the error code was, and what the
error properties were. We don't want to handle objects or data structures for
every single return value, but we do want to check error conditions in our
code because that's what good programmers do.

When functions are successful they may return true, or perhaps some useful
data. In the quest to provide consistent return values, this gets confusing
between complex, informational errors and successful return values.

This module provides these features with a simple API that should get you what
you're looking for in each contex a return value is used in.

Imported from pkgsrc-wip and packaged by kuli0020@umn.edu
devel/p5-Return-Value/DESCR [new file with mode: 0644]
devel/p5-Return-Value/Makefile [new file with mode: 0644]
devel/p5-Return-Value/PLIST [new file with mode: 0644]
devel/p5-Return-Value/distinfo [new file with mode: 0644]