comment on

I second unbolding your post. It is good that you name disadvantages and vulnerabilities, but bold should be used sparingly.
choroba already commented on several of your points
2: instead of calling it a "module that isn't really a module", you could call it a "snippet", or a "paste".
3c: the execute bit is not relevant in this context (it doesn't prevent reading, that's what read permission is for) The execute bit would allow for a standalone script with shebang to be called directly without explicitly calling perl[.exe]
5: I myself have a snippet that defines π via
```
use constant PI => atan2(0, -1);
[download]
```
(which has other disadvantages)
The non-accessibility of $PI in your case is because it is defined within eval.
reading a complete file was just recently discussed in e.g. Re^3: Entity statistics. (I like Path::Tiny)

In reply to Re^2: Trouble usig a subroutine from a custom module by soonix
in thread Trouble usig a subroutine from a custom module by fritz1968

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.