Sponsored Content
Full Discussion: ${bindir} vs $bindir
Top Forums UNIX for Dummies Questions & Answers ${bindir} vs $bindir Post 43122 by Perderabo on Wednesday 12th of November 2003 12:39:30 AM
Old 11-12-2003
I would always go with "${bindir}/exc" rather than "$bindir/exc" because the former is more readable. I use understandable variable names, blank lines, superfluous parentheses, etc for the same reason.

And yes, the more readable the code, the fewer the errors.... made by the programmmer. Write a complex program with dozens of variables but only use the letters x and y in your variable names. This won't matter to the computer, but it matters a lot to the programmer. You will have many more errors than if you had used readable variable names.
 
PTH-CONFIG(1)						       GNU Portable Threads						     PTH-CONFIG(1)

NAME
pth-config - Pth library build utility VERSION
GNU Pth 2.0.7 (08-Jun-2006) SYNOPSIS
pth-config [--help] [--version] [--all] [--prefix] [--exec-prefix] [--bindir] [--libdir] [--includedir] [--mandir] [--datadir] [--acdir] [--cflags] [--ldflags] [--libs] DESCRIPTION
The pth-config program is a little helper utility for easy configuring and building applications based on the pth(3) library. It can be used to query the C compiler and linker flags which are required to correctly compile and link the application against the pth(3) library. OPTIONS
pth-config accepts the following options: --help Prints the short usage information. --version Prints the version number and date of the installed pth(3) library. --all Forces the output of all flags, that is, including extra flags which are not Pth specific. --prefix Prints the installation prefix of architecture independent files --exec-prefix Prints the installation prefix of architecture dependent files. --bindir Prints the installation directory of binaries. --libdir Prints the installation directory of libraries. --includedir Prints the installation directory of include headers. --mandir Prints the installation directory of manual pages. --datadir Prints the installation directory of shared data. --acdir Prints the installation directory of autoconf data. --cflags Prints the C compiler flags which are needed to compile the pth(3)-based application. The output is usually added to the "CFLAGS" vari- able of the applications "Makefile". --ldflags Prints the linker flags ("-L") which are needed to link the application with the pth(3) library. The output is usually added to the "LDFLAGS" variable of the applications "Makefile". --libs Prints the library flags ("-l") which are needed to link the application with the pth(3) library. The output is usually added to the "LIBS" variable of the applications "Makefile". EXAMPLE
CC = cc CFLAGS = -O `pth-config --cflags` LDFLAGS = `pth-config --ldflags` LIBS = -lm `pth-config --libs` all: foo foo: foo.o $(CC) $(LDFLAGS) -o foo foo.o $(LIBS) foo.o: foo.c $(CC) $(CFLAGS) -c foo.c SEE ALSO
pth(3), cc(1). AUTHOR
Ralf S. Engelschall rse@engelschall.com www.engelschall.com 08-Jun-2006 GNU Pth 2.0.7 PTH-CONFIG(1)
All times are GMT -4. The time now is 05:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy