Re: ::Tiny modules namespace origins

Here are the rules Adam Kennedy originally defined for what ::Tiny means:

The module should be implemented in "as little code as possible"
The module should implement a useful subset of functionality
The module should use at least 1/10th the amount of memory overhead, ideally less than 100k
The module MUST have no non-core dependencies
The module MUST be only one single .pm file
The module should be back-compatible to at least 5.004
The module should omit functionality rather than implement it incorrectly.
If applicable, the module should be compatible with the larger module.

map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

Comment on Re: ::Tiny modules namespace origins Download Code

Replies are listed 'Best First'.
Re^2: ::Tiny modules namespace origins by Smonff (Scribe) on Oct 08, 2020 at 11:25 UTC
Thanks! I'm glad I asked because it is much more formal than what I was thinking. Very impressive... 🌸	[reply]
Re^2: ::Tiny modules namespace origins by Aldebaran (Curate) on Oct 09, 2020 at 21:12 UTC
The module should use at least 1/10th the amount of memory overhead, ideally less than 100k Does memory overhead mean memory allocated by C libraries under the hood? Is using 50% of memory allocated "good" and 5 per cent less so, because we will have asked for too much?	[reply]