Is there a simple way of calculating the max number in a set of variables, so
something that says
I've found a way to do it using:
is there a simpler, more elegant way to do it?
Last edited by unclecameron; 02-20-2010 at 01:27 PM..
OS - Sun OS7
What sources can I go to to figure out what is the maximun number of processes for OS7 with 2GB of memory.
I believe it is 64K processes, but this number reflects resources being swaped.
Any help is appreciated
SmartJuniorUnix (1 Reply)
Hi,
Anyone can help ?
I have 21,000 sub-folder under the main folder .
Now are having some problem writing .
Is there a max no. of sub-folder can be create under Solaris .
If yes ,what is the max no. , can it be configure to increase ?
Thanks (4 Replies)
Hi, i have a file with numbers in it and i was wondering if there's a script i could use to find the max number and have that printed to a new file?
example a.txt
18
26
47
34
27
so find the max number in a.txt and print it to b.txt.
Thanks! (17 Replies)
Hello all,
I'm looking to implement a Linux server that will host up to 60 simultaneous X sessions, all running firefox to a secured web interface.
Does anyone have any experience sizing a system like this?
The reason for the setup isn't as important (Since I really don't understand why... (1 Reply)
Hi Folks.Just out of interest does anyone know if their is a maximum number of variables that korn shell supports and if so how do I query what it is?Cheers (1 Reply)
Hi,
I was wondering, whether there is a limit regarding the max number of nfs mounts in
Oracle Solaris 10 (newest update).
The data center plans to migrate from a fibre channel based storage environment (hitachi) to a nfs based storage environment (netapp). Regarding the Solaris 10 database... (1 Reply)
I need to know what is the maximum stack size i.e. -Xss my java program is running with.
Is there a way to find that out from inside my java program code and outside of it.
What i am looking for is to read whatever the current set max limit -Xss (stack sie) is for a particular JVM(not... (3 Replies)
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)