POSIX compliance... Post: 302976886

Sponsored Content

Operating Systems OS X (Apple) POSIX compliance... Post 302976886 by Don Cragun on Thursday 7th of July 2016 02:24:13 PM

07-07-2016

Registered User

Some shells (such as bash and 1993 or later versions of ksh) provide:

Code:

for((n=1; n<=100; n++))
do	echo "process n=$n"
done

but this is an extension that is not yet specified by the standards. As you said, standard ways to do the same thing require an initialization step before the loop, such as in:

Code:

n=1
while [ $n -le 100 ]
do	echo "process n=$n"
	n=$((n + 1))
done

and in:

Code:

n=0
while [ $((++n <= 100)) -eq 1 ]
do	echo "process n=$n"
done

Note: As noted by Scrutinizer in post #8, the POSIX standards do not require $((++n)) to work. (It works with a recent bash and with a 1993 or later version of ksh, but is an extension to the requirements specified by the standards.)

Code:

n=0
while [ $(((n += 1) <= 100)) -eq 1 ]
do	echo "process n=$n"
done

should work in an POSIX-conforming shell.

Last edited by Don Cragun; 07-10-2016 at 04:56 PM.. Reason: Add note.

This User Gave Thanks to Don Cragun For This Post:

Don Cragun

View Public Profile for Don Cragun

Find all posts by Don Cragun

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

sudo & Sox compliance

Hello, I am trying to convince my boss to stop allowing our users to login as root (superuser). Currently our users login to our unix server with their own account, then as needed, they will do an su and put in the root password. This scares me, for a bunch of reasons. Mainly, one is that we...

2. UNIX for Dummies Questions & Answers

man synopsis standard compliance

In different online sources, I found bits and pieces of information about those square and angular brackets and pipes. From what I have read, I can conclude it looks like this: 1. Options outside any brackets are mandatory 2. Options inside these < .. > are mandatory too 3. Options inside ...

3. Cybersecurity

PCI DSS Compliance : Insecure Communication Has Been Detected

From the nessus scanner tool report i got below vulnerability PCI DSS Compliance : Insecure Communication Has Been Detected http://www.tenable.com/plugins/index.php?view=single&id=56208 As per the description given in above link - I am not able to understand How to find insecure port...

4. Red Hat

Looking for PCI Compliance tool for Redhat Lix.

Hi i am in new to Linux world . I have been assigned to a project to find out a tool that will fulfill the PCI compliance for Linux servers for Audit process. anyone have any recommendation on that. Do Rad hat have any native application or plug-ins which we can use for that.

5. HP-UX

Password compliance setting

I need to set password compliance for some servers in my company. However, the requirements are that we need to set different password policies for 3 different user groups within the company. These are : System Users: i.e root, etc Batch/Application Users: oracle, bscs, etc Standard User:...

LEARN ABOUT X11R4

pcre-config

PCRE-CONFIG(1)						      General Commands Manual						    PCRE-CONFIG(1)

NAME

       pcre-config - program to return PCRE configuration

SYNOPSIS


       pcre-config [--prefix] [--exec-prefix] [--version] [--libs]
	    [--libs-posix] [--cflags] [--cflags-posix]

DESCRIPTION


       pcre-config returns the configuration of the installed PCRE libraries and the options required to compile a program to use them.

OPTIONS


       --prefix  Writes the directory prefix used in the PCRE installation for architecture independent files (/usr on many systems, /usr/local on
		 some systems) to the standard output.

       --exec-prefix
		 Writes the directory prefix used in the PCRE installation for architecture dependent files (normally the same as --prefix) to the
		 standard output.

       --version Writes the version number of the installed PCRE libraries to the standard output.

       --libs	 Writes to the standard output the command line options required to link with PCRE (-lpcre on many systems).

       --libs-posix
		 Writes to the standard output the command line options required to link with the PCRE posix emulation library (-lpcreposix -lpcre
		 on many systems).

       --cflags  Writes to the standard output the command line options required to compile files that use PCRE (this may include some -I options,
		 but is blank on many systems).

       --cflags-posix
		 Writes  to the standard output the command line options required to compile files that use the PCRE posix emulation library (this
		 may include some -I options, but is blank on many systems).

SEE ALSO


       pcre(3)

AUTHOR


       This manual page was originally written by Mark Baker for the Debian GNU/Linux system. It has been slightly revised as a generic  PCRE  man
       page.

REVISION


       Last updated: 18 April 2007

																    PCRE-CONFIG(1)

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

sudo & Sox compliance

Discussion started by: rwallaceisg

2. UNIX for Dummies Questions & Answers

man synopsis standard compliance

Discussion started by: vkleban

3. Cybersecurity

PCI DSS Compliance : Insecure Communication Has Been Detected

Discussion started by: saurabh84g

4. Red Hat

Looking for PCI Compliance tool for Redhat Lix.

Discussion started by: sahasuman

5. HP-UX

Password compliance setting

Discussion started by: anaigini45

LEARN ABOUT X11R4

pcre-config