07-04-2012
Error in eval man page
Hello,
I believe that the following man page contains an error: <www dot unix dot com>/man-page/posix/1posix/eval/
In section "EXAMPLES", the fourth line should probably be:
eval y='$'$x
rather than:
$fooeval y='$'$x
Regards,
Jérôme DUBOIS.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i've never done this before. i created a script that I placed in /usr/bin, but want to create a man page for it. i'm clueless
thanks (3 Replies)
Discussion started by: theDirtiest
3 Replies
2. UNIX for Dummies Questions & Answers
I was wonderiong if ther is a way for a user to add a man page specific to thier account. similar to copying the .1 or .1.gz to /usr/share/man/man1 "cp *.1.gz /usr/share/man/man1". Except for using another folder as I don't have access to /usr/share/man/man1. I would think that this might involve... (1 Reply)
Discussion started by: jacob358
1 Replies
3. Red Hat
Hi Guys,
I'm looking for the man page for scp version 1.2.27
I have an old redhat server that has a few large scripts that use this version and I want to know what the -A flag does and the man page is not on there. (4 Replies)
Discussion started by: Tornado
4 Replies
4. UNIX for Advanced & Expert Users
Man page is not working my system. It is giving the following the following error
> man ls
gdbm fatal: read error
with debug option
> man -d ls
...
....
...
...
using less as pager
checking for locale en_US
add_nls_manpath(): processing /usr/local/man:/usr/share/man:/usr/X11R6/man... (4 Replies)
Discussion started by: praveenkumar_l
4 Replies
5. Solaris
Help,
it seem that i am unable to get man help form solaris 10.
I am running SunOS unknown 5.10 Generic_120012-14 i86pc i386 i86pc
when ever i try to man a command what i get is "No manual entry" like the one below.
# man grep
No manual entry for grep.
# man ls
No manual entry for ls.... (8 Replies)
Discussion started by: ezsurf
8 Replies
6. Solaris
What does the last change means in man page .. does that this man page has not been updated since 2003 or something else ?
newfs-options
The options are documented in the newfs man page.
SunOS 5.10 Last change: 9 Dec 2003 1
System... (2 Replies)
Discussion started by: fugitive
2 Replies
7. Shell Programming and Scripting
Hello,
hope this is the correct forum for this question.
I have created a man page, named nfwatchdog.1.gz. This man page was installed under /usr/share/man/man1. When I execute: man nfwatchdog from any location, the man page is incorrectly opened (I see ASCII garbage). But when I directly... (4 Replies)
Discussion started by: nardix
4 Replies
8. Shell Programming and Scripting
anyone has any info on why this is complaining???
vivek@vivek-c5e55ef2e ~/TAC
$ zoneCounter=1
vivek@vivek-c5e55ef2e ~/TAC
$ optUsage1=23%
vivek@vivek-c5e55ef2e ~/TAC
$ eval eval echo "<th>Zone $zoneCounter </th><th align=\"left\"> \$optUsage$zoneCounter </th>"
-bash: syntax error... (1 Reply)
Discussion started by: vivek d r
1 Replies
9. Shell Programming and Scripting
anyone has any info on why this is complaining???
vivek@vivek-c5e55ef2e ~/TAC
$ zoneCounter=1
vivek@vivek-c5e55ef2e ~/TAC
$ optUsage1=23%
vivek@vivek-c5e55ef2e ~/TAC
$ eval eval echo "<th>Zone $zoneCounter </th><th align=\"left\"> \$optUsage$zoneCounter </th>"
-bash: syntax error... (13 Replies)
Discussion started by: vivek d r
13 Replies
LEARN ABOUT CENTOS
perl::critic::policy::builtinfunctions::prohibitstringyeval
Perl::Critic::Policy::BuiltinFunctions::ProhibitStringyEUser3Contributed Perl DocumePerl::Critic::Policy::BuiltinFunctions::ProhibitStringyEval(3)
NAME
Perl::Critic::Policy::BuiltinFunctions::ProhibitStringyEval - Write "eval { my $foo; bar($foo) }" instead of "eval "my $foo; bar($foo);"".
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
The string form of "eval" is recompiled every time it is executed, whereas the block form is only compiled once. Also, the string form
doesn't give compile-time warnings.
eval "print $foo"; # not ok
eval {print $foo}; # ok
CONFIGURATION
There is an "allow_includes" boolean option for this Policy. If set, then strings that look like they only include a single "use" or
"require" statement (with the possible following statement that consists of a single number) are allowed. With this option set, the
following are flagged as indicated:
eval 'use Foo'; # ok
eval 'require Foo'; # ok
eval "use $thingy;"; # ok
eval "require $thingy;"; # ok
eval "use $thingy; 1;"; # ok
eval "require $thingy; 1;"; # ok
eval 'use Foo; blah;'; # still not ok
eval 'require Foo; 2; 1;'; # still not ok
eval 'use $thingy;'; # still not ok
eval 'no Foo'; # still not ok
If you don't understand why the number is allowed, see Perl::Critic::Policy::ErrorHandling::RequireCheckingReturnValueOfEval.
This option inspired by Ricardo SIGNES' Perl::Critic::Policy::Lax::ProhibitStringyEval::ExceptForRequire.
SEE ALSO
Perl::Critic::Policy::ControlStrucutres::RequireBlockGrep
Perl::Critic::Policy::ControlStrucutres::RequireBlockMap
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.16.3 2014-06-09 Perl::Critic::Policy::BuiltinFunctions::ProhibitStringyEval(3)