Zonbox: The $100 Green PC of the Future - Digitaltrends.com
Zonbox: The $100 Green PC of the Future Digitaltrends.com, OR - 8 minutes ago ... uses Linux as its core OS (but conceals the complexity of Linux, much like OSX conceals the complexity of UNIX), and is at the outset, a Web 2.0 device ...
Admins...
I just lerve the pop-ups that appear whilst replying to someones post.
It reminds me of "Paperclip" from my MS Windows days... ;oDD
Love it, as it makes me smile, telling me I am creating a thread ATM... ;o)
Neat little addition/feature guys... (4 Replies)
Hello,
I have HP-UX 11.x running and the screen turns green with white text from the start. Sometimes, more desirable, the screen will start off with the normal black and white text terminal, but out of nowhere it will go green. For instance, I started it up an hour ago and it was fine, I then... (2 Replies)
Hey! (first post!)
Has anyone here ever played Dungeons and Dragons before? Well, this game, Legend of the Green Dragon, does have it's similiarities.. And is a great roleplaying environment..
I would really like to to get the community built up -- It's sort of difficult because this game... (1 Reply)
Perl::Critic::Policy::Modules::ProhibitExcessMainComplexUser3Contributed Perl DocuPerl::Critic::Policy::Modules::ProhibitExcessMainComplexity(3pm)NAME
Perl::Critic::Policy::Modules::ProhibitExcessMainComplexity - Minimize complexity in code that is outside of subroutines.
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
All else being equal, complicated code is more error-prone and more expensive to maintain than simpler code. The first step towards
managing complexity is to establish formal complexity metrics. One such metric is the McCabe score, which describes the number of possible
paths through a block of code. This Policy approximates the McCabe score by summing the number of conditional statements and operators
within a block of code. Research has shown that a McCabe score higher than 20 is a sign of high-risk, potentially untestable code. See
<http://en.wikipedia.org/wiki/Cyclomatic_complexity> for some discussion about the McCabe number and other complexity metrics.
Whereas Perl::Critic::Policy::Subroutines::ProhibitExcessComplexity scores the complexity of each subroutine, this Policy scores the total
complexity of all the code that is outside of any subroutine declaration.
The usual prescription for reducing complexity is to refactor code into smaller subroutines. Mark Dominus book "Higher Order Perl" also
describes callbacks, recursion, memoization, iterators, and other techniques that help create simple and extensible Perl code.
CONFIGURATION
The maximum acceptable McCabe score can be set with the "max_mccabe"
configuration item. If the sum of all code outside any subroutine has a McCabe score higher than this number, it will generate a Policy
violation. The default is 20. An example section for a .perlcriticrc:
[Modules::ProhibitExcessMainComplexity]
max_mccabe = 30
NOTES
"Everything should be made as simple as possible, but no simpler."
-- Albert Einstein
Complexity is subjective, but formal complexity metrics are still incredibly valuable. Every problem has an inherent level of complexity,
so it is not necessarily optimal to minimize the McCabe number. So don't get offended if your code triggers this Policy. Just consider if
there might be a simpler way to get the job done.
SEE ALSO
Perl::Critic::Policy::Subroutines::ProhibitExcessComplexity
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::ProhibitExcessMainComplexity(3pm)
