Sponsored Content
Top Forums UNIX for Advanced & Expert Users Detecting unused variables... Post 302975368 by wisecracker on Saturday 11th of June 2016 05:09:06 PM
Old 06-11-2016
Well guys I have done some some experiments printf .
(All 'printf' statements now changed inside AudioScope.
Now consider the code below:-
Code:
#!/bin/sh --posix
clear
x=8
y=2
printf "\x1B["$y";"$x"fWorks but is not POSIX or sh compliant...\n"
y=4
printf "%b" "\x1B["$y";"$x"fWorks but is not POSIX or sh compliant...\n"
y=6
printf "%b" "\x1B[""$y"";""$x""fWorks but is POSIX and sh compliant...\n"
y=8
printf "%b" "\x1B[$y;$x""fWorks but is POSIX and sh compliant...\n"
y=10
printf "%b" "\x1B[$y;$xfDoes not work for obvious reasons but it is POSIX or sh compliant.\n"
y=12
printf "%b" "\x1B[""$y"';'"$x""fWorks but is POSIX and sh compliant...\n"
y=14
# Why is line 5 not posix complaint but line 18 is?
printf "%b" "\x1B["$y';'$x"fWorks but is POSIX and sh compliant...\n"
exit 0

Results from 'ShellCheck':-
Code:
$ shellcheck myscript
 
Line 5:
printf "\x1B["$y";"$x"fWorks but is not POSIX or sh compliant...\n"
       ^-- SC2059: Don't use variables in the printf format string. Use printf "..%s.." "$foo".
              ^-- SC2027: The surrounding quotes actually unquote this. Remove or escape them.
                   ^-- SC2027: The surrounding quotes actually unquote this. Remove or escape them.
 
Line 7:
printf "%b" "\x1B["$y";"$x"fWorks but is not POSIX or sh compliant...\n"
                   ^-- SC2027: The surrounding quotes actually unquote this. Remove or escape them.
                        ^-- SC2027: The surrounding quotes actually unquote this. Remove or escape them.
 
Line 13:
printf "%b" "\x1B[$y;$xfDoes not work for obvious reasons but it is POSIX and sh compliant.\n"
                     ^-- SC2154: xfDoes is referenced but not assigned.

$

Now line 13 is obviously wrong so ignore that but why is line 5 NOT posix compliant but line 18 IS compliant?
Most of the AudioScope.sh printf statements follow the line 9 format...
Terminal results; OSX 10.7.5, default terminal calling 'sh'.
Code:
       Works but is not POSIX or sh compliant...

       Works but is not POSIX or sh compliant...

       Works but is POSIX and sh compliant...

       Works but is POSIX and sh compliant...
ot work for obvious reasons but it is POSIX or sh compliant.


       Works but is POSIX and sh compliant...

       Works but is POSIX and sh compliant...
AMIGA:barrywalker~/Desktop/Code/Shell> _

TIA...
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How do I get the unused space?

One of my Solaris 8 machines hd was about to die. So I used g4u to create an image of the 9gb drive and I put it in a 36gb drive. That solved my dieing hd problem. But.... How do I get my machine to see the unused 27gb of space? Any help would be greatly appreciated. (1 Reply)
Discussion started by: Spyzic
1 Replies

2. AIX

unused storage on AIX 4.3

Hi, How do I query for unused partition in AIX 4.3 with DAS and SAA storage? I know most unix administrator don't put all the capacity on the system at once. thanks, vene (1 Reply)
Discussion started by: venerayan
1 Replies

3. UNIX for Dummies Questions & Answers

delete the unused file

Hi All, Can you please let me know how to delete any files that have not been accessed in the past 28 days in a directory. Thanks, Arun (3 Replies)
Discussion started by: arunkumar_mca
3 Replies

4. AIX

how to clean Unused semaphore??

How can i clean up my unused semaphore??? (4 Replies)
Discussion started by: abhishek27
4 Replies

5. HP-UX

HP-UX using unused HDD space

Hello, I have a system with HP-UX 11.23 installed on it. There are ~36GB of unused space on the HDD. I did a very basic installation, and it created the usual volume group /dev/vg00. When I look at the output of ioscan -funC disk, I see this (and more, but irrelevant to this post): disk ... (1 Reply)
Discussion started by: goon12
1 Replies

6. Solaris

unused disk space

i Have alloted 20G in my vmware for solaris 10, upon installation, and some distribution of disk space to /,/opt,swap i just use 19G. Can i still use the 1G? How? how to see the 1G? that i did not use? how can i use it? appreciate your responce (17 Replies)
Discussion started by: kenshinhimura
17 Replies

7. AIX

Temporarily disabling unused ethernet adapter

Hi, In our AIX 5.2 server , we have one unused ethernet adapter which doesn't have cable connection . For this interface , we are getting alerts in errpt . Could you suggesthow to stop this alert ? And sametime i would like to keep this device in ODM . Is there... (1 Reply)
Discussion started by: sekarsamy
1 Replies

8. Programming

What Unix do with unused shared memory?

Hello, When creating shared memory in C, should be remove shared memory with shmctl function when don't need it. If it didn't remove, occupied shared memory stay and remain. If we create shared memory repeatedly without removing unusable shared memory, /dev/shm will full. Does Unix or... (1 Reply)
Discussion started by: pronetin
1 Replies

9. Solaris

Solaris 10: how to disable an unused HBA card

Dear all, I have a new Oracle Blade X4-2B server, running Solaris 10. The server comes with a HBA card that will not be used now. It has not fibers connected to it. As a consequence, its leds never stop flashing. My question is: how to disable this HBA card, without removing it physically... (2 Replies)
Discussion started by: Gus1971
2 Replies
STRERROR(3)                                                  Linux Programmer's Manual                                                 STRERROR(3)

NAME
strerror, strerror_r, strerror_l - return string describing error number SYNOPSIS
#include <string.h> char *strerror(int errnum); int strerror_r(int errnum, char *buf, size_t buflen); /* XSI-compliant */ char *strerror_r(int errnum, char *buf, size_t buflen); /* GNU-specific */ char *strerror_l(int errnum, locale_t locale); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): strerror_r(): The XSI-compliant version is provided if: (_POSIX_C_SOURCE >= 200112L) && ! _GNU_SOURCE Otherwise, the GNU-specific version is provided. DESCRIPTION
The strerror() function returns a pointer to a string that describes the error code passed in the argument errnum, possibly using the LC_MESSAGES part of the current locale to select the appropriate language. (For example, if errnum is EINVAL, the returned description will be "Invalid argument".) This string must not be modified by the application, but may be modified by a subsequent call to strerror() or strerror_l(). No other library function, including perror(3), will modify this string. strerror_r() The strerror_r() function is similar to strerror(), but is thread safe. This function is available in two versions: an XSI-compliant ver- sion specified in POSIX.1-2001 (available since glibc 2.3.4, but not POSIX-compliant until glibc 2.13), and a GNU-specific version (avail- able since glibc 2.0). The XSI-compliant version is provided with the feature test macros settings shown in the SYNOPSIS; otherwise the GNU-specific version is provided. If no feature test macros are explicitly defined, then (since glibc 2.4) _POSIX_C_SOURCE is defined by default with the value 200112L, so that the XSI-compliant version of strerror_r() is provided by default. The XSI-compliant strerror_r() is preferred for portable applications. It returns the error string in the user-supplied buffer buf of length buflen. The GNU-specific strerror_r() returns a pointer to a string containing the error message. This may be either a pointer to a string that the function stores in buf, or a pointer to some (immutable) static string (in which case buf is unused). If the function stores a string in buf, then at most buflen bytes are stored (the string may be truncated if buflen is too small and errnum is unknown). The string always includes a terminating null byte (''). strerror_l() strerror_l() is like strerror(), but maps errnum to a locale-dependent error message in the locale specified by locale. The behavior of strerror_l() is undefined if locale is the special locale object LC_GLOBAL_LOCALE or is not a valid locale object handle. RETURN VALUE
The strerror(), strerror_l(), and the GNU-specific strerror_r() functions return the appropriate error description string, or an "Unknown error nnn" message if the error number is unknown. The XSI-compliant strerror_r() function returns 0 on success. On error, a (positive) error number is returned (since glibc 2.13), or -1 is returned and errno is set to indicate the error (glibc versions before 2.13). POSIX.1-2001 and POSIX.1-2008 require that a successful call to strerror() or strerror_l() shall leave errno unchanged, and note that, since no function return value is reserved to indicate an error, an application that wishes to check for errors should initialize errno to zero before the call, and then check errno after the call. ERRORS
EINVAL The value of errnum is not a valid error number. ERANGE Insufficient storage was supplied to contain the error description string. VERSIONS
The strerror_l() function first appeared in glibc 2.6. ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7). +---------------+---------------+-------------------------+ |Interface | Attribute | Value | +---------------+---------------+-------------------------+ |strerror() | Thread safety | MT-Unsafe race:strerror | +---------------+---------------+-------------------------+ |strerror_r(), | Thread safety | MT-Safe | |strerror_l() | | | +---------------+---------------+-------------------------+ CONFORMING TO
strerror() is specified by POSIX.1-2001, POSIX.1-2008, C89, and C99. strerror_r() is specified by POSIX.1-2001 and POSIX.1-2008. strerror_l() is specified in POSIX.1-2008. The GNU-specific strerror_r() function is a nonstandard extension. POSIX.1-2001 permits strerror() to set errno if the call encounters an error, but does not specify what value should be returned as the function result in the event of an error. On some systems, strerror() returns NULL if the error number is unknown. On other systems, str- error() returns a string something like "Error nnn occurred" and sets errno to EINVAL if the error number is unknown. C99 and POSIX.1-2008 require the return value to be non-NULL. NOTES
The GNU C Library uses a buffer of 1024 characters for strerror(). This buffer size therefore should be sufficient to avoid an ERANGE error when calling strerror_r() and strerror_l(). SEE ALSO
err(3), errno(3), error(3), perror(3), strsignal(3), locale(7) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. 2017-09-15 STRERROR(3)
All times are GMT -4. The time now is 02:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy