Personally, I'm not too happy with hiding "boilerplate" away, but if you have a strong company policy, using something like Toolkit might make it easier to do the right thing for everybody by implicitly loading the modules.
Me not also, I want to have an easy way to write quick and dirty one liners or 4 liners for simple stuff :-) Firm policy is putting it inside as posted and for production code running at live systems, I'd enhance it also (allthough I need good examples of how much you can shorten source code to fight vs copy+paste culture :-))
Greetings,
Janek Schleicher
In reply to Re^2: How to export several modules intu users name space to not have a use ...; use ...; use ...; with the same modules all over again
by bigj
in thread How to export several modules intu users name space to not have a use ...; use ...; use ...; with the same modules all over again
by bigj
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |