05-23-2019
Regarding Kalkar:
it was a
fast breeder - the few existing ones did not breed as promised, and during operation showed that managing the risks (much higher than the other non-breeding types) was 1. more expensive than estimated and 2. led to too many unplanned downtimes. None of them made profit.
Kalkar was designed with some new techniques, but during construction more and more indications showed up that it would not become profitable.
The people protest certainly caused an earlier withdrawel - the nuclear industry leaders were thinking of another round of redesign/reconstruction.
7 More Discussions You Might Find Interesting
1. Cybersecurity
hi ,
Is there anyway to change ip on sco5.04 i tried using netconfig on the prompt but gives me error . how do u manually change ip cant use acoadmin and netconfig ....
thx
art (2 Replies)
Discussion started by: art_malabanan
2 Replies
2. Shell Programming and Scripting
I have a column in % and I want to display it as a one decimal place number for sorting - what function would I be looking at for dropping the % sign? (2 Replies)
Discussion started by: nortypig
2 Replies
3. Homework & Coursework Questions
bh,lg.yu.,fgh,ry,.tyl,tyk,ty,ty,ty,. (7 Replies)
Discussion started by: frankycool
7 Replies
4. Shell Programming and Scripting
Hi, I am creating a ksh script to search for a string of text inside files within a directory tree. Some of these file are going to be read/execute only. I know to use chmod to change the permissions of the file, but I want to preserve the original permissions after writing to the file. How can I... (3 Replies)
Discussion started by: right_coaster
3 Replies
5. Shell Programming and Scripting
I have 100 files in a directory , all the files have a word "error" and they are created in different date . Now I would like to change the word from "error" to "warning" , and keep the date of the files ( that means do not change the file creation date after change the word ) , can advise what can... (0 Replies)
Discussion started by: ust3
0 Replies
6. Shell Programming and Scripting
I have 100 files in a directory , all the files have a word "error" and they are created in different date . Now I would like to change the word from "error" to "warning" , and keep the date of the files ( that means do not change the file creation date after change the word ) , can advise what can... (7 Replies)
Discussion started by: ust3
7 Replies
7. SCO
Hello
I'm trying to virtualize an instance of Sco Unix 5.0.5 in VirtualBox (called VM-A) , but sco I have problems set to launch with the new raid controller .
The physical machine has a raid controller adaptec (alad driver) but VirtualBox uses buslogic (blc driver)
What ... (3 Replies)
Discussion started by: flako
3 Replies
LEARN ABOUT DEBIAN
perl::critic::policy::subroutines::prohibitexcesscomplexity
Perl::Critic::Policy::Subroutines::ProhibitExcessComplexUser3Contributed Perl DocuPerl::Critic::Policy::Subroutines::ProhibitExcessComplexity(3pm)
NAME
Perl::Critic::Policy::Subroutines::ProhibitExcessComplexity - Minimize complexity by factoring code into smaller 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 subroutine. This Policy approximates the McCabe score by summing the number of conditional statements and operators within
a subroutine. 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.
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 can be set with the "max_mccabe" configuration item. Any subroutine with a McCabe score higher than this
number will generate a policy violation. The default is 20. An example section for a .perlcriticrc:
[Subroutines::ProhibitExcessComplexity]
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.
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::Subroutines::ProhibitExcessComplexity(3pm)