{"schema_version":1,"metadata":{"branch":"current","release":"7.9","architecture":"amd64","generated_at":"2026-09-09T04:04:41.004595+00:00","source_url":"https://cdn.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/sqlports-7.55.tgz","source_sha256":"fcdbba1b9df747882aa9bab4af20ebec8dac10655069c90f1cd4145c06e1235e","package_count":12031,"source_kind":"sqlports"},"package":{"name":"p5-indirect-0.39p0","path":"devel/p5-indirect","url":"/packages/current/devel/p5-indirect/","comment":"lexically warn about using the indirect method call syntax","homepage":"https://metacpan.org/release/indirect","maintainer":"The OpenBSD ports mailing-list <ports@openbsd.org>","description":"When enabled, this pragma warns about indirect method calls that are\npresent in your code.\n\nThe indirect syntax is now considered harmful, since its parsing has\nmany quirks and its use is error prone : when the subroutine foo has not\nbeen declared in the current package, foo $x actually compiles to\n$x->foo, and foo { key => 1 } to 'key'->foo(1). In\nhttp://www.shadowcat.co.uk/blog/matt-s-trout/indirect-but-still-fatal,\nMatt S. Trout gives an example of an undesirable indirect method call on\na block that can cause a particularly bewildering error.\n\nThis pragma currently does not warn for core functions (print, say, exec\nor system). This may change in the future, or may be added as optional\nfeatures that would be enabled by passing options to unimport.\n","package_architecture":"amd64","stem":"p5-indirect","readme":null,"dependencies":[{"path":"devel/p5-Devel-Declare","type":"test","package_spec":"","url":"/packages/current/devel/p5-Devel-Declare/"}],"reverse_dependencies":{"count":1,"url":"/packages/data/d4/d4f1f0ffd3ef6bfebae13cae5afd2e732b4cd3ccf578d2ca90ea7852a8eacf07.json"},"categories":["devel","perl5"],"flavors":[],"only_for_architectures":[],"not_for_architectures":[]}}