return polymorphic values

devel/p5-Return-Value/Makefile

@@ -0,0 +1,19 @@
+# $OpenBSD: Makefile,v 1.1.1.1 2006/11/13 00:10:03 espie Exp $
+
+COMMENT= 	"polymorphic return values"
+
+MODULES=	cpan 
+
+DISTNAME=	Return-Value-1.301
+CATEGORIES=	devel
+
+MASTER_SITES=	${MASTER_SITE_PERL_CPAN:=../by-authors/id/R/RJ/RJBS/}
+
+# perl
+PERMIT_PACKAGE_CDROM=	Yes
+PERMIT_PACKAGE_FTP=	Yes
+PERMIT_DISTFILES_CDROM=	Yes
+PERMIT_DISTFILES_FTP=	Yes
+
+MAKE_ENV=	TEST_POD=Yes
+.include <bsd.port.mk>

devel/p5-Return-Value/distinfo

@@ -0,0 +1,4 @@
+MD5 (Return-Value-1.301.tar.gz) = 15aeae9a075d58431c2656ec0e2f6cb3
+RMD160 (Return-Value-1.301.tar.gz) = 9848b7b6eb12b6588a3833d9a26a454f521f02a7
+SHA1 (Return-Value-1.301.tar.gz) = b9e12d054256d840e90c17acf5b6922b74610433
+SIZE (Return-Value-1.301.tar.gz) = 6688

devel/p5-Return-Value/pkg/DESCR

@@ -0,0 +1,15 @@
+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.

devel/p5-Return-Value/pkg/PLIST

@@ -0,0 +1,4 @@
+@comment $OpenBSD: PLIST,v 1.1.1.1 2006/11/13 00:10:03 espie Exp $
+${P5SITE}/Return/
+${P5SITE}/Return/Value.pm
+@man man/man3p/Return::Value.3p