{"schema_version":1,"metadata":{"branch":"release","release":"7.9","architecture":"amd64","generated_at":"2026-09-09T04:04:02.361425+00:00","source_url":"https://cdn.openbsd.org/pub/OpenBSD/7.9/packages/amd64/sqlports-7.54.tgz","source_sha256":"2de00144847bf9da3a365be982f101dbb55d591ed7a915ea94984a16ab0e0404","package_count":12059,"source_kind":"sqlports"},"package":{"name":"p5-Return-Value-1.666005p0","path":"devel/p5-Return-Value","url":"/packages/release/devel/p5-Return-Value/","comment":"polymorphic return values","homepage":"https://metacpan.org/release/Return-Value","maintainer":"The OpenBSD ports mailing-list <ports@openbsd.org>","description":"Polymorphic return values are really useful. Often, we just want to know\nif something worked or not. Other times, we'd like to know what the\nerror text was. Still others, we may want to know what the error code\nwas, and what the error properties were. We don't want to handle objects\nor data structures for every single return value, but we do want to\ncheck error conditions in our code because that's what good programmers\ndo.\n\nWhen functions are successful they may return true, or perhaps some\nuseful data. In the quest to provide consistent return values, this gets\nconfusing between complex, informational errors and successful return\nvalues.\n\nThis module provides these features with a simple API that should get\nyou what you're looking for in each contex a return value is used in.\n","package_architecture":"*","stem":"p5-Return-Value","readme":null,"dependencies":[{"path":"devel/p5-Test-Pod","type":"test","package_spec":"","url":"/packages/release/devel/p5-Test-Pod/"},{"path":"devel/p5-Test-Pod-Coverage","type":"test","package_spec":"","url":"/packages/release/devel/p5-Test-Pod-Coverage/"}],"reverse_dependencies":{"count":2,"url":"/packages/data/59/597b1359413b3e1a1f8dde236866c42903e360e6adc678a672f60fb4a0c477d8.json"},"categories":["devel","perl5"],"flavors":[],"only_for_architectures":[],"not_for_architectures":[]}}