Re^2: Exporting use strict/warnings into main::

Replies are listed 'Best First'.
Re^3: Exporting use strict/warnings into main:: by haukex (Archbishop) on May 19, 2020 at 06:47 UTC
Sure, certain packages do it, but they are rather lower-level than this utility. Moo, Role::Tiny, Moose, Mojolicious, Dancer, Dancer2, Test::Most, and lots more...	[reply]
Re^4: Exporting use strict/warnings into main:: by 1nickt (Canon) on May 19, 2020 at 18:44 UTC
Yes, that's exactly my point. All of those are frameworks on which you build an app, so it's appropriate to have them export things like `strict` into the caller's namespace. The OP's utility does not fit that category. The way forward always starts with a minimal test.	[reply] [d/l]
Re^5: Exporting use strict/warnings into main:: by haukex (Archbishop) on May 19, 2020 at 21:11 UTC
Yes, that's exactly my point. All of those are frameworks ... Ah, I see, I thought with "lower-level" you meant modules like strictures or Modern::Perl, which is why I didn't list those.	[reply]
Re^5: Exporting use strict/warnings into main:: by haj (Vicar) on May 19, 2020 at 19:37 UTC
The OP's utility does not fit that category. It doesn't? That module is a special purpose utility with a rich DSL. So, the module does define its own rules. It is rather unlikely that someone casually uses it and all of a sudden trips over `strict`.	[reply]
Re^3: Exporting use strict/warnings into main:: by haj (Vicar) on May 19, 2020 at 10:07 UTC
I'd say that importing `strict` into your caller's scope is acceptable if the package in question defines the way you write your code anyway, like the examples given by haukex do, but presumptuous in an ordinary OO package. But maybe that's what you mean with "lower-level".	[reply]
Re^4: Exporting use strict/warnings into main:: by 1nickt (Canon) on May 19, 2020 at 18:46 UTC
Precisely. The way forward always starts with a minimal test.	[reply]