Sponsored Content
Full Discussion: Moric
Top Forums UNIX for Dummies Questions & Answers Moric Post 302102456 by BOFH on Wednesday 10th of January 2007 02:16:35 PM
Old 01-10-2007
This will probably be removed eventually, however this isn't the right site for this sort of question from either of you.

You guys are in school and are supposed to be studying, homework, etc. Spend more time in the library reading than trying to get around school blocks.

Carl
 

We Also Found This Discussion For You

1. Windows & DOS: Issues & Discussions

Mote Moric Blocks In My School.

I was wondering if anyone knew whether or not there was a way past these blocks. It isn't like I'm trying to get into anything bad or things like that, but I'd like to visit sites that normal 16 year olds go to, such as Myspace, GaiaOnline, and sites like that. Please, if anyone knows any... (2 Replies)
Discussion started by: GreekCoeus
2 Replies
Perl::Critic::Policy::Modules::RequireBarewordIncludes(3User Contributed Perl DocumentaPerl::Critic::Policy::Modules::RequireBarewordIncludes(3pm)

NAME
Perl::Critic::Policy::Modules::RequireBarewordIncludes - Write "require Module" instead of "require 'Module.pm'". AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
When including another module (or library) via the "require" or "use" statements, it is best to identify the module (or library) using a bareword rather than an explicit path. This is because paths are usually not portable from one machine to another. Also, Perl automatically assumes that the filename ends in '.pm' when the library is expressed as a bareword. So as a side-effect, this Policy encourages people to write '*.pm' modules instead of the old-school '*.pl' libraries. use 'My/Perl/Module.pm'; #not ok use My::Perl::Module; #ok CONFIGURATION
This Policy is not configurable except for the standard options. NOTES
This Policy is a replacement for "ProhibitRequireStatements", which completely banned the use of "require" for the sake of eliminating the old '*.pl' libraries from Perl4. Upon further consideration, I realized that "require" is quite useful and necessary to enable run-time loading. Thus, "RequireBarewordIncludes" does allow you to use "require", but still encourages you to write '*.pm' modules. Sometimes, you may want to load modules at run-time, but you don't know at design-time exactly which module you will need to load (Perl::Critic is an example of this). In that case, just attach the '## no critic' annotation like so: require $module_name; ## no critic CREDITS
Chris Dolan <cdolan@cpan.org> was instrumental in identifying the correct motivation for and behavior of this Policy. Thanks Chris. AUTHOR
Jeffrey Ryan Thalhammer <jeff@imaginative-software.com> COPYRIGHT
Copyright (c) 2005-2011 Imaginative Software Systems. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license can be found in the LICENSE file included with this module. perl v5.14.2 2012-06-07 Perl::Critic::Policy::Modules::RequireBarewordIncludes(3pm)
All times are GMT -4. The time now is 03:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy