units-2.12/ 0000777 0001750 0001750 00000000000 12607610576 012074 5 ustar adrian adrian units-2.12/Makefile.in 0000664 0001750 0001750 00000022171 12321651015 014124 0 ustar adrian adrian # Makefile for units, a program for units conversion
#
# Copyright (C) 1996, 1997, 1999, 2005, 2006, 2012, 2014
# Free Software Foundation, Inc
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
#
#
# This program was written by Adrian Mariano (adrianm@gnu.org)
#
@MKSFIX@
SHELL = /bin/sh
prefix = @prefix@
exec_prefix = @exec_prefix@
srcdir = @srcdir@
CC = @CC@
INSTALL = @INSTALL@
INSTALL_DATA = @INSTALL_DATA@
INSTALL_PROGRAM = @INSTALL_PROGRAM@
MAKEINFO = makeinfo
TEXI2DVI = texi2dvi
TEXI2PDF = texi2pdf
MKDIR_P = @MKDIR_P@
LDFLAGS = @LDFLAGS@
LIBS= @LIBS@
VPATH = @srcdir@
HAVE_PYTHON = @HAVE_PYTHON@
PYTHON = @PYTHON@
datarootdir = @datarootdir@
datadir = @datadir@
bindir = @bindir@
infodir = @infodir@
mandir = @mandir@
transform=@program_transform_name@
DEFS=-DUNITSFILE=\"@UDAT@definitions.units\" -DLOCALEMAP=\"@UDAT@locale_map.txt\" \
@DEFIS@ @DEFS@
CFLAGS = @CFLAGS@
OBJECTS = units.@OBJEXT@ parse.tab.@OBJEXT@ getopt.@OBJEXT@ getopt1.@OBJEXT@ @STRFUNC@
.SUFFIXES:
.SUFFIXES: .c .@OBJEXT@
.c.@OBJEXT@:
$(CC) $(DEFS) $(CPPFLAGS) $(CFLAGS) -I$(srcdir) -c $<
# %.@OBJEXT@: %.c
# $(CC) $(DEFS) $(CFLAGS) -I$(srcdir) -c %.c
DISTFILES = README ChangeLog units.info units.txt getopt1.c units.dvi \
Makefile.in units.c getopt.c getopt.h definitions.units units.texinfo \
configure.ac configure strfunc.c COPYING Makefile.Win install-sh \
units.man NEWS texi2man INSTALL units.pdf units_cur2 units_cur3 \
parse.tab.c parse.y units.h Makefile.OS2 makeobjs.cmd README.OS2 \
README.MKS locale_map.txt fdl-1.3.texi currency.units README.Win \
unitsfile.ico unitsprog.ico icon_ms.png winmkdirs.bat
all: units@EXEEXT@ units.1 units.info units_cur_inst
units.@OBJEXT@: units.c units.h
parse.tab.c: parse.y
bison parse.y
parse.tab.@OBJEXT@: parse.tab.c
units@EXEEXT@: $(OBJECTS)
$(CC) $(CFLAGS) $(LDFLAGS) -o units@EXEEXT@ $(OBJECTS) $(LIBS)
units_cur: units_cur2 units_cur3
@if test $(HAVE_PYTHON) = no; then \
$(MAKE) units_cur_dummy; \
else \
version=`$(PYTHON) --version 2>&1`; \
if echo $$version | grep 'Python 2' >/dev/null; then \
cp $(srcdir)/units_cur2 units_cur; \
echo Creating units_cur for Python 2; \
elif echo $$version | grep 'Python 3'>/dev/null; then \
cp $(srcdir)/units_cur3 units_cur; \
echo Creating units_cur for Python 3; \
else \
echo Unrecognized Python version: $$version; \
echo Unable to create correct units_cur; \
exit 1; \
fi; \
fi
units_cur_dummy:
echo '\#!/bin/sh' > units_cur
echo 'echo Units_cur requires python, which was not found when units was configured' >> units_cur
chmod +x units_cur
units_cur3: units_cur2
-mkdir python3_tempdir
2to3 --no-diffs -n -o python3_tempdir -w units_cur2
mv python3_tempdir/units_cur2 units_cur3
rm -rf python3_tempdir
units_cur_inst: units_cur
sed -e "s@outfile = 'currency.units'@outfile='@UDAT@currency.units'@"\
-e "s@/usr/bin/python@$(PYTHON)@" \
units_cur > units_cur_inst
install-support: definitions.units currency.units units_cur_inst
$(MKDIR_P) $(DESTDIR)@UDAT@ $(DESTDIR)$(bindir)
$(INSTALL_DATA) $(srcdir)/definitions.units $(DESTDIR)@UDAT@definitions.units
$(INSTALL_DATA) $(srcdir)/currency.units $(DESTDIR)@UDAT@currency.units
$(INSTALL_DATA) $(srcdir)/locale_map.txt $(DESTDIR)@UDAT@locale_map.txt
if test $(HAVE_PYTHON) = yes; then \
$(INSTALL_PROGRAM) units_cur_inst $(DESTDIR)$(bindir)/`echo units_cur|sed '$(transform)'`;fi
install: units@EXEEXT@ install-doc install-support
$(MKDIR_P) $(DESTDIR)$(bindir)
$(INSTALL_PROGRAM) units@EXEEXT@ $(DESTDIR)$(bindir)/`echo units@EXEEXT@|sed '$(transform)'`
install-strip: units@EXEEXT@ install-doc install-support
$(MKDIR_P) $(DESTDIR)$(bindir)
$(INSTALL_PROGRAM) -s units@EXEEXT@ $(DESTDIR)$(bindir)/`echo units@EXEEXT@|sed '$(transform)'`
install-doc: install-man install-info
install-man: units.1
$(MKDIR_P) $(DESTDIR)$(mandir)/man1
$(INSTALL_DATA) units.1 $(DESTDIR)$(mandir)/man1/`echo units|sed '$(transform)'`.1
units.man: units.texinfo texi2man
./texi2man units.texinfo > units.man
units.1: units.man
sed s!@DATAFILE@!@UDAT@definitions.units! $(srcdir)/units.man > units.1
install-info: $(DESTDIR)$(infodir)/units.info
$(DESTDIR)$(infodir)/units.info: units.info
$(POST_INSTALL)
$(MKDIR_P) $(DESTDIR)$(infodir)
# There may be a newer info file in . than in srcdir.
-if test -f units.info; then d=.; \
else d=$(srcdir); fi; \
$(INSTALL_DATA) $$d/units.info $@; \
# Run install-info only if it exists.
# Use `if' instead of just prepending `-' to the
# line so we notice real errors from install-info.
# We use `$(SHELL) -c' because some shells do not
# fail gracefully when there is an unknown command.
if test -f $(DESTDIR)$(infodir)/dir; then \
if $(SHELL) -c 'install-info --version' \
>/dev/null 2>&1; then \
install-info --dir-file=$(DESTDIR)$(infodir)/dir \
$(DESTDIR)$(infodir)/units.info; \
else true; fi \
else true; fi
Makefile: Makefile.in config.status
./config.status
uninstall:
-rm -f $(DESTDIR)$(bindir)/`echo units@EXEEXT@|sed '$(transform)'` \
$(DESTDIR)$(mandir)/man1/`echo units|sed '$(transform)'`.1 \
$(DESTDIR)$(infodir)/units.info \
$(DESTDIR)@UDAT@definitions.units \
$(DESTDIR)@UDAT@currency.units \
$(DESTDIR)@UDAT@locale_map.txt \
$(DESTDIR)$(bindir)/`echo units_cur|sed '$(transform)'`
-rmdir $(DESTDIR)@UDAT@
@if test -f $(DESTDIR)$(infodir)/dir; then \
echo You may need to remove units.info from $(DESTDIR)$(infodir)/dir; \
else true; fi
clean mostlyclean:
-rm -f *.@OBJEXT@ units@EXEEXT@ units.fn units.ky units.pg units.tp \
units.vr units.log units.dvi units.1 units.cp distname .chk \
units.toc units.aux units.cps units.op units_cur_inst units_cur
distclean: clean
-rm -f config.* Makefile TAGS
maintainer-clean: clean
-rm -f units.txt units.info units.pdf units.dvi \
units-*.tar.gz parse.tab.c currency.units
currency.units: units_cur
@echo "Trying to update currency.units (will use existing file if this fails)"
-./units_cur
sig:
echo units-`sed -n -e '/\#.*VERSION/s/.*"\(.*\)"/\1/gp' \
$(srcdir)/units.c`.tar.gz > distname
echo 'version: 1.2' > `cat distname`.directive
echo 'directory: units' >> `cat distname`.directive
echo 'filename: '`cat distname` >> `cat distname`.directive
gpg --clearsign `cat distname`.directive
gpg -b `cat distname`
-rm -f `cat distname`.directive distname
dist: $(DISTFILES) units_cur
@./units_cur
@echo Updated currencies, running check:
./units -f definitions.units -c
@echo ''
@chmod g+rw,o+r *
@echo units-`sed -n -e '/\#.*VERSION/s/.*"\(.*\)"/\1/gp' \
$(srcdir)/units.c` > distname
-@if [ -d `cat distname` ]; then rm -r `cat distname`; fi
-@if [ -e `cat distname`.tar.gz ]; then rm `cat distname`.tar.gz; fi
@mkdir `cat distname`
@dst=`cat distname`; for f in $(DISTFILES); do \
ln $(srcdir)/$$f $$dst/$$f || { echo copying $$f; \
cp -p $(srcdir)/$$f $$dst/$$f ; } \
done
@chmod 777 `cat distname`
@tar czf `cat distname`.tar.gz `cat distname`
@echo `cat distname`.tar.gz created
-@rm -rf `cat distname` distname
dvi: units.dvi
pdf: units.pdf
units.dvi: units.texinfo
$(TEXI2DVI) $(srcdir)/units.texinfo
units.pdf: units.texinfo
$(TEXI2PDF) $(srcdir)/units.texinfo
info: units.info
units.info: units.texinfo
$(MAKEINFO) $(srcdir)/units.texinfo
units.txt: units.1
nroff -Tascii -man $(srcdir)/units.1 | col -b > units.txt
doc: units.dvi units.info units.txt units.pdf
check: all
@echo Checking units
@./units -f $(srcdir)/definitions.units \
'(((square(kiloinch)+2.84m2) /0.5) meters^2)^(1|4)' m \
| sed -n -e 's/ \* //p' > .chk
@if [ "`cat .chk`" = 6 ]; then echo Units seems to work; \
else echo Something is wrong: units failed the check: ;cat .chk; fi
@rm -f .chk
configure: configure.ac
autoconf
TAGS: units.c
etags $(srcdir)/units.c $(srcdir)/parse.y
tags: units.c
ctags $(srcdir)/units.c
smalldist: units.c units.h parse.y parse.tab.c
echo units-`sed -n -e '/\#.*VERSION/s/.*"\(.*\)"/\1/gp' \
$(srcdir)/units.c` > distname
-rm -r `cat distname` `cat distname`.tar `cat distname`.tar.gz
tar cf `cat distname`.tar units.c units.h parse.y parse.tab.c\
getopt1.c getopt.c getopt.h
gzip `cat distname`.tar
#
# Not very portable code to compile into library (written for Linux)
#
libunits.a: $(OBJECTS)
ar -r libunits.a $^
libunits.so: $(OBJECTS)
$(CC) $(LDFLAGS) -shared -o $@ $^
# Tell versions [3.59,3.63) of GNU make not to export all variables.
# Otherwise a system limit (for SysV at least) may be exceeded.
.NOEXPORT:
units-2.12/COPYING 0000664 0001750 0001750 00000104513 10642156735 013130 0 ustar adrian adrian GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc.
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
Copyright (C)
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see .
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
Copyright (C)
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
.
units-2.12/strfunc.c 0000664 0001750 0001750 00000004231 10641165333 013712 0 ustar adrian adrian /*
* Copyright (C) 1996 Free Software Foundation, Inc
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 3 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*
*/
#define NULL 0
#define size_t int
#ifdef NO_STRTOK
/* Find the first ocurrence in S of any character in ACCEPT. */
char *
strpbrk(char *s, char *accept)
{
while (*s != '\0')
if (strchr(accept, *s) == NULL)
++s;
else
return (char *) s;
return NULL;
}
static char *olds = NULL;
char *
strtok(char *s, char *delim)
{
char *token;
if (s == NULL)
{
if (olds == NULL)
{
/*errno = EINVAL; Wonder where errno is defined....*/
return NULL;
}
else
s = olds;
}
/* Scan leading delimiters. */
s += strspn(s, delim);
if (*s == '\0')
{
olds = NULL;
return NULL;
}
/* Find the end of the token. */
token = s;
s = strpbrk(token, delim);
if (s == NULL)
/* This token finishes the string. */
olds = NULL;
else
{
/* Terminate the token and make OLDS point past it. */
*s = '\0';
olds = s + 1;
}
return token;
}
#endif /* NO_STRTOK */
#ifdef NO_STRSPN
/* Return the length of the maximum initial segment
of S which contains only characters in ACCEPT. */
size_t
strspn(char *s, char *accept)
{
register char *p;
register char *a;
register size_t count = 0;
for (p = s; *p != '\0'; ++p)
{
for (a = accept; *a != '\0'; ++a)
if (*p == *a)
break;
if (*a == '\0')
return count;
else
++count;
}
return count;
}
#endif NO_STRSPN
units-2.12/README.MKS 0000664 0001750 0001750 00000004540 12316637516 013406 0 ustar adrian adrian This comments in this file are based on MKS Toolkit for developers,
version 9.6, running on Windows XP Professional, SP3. The configure
script was generated by GNU Autoconf 2.68.
The most recent build of units with the Toolkit (using Microsoft Visual
C/C++ 6.0, and Visual C/C++ Express 9.0 and 10.0) was for version 2.11
on 24 March 2014.
The system on which the build was done had /bin as a symbolic link to
C:/Program Files/MKS Toolkit/mksnt.
-- Jeff Conrad (jeff_conrad@msn.com) 1 April 2014
Configure
---------
Configure will fail unless invoked as
./configure PATH_SEPARATOR=';'
Compilation
-----------
The MKS version of make ignores suffix rules in Makefile unless the line
.POSIX:
appears in Makefile before any suffix rules. This target is also
required for the currency updater units_cur to run properly from
Makefile. The configure script attempts to detect the Toolkit by
running mksinfo, and if this succeeds, the .POSIX target is added. If
you have the MKS Toolkit and it somehow is not detected, you should add
this line manually.
Behavior of PAGER
-----------------
The MKS versions of more and less do not recognize '+n' as an option to
display a file beginning at line n, so help from within units
will fail. If configure is able to detect the Toolkit by running
mksinfo,
-DHAVE_MKS_TOOLKIT
is added to the DEFS in Makefile. If you have the MKS Toolkit and it
somehow is not detected, you should add this manually.
Install Program
---------------
If the PATH at shell invocation uses the backslash as the path
separator, and you have a BSD-compatible install program, the Makefile
may have the incorrect entry
INSTALL = c:usrlocalbin/install.exe -c
Add the slashes to get
INSTALL = c:/usr/local/bin/install.exe -c
Giving a PATH with forward slashes in a file given by ENV will have no
effect because configure unsets that variable, and the file will not be
read.
Python and units_cur
--------------------
If python is installed, a copy of python.exe must be placed in /usr/bin
so the shell can find it. Alternatively, you can change the first line
of units_cur to specify the location of the python executable.
The complete pathname in Makefile may contain backslashes; for example,
PYTHON = C:\usr\bin/python.exe
The build will fail unless the backslashes are changed to forward
slashes:
PYTHON = C:/usr/bin/python.exe
units-2.12/icon_ms.png 0000664 0001750 0001750 00000000516 12312651560 014220 0 ustar adrian adrian PNG
IHDR ѓџa sRGB ЎЮ щ bKGD џ џ џ НЇ pHYs tIMEмC%+ ЮIDAT8ЫгНjBAс'Rк:XJHSЄГА$з`ЁМxжFmьX& XXiГВ ? ,ьЬ№~3ЬВ\A;tБФ/шр?x,b№
ки Ф_GИд ЅHМР}ЌГ NїCwчє"ѕТI .Њрtф\xїpЏg§У<?ЊUиzЊ)ИC
will complete unit names. *Note Readline Support::, for more
information about 'readline'. To quit the program under Unix, press
or . Under Windows, press or ; with
the latter, you may also need to press .
The result will be displayed in two ways. The first line of output,
which is marked with a '*' to indicate multiplication, gives the result
of the conversion you have asked for. The second line of output, which
is marked with a '/' to indicate division, gives the inverse of the
conversion factor. If you convert 10 meters to feet, 'units' will print
* 32.808399
/ 0.03048
which tells you that 10 meters equals about 32.8 feet. The second
number gives the conversion in the opposite direction. In this case, it
tells you that 1 foot is equal to about 0.03 dekameters since the
dekameter is 10 meters. It also tells you that 1/32.8 is about 0.03.
The 'units' program prints the inverse because sometimes it is a more
convenient number. In the example above, for example, the inverse value
is an exact conversion: a foot is exactly 0.03048 dekameters. But the
number given the other direction is inexact.
If you convert grains to pounds, you will see the following:
You have: grains
You want: pounds
* 0.00014285714
/ 7000
From the second line of the output you can immediately see that a grain
is equal to a seven thousandth of a pound. This is not so obvious from
the first line of the output. If you find the output format confusing,
try using the '--verbose' option:
You have: grain
You want: aeginamina
grain = 0.00010416667 aeginamina
grain = (1 / 9600) aeginamina
If you request a conversion between units that measure reciprocal
dimensions, then 'units' will display the conversion results with an
extra note indicating that reciprocal conversion has been done:
You have: 6 ohms
You want: siemens
reciprocal conversion
* 0.16666667
/ 6
Reciprocal conversion can be suppressed by using the '--strict' option.
As usual, use the '--verbose' option to get more comprehensible output:
You have: tex
You want: typp
reciprocal conversion
1 / tex = 496.05465 typp
1 / tex = (1 / 0.0020159069) typp
You have: 20 mph
You want: sec/mile
reciprocal conversion
1 / 20 mph = 180 sec/mile
1 / 20 mph = (1 / 0.0055555556) sec/mile
If you enter incompatible unit types, the 'units' program will print a
message indicating that the units are not conformable and it will
display the reduced form for each unit:
You have: ergs/hour
You want: fathoms kg^2 / day
conformability error
2.7777778e-11 kg m^2 / sec^3
2.1166667e-05 kg^2 m / sec
If you only want to find the reduced form or definition of a unit,
simply press at the 'You want:' prompt. Here is an example:
You have: jansky
You want:
Definition: fluxunit = 1e-26 W/m^2 Hz = 1e-26 kg / s^2
The output from 'units' indicates that the jansky is defined to be equal
to a fluxunit which in turn is defined to be a certain combination of
watts, meters, and hertz. The fully reduced (and in this case somewhat
more cryptic) form appears on the far right.
Some named units are treated as dimensionless in some situations.
These units include the radian and steradian. These units will be
treated as equal to 1 in units conversions. Power is equal to torque
times angular velocity. This conversion can only be performed if the
radian is dimensionless.
You have: (14 ft lbf) (12 radians/sec)
You want: watts
* 227.77742
/ 0.0043902509
It is also possible to compute roots and other non-integer powers of
dimensionless units; this allows computations such as the altitude of
geosynchronous orbit:
You have: cuberoot(G earthmass / (circle/siderealday)^2) - earthradius
You want: miles
* 22243.267
/ 4.4957425e-05
Named dimensionless units are not treated as dimensionless in other
contexts. They cannot be used as exponents so for example,
'meter^radian' is forbidden.
If you want a list of options you can type '?' at the 'You want:'
prompt. The program will display a list of named units that are
conformable with the unit that you entered at the 'You have:' prompt
above. Conformable unit _combinations_ will not appear on this list.
Typing 'help' at either prompt displays a short help message. You
can also type 'help' followed by a unit name. This will invoke a pager
on the units data base at the point where that unit is defined. You can
read the definition and comments that may give more details or
historical information about the unit. (You can generally quit out of
the page by pressing 'q'.)
Typing 'search' TEXT will display a list of all of the units whose
names contain TEXT as a substring along with their definitions. This
may help in the case where you aren't sure of the right unit name.
File: units.info, Node: Command Line Use, Next: Unit Definitions, Prev: Interactive Use, Up: Top
3 Using 'units' Non-Interactively
*********************************
The 'units' program can perform units conversions non-interactively from
the command line. To do this, type the command, type the original unit
expression, and type the new units you want. If a units expression
contains non-alphanumeric characters, you may need to protect it from
interpretation by the shell using single or double quote characters.
If you type
units "2 liters" quarts
then 'units' will print
* 2.1133764
/ 0.47317647
and then exit. The output tells you that 2 liters is about 2.1 quarts,
or alternatively that a quart is about 0.47 times 2 liters.
If the conversion is successful, then 'units' will return success
(zero) to the calling environment. If you enter non-conformable units
then 'units' will print a message giving the reduced form of each unit
and it will return failure (nonzero) to the calling environment.
When you invoke 'units' with only one argument, it will print out the
definition of the specified unit. It will return failure if the unit is
not defined and success if the unit is defined.
File: units.info, Node: Unit Definitions, Next: Unit Expressions, Prev: Command Line Use, Up: Top
4 Unit Definitions
******************
The conversion information is read from a units data file that is called
'definitions.units' and is usually located in the '/usr/share/units'
directory. If you invoke 'units' with the '-V' option, it will print
the location of this file. The default file includes definitions for
all familiar units, abbreviations and metric prefixes. It also includes
many obscure or archaic units.
Many constants of nature are defined, including these:
pi ratio of circumference to diameter
c speed of light
e charge on an electron
force acceleration of gravity
mole Avogadro's number
water pressure per unit height of water
Hg pressure per unit height of mercury
au astronomical unit
k Boltzman's constant
mu0 permeability of vacuum
epsilon0 permittivity of vacuum
G Gravitational constant
mach speed of sound
The standard data file includes atomic masses for all of the elements
and numerous other constants. Also included are the densities of
various ingredients used in baking so that '2 cups flour_sifted' can be
converted to 'grams'. This is not an exhaustive list. Consult the
units data file to see the complete list, or to see the definitions that
are used.
The 'pound' is a unit of mass. To get force, multiply by the force
conversion unit 'force' or use the shorthand 'lbf'. (Note that 'g' is
already taken as the standard abbreviation for the gram.) The unit
'ounce' is also a unit of mass. The fluid ounce is 'fluidounce' or
'floz'. When British capacity units differ from their US counterparts,
such as the British Imperial gallon, the unit is defined both ways with
'br' and 'us' prefixes. Your locale settings will determine the value
of the unprefixed unit. Currency is prefixed with its country name:
'belgiumfranc', 'britainpound'.
When searching for a unit, if the specified string does not appear
exactly as a unit name, then the 'units' program will try to remove a
trailing 's', 'es'. Next units will replace a trailing 'ies' with 'y'.
If that fails, 'units' will check for a prefix. The database includes
all of the standard metric prefixes. Only one prefix is permitted per
unit, so 'micromicrofarad' will fail. However, prefixes can appear
alone with no unit following them, so 'micro*microfarad' will work, as
will 'micro microfarad'.
To find out which units and prefixes are available, read the standard
units data file, which is extensively annotated.
4.1 English Customary Units
===========================
English customary units differ in various ways in different regions. In
Britain a complex system of volume measurements featured different
gallons for different materials such as a wine gallon and ale gallon
that different by twenty percent. This complexity was swept away in
1824 by a reform that created an entirely new gallon, the British
Imperial gallon defined as the volume occupied by ten pounds of water.
Meanwhile in the USA the gallon is derived from the 1707 Winchester wine
gallon, which is 231 cubic inches. These gallons differ by about twenty
percent. By default if 'units' runs in the 'en_GB' locale you will get
the British volume measures. If it runs in the 'en_US' locale you will
get the US volume measures. In other locales the default values are the
US definitions. If you wish to force different definitions then set the
environment variable 'UNITS_ENGLISH' to either 'US' or 'GB' to set the
desired definitions independent of the locale.
Before 1959, the value of a yard (and other units of measure defined
in terms of it) differed slightly among English-speaking countries. In
1959, Australia, Canada, New Zealand, the United Kingdom, the United
States, and South Africa adopted the Canadian value of 1 yard = 0.9144 m
(exactly), which was approximately halfway between the values used by
the UK and the US; it had the additional advantage of making 1 inch =
2.54 cm (exactly). This new standard was termed the "International
Yard". Australia, Canada, and the UK then defined all customary lengths
in terms of the International Yard (Australia did not define the furlong
or rod); because many US land surveys were in terms of the pre-1959
units, the US continued to define customary surveyors' units (furlong,
chain, rod, and link) in terms of the previous value for the foot, which
was termed the "US survey foot". The US defined a "US survey mile" as
5280 US survey feet, and defined a "statute mile" as a US survey mile.
The US values for these units differ from the international values by
about 2 ppm.
The 'units' program uses the international values for these units;
the US values can be obtained by using either the 'US' or the 'survey'
prefix. In either case, the simple familiar relationships among the
units are maintained, e.g., 1 'furlong' = 660 'ft', and 1 'USfurlong' =
660 'USft', though the metric equivalents differ slightly between the
two cases. The 'US' prefix or the 'survey' prefix can also be used to
obtain the US survey mile and the value of the US yard prior to 1959,
e.g., 'USmile' or 'surveymile' (but _not_ 'USsurveymile'). To get the
US value of the statute mile, use either 'USstatutemile' or 'USmile'.
Except for distances that extend over hundreds of miles (such as in
the US State Plane Coordinate System), the differences in the miles are
usually insignificant:
You have: 100 surveymile - 100 mile
You want: inch
* 12.672025
/ 0.078913984
The pre-1959 UK values for these units can be obtained with the prefix
'UK'.
In the US, the acre is officially defined in terms of the US survey
foot, but 'units' uses a definition based on the international foot. If
you want the official US acre use 'USacre' and similarly use
'USacrefoot' for the official US version of that unit. The difference
between these units is about 4 parts per million.
File: units.info, Node: Unit Expressions, Next: Nonlinear Conversions, Prev: Unit Definitions, Up: Top
5 Unit Expressions
******************
* Menu:
* Operators:: The usual arithmetic operators, with a few extras
* Sums and Differences of Units:: Adding and subtracting units
* Numbers as Units:: A number is a dimensionless unit
* Built-in Functions:: Trigonometric functions, logarithms, roots
* Previous Result:: Inserting the result of the previous conversion
* Complicated Unit Expressions:: A complicated example
* Backwards Compatibility:: Alternate behavior for '*' and '-'
File: units.info, Node: Operators, Next: Sums and Differences of Units, Up: Unit Expressions
5.1 Operators
=============
You can enter more complicated units by combining units with operations
such as multiplication, division, powers, addition, subtraction, and
parentheses for grouping. You can use the customary symbols for these
operators when 'units' is invoked with its default options.
Additionally, 'units' supports some extensions, including high priority
multiplication using a space, and a high priority numerical division
operator ('|') that can simplify some expressions.
You multiply units using a space or an asterisk ('*'). The next
example shows both forms:
You have: arabicfoot * arabictradepound * force
You want: ft lbf
* 0.7296
/ 1.370614
You can divide units using the slash ('/') or with 'per':
You have: furlongs per fortnight
You want: m/s
* 0.00016630986
/ 6012.8727
You can use parentheses for grouping:
You have: (1/2) kg / (kg/meter)
You want: league
* 0.00010356166
/ 9656.0833
Multiplication using a space has a higher precedence than division using
a slash and is evaluated left to right; in effect, the first '/'
character marks the beginning of the denominator of a unit expression.
This makes it simple to enter a quotient with several terms in the
denominator: 'J / mol K'. The '*' and '/' operators have the same
precedence, and are evaluated left to right; if you multiply with '*',
you must group the terms in the denominator with parentheses:
'J / (mol * K)'.
The higher precedence of the space operator may not always be
advantageous. For example, 'm/s s/day' is equivalent to 'm / s s day'
and has dimensions of length per time cubed. Similarly, '1/2 meter'
refers to a unit of reciprocal length equivalent to 0.5/meter, perhaps
not what you would intend if you entered that expression. The get a
half meter you would need to use parentheses: '(1/2) meter'. The '*'
operator is convenient for multiplying a sequence of quotients. For
example, 'm/s * s/day' is equivalent to 'm/day'. Similarly, you could
write '1/2 * meter' to get half a meter.
The 'units' program supports another option for numerical fractions:
you can indicate division of _numbers_ with the vertical bar ('|'), so
if you wanted half a meter you could write '1|2 meter'. You cannot use
the vertical bar to indicate division of non-numerical units (e.g.,
'm|s' results in an error message).
Powers of units can be specified using the '^' character, as shown in
the following example, or by simple concatenation of a unit and its
exponent: 'cm3' is equivalent to 'cm^3'; if the exponent is more than
one digit, the '^' is required. You can also use '**' as an exponent
operator.
You have: cm^3
You want: gallons
* 0.00026417205
/ 3785.4118
Concatenation only works with a single unit name: if you write '(m/s)2',
'units' will treat it as multiplication by 2. When a unit includes a
prefix, exponent operators apply to the combination, so 'centimeter3'
gives cubic centimeters. If you separate the prefix from the unit with
any multiplication operator (e.g., 'centi meter^3'), the prefix is
treated as a separate unit, so the exponent applies only to the unit
without the prefix. The second example is equivalent to 'centi *
(meter^3)', and gives a hundredth of a cubic meter, not a cubic
centimeter. The 'units' program is limited internally to products of 99
units; accordingly, expressions like 'meter^100' or 'joule^34'
(represented internally as 'kg^34 m^68 / s^68') will fail.
The '|' operator has the highest precedence, so you can write the
square root of two thirds as '2|3^1|2'. The '^' operator has the second
highest precedence, and is evaluated right to left, as usual:
You have: 5 * 2^3^2
You want:
Definition: 2560
With a dimensionless base unit, any dimensionless exponent is meaningful
(e.g., 'pi^exp(2.371)'). Even though angle is sometimes treated as
dimensionless, exponents cannot have dimensions of angle:
You have: 2^radian
^
Exponent not dimensionless
If the base unit is not dimensionless, the exponent must be a rational
number P/Q, and the dimension of the unit must be a power of Q, so
'gallon^2|3' works but 'acre^2|3' fails. An exponent using the slash
('/') operator (e.g., 'gallon^(2/3)') is also acceptable; the
parentheses are needed because the precedence of '^' is higher than that
of '/'. Since 'units' cannot represent dimensions with exponents
greater than 99, a fully reduced exponent must have Q < 100. When
raising a non-dimensionless unit to a power, 'units' attempts to convert
a decimal exponent to a rational number with Q < 100. If this is not
possible 'units' displays an error message:
You have: ft^1.234
Base unit not dimensionless; rational exponent required
A decimal exponent must match its rational representation to machine
precision, so 'acre^1.5' works but 'gallon^0.666' does not.
File: units.info, Node: Sums and Differences of Units, Next: Numbers as Units, Prev: Operators, Up: Unit Expressions
5.2 Sums and Differences of Units
=================================
You may sometimes want to add values of different units that are outside
the SI. You may also wish to use 'units' as a calculator that keeps
track of units. Sums of conformable units are written with the '+'
character, and differences with the '-' character.
You have: 2 hours + 23 minutes + 32 seconds
You want: seconds
* 8612
/ 0.00011611705
You have: 12 ft + 3 in
You want: cm
* 373.38
/ 0.0026782366
You have: 2 btu + 450 ft lbf
You want: btu
* 2.5782804
/ 0.38785542
The expressions that are added or subtracted must reduce to identical
expressions in primitive units, or an error message will be displayed:
You have: 12 printerspoint - 4 heredium
^
Illegal sum of non-conformable units
As usual, the precedence for '+' and '-' is lower than that of the other
operators. A fractional quantity such as 2 1/2 cups can be given as
'(2+1|2) cups'; the parentheses are necessary because multiplication has
higher precedence than addition. If you omit the parentheses, 'units'
attempts to add '2' and '1|2 cups', and you get an error message:
You have: 2+1|2 cups
^
Illegal sum or difference of non-conformable units
The expression could also be correctly written as '(2+1/2) cups'. If
you write '2 1|2 cups' the space is interpreted as _multiplication_ so
the result is the same as '1 cup'.
The '+' and '-' characters sometimes appears in exponents like
'3.43e+8'. This leads to an ambiguity in an expression like '3e+2 yC'.
The unit 'e' is a small unit of charge, so this can be regarded as
equivalent to '(3e+2) yC' or '(3 e)+(2 yC)'. This ambiguity is resolved
by always interpreting '+' and '-' as part of an exponent if possible.
File: units.info, Node: Numbers as Units, Next: Built-in Functions, Prev: Sums and Differences of Units, Up: Unit Expressions
5.3 Numbers as Units
====================
For 'units', numbers are just another kind of unit. They can appear as
many times as you like and in any order in a unit expression. For
example, to find the volume of a box that is 2 ft by 3 ft by 12 ft in
steres, you could do the following:
You have: 2 ft 3 ft 12 ft
You want: stere
* 2.038813
/ 0.49048148
You have: $ 5 / yard
You want: cents / inch
* 13.888889
/ 0.072
And the second example shows how the dollar sign in the units conversion
can precede the five. Be careful: 'units' will interpret '$5' with no
space as equivalent to 'dollar^5'.
File: units.info, Node: Built-in Functions, Next: Previous Result, Prev: Numbers as Units, Up: Unit Expressions
5.4 Built-in Functions
======================
Several built-in functions are provided: 'sin', 'cos', 'tan', 'ln',
'log', 'log2', 'exp', 'acos', 'atan' and 'asin'. The 'sin', 'cos', and
'tan' functions require either a dimensionless argument or an argument
with dimensions of angle.
You have: sin(30 degrees)
You want:
Definition: 0.5
You have: sin(pi/2)
You want:
Definition: 1
You have: sin(3 kg)
^
Unit not dimensionless
The other functions on the list require dimensionless arguments. The
inverse trigonometric functions return arguments with dimensions of
angle.
If you wish to take roots of units, you may use the 'sqrt' or
'cuberoot' functions. These functions require that the argument have
the appropriate root. You can obtain higher roots by using fractional
exponents:
You have: sqrt(acre)
You want: feet
* 208.71074
/ 0.0047913202
You have: (400 W/m^2 / stefanboltzmann)^(1/4)
You have:
Definition: 289.80882 K
You have: cuberoot(hectare)
^
Unit not a root
File: units.info, Node: Previous Result, Next: Complicated Unit Expressions, Prev: Built-in Functions, Up: Unit Expressions
5.5 Previous Result
===================
You can insert the result of the previous conversion using the
underscore ('_'). It is useful when you want to convert the same input
to several different units, for example
You have: 2.3 tonrefrigeration
You want: btu/hr
* 27600
/ 3.6231884e-005
You have: _
You want: kW
* 8.0887615
/ 0.12362832
Suppose you want to do some deep frying that requires an oil depth of
2 inches. You have 1/2 gallon of oil, and want to know the
largest-diameter pan that will maintain the required depth. The
nonlinear unit 'circlearea' gives the _radius_ of the circle (*note
Other Nonlinear Units::, for a more detailed description) in SI units;
you want the _diameter_ in _inches_:
You have: 1|2 gallon / 2 in
You want: circlearea
0.10890173 m
You have: 2 _
You want: in
* 8.5749393
/ 0.1166189
In most cases, surrounding white space is optional, so the previous
example could have used '2_'. If '_' follows a non-numerical unit
symbol, however, the space is required:
You have: m_
^
Parse error
When '_' is followed by a digit, the operation is multiplication rather
than exponentiation, so that '_2', is equivalent to '_ * 2' rather than
'_^2'.
You can use the '_' symbol any number of times; for example,
You have: m
You want:
Definition: 1 m
You have: _ _
You want:
Definition: 1 m^2
Using '_' before a conversion has been performed (e.g., immediately
after invocation) generates an error:
You have: _
^
No previous result; '_' not set
Accordingly, '_' serves no purpose when 'units' is invoked
non-interactively.
If 'units' is invoked with the '--verbose' option (*note Invoking
Units::), the value of '_' is not expanded:
You have: mile
You want: ft
mile = 5280 ft
mile = (1 / 0.00018939394) ft
You have: _
You want: m
_ = 1609.344 m
_ = (1 / 0.00062137119) m
You can give '_' at the 'You want:' prompt, but it usually is not very
useful.
File: units.info, Node: Complicated Unit Expressions, Next: Backwards Compatibility, Prev: Previous Result, Up: Unit Expressions
5.6 Complicated Unit Expressions
================================
The 'units' program is especially helpful in ensuring accuracy and
dimensional consistency when converting lengthy unit expressions. For
example, one form of the Darcy-Weisbach fluid-flow equation is
Delta P = (8/pi^2) rho f L (Q^2 / d^5)
where \Delta P is the pressure drop, \rho is the mass density, f is the
(dimensionless) friction factor, L is the length of the pipe, Q is the
volumetric flow rate, and d is the pipe diameter. It might be desired
to have the equation in the form
Delta P = A1 rho f L (Q^2 / d^5)
that accepted the user's normal units; for typical units used in the US,
the required conversion could be something like
You have: (8/pi^2)(lbm/ft^3)ft(ft^3/s)^2(1/in^5)
You want: psi
* 43.533969
/ 0.022970568
The parentheses allow individual terms in the expression to be entered
naturally, as they might be read from the formula. Alternatively, the
multiplication could be done with the '*' rather than a space; then
parentheses are needed only around 'ft^3/s' because of its exponent:
You have: 8/pi^2 * lbm/ft^3 * ft * (ft^3/s)^2 /in^5
You want: psi
* 43.533969
/ 0.022970568
Without parentheses, and using spaces for multiplication, the previous
conversion would need to be entered as
You have: 8 lb ft ft^3 ft^3 / pi^2 ft^3 s^2 in^5
You want: psi
* 43.533969
/ 0.022970568
File: units.info, Node: Backwards Compatibility, Prev: Complicated Unit Expressions, Up: Unit Expressions
5.7 Backwards Compatibility: '*' and '-'
========================================
The original 'units' assigned multiplication a higher precedence than
division using the slash. This differs from the usual precedence rules,
which give multiplication and division equal precedence, and can be
confusing for people who think of units as a calculator.
The star operator ('*') included in this 'units' program has, by
default, the same precedence as division, and hence follows the usual
precedence rules. For backwards compatibility you can invoke 'units'
with the '--oldstar' option. Then '*' has a higher precedence than
division, and the same precedence as multiplication using the space.
Historically, the hyphen ('-') has been used in technical
publications to indicate products of units, and the original 'units'
program treated it as a multiplication operator. Because 'units'
provides several other ways to obtain unit products, and because '-' is
a subtraction operator in general algebraic expressions, 'units' treats
the binary '-' as a subtraction operator by default. For backwards
compatibility use the '--product' option, which causes 'units' to treat
the binary '-' operator as a product operator. When '-' is a
multiplication operator it has the same precedence as multiplication
with a space, giving it a higher precedence than division.
When '-' is used as a unary operator it negates its operand.
Regardless of the 'units' options, if '-' appears after '(' or after '+'
then it will act as a negation operator. So you can always compute 20
degrees minus 12 minutes by entering '20 degrees + -12 arcmin'. You
must use this construction when you define new units because you cannot
know what options will be in force when your definition is processed.
File: units.info, Node: Nonlinear Conversions, Next: Unit Lists, Prev: Unit Expressions, Up: Top
6 Nonlinear Unit Conversions
****************************
Nonlinear units are represented using functional notation. They make
possible nonlinear unit conversions such as temperature.
* Menu:
* Temperature Conversions:: Conversion between temperature scales
* Other Nonlinear Units:: Ring size, wire gauge, abrasive grit size
File: units.info, Node: Temperature Conversions, Next: Other Nonlinear Units, Up: Nonlinear Conversions
6.1 Temperature Conversions
===========================
Conversions between temperatures are different from linear conversions
between temperature _increments_--see the example below. The absolute
temperature conversions are handled by units starting with 'temp', and
you must use functional notation. The temperature-increment conversions
are done using units starting with 'deg' and they do not require
functional notation.
You have: tempF(45)
You want: tempC
7.2222222
You have: 45 degF
You want: degC
* 25
/ 0.04
Think of 'tempF(X)' not as a function but as a notation that indicates
that X should have units of 'tempF' attached to it. *Note Defining
Nonlinear Units::. The first conversion shows that if it's 45 degrees
Fahrenheit outside, it's 7.2 degrees Celsius. The second conversion
indicates that a change of 45 degrees Fahrenheit corresponds to a change
of 25 degrees Celsius. The conversion from 'tempF(X)' is to absolute
temperature, so that
You have: tempF(45)
You want: degR
* 504.67
/ 0.0019814929
gives the same result as
You have: tempF(45)
You want: tempR
* 504.67
/ 0.0019814929
But if you convert 'tempF(X)' to 'degC', the output is probably not what
you expect:
You have: tempF(45)
You want: degC
* 280.37222
/ 0.0035666871
The result is the temperature in K, because 'degC' is defined as 'K',
the Kelvin. For consistent results, use the 'tempX' units when
converting to a temperature rather than converting a temperature
increment.
The 'tempC()' and 'tempF()' definitions are limited to positive
absolute temperatures, and giving a value that would result in a
negative absolute temperature generates an error message:
You have: tempC(-275)
^
Argument of function outside domain
^
File: units.info, Node: Other Nonlinear Units, Prev: Temperature Conversions, Up: Nonlinear Conversions
6.2 Other Nonlinear Units
=========================
Some other examples of nonlinear units are numerous different ring sizes
and wire gauges, the grit sizes used for abrasives, the decibel scale,
shoe size, scales for the density of sugar (e.g., baume). The standard
data file also supplies units for computing the area of a circle and the
volume of a sphere. See the standard units data file for more details.
Wire gauges with multiple zeroes are signified using negative numbers
where two zeroes is '-1'. Alternatively, you can use the synonyms
'g00', 'g000', and so on that are defined in the standard units data
file.
You have: wiregauge(11)
You want: inches
* 0.090742002
/ 11.020255
You have: brwiregauge(g00)
You want: inches
* 0.348
/ 2.8735632
You have: 1 mm
You want: wiregauge
18.201919
You have: grit_P(600)
You want: grit_ansicoated
342.76923
The last example shows the conversion from P graded sand paper, which is
the European standard and may be marked "P600" on the back, to the USA
standard.
You can compute the area of a circle using the nonlinear unit,
'circlearea'. You can also do this using the circularinch or
circleinch. The next example shows two ways to compute the area of a
circle with a five inch radius and one way to compute the volume of a
sphere with a radius of one meter.
You have: circlearea(5 in)
You want: in2
* 78.539816
/ 0.012732395
You have: 10^2 circleinch
You want: in2
* 78.539816
/ 0.012732395
You have: spherevol(meter)
You want: ft3
* 147.92573
/ 0.0067601492
The inverse of a nonlinear conversion is indicated by prefixing a tilde
('~') to the nonlinear unit name:
You have: ~wiregauge(0.090742002 inches)
You want:
Definition: 11
You can give a nonlinear unit definition without an argument or
parentheses, and press at the 'You want:' prompt to get the
definition of a nonlinear unit; if the definition is not valid for all
real numbers, the range of validity is also given. If the definition
requires specific units this information is also displayed:
You have: tempC
Definition: tempC(x) = x K + stdtemp
defined for x >= -273.15
You have: ~tempC
Definition: ~tempC(tempC) = (tempC +(-stdtemp))/K
defined for tempC >= 0 K
You have: circlearea
Definition: circlearea(r) = pi r^2
r has units m
To see the definition of the inverse use the '~' notation. In this case
the parameter in the functional definition will usually be the name of
the unit. Note that the inverse for 'tempC' shows that it requires
units of 'K' in the specification of the allowed range of values.
Nonlinear unit conversions are described in more detail in *note
Defining Nonlinear Units::.
File: units.info, Node: Unit Lists, Next: Logging Calculations, Prev: Nonlinear Conversions, Up: Top
7 Unit Lists: Conversion to Sums of Units
*****************************************
Outside of the SI, it is sometimes desirable to convert a single unit to
a sum of units--for example, feet to feet plus inches. The conversion
_from_ sums of units was described in *note Sums and Differences of
Units::, and is a simple matter of adding the units with the '+' sign:
You have: 12 ft + 3 in + 3|8 in
You want: ft
* 12.28125
/ 0.081424936
Although you can similarly write a sum of units to convert _to_, the
result will not be the conversion to the units in the sum, but rather
the conversion to the particular sum that you have entered:
You have: 12.28125 ft
You want: ft + in + 1|8 in
* 11.228571
/ 0.089058524
The unit expression given at the 'You want:' prompt is equivalent to
asking for conversion to multiples of '1 ft + 1 in + 1|8 in', which is
1.09375 ft, so the conversion in the previous example is equivalent to
You have: 12.28125 ft
You want: 1.09375 ft
* 11.228571
/ 0.089058524
In converting to a sum of units like miles, feet and inches, you
typically want the largest integral value for the first unit, followed
by the largest integral value for the next, and the remainder converted
to the last unit. You can do this conversion easily with 'units' using
a special syntax for lists of units. You must list the desired units in
order from largest to smallest, separated by the semicolon (';')
character:
You have: 12.28125 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3|8 in
The conversion always gives integer coefficients on the units in the
list, except possibly the last unit when the conversion is not exact:
You have: 12.28126 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3.00096 * 1|8 in
The order in which you list the units is important:
You have: 3 kg
You want: oz;lb
105 oz + 0.051367866 lb
You have: 3 kg
You want: lb;oz
6 lb + 9.8218858 oz
Listing ounces before pounds produces a technically correct result, but
not a very useful one. You must list the units in descending order of
size in order to get the most useful result.
Ending a unit list with the separator ';' has the same effect as
repeating the last unit on the list, so 'ft;in;1|8 in;' is equivalent to
'ft;in;1|8 in;1|8 in'. With the example above, this gives
You have: 12.28126 ft
You want: ft;in;1|8 in;
12 ft + 3 in + 3|8 in + 0.00096 * 1|8 in
in effect separating the integer and fractional parts of the coefficient
for the last unit. If you instead prefer to round the last coefficient
to an integer you can do this with the '--round' ('-r') option. With
the previous example, the result is
You have: 12.28126 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3|8 in (rounded down to nearest 1|8 in)
When you use the '-r' option, repeating the last unit on the list has no
effect (e.g., 'ft;in;1|8 in;1|8 in' is equivalent to 'ft;in;1|8 in'),
and hence neither does ending a list with a ';'. With a single unit and
the '-r' option, a terminal ';' _does_ have an effect: it causes 'units'
to treat the single unit as a list and produce a rounded value for the
single unit. Without the extra ';', the '-r' option has no effect on
single unit conversions. This example shows the output using the '-r'
option:
You have: 12.28126 ft
You want: in
* 147.37512
/ 0.0067854058
You have: 12.28126 ft
You want: in;
147 in (rounded down to nearest in)
Each unit that appears in the list must be conformable with the first
unit on the list, and of course the listed units must also be
conformable with the unit that you enter at the 'You have:' prompt.
You have: meter
You want: ft;kg
^
conformability error
ft = 0.3048 m
kg = 1 kg
You have: meter
You want: lb;oz
conformability error
1 m
0.45359237 kg
In the first case, 'units' reports the disagreement between units
appearing on the list. In the second case, 'units' reports disagreement
between the unit you entered and the desired conversion. This
conformability error is based on the first unit on the unit list.
Other common candidates for conversion to sums of units are angles
and time:
You have: 23.437754 deg
You want; deg;arcmin;arcsec
23 deg + 26 arcmin + 15.9144 arcsec
You have: 7.2319 hr
You want: hr;min;sec
7 hr + 13 min + 54.84 sec
In North America, recipes for cooking typically measure ingredients by
volume, and use units that are not always convenient multiples of each
other. Suppose that you have a recipe for 6 and you wish to make a
portion for 1. If the recipe calls for 2 1/2 cups of an ingredient, you
might wish to know the measurements in terms of measuring devices you
have available, you could use 'units' and enter
You have: (2+1|2) cup / 6
You want: cup;1|2 cup;1|3 cup;1|4 cup;tbsp;tsp;1|2 tsp;1|4 tsp
1|3 cup + 1 tbsp + 1 tsp
By default, if a unit in a list begins with fraction of the form 1|X and
its multiplier is an integer, the fraction is given as the product of
the multiplier and the numerator; for example,
You have: 12.28125 ft
You want: ft;in;1|8 in;
12 ft + 3 in + 3|8 in
In many cases, such as the example above, this is what is wanted, but
sometimes it is not. For example, a cooking recipe for 6 might call for
5 1/4 cup of an ingredient, but you want a portion for 2, and your 1-cup
measure is not available; you might try
You have: (5+1|4) cup / 3
You want: 1|2 cup;1|3 cup;1|4 cup
3|2 cup + 1|4 cup
This result might be fine for a baker who has a 1 1/2-cup measure (and
recognizes the equivalence), but it may not be as useful to someone with
more limited set of measures, who does want to do additional
calculations, and only wants to know "How many 1/2-cup measures to I
need to add?" After all, that's what was actually asked. With the
'--show-factor' option, the factor will not be combined with a unity
numerator, so that you get
You have: (5+1|4) cup / 3
You want: 1|2 cup;1|3 cup;1|4 cup
3 * 1|2 cup + 1|4 cup
A user-specified fractional unit with a numerator other than 1 is never
overridden, however--if a unit list specifies '3|4 cup;1|2 cup', a
result equivalent to 1 1/2 cups will always be shown as '2 * 3|4 cup'
whether or not the '--show-factor' option is given.
Some applications for unit lists may be less obvious. Suppose that
you have a postal scale and wish to ensure that it's accurate at 1 oz,
but have only metric calibration weights. You might try
You have: 1 oz
You want: 100 g;50 g; 20 g;10 g;5 g;2 g;1 g;
20 g + 5 g + 2 g + 1 g + 0.34952312 * 1 g
You might then place one each of the 20 g, 5 g, 2 g, and 1 g weights on
the scale and hope that it indicates close to
You have: 20 g + 5 g + 2 g + 1 g
You want: oz;
0.98767093 oz
Appending ';' to 'oz' forces a one-line display that includes the unit;
here the integer part of the result is zero, so it is not displayed.
A unit list such as
cup;1|2 cup;1|3 cup;1|4 cup;tbsp;tsp;1|2 tsp;1|4 tsp
can be tedious to enter. The 'units' program provides shorthand names
for some common combinations:
hms hours, minutes, seconds
dms angle: degrees, minutes, seconds
time years, days, hours, minutes and seconds
usvol US cooking volume: cups and smaller
Using these shorthands, or "unit list aliases", you can do the following
conversions:
You have: anomalisticyear
You want: time
1 year + 25 min + 3.4653216 sec
You have: 1|6 cup
You want: usvol
2 tbsp + 2 tsp
You cannot combine a unit list alias with other units: it must appear
alone at the 'You want:' prompt.
You can display the definition of a unit list alias by entering it at
the 'You have:' prompt:
You have: dms
Definition: unit list, deg;arcmin;arcsec
When you specify compact output with '--compact', '--terse' or '-t' and
perform conversion to a unit list, 'units' lists the conversion factors
for each unit in the list, separated by semicolons.
You have: year
You want: day;min;sec
365;348;45.974678
Unlike the case of regular output, zeros _are_ included in this output
list:
You have: liter
You want: cup;1|2 cup;1|4 cup;tbsp
4;0;0;3.6280454
File: units.info, Node: Logging Calculations, Next: Invoking Units, Prev: Unit Lists, Up: Top
8 Logging Calculations
**********************
The '--log' option allows you to save the results of calculations in a
file; this can be useful if you need a permanent record of your work.
For example, the fluid-flow conversion in *note Complicated Unit
Expressions::, is lengthy, and if you were to use it in designing a
piping system, you might want a record of it for the project file. If
the interactive session
# Conversion factor A1 for pressure drop
# dP = A1 rho f L Q^2/d^5
You have: (8/pi^2) (lbm/ft^3)ft(ft^3/s)^2(1/in^5) # Input units
You want: psi
* 43.533969
/ 0.022970568
were logged, the log file would contain
### Log started Fri Oct 02 15:55:35 2015
# Conversion factor A1 for pressure drop
# dP = A1 rho f L Q^2/d^5
From: (8/pi^2) (lbm/ft^3)ft(ft^3/s)^2(1/in^5) # Input units
To: psi
* 43.533969
/ 0.022970568
The time is written to the log file when the file is opened.
The use of comments can help clarify the meaning of calculations for
the log. The log includes conformability errors between the units at
the 'You have:' and 'You want:' prompts, but not other errors, including
lack of conformability of items in sums or differences or among items in
a unit list. For example, a conversion between zenith angle and
elevation angle could involve
You have: 90 deg - (5 deg + 22 min + 9 sec)
^
Illegal sum or difference of non-conformable units
You have: 90 deg - (5 deg + 22 arcmin + 9 arcsec)
You want: dms
84 deg + 37 arcmin + 51 arcsec
You have: _
You want: deg
* 84.630833
/ 0.011816024
You have:
The log file would contain
From: 90 deg - (5 deg + 22 arcmin + 9 arcsec)
To: deg;arcmin;arcsec
84 deg + 37 arcmin + 51 arcsec
From: _
To: deg
* 84.630833
/ 0.011816024
The initial entry error (forgetting that minutes have dimension of time,
and that arcminutes must be used for dimensions of angle) does not
appear in the output. When converting to a unit list alias, 'units'
expands the alias in the log file.
The 'From:' and 'To:' tags are written to the log file even if the
'--quiet' option is given. If the log file exists when 'units' is
invoked, the new results are appended to the log file. The time is
written to the log file each time the file is opened. The '--log'
option is ignored when 'units' is used non-interactively.
File: units.info, Node: Invoking Units, Next: Defining Your Own Units, Prev: Logging Calculations, Up: Top
9 Invoking 'units'
******************
You invoke 'units' like this:
units [OPTIONS] [FROM-UNIT [TO-UNIT]]
If the FROM-UNIT and TO-UNIT are omitted, the program will use
interactive prompts to determine which conversions to perform. *Note
Interactive Use::. If both FROM-UNIT and TO-UNIT are given, 'units'
will print the result of that single conversion and then exit. If only
FROM-UNIT appears on the command line, 'units' will display the
definition of that unit and exit. Units specified on the command line
may need to be quoted to protect them from shell interpretation and to
group them into two arguments. *Note Command Line Use::.
The default behavior of 'units' can be changed by various options
given on the command line. In most cases, the options may be given in
either short form (a single '-' followed by a single character) or long
form ('--' followed by a word or hyphen-separated words). Short-form
options are cryptic but require less typing; long-form options require
more typing but are more explanatory and may be more mnemonic. With
long-form options you need only enter sufficient characters to uniquely
identify the option to the program. For example, '--out %f' works, but
'--o %f' fails because 'units' has other long options beginning with
'o'. However, '--q' works because '--quiet' is the only long option
beginning with 'q'.
Some options require arguments to specify a value (e.g., '-d 12' or
'--digits 12'). Short-form options that do not take arguments may be
concatenated (e.g., '-erS' is equivalent to '-e -r -S'); the last option
in such a list may be one that takes an argument (e.g., '-ed 12'). With
short-form options, the space between an option and its argument is
optional (e.g., '-d12' is equivalent to '-d 12'). Long-form options may
not be concatenated, and the space between a long-form option and its
argument is required. Short-form and long-form options may be
intermixed on the command line. Options may be given in any order, but
when incompatible options (e.g., '--output-format' and '--exponential')
are given in combination, behavior is controlled by the last option
given. For example, '-o%.12f -e' gives exponential format with the
default eight significant digits).
The following options are available:
'-c'
'--check'
Check that all units and prefixes defined in the units data file
reduce to primitive units. Print a list of all units that cannot
be reduced. Also display some other diagnostics about suspicious
definitions in the units data file. Only definitions active in the
current locale are checked. You should always run 'units' with
this option after modifying a units data file.
'--check-verbose'
'--verbose-check'
Like the '--check' option, this option prints a list of units that
cannot be reduced. But to help find unit definitions that cause
endless loops, it lists the units as they are checked. If 'units'
hangs, then the last unit to be printed has a bad definition. Only
definitions active in the current locale are checked.
'-d NDIGITS'
'--digits NDIGITS'
Set the number of significant digits in the output to the value
specified (which must be greater than zero). For example, '-d 12'
sets the number of significant digits to 12. With exponential
output 'units' displays one digit to the left of the decimal
point(1) and eleven digits to the right of the decimal point. On
most systems, the maximum number of internally meaningful digits is
15; if you specify a greater number than your system's maximum,
'units' will print a warning and set the number to the largest
meaningful value. To directly set the maximum value, give an
argument of 'max' (e.g., '-d max'). Be aware, of course, that
"significant" here refers only to the _display_ of numbers; if
results depend on physical constants not known to this precision,
the physically meaningful precision may be less than that shown.
The '--digits' option conflicts with the '--output-format' option.
'-e'
'--exponential'
Set the numeric output format to exponential (i.e., scientific
notation), like that used in the Unix 'units' program. The default
precision is eight significant digits (seven digits to the right of
the decimal point); this can be changed with the '--digits' option.
The '--exponential' option conflicts with the '--output-format'
option.
'-o FORMAT'
'--output-format FORMAT'
This option affords complete control over the numeric output format
using the specified FORMAT. The format is a single floating point
numeric format for the 'printf()' function in the C programming
language. All compilers support the format types 'g' and 'G' to
specify significant digits, 'e' and 'E' for scientific notation,
and 'f' for fixed-point decimal. The ISO C99 standard introduced
the 'F' type for fixed-point decimal and the 'a' and 'A' types for
hexadecimal floating point; these types are allowed with compilers
that support them. The default format is '%.8g'; for greater
precision, you could specify '-o %.15g'. *Note Numeric Output
Format::, and the documentation for 'printf()' for more detailed
descriptions of the format specification. The '--output-format'
option affords the greatest control of the output appearance, but
requires at least rudimentary knowledge of the 'printf()' format
syntax. If you don't want to bother with the 'printf()' syntax,
you can specify greater precision more simply with the '--digits'
option or select exponential format with '--exponential'. The
'--output-format' option is incompatible with the '--exponential'
and '--digits' options.
'-f FILENAME'
'--file FILENAME'
Instruct 'units' to load the units file FILENAME. You can specify
up to 25 units files on the command line. When you use this
option, 'units' will load _only_ the files you list on the command
line; it will not load the standard file or your personal units
file unless you explicitly list them. If FILENAME is the empty
string ('-f ""'), the default units file (or that specified by
'UNITSFILE') will be loaded in addition to any others specified
with '-f'.
'-L LOGFILE'
'--log LOGFILE'
Save the results of calculations in the file LOGFILE; this can be
useful if it is important to have a record of unit conversions or
other calculations that are to be used extensively or in a critical
activity such as a program or design project. If LOGFILE exits,
the new results are appended to the file. This option is ignored
when 'units' is used non-interactively. *Note Logging
Calculations::, for a more detailed description and some examples.
'-H FILENAME'
'--history FILENAME'
Instruct 'units' to save history to FILENAME, so that a record of
your commands is available for retrieval across different 'units'
invocations. To prevent the history from being saved set FILENAME
to the emptry string ('-f ""'). This option has no effect if
readline is not available.
'-h'
'--help'
Print out a summary of the options for 'units'.
'-m'
'--minus'
Causes '-' to be interpreted as a subtraction operator. This is
the default behavior.
'-p'
'--product'
Causes '-' to be interpreted as a multiplication operator when it
has two operands. It will act as a negation operator when it has
only one operand: '(-3)'. By default '-' is treated as a
subtraction operator.
'--oldstar'
Causes '*' to have the old-style precedence, higher than the
precedence of division so that '1/2*3' will equal '1/6'.
'--newstar'
Forces '*' to have the new (default) precedence that follows the
usual rules of algebra: the precedence of '*' is the same as the
precedence of '/', so that '1/2*3' will equal '3/2'.
'--compact'
Give compact output featuring only the conversion factor. This
turns off the '--verbose' option.
'-q'
'--quiet'
'--silent'
Suppress prompting of the user for units and the display of
statistics about the number of units loaded.
'-n'
'--nolists'
Disable conversion to unit lists.
'-r'
'--round'
When converting to a combination of units given by a unit list,
round the value of the last unit in the list to the nearest
integer.
'-S'
'--show-factor'
When converting to a combination of units specified in a list,
always show a non-unity factor before a unit that begins with a
fraction with a unity denominator. By default, if the unit in a
list begins with fraction of the form 1|X and its multiplier is an
integer other than 1, the fraction is given as the product of the
multiplier and the numerator (e.g., '3|8 in' rather than '3 *
1|8 in'). In some cases, this is not what is wanted; for example,
the results for a cooking recipe might show '3 * 1|2 cup' as
'3|2 cup'. With the '--show-factor' option, a result equivalent to
1.5 cups will display as '3 * 1|2 cup' rather than '3|2 cup'. A
user-specified fractional unit with a numerator other than 1 is
never overridden, however--if a unit list specifies '3|4 cup;1|2
cup', a result equivalent to 1 1/2 cups will always be shown as '2
* 3|4 cup' whether or not the '--show-factor' option is given.
'-s'
'--strict'
Suppress conversion of units to their reciprocal units. For
example, 'units' will normally convert hertz to seconds because
these units are reciprocals of each other. The strict option
requires that units be strictly conformable to perform a
conversion, and will give an error if you attempt to convert hertz
to seconds.
'-1'
'--one-line'
Give only one line of output (the forward conversion). Do not
print the reverse conversion. If a reciprocal conversion is
performed then 'units' will still print the "reciprocal conversion"
line.
'-t'
'--terse'
Give terse output when converting units. This option can be used
when calling 'units' from another program so that the output is
easy to parse. This option has the combined effect of these
options: '--strict' '--quiet' '--one-line' '--compact'. When
combined with '--version' it produces a display showing only the
program name and version number.
'-v'
'--verbose'
Give slightly more verbose output when converting units. When
combined with the '-c' option this gives the same effect as
'--check-verbose'. When combined with '--version' produces a more
detailed output, equivalent to the '--info' option.
'-V'
'--version'
Print the program version number, tell whether the 'readline'
library has been included, tell whether UTF-8 support has been
included; give the locale, the location of the default units data
file, and the location of the personal units data file; indicate if
the personal units data file does not exist.
When given in combination with the '--terse' option, the program
prints only the version number and exits.
When given in combination with the '--verbose' option, the program,
the '--version' option has the same effect as the '--info' option
below.
'-I'
'--info'
Print the information given with the '--version' option, show the
pathname of the units program, show the status of the 'UNITSFILE'
and 'MYUNITSFILE' environment variables, and additional information
about how 'units' locates the related files. On systems running
Microsoft Windows, the status of the 'UNITSLOCALE' environment
variable and information about the related locale map are also
given. This option is usually of interest only to developers and
administrators, but it can sometimes be useful for troubleshooting.
Combining the '--version' and '--verbose' options has the same
effect as giving '--info'.
'-U'
'--unitsfile'
Print the location of the default units data file and exit; if the
file cannot be found, print "Units data file not found".
'-l LOCALE'
'--locale LOCALE'
Print the information given with the '--version' option, show the
Force a specified locale such as 'en_GB' to get British definitions
by default. This overrides the locale determined from system
settings or environment variables. *Note Locale::, for a
description of locale format.
---------- Footnotes ----------
(1) This document refers to "decimal point," but strictly, the
"radix" separates the integer and fractional parts of a floating-point
number; in English-speaking countries, the radix is a point ('.'), but
in most other countries it is a comma (',').
File: units.info, Node: Defining Your Own Units, Next: Numeric Output Format, Prev: Invoking Units, Up: Top
10 Adding Your Own Definitions
******************************
* Menu:
* Units Data Files:: Where are units defined?
* Defining New Units:: Writing your own unit and prefix definitions
* Defining Nonlinear Units:: Writing your own nonlinear unit definitions
* Piecewise Linear Units:: Writing your own piecewise linear definitions
* Defining Unit List Aliases:: Writing your own unit list aliases
File: units.info, Node: Units Data Files, Next: Defining New Units, Up: Defining Your Own Units
10.1 Units Data Files
=====================
The units and prefixes that 'units' can convert are defined in the units
data file, typically '/usr/share/units/definitions.units'. If you can't
find this file, run 'units --version' to get information on the file
locations for your installation. Although you can extend or modify this
data file if you have appropriate user privileges, it's usually better
to put extensions in separate files so that the definitions will be
preserved if you update 'units'.
You can include additional data files in the units database using the
'!include' command in the standard units data file. For example
!include /usr/local/share/units/local.units
might be appropriate for a site-wide supplemental data file. The
location of the '!include' statement in the standard units data file is
important; later definitions replace earlier ones, so any definitions in
an included file will override definitions before the '!include'
statement in the standard units data file. With normal invocation, no
warning is given about redefinitions; to ensure that you don't have an
unintended redefinition, run 'units -c' after making changes to any
units data file.
If you want to add your own units in addition to or in place of
standard or site-wide supplemental units data files, you can include
them in the '.units' file in your home directory. If this file exists
it is read after the standard units data file, so that any definitions
in this file will replace definitions of the same units in the standard
data file or in files included from the standard data file. This file
will not be read if any units files are specified on the command line.
(Under Windows the personal units file is named 'unitdef.units'.)
Running 'units -V' will display the location and name of your personal
units file.
The 'units' program first tries to determine your home directory from
the 'HOME' environment variable. On systems running Microsoft Windows,
if 'HOME' does not exist, 'units' attempts to find your home directory
from 'HOMEDRIVE', 'HOMEPATH' and 'USERPROFILE'. You can specify an
arbitrary file as your personal units data file with the 'MYUNITSFILE'
environment variable; if this variable exists, its value is used without
searching your home directory. The default units data files are
described in more detail in *note Data Files::.
File: units.info, Node: Defining New Units, Next: Defining Nonlinear Units, Prev: Units Data Files, Up: Defining Your Own Units
10.2 Defining New Units and Prefixes
====================================
A unit is specified on a single line by giving its name and an
equivalence. Comments start with a '#' character, which can appear
anywhere in a line. The backslash character ('\') acts as a
continuation character if it appears as the last character on a line,
making it possible to spread definitions out over several lines if
desired. A file can be included by giving the command '!include'
followed by the file's name. The '!' must be the first character on the
line. The file will be sought in the same directory as the parent file
unless you give a full path. The name of the file to be included cannot
contain the comment character '#'.
Unit names must not contain any of the operator characters '+', '-',
'*', '/', '|', '^', ';', '~', the comment character '#', or parentheses.
They cannot begin or end with an underscore ('_'), a comma (',') or a
decimal point ('.'). The figure dash (U+2012), typographical minus
('-'; U+2212), and en dash ('-'; U+2013) are converted to the operator
'-', so none of these characters can appear in unit names. Names cannot
begin with a digit, and if a name ends in a digit other than zero, the
digit must be preceded by a string beginning with an underscore, and
afterwards consisting only of digits, decimal points, or commas. For
example, 'foo_2', 'foo_2,1', or 'foo_3.14' are valid names but 'foo2' or
'foo_a2' are invalid. You could define nitrous oxide as
N2O nitrogen 2 + oxygen
but would need to define nitrogen dioxide as
NO_2 nitrogen + oxygen 2
Be careful to define new units in terms of old ones so that a reduction
leads to the primitive units, which are marked with '!' characters.
Dimensionless units are indicated by using the string '!dimensionless'
for the unit definition.
When adding new units, be sure to use the '-c' option to check that
the new units reduce properly. If you create a loop in the units
definitions, then 'units' will hang when invoked with the '-c' option.
You will need to use the '--check-verbose' option, which prints out each
unit as it is checked. The program will still hang, but the last unit
printed will be the unit that caused the infinite loop.
If you define any units that contain '+' characters, carefully check
them because the '-c' option will not catch non-conformable sums. Be
careful with the '-' operator as well. When used as a binary operator,
the '-' character can perform addition or multiplication depending on
the options used to invoke 'units'. To ensure consistent behavior use
'-' only as a unary negation operator when writing units definitions.
To multiply two units leave a space or use the '*' operator with care,
recalling that it has two possible precedence values and may require
parentheses to ensure consistent behavior. To compute the difference of
'foo' and 'bar' write 'foo+(-bar)' or even 'foo+-bar'.
Here is an example of a short data file that defines some basic
units:
m ! # The meter is a primitive unit
sec ! # The second is a primitive unit
rad !dimensionless # A dimensionless primitive unit
micro- 1e-6 # Define a prefix
minute 60 sec # A minute is 60 seconds
hour 60 min # An hour is 60 minutes
inch 0.0254 m # Inch defined in terms of meters
ft 12 inches # The foot defined in terms of inches
mile 5280 ft # And the mile
A unit that ends with a '-' character is a prefix. If a prefix
definition contains any '/' characters, be sure they are protected by
parentheses. If you define 'half- 1/2' then 'halfmeter' would be
equivalent to '1 / (2 meter)'.
File: units.info, Node: Defining Nonlinear Units, Next: Piecewise Linear Units, Prev: Defining New Units, Up: Defining Your Own Units
10.3 Defining Nonlinear Units
=============================
Some unit conversions of interest are nonlinear; for example,
temperature conversions between the Fahrenheit and Celsius scales cannot
be done by simply multiplying by conversion factors.
When you give a linear unit definition such as 'inch 2.54 cm' you are
providing information that 'units' uses to convert values in inches into
primitive units of meters. For nonlinear units, you give a functional
definition that provides the same information.
Nonlinear units are represented using a functional notation. It is
best to regard this notation not as a function call but as a way of
adding units to a number, much the same way that writing a linear unit
name after a number adds units to that number. Internally, nonlinear
units are defined by a pair of functions that convert to and from linear
units in the database, so that an eventual conversion to primitive units
is possible.
Here is an example nonlinear unit definition:
tempF(x) units=[1;K] domain=[-459.67,) range=[0,) \
(x+(-32)) degF + stdtemp ; (tempF+(-stdtemp))/degF + 32
A nonlinear unit definition comprises a unit name, a formal parameter
name, two functions, and optional specifications for units, the domain,
and the range (the domain of the inverse function). The functions tell
'units' how to convert to and from the new unit. To produce valid
results, the arguments of these functions need to have the correct
dimensions and be within the domains for which the functions are
defined.
The definition begins with the unit name followed immediately (with
no spaces) by a '(' character. In the parentheses is the name of the
formal parameter. Next is an optional specification of the units
required by the functions in the definition. In the example above, the
'units=[1;K]' specification indicates that the 'tempF' function requires
an input argument conformable with '1' (i.e., the argument is
dimensionless), and that the inverse function requires an input argument
conformable with 'K'. For normal nonlinear units definition, the
forward function will always take a dimensionless argument; in general,
the inverse function will need units that match the quantity measured by
your nonlinear unit. Specifying the units enables 'units' to perform
error checking on function arguments, and also to assign units to domain
and range specifications, which are described later.
Next the function definitions appear. In the example above, the
'tempF' function is defined by
tempF(x) = (x+(-32)) degF + stdtemp
This gives a rule for converting 'x' in the units 'tempF' to linear
units of absolute temperature, which makes it possible to convert from
tempF to other units.
To enable conversions to Fahrenheit, you must give a rule for the
inverse conversions. The inverse will be 'x(tempF)' and its definition
appears after a ';' character. In our example, the inverse is
x(tempF) = (tempF+(-stdtemp))/degF + 32
This inverse definition takes an absolute temperature as its argument
and converts it to the Fahrenheit temperature. The inverse can be
omitted by leaving out the ';' character and the inverse definition, but
then conversions _to_ the unit will not be possible. If the inverse
definition is omitted, the '--check' option will display a warning. It
is up to you to calculate and enter the correct inverse function to
obtain proper conversions; the '--check' option tests the inverse at one
point and prints an error if it is not valid there, but this is not a
guarantee that your inverse is correct.
With some definitions, the units may vary. For example, the
definition
square(x) x^2
can have any arbitrary units, and can also take dimensionless arguments.
In such a case, you should _not_ specify units. If a definition takes a
root of its arguments, the definition is valid only for units that yield
such a root. For example,
squirt(x) sqrt(x)
is valid for a dimensionless argument, and for arguments with even
powers of units.
Some definitions may not be valid for all real numbers. In such
cases, 'units' can handle errors better if you specify an appropriate
domain and range. You specify the domain and range as shown below:
baume(d) units=[1;g/cm^3] domain=[0,130.5] range=[1,10] \
(145/(145-d)) g/cm^3 ; (baume+-g/cm^3) 145 / baume
In this example the domain is specified after 'domain=' with the
endpoints given in brackets. In accord with mathematical convention,
square brackets indicate a closed interval (one that includes its
endpoints), and parentheses indicate an open interval (one that does not
include its endpoints). An interval can be open or closed on one or
both ends; an interval that is unbounded on either end is indicated by
omitting the limit on that end. For example, a quantity to which
decibel (dB) is applied may have any value greater than zero, so the
range is indicated by '(0,)':
decibel(x) units=[1;1] range=(0,) 10^(x/10); 10 log(decibel)
If the domain or range is given, the second endpoint must be greater
than the first.
The domain and range specifications can appear independently and in
any order along with the units specification. The values for the domain
and range endpoints are attached to the units given in the units
specification, and if necessary, the parameter value is adjusted for
comparison with the endpoints. For example, if a definition includes
'units=[1;ft]' and 'range=[3,)', the range will be taken as 3 ft to
infinity. If the function is passed a parameter of '900 mm', that value
will be adjusted to 2.9527559 ft, which is outside the specified range.
If you omit the units specification from the previous example, 'units'
can not tell whether you intend the lower endpoint to be 3 ft or
3 microfurlongs, and can not adjust the parameter value of 900 mm for
comparison. Without units, numerical values other than zero or plus or
minus infinity for domain or range endpoints are meaningless, and
accordingly they are not allowed. If you give other values without
units then the definition will be ignored and you will get an error
message.
Although the units, domain, and range specifications are optional,
it's best to give them when they are applicable; doing so allows 'units'
to perform better error checking and give more helpful error messages.
Giving the domain and range also enables the '--check' option to find a
point in the domain to use for its point check of your inverse
definition.
You can make synonyms for nonlinear units by providing both the
forward and inverse functions; inverse functions can be obtained using
the '~' operator. So to create a synonym for 'tempF' you could write
fahrenheit(x) units=[1;K] tempF(x); ~tempF(fahrenheit)
This is useful for creating a nonlinear unit definition that differs
slightly from an existing definition without having to repeat the
original functions. For example,
dBW(x) units=[1;W] range=[0,) dB(x) W ; ~dB(dBW/W)
If you wish a synonym to refer to an existing nonlinear unit without
modification, you can do so more simply by adding the synonym with
appended parentheses as a new unit, with the existing nonlinear
unit--without parentheses--as the definition. So to create a synonym
for 'tempF' you could write
fahrenheit() tempF
The definition must be a nonlinear unit; for example, the synonym
fahrenheit() meter
will result in an error message when 'units' starts.
You may occasionally wish to define a function that operates on
units. This can be done using a nonlinear unit definition. For
example, the definition below provides conversion between radius and the
area of a circle. This definition requires a length as input and
produces an area as output, as indicated by the 'units=' specification.
Specifying the range as the nonnegative numbers can prevent cryptic
error messages.
circlearea(r) units=[m;m^2] range=[0,) pi r^2 ; sqrt(circlearea/pi)
File: units.info, Node: Piecewise Linear Units, Next: Defining Unit List Aliases, Prev: Defining Nonlinear Units, Up: Defining Your Own Units
10.4 Defining Piecewise Linear Units
====================================
Sometimes you may be interested in a piecewise linear unit such as many
wire gauges. Piecewise linear units can be defined by specifying
conversions to linear units on a list of points. Conversion at other
points will be done by linear interpolation. A partial definition of
zinc gauge is
zincgauge[in] 1 0.002, 10 0.02, 15 0.04, 19 0.06, 23 0.1
In this example, 'zincgauge' is the name of the piecewise linear unit.
The definition of such a unit is indicated by the embedded '['
character. After the bracket, you should indicate the units to be
attached to the numbers in the table. No spaces can appear before the
']' character, so a definition like 'foo[kg meters]' is invalid; instead
write 'foo[kg*meters]'. The definition of the unit consists of a list
of pairs optionally separated by commas. This list defines a function
for converting from the piecewise linear unit to linear units. The
first item in each pair is the function argument; the second item is the
value of the function at that argument (in the units specified in
brackets). In this example, we define 'zincgauge' at five points. For
example, we set 'zincgauge(1)' equal to '0.002 in'. Definitions like
this may be more readable if written using continuation characters as
zincgauge[in] \
1 0.002 \
10 0.02 \
15 0.04 \
19 0.06 \
23 0.1
With the preceding definition, the following conversion can be
performed:
You have: zincgauge(10)
You want: in
* 0.02
/ 50
You have: .01 inch
You want: zincgauge
5
If you define a piecewise linear unit that is not strictly monotonic,
then the inverse will not be well defined. If the inverse is requested
for such a unit, 'units' will return the smallest inverse.
After adding nonlinear units definitions, you should normally run 'units --check'
to check for errors. If the 'units' keyword is not given, the '--check'
option checks a nonlinear unit definition using a dimensionless
argument, and then checks using an arbitrary combination of units, as
well as the square and cube of that combination; a warning is given if
any of these tests fail. For example,
Warning: function 'squirt(x)' defined as 'sqrt(x)'
failed for some test inputs:
squirt(7(kg K)^1): Unit not a root
squirt(7(kg K)^3): Unit not a root
Running 'units --check' will print a warning if a non-monotonic
piecewise linear unit is encountered. For example, the relationship
between ANSI coated abrasive designation and mean particle size is
non-monotonic in the vicinity of 800 grit:
ansicoated[micron] \
. . .
600 10.55 \
800 11.5 \
1000 9.5 \
Running 'units --check' would give the error message
Table 'ansicoated' lacks unique inverse around entry 800
Although the inverse is not well defined in this region, it's not really
an error. Viewing such error messages can be tedious, and if there are
enough of them, they can distract from true errors. Error checking for
nonlinear unit definitions can be suppressed by giving the 'noerror'
keyword; for the examples above, this could be done as
squirt(x) noerror domain=[0,) range=[0,) sqrt(x); squirt^2
ansicoated[micron] noerror \
. . .
Use the 'noerror' keyword with caution. The safest approach after
adding a nonlinear unit definition is to run 'units --check' and confirm
that there are no actual errors before adding the 'noerror' keyword.
File: units.info, Node: Defining Unit List Aliases, Prev: Piecewise Linear Units, Up: Defining Your Own Units
10.5 Defining Unit List Aliases
===============================
Unit list aliases are treated differently from unit definitions, because
they are a data entry shorthand rather than a true definition for a new
unit. A unit list alias definition begins with '!unitlist' and includes
the alias and the definition; for example, the aliases included in the
standard units data file are
!unitlist hms hr;min;sec
!unitlist time year;day;hr;min;sec
!unitlist dms deg;arcmin;arcsec
!unitlist ftin ft;in;1|8 in
!unitlist usvol cup;3|4 cup;2|3 cup;1|2 cup;1|3 cup;1|4 cup;\
tbsp;tsp;1|2 tsp;1|4 tsp;1|8 tsp
Unit list aliases are only for unit lists, so the definition must
include a ';'. Unit list aliases can never be combined with units or
other unit list aliases, so the definition of 'time' shown above could
_not_ have been shortened to 'year;day;hms'.
As usual, be sure to run 'units --check' to ensure that the units
listed in unit list aliases are conformable.
File: units.info, Node: Numeric Output Format, Next: Localization, Prev: Defining Your Own Units, Up: Top
11 Numeric Output Format
************************
* Menu:
* Format Specification:: The output format specification
* Flags:: Optional format flags
* Field Width:: Specifying output field width
* Precision:: Specifying output precision
By default, 'units' shows results to eight significant digits. You can
change this with the '--exponential', '--digits', and '--output-format'
options. The first sets an exponential format (i.e., scientific
notation) like that used in the original Unix 'units' program, the
second allows you to specify a different number of significant digits,
and the last allows you to control the output appearance using the
format for the 'printf()' function in the C programming language. If
you only want to change the number of significant digits or specify
exponential format type, use the '--digits' and '--exponential' options.
The '--output-format' option affords the greatest control of the output
appearance, but requires at least rudimentary knowledge of the
'printf()' format syntax. *Note Invoking Units::, for descriptions of
these options.
File: units.info, Node: Format Specification, Next: Flags, Up: Numeric Output Format
11.1 Format Specification
=========================
The format specification recognized with the '--output-format' option is
a subset of that for 'printf()'. The format specification has the form
'%'[flags][width]['.'precision]type; it must begin with '%', and must
end with a floating-point type specifier: 'g' or 'G' to specify the
number of significant digits, 'e' or 'E' for scientific notation, and
'f' for fixed-point decimal. The ISO C99 standard added the 'F' type
for fixed-point decimal and the 'a' and 'A' types for hexadecimal
floating point; these types are allowed with compilers that support
them. Type length modifiers (e.g., 'L' to indicate a long double) are
inapplicable and are not allowed.
The default format for 'units' is '%.8g'; for greater precision, you
could specify '-o %.15g'. The 'g' and 'G' format types use exponential
format whenever the exponent would be less than -4, so the value
0.000013 displays as '1.3e-005'. These types also use exponential
notation when the exponent is greater than or equal to the precision, so
with the default format, the value 5e7 displays as '50000000' and the
value 5e8 displays as '5e+008'. If you prefer fixed-point display, you
might specify '-o %.8f'; however, small numbers will display very few
significant digits, and values less than 0.5e-8 will show nothing but
zeros.
The format specification may include one or more optional flags: '+',
' ' (space), '#', '-', or '0' (the digit zero). The digit-grouping flag
''' (apostrophe) is allowed with compilers that support it. Flags are
followed by an optional value for the minimum field width, and an
optional precision specification that begins with a period (e.g., '.6').
The field width includes the digits, decimal point, the exponent,
thousands separators (with the digit-grouping flag), and the sign if any
of these are shown.
File: units.info, Node: Flags, Next: Field Width, Prev: Format Specification, Up: Numeric Output Format
11.2 Flags
==========
The '+' flag causes the output to have a sign ('+' or '-'). The space
flag ' ' is similar to the '+' flag, except that when the value is
positive, it is prefixed with a space rather than a plus sign; this flag
is ignored if the '+' flag is also given. The '+' or ' ' flag could be
useful if conversions might include positive and negative results, and
you wanted to align the decimal points in exponential notation. The '#'
flag causes the output value to contain a decimal point in all cases; by
default, the output contains a decimal point only if there are digits
(which can be trailing zeros) to the right of the point. With the 'g'
or 'G' types, the '#' flag also prevents the suppression of trailing
zeros. The digit-grouping flag ''' shows a thousands separator in
digits to the left of the decimal point. This can be useful when
displaying large numbers in fixed-point decimal; for example, with the
format '%f',
You have: mile
You want: microfurlong
* 8000000.000000
/ 0.000000
the magnitude of the first result may not be immediately obvious without
counting the digits to the left of the decimal point. If the thousands
separator is the comma (','), the output with the format '%'f' might be
You have: mile
You want: microfurlong
* 8,000,000.000000
/ 0.000000
making the magnitude readily apparent. Unfortunately, few compilers
support the digit-grouping flag.
With the '-' flag, the output value is left aligned within the
specified field width. If a field width greater than needed to show the
output value is specified, the '0' (zero) flag causes the output value
to be left padded with zeros until the specified field width is reached;
for example, with the format '%011.6f',
You have: troypound
You want: grain
* 5760.000000
/ 0000.000174
The '0' flag has no effect if the '-' (left align) flag is given.
File: units.info, Node: Field Width, Next: Precision, Prev: Flags, Up: Numeric Output Format
11.3 Field Width
================
By default, the output value is left aligned and shown with the minimum
width necessary for the specified (or default) precision. If a field
width greater than this is specified, the value shown is right aligned,
and padded on the left with enough spaces to provide the specified field
width. A width specification is typically used with fixed-point decimal
to have columns of numbers align at the decimal point; this arguably is
less useful with 'units' than with long columnar output, but it may
nonetheless assist in quickly assessing the relative magnitudes of
results. For example, with the format '%12.6f',
You have: km
You want: in
* 39370.078740
/ 0.000025
You have: km
You want: rod
* 198.838782
/ 0.005029
You have: km
You want: furlong
* 4.970970
/ 0.201168
File: units.info, Node: Precision, Prev: Field Width, Up: Numeric Output Format
11.4 Precision
==============
The meaning of "precision" depends on the format type. With 'g' or 'G',
it specifies the number of significant digits (like the '--digits'
option); with 'e', 'E', 'f', or 'F', it specifies the maximum number of
digits to be shown after the decimal point.
With the 'g' and 'G' format types, trailing zeros are suppressed, so
the results may sometimes have fewer digits than the specified precision
(as indicated above, the '#' flag causes trailing zeros to be
displayed).
The default precision is 6, so '%g' is equivalent to '%.6g', and
would show the output to six significant digits. Similarly, '%e' or
'%f' would show the output with six digits after the decimal point.
The C 'printf()' function allows a precision of arbitrary size,
whether or not all of the digits are meaningful. With most compilers,
the maximum internal precision with 'units' is 15 decimal digits (or 13
hexadecimal digits). With the '--digits' option, you are limited to the
maximum internal precision; with the '--output-format' option, you may
specify a precision greater than this, but it may not be meaningful. In
some cases, specifying excess precision can result in rounding
artifacts. For example, a pound is exactly 7000 grains, but with the
format '%.18g', the output might be
You have: pound
You want: grain
* 6999.9999999999991
/ 0.00014285714285714287
With the format '%.25g' you might get the following:
You have: 1/3
You want:
Definition: 0.333333333333333314829616256247
In this case the displayed value includes a series of digits that
represent the underlying binary floating-point approximation to 1/3 but
are not meaningful for the desired computation. In general, the result
with excess precision is system dependent. The precision affects only
the _display_ of numbers; if a result relies on physical constants that
are not known to the specified precision, the number of physically
meaningful digits may be less than the number of digits shown.
See the documentation for 'printf()' for more detailed descriptions
of the format specification.
The '--output-format' option is incompatible with the '--exponential'
or '--digits' options; if the former is given in combination with either
of the latter, the format is controlled by the last option given.
File: units.info, Node: Localization, Next: Environment Vars, Prev: Numeric Output Format, Up: Top
12 Localization
***************
* Menu:
* Locale:: What is a locale?
* Additional Localization:: When the locale isn't enough
Some units have different values in different locations. The
localization feature accommodates this by allowing a units data file to
specify definitions that depend on the user's locale.
File: units.info, Node: Locale, Next: Additional Localization, Up: Localization
12.1 Locale
===========
A locale is a subset of a user's environment that indicates the user's
language and country, and some attendant preferences, such as the
formatting of dates. The 'units' program attempts to determine the
locale from the POSIX setlocale function; if this cannot be done,
'units' examines the environment variables 'LC_CTYPE' and 'LANG'. On
POSIX systems, a locale is of the form LANGUAGE'_'COUNTRY, where
LANGUAGE is the two-character code from ISO 639-1 and COUNTRY is the
two-character code from ISO 3166-1; LANGUAGE is lower case and COUNTRY
is upper case. For example, the POSIX locale for the United Kingdom is
'en_GB'.
On systems running Microsoft Windows, the value returned by
setlocale() is different from that on POSIX systems; 'units' attempts to
map the Windows value to a POSIX value by means of a table in the file
'locale_map.txt' in the same directory as the other data files. The
file includes entries for many combinations of language and country, and
can be extended to include other combinations. The 'locale_map.txt'
file comprises two tab-separated columns; each entry is of the form
WINDOWS-LOCALE POSIX-LOCALE
where POSIX-LOCALE is as described above, and WINDOWS-LOCALE typically
spells out both the language and country. For example, the entry for
the United States is
English_United States en_US
You can force 'units' to run in a desired locale by using the '-l'
option.
In order to create unit definitions for a particular locale you begin
a block of definitions in a unit datafile with '!locale' followed by a
locale name. The '!' must be the first character on the line. The
'units' program reads the following definitions only if the current
locale matches. You end the block of localized units with '!endlocale'.
Here is an example, which defines the British gallon.
!locale en_GB
gallon 4.54609 liter
!endlocale
File: units.info, Node: Additional Localization, Prev: Locale, Up: Localization
12.2 Additional Localization
============================
Sometimes the locale isn't sufficient to determine unit preferences.
There could be regional preferences, or a company could have specific
preferences. Though probably uncommon, such differences could arise
with the choice of English customary units outside of English-speaking
countries. To address this, 'units' allows specifying definitions that
depend on environment variable settings. The environment variables can
be controled based on the current locale, or the user can set them to
force a particular group of definitions.
A conditional block of definitions in a units data file begins with
either '!var' or '!varnot' following by an environment variable name and
then a space separated list of values. The leading '!' must appear in
the first column of a units data file, and the conditional block is
terminated by '!endvar'. Definitions in blocks beginning with '!var'
are executed only if the environment variable is exactly equal to one of
the listed values. Definitions in blocks beginning with '!varnot' are
executed only if the environment variable does _not_ equal any of the
list values.
The inch has long been a customary measure of length in many places.
The word comes from the latin _uncia_ meaning "one twelfth," referring
to its relationship with the foot. By the 20th century, the inch was
officially defined in English-speaking countries relative to the yard,
but until 1959, the yard differed slightly among those countries. In
France the customary inch, which was displaced in 1799 by the meter, had
a different length based on a french foot. These customary definitions
could be accommodated as follows:
!var INCH_UNIT usa
yard 3600|3937 m
!endvar
!var INCH_UNIT canada
yard 0.9144 meter
!endvar
!var INCH_UNIT uk
yard 0.91439841 meter
!endvar
!var INCH_UNIT canada uk usa
foot 1|3 yard
inch 1|12 foot
!endvar
!var INCH_UNIT france
foot 144|443.296 m
inch 1|12 foot
line 1|12 inch
!endvar
!varnot INCH_UNIT usa uk france canada
!message Unknown value for INCH_UNIT
!endvar
When 'units' reads the above definitions it will check the environment
variable 'INCH_UNIT' and load only the definitions for the appropriate
section. If 'INCH_UNIT' is unset or is not set to one of the four
values listed then 'units' will run the last block. In this case that
block uses the '!message' command to display a warning message.
Alternatively that block could set default values.
In order to create default values that are overridden by user
settings the data file can use the '!set' command, which sets an
environment variable _only if it is not already set_; these settings are
only for the current 'units' invocation and do not persist. So if the
example above were preceded by '!set INCH_UNIT france' then this would
make 'france' the default value for 'INCH_UNIT'. If the user had set
the variable in the environment before invoking 'units', then 'units'
would use the user's value.
To link these settings to the user's locale you combine the '!set'
command with the '!locale' command. If you wanted to combine the above
example with suitable locales you could do by _preceding_ the above
definition with the following:
!locale en_US
!set INCH_UNIT usa
!endlocale
!locale en_GB
!set INCH_UNIT uk
!endlocale
!locale en_CA
!set INCH_UNIT canada
!endlocale
!locale fr_FR
!set INCH_UNIT france
!endlocale
!set INCH_UNIT france
These definitions set the overall default for 'INCH_UNIT' to 'france'
and set default values for four locales appropriately. The overall
default setting comes last so that it only applies when 'INCH_UNIT' was
not set by one of the other commands or by the user.
If the variable given after '!var' or '!varnot' is undefined then
'units' prints an error message and ignores the definitions that follow.
Use '!set' to create defaults to prevent this situation from arising.
The '-c' option only checks the definitions that are active for the
current environment and locale, so when adding new definitions take care
to check that all cases give rise to a well defined set of definitions.
File: units.info, Node: Environment Vars, Next: Data Files, Prev: Localization, Up: Top
13 Environment Variables
************************
The 'units' program uses the following environment variables:
'HOME'
Specifies the location of your home directory; it is used by
'units' to find a personal units data file '.units'. On systems
running Microsoft Windows, the file is 'unitdef.units', and if
'HOME' does not exist, 'units' tries to determine your home
directory from the 'HOMEDRIVE' and 'HOMEPATH' environment
variables; if these variables do not exist, units finally tries
'USERPROFILE'--typically 'C:\Users\USERNAME' (Windows Vista and
Windows 7) or 'C:\Documents and Settings\USERNAME' (Windows XP).
'LC_CTYPE, LANG'
Checked to determine the locale if 'units' cannot obtain it from
the operating system. Sections of the standard units data file are
specific to certain locales.
'MYUNITSFILE'
Specifies your personal units data file. If this variable exists,
'units' uses its value rather than searching your home directory
for '.units'. The personal units file will not be loaded if any
data files are given using the '-f' option.
'PAGER'
Specifies the pager to use for help and for displaying the
conformable units. The help function browses the units database
and calls the pager using the '+n'N syntax for specifying a line
number. The default pager is 'more'; 'PAGER' can be used to
specify alternatives such as 'less', 'pg', 'emacs', or 'vi'.
'UNITS_ENGLISH'
Set to either 'US' or 'GB' to choose United States or British
volume definitions, overriding the default from your locale.
'UNITSFILE'
Specifies the units data file to use (instead of the default). You
can only specify a single units data file using this environment
variable. If units data files are given using the '-f' option, the
file specified by 'UNITSFILE' will be not be loaded unless the '-f'
option is given with the empty string ('units -f ""').
'UNITSLOCALEMAP'
Windows only; this variable has no effect on Unix-like systems.
Specifies the units locale map file to use (instead of the
default). This variable seldom needs to be set, but you can use it
to ensure that the locale map file will be found if you specify a
location for the units data file using either the '-f' option or
the 'UNITSFILE' environment variable, and that location does not
also contain the locale map file.
File: units.info, Node: Data Files, Next: Unicode Support, Prev: Environment Vars, Up: Top
14 Data Files
*************
The 'units' program uses two default data files: 'definitions.units' and
'currency.units'. The program can also use an optional personal units
data file '.units' ('unitdef.units' under Windows) located in the user's
home directory. The personal units data file is described in more
detail in *note Units Data Files::.
On Unix-like systems, the data files are typically located in
'/usr/share/units' if 'units' is provided with the operating system, or
in '/usr/local/share/units' if 'units' is compiled from the source
distribution.
On systems running Microsoft Windows, the files may be in the same
locations if Unix-like commands are available, a Unix-like file
structure is present (e.g., 'C:/usr/local'), and 'units' is compiled
from the source distribution. If Unix-like commands are not available,
a more common location is 'C:\Program Files (x86)\GNU\units' (for 64-bit
Windows installations) or 'C:\Program Files\GNU\units' (for 32-bit
installations).
If 'units' is obtained from the GNU Win32 Project
(), the files are commonly in
'C:\Program Files\GnuWin32\share\units'.
If the default units data file is not an absolute pathname, 'units'
will look for the file in the directory that contains the 'units'
program; if the file is not found there, 'units' will look in a
directory '../share/units' relative to the directory with the 'units'
program.
You can determine the location of the files by running
'units --version'. Running 'units --info' will give you additional
information about the files, how 'units' will attempt to find them, and
the status of the related environment variables.
File: units.info, Node: Unicode Support, Next: Readline Support, Prev: Data Files, Up: Top
15 Unicode Support
******************
The standard units data file is in Unicode, using UTF-8 encoding. Most
definitions use only ASCII characters (i.e., code points U+0000 through
U+007F); definitions using non-ASCII characters appear in blocks
beginning with '!utf8' and ending with '!endutf8'.
When 'units' starts, it checks the locale to determine the character
set. If 'units' is compiled with Unicode support and definitions;
otherwise these definitions are ignored. When Unicode support is
active, 'units' will check every line of all of the units data files for
invalid or non-printing UTF-8 sequences; if such sequences occur,
'units' ignores the entire line. In addition to checking validity,
'units' determines the display width of non-ASCII characters to ensure
proper positioning of the pointer in some error messages and to align
columns for the 'search' and '?' commands.
At present, 'units' does not support Unicode under Microsoft Windows.
The UTF-16 and UTF-32 encodings are not supported on any systems.
If definitions that contain non-ASCII characters are added to a units
data file, those definitions should be enclosed within '!utf8' ...
'!endutf8' to ensure that they are only loaded when Unicode support is
available. As usual, the '!' must appear as the first character on the
line. As discussed in *note Units Data Files::, it's usually best to
put such definitions in supplemental data files linked by an '!include'
command or in a personal units data file.
When Unicode support is not active, 'units' makes no assumptions
about character encoding, except that characters in the range 00-7F
hexadecimal correspond to ASCII encoding. Non-ASCII characters are
simply sequences of bytes, and have no special meanings; for definitions
in supplementary units data files, you can use any encoding consistent
with this assumption. For example, if you wish to use non-ASCII
characters in definitions when running 'units' under Windows, you can
use a character set such as Windows "ANSI" (code page 1252 in the US and
Western Europe). You can even use UTF-8, though some messages may be
improperly aligned, and 'units' will not detect invalid UTF-8 sequences.
If you use UTF-8 encoding when Unicode support is not active, you should
place any definitions with non-ASCII characters _outside_ '!utf8' ...
'!endutf8' blocks--otherwise, they will be ignored.
Typeset material other than code examples usually uses the Unicode
minus (U+2212) rather than the ASCII hyphen-minus operator (U+002D) used
in 'units'; the figure dash (U+2012) and en dash (U+2013) are also
occasionally used. To allow such material to be copied and pasted for
interactive use or in units data files, 'units' converts these
characters to U+002D before further processing. Because of this, none
of these characters can appear in unit names.
File: units.info, Node: Readline Support, Next: Currency, Prev: Unicode Support, Up: Top
16 Readline Support
*******************
If the 'readline' package has been compiled in, then when 'units' is
used interactively, numerous command line editing features are
available. To check if your version of 'units' includes 'readline',
invoke the program with the '--version' option.
For complete information about 'readline', consult the documentation
for the 'readline' package. Without any configuration, 'units' will
allow editing in the style of emacs. Of particular use with 'units' are
the completion commands.
If you type a few characters and then hit followed by '?' then
'units' will display a list of all the units that start with the
characters typed. For example, if you type 'metr' and then request
completion, you will see something like this:
You have: metr
metre metriccup metrichorsepower metrictenth
metretes metricfifth metricounce metricton
metriccarat metricgrain metricquart metricyarncount
You have: metr
If there is a unique way to complete a unitname, you can hit the
key and 'units' will provide the rest of the unit name. If 'units'
beeps, it means that there is no unique completion. Pressing the
key a second time will print the list of all completions.
The readline library also keeps a history of the values you enter.
You can move through this history using the up and down arrows. The
history is saved to the file '.units_history' in your home directory so
that it will persist across multiple 'units' invocations. If you wish
to keep work for a certain project separate you can change the history
filename using the '--history' option. You could, for example, make an
alias for 'units' to 'units --history .units_history' so that 'units'
would save separate history in the current directory. The length of
each history file is limited to 5000 lines. Note also that if you run
several concurrent copies of 'units' each one will save its new history
to the history file upon exit.
File: units.info, Node: Currency, Next: Database Syntax, Prev: Readline Support, Up: Top
17 Updating Currency Exchange Rates
***********************************
The units program includes currency exchange rates and prices for some
precious metals in the database. Of course, these values change over
time, sometimes very rapidly, and 'units' cannot provide real time
values. To update the exchange rates run the 'units_cur', which
rewrites the files containing the currency rates, typically
'/usr/share/units/currency.units'. This program requires 'python' and
the 'unidecode' package, and must be run with suitable permissions to
write the file. To keep the rates updated automatically, run it using a
cron job on a Unix-like system, or a similar scheduling program on a
different system. Currency exchange rates are taken from Time Genie
() and precious metals pricing from Packetizer
(). These sites update once per day, so there is no
benefit in running the update script more often than daily. You can run
'units_cur' with a filename specified on the command line and it will
write the data to that file. If you give '-' for the file it will write
to standard output.
File: units.info, Node: Database Syntax, Next: GNU Free Documentation License, Prev: Currency, Up: Top
18 Database Command Syntax
**************************
UNIT DEFINITION
Define a regular unit.
PREFIX- DEFINITION
Define a prefix.
FUNCNAME(VAR) noerror units=[IN-UNITS,OUT-UNITS] domain=[X1,X2] range=[Y1,Y2] DEFINITION(VAR) ; INVERSE(FUNCNAME)
Define a nonlinear unit or unit function. The four optional
keywords 'noerror', 'units=', 'range=' and 'domain=' can appear in
any order. The definition of the inverse is optional.
TABNAME[OUT-UNITS] noerror PAIR-LIST
Define a piecewise linear unit. The pair list gives the points on
the table listed in ascending order. The 'noerror' keyword is
optional.
!endlocale
End a block of definitions beginning with '!locale'
!endutf8
End a block of definitions begun with '!utf8'
!endvar
End a block of definitions begun with '!var' or '!varnot'
!include FILE
Include the specified file.
!locale VALUE
Load the following definitions only of the locale is set to VALUE.
!message TEXT
Display TEXT when the database is read unless the quiet option
('-q') is enabled.
!set VARIABLE VALUE
Sets the environment variable, VARIABLE, to the specified value
_only if_ it is not already set.
!unitlist ALIAS DEFINITION
Define a unit list alias.
!utf8
Load the following definitions only if 'units' is running with
UTF-8 enabled.
!var ENVAR VALUE-LIST
Load the block of definitions that follows only if the environment
variable ENVAR is set to one of the values listed in the
space-separated value list. If ENVAR is not set, 'units' prints an
error message and ignores the block of definitions.
!varnot ENVAR VALUE-LIST
Load the block of definitions that follows only if the environment
variable ENVAR is set to value that is _not_ listed in the
space-separated value list. If ENVAR is not set, 'units' prints an
error message and ignores the block of definitions.
File: units.info, Node: GNU Free Documentation License, Next: Index, Prev: Database Syntax, Up: Top
19 GNU Free Documentation License
*********************************
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
0. PREAMBLE
The purpose of this License is to make a manual, textbook, or other
functional and useful document "free" in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or
noncommercially. Secondarily, this License preserves for the
author and publisher a way to get credit for their work, while not
being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative
works of the document must themselves be free in the same sense.
It complements the GNU General Public License, which is a copyleft
license designed for free software.
We have designed this License in order to use it for manuals for
free software, because free software needs free documentation: a
free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to
software manuals; it can be used for any textual work, regardless
of subject matter or whether it is published as a printed book. We
recommend this License principally for works whose purpose is
instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium,
that contains a notice placed by the copyright holder saying it can
be distributed under the terms of this License. Such a notice
grants a world-wide, royalty-free license, unlimited in duration,
to use that work under the conditions stated herein. The
"Document", below, refers to any such manual or work. Any member
of the public is a licensee, and is addressed as "you". You accept
the license if you copy, modify or distribute the work in a way
requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall
subject (or to related matters) and contains nothing that could
fall directly within that overall subject. (Thus, if the Document
is in part a textbook of mathematics, a Secondary Section may not
explain any mathematics.) The relationship could be a matter of
historical connection with the subject or with related matters, or
of legal, commercial, philosophical, ethical or political position
regarding them.
The "Invariant Sections" are certain Secondary Sections whose
titles are designated, as being those of Invariant Sections, in the
notice that says that the Document is released under this License.
If a section does not fit the above definition of Secondary then it
is not allowed to be designated as Invariant. The Document may
contain zero Invariant Sections. If the Document does not identify
any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
that says that the Document is released under this License. A
Front-Cover Text may be at most 5 words, and a Back-Cover Text may
be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed
of pixels) generic paint programs or (for drawings) some widely
available drawing editor, and that is suitable for input to text
formatters or for automatic translation to a variety of formats
suitable for input to text formatters. A copy made in an otherwise
Transparent file format whose markup, or absence of markup, has
been arranged to thwart or discourage subsequent modification by
readers is not Transparent. An image format is not Transparent if
used for any substantial amount of text. A copy that is not
"Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
SGML or XML using a publicly available DTD, and standard-conforming
simple HTML, PostScript or PDF designed for human modification.
Examples of transparent image formats include PNG, XCF and JPG.
Opaque formats include proprietary formats that can be read and
edited only by proprietary word processors, SGML or XML for which
the DTD and/or processing tools are not generally available, and
the machine-generated HTML, PostScript or PDF produced by some word
processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
material this License requires to appear in the title page. For
works in formats which do not have any title page as such, "Title
Page" means the text near the most prominent appearance of the
work's title, preceding the beginning of the body of the text.
The "publisher" means any person or entity that distributes copies
of the Document to the public.
A section "Entitled XYZ" means a named subunit of the Document
whose title either is precisely XYZ or contains XYZ in parentheses
following text that translates XYZ in another language. (Here XYZ
stands for a specific section name mentioned below, such as
"Acknowledgements", "Dedications", "Endorsements", or "History".)
To "Preserve the Title" of such a section when you modify the
Document means that it remains a section "Entitled XYZ" according
to this definition.
The Document may include Warranty Disclaimers next to the notice
which states that this License applies to the Document. These
Warranty Disclaimers are considered to be included by reference in
this License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and
has no effect on the meaning of this License.
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License
applies to the Document are reproduced in all copies, and that you
add no other conditions whatsoever to those of this License. You
may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute. However,
you may accept compensation in exchange for copies. If you
distribute a large enough number of copies you must also follow the
conditions in section 3.
You may also lend copies, under the same conditions stated above,
and you may publicly display copies.
3. COPYING IN QUANTITY
If you publish printed copies (or copies in media that commonly
have printed covers) of the Document, numbering more than 100, and
the Document's license notice requires Cover Texts, you must
enclose the copies in covers that carry, clearly and legibly, all
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
and legibly identify you as the publisher of these copies. The
front cover must present the full title with all words of the title
equally prominent and visible. You may add other material on the
covers in addition. Copying with changes limited to the covers, as
long as they preserve the title of the Document and satisfy these
conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto
adjacent pages.
If you publish or distribute Opaque copies of the Document
numbering more than 100, you must either include a machine-readable
Transparent copy along with each Opaque copy, or state in or with
each Opaque copy a computer-network location from which the general
network-using public has access to download using public-standard
network protocols a complete Transparent copy of the Document, free
of added material. If you use the latter option, you must take
reasonably prudent steps, when you begin distribution of Opaque
copies in quantity, to ensure that this Transparent copy will
remain thus accessible at the stated location until at least one
year after the last time you distribute an Opaque copy (directly or
through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of
the Document well before redistributing any large number of copies,
to give them a chance to provide you with an updated version of the
Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you
release the Modified Version under precisely this License, with the
Modified Version filling the role of the Document, thus licensing
distribution and modification of the Modified Version to whoever
possesses a copy of it. In addition, you must do these things in
the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title
distinct from that of the Document, and from those of previous
versions (which should, if there were any, be listed in the
History section of the Document). You may use the same title
as a previous version if the original publisher of that
version gives permission.
B. List on the Title Page, as authors, one or more persons or
entities responsible for authorship of the modifications in
the Modified Version, together with at least five of the
principal authors of the Document (all of its principal
authors, if it has fewer than five), unless they release you
from this requirement.
C. State on the Title page the name of the publisher of the
Modified Version, as the publisher.
D. Preserve all the copyright notices of the Document.
E. Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
F. Include, immediately after the copyright notices, a license
notice giving the public permission to use the Modified
Version under the terms of this License, in the form shown in
the Addendum below.
G. Preserve in that license notice the full lists of Invariant
Sections and required Cover Texts given in the Document's
license notice.
H. Include an unaltered copy of this License.
I. Preserve the section Entitled "History", Preserve its Title,
and add to it an item stating at least the title, year, new
authors, and publisher of the Modified Version as given on the
Title Page. If there is no section Entitled "History" in the
Document, create one stating the title, year, authors, and
publisher of the Document as given on its Title Page, then add
an item describing the Modified Version as stated in the
previous sentence.
J. Preserve the network location, if any, given in the Document
for public access to a Transparent copy of the Document, and
likewise the network locations given in the Document for
previous versions it was based on. These may be placed in the
"History" section. You may omit a network location for a work
that was published at least four years before the Document
itself, or if the original publisher of the version it refers
to gives permission.
K. For any section Entitled "Acknowledgements" or "Dedications",
Preserve the Title of the section, and preserve in the section
all the substance and tone of each of the contributor
acknowledgements and/or dedications given therein.
L. Preserve all the Invariant Sections of the Document, unaltered
in their text and in their titles. Section numbers or the
equivalent are not considered part of the section titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
N. Do not retitle any existing section to be Entitled
"Endorsements" or to conflict in title with any Invariant
Section.
O. Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no
material copied from the Document, you may at your option designate
some or all of these sections as invariant. To do this, add their
titles to the list of Invariant Sections in the Modified Version's
license notice. These titles must be distinct from any other
section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
parties--for example, statements of peer review or that the text
has been approved by an organization as the authoritative
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
and a passage of up to 25 words as a Back-Cover Text, to the end of
the list of Cover Texts in the Modified Version. Only one passage
of Front-Cover Text and one of Back-Cover Text may be added by (or
through arrangements made by) any one entity. If the Document
already includes a cover text for the same cover, previously added
by you or by arrangement made by the same entity you are acting on
behalf of, you may not add another; but you may replace the old
one, on explicit permission from the previous publisher that added
the old one.
The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to
assert or imply endorsement of any Modified Version.
5. COMBINING DOCUMENTS
You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for
modified versions, provided that you include in the combination all
of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice, and that you preserve all
their Warranty Disclaimers.
The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name
but different contents, make the title of each such section unique
by adding at the end of it, in parentheses, the name of the
original author or publisher of that section if known, or else a
unique number. Make the same adjustment to the section titles in
the list of Invariant Sections in the license notice of the
combined work.
In the combination, you must combine any sections Entitled
"History" in the various original documents, forming one section
Entitled "History"; likewise combine any sections Entitled
"Acknowledgements", and any sections Entitled "Dedications". You
must delete all sections Entitled "Endorsements."
6. COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the
rules of this License for verbatim copying of each of the documents
in all other respects.
You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert
a copy of this License into the extracted document, and follow this
License in all other respects regarding verbatim copying of that
document.
7. AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of a
storage or distribution medium, is called an "aggregate" if the
copyright resulting from the compilation is not used to limit the
legal rights of the compilation's users beyond what the individual
works permit. When the Document is included in an aggregate, this
License does not apply to the other works in the aggregate which
are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half
of the entire aggregate, the Document's Cover Texts may be placed
on covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic
form. Otherwise they must appear on printed covers that bracket
the whole aggregate.
8. TRANSLATION
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section
4. Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections. You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also
include the original English version of this License and the
original versions of those notices and disclaimers. In case of a
disagreement between the translation and the original version of
this License or a notice or disclaimer, the original version will
prevail.
If a section in the Document is Entitled "Acknowledgements",
"Dedications", or "History", the requirement (section 4) to
Preserve its Title (section 1) will typically require changing the
actual title.
9. TERMINATION
You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense, or distribute it is void,
and will automatically terminate your rights under this License.
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from
that copyright holder, and you cure the violation prior to 30 days
after your receipt of the notice.
Termination of your rights under this section does not terminate
the licenses of parties who have received copies or rights from you
under this License. If your rights have been terminated and not
permanently reinstated, receipt of a copy of some or all of the
same material does not give you any rights to use it.
10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
.
Each version of the License is given a distinguishing version
number. If the Document specifies that a particular numbered
version of this License "or any later version" applies to it, you
have the option of following the terms and conditions either of
that specified version or of any later version that has been
published (not as a draft) by the Free Software Foundation. If the
Document does not specify a version number of this License, you may
choose any version ever published (not as a draft) by the Free
Software Foundation. If the Document specifies that a proxy can
decide which future versions of this License can be used, that
proxy's public statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
11. RELICENSING
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server.
A "Massive Multiauthor Collaboration" (or "MMC") contained in the
site means any set of copyrightable works thus published on the MMC
site.
"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
"Incorporate" means to publish or republish a Document, in whole or
in part, as part of another Document.
An MMC is "eligible for relicensing" if it is licensed under this
License, and if all works that were first published under this
License somewhere other than this MMC, and subsequently
incorporated in whole or in part into the MMC, (1) had no cover
texts or invariant sections, and (2) were thus incorporated prior
to November 1, 2008.
The operator of an MMC Site may republish an MMC contained in the
site under CC-BY-SA on the same site at any time before August 1,
2009, provided the MMC is eligible for relicensing.
ADDENDUM: How to use this License for your documents
====================================================
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and license
notices just after the title page:
Copyright (C) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled ``GNU
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover
Texts, replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with
the Front-Cover Texts being LIST, and with the Back-Cover Texts
being LIST.
If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of free
software license, such as the GNU General Public License, to permit
their use in free software.
File: units.info, Node: Index, Prev: GNU Free Documentation License, Up: Top
Index
*****
[index ]
* Menu:
* '!' to indicate primitive units: Defining New Units. (line 6)
* '!endlocale': Localization. (line 6)
* '!endutf8': Unicode Support. (line 6)
* '!include': Units Data Files. (line 6)
* '!locale': Localization. (line 6)
* '!unitlist': Defining Unit List Aliases.
(line 6)
* '!utf8': Unicode Support. (line 6)
* '*' operator: Operators. (line 14)
* '**' operator: Operators. (line 65)
* '+' operator: Sums and Differences of Units.
(line 6)
* '-' as multiplication operator: Backwards Compatibility.
(line 17)
* '-' as subtraction operator: Sums and Differences of Units.
(line 6)
* --check (option for 'units'): Invoking Units. (line 50)
* --check-verbose (option for 'units'): Invoking Units. (line 59)
* --compact (option for 'units'): Invoking Units. (line 170)
* --digits (option for 'units'): Invoking Units. (line 67)
* --exponential (option for 'units'): Invoking Units. (line 84)
* --file (option for 'units'): Invoking Units. (line 115)
* --file (option for 'units') <1>: Invoking Units. (line 137)
* --help (option for 'units'): Invoking Units. (line 146)
* --info (option for 'units'): Invoking Units. (line 256)
* --locale (option for 'units'): Invoking Units. (line 275)
* --log (option for 'units'): Invoking Units. (line 127)
* --minus (option for 'units'): Invoking Units. (line 150)
* --newstar (option for 'units'): Invoking Units. (line 165)
* --oldstar (option for 'units'): Invoking Units. (line 161)
* --one-line (option for 'units'): Invoking Units. (line 218)
* --output-format (option for 'units'): Invoking Units. (line 93)
* --product (option for 'units'): Invoking Units. (line 155)
* --quiet (option for 'units'): Invoking Units. (line 176)
* --silent (option for 'units'): Invoking Units. (line 176)
* --strict (option for 'units'): Invoking Units. (line 209)
* --terse (option for 'units'): Invoking Units. (line 225)
* --unitsfile (option for 'units'): Invoking Units. (line 270)
* --verbose (option for 'units'): Invoking Units. (line 234)
* --verbose-check (option for 'units'): Invoking Units. (line 59)
* --version (option for 'units'): Invoking Units. (line 241)
* -1 (option for 'units'): Invoking Units. (line 218)
* -c (option for 'units'): Invoking Units. (line 50)
* -d (option for 'units'): Invoking Units. (line 67)
* -e (option for 'units'): Invoking Units. (line 84)
* -f (option for 'units'): Invoking Units. (line 115)
* -f (option for 'units') <1>: Invoking Units. (line 137)
* -h (option for 'units'): Invoking Units. (line 146)
* -I (option for 'units'): Invoking Units. (line 256)
* -L (option for 'units'): Invoking Units. (line 127)
* -l (option for 'units'): Invoking Units. (line 275)
* -m (option for 'units'): Invoking Units. (line 150)
* -o (option for 'units'): Invoking Units. (line 93)
* -p (option for 'units'): Invoking Units. (line 155)
* -q (option for 'units'): Invoking Units. (line 176)
* -s (option for 'units'): Invoking Units. (line 209)
* -t (option for 'units'): Invoking Units. (line 225)
* -U (option for 'units'): Invoking Units. (line 270)
* -v (option for 'units'): Invoking Units. (line 234)
* -V (option for 'units'): Invoking Units. (line 241)
* '?' for unit completion with 'readline': Readline Support. (line 16)
* '?' to show conformable units: Interactive Use. (line 131)
* '_' to use result of previous conversion: Previous Result. (line 6)
* '|' operator: Operators. (line 46)
* abrasive grit size: Other Nonlinear Units.
(line 36)
* addition of units: Sums and Differences of Units.
(line 9)
* additional units data files: Units Data Files. (line 6)
* backwards compatibility: Backwards Compatibility.
(line 6)
* British Imperial measure: Unit Definitions. (line 36)
* circle, area of: Other Nonlinear Units.
(line 42)
* command, '!' to indicate primitive units: Defining New Units.
(line 6)
* command, '!endlocale': Localization. (line 6)
* command, '!endutf8': Unicode Support. (line 6)
* command, '!endvar': Localization. (line 6)
* command, '!include': Units Data Files. (line 6)
* command, '!locale': Localization. (line 6)
* command, '!message': Localization. (line 6)
* command, '!set': Localization. (line 6)
* command, '!unitlist': Defining Unit List Aliases.
(line 6)
* command, '!utf8': Unicode Support. (line 6)
* command, '!var': Localization. (line 6)
* command, '!varnot': Localization. (line 6)
* command-line options: Invoking Units. (line 6)
* command-line unit conversion: Command Line Use. (line 6)
* commands in units database: Database Syntax. (line 6)
* compatibility: Backwards Compatibility.
(line 6)
* compatibility with earlier versions: Backwards Compatibility.
(line 6)
* completion, unit, using '?' ('readline' only): Readline Support.
(line 16)
* conformable units, '?' to show: Interactive Use. (line 131)
* currency, updating: Currency. (line 6)
* Darcy-Weisbach equation: Complicated Unit Expressions.
(line 7)
* data files: Data Files. (line 6)
* data files, additional: Units Data Files. (line 6)
* database syntax summary: Database Syntax. (line 6)
* defining nonlinear units: Defining Nonlinear Units.
(line 6)
* defining piecewise linear units: Piecewise Linear Units.
(line 6)
* defining prefixes: Defining New Units. (line 6)
* defining unit list aliases: Defining Unit List Aliases.
(line 6)
* defining units: Defining New Units. (line 6)
* defining units with '-': Backwards Compatibility.
(line 33)
* differences of units: Sums and Differences of Units.
(line 9)
* dimensionless units: Interactive Use. (line 129)
* dimensionless units, defining: Defining New Units. (line 38)
* division of numbers: Operators. (line 46)
* division of units: Operators. (line 14)
* domain, nonlinear unit definitions: Defining Nonlinear Units.
(line 90)
* environment dependent definitions: Localization. (line 6)
* environment variable, HOME: Environment Vars. (line 9)
* environment variable, LANG: Environment Vars. (line 20)
* environment variable, LC_CTYPE: Environment Vars. (line 20)
* environment variable, MYUNITSFILE: Units Data Files. (line 43)
* environment variable, MYUNITSFILE <1>: Environment Vars. (line 25)
* environment variable, PAGER: Environment Vars. (line 31)
* environment variable, UNITSFILE: Environment Vars. (line 42)
* environment variable, UNITSLOCALEMAP: Environment Vars. (line 49)
* environment variable, UNITS_ENGLISH: Environment Vars. (line 38)
* environment variables: Environment Vars. (line 6)
* exchange rates, updating: Currency. (line 6)
* exponent operator: Operators. (line 65)
* files, data: Data Files. (line 6)
* flags, output format: Flags. (line 6)
* format specification, output: Format Specification.
(line 6)
* fractions, numerical: Operators. (line 46)
* functions of units: Defining Nonlinear Units.
(line 162)
* functions, built in: Built-in Functions. (line 6)
* help: Interactive Use. (line 137)
* help <1>: Environment Vars. (line 31)
* HOME environment variable: Environment Vars. (line 9)
* hyphen as multiplication operator: Backwards Compatibility.
(line 17)
* Imperial measure: Unit Definitions. (line 36)
* include files: Defining New Units. (line 15)
* including additional units data files: Units Data Files. (line 6)
* incompatible units: Interactive Use. (line 87)
* interactive use: Interactive Use. (line 6)
* international mile: Unit Definitions. (line 76)
* international yard: Unit Definitions. (line 76)
* invoking units: Invoking Units. (line 6)
* LANG environment variable: Environment Vars. (line 20)
* LC_CTYPE environment variable: Environment Vars. (line 20)
* length measure, English customary: Unit Definitions. (line 76)
* length measure, UK: Unit Definitions. (line 76)
* linear interpolation: Piecewise Linear Units.
(line 6)
* locale: Locale. (line 6)
* 'locale_map.txt': Locale. (line 17)
* localization: Localization. (line 6)
* log file: Logging Calculations.
(line 6)
* logging calculations: Logging Calculations.
(line 6)
* measure, Imperial: Unit Definitions. (line 36)
* mile, international: Unit Definitions. (line 76)
* minus ('-') operator, subtraction: Sums and Differences of Units.
(line 6)
* multiplication of units: Operators. (line 14)
* multiplication, hyphen: Backwards Compatibility.
(line 17)
* MYUNITSFILE environment variable: Units Data Files. (line 43)
* MYUNITSFILE environment variable <1>: Environment Vars. (line 25)
* non-conformable units: Interactive Use. (line 87)
* non-interactive unit conversion: Command Line Use. (line 6)
* nonlinear unit conversions: Nonlinear Conversions.
(line 6)
* nonlinear unit conversions <1>: Defining Nonlinear Units.
(line 6)
* nonlinear units, defining: Defining Nonlinear Units.
(line 6)
* nonlinear units, other: Other Nonlinear Units.
(line 6)
* numbers as units: Numbers as Units. (line 6)
* numeric output format: Numeric Output Format.
(line 6)
* numerical fractions: Operators. (line 46)
* operator precedence: Operators. (line 36)
* operator, ('**'): Operators. (line 65)
* operator, caret ('^'): Operators. (line 65)
* operator, hyphen ('-') as multiplication: Backwards Compatibility.
(line 17)
* operator, hyphen ('-') as subtraction: Sums and Differences of Units.
(line 6)
* operator, minus ('-'): Sums and Differences of Units.
(line 6)
* operator, 'per': Operators. (line 14)
* operator, plus ('+'): Sums and Differences of Units.
(line 6)
* operator, slash ('/'): Operators. (line 14)
* operator, solidus ('/'): Operators. (line 14)
* operator, space: Operators. (line 14)
* operator, star ('*'): Operators. (line 14)
* operator, vertical bar ('|'): Operators. (line 46)
* operators: Operators. (line 6)
* output field width: Field Width. (line 6)
* output format: Numeric Output Format.
(line 6)
* output format flags: Flags. (line 6)
* output format specification: Format Specification.
(line 6)
* output precision: Precision. (line 6)
* PAGER environment variable: Environment Vars. (line 31)
* parentheses: Operators. (line 29)
* parentheses <1>: Operators. (line 36)
* parentheses <2>: Operators. (line 65)
* parentheses <3>: Sums and Differences of Units.
(line 33)
* parentheses <4>: Complicated Unit Expressions.
(line 27)
* parentheses <5>: Defining New Units. (line 47)
* parentheses <6>: Defining New Units. (line 71)
* parentheses <7>: Defining Nonlinear Units.
(line 36)
* 'per' operator: Operators. (line 14)
* personal units data file: Units Data Files. (line 28)
* piecewise linear units: Piecewise Linear Units.
(line 6)
* plus ('+') operator: Sums and Differences of Units.
(line 6)
* powers: Operators. (line 65)
* precision, output: Precision. (line 6)
* prefixes: Unit Definitions. (line 55)
* prefixes and exponents: Operators. (line 77)
* prefixes, definition of: Defining New Units. (line 6)
* previous result: Previous Result. (line 6)
* primitive units: Defining New Units. (line 6)
* products of units: Operators. (line 14)
* quotients of units: Operators. (line 14)
* range, nonlinear unit definitions: Defining Nonlinear Units.
(line 90)
* 'readline', use with 'units': Readline Support. (line 6)
* reciprocal conversion: Interactive Use. (line 62)
* roots: Built-in Functions. (line 27)
* setlocale function: Locale. (line 17)
* slash ('/') operator: Operators. (line 14)
* solidus ('/') operator: Operators. (line 14)
* sphere, volume of: Other Nonlinear Units.
(line 42)
* square roots: Built-in Functions. (line 27)
* star ('*') operator: Operators. (line 14)
* State Plane Coordinate System, US: Unit Definitions. (line 76)
* strict conversion: Interactive Use. (line 71)
* subtraction of units: Sums and Differences of Units.
(line 9)
* sums and differences of units: Sums and Differences of Units.
(line 6)
* sums of units: Sums and Differences of Units.
(line 9)
* sums of units <1>: Unit Lists. (line 6)
* survey foot, US: Unit Definitions. (line 76)
* survey measure, US: Unit Definitions. (line 76)
* survey mile, US: Unit Definitions. (line 76)
* syntax of units database: Database Syntax. (line 6)
* temperature conversions: Temperature Conversions.
(line 6)
* Unicode support: Unicode Support. (line 6)
* unit completion using '?' ('readline' only): Readline Support.
(line 16)
* unit definitions: Unit Definitions. (line 6)
* unit expressions: Unit Expressions. (line 6)
* unit expressions, complicated: Complicated Unit Expressions.
(line 6)
* unit list aliases, defining: Defining Unit List Aliases.
(line 6)
* unit lists: Unit Lists. (line 6)
* unit name completion: Readline Support. (line 19)
* units data file, personal: Units Data Files. (line 28)
* units data files, additional: Units Data Files. (line 6)
* units definitions, adding: Defining New Units. (line 6)
* units definitions, changing: Defining New Units. (line 6)
* units functions: Defining Nonlinear Units.
(line 162)
* units quotients: Operators. (line 14)
* units, definition of: Defining New Units. (line 6)
* units, lookup method: Unit Definitions. (line 46)
* units, piecewise linear: Piecewise Linear Units.
(line 6)
* units, primitive: Defining New Units. (line 6)
* units, sums and differences: Sums and Differences of Units.
(line 6)
* units, sums of: Unit Lists. (line 6)
* UNITSFILE environment variable: Environment Vars. (line 42)
* UNITSLOCALEMAP environment variable: Environment Vars. (line 49)
* UNITS_ENGLISH environment variable: Environment Vars. (line 38)
* US State Plane Coordinate System: Unit Definitions. (line 76)
* US survey foot: Unit Definitions. (line 76)
* US survey measure: Unit Definitions. (line 76)
* US survey mile: Unit Definitions. (line 76)
* UTF-8: Unicode Support. (line 6)
* verbose output: Interactive Use. (line 53)
* verbose output <1>: Interactive Use. (line 71)
* vertical bar ('|') operator: Operators. (line 46)
* volume measure, English customary: Unit Definitions. (line 61)
* wire gauge: Other Nonlinear Units.
(line 14)
* yard, international: Unit Definitions. (line 76)
Tag Table:
Node: Top842
Node: Overview2324
Ref: Overview-Footnote-14088
Node: Interactive Use4282
Node: Command Line Use10178
Node: Unit Definitions11424
Node: Unit Expressions17565
Node: Operators18178
Node: Sums and Differences of Units23297
Node: Numbers as Units25339
Node: Built-in Functions26144
Node: Previous Result27427
Node: Complicated Unit Expressions29754
Node: Backwards Compatibility31389
Node: Nonlinear Conversions33290
Node: Temperature Conversions33729
Node: Other Nonlinear Units35794
Node: Unit Lists38931
Node: Logging Calculations47703
Node: Invoking Units50363
Ref: Invoking Units-Footnote-163090
Node: Defining Your Own Units63344
Node: Units Data Files63882
Node: Defining New Units66370
Node: Defining Nonlinear Units70273
Node: Piecewise Linear Units78450
Node: Defining Unit List Aliases82207
Node: Numeric Output Format83367
Node: Format Specification84640
Node: Flags86602
Node: Field Width88685
Node: Precision89720
Node: Localization92177
Node: Locale92620
Node: Additional Localization94633
Node: Environment Vars99086
Node: Data Files101645
Node: Unicode Support103432
Node: Readline Support106392
Node: Currency108536
Node: Database Syntax109773
Node: GNU Free Documentation License111836
Node: Index136968
End Tag Table
units-2.12/parse.y 0000664 0001750 0001750 00000031324 12303457637 013401 0 ustar adrian adrian /*
* parse.y: the parser for GNU units, a program for units conversion
* Copyright (C) 1999, 2000, 2001, 2002, 2007, 2009, 2014 Free Software
* Foundation, Inc
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 3 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*
* This program was written by Adrian Mariano (adrianm@gnu.org)
*/
%{
#include "units.h"
struct commtype {
int location;
char *data;
struct unittype *result;
int errorcode;
char *paramname;
struct unittype *paramvalue;
};
static int err; /* value used by parser to store return values */
#define CHECK if (err) { comm->errorcode=err; YYABORT; }
int yylex();
void yyerror(struct commtype *comm, char *);
#define MEMSIZE 100
struct unittype *memtable[MEMSIZE];
int nextunit=0;
int maxunit=0;
struct function {
char *name;
double (*func)(double);
int type;
};
#define DIMENSIONLESS 0
#define ANGLEIN 1
#define ANGLEOUT 2
struct unittype *
getnewunit()
{
if (nextunit>=MEMSIZE)
return 0;
memtable[nextunit] = (struct unittype *)
mymalloc(sizeof(struct unittype),"(getnewunit)");
if (!memtable[nextunit])
return 0;
initializeunit(memtable[nextunit]);
return memtable[nextunit++];
}
struct unittype *
makenumunit(double num,int *myerr)
{
struct unittype *ret;
ret=getnewunit();
if (!ret){
*myerr = E_PARSEMEM;
return 0;
}
ret->factor = num;
*myerr = 0;
return ret;
}
double
logb2(double x)
{
return log(x)/log(2.0);
}
int
funcunit(struct unittype *theunit, struct function *fun)
{
struct unittype angleunit;
if (fun->type==ANGLEIN){
err=unit2num(theunit);
if (err==E_NOTANUMBER){
initializeunit(&angleunit);
angleunit.denominator[0] = dupstr("radian");
angleunit.denominator[1] = 0;
err = multunit(theunit, &angleunit);
freeunit(&angleunit);
if (!err)
err = unit2num(theunit);
}
if (err)
return err;
} else if (fun->type==ANGLEOUT || fun->type == DIMENSIONLESS) {
if ((err=unit2num(theunit)))
return err;
} else
return E_BADFUNCTYPE;
errno = 0;
theunit->factor = (*(fun->func))(theunit->factor);
if (errno)
return E_FUNC;
if (fun->type==ANGLEOUT) {
theunit->numerator[0] = dupstr("radian");
theunit->numerator[1] = 0;
}
return 0;
}
%}
%parse-param {struct commtype *comm}
%lex-param {struct commtype *comm}
%pure_parser
%name-prefix="units"
%union {
double number;
int integer;
struct unittype *utype;
struct function *dfunc;
struct func *ufunc;
}
%token REAL
%token UNIT
%token RFUNC
%token UFUNC
%token EXPONENT
%token MULTIPLY
%token MULTSTAR
%token DIVIDE
%token NUMDIV
%token SQRT
%token CUBEROOT
%token MULTMINUS
%token EOL
%token FUNCINV
%token MEMERROR
%token BADNUMBER
%token UNITEND
%token LASTUNSET
%type numexpr
%type expr
%type list
%type pexpr
%type unitexpr
%left ADD MINUS
%left UNARY
%left DIVIDE MULTSTAR
%left MULTIPLY MULTMINUS
%nonassoc '(' SQRT CUBEROOT RFUNC UNIT REAL UFUNC FUNCINV MEMERROR BADNUMBER UNITEND LASTUNSET
%right EXPONENT
%left NUMDIV
%%
input: EOL { comm->result = makenumunit(1,&err); CHECK; YYACCEPT; }
| unitexpr EOL { comm->result = $1; YYACCEPT; }
| error { YYABORT; }
;
unitexpr: expr {$$ = $1;}
| DIVIDE list { invertunit($2); $$=$2;}
;
expr: list { $$ = $1; }
| MULTMINUS list %prec UNARY { $$ = $2; $$->factor *= -1; }
| MINUS list %prec UNARY { $$ = $2; $$->factor *= -1; }
| expr ADD expr { err = addunit($1,$3); CHECK; $$=$1;}
| expr MINUS expr { $3->factor *= -1; err = addunit($1,$3);
CHECK; $$=$1;}
| expr DIVIDE expr { err = divunit($1, $3); CHECK; $$=$1;}
| expr MULTIPLY expr { err = multunit($1,$3); CHECK; $$=$1;}
| expr MULTSTAR expr { err = multunit($1,$3); CHECK; $$=$1;}
;
numexpr: REAL { $$ = $1; }
| numexpr NUMDIV numexpr { $$ = $1 / $3; }
;
pexpr: '(' expr ')' { $$ = $2; }
;
/* list is a list of units, possibly raised to powers, to be multiplied
together. */
list: numexpr { $$ = makenumunit($1,&err); CHECK;}
| UNIT { $$ = $1; }
| list EXPONENT list { err = unitpower($1,$3); CHECK; $$=$1;}
| list MULTMINUS list { err = multunit($1,$3); CHECK; $$=$1;}
| list list %prec MULTIPLY { err = multunit($1,$2); CHECK; $$=$1;}
| pexpr { $$=$1; }
| SQRT pexpr { err = rootunit($2,2); CHECK; $$=$2;}
| CUBEROOT pexpr { err = rootunit($2,3); CHECK; $$=$2;}
| RFUNC pexpr { err = funcunit($2,$1); CHECK; $$=$2;}
| UFUNC pexpr { err = evalfunc($2,$1,0,0); CHECK; $$=$2;}
| FUNCINV UFUNC pexpr { err = evalfunc($3,$2,1,0); CHECK; $$=$3;}
| list EXPONENT MULTMINUS list %prec EXPONENT
{ $4->factor *= -1;
err = unitpower($1,$4); CHECK; $$=$1;}
| list EXPONENT MINUS list %prec EXPONENT
{ $4->factor *= -1;
err = unitpower($1,$4); CHECK; $$=$1;}
| BADNUMBER { err = E_BADNUM; CHECK; }
| MEMERROR { err = E_PARSEMEM; CHECK; }
| UNITEND { err = E_UNITEND; CHECK; }
| LASTUNSET { err = E_LASTUNSET; CHECK; }
| FUNCINV UNIT { err = E_NOTAFUNC; CHECK; }
;
%%
#ifndef strchr
# ifdef NO_STRCHR
# define strchr(a,b) index((a),(b))
# else
char *strchr();
# endif
#endif /* !strchr */
double strtod();
struct function
realfunctions[] = { {"sin", sin, ANGLEIN},
{"cos", cos, ANGLEIN},
{"tan", tan, ANGLEIN},
{"ln", log, DIMENSIONLESS},
{"log", log10, DIMENSIONLESS},
{"log2", logb2, DIMENSIONLESS},
{"exp", exp, DIMENSIONLESS},
{"acos", acos, ANGLEOUT},
{"atan", atan, ANGLEOUT},
{"asin", asin, ANGLEOUT},
{0, 0, 0}};
struct {
char op;
int value;
} optable[] = { {'*', MULTIPLY},
{'/', DIVIDE},
{'|', NUMDIV},
{'+', ADD},
{'(', '('},
{')', ')'},
{'^', EXPONENT},
{'~', FUNCINV},
{0, 0}};
struct {
char *name;
int value;
} strtable[] = { {"sqrt", SQRT},
{"cuberoot", CUBEROOT},
{"per" , DIVIDE},
{0, 0}};
#define LASTUNIT '_' /* Last unit symbol */
int yylex(YYSTYPE *lvalp, struct commtype *comm)
{
int length, count;
struct unittype *output;
char *inptr;
char *nonunitchars = "~;+-*/|\t\n^ ()"; /* Chars not allowed in unit name */
char *nonunitends = ".,_"; /* Can't start or end a unit */
char *number_start = ".,0123456789"; /* Can be first char of a number */
if (comm->location==-1) return 0;
inptr = comm->data + comm->location; /* Point to start of data */
/* Skip white space */
while( *inptr && strchr(WHITE,*inptr)) inptr++, comm->location++;
if (*inptr==0) {
comm->location = -1;
return EOL; /* Return failure if string has ended */
}
/* Check for **, an exponent operator. */
if (0==strncmp("**",inptr,2)){
comm->location += 2;
return EXPONENT;
}
/* Check for '-' and '*' which get special handling */
if (*inptr=='-'){
comm->location++;
if (parserflags.minusminus)
return MINUS;
return MULTMINUS;
}
if (*inptr=='*'){
comm->location++;
if (parserflags.oldstar)
return MULTIPLY;
return MULTSTAR;
}
/* Check for the "last unit" symbol */
if (*inptr == LASTUNIT) {
comm->location++;
if (!lastunitset)
return LASTUNSET;
output = getnewunit();
if (!output)
return MEMERROR;
unitcopy(output, &lastunit);
lvalp->utype = output;
return UNIT;
}
/* Look for single character ops */
for(count=0; optable[count].op; count++){
if (*inptr==optable[count].op) {
comm->location++;
return optable[count].value;
}
}
/* Look for numbers */
if (strchr(number_start,*inptr)){ /* prevent "nan" from being recognized */
char *endloc;
lvalp->number = strtod(inptr, &endloc);
if (inptr != endloc) {
comm->location += (endloc-inptr);
if (*endloc && strchr(number_start,*endloc))
return BADNUMBER;
else
return REAL;
}
}
/* Look for a word (function name or unit name) */
length = strcspn(inptr,nonunitchars);
if (!length){ /* Next char is not a valid unit char */
comm->location++;
return 0;
}
/* Check that unit name doesn't start or end with forbidden chars */
if (strchr(nonunitends,*inptr)){
comm->location++;
return 0;
}
if (strchr(nonunitends, inptr[length-1])){
comm->location+=length;
return 0;
}
/* Look for string operators */
for(count=0;strtable[count].name;count++){
if (length==strlen(strtable[count].name) &&
0==strncmp(strtable[count].name,inptr,length)){
comm->location += length;
return strtable[count].value;
}
}
/* Look for real function names */
for(count=0;realfunctions[count].name;count++){
if (length==strlen(realfunctions[count].name) &&
0==strncmp(realfunctions[count].name,inptr,length)){
lvalp->dfunc = realfunctions+count;
comm->location += length;
return RFUNC;
}
}
/* Look for function parameter */
if (function_parameter && length==strlen(function_parameter) &&
0==strncmp(function_parameter, inptr, length)){
output = getnewunit();
if (!output)
return MEMERROR;
unitcopy(output, parameter_value);
lvalp->utype = output;
comm->location += length;
return UNIT;
}
/* Look for user defined function */
lvalp->ufunc = fnlookup(inptr,length);
if (lvalp->ufunc){
comm->location += length;
return UFUNC;
}
/* Didn't find a special string, so treat it as unit name */
comm->location+=length;
if (strchr("23456789",inptr[length-1]) &&
!hassubscript(inptr,length)) { /* do exponent handling like m3 */
count = inptr[length-1] - '0';
length--;
if (strchr(number_start, inptr[length-1])){
return UNITEND;
}
} else count=1;
output = getnewunit();
if (!output)
return MEMERROR;
output->numerator[count]=0;
for(;count;count--){
output->numerator[count-1] = mymalloc(length+1,"(yylex)");
strncpy(output->numerator[count-1], inptr, length);
output->numerator[count-1][length]=0;
}
lvalp->utype=output;
return UNIT;
}
void yyerror(struct commtype *comm, char *s){}
void
freelist(int startunit)
{
if (nextunit>maxunit)
maxunit = nextunit;
while(nextunit>startunit){
freeunit(memtable[--nextunit]);
free(memtable[nextunit]);
}
}
int
parseunit(struct unittype *output, char *input,char **errstr,int *errloc)
{
struct commtype comm;
int startunit;
startunit = nextunit;
initializeunit(output);
comm.location = 0;
comm.data = input;
comm.errorcode = E_PARSE; /* Assume parse error */
errno=0;
if (yyparse(&comm) || errno){
if (comm.location==-1)
comm.location = strlen(input);
if (errstr){
if (comm.errorcode==E_FUNC || errno)
*errstr = strerror(errno);
else
*errstr=errormsg[comm.errorcode];
}
if (errloc)
*errloc = comm.location;
freelist(startunit);
return comm.errorcode;
} else {
if (errstr)
*errstr = 0;
multunit(output,comm.result);
freeunit(comm.result);
freelist(startunit);
return 0;
}
}
units-2.12/fdl-1.3.texi 0000664 0001750 0001750 00000055607 12007313547 014036 0 ustar adrian adrian @c The GNU Free Documentation License.
@center Version 1.3, 3 November 2008
@c This file is intended to be included within another document,
@c hence no sectioning command or @node.
@display
Copyright @copyright{} 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
@uref{http://fsf.org/}
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@end display
@enumerate 0
@item
PREAMBLE
The purpose of this License is to make a manual, textbook, or other
functional and useful document @dfn{free} in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
This License is a kind of ``copyleft'', which means that derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
@item
APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
work under the conditions stated herein. The ``Document'', below,
refers to any such manual or work. Any member of the public is a
licensee, and is addressed as ``you''. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
A ``Modified Version'' of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
A ``Secondary Section'' is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
any mathematics.) The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
The ``Invariant Sections'' are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
The ``Cover Texts'' are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
A ``Transparent'' copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
pixels) generic paint programs or (for drawings) some widely available
drawing editor, and that is suitable for input to text formatters or
for automatic translation to a variety of formats suitable for input
to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not ``Transparent'' is called ``Opaque''.
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, La@TeX{} input
format, SGML or XML using a publicly available
DTD, and standard-conforming simple HTML,
PostScript or PDF designed for human modification. Examples
of transparent image formats include PNG, XCF and
JPG. Opaque formats include proprietary formats that can be
read and edited only by proprietary word processors, SGML or
XML for which the DTD and/or processing tools are
not generally available, and the machine-generated HTML,
PostScript or PDF produced by some word processors for
output purposes only.
The ``Title Page'' means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, ``Title Page'' means
the text near the most prominent appearance of the work's title,
preceding the beginning of the body of the text.
The ``publisher'' means any person or entity that distributes copies
of the Document to the public.
A section ``Entitled XYZ'' means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as ``Acknowledgements'',
``Dedications'', ``Endorsements'', or ``History''.) To ``Preserve the Title''
of such a section when you modify the Document means that it remains a
section ``Entitled XYZ'' according to this definition.
The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
@item
VERBATIM COPYING
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
@item
COPYING IN QUANTITY
If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
Document's license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
you as the publisher of these copies. The front cover must present
the full title with all words of the title equally prominent and
visible. You may add other material on the covers in addition.
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
public has access to download using public-standard network protocols
a complete Transparent copy of the Document, free of added material.
If you use the latter option, you must take reasonably prudent steps,
when you begin distribution of Opaque copies in quantity, to ensure
that this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
@item
MODIFICATIONS
You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:
@enumerate A
@item
Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
@item
List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
@item
State on the Title page the name of the publisher of the
Modified Version, as the publisher.
@item
Preserve all the copyright notices of the Document.
@item
Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
@item
Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
@item
Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document's license notice.
@item
Include an unaltered copy of this License.
@item
Preserve the section Entitled ``History'', Preserve its Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled ``History'' in the Document, create one
stating the title, year, authors, and publisher of the Document as
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
@item
Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the ``History'' section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
@item
For any section Entitled ``Acknowledgements'' or ``Dedications'', Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.
@item
Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
@item
Delete any section Entitled ``Endorsements''. Such a section
may not be included in the Modified Version.
@item
Do not retitle any existing section to be Entitled ``Endorsements'' or
to conflict in title with any Invariant Section.
@item
Preserve any Warranty Disclaimers.
@end enumerate
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
list of Invariant Sections in the Modified Version's license notice.
These titles must be distinct from any other section titles.
You may add a section Entitled ``Endorsements'', provided it contains
nothing but endorsements of your Modified Version by various
parties---for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
through arrangements made by) any one entity. If the Document already
includes a cover text for the same cover, previously added by you or
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
@item
COMBINING DOCUMENTS
You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
adding at the end of it, in parentheses, the name of the original
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled ``History''
in the various original documents, forming one section Entitled
``History''; likewise combine any sections Entitled ``Acknowledgements'',
and any sections Entitled ``Dedications''. You must delete all
sections Entitled ``Endorsements.''
@item
COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
@item
AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an ``aggregate'' if the copyright
resulting from the compilation is not used to limit the legal rights
of the compilation's users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
the entire aggregate, the Document's Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
@item
TRANSLATION
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections. You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
If a section in the Document is Entitled ``Acknowledgements'',
``Dedications'', or ``History'', the requirement (section 4) to Preserve
its Title (section 1) will typically require changing the actual
title.
@item
TERMINATION
You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense, or distribute it is void, and
will automatically terminate your rights under this License.
However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
@item
FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
@uref{http://www.gnu.org/copyleft/}.
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License ``or any later version'' applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation. If the Document
specifies that a proxy can decide which future versions of this
License can be used, that proxy's public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.
@item
RELICENSING
``Massive Multiauthor Collaboration Site'' (or ``MMC Site'') means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server. A
``Massive Multiauthor Collaboration'' (or ``MMC'') contained in the
site means any set of copyrightable works thus published on the MMC
site.
``CC-BY-SA'' means the Creative Commons Attribution-Share Alike 3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
``Incorporate'' means to publish or republish a Document, in whole or
in part, as part of another Document.
An MMC is ``eligible for relicensing'' if it is licensed under this
License, and if all works that were first published under this License
somewhere other than this MMC, and subsequently incorporated in whole
or in part into the MMC, (1) had no cover texts or invariant sections,
and (2) were thus incorporated prior to November 1, 2008.
The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.
@end enumerate
@page
@heading ADDENDUM: How to use this License for your documents
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
@smallexample
@group
Copyright (C) @var{year} @var{your name}.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled ``GNU
Free Documentation License''.
@end group
@end smallexample
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
replace the ``with@dots{}Texts.''@: line with this:
@smallexample
@group
with the Invariant Sections being @var{list their titles}, with
the Front-Cover Texts being @var{list}, and with the Back-Cover Texts
being @var{list}.
@end group
@end smallexample
If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
@c Local Variables:
@c ispell-local-pdict: "ispell-dict"
@c End:
units-2.12/locale_map.txt 0000664 0001750 0001750 00000012706 11747125613 014732 0 ustar adrian adrian Afrikaans_South Africa af_ZA
Albanian_Albania sq_AL
Alsatian_France gsw_FR
Amharic_Ethiopia am_ET
Arabic_Algeria ar_DZ
Arabic_Bahrain ar_BH
Arabic_Egypt ar_EG
Arabic_Iraq ar_IQ
Arabic_Jordan ar_JO
Arabic_Kuwait ar_KW
Arabic_Lebanon ar_LB
Arabic_Libya ar_LY
Arabic_Morocco ar_MA
Arabic_Oman ar_OM
Arabic_Qatar ar_QA
Arabic_Saudi Arabia ar_SA
Arabic_Syria ar_SY
Arabic_Tunisia ar_TN
Arabic_U.A.E. ar_AE
Arabic_Yemen ar_YE
Armenian_Armenia hy_AM
Assamese_India as_IN
Azeri_Azerbaijan, Cyrillic az_AZ
Azeri_Azerbaijan, Latin az_AZ
Bashkir_Russia ba_RU
Basque_Basque eu_ES
Belarusian_Belarus be_BY
Bengali_Bangladesh bn_??
Bengali_India bn_IN
Bosnian_Neutral bs_??
Bosnian_Bosnia and Herzegovina, Cyrillic bs_BA
Bosnian_Bosnia and Herzegovina, Latin bs_BA
Breton_France br_FR
Bulgarian_Bulgaria bg_BG
Central Kurdish_Iraq ku_IQ
Cherokee_Cherokee chr_Cher
Catalan_Spain ca_ES
Chinese_Hong Kong SAR, PRC zh_HK
Chinese_Macao SAR zh_MO
Chinese_Singapore zh_SG
Chinese_Simplified zh_Hans
Chinese_Traditional zh_Hant
Corsican_France co_FR
Croatian_Neutral hr_??
Croatian_Bosnia and Herzegovina, Latin hr_BA
Croatian_Croatia hr_HR
Czech_Czech Republic cs_CZ
Danish_Denmark da_DK
Dari_Afghanistan prs_AF
Divehi_Maldives dv_MV
Dutch_Belgium nl_BE
Dutch_Netherlands nl_NL
English_Australia en_AU
English_Belize en_BZ
English_Canada en_CA
English_Caribbean en_029
English_India en_IN
English_Ireland en_IE
English_Ireland en_IE
English_Jamaica en_JM
English_Malaysia en_MY
English_New Zealand en_NZ
English_Philippines en_PH
English_Singapore en_SG
English_South Africa en_ZA
English_Trinidad and Tobago en_TT
English_United Kingdom en_GB
English_United States en_US
English_Zimbabwe en_ZW
Estonian_Estonia et_EE
Faroese_Faroe Islands fo_FO
Filipino_Philippines fil_PH
Finnish_Finland fi_FI
French_Belgium fr_BE
French_Canada fr_CA
French_France fr_FR
French_Luxembourg fr_LU
French_Monaco fr_MC
French_Switzerland fr_CH
Frisian_Netherlands fy_NL
Galician_Spain gl_ES
Georgian_Georgia ka_GE
German_Austria de_AT
German_Germany de_DE
German_Liechtenstein de_LI
German_Luxembourg de_LU
German_Switzerland de_CH
Greek_Greece el_GR
Greenlandic_Greenland kl_GL
Gujarati_India gu_IN
Hausa_Nigeria ha_NG
Hawiian_United States haw_US
Hebrew_Israel he_IL
Hindi_India hi_IN
Hungarian_Hungary hu_HU
Icelandic_Iceland is_IS
Igbo_Nigeria ig_NG
Indonesian_Indonesia id_ID
Inuktitut_Canada iu_CA, Latin
Inuktitut_Canada iu_CA, Canadian Syllabics
Irish_Ireland ga_IE
isiXhosa_South Africa xh_ZA
isiZulu_South Africa zu_ZA
Italian_Italy it_IT
Italian_Switzerland it_CH
Japanese_Japan ja_JP
Kannada_India kn_IN
Kazakh_Kazakhstan kk_KZ
Khmer_Cambodia kh_KH
K'iche_Guatemala qut_GT
Kinyarwanda_Rwanda rw_RW
Konkani_India kok_IN
Korean_Korea ko_KR
Kyrgyz_Kyrgyzstan ky_KG
Lao_Lao PDR lo_LA
Latvian_Latvia lv_LV
Lithuanian_Lithuanian lt_LT
Lower Sorbian_Germany dsb_DE
Luxembourgish_Luxembourg lb_LU
Macedonian_Macedonia, FYROM mk_MK
Malay_Brunei Darassalam ms_BN
Malay_Malaysia ms_MY
Malayalam_India ml_IN
Maltese_Malta mt_MT
Maori_New Zealand mi_NZ
Mapudungun_Chile arn_CL
Marathi_India mr_IN
Mohawk_Canada moh_CA
Mongolian_Mongolia, Cyrillic mn_MN
Mongolian_Mongolia, Mong mn_MN
Nepali_Nepal ne_NP
Nepali_India ne_IN
Norwegian_BokmУЅl, Norway no_NO
Norwegian_Nynorsk, Norway no_NO
Occitan_France oc_FR
Oriya_India or_IN
Pashto_Afghanistan ps_AF
Persian_Iran fa_IR
Polish_Poland pl_PL
Portuguese_Brazil pt_BR
Portuguese_Portugal pt_PT
Pular_Senegal ff_SN
Punjabi_India, Gurmukhi script pa_IN
Punjabi_Pakistan, Arabic script pa_PK
Quechua_Bolivia quz_BO
Quechua_Ecuador quz_EC
Quechua_Peru quz_PE
Romanian_Romania ro_RO
Romansh_Switzerland rm_CH
Russian_Russia ru_RU
Sakha_Russia sah_RU
Sami_Inari, Finland smn_FI
Sami_Lule, Norway smj_NO
Sami_Lule, Sweden smj_SE
Sami_Northern, Finland se_FI
Sami_Northern, Norway se_NO
Sami_Northern, Sweden se_SE
Sami_Skolt, Finland sms_FI
Sami_Southern, Norway sma_NO
Sami_Southern, Sweden sma_SE
Sanskrit_India sa_IN
Serbian_Neutral sr_??
Serbian_Bosnia and Herzegovina, Cyrillic sr_BA
Serbian_Bosnia and Herzegovina, Latin sr_BA
Serbian_Croatia sr_HR
Serbian_Serbia and Montenegro, Former, Cyrillic sr_CS
Serbian_Serbia and Montenegro, Former, Latin sr_CS
Sesotho sa Leboa_South Africa nso_ZA
Setswana / Tswana_Botswana tn_BW
Setswana / Tswana_South Africa tn_ZA
Sindhi_Pakistan sd_PK
Sinhala_Sri Lanka si_LK
Slovak_Slovakia sk_SK
Slovenian_Slovenia sl_SI
Spanish_Argentina es_AR
Spanish_Bolivia es_BO
Spanish_Chile es_CL
Spanish_Colombia es_CO
Spanish_Costa Rica es_CR
Spanish_Dominican Republic es_DO
Spanish_Ecuador es_EC
Spanish_El Salvador es_SV
Spanish_Guatemala es_GT
Spanish_Honduras es_HN
Spanish_Mexico es_MX
Spanish_Nicaragua es_NI
Spanish_Panama es_PA
Spanish_Paraguay es_PY
Spanish_Peru es_PE
Spanish_Puerto Rico es_PR
Spanish_Spain, Modern Sort es_ES
Spanish_Spain, Traditional Sort es_ES
Spanish_United States es_US
Spanish_Uruguay es_UY
Spanish_Venezuela es_VE
Swahili_Kenya sw_KE
Swedish_Finland sv_FI
Swedish_Sweden sv_SE
Swedish_Sweden sv_SE
Syriac_Syria syr_SY
Tajik_Tajikistan, Cyrillic tg_TJ
Tamazight_Algeria, Latin tzm_DZ
Tamil_India ta_IN
Tamil_Sri Lanka ta_LK
Tatar_Russia tt_RU
Telugu_India te_IN
Thai_Thailand th_TH
Tibetan_PRC bo_CN
Tigrinya_Eritrea ti_ER
Tigrinya_Ethiopia ti_ET
Turkish_Turkey tr_TR
Turkmen_Turkmenistan tk_TM
Ukrainian_Ukraine uk_UA
Upper Sorbian_Germany hsb_DE
Urdu_(reserved) ur_??
Urdu_Pakistan ur_PK
Uyghur_PRC ug_CN
Uzbek_Uzbekistan, Cyrillic uz_UZ
Uzbek_Uzbekistan, Latin uz_UZ
Valencian_Valencia ca_ES-Valencia
Vietnamese_Vietnam vi_VN
Welsh_United Kingdom cy_GB
Wolof_Senegal wo_SN
Yi_PRC ii_CN
Yoruba_Nigeria yo_NG
units-2.12/parse.tab.c 0000664 0001750 0001750 00000176126 12303461132 014113 0 ustar adrian adrian /* A Bison parser, made by GNU Bison 2.5. */
/* Bison implementation for Yacc-like parsers in C
Copyright (C) 1984, 1989-1990, 2000-2011 Free Software Foundation, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see . */
/* As a special exception, you may create a larger work that contains
part or all of the Bison parser skeleton and distribute that work
under terms of your choice, so long as that work isn't itself a
parser generator using the skeleton or a modified version thereof
as a parser skeleton. Alternatively, if you modify or redistribute
the parser skeleton itself, you may (at your option) remove this
special exception, which will cause the skeleton and the resulting
Bison output files to be licensed under the GNU General Public
License without this special exception.
This special exception was added by the Free Software Foundation in
version 2.2 of Bison. */
/* C LALR(1) parser skeleton written by Richard Stallman, by
simplifying the original so-called "semantic" parser. */
/* All symbols defined below should begin with yy or YY, to avoid
infringing on user name space. This should be done even for local
variables, as they might otherwise be expanded by user macros.
There are some unavoidable exceptions within include files to
define necessary library symbols; they are noted "INFRINGES ON
USER NAME SPACE" below. */
/* Identify Bison output. */
#define YYBISON 1
/* Bison version. */
#define YYBISON_VERSION "2.5"
/* Skeleton name. */
#define YYSKELETON_NAME "yacc.c"
/* Pure parsers. */
#define YYPURE 1
/* Push parsers. */
#define YYPUSH 0
/* Pull parsers. */
#define YYPULL 1
/* Using locations. */
#define YYLSP_NEEDED 0
/* Substitute the variable and function names. */
#define yyparse unitsparse
#define yylex unitslex
#define yyerror unitserror
#define yylval unitslval
#define yychar unitschar
#define yydebug unitsdebug
#define yynerrs unitsnerrs
/* Copy the first part of user declarations. */
/* Line 268 of yacc.c */
#line 24 "parse.y"
#include "units.h"
struct commtype {
int location;
char *data;
struct unittype *result;
int errorcode;
char *paramname;
struct unittype *paramvalue;
};
static int err; /* value used by parser to store return values */
#define CHECK if (err) { comm->errorcode=err; YYABORT; }
int yylex();
void yyerror(struct commtype *comm, char *);
#define MEMSIZE 100
struct unittype *memtable[MEMSIZE];
int nextunit=0;
int maxunit=0;
struct function {
char *name;
double (*func)(double);
int type;
};
#define DIMENSIONLESS 0
#define ANGLEIN 1
#define ANGLEOUT 2
struct unittype *
getnewunit()
{
if (nextunit>=MEMSIZE)
return 0;
memtable[nextunit] = (struct unittype *)
mymalloc(sizeof(struct unittype),"(getnewunit)");
if (!memtable[nextunit])
return 0;
initializeunit(memtable[nextunit]);
return memtable[nextunit++];
}
struct unittype *
makenumunit(double num,int *myerr)
{
struct unittype *ret;
ret=getnewunit();
if (!ret){
*myerr = E_PARSEMEM;
return 0;
}
ret->factor = num;
*myerr = 0;
return ret;
}
double
logb2(double x)
{
return log(x)/log(2.0);
}
int
funcunit(struct unittype *theunit, struct function *fun)
{
struct unittype angleunit;
if (fun->type==ANGLEIN){
err=unit2num(theunit);
if (err==E_NOTANUMBER){
initializeunit(&angleunit);
angleunit.denominator[0] = dupstr("radian");
angleunit.denominator[1] = 0;
err = multunit(theunit, &angleunit);
freeunit(&angleunit);
if (!err)
err = unit2num(theunit);
}
if (err)
return err;
} else if (fun->type==ANGLEOUT || fun->type == DIMENSIONLESS) {
if ((err=unit2num(theunit)))
return err;
} else
return E_BADFUNCTYPE;
errno = 0;
theunit->factor = (*(fun->func))(theunit->factor);
if (errno)
return E_FUNC;
if (fun->type==ANGLEOUT) {
theunit->numerator[0] = dupstr("radian");
theunit->numerator[1] = 0;
}
return 0;
}
/* Line 268 of yacc.c */
#line 189 "parse.tab.c"
/* Enabling traces. */
#ifndef YYDEBUG
# define YYDEBUG 0
#endif
/* Enabling verbose error messages. */
#ifdef YYERROR_VERBOSE
# undef YYERROR_VERBOSE
# define YYERROR_VERBOSE 1
#else
# define YYERROR_VERBOSE 0
#endif
/* Enabling the token table. */
#ifndef YYTOKEN_TABLE
# define YYTOKEN_TABLE 0
#endif
/* Tokens. */
#ifndef YYTOKENTYPE
# define YYTOKENTYPE
/* Put the tokens into the symbol table, so that GDB and other debuggers
know about them. */
enum yytokentype {
REAL = 258,
UNIT = 259,
RFUNC = 260,
UFUNC = 261,
EXPONENT = 262,
MULTIPLY = 263,
MULTSTAR = 264,
DIVIDE = 265,
NUMDIV = 266,
SQRT = 267,
CUBEROOT = 268,
MULTMINUS = 269,
EOL = 270,
FUNCINV = 271,
MEMERROR = 272,
BADNUMBER = 273,
UNITEND = 274,
LASTUNSET = 275,
MINUS = 276,
ADD = 277,
UNARY = 278
};
#endif
#if ! defined YYSTYPE && ! defined YYSTYPE_IS_DECLARED
typedef union YYSTYPE
{
/* Line 293 of yacc.c */
#line 139 "parse.y"
double number;
int integer;
struct unittype *utype;
struct function *dfunc;
struct func *ufunc;
/* Line 293 of yacc.c */
#line 258 "parse.tab.c"
} YYSTYPE;
# define YYSTYPE_IS_TRIVIAL 1
# define yystype YYSTYPE /* obsolescent; will be withdrawn */
# define YYSTYPE_IS_DECLARED 1
#endif
/* Copy the second part of user declarations. */
/* Line 343 of yacc.c */
#line 270 "parse.tab.c"
#ifdef short
# undef short
#endif
#ifdef YYTYPE_UINT8
typedef YYTYPE_UINT8 yytype_uint8;
#else
typedef unsigned char yytype_uint8;
#endif
#ifdef YYTYPE_INT8
typedef YYTYPE_INT8 yytype_int8;
#elif (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
typedef signed char yytype_int8;
#else
typedef short int yytype_int8;
#endif
#ifdef YYTYPE_UINT16
typedef YYTYPE_UINT16 yytype_uint16;
#else
typedef unsigned short int yytype_uint16;
#endif
#ifdef YYTYPE_INT16
typedef YYTYPE_INT16 yytype_int16;
#else
typedef short int yytype_int16;
#endif
#ifndef YYSIZE_T
# ifdef __SIZE_TYPE__
# define YYSIZE_T __SIZE_TYPE__
# elif defined size_t
# define YYSIZE_T size_t
# elif ! defined YYSIZE_T && (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
# include /* INFRINGES ON USER NAME SPACE */
# define YYSIZE_T size_t
# else
# define YYSIZE_T unsigned int
# endif
#endif
#define YYSIZE_MAXIMUM ((YYSIZE_T) -1)
#ifndef YY_
# if defined YYENABLE_NLS && YYENABLE_NLS
# if ENABLE_NLS
# include /* INFRINGES ON USER NAME SPACE */
# define YY_(msgid) dgettext ("bison-runtime", msgid)
# endif
# endif
# ifndef YY_
# define YY_(msgid) msgid
# endif
#endif
/* Suppress unused-variable warnings by "using" E. */
#if ! defined lint || defined __GNUC__
# define YYUSE(e) ((void) (e))
#else
# define YYUSE(e) /* empty */
#endif
/* Identity function, used to suppress warnings about constant conditions. */
#ifndef lint
# define YYID(n) (n)
#else
#if (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
static int
YYID (int yyi)
#else
static int
YYID (yyi)
int yyi;
#endif
{
return yyi;
}
#endif
#if ! defined yyoverflow || YYERROR_VERBOSE
/* The parser invokes alloca or malloc; define the necessary symbols. */
# ifdef YYSTACK_USE_ALLOCA
# if YYSTACK_USE_ALLOCA
# ifdef __GNUC__
# define YYSTACK_ALLOC __builtin_alloca
# elif defined __BUILTIN_VA_ARG_INCR
# include /* INFRINGES ON USER NAME SPACE */
# elif defined _AIX
# define YYSTACK_ALLOC __alloca
# elif defined _MSC_VER
# include /* INFRINGES ON USER NAME SPACE */
# define alloca _alloca
# else
# define YYSTACK_ALLOC alloca
# if ! defined _ALLOCA_H && ! defined EXIT_SUCCESS && (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
# include /* INFRINGES ON USER NAME SPACE */
# ifndef EXIT_SUCCESS
# define EXIT_SUCCESS 0
# endif
# endif
# endif
# endif
# endif
# ifdef YYSTACK_ALLOC
/* Pacify GCC's `empty if-body' warning. */
# define YYSTACK_FREE(Ptr) do { /* empty */; } while (YYID (0))
# ifndef YYSTACK_ALLOC_MAXIMUM
/* The OS might guarantee only one guard page at the bottom of the stack,
and a page size can be as small as 4096 bytes. So we cannot safely
invoke alloca (N) if N exceeds 4096. Use a slightly smaller number
to allow for a few compiler-allocated temporary stack slots. */
# define YYSTACK_ALLOC_MAXIMUM 4032 /* reasonable circa 2006 */
# endif
# else
# define YYSTACK_ALLOC YYMALLOC
# define YYSTACK_FREE YYFREE
# ifndef YYSTACK_ALLOC_MAXIMUM
# define YYSTACK_ALLOC_MAXIMUM YYSIZE_MAXIMUM
# endif
# if (defined __cplusplus && ! defined EXIT_SUCCESS \
&& ! ((defined YYMALLOC || defined malloc) \
&& (defined YYFREE || defined free)))
# include /* INFRINGES ON USER NAME SPACE */
# ifndef EXIT_SUCCESS
# define EXIT_SUCCESS 0
# endif
# endif
# ifndef YYMALLOC
# define YYMALLOC malloc
# if ! defined malloc && ! defined EXIT_SUCCESS && (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
void *malloc (YYSIZE_T); /* INFRINGES ON USER NAME SPACE */
# endif
# endif
# ifndef YYFREE
# define YYFREE free
# if ! defined free && ! defined EXIT_SUCCESS && (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
void free (void *); /* INFRINGES ON USER NAME SPACE */
# endif
# endif
# endif
#endif /* ! defined yyoverflow || YYERROR_VERBOSE */
#if (! defined yyoverflow \
&& (! defined __cplusplus \
|| (defined YYSTYPE_IS_TRIVIAL && YYSTYPE_IS_TRIVIAL)))
/* A type that is properly aligned for any stack member. */
union yyalloc
{
yytype_int16 yyss_alloc;
YYSTYPE yyvs_alloc;
};
/* The size of the maximum gap between one aligned stack and the next. */
# define YYSTACK_GAP_MAXIMUM (sizeof (union yyalloc) - 1)
/* The size of an array large to enough to hold all stacks, each with
N elements. */
# define YYSTACK_BYTES(N) \
((N) * (sizeof (yytype_int16) + sizeof (YYSTYPE)) \
+ YYSTACK_GAP_MAXIMUM)
# define YYCOPY_NEEDED 1
/* Relocate STACK from its old location to the new one. The
local variables YYSIZE and YYSTACKSIZE give the old and new number of
elements in the stack, and YYPTR gives the new location of the
stack. Advance YYPTR to a properly aligned location for the next
stack. */
# define YYSTACK_RELOCATE(Stack_alloc, Stack) \
do \
{ \
YYSIZE_T yynewbytes; \
YYCOPY (&yyptr->Stack_alloc, Stack, yysize); \
Stack = &yyptr->Stack_alloc; \
yynewbytes = yystacksize * sizeof (*Stack) + YYSTACK_GAP_MAXIMUM; \
yyptr += yynewbytes / sizeof (*yyptr); \
} \
while (YYID (0))
#endif
#if defined YYCOPY_NEEDED && YYCOPY_NEEDED
/* Copy COUNT objects from FROM to TO. The source and destination do
not overlap. */
# ifndef YYCOPY
# if defined __GNUC__ && 1 < __GNUC__
# define YYCOPY(To, From, Count) \
__builtin_memcpy (To, From, (Count) * sizeof (*(From)))
# else
# define YYCOPY(To, From, Count) \
do \
{ \
YYSIZE_T yyi; \
for (yyi = 0; yyi < (Count); yyi++) \
(To)[yyi] = (From)[yyi]; \
} \
while (YYID (0))
# endif
# endif
#endif /* !YYCOPY_NEEDED */
/* YYFINAL -- State number of the termination state. */
#define YYFINAL 34
/* YYLAST -- Last index in YYTABLE. */
#define YYLAST 179
/* YYNTOKENS -- Number of terminals. */
#define YYNTOKENS 26
/* YYNNTS -- Number of nonterminals. */
#define YYNNTS 7
/* YYNRULES -- Number of rules. */
#define YYNRULES 35
/* YYNRULES -- Number of states. */
#define YYNSTATES 59
/* YYTRANSLATE(YYLEX) -- Bison symbol number corresponding to YYLEX. */
#define YYUNDEFTOK 2
#define YYMAXUTOK 278
#define YYTRANSLATE(YYX) \
((unsigned int) (YYX) <= YYMAXUTOK ? yytranslate[YYX] : YYUNDEFTOK)
/* YYTRANSLATE[YYLEX] -- Bison symbol number corresponding to YYLEX. */
static const yytype_uint8 yytranslate[] =
{
0, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
24, 25, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 1, 2, 3, 4,
5, 6, 7, 8, 9, 10, 11, 12, 13, 14,
15, 16, 17, 18, 19, 20, 21, 22, 23
};
#if YYDEBUG
/* YYPRHS[YYN] -- Index of the first RHS symbol of rule number YYN in
YYRHS. */
static const yytype_uint8 yyprhs[] =
{
0, 0, 3, 5, 8, 10, 12, 15, 17, 20,
23, 27, 31, 35, 39, 43, 45, 49, 53, 55,
57, 61, 65, 68, 70, 73, 76, 79, 82, 86,
91, 96, 98, 100, 102, 104
};
/* YYRHS -- A `-1'-separated list of the rules' RHS. */
static const yytype_int8 yyrhs[] =
{
27, 0, -1, 15, -1, 28, 15, -1, 1, -1,
29, -1, 10, 32, -1, 32, -1, 14, 32, -1,
21, 32, -1, 29, 22, 29, -1, 29, 21, 29,
-1, 29, 10, 29, -1, 29, 8, 29, -1, 29,
9, 29, -1, 3, -1, 30, 11, 30, -1, 24,
29, 25, -1, 30, -1, 4, -1, 32, 7, 32,
-1, 32, 14, 32, -1, 32, 32, -1, 31, -1,
12, 31, -1, 13, 31, -1, 5, 31, -1, 6,
31, -1, 16, 6, 31, -1, 32, 7, 14, 32,
-1, 32, 7, 21, 32, -1, 18, -1, 17, -1,
19, -1, 20, -1, 16, 4, -1
};
/* YYRLINE[YYN] -- source line where rule number YYN was defined. */
static const yytype_uint8 yyrline[] =
{
0, 185, 185, 186, 187, 190, 191, 194, 195, 196,
197, 198, 200, 201, 202, 205, 206, 209, 215, 216,
217, 218, 219, 220, 221, 222, 223, 224, 225, 226,
229, 232, 233, 234, 235, 236
};
#endif
#if YYDEBUG || YYERROR_VERBOSE || YYTOKEN_TABLE
/* YYTNAME[SYMBOL-NUM] -- String name of the symbol SYMBOL-NUM.
First, the terminals, then, starting at YYNTOKENS, nonterminals. */
static const char *const yytname[] =
{
"$end", "error", "$undefined", "REAL", "UNIT", "RFUNC", "UFUNC",
"EXPONENT", "MULTIPLY", "MULTSTAR", "DIVIDE", "NUMDIV", "SQRT",
"CUBEROOT", "MULTMINUS", "EOL", "FUNCINV", "MEMERROR", "BADNUMBER",
"UNITEND", "LASTUNSET", "MINUS", "ADD", "UNARY", "'('", "')'", "$accept",
"input", "unitexpr", "expr", "numexpr", "pexpr", "list", 0
};
#endif
# ifdef YYPRINT
/* YYTOKNUM[YYLEX-NUM] -- Internal token number corresponding to
token YYLEX-NUM. */
static const yytype_uint16 yytoknum[] =
{
0, 256, 257, 258, 259, 260, 261, 262, 263, 264,
265, 266, 267, 268, 269, 270, 271, 272, 273, 274,
275, 276, 277, 278, 40, 41
};
# endif
/* YYR1[YYN] -- Symbol number of symbol that rule YYN derives. */
static const yytype_uint8 yyr1[] =
{
0, 26, 27, 27, 27, 28, 28, 29, 29, 29,
29, 29, 29, 29, 29, 30, 30, 31, 32, 32,
32, 32, 32, 32, 32, 32, 32, 32, 32, 32,
32, 32, 32, 32, 32, 32
};
/* YYR2[YYN] -- Number of symbols composing right hand side of rule YYN. */
static const yytype_uint8 yyr2[] =
{
0, 2, 1, 2, 1, 1, 2, 1, 2, 2,
3, 3, 3, 3, 3, 1, 3, 3, 1, 1,
3, 3, 2, 1, 2, 2, 2, 2, 3, 4,
4, 1, 1, 1, 1, 2
};
/* YYDEFACT[STATE-NAME] -- Default reduction number in state STATE-NUM.
Performed when YYTABLE doesn't specify something else to do. Zero
means the default is an error. */
static const yytype_uint8 yydefact[] =
{
0, 4, 15, 19, 0, 0, 0, 0, 0, 0,
2, 0, 32, 31, 33, 34, 0, 0, 0, 0,
5, 18, 23, 7, 26, 27, 6, 24, 25, 8,
35, 0, 9, 0, 1, 3, 0, 0, 0, 0,
0, 0, 0, 0, 22, 28, 17, 13, 14, 12,
11, 10, 16, 0, 0, 20, 21, 29, 30
};
/* YYDEFGOTO[NTERM-NUM]. */
static const yytype_int8 yydefgoto[] =
{
-1, 18, 19, 20, 21, 22, 44
};
/* YYPACT[STATE-NUM] -- Index in YYTABLE of the portion describing
STATE-NUM. */
#define YYPACT_NINF -18
static const yytype_int16 yypact[] =
{
45, -18, -18, -18, -17, -17, 155, -17, -17, 155,
-18, 9, -18, -18, -18, -18, 155, 67, 8, -1,
68, 16, -18, 89, -18, -18, 89, -18, -18, 89,
-18, -17, 89, 10, -18, -18, 67, 67, 67, 67,
67, 18, 111, 155, 133, -18, -18, -18, 21, 21,
2, 2, -18, 155, 155, 23, 133, 23, 23
};
/* YYPGOTO[NTERM-NUM]. */
static const yytype_int8 yypgoto[] =
{
-18, -18, -18, -14, -8, -3, 0
};
/* YYTABLE[YYPACT[STATE-NUM]]. What to do in state STATE-NUM. If
positive, shift that token. If negative, reduce the rule which
number is the opposite. If YYTABLE_NINF, syntax error. */
#define YYTABLE_NINF -1
static const yytype_uint8 yytable[] =
{
23, 24, 25, 33, 27, 28, 26, 17, 34, 29,
36, 37, 38, 30, 35, 31, 32, 23, 36, 37,
38, 2, 47, 48, 49, 50, 51, 41, 45, 36,
42, 39, 40, 52, 0, 46, 23, 23, 23, 23,
23, 0, 55, 56, 0, 0, 1, 0, 2, 3,
4, 5, 0, 57, 58, 6, 0, 7, 8, 9,
10, 11, 12, 13, 14, 15, 16, 0, 0, 17,
2, 3, 4, 5, 0, 0, 36, 37, 38, 7,
8, 9, 0, 11, 12, 13, 14, 15, 16, 39,
40, 17, 2, 3, 4, 5, 42, 0, 0, 0,
0, 7, 8, 43, 0, 11, 12, 13, 14, 15,
0, 0, 0, 17, 2, 3, 4, 5, 0, 0,
0, 0, 0, 7, 8, 53, 0, 11, 12, 13,
14, 15, 54, 0, 0, 17, 2, 3, 4, 5,
42, 0, 0, 0, 0, 7, 8, 0, 0, 11,
12, 13, 14, 15, 0, 0, 0, 17, 2, 3,
4, 5, 0, 0, 0, 0, 0, 7, 8, 0,
0, 11, 12, 13, 14, 15, 0, 0, 0, 17
};
#define yypact_value_is_default(yystate) \
((yystate) == (-18))
#define yytable_value_is_error(yytable_value) \
YYID (0)
static const yytype_int8 yycheck[] =
{
0, 4, 5, 17, 7, 8, 6, 24, 0, 9,
8, 9, 10, 4, 15, 6, 16, 17, 8, 9,
10, 3, 36, 37, 38, 39, 40, 11, 31, 8,
7, 21, 22, 41, -1, 25, 36, 37, 38, 39,
40, -1, 42, 43, -1, -1, 1, -1, 3, 4,
5, 6, -1, 53, 54, 10, -1, 12, 13, 14,
15, 16, 17, 18, 19, 20, 21, -1, -1, 24,
3, 4, 5, 6, -1, -1, 8, 9, 10, 12,
13, 14, -1, 16, 17, 18, 19, 20, 21, 21,
22, 24, 3, 4, 5, 6, 7, -1, -1, -1,
-1, 12, 13, 14, -1, 16, 17, 18, 19, 20,
-1, -1, -1, 24, 3, 4, 5, 6, -1, -1,
-1, -1, -1, 12, 13, 14, -1, 16, 17, 18,
19, 20, 21, -1, -1, 24, 3, 4, 5, 6,
7, -1, -1, -1, -1, 12, 13, -1, -1, 16,
17, 18, 19, 20, -1, -1, -1, 24, 3, 4,
5, 6, -1, -1, -1, -1, -1, 12, 13, -1,
-1, 16, 17, 18, 19, 20, -1, -1, -1, 24
};
/* YYSTOS[STATE-NUM] -- The (internal number of the) accessing
symbol of state STATE-NUM. */
static const yytype_uint8 yystos[] =
{
0, 1, 3, 4, 5, 6, 10, 12, 13, 14,
15, 16, 17, 18, 19, 20, 21, 24, 27, 28,
29, 30, 31, 32, 31, 31, 32, 31, 31, 32,
4, 6, 32, 29, 0, 15, 8, 9, 10, 21,
22, 11, 7, 14, 32, 31, 25, 29, 29, 29,
29, 29, 30, 14, 21, 32, 32, 32, 32
};
#define yyerrok (yyerrstatus = 0)
#define yyclearin (yychar = YYEMPTY)
#define YYEMPTY (-2)
#define YYEOF 0
#define YYACCEPT goto yyacceptlab
#define YYABORT goto yyabortlab
#define YYERROR goto yyerrorlab
/* Like YYERROR except do call yyerror. This remains here temporarily
to ease the transition to the new meaning of YYERROR, for GCC.
Once GCC version 2 has supplanted version 1, this can go. However,
YYFAIL appears to be in use. Nevertheless, it is formally deprecated
in Bison 2.4.2's NEWS entry, where a plan to phase it out is
discussed. */
#define YYFAIL goto yyerrlab
#if defined YYFAIL
/* This is here to suppress warnings from the GCC cpp's
-Wunused-macros. Normally we don't worry about that warning, but
some users do, and we want to make it easy for users to remove
YYFAIL uses, which will produce warnings from Bison 2.5. */
#endif
#define YYRECOVERING() (!!yyerrstatus)
#define YYBACKUP(Token, Value) \
do \
if (yychar == YYEMPTY && yylen == 1) \
{ \
yychar = (Token); \
yylval = (Value); \
YYPOPSTACK (1); \
goto yybackup; \
} \
else \
{ \
yyerror (comm, YY_("syntax error: cannot back up")); \
YYERROR; \
} \
while (YYID (0))
#define YYTERROR 1
#define YYERRCODE 256
/* YYLLOC_DEFAULT -- Set CURRENT to span from RHS[1] to RHS[N].
If N is 0, then set CURRENT to the empty location which ends
the previous symbol: RHS[0] (always defined). */
#define YYRHSLOC(Rhs, K) ((Rhs)[K])
#ifndef YYLLOC_DEFAULT
# define YYLLOC_DEFAULT(Current, Rhs, N) \
do \
if (YYID (N)) \
{ \
(Current).first_line = YYRHSLOC (Rhs, 1).first_line; \
(Current).first_column = YYRHSLOC (Rhs, 1).first_column; \
(Current).last_line = YYRHSLOC (Rhs, N).last_line; \
(Current).last_column = YYRHSLOC (Rhs, N).last_column; \
} \
else \
{ \
(Current).first_line = (Current).last_line = \
YYRHSLOC (Rhs, 0).last_line; \
(Current).first_column = (Current).last_column = \
YYRHSLOC (Rhs, 0).last_column; \
} \
while (YYID (0))
#endif
/* This macro is provided for backward compatibility. */
#ifndef YY_LOCATION_PRINT
# define YY_LOCATION_PRINT(File, Loc) ((void) 0)
#endif
/* YYLEX -- calling `yylex' with the right arguments. */
#ifdef YYLEX_PARAM
# define YYLEX yylex (&yylval, YYLEX_PARAM)
#else
# define YYLEX yylex (&yylval, comm)
#endif
/* Enable debugging if requested. */
#if YYDEBUG
# ifndef YYFPRINTF
# include /* INFRINGES ON USER NAME SPACE */
# define YYFPRINTF fprintf
# endif
# define YYDPRINTF(Args) \
do { \
if (yydebug) \
YYFPRINTF Args; \
} while (YYID (0))
# define YY_SYMBOL_PRINT(Title, Type, Value, Location) \
do { \
if (yydebug) \
{ \
YYFPRINTF (stderr, "%s ", Title); \
yy_symbol_print (stderr, \
Type, Value, comm); \
YYFPRINTF (stderr, "\n"); \
} \
} while (YYID (0))
/*--------------------------------.
| Print this symbol on YYOUTPUT. |
`--------------------------------*/
/*ARGSUSED*/
#if (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
static void
yy_symbol_value_print (FILE *yyoutput, int yytype, YYSTYPE const * const yyvaluep, struct commtype *comm)
#else
static void
yy_symbol_value_print (yyoutput, yytype, yyvaluep, comm)
FILE *yyoutput;
int yytype;
YYSTYPE const * const yyvaluep;
struct commtype *comm;
#endif
{
if (!yyvaluep)
return;
YYUSE (comm);
# ifdef YYPRINT
if (yytype < YYNTOKENS)
YYPRINT (yyoutput, yytoknum[yytype], *yyvaluep);
# else
YYUSE (yyoutput);
# endif
switch (yytype)
{
default:
break;
}
}
/*--------------------------------.
| Print this symbol on YYOUTPUT. |
`--------------------------------*/
#if (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
static void
yy_symbol_print (FILE *yyoutput, int yytype, YYSTYPE const * const yyvaluep, struct commtype *comm)
#else
static void
yy_symbol_print (yyoutput, yytype, yyvaluep, comm)
FILE *yyoutput;
int yytype;
YYSTYPE const * const yyvaluep;
struct commtype *comm;
#endif
{
if (yytype < YYNTOKENS)
YYFPRINTF (yyoutput, "token %s (", yytname[yytype]);
else
YYFPRINTF (yyoutput, "nterm %s (", yytname[yytype]);
yy_symbol_value_print (yyoutput, yytype, yyvaluep, comm);
YYFPRINTF (yyoutput, ")");
}
/*------------------------------------------------------------------.
| yy_stack_print -- Print the state stack from its BOTTOM up to its |
| TOP (included). |
`------------------------------------------------------------------*/
#if (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
static void
yy_stack_print (yytype_int16 *yybottom, yytype_int16 *yytop)
#else
static void
yy_stack_print (yybottom, yytop)
yytype_int16 *yybottom;
yytype_int16 *yytop;
#endif
{
YYFPRINTF (stderr, "Stack now");
for (; yybottom <= yytop; yybottom++)
{
int yybot = *yybottom;
YYFPRINTF (stderr, " %d", yybot);
}
YYFPRINTF (stderr, "\n");
}
# define YY_STACK_PRINT(Bottom, Top) \
do { \
if (yydebug) \
yy_stack_print ((Bottom), (Top)); \
} while (YYID (0))
/*------------------------------------------------.
| Report that the YYRULE is going to be reduced. |
`------------------------------------------------*/
#if (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
static void
yy_reduce_print (YYSTYPE *yyvsp, int yyrule, struct commtype *comm)
#else
static void
yy_reduce_print (yyvsp, yyrule, comm)
YYSTYPE *yyvsp;
int yyrule;
struct commtype *comm;
#endif
{
int yynrhs = yyr2[yyrule];
int yyi;
unsigned long int yylno = yyrline[yyrule];
YYFPRINTF (stderr, "Reducing stack by rule %d (line %lu):\n",
yyrule - 1, yylno);
/* The symbols being reduced. */
for (yyi = 0; yyi < yynrhs; yyi++)
{
YYFPRINTF (stderr, " $%d = ", yyi + 1);
yy_symbol_print (stderr, yyrhs[yyprhs[yyrule] + yyi],
&(yyvsp[(yyi + 1) - (yynrhs)])
, comm);
YYFPRINTF (stderr, "\n");
}
}
# define YY_REDUCE_PRINT(Rule) \
do { \
if (yydebug) \
yy_reduce_print (yyvsp, Rule, comm); \
} while (YYID (0))
/* Nonzero means print parse trace. It is left uninitialized so that
multiple parsers can coexist. */
int yydebug;
#else /* !YYDEBUG */
# define YYDPRINTF(Args)
# define YY_SYMBOL_PRINT(Title, Type, Value, Location)
# define YY_STACK_PRINT(Bottom, Top)
# define YY_REDUCE_PRINT(Rule)
#endif /* !YYDEBUG */
/* YYINITDEPTH -- initial size of the parser's stacks. */
#ifndef YYINITDEPTH
# define YYINITDEPTH 200
#endif
/* YYMAXDEPTH -- maximum size the stacks can grow to (effective only
if the built-in stack extension method is used).
Do not make this value too large; the results are undefined if
YYSTACK_ALLOC_MAXIMUM < YYSTACK_BYTES (YYMAXDEPTH)
evaluated with infinite-precision integer arithmetic. */
#ifndef YYMAXDEPTH
# define YYMAXDEPTH 10000
#endif
#if YYERROR_VERBOSE
# ifndef yystrlen
# if defined __GLIBC__ && defined _STRING_H
# define yystrlen strlen
# else
/* Return the length of YYSTR. */
#if (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
static YYSIZE_T
yystrlen (const char *yystr)
#else
static YYSIZE_T
yystrlen (yystr)
const char *yystr;
#endif
{
YYSIZE_T yylen;
for (yylen = 0; yystr[yylen]; yylen++)
continue;
return yylen;
}
# endif
# endif
# ifndef yystpcpy
# if defined __GLIBC__ && defined _STRING_H && defined _GNU_SOURCE
# define yystpcpy stpcpy
# else
/* Copy YYSRC to YYDEST, returning the address of the terminating '\0' in
YYDEST. */
#if (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
static char *
yystpcpy (char *yydest, const char *yysrc)
#else
static char *
yystpcpy (yydest, yysrc)
char *yydest;
const char *yysrc;
#endif
{
char *yyd = yydest;
const char *yys = yysrc;
while ((*yyd++ = *yys++) != '\0')
continue;
return yyd - 1;
}
# endif
# endif
# ifndef yytnamerr
/* Copy to YYRES the contents of YYSTR after stripping away unnecessary
quotes and backslashes, so that it's suitable for yyerror. The
heuristic is that double-quoting is unnecessary unless the string
contains an apostrophe, a comma, or backslash (other than
backslash-backslash). YYSTR is taken from yytname. If YYRES is
null, do not copy; instead, return the length of what the result
would have been. */
static YYSIZE_T
yytnamerr (char *yyres, const char *yystr)
{
if (*yystr == '"')
{
YYSIZE_T yyn = 0;
char const *yyp = yystr;
for (;;)
switch (*++yyp)
{
case '\'':
case ',':
goto do_not_strip_quotes;
case '\\':
if (*++yyp != '\\')
goto do_not_strip_quotes;
/* Fall through. */
default:
if (yyres)
yyres[yyn] = *yyp;
yyn++;
break;
case '"':
if (yyres)
yyres[yyn] = '\0';
return yyn;
}
do_not_strip_quotes: ;
}
if (! yyres)
return yystrlen (yystr);
return yystpcpy (yyres, yystr) - yyres;
}
# endif
/* Copy into *YYMSG, which is of size *YYMSG_ALLOC, an error message
about the unexpected token YYTOKEN for the state stack whose top is
YYSSP.
Return 0 if *YYMSG was successfully written. Return 1 if *YYMSG is
not large enough to hold the message. In that case, also set
*YYMSG_ALLOC to the required number of bytes. Return 2 if the
required number of bytes is too large to store. */
static int
yysyntax_error (YYSIZE_T *yymsg_alloc, char **yymsg,
yytype_int16 *yyssp, int yytoken)
{
YYSIZE_T yysize0 = yytnamerr (0, yytname[yytoken]);
YYSIZE_T yysize = yysize0;
YYSIZE_T yysize1;
enum { YYERROR_VERBOSE_ARGS_MAXIMUM = 5 };
/* Internationalized format string. */
const char *yyformat = 0;
/* Arguments of yyformat. */
char const *yyarg[YYERROR_VERBOSE_ARGS_MAXIMUM];
/* Number of reported tokens (one for the "unexpected", one per
"expected"). */
int yycount = 0;
/* There are many possibilities here to consider:
- Assume YYFAIL is not used. It's too flawed to consider. See
for details. YYERROR is fine as it does not invoke this
function.
- If this state is a consistent state with a default action, then
the only way this function was invoked is if the default action
is an error action. In that case, don't check for expected
tokens because there are none.
- The only way there can be no lookahead present (in yychar) is if
this state is a consistent state with a default action. Thus,
detecting the absence of a lookahead is sufficient to determine
that there is no unexpected or expected token to report. In that
case, just report a simple "syntax error".
- Don't assume there isn't a lookahead just because this state is a
consistent state with a default action. There might have been a
previous inconsistent state, consistent state with a non-default
action, or user semantic action that manipulated yychar.
- Of course, the expected token list depends on states to have
correct lookahead information, and it depends on the parser not
to perform extra reductions after fetching a lookahead from the
scanner and before detecting a syntax error. Thus, state merging
(from LALR or IELR) and default reductions corrupt the expected
token list. However, the list is correct for canonical LR with
one exception: it will still contain any token that will not be
accepted due to an error action in a later state.
*/
if (yytoken != YYEMPTY)
{
int yyn = yypact[*yyssp];
yyarg[yycount++] = yytname[yytoken];
if (!yypact_value_is_default (yyn))
{
/* Start YYX at -YYN if negative to avoid negative indexes in
YYCHECK. In other words, skip the first -YYN actions for
this state because they are default actions. */
int yyxbegin = yyn < 0 ? -yyn : 0;
/* Stay within bounds of both yycheck and yytname. */
int yychecklim = YYLAST - yyn + 1;
int yyxend = yychecklim < YYNTOKENS ? yychecklim : YYNTOKENS;
int yyx;
for (yyx = yyxbegin; yyx < yyxend; ++yyx)
if (yycheck[yyx + yyn] == yyx && yyx != YYTERROR
&& !yytable_value_is_error (yytable[yyx + yyn]))
{
if (yycount == YYERROR_VERBOSE_ARGS_MAXIMUM)
{
yycount = 1;
yysize = yysize0;
break;
}
yyarg[yycount++] = yytname[yyx];
yysize1 = yysize + yytnamerr (0, yytname[yyx]);
if (! (yysize <= yysize1
&& yysize1 <= YYSTACK_ALLOC_MAXIMUM))
return 2;
yysize = yysize1;
}
}
}
switch (yycount)
{
# define YYCASE_(N, S) \
case N: \
yyformat = S; \
break
YYCASE_(0, YY_("syntax error"));
YYCASE_(1, YY_("syntax error, unexpected %s"));
YYCASE_(2, YY_("syntax error, unexpected %s, expecting %s"));
YYCASE_(3, YY_("syntax error, unexpected %s, expecting %s or %s"));
YYCASE_(4, YY_("syntax error, unexpected %s, expecting %s or %s or %s"));
YYCASE_(5, YY_("syntax error, unexpected %s, expecting %s or %s or %s or %s"));
# undef YYCASE_
}
yysize1 = yysize + yystrlen (yyformat);
if (! (yysize <= yysize1 && yysize1 <= YYSTACK_ALLOC_MAXIMUM))
return 2;
yysize = yysize1;
if (*yymsg_alloc < yysize)
{
*yymsg_alloc = 2 * yysize;
if (! (yysize <= *yymsg_alloc
&& *yymsg_alloc <= YYSTACK_ALLOC_MAXIMUM))
*yymsg_alloc = YYSTACK_ALLOC_MAXIMUM;
return 1;
}
/* Avoid sprintf, as that infringes on the user's name space.
Don't have undefined behavior even if the translation
produced a string with the wrong number of "%s"s. */
{
char *yyp = *yymsg;
int yyi = 0;
while ((*yyp = *yyformat) != '\0')
if (*yyp == '%' && yyformat[1] == 's' && yyi < yycount)
{
yyp += yytnamerr (yyp, yyarg[yyi++]);
yyformat += 2;
}
else
{
yyp++;
yyformat++;
}
}
return 0;
}
#endif /* YYERROR_VERBOSE */
/*-----------------------------------------------.
| Release the memory associated to this symbol. |
`-----------------------------------------------*/
/*ARGSUSED*/
#if (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
static void
yydestruct (const char *yymsg, int yytype, YYSTYPE *yyvaluep, struct commtype *comm)
#else
static void
yydestruct (yymsg, yytype, yyvaluep, comm)
const char *yymsg;
int yytype;
YYSTYPE *yyvaluep;
struct commtype *comm;
#endif
{
YYUSE (yyvaluep);
YYUSE (comm);
if (!yymsg)
yymsg = "Deleting";
YY_SYMBOL_PRINT (yymsg, yytype, yyvaluep, yylocationp);
switch (yytype)
{
default:
break;
}
}
/* Prevent warnings from -Wmissing-prototypes. */
#ifdef YYPARSE_PARAM
#if defined __STDC__ || defined __cplusplus
int yyparse (void *YYPARSE_PARAM);
#else
int yyparse ();
#endif
#else /* ! YYPARSE_PARAM */
#if defined __STDC__ || defined __cplusplus
int yyparse (struct commtype *comm);
#else
int yyparse ();
#endif
#endif /* ! YYPARSE_PARAM */
/*----------.
| yyparse. |
`----------*/
#ifdef YYPARSE_PARAM
#if (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
int
yyparse (void *YYPARSE_PARAM)
#else
int
yyparse (YYPARSE_PARAM)
void *YYPARSE_PARAM;
#endif
#else /* ! YYPARSE_PARAM */
#if (defined __STDC__ || defined __C99__FUNC__ \
|| defined __cplusplus || defined _MSC_VER)
int
yyparse (struct commtype *comm)
#else
int
yyparse (comm)
struct commtype *comm;
#endif
#endif
{
/* The lookahead symbol. */
int yychar;
/* The semantic value of the lookahead symbol. */
YYSTYPE yylval;
/* Number of syntax errors so far. */
int yynerrs;
int yystate;
/* Number of tokens to shift before error messages enabled. */
int yyerrstatus;
/* The stacks and their tools:
`yyss': related to states.
`yyvs': related to semantic values.
Refer to the stacks thru separate pointers, to allow yyoverflow
to reallocate them elsewhere. */
/* The state stack. */
yytype_int16 yyssa[YYINITDEPTH];
yytype_int16 *yyss;
yytype_int16 *yyssp;
/* The semantic value stack. */
YYSTYPE yyvsa[YYINITDEPTH];
YYSTYPE *yyvs;
YYSTYPE *yyvsp;
YYSIZE_T yystacksize;
int yyn;
int yyresult;
/* Lookahead token as an internal (translated) token number. */
int yytoken;
/* The variables used to return semantic value and location from the
action routines. */
YYSTYPE yyval;
#if YYERROR_VERBOSE
/* Buffer for error messages, and its allocated size. */
char yymsgbuf[128];
char *yymsg = yymsgbuf;
YYSIZE_T yymsg_alloc = sizeof yymsgbuf;
#endif
#define YYPOPSTACK(N) (yyvsp -= (N), yyssp -= (N))
/* The number of symbols on the RHS of the reduced rule.
Keep to zero when no symbol should be popped. */
int yylen = 0;
yytoken = 0;
yyss = yyssa;
yyvs = yyvsa;
yystacksize = YYINITDEPTH;
YYDPRINTF ((stderr, "Starting parse\n"));
yystate = 0;
yyerrstatus = 0;
yynerrs = 0;
yychar = YYEMPTY; /* Cause a token to be read. */
/* Initialize stack pointers.
Waste one element of value and location stack
so that they stay on the same level as the state stack.
The wasted elements are never initialized. */
yyssp = yyss;
yyvsp = yyvs;
goto yysetstate;
/*------------------------------------------------------------.
| yynewstate -- Push a new state, which is found in yystate. |
`------------------------------------------------------------*/
yynewstate:
/* In all cases, when you get here, the value and location stacks
have just been pushed. So pushing a state here evens the stacks. */
yyssp++;
yysetstate:
*yyssp = yystate;
if (yyss + yystacksize - 1 <= yyssp)
{
/* Get the current used size of the three stacks, in elements. */
YYSIZE_T yysize = yyssp - yyss + 1;
#ifdef yyoverflow
{
/* Give user a chance to reallocate the stack. Use copies of
these so that the &'s don't force the real ones into
memory. */
YYSTYPE *yyvs1 = yyvs;
yytype_int16 *yyss1 = yyss;
/* Each stack pointer address is followed by the size of the
data in use in that stack, in bytes. This used to be a
conditional around just the two extra args, but that might
be undefined if yyoverflow is a macro. */
yyoverflow (YY_("memory exhausted"),
&yyss1, yysize * sizeof (*yyssp),
&yyvs1, yysize * sizeof (*yyvsp),
&yystacksize);
yyss = yyss1;
yyvs = yyvs1;
}
#else /* no yyoverflow */
# ifndef YYSTACK_RELOCATE
goto yyexhaustedlab;
# else
/* Extend the stack our own way. */
if (YYMAXDEPTH <= yystacksize)
goto yyexhaustedlab;
yystacksize *= 2;
if (YYMAXDEPTH < yystacksize)
yystacksize = YYMAXDEPTH;
{
yytype_int16 *yyss1 = yyss;
union yyalloc *yyptr =
(union yyalloc *) YYSTACK_ALLOC (YYSTACK_BYTES (yystacksize));
if (! yyptr)
goto yyexhaustedlab;
YYSTACK_RELOCATE (yyss_alloc, yyss);
YYSTACK_RELOCATE (yyvs_alloc, yyvs);
# undef YYSTACK_RELOCATE
if (yyss1 != yyssa)
YYSTACK_FREE (yyss1);
}
# endif
#endif /* no yyoverflow */
yyssp = yyss + yysize - 1;
yyvsp = yyvs + yysize - 1;
YYDPRINTF ((stderr, "Stack size increased to %lu\n",
(unsigned long int) yystacksize));
if (yyss + yystacksize - 1 <= yyssp)
YYABORT;
}
YYDPRINTF ((stderr, "Entering state %d\n", yystate));
if (yystate == YYFINAL)
YYACCEPT;
goto yybackup;
/*-----------.
| yybackup. |
`-----------*/
yybackup:
/* Do appropriate processing given the current state. Read a
lookahead token if we need one and don't already have one. */
/* First try to decide what to do without reference to lookahead token. */
yyn = yypact[yystate];
if (yypact_value_is_default (yyn))
goto yydefault;
/* Not known => get a lookahead token if don't already have one. */
/* YYCHAR is either YYEMPTY or YYEOF or a valid lookahead symbol. */
if (yychar == YYEMPTY)
{
YYDPRINTF ((stderr, "Reading a token: "));
yychar = YYLEX;
}
if (yychar <= YYEOF)
{
yychar = yytoken = YYEOF;
YYDPRINTF ((stderr, "Now at end of input.\n"));
}
else
{
yytoken = YYTRANSLATE (yychar);
YY_SYMBOL_PRINT ("Next token is", yytoken, &yylval, &yylloc);
}
/* If the proper action on seeing token YYTOKEN is to reduce or to
detect an error, take that action. */
yyn += yytoken;
if (yyn < 0 || YYLAST < yyn || yycheck[yyn] != yytoken)
goto yydefault;
yyn = yytable[yyn];
if (yyn <= 0)
{
if (yytable_value_is_error (yyn))
goto yyerrlab;
yyn = -yyn;
goto yyreduce;
}
/* Count tokens shifted since error; after three, turn off error
status. */
if (yyerrstatus)
yyerrstatus--;
/* Shift the lookahead token. */
YY_SYMBOL_PRINT ("Shifting", yytoken, &yylval, &yylloc);
/* Discard the shifted token. */
yychar = YYEMPTY;
yystate = yyn;
*++yyvsp = yylval;
goto yynewstate;
/*-----------------------------------------------------------.
| yydefault -- do the default action for the current state. |
`-----------------------------------------------------------*/
yydefault:
yyn = yydefact[yystate];
if (yyn == 0)
goto yyerrlab;
goto yyreduce;
/*-----------------------------.
| yyreduce -- Do a reduction. |
`-----------------------------*/
yyreduce:
/* yyn is the number of a rule to reduce with. */
yylen = yyr2[yyn];
/* If YYLEN is nonzero, implement the default value of the action:
`$$ = $1'.
Otherwise, the following line sets YYVAL to garbage.
This behavior is undocumented and Bison
users should not rely upon it. Assigning to YYVAL
unconditionally makes the parser a bit smaller, and it avoids a
GCC warning that YYVAL may be used uninitialized. */
yyval = yyvsp[1-yylen];
YY_REDUCE_PRINT (yyn);
switch (yyn)
{
case 2:
/* Line 1806 of yacc.c */
#line 185 "parse.y"
{ comm->result = makenumunit(1,&err); CHECK; YYACCEPT; }
break;
case 3:
/* Line 1806 of yacc.c */
#line 186 "parse.y"
{ comm->result = (yyvsp[(1) - (2)].utype); YYACCEPT; }
break;
case 4:
/* Line 1806 of yacc.c */
#line 187 "parse.y"
{ YYABORT; }
break;
case 5:
/* Line 1806 of yacc.c */
#line 190 "parse.y"
{(yyval.utype) = (yyvsp[(1) - (1)].utype);}
break;
case 6:
/* Line 1806 of yacc.c */
#line 191 "parse.y"
{ invertunit((yyvsp[(2) - (2)].utype)); (yyval.utype)=(yyvsp[(2) - (2)].utype);}
break;
case 7:
/* Line 1806 of yacc.c */
#line 194 "parse.y"
{ (yyval.utype) = (yyvsp[(1) - (1)].utype); }
break;
case 8:
/* Line 1806 of yacc.c */
#line 195 "parse.y"
{ (yyval.utype) = (yyvsp[(2) - (2)].utype); (yyval.utype)->factor *= -1; }
break;
case 9:
/* Line 1806 of yacc.c */
#line 196 "parse.y"
{ (yyval.utype) = (yyvsp[(2) - (2)].utype); (yyval.utype)->factor *= -1; }
break;
case 10:
/* Line 1806 of yacc.c */
#line 197 "parse.y"
{ err = addunit((yyvsp[(1) - (3)].utype),(yyvsp[(3) - (3)].utype)); CHECK; (yyval.utype)=(yyvsp[(1) - (3)].utype);}
break;
case 11:
/* Line 1806 of yacc.c */
#line 198 "parse.y"
{ (yyvsp[(3) - (3)].utype)->factor *= -1; err = addunit((yyvsp[(1) - (3)].utype),(yyvsp[(3) - (3)].utype));
CHECK; (yyval.utype)=(yyvsp[(1) - (3)].utype);}
break;
case 12:
/* Line 1806 of yacc.c */
#line 200 "parse.y"
{ err = divunit((yyvsp[(1) - (3)].utype), (yyvsp[(3) - (3)].utype)); CHECK; (yyval.utype)=(yyvsp[(1) - (3)].utype);}
break;
case 13:
/* Line 1806 of yacc.c */
#line 201 "parse.y"
{ err = multunit((yyvsp[(1) - (3)].utype),(yyvsp[(3) - (3)].utype)); CHECK; (yyval.utype)=(yyvsp[(1) - (3)].utype);}
break;
case 14:
/* Line 1806 of yacc.c */
#line 202 "parse.y"
{ err = multunit((yyvsp[(1) - (3)].utype),(yyvsp[(3) - (3)].utype)); CHECK; (yyval.utype)=(yyvsp[(1) - (3)].utype);}
break;
case 15:
/* Line 1806 of yacc.c */
#line 205 "parse.y"
{ (yyval.number) = (yyvsp[(1) - (1)].number); }
break;
case 16:
/* Line 1806 of yacc.c */
#line 206 "parse.y"
{ (yyval.number) = (yyvsp[(1) - (3)].number) / (yyvsp[(3) - (3)].number); }
break;
case 17:
/* Line 1806 of yacc.c */
#line 209 "parse.y"
{ (yyval.utype) = (yyvsp[(2) - (3)].utype); }
break;
case 18:
/* Line 1806 of yacc.c */
#line 215 "parse.y"
{ (yyval.utype) = makenumunit((yyvsp[(1) - (1)].number),&err); CHECK;}
break;
case 19:
/* Line 1806 of yacc.c */
#line 216 "parse.y"
{ (yyval.utype) = (yyvsp[(1) - (1)].utype); }
break;
case 20:
/* Line 1806 of yacc.c */
#line 217 "parse.y"
{ err = unitpower((yyvsp[(1) - (3)].utype),(yyvsp[(3) - (3)].utype)); CHECK; (yyval.utype)=(yyvsp[(1) - (3)].utype);}
break;
case 21:
/* Line 1806 of yacc.c */
#line 218 "parse.y"
{ err = multunit((yyvsp[(1) - (3)].utype),(yyvsp[(3) - (3)].utype)); CHECK; (yyval.utype)=(yyvsp[(1) - (3)].utype);}
break;
case 22:
/* Line 1806 of yacc.c */
#line 219 "parse.y"
{ err = multunit((yyvsp[(1) - (2)].utype),(yyvsp[(2) - (2)].utype)); CHECK; (yyval.utype)=(yyvsp[(1) - (2)].utype);}
break;
case 23:
/* Line 1806 of yacc.c */
#line 220 "parse.y"
{ (yyval.utype)=(yyvsp[(1) - (1)].utype); }
break;
case 24:
/* Line 1806 of yacc.c */
#line 221 "parse.y"
{ err = rootunit((yyvsp[(2) - (2)].utype),2); CHECK; (yyval.utype)=(yyvsp[(2) - (2)].utype);}
break;
case 25:
/* Line 1806 of yacc.c */
#line 222 "parse.y"
{ err = rootunit((yyvsp[(2) - (2)].utype),3); CHECK; (yyval.utype)=(yyvsp[(2) - (2)].utype);}
break;
case 26:
/* Line 1806 of yacc.c */
#line 223 "parse.y"
{ err = funcunit((yyvsp[(2) - (2)].utype),(yyvsp[(1) - (2)].dfunc)); CHECK; (yyval.utype)=(yyvsp[(2) - (2)].utype);}
break;
case 27:
/* Line 1806 of yacc.c */
#line 224 "parse.y"
{ err = evalfunc((yyvsp[(2) - (2)].utype),(yyvsp[(1) - (2)].ufunc),0,0); CHECK; (yyval.utype)=(yyvsp[(2) - (2)].utype);}
break;
case 28:
/* Line 1806 of yacc.c */
#line 225 "parse.y"
{ err = evalfunc((yyvsp[(3) - (3)].utype),(yyvsp[(2) - (3)].ufunc),1,0); CHECK; (yyval.utype)=(yyvsp[(3) - (3)].utype);}
break;
case 29:
/* Line 1806 of yacc.c */
#line 227 "parse.y"
{ (yyvsp[(4) - (4)].utype)->factor *= -1;
err = unitpower((yyvsp[(1) - (4)].utype),(yyvsp[(4) - (4)].utype)); CHECK; (yyval.utype)=(yyvsp[(1) - (4)].utype);}
break;
case 30:
/* Line 1806 of yacc.c */
#line 230 "parse.y"
{ (yyvsp[(4) - (4)].utype)->factor *= -1;
err = unitpower((yyvsp[(1) - (4)].utype),(yyvsp[(4) - (4)].utype)); CHECK; (yyval.utype)=(yyvsp[(1) - (4)].utype);}
break;
case 31:
/* Line 1806 of yacc.c */
#line 232 "parse.y"
{ err = E_BADNUM; CHECK; }
break;
case 32:
/* Line 1806 of yacc.c */
#line 233 "parse.y"
{ err = E_PARSEMEM; CHECK; }
break;
case 33:
/* Line 1806 of yacc.c */
#line 234 "parse.y"
{ err = E_UNITEND; CHECK; }
break;
case 34:
/* Line 1806 of yacc.c */
#line 235 "parse.y"
{ err = E_LASTUNSET; CHECK; }
break;
case 35:
/* Line 1806 of yacc.c */
#line 236 "parse.y"
{ err = E_NOTAFUNC; CHECK; }
break;
/* Line 1806 of yacc.c */
#line 1803 "parse.tab.c"
default: break;
}
/* User semantic actions sometimes alter yychar, and that requires
that yytoken be updated with the new translation. We take the
approach of translating immediately before every use of yytoken.
One alternative is translating here after every semantic action,
but that translation would be missed if the semantic action invokes
YYABORT, YYACCEPT, or YYERROR immediately after altering yychar or
if it invokes YYBACKUP. In the case of YYABORT or YYACCEPT, an
incorrect destructor might then be invoked immediately. In the
case of YYERROR or YYBACKUP, subsequent parser actions might lead
to an incorrect destructor call or verbose syntax error message
before the lookahead is translated. */
YY_SYMBOL_PRINT ("-> $$ =", yyr1[yyn], &yyval, &yyloc);
YYPOPSTACK (yylen);
yylen = 0;
YY_STACK_PRINT (yyss, yyssp);
*++yyvsp = yyval;
/* Now `shift' the result of the reduction. Determine what state
that goes to, based on the state we popped back to and the rule
number reduced by. */
yyn = yyr1[yyn];
yystate = yypgoto[yyn - YYNTOKENS] + *yyssp;
if (0 <= yystate && yystate <= YYLAST && yycheck[yystate] == *yyssp)
yystate = yytable[yystate];
else
yystate = yydefgoto[yyn - YYNTOKENS];
goto yynewstate;
/*------------------------------------.
| yyerrlab -- here on detecting error |
`------------------------------------*/
yyerrlab:
/* Make sure we have latest lookahead translation. See comments at
user semantic actions for why this is necessary. */
yytoken = yychar == YYEMPTY ? YYEMPTY : YYTRANSLATE (yychar);
/* If not already recovering from an error, report this error. */
if (!yyerrstatus)
{
++yynerrs;
#if ! YYERROR_VERBOSE
yyerror (comm, YY_("syntax error"));
#else
# define YYSYNTAX_ERROR yysyntax_error (&yymsg_alloc, &yymsg, \
yyssp, yytoken)
{
char const *yymsgp = YY_("syntax error");
int yysyntax_error_status;
yysyntax_error_status = YYSYNTAX_ERROR;
if (yysyntax_error_status == 0)
yymsgp = yymsg;
else if (yysyntax_error_status == 1)
{
if (yymsg != yymsgbuf)
YYSTACK_FREE (yymsg);
yymsg = (char *) YYSTACK_ALLOC (yymsg_alloc);
if (!yymsg)
{
yymsg = yymsgbuf;
yymsg_alloc = sizeof yymsgbuf;
yysyntax_error_status = 2;
}
else
{
yysyntax_error_status = YYSYNTAX_ERROR;
yymsgp = yymsg;
}
}
yyerror (comm, yymsgp);
if (yysyntax_error_status == 2)
goto yyexhaustedlab;
}
# undef YYSYNTAX_ERROR
#endif
}
if (yyerrstatus == 3)
{
/* If just tried and failed to reuse lookahead token after an
error, discard it. */
if (yychar <= YYEOF)
{
/* Return failure if at end of input. */
if (yychar == YYEOF)
YYABORT;
}
else
{
yydestruct ("Error: discarding",
yytoken, &yylval, comm);
yychar = YYEMPTY;
}
}
/* Else will try to reuse lookahead token after shifting the error
token. */
goto yyerrlab1;
/*---------------------------------------------------.
| yyerrorlab -- error raised explicitly by YYERROR. |
`---------------------------------------------------*/
yyerrorlab:
/* Pacify compilers like GCC when the user code never invokes
YYERROR and the label yyerrorlab therefore never appears in user
code. */
if (/*CONSTCOND*/ 0)
goto yyerrorlab;
/* Do not reclaim the symbols of the rule which action triggered
this YYERROR. */
YYPOPSTACK (yylen);
yylen = 0;
YY_STACK_PRINT (yyss, yyssp);
yystate = *yyssp;
goto yyerrlab1;
/*-------------------------------------------------------------.
| yyerrlab1 -- common code for both syntax error and YYERROR. |
`-------------------------------------------------------------*/
yyerrlab1:
yyerrstatus = 3; /* Each real token shifted decrements this. */
for (;;)
{
yyn = yypact[yystate];
if (!yypact_value_is_default (yyn))
{
yyn += YYTERROR;
if (0 <= yyn && yyn <= YYLAST && yycheck[yyn] == YYTERROR)
{
yyn = yytable[yyn];
if (0 < yyn)
break;
}
}
/* Pop the current state because it cannot handle the error token. */
if (yyssp == yyss)
YYABORT;
yydestruct ("Error: popping",
yystos[yystate], yyvsp, comm);
YYPOPSTACK (1);
yystate = *yyssp;
YY_STACK_PRINT (yyss, yyssp);
}
*++yyvsp = yylval;
/* Shift the error token. */
YY_SYMBOL_PRINT ("Shifting", yystos[yyn], yyvsp, yylsp);
yystate = yyn;
goto yynewstate;
/*-------------------------------------.
| yyacceptlab -- YYACCEPT comes here. |
`-------------------------------------*/
yyacceptlab:
yyresult = 0;
goto yyreturn;
/*-----------------------------------.
| yyabortlab -- YYABORT comes here. |
`-----------------------------------*/
yyabortlab:
yyresult = 1;
goto yyreturn;
#if !defined(yyoverflow) || YYERROR_VERBOSE
/*-------------------------------------------------.
| yyexhaustedlab -- memory exhaustion comes here. |
`-------------------------------------------------*/
yyexhaustedlab:
yyerror (comm, YY_("memory exhausted"));
yyresult = 2;
/* Fall through. */
#endif
yyreturn:
if (yychar != YYEMPTY)
{
/* Make sure we have latest lookahead translation. See comments at
user semantic actions for why this is necessary. */
yytoken = YYTRANSLATE (yychar);
yydestruct ("Cleanup: discarding lookahead",
yytoken, &yylval, comm);
}
/* Do not reclaim the symbols of the rule which action triggered
this YYABORT or YYACCEPT. */
YYPOPSTACK (yylen);
YY_STACK_PRINT (yyss, yyssp);
while (yyssp != yyss)
{
yydestruct ("Cleanup: popping",
yystos[*yyssp], yyvsp, comm);
YYPOPSTACK (1);
}
#ifndef yyoverflow
if (yyss != yyssa)
YYSTACK_FREE (yyss);
#endif
#if YYERROR_VERBOSE
if (yymsg != yymsgbuf)
YYSTACK_FREE (yymsg);
#endif
/* Make sure YYID is used. */
return YYID (yyresult);
}
/* Line 2067 of yacc.c */
#line 242 "parse.y"
#ifndef strchr
# ifdef NO_STRCHR
# define strchr(a,b) index((a),(b))
# else
char *strchr();
# endif
#endif /* !strchr */
double strtod();
struct function
realfunctions[] = { {"sin", sin, ANGLEIN},
{"cos", cos, ANGLEIN},
{"tan", tan, ANGLEIN},
{"ln", log, DIMENSIONLESS},
{"log", log10, DIMENSIONLESS},
{"log2", logb2, DIMENSIONLESS},
{"exp", exp, DIMENSIONLESS},
{"acos", acos, ANGLEOUT},
{"atan", atan, ANGLEOUT},
{"asin", asin, ANGLEOUT},
{0, 0, 0}};
struct {
char op;
int value;
} optable[] = { {'*', MULTIPLY},
{'/', DIVIDE},
{'|', NUMDIV},
{'+', ADD},
{'(', '('},
{')', ')'},
{'^', EXPONENT},
{'~', FUNCINV},
{0, 0}};
struct {
char *name;
int value;
} strtable[] = { {"sqrt", SQRT},
{"cuberoot", CUBEROOT},
{"per" , DIVIDE},
{0, 0}};
#define LASTUNIT '_' /* Last unit symbol */
int yylex(YYSTYPE *lvalp, struct commtype *comm)
{
int length, count;
struct unittype *output;
char *inptr;
char *nonunitchars = "~;+-*/|\t\n^ ()"; /* Chars not allowed in unit name */
char *nonunitends = ".,_"; /* Can't start or end a unit */
char *number_start = ".,0123456789"; /* Can be first char of a number */
if (comm->location==-1) return 0;
inptr = comm->data + comm->location; /* Point to start of data */
/* Skip white space */
while( *inptr && strchr(WHITE,*inptr)) inptr++, comm->location++;
if (*inptr==0) {
comm->location = -1;
return EOL; /* Return failure if string has ended */
}
/* Check for **, an exponent operator. */
if (0==strncmp("**",inptr,2)){
comm->location += 2;
return EXPONENT;
}
/* Check for '-' and '*' which get special handling */
if (*inptr=='-'){
comm->location++;
if (parserflags.minusminus)
return MINUS;
return MULTMINUS;
}
if (*inptr=='*'){
comm->location++;
if (parserflags.oldstar)
return MULTIPLY;
return MULTSTAR;
}
/* Check for the "last unit" symbol */
if (*inptr == LASTUNIT) {
comm->location++;
if (!lastunitset)
return LASTUNSET;
output = getnewunit();
if (!output)
return MEMERROR;
unitcopy(output, &lastunit);
lvalp->utype = output;
return UNIT;
}
/* Look for single character ops */
for(count=0; optable[count].op; count++){
if (*inptr==optable[count].op) {
comm->location++;
return optable[count].value;
}
}
/* Look for numbers */
if (strchr(number_start,*inptr)){ /* prevent "nan" from being recognized */
char *endloc;
lvalp->number = strtod(inptr, &endloc);
if (inptr != endloc) {
comm->location += (endloc-inptr);
if (*endloc && strchr(number_start,*endloc))
return BADNUMBER;
else
return REAL;
}
}
/* Look for a word (function name or unit name) */
length = strcspn(inptr,nonunitchars);
if (!length){ /* Next char is not a valid unit char */
comm->location++;
return 0;
}
/* Check that unit name doesn't start or end with forbidden chars */
if (strchr(nonunitends,*inptr)){
comm->location++;
return 0;
}
if (strchr(nonunitends, inptr[length-1])){
comm->location+=length;
return 0;
}
/* Look for string operators */
for(count=0;strtable[count].name;count++){
if (length==strlen(strtable[count].name) &&
0==strncmp(strtable[count].name,inptr,length)){
comm->location += length;
return strtable[count].value;
}
}
/* Look for real function names */
for(count=0;realfunctions[count].name;count++){
if (length==strlen(realfunctions[count].name) &&
0==strncmp(realfunctions[count].name,inptr,length)){
lvalp->dfunc = realfunctions+count;
comm->location += length;
return RFUNC;
}
}
/* Look for function parameter */
if (function_parameter && length==strlen(function_parameter) &&
0==strncmp(function_parameter, inptr, length)){
output = getnewunit();
if (!output)
return MEMERROR;
unitcopy(output, parameter_value);
lvalp->utype = output;
comm->location += length;
return UNIT;
}
/* Look for user defined function */
lvalp->ufunc = fnlookup(inptr,length);
if (lvalp->ufunc){
comm->location += length;
return UFUNC;
}
/* Didn't find a special string, so treat it as unit name */
comm->location+=length;
if (strchr("23456789",inptr[length-1]) &&
!hassubscript(inptr,length)) { /* do exponent handling like m3 */
count = inptr[length-1] - '0';
length--;
if (strchr(number_start, inptr[length-1])){
return UNITEND;
}
} else count=1;
output = getnewunit();
if (!output)
return MEMERROR;
output->numerator[count]=0;
for(;count;count--){
output->numerator[count-1] = mymalloc(length+1,"(yylex)");
strncpy(output->numerator[count-1], inptr, length);
output->numerator[count-1][length]=0;
}
lvalp->utype=output;
return UNIT;
}
void yyerror(struct commtype *comm, char *s){}
void
freelist(int startunit)
{
if (nextunit>maxunit)
maxunit = nextunit;
while(nextunit>startunit){
freeunit(memtable[--nextunit]);
free(memtable[nextunit]);
}
}
int
parseunit(struct unittype *output, char *input,char **errstr,int *errloc)
{
struct commtype comm;
int startunit;
startunit = nextunit;
initializeunit(output);
comm.location = 0;
comm.data = input;
comm.errorcode = E_PARSE; /* Assume parse error */
errno=0;
if (yyparse(&comm) || errno){
if (comm.location==-1)
comm.location = strlen(input);
if (errstr){
if (comm.errorcode==E_FUNC || errno)
*errstr = strerror(errno);
else
*errstr=errormsg[comm.errorcode];
}
if (errloc)
*errloc = comm.location;
freelist(startunit);
return comm.errorcode;
} else {
if (errstr)
*errstr = 0;
multunit(output,comm.result);
freeunit(comm.result);
freelist(startunit);
return 0;
}
}
units-2.12/configure 0000775 0001750 0001750 00000442320 12603104457 013776 0 ustar adrian adrian #! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.69 for GNU units 2.12.
#
# Report bugs to .
#
#
# Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
#
#
# This configure script is free software; the Free Software Foundation
# gives unlimited permission to copy, distribute and modify it.
## -------------------- ##
## M4sh Initialization. ##
## -------------------- ##
# Be more Bourne compatible
DUALCASE=1; export DUALCASE # for MKS sh
if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then :
emulate sh
NULLCMD=:
# Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
# is contrary to our usage. Disable this feature.
alias -g '${1+"$@"}'='"$@"'
setopt NO_GLOB_SUBST
else
case `(set -o) 2>/dev/null` in #(
*posix*) :
set -o posix ;; #(
*) :
;;
esac
fi
as_nl='
'
export as_nl
# Printing a long string crashes Solaris 7 /usr/bin/printf.
as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
# Prefer a ksh shell builtin over an external printf program on Solaris,
# but without wasting forks for bash or zsh.
if test -z "$BASH_VERSION$ZSH_VERSION" \
&& (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='print -r --'
as_echo_n='print -rn --'
elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='printf %s\n'
as_echo_n='printf %s'
else
if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
as_echo_n='/usr/ucb/echo -n'
else
as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
as_echo_n_body='eval
arg=$1;
case $arg in #(
*"$as_nl"*)
expr "X$arg" : "X\\(.*\\)$as_nl";
arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
esac;
expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
'
export as_echo_n_body
as_echo_n='sh -c $as_echo_n_body as_echo'
fi
export as_echo_body
as_echo='sh -c $as_echo_body as_echo'
fi
# The user is always right.
if test "${PATH_SEPARATOR+set}" != set; then
PATH_SEPARATOR=:
(PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
(PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
PATH_SEPARATOR=';'
}
fi
# IFS
# We need space, tab and new line, in precisely that order. Quoting is
# there to prevent editors from complaining about space-tab.
# (If _AS_PATH_WALK were called with IFS unset, it would disable word
# splitting by setting IFS to empty value.)
IFS=" "" $as_nl"
# Find who we are. Look in the path if we contain no directory separator.
as_myself=
case $0 in #((
*[\\/]* ) as_myself=$0 ;;
*) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
done
IFS=$as_save_IFS
;;
esac
# We did not find ourselves, most probably we were run as `sh COMMAND'
# in which case we are not to be found in the path.
if test "x$as_myself" = x; then
as_myself=$0
fi
if test ! -f "$as_myself"; then
$as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
exit 1
fi
# Unset variables that we do not need and which cause bugs (e.g. in
# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1"
# suppresses any "Segmentation fault" message there. '((' could
# trigger a bug in pdksh 5.2.14.
for as_var in BASH_ENV ENV MAIL MAILPATH
do eval test x\${$as_var+set} = xset \
&& ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || :
done
PS1='$ '
PS2='> '
PS4='+ '
# NLS nuisances.
LC_ALL=C
export LC_ALL
LANGUAGE=C
export LANGUAGE
# CDPATH.
(unset CDPATH) >/dev/null 2>&1 && unset CDPATH
# Use a proper internal environment variable to ensure we don't fall
# into an infinite loop, continuously re-executing ourselves.
if test x"${_as_can_reexec}" != xno && test "x$CONFIG_SHELL" != x; then
_as_can_reexec=no; export _as_can_reexec;
# We cannot yet assume a decent shell, so we have to provide a
# neutralization value for shells without unset; and this also
# works around shells that cannot unset nonexistent variables.
# Preserve -v and -x to the replacement shell.
BASH_ENV=/dev/null
ENV=/dev/null
(unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV
case $- in # ((((
*v*x* | *x*v* ) as_opts=-vx ;;
*v* ) as_opts=-v ;;
*x* ) as_opts=-x ;;
* ) as_opts= ;;
esac
exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"}
# Admittedly, this is quite paranoid, since all the known shells bail
# out after a failed `exec'.
$as_echo "$0: could not re-execute with $CONFIG_SHELL" >&2
as_fn_exit 255
fi
# We don't want this to propagate to other subprocesses.
{ _as_can_reexec=; unset _as_can_reexec;}
if test "x$CONFIG_SHELL" = x; then
as_bourne_compatible="if test -n \"\${ZSH_VERSION+set}\" && (emulate sh) >/dev/null 2>&1; then :
emulate sh
NULLCMD=:
# Pre-4.2 versions of Zsh do word splitting on \${1+\"\$@\"}, which
# is contrary to our usage. Disable this feature.
alias -g '\${1+\"\$@\"}'='\"\$@\"'
setopt NO_GLOB_SUBST
else
case \`(set -o) 2>/dev/null\` in #(
*posix*) :
set -o posix ;; #(
*) :
;;
esac
fi
"
as_required="as_fn_return () { (exit \$1); }
as_fn_success () { as_fn_return 0; }
as_fn_failure () { as_fn_return 1; }
as_fn_ret_success () { return 0; }
as_fn_ret_failure () { return 1; }
exitcode=0
as_fn_success || { exitcode=1; echo as_fn_success failed.; }
as_fn_failure && { exitcode=1; echo as_fn_failure succeeded.; }
as_fn_ret_success || { exitcode=1; echo as_fn_ret_success failed.; }
as_fn_ret_failure && { exitcode=1; echo as_fn_ret_failure succeeded.; }
if ( set x; as_fn_ret_success y && test x = \"\$1\" ); then :
else
exitcode=1; echo positional parameters were not saved.
fi
test x\$exitcode = x0 || exit 1
test -x / || exit 1"
as_suggested=" as_lineno_1=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_1a=\$LINENO
as_lineno_2=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_2a=\$LINENO
eval 'test \"x\$as_lineno_1'\$as_run'\" != \"x\$as_lineno_2'\$as_run'\" &&
test \"x\`expr \$as_lineno_1'\$as_run' + 1\`\" = \"x\$as_lineno_2'\$as_run'\"' || exit 1
test \$(( 1 + 1 )) = 2 || exit 1"
if (eval "$as_required") 2>/dev/null; then :
as_have_required=yes
else
as_have_required=no
fi
if test x$as_have_required = xyes && (eval "$as_suggested") 2>/dev/null; then :
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
as_found=false
for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
as_found=:
case $as_dir in #(
/*)
for as_base in sh bash ksh sh5; do
# Try only shells that exist, to save several forks.
as_shell=$as_dir/$as_base
if { test -f "$as_shell" || test -f "$as_shell.exe"; } &&
{ $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$as_shell"; } 2>/dev/null; then :
CONFIG_SHELL=$as_shell as_have_required=yes
if { $as_echo "$as_bourne_compatible""$as_suggested" | as_run=a "$as_shell"; } 2>/dev/null; then :
break 2
fi
fi
done;;
esac
as_found=false
done
$as_found || { if { test -f "$SHELL" || test -f "$SHELL.exe"; } &&
{ $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$SHELL"; } 2>/dev/null; then :
CONFIG_SHELL=$SHELL as_have_required=yes
fi; }
IFS=$as_save_IFS
if test "x$CONFIG_SHELL" != x; then :
export CONFIG_SHELL
# We cannot yet assume a decent shell, so we have to provide a
# neutralization value for shells without unset; and this also
# works around shells that cannot unset nonexistent variables.
# Preserve -v and -x to the replacement shell.
BASH_ENV=/dev/null
ENV=/dev/null
(unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV
case $- in # ((((
*v*x* | *x*v* ) as_opts=-vx ;;
*v* ) as_opts=-v ;;
*x* ) as_opts=-x ;;
* ) as_opts= ;;
esac
exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"}
# Admittedly, this is quite paranoid, since all the known shells bail
# out after a failed `exec'.
$as_echo "$0: could not re-execute with $CONFIG_SHELL" >&2
exit 255
fi
if test x$as_have_required = xno; then :
$as_echo "$0: This script requires a shell more modern than all"
$as_echo "$0: the shells that I found on your system."
if test x${ZSH_VERSION+set} = xset ; then
$as_echo "$0: In particular, zsh $ZSH_VERSION has bugs and should"
$as_echo "$0: be upgraded to zsh 4.3.4 or later."
else
$as_echo "$0: Please tell bug-autoconf@gnu.org and adrianm@gnu.org
$0: about your system, including any error possibly output
$0: before this message. Then install a modern shell, or
$0: manually run the script under such a shell if you do
$0: have one."
fi
exit 1
fi
fi
fi
SHELL=${CONFIG_SHELL-/bin/sh}
export SHELL
# Unset more variables known to interfere with behavior of common tools.
CLICOLOR_FORCE= GREP_OPTIONS=
unset CLICOLOR_FORCE GREP_OPTIONS
## --------------------- ##
## M4sh Shell Functions. ##
## --------------------- ##
# as_fn_unset VAR
# ---------------
# Portably unset VAR.
as_fn_unset ()
{
{ eval $1=; unset $1;}
}
as_unset=as_fn_unset
# as_fn_set_status STATUS
# -----------------------
# Set $? to STATUS, without forking.
as_fn_set_status ()
{
return $1
} # as_fn_set_status
# as_fn_exit STATUS
# -----------------
# Exit the shell with STATUS, even in a "trap 0" or "set -e" context.
as_fn_exit ()
{
set +e
as_fn_set_status $1
exit $1
} # as_fn_exit
# as_fn_mkdir_p
# -------------
# Create "$as_dir" as a directory, including parents if necessary.
as_fn_mkdir_p ()
{
case $as_dir in #(
-*) as_dir=./$as_dir;;
esac
test -d "$as_dir" || eval $as_mkdir_p || {
as_dirs=
while :; do
case $as_dir in #(
*\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
*) as_qdir=$as_dir;;
esac
as_dirs="'$as_qdir' $as_dirs"
as_dir=`$as_dirname -- "$as_dir" ||
$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$as_dir" : 'X\(//\)[^/]' \| \
X"$as_dir" : 'X\(//\)$' \| \
X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$as_dir" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
test -d "$as_dir" && break
done
test -z "$as_dirs" || eval "mkdir $as_dirs"
} || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir"
} # as_fn_mkdir_p
# as_fn_executable_p FILE
# -----------------------
# Test if FILE is an executable regular file.
as_fn_executable_p ()
{
test -f "$1" && test -x "$1"
} # as_fn_executable_p
# as_fn_append VAR VALUE
# ----------------------
# Append the text in VALUE to the end of the definition contained in VAR. Take
# advantage of any shell optimizations that allow amortized linear growth over
# repeated appends, instead of the typical quadratic growth present in naive
# implementations.
if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then :
eval 'as_fn_append ()
{
eval $1+=\$2
}'
else
as_fn_append ()
{
eval $1=\$$1\$2
}
fi # as_fn_append
# as_fn_arith ARG...
# ------------------
# Perform arithmetic evaluation on the ARGs, and store the result in the
# global $as_val. Take advantage of shells that can avoid forks. The arguments
# must be portable across $(()) and expr.
if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then :
eval 'as_fn_arith ()
{
as_val=$(( $* ))
}'
else
as_fn_arith ()
{
as_val=`expr "$@" || test $? -eq 1`
}
fi # as_fn_arith
# as_fn_error STATUS ERROR [LINENO LOG_FD]
# ----------------------------------------
# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are
# provided, also output the error to LOG_FD, referencing LINENO. Then exit the
# script with STATUS, using 1 if that was 0.
as_fn_error ()
{
as_status=$1; test $as_status -eq 0 && as_status=1
if test "$4"; then
as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
$as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4
fi
$as_echo "$as_me: error: $2" >&2
as_fn_exit $as_status
} # as_fn_error
if expr a : '\(a\)' >/dev/null 2>&1 &&
test "X`expr 00001 : '.*\(...\)'`" = X001; then
as_expr=expr
else
as_expr=false
fi
if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
as_basename=basename
else
as_basename=false
fi
if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
as_dirname=dirname
else
as_dirname=false
fi
as_me=`$as_basename -- "$0" ||
$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
X"$0" : 'X\(//\)$' \| \
X"$0" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X/"$0" |
sed '/^.*\/\([^/][^/]*\)\/*$/{
s//\1/
q
}
/^X\/\(\/\/\)$/{
s//\1/
q
}
/^X\/\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
# Avoid depending upon Character Ranges.
as_cr_letters='abcdefghijklmnopqrstuvwxyz'
as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
as_cr_Letters=$as_cr_letters$as_cr_LETTERS
as_cr_digits='0123456789'
as_cr_alnum=$as_cr_Letters$as_cr_digits
as_lineno_1=$LINENO as_lineno_1a=$LINENO
as_lineno_2=$LINENO as_lineno_2a=$LINENO
eval 'test "x$as_lineno_1'$as_run'" != "x$as_lineno_2'$as_run'" &&
test "x`expr $as_lineno_1'$as_run' + 1`" = "x$as_lineno_2'$as_run'"' || {
# Blame Lee E. McMahon (1931-1989) for sed's syntax. :-)
sed -n '
p
/[$]LINENO/=
' <$as_myself |
sed '
s/[$]LINENO.*/&-/
t lineno
b
:lineno
N
:loop
s/[$]LINENO\([^'$as_cr_alnum'_].*\n\)\(.*\)/\2\1\2/
t loop
s/-\n.*//
' >$as_me.lineno &&
chmod +x "$as_me.lineno" ||
{ $as_echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2; as_fn_exit 1; }
# If we had to re-execute with $CONFIG_SHELL, we're ensured to have
# already done that, so ensure we don't try to do so again and fall
# in an infinite loop. This has already happened in practice.
_as_can_reexec=no; export _as_can_reexec
# Don't try to exec as it changes $[0], causing all sort of problems
# (the dirname of $[0] is not the place where we might find the
# original and so on. Autoconf is especially sensitive to this).
. "./$as_me.lineno"
# Exit status is that of the last command.
exit
}
ECHO_C= ECHO_N= ECHO_T=
case `echo -n x` in #(((((
-n*)
case `echo 'xy\c'` in
*c*) ECHO_T=' ';; # ECHO_T is single tab character.
xy) ECHO_C='\c';;
*) echo `echo ksh88 bug on AIX 6.1` > /dev/null
ECHO_T=' ';;
esac;;
*)
ECHO_N='-n';;
esac
rm -f conf$$ conf$$.exe conf$$.file
if test -d conf$$.dir; then
rm -f conf$$.dir/conf$$.file
else
rm -f conf$$.dir
mkdir conf$$.dir 2>/dev/null
fi
if (echo >conf$$.file) 2>/dev/null; then
if ln -s conf$$.file conf$$ 2>/dev/null; then
as_ln_s='ln -s'
# ... but there are two gotchas:
# 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
# 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
# In both cases, we have to default to `cp -pR'.
ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
as_ln_s='cp -pR'
elif ln conf$$.file conf$$ 2>/dev/null; then
as_ln_s=ln
else
as_ln_s='cp -pR'
fi
else
as_ln_s='cp -pR'
fi
rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
rmdir conf$$.dir 2>/dev/null
if mkdir -p . 2>/dev/null; then
as_mkdir_p='mkdir -p "$as_dir"'
else
test -d ./-p && rmdir ./-p
as_mkdir_p=false
fi
as_test_x='test -x'
as_executable_p=as_fn_executable_p
# Sed expression to map a string onto a valid CPP name.
as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
# Sed expression to map a string onto a valid variable name.
as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
test -n "$DJDIR" || exec 7<&0 &1
# Name of the host.
# hostname on some systems (SVR3.2, old GNU/Linux) returns a bogus exit status,
# so uname gets run too.
ac_hostname=`(hostname || uname -n) 2>/dev/null | sed 1q`
#
# Initializations.
#
ac_default_prefix=/usr/local
ac_clean_files=
ac_config_libobj_dir=.
LIBOBJS=
cross_compiling=no
subdirs=
MFLAGS=
MAKEFLAGS=
# Identity of this package.
PACKAGE_NAME='GNU units'
PACKAGE_TARNAME='units'
PACKAGE_VERSION='2.12'
PACKAGE_STRING='GNU units 2.12'
PACKAGE_BUGREPORT='adrianm@gnu.org'
PACKAGE_URL='http://www.gnu.org/software/units/'
# Factoring default headers for most tests.
ac_includes_default="\
#include
#ifdef HAVE_SYS_TYPES_H
# include
#endif
#ifdef HAVE_SYS_STAT_H
# include
#endif
#ifdef STDC_HEADERS
# include
# include
#else
# ifdef HAVE_STDLIB_H
# include
# endif
#endif
#ifdef HAVE_STRING_H
# if !defined STDC_HEADERS && defined HAVE_MEMORY_H
# include
# endif
# include
#endif
#ifdef HAVE_STRINGS_H
# include
#endif
#ifdef HAVE_INTTYPES_H
# include
#endif
#ifdef HAVE_STDINT_H
# include
#endif
#ifdef HAVE_UNISTD_H
# include
#endif"
ac_subst_vars='LTLIBOBJS
LIBOBJS
PYTHON
mkstoolkit
EGREP
GREP
CPP
MKDIR_P
INSTALL_DATA
INSTALL_SCRIPT
INSTALL_PROGRAM
OBJEXT
EXEEXT
ac_ct_CC
CPPFLAGS
LDFLAGS
CFLAGS
CC
MKSFIX
PYTHON_VERSION
HAVE_PYTHON
UDAT
STRFUNC
DEFIS
target_alias
host_alias
build_alias
LIBS
ECHO_T
ECHO_N
ECHO_C
DEFS
mandir
localedir
libdir
psdir
pdfdir
dvidir
htmldir
infodir
docdir
oldincludedir
includedir
localstatedir
sharedstatedir
sysconfdir
datadir
datarootdir
libexecdir
sbindir
bindir
program_transform_name
prefix
exec_prefix
PACKAGE_URL
PACKAGE_BUGREPORT
PACKAGE_STRING
PACKAGE_VERSION
PACKAGE_TARNAME
PACKAGE_NAME
PATH_SEPARATOR
SHELL'
ac_subst_files=''
ac_user_opts='
enable_option_checking
enable_relocation
'
ac_precious_vars='build_alias
host_alias
target_alias
CC
CFLAGS
LDFLAGS
LIBS
CPPFLAGS
CPP'
# Initialize some variables set by options.
ac_init_help=
ac_init_version=false
ac_unrecognized_opts=
ac_unrecognized_sep=
# The variables have the same names as the options, with
# dashes changed to underlines.
cache_file=/dev/null
exec_prefix=NONE
no_create=
no_recursion=
prefix=NONE
program_prefix=NONE
program_suffix=NONE
program_transform_name=s,x,x,
silent=
site=
srcdir=
verbose=
x_includes=NONE
x_libraries=NONE
# Installation directory options.
# These are left unexpanded so users can "make install exec_prefix=/foo"
# and all the variables that are supposed to be based on exec_prefix
# by default will actually change.
# Use braces instead of parens because sh, perl, etc. also accept them.
# (The list follows the same order as the GNU Coding Standards.)
bindir='${exec_prefix}/bin'
sbindir='${exec_prefix}/sbin'
libexecdir='${exec_prefix}/libexec'
datarootdir='${prefix}/share'
datadir='${datarootdir}'
sysconfdir='${prefix}/etc'
sharedstatedir='${prefix}/com'
localstatedir='${prefix}/var'
includedir='${prefix}/include'
oldincludedir='/usr/include'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
infodir='${datarootdir}/info'
htmldir='${docdir}'
dvidir='${docdir}'
pdfdir='${docdir}'
psdir='${docdir}'
libdir='${exec_prefix}/lib'
localedir='${datarootdir}/locale'
mandir='${datarootdir}/man'
ac_prev=
ac_dashdash=
for ac_option
do
# If the previous option needs an argument, assign it.
if test -n "$ac_prev"; then
eval $ac_prev=\$ac_option
ac_prev=
continue
fi
case $ac_option in
*=?*) ac_optarg=`expr "X$ac_option" : '[^=]*=\(.*\)'` ;;
*=) ac_optarg= ;;
*) ac_optarg=yes ;;
esac
# Accept the important Cygnus configure options, so we can diagnose typos.
case $ac_dashdash$ac_option in
--)
ac_dashdash=yes ;;
-bindir | --bindir | --bindi | --bind | --bin | --bi)
ac_prev=bindir ;;
-bindir=* | --bindir=* | --bindi=* | --bind=* | --bin=* | --bi=*)
bindir=$ac_optarg ;;
-build | --build | --buil | --bui | --bu)
ac_prev=build_alias ;;
-build=* | --build=* | --buil=* | --bui=* | --bu=*)
build_alias=$ac_optarg ;;
-cache-file | --cache-file | --cache-fil | --cache-fi \
| --cache-f | --cache- | --cache | --cach | --cac | --ca | --c)
ac_prev=cache_file ;;
-cache-file=* | --cache-file=* | --cache-fil=* | --cache-fi=* \
| --cache-f=* | --cache-=* | --cache=* | --cach=* | --cac=* | --ca=* | --c=*)
cache_file=$ac_optarg ;;
--config-cache | -C)
cache_file=config.cache ;;
-datadir | --datadir | --datadi | --datad)
ac_prev=datadir ;;
-datadir=* | --datadir=* | --datadi=* | --datad=*)
datadir=$ac_optarg ;;
-datarootdir | --datarootdir | --datarootdi | --datarootd | --dataroot \
| --dataroo | --dataro | --datar)
ac_prev=datarootdir ;;
-datarootdir=* | --datarootdir=* | --datarootdi=* | --datarootd=* \
| --dataroot=* | --dataroo=* | --dataro=* | --datar=*)
datarootdir=$ac_optarg ;;
-disable-* | --disable-*)
ac_useropt=`expr "x$ac_option" : 'x-*disable-\(.*\)'`
# Reject names that are not valid shell variable names.
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid feature name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"enable_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--disable-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval enable_$ac_useropt=no ;;
-docdir | --docdir | --docdi | --doc | --do)
ac_prev=docdir ;;
-docdir=* | --docdir=* | --docdi=* | --doc=* | --do=*)
docdir=$ac_optarg ;;
-dvidir | --dvidir | --dvidi | --dvid | --dvi | --dv)
ac_prev=dvidir ;;
-dvidir=* | --dvidir=* | --dvidi=* | --dvid=* | --dvi=* | --dv=*)
dvidir=$ac_optarg ;;
-enable-* | --enable-*)
ac_useropt=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'`
# Reject names that are not valid shell variable names.
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid feature name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"enable_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--enable-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval enable_$ac_useropt=\$ac_optarg ;;
-exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \
| --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \
| --exec | --exe | --ex)
ac_prev=exec_prefix ;;
-exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* \
| --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* \
| --exec=* | --exe=* | --ex=*)
exec_prefix=$ac_optarg ;;
-gas | --gas | --ga | --g)
# Obsolete; use --with-gas.
with_gas=yes ;;
-help | --help | --hel | --he | -h)
ac_init_help=long ;;
-help=r* | --help=r* | --hel=r* | --he=r* | -hr*)
ac_init_help=recursive ;;
-help=s* | --help=s* | --hel=s* | --he=s* | -hs*)
ac_init_help=short ;;
-host | --host | --hos | --ho)
ac_prev=host_alias ;;
-host=* | --host=* | --hos=* | --ho=*)
host_alias=$ac_optarg ;;
-htmldir | --htmldir | --htmldi | --htmld | --html | --htm | --ht)
ac_prev=htmldir ;;
-htmldir=* | --htmldir=* | --htmldi=* | --htmld=* | --html=* | --htm=* \
| --ht=*)
htmldir=$ac_optarg ;;
-includedir | --includedir | --includedi | --included | --include \
| --includ | --inclu | --incl | --inc)
ac_prev=includedir ;;
-includedir=* | --includedir=* | --includedi=* | --included=* | --include=* \
| --includ=* | --inclu=* | --incl=* | --inc=*)
includedir=$ac_optarg ;;
-infodir | --infodir | --infodi | --infod | --info | --inf)
ac_prev=infodir ;;
-infodir=* | --infodir=* | --infodi=* | --infod=* | --info=* | --inf=*)
infodir=$ac_optarg ;;
-libdir | --libdir | --libdi | --libd)
ac_prev=libdir ;;
-libdir=* | --libdir=* | --libdi=* | --libd=*)
libdir=$ac_optarg ;;
-libexecdir | --libexecdir | --libexecdi | --libexecd | --libexec \
| --libexe | --libex | --libe)
ac_prev=libexecdir ;;
-libexecdir=* | --libexecdir=* | --libexecdi=* | --libexecd=* | --libexec=* \
| --libexe=* | --libex=* | --libe=*)
libexecdir=$ac_optarg ;;
-localedir | --localedir | --localedi | --localed | --locale)
ac_prev=localedir ;;
-localedir=* | --localedir=* | --localedi=* | --localed=* | --locale=*)
localedir=$ac_optarg ;;
-localstatedir | --localstatedir | --localstatedi | --localstated \
| --localstate | --localstat | --localsta | --localst | --locals)
ac_prev=localstatedir ;;
-localstatedir=* | --localstatedir=* | --localstatedi=* | --localstated=* \
| --localstate=* | --localstat=* | --localsta=* | --localst=* | --locals=*)
localstatedir=$ac_optarg ;;
-mandir | --mandir | --mandi | --mand | --man | --ma | --m)
ac_prev=mandir ;;
-mandir=* | --mandir=* | --mandi=* | --mand=* | --man=* | --ma=* | --m=*)
mandir=$ac_optarg ;;
-nfp | --nfp | --nf)
# Obsolete; use --without-fp.
with_fp=no ;;
-no-create | --no-create | --no-creat | --no-crea | --no-cre \
| --no-cr | --no-c | -n)
no_create=yes ;;
-no-recursion | --no-recursion | --no-recursio | --no-recursi \
| --no-recurs | --no-recur | --no-recu | --no-rec | --no-re | --no-r)
no_recursion=yes ;;
-oldincludedir | --oldincludedir | --oldincludedi | --oldincluded \
| --oldinclude | --oldinclud | --oldinclu | --oldincl | --oldinc \
| --oldin | --oldi | --old | --ol | --o)
ac_prev=oldincludedir ;;
-oldincludedir=* | --oldincludedir=* | --oldincludedi=* | --oldincluded=* \
| --oldinclude=* | --oldinclud=* | --oldinclu=* | --oldincl=* | --oldinc=* \
| --oldin=* | --oldi=* | --old=* | --ol=* | --o=*)
oldincludedir=$ac_optarg ;;
-prefix | --prefix | --prefi | --pref | --pre | --pr | --p)
ac_prev=prefix ;;
-prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*)
prefix=$ac_optarg ;;
-program-prefix | --program-prefix | --program-prefi | --program-pref \
| --program-pre | --program-pr | --program-p)
ac_prev=program_prefix ;;
-program-prefix=* | --program-prefix=* | --program-prefi=* \
| --program-pref=* | --program-pre=* | --program-pr=* | --program-p=*)
program_prefix=$ac_optarg ;;
-program-suffix | --program-suffix | --program-suffi | --program-suff \
| --program-suf | --program-su | --program-s)
ac_prev=program_suffix ;;
-program-suffix=* | --program-suffix=* | --program-suffi=* \
| --program-suff=* | --program-suf=* | --program-su=* | --program-s=*)
program_suffix=$ac_optarg ;;
-program-transform-name | --program-transform-name \
| --program-transform-nam | --program-transform-na \
| --program-transform-n | --program-transform- \
| --program-transform | --program-transfor \
| --program-transfo | --program-transf \
| --program-trans | --program-tran \
| --progr-tra | --program-tr | --program-t)
ac_prev=program_transform_name ;;
-program-transform-name=* | --program-transform-name=* \
| --program-transform-nam=* | --program-transform-na=* \
| --program-transform-n=* | --program-transform-=* \
| --program-transform=* | --program-transfor=* \
| --program-transfo=* | --program-transf=* \
| --program-trans=* | --program-tran=* \
| --progr-tra=* | --program-tr=* | --program-t=*)
program_transform_name=$ac_optarg ;;
-pdfdir | --pdfdir | --pdfdi | --pdfd | --pdf | --pd)
ac_prev=pdfdir ;;
-pdfdir=* | --pdfdir=* | --pdfdi=* | --pdfd=* | --pdf=* | --pd=*)
pdfdir=$ac_optarg ;;
-psdir | --psdir | --psdi | --psd | --ps)
ac_prev=psdir ;;
-psdir=* | --psdir=* | --psdi=* | --psd=* | --ps=*)
psdir=$ac_optarg ;;
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil)
silent=yes ;;
-sbindir | --sbindir | --sbindi | --sbind | --sbin | --sbi | --sb)
ac_prev=sbindir ;;
-sbindir=* | --sbindir=* | --sbindi=* | --sbind=* | --sbin=* \
| --sbi=* | --sb=*)
sbindir=$ac_optarg ;;
-sharedstatedir | --sharedstatedir | --sharedstatedi \
| --sharedstated | --sharedstate | --sharedstat | --sharedsta \
| --sharedst | --shareds | --shared | --share | --shar \
| --sha | --sh)
ac_prev=sharedstatedir ;;
-sharedstatedir=* | --sharedstatedir=* | --sharedstatedi=* \
| --sharedstated=* | --sharedstate=* | --sharedstat=* | --sharedsta=* \
| --sharedst=* | --shareds=* | --shared=* | --share=* | --shar=* \
| --sha=* | --sh=*)
sharedstatedir=$ac_optarg ;;
-site | --site | --sit)
ac_prev=site ;;
-site=* | --site=* | --sit=*)
site=$ac_optarg ;;
-srcdir | --srcdir | --srcdi | --srcd | --src | --sr)
ac_prev=srcdir ;;
-srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*)
srcdir=$ac_optarg ;;
-sysconfdir | --sysconfdir | --sysconfdi | --sysconfd | --sysconf \
| --syscon | --sysco | --sysc | --sys | --sy)
ac_prev=sysconfdir ;;
-sysconfdir=* | --sysconfdir=* | --sysconfdi=* | --sysconfd=* | --sysconf=* \
| --syscon=* | --sysco=* | --sysc=* | --sys=* | --sy=*)
sysconfdir=$ac_optarg ;;
-target | --target | --targe | --targ | --tar | --ta | --t)
ac_prev=target_alias ;;
-target=* | --target=* | --targe=* | --targ=* | --tar=* | --ta=* | --t=*)
target_alias=$ac_optarg ;;
-v | -verbose | --verbose | --verbos | --verbo | --verb)
verbose=yes ;;
-version | --version | --versio | --versi | --vers | -V)
ac_init_version=: ;;
-with-* | --with-*)
ac_useropt=`expr "x$ac_option" : 'x-*with-\([^=]*\)'`
# Reject names that are not valid shell variable names.
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid package name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"with_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--with-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval with_$ac_useropt=\$ac_optarg ;;
-without-* | --without-*)
ac_useropt=`expr "x$ac_option" : 'x-*without-\(.*\)'`
# Reject names that are not valid shell variable names.
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid package name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"with_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--without-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval with_$ac_useropt=no ;;
--x)
# Obsolete; use --with-x.
with_x=yes ;;
-x-includes | --x-includes | --x-include | --x-includ | --x-inclu \
| --x-incl | --x-inc | --x-in | --x-i)
ac_prev=x_includes ;;
-x-includes=* | --x-includes=* | --x-include=* | --x-includ=* | --x-inclu=* \
| --x-incl=* | --x-inc=* | --x-in=* | --x-i=*)
x_includes=$ac_optarg ;;
-x-libraries | --x-libraries | --x-librarie | --x-librari \
| --x-librar | --x-libra | --x-libr | --x-lib | --x-li | --x-l)
ac_prev=x_libraries ;;
-x-libraries=* | --x-libraries=* | --x-librarie=* | --x-librari=* \
| --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*)
x_libraries=$ac_optarg ;;
-*) as_fn_error $? "unrecognized option: \`$ac_option'
Try \`$0 --help' for more information"
;;
*=*)
ac_envvar=`expr "x$ac_option" : 'x\([^=]*\)='`
# Reject names that are not valid shell variable names.
case $ac_envvar in #(
'' | [0-9]* | *[!_$as_cr_alnum]* )
as_fn_error $? "invalid variable name: \`$ac_envvar'" ;;
esac
eval $ac_envvar=\$ac_optarg
export $ac_envvar ;;
*)
# FIXME: should be removed in autoconf 3.0.
$as_echo "$as_me: WARNING: you should use --build, --host, --target" >&2
expr "x$ac_option" : ".*[^-._$as_cr_alnum]" >/dev/null &&
$as_echo "$as_me: WARNING: invalid host type: $ac_option" >&2
: "${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option}"
;;
esac
done
if test -n "$ac_prev"; then
ac_option=--`echo $ac_prev | sed 's/_/-/g'`
as_fn_error $? "missing argument to $ac_option"
fi
if test -n "$ac_unrecognized_opts"; then
case $enable_option_checking in
no) ;;
fatal) as_fn_error $? "unrecognized options: $ac_unrecognized_opts" ;;
*) $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2 ;;
esac
fi
# Check all directory arguments for consistency.
for ac_var in exec_prefix prefix bindir sbindir libexecdir datarootdir \
datadir sysconfdir sharedstatedir localstatedir includedir \
oldincludedir docdir infodir htmldir dvidir pdfdir psdir \
libdir localedir mandir
do
eval ac_val=\$$ac_var
# Remove trailing slashes.
case $ac_val in
*/ )
ac_val=`expr "X$ac_val" : 'X\(.*[^/]\)' \| "X$ac_val" : 'X\(.*\)'`
eval $ac_var=\$ac_val;;
esac
# Be sure to have absolute directory names.
case $ac_val in
[\\/$]* | ?:[\\/]* ) continue;;
NONE | '' ) case $ac_var in *prefix ) continue;; esac;;
esac
as_fn_error $? "expected an absolute directory name for --$ac_var: $ac_val"
done
# There might be people who depend on the old broken behavior: `$host'
# used to hold the argument of --host etc.
# FIXME: To remove some day.
build=$build_alias
host=$host_alias
target=$target_alias
# FIXME: To remove some day.
if test "x$host_alias" != x; then
if test "x$build_alias" = x; then
cross_compiling=maybe
elif test "x$build_alias" != "x$host_alias"; then
cross_compiling=yes
fi
fi
ac_tool_prefix=
test -n "$host_alias" && ac_tool_prefix=$host_alias-
test "$silent" = yes && exec 6>/dev/null
ac_pwd=`pwd` && test -n "$ac_pwd" &&
ac_ls_di=`ls -di .` &&
ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||
as_fn_error $? "working directory cannot be determined"
test "X$ac_ls_di" = "X$ac_pwd_ls_di" ||
as_fn_error $? "pwd does not report name of working directory"
# Find the source files, if location was not specified.
if test -z "$srcdir"; then
ac_srcdir_defaulted=yes
# Try the directory containing this script, then the parent directory.
ac_confdir=`$as_dirname -- "$as_myself" ||
$as_expr X"$as_myself" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$as_myself" : 'X\(//\)[^/]' \| \
X"$as_myself" : 'X\(//\)$' \| \
X"$as_myself" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$as_myself" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
srcdir=$ac_confdir
if test ! -r "$srcdir/$ac_unique_file"; then
srcdir=..
fi
else
ac_srcdir_defaulted=no
fi
if test ! -r "$srcdir/$ac_unique_file"; then
test "$ac_srcdir_defaulted" = yes && srcdir="$ac_confdir or .."
as_fn_error $? "cannot find sources ($ac_unique_file) in $srcdir"
fi
ac_msg="sources are in $srcdir, but \`cd $srcdir' does not work"
ac_abs_confdir=`(
cd "$srcdir" && test -r "./$ac_unique_file" || as_fn_error $? "$ac_msg"
pwd)`
# When building in place, set srcdir=.
if test "$ac_abs_confdir" = "$ac_pwd"; then
srcdir=.
fi
# Remove unnecessary trailing slashes from srcdir.
# Double slashes in file names in object file debugging info
# mess up M-x gdb in Emacs.
case $srcdir in
*/) srcdir=`expr "X$srcdir" : 'X\(.*[^/]\)' \| "X$srcdir" : 'X\(.*\)'`;;
esac
for ac_var in $ac_precious_vars; do
eval ac_env_${ac_var}_set=\${${ac_var}+set}
eval ac_env_${ac_var}_value=\$${ac_var}
eval ac_cv_env_${ac_var}_set=\${${ac_var}+set}
eval ac_cv_env_${ac_var}_value=\$${ac_var}
done
#
# Report the --help message.
#
if test "$ac_init_help" = "long"; then
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
\`configure' configures GNU units 2.12 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.
Defaults for the options are specified in brackets.
Configuration:
-h, --help display this help and exit
--help=short display options specific to this package
--help=recursive display the short help of all the included packages
-V, --version display version information and exit
-q, --quiet, --silent do not print \`checking ...' messages
--cache-file=FILE cache test results in FILE [disabled]
-C, --config-cache alias for \`--cache-file=config.cache'
-n, --no-create do not create output files
--srcdir=DIR find the sources in DIR [configure dir or \`..']
Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
[$ac_default_prefix]
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
[PREFIX]
By default, \`make install' will install all the files in
\`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc. You can specify
an installation prefix other than \`$ac_default_prefix' using \`--prefix',
for instance \`--prefix=\$HOME'.
For better control, use the options below.
Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
--datadir=DIR read-only architecture-independent data [DATAROOTDIR]
--infodir=DIR info documentation [DATAROOTDIR/info]
--localedir=DIR locale-dependent data [DATAROOTDIR/locale]
--mandir=DIR man documentation [DATAROOTDIR/man]
--docdir=DIR documentation root [DATAROOTDIR/doc/units]
--htmldir=DIR html documentation [DOCDIR]
--dvidir=DIR dvi documentation [DOCDIR]
--pdfdir=DIR pdf documentation [DOCDIR]
--psdir=DIR ps documentation [DOCDIR]
_ACEOF
cat <<\_ACEOF
Program names:
--program-prefix=PREFIX prepend PREFIX to installed program names
--program-suffix=SUFFIX append SUFFIX to installed program names
--program-transform-name=PROGRAM run sed PROGRAM on installed program names
_ACEOF
fi
if test -n "$ac_init_help"; then
case $ac_init_help in
short | recursive ) echo "Configuration of GNU units 2.12:";;
esac
cat <<\_ACEOF
Optional Features:
--disable-option-checking ignore unrecognized --enable/--with options
--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
--enable-relocation look in program directory for units data files
(default is NO)
Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L if you have libraries in a
nonstandard directory
LIBS libraries to pass to the linker, e.g. -l
CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I if
you have headers in a nonstandard directory
CPP C preprocessor
Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.
Report bugs to .
GNU units home page: .
General help using GNU software: .
_ACEOF
ac_status=$?
fi
if test "$ac_init_help" = "recursive"; then
# If there are subdirs, report their specific --help.
for ac_dir in : $ac_subdirs_all; do test "x$ac_dir" = x: && continue
test -d "$ac_dir" ||
{ cd "$srcdir" && ac_pwd=`pwd` && srcdir=. && test -d "$ac_dir"; } ||
continue
ac_builddir=.
case "$ac_dir" in
.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
*)
ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
# A ".." for each directory in $ac_dir_suffix.
ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
case $ac_top_builddir_sub in
"") ac_top_builddir_sub=. ac_top_build_prefix= ;;
*) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
esac ;;
esac
ac_abs_top_builddir=$ac_pwd
ac_abs_builddir=$ac_pwd$ac_dir_suffix
# for backward compatibility:
ac_top_builddir=$ac_top_build_prefix
case $srcdir in
.) # We are building in place.
ac_srcdir=.
ac_top_srcdir=$ac_top_builddir_sub
ac_abs_top_srcdir=$ac_pwd ;;
[\\/]* | ?:[\\/]* ) # Absolute name.
ac_srcdir=$srcdir$ac_dir_suffix;
ac_top_srcdir=$srcdir
ac_abs_top_srcdir=$srcdir ;;
*) # Relative name.
ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
ac_top_srcdir=$ac_top_build_prefix$srcdir
ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
esac
ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
cd "$ac_dir" || { ac_status=$?; continue; }
# Check for guested configure.
if test -f "$ac_srcdir/configure.gnu"; then
echo &&
$SHELL "$ac_srcdir/configure.gnu" --help=recursive
elif test -f "$ac_srcdir/configure"; then
echo &&
$SHELL "$ac_srcdir/configure" --help=recursive
else
$as_echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2
fi || ac_status=$?
cd "$ac_pwd" || { ac_status=$?; break; }
done
fi
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
GNU units configure 2.12
generated by GNU Autoconf 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
This configure script is free software; the Free Software Foundation
gives unlimited permission to copy, distribute and modify it.
_ACEOF
exit
fi
## ------------------------ ##
## Autoconf initialization. ##
## ------------------------ ##
# ac_fn_c_try_compile LINENO
# --------------------------
# Try to compile conftest.$ac_ext, and return whether this succeeded.
ac_fn_c_try_compile ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
rm -f conftest.$ac_objext
if { { ac_try="$ac_compile"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_compile") 2>conftest.err
ac_status=$?
if test -s conftest.err; then
grep -v '^ *+' conftest.err >conftest.er1
cat conftest.er1 >&5
mv -f conftest.er1 conftest.err
fi
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; } && {
test -z "$ac_c_werror_flag" ||
test ! -s conftest.err
} && test -s conftest.$ac_objext; then :
ac_retval=0
else
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
ac_retval=1
fi
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
as_fn_set_status $ac_retval
} # ac_fn_c_try_compile
# ac_fn_c_try_link LINENO
# -----------------------
# Try to link conftest.$ac_ext, and return whether this succeeded.
ac_fn_c_try_link ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
rm -f conftest.$ac_objext conftest$ac_exeext
if { { ac_try="$ac_link"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>conftest.err
ac_status=$?
if test -s conftest.err; then
grep -v '^ *+' conftest.err >conftest.er1
cat conftest.er1 >&5
mv -f conftest.er1 conftest.err
fi
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; } && {
test -z "$ac_c_werror_flag" ||
test ! -s conftest.err
} && test -s conftest$ac_exeext && {
test "$cross_compiling" = yes ||
test -x conftest$ac_exeext
}; then :
ac_retval=0
else
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
ac_retval=1
fi
# Delete the IPA/IPO (Inter Procedural Analysis/Optimization) information
# created by the PGI compiler (conftest_ipa8_conftest.oo), as it would
# interfere with the next link command; also delete a directory that is
# left behind by Apple's compiler. We do this before executing the actions.
rm -rf conftest.dSYM conftest_ipa8_conftest.oo
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
as_fn_set_status $ac_retval
} # ac_fn_c_try_link
# ac_fn_c_check_decl LINENO SYMBOL VAR INCLUDES
# ---------------------------------------------
# Tests whether SYMBOL is declared in INCLUDES, setting cache variable VAR
# accordingly.
ac_fn_c_check_decl ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
as_decl_name=`echo $2|sed 's/ *(.*//'`
as_decl_use=`echo $2|sed -e 's/(/((/' -e 's/)/) 0&/' -e 's/,/) 0& (/g'`
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $as_decl_name is declared" >&5
$as_echo_n "checking whether $as_decl_name is declared... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
$4
int
main ()
{
#ifndef $as_decl_name
#ifdef __cplusplus
(void) $as_decl_use;
#else
(void) $as_decl_name;
#endif
#endif
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
eval "$3=yes"
else
eval "$3=no"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
} # ac_fn_c_check_decl
# ac_fn_c_try_cpp LINENO
# ----------------------
# Try to preprocess conftest.$ac_ext, and return whether this succeeded.
ac_fn_c_try_cpp ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
if { { ac_try="$ac_cpp conftest.$ac_ext"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_cpp conftest.$ac_ext") 2>conftest.err
ac_status=$?
if test -s conftest.err; then
grep -v '^ *+' conftest.err >conftest.er1
cat conftest.er1 >&5
mv -f conftest.er1 conftest.err
fi
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; } > conftest.i && {
test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" ||
test ! -s conftest.err
}; then :
ac_retval=0
else
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
ac_retval=1
fi
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
as_fn_set_status $ac_retval
} # ac_fn_c_try_cpp
# ac_fn_c_check_header_mongrel LINENO HEADER VAR INCLUDES
# -------------------------------------------------------
# Tests whether HEADER exists, giving a warning if it cannot be compiled using
# the include files in INCLUDES and setting the cache variable VAR
# accordingly.
ac_fn_c_check_header_mongrel ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
if eval \${$3+:} false; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
$as_echo_n "checking for $2... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
else
# Is the header compilable?
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking $2 usability" >&5
$as_echo_n "checking $2 usability... " >&6; }
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
$4
#include <$2>
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
ac_header_compiler=yes
else
ac_header_compiler=no
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_header_compiler" >&5
$as_echo "$ac_header_compiler" >&6; }
# Is the header present?
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking $2 presence" >&5
$as_echo_n "checking $2 presence... " >&6; }
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include <$2>
_ACEOF
if ac_fn_c_try_cpp "$LINENO"; then :
ac_header_preproc=yes
else
ac_header_preproc=no
fi
rm -f conftest.err conftest.i conftest.$ac_ext
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_header_preproc" >&5
$as_echo "$ac_header_preproc" >&6; }
# So? What about this header?
case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in #((
yes:no: )
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: accepted by the compiler, rejected by the preprocessor!" >&5
$as_echo "$as_me: WARNING: $2: accepted by the compiler, rejected by the preprocessor!" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5
$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;}
;;
no:yes:* )
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: present but cannot be compiled" >&5
$as_echo "$as_me: WARNING: $2: present but cannot be compiled" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: check for missing prerequisite headers?" >&5
$as_echo "$as_me: WARNING: $2: check for missing prerequisite headers?" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: see the Autoconf documentation" >&5
$as_echo "$as_me: WARNING: $2: see the Autoconf documentation" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: section \"Present But Cannot Be Compiled\"" >&5
$as_echo "$as_me: WARNING: $2: section \"Present But Cannot Be Compiled\"" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5
$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;}
( $as_echo "## ------------------------------ ##
## Report this to adrianm@gnu.org ##
## ------------------------------ ##"
) | sed "s/^/$as_me: WARNING: /" >&2
;;
esac
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
$as_echo_n "checking for $2... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
else
eval "$3=\$ac_header_compiler"
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
fi
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
} # ac_fn_c_check_header_mongrel
# ac_fn_c_try_run LINENO
# ----------------------
# Try to link conftest.$ac_ext, and return whether this succeeded. Assumes
# that executables *can* be run.
ac_fn_c_try_run ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
if { { ac_try="$ac_link"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; } && { ac_try='./conftest$ac_exeext'
{ { case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_try") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; }; then :
ac_retval=0
else
$as_echo "$as_me: program exited with status $ac_status" >&5
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
ac_retval=$ac_status
fi
rm -rf conftest.dSYM conftest_ipa8_conftest.oo
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
as_fn_set_status $ac_retval
} # ac_fn_c_try_run
# ac_fn_c_check_header_compile LINENO HEADER VAR INCLUDES
# -------------------------------------------------------
# Tests whether HEADER exists and can be compiled using the include files in
# INCLUDES, setting the cache variable VAR accordingly.
ac_fn_c_check_header_compile ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
$as_echo_n "checking for $2... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
$4
#include <$2>
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
eval "$3=yes"
else
eval "$3=no"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
} # ac_fn_c_check_header_compile
# ac_fn_c_check_func LINENO FUNC VAR
# ----------------------------------
# Tests whether FUNC exists, setting the cache variable VAR accordingly
ac_fn_c_check_func ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
$as_echo_n "checking for $2... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
/* Define $2 to an innocuous variant, in case declares $2.
For example, HP-UX 11i declares gettimeofday. */
#define $2 innocuous_$2
/* System header to define __stub macros and hopefully few prototypes,
which can conflict with char $2 (); below.
Prefer to if __STDC__ is defined, since
exists even on freestanding compilers. */
#ifdef __STDC__
# include
#else
# include
#endif
#undef $2
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char $2 ();
/* The GNU C library defines this for functions which it implements
to always fail with ENOSYS. Some functions are actually named
something starting with __ and the normal name is an alias. */
#if defined __stub_$2 || defined __stub___$2
choke me
#endif
int
main ()
{
return $2 ();
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
eval "$3=yes"
else
eval "$3=no"
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
} # ac_fn_c_check_func
cat >config.log <<_ACEOF
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by GNU units $as_me 2.12, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ $0 $@
_ACEOF
exec 5>>config.log
{
cat <<_ASUNAME
## --------- ##
## Platform. ##
## --------- ##
hostname = `(hostname || uname -n) 2>/dev/null | sed 1q`
uname -m = `(uname -m) 2>/dev/null || echo unknown`
uname -r = `(uname -r) 2>/dev/null || echo unknown`
uname -s = `(uname -s) 2>/dev/null || echo unknown`
uname -v = `(uname -v) 2>/dev/null || echo unknown`
/usr/bin/uname -p = `(/usr/bin/uname -p) 2>/dev/null || echo unknown`
/bin/uname -X = `(/bin/uname -X) 2>/dev/null || echo unknown`
/bin/arch = `(/bin/arch) 2>/dev/null || echo unknown`
/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null || echo unknown`
/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null || echo unknown`
/usr/bin/hostinfo = `(/usr/bin/hostinfo) 2>/dev/null || echo unknown`
/bin/machine = `(/bin/machine) 2>/dev/null || echo unknown`
/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null || echo unknown`
/bin/universe = `(/bin/universe) 2>/dev/null || echo unknown`
_ASUNAME
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
$as_echo "PATH: $as_dir"
done
IFS=$as_save_IFS
} >&5
cat >&5 <<_ACEOF
## ----------- ##
## Core tests. ##
## ----------- ##
_ACEOF
# Keep a trace of the command line.
# Strip out --no-create and --no-recursion so they do not pile up.
# Strip out --silent because we don't want to record it for future runs.
# Also quote any args containing shell meta-characters.
# Make two passes to allow for proper duplicate-argument suppression.
ac_configure_args=
ac_configure_args0=
ac_configure_args1=
ac_must_keep_next=false
for ac_pass in 1 2
do
for ac_arg
do
case $ac_arg in
-no-create | --no-c* | -n | -no-recursion | --no-r*) continue ;;
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil)
continue ;;
*\'*)
ac_arg=`$as_echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;;
esac
case $ac_pass in
1) as_fn_append ac_configure_args0 " '$ac_arg'" ;;
2)
as_fn_append ac_configure_args1 " '$ac_arg'"
if test $ac_must_keep_next = true; then
ac_must_keep_next=false # Got value, back to normal.
else
case $ac_arg in
*=* | --config-cache | -C | -disable-* | --disable-* \
| -enable-* | --enable-* | -gas | --g* | -nfp | --nf* \
| -q | -quiet | --q* | -silent | --sil* | -v | -verb* \
| -with-* | --with-* | -without-* | --without-* | --x)
case "$ac_configure_args0 " in
"$ac_configure_args1"*" '$ac_arg' "* ) continue ;;
esac
;;
-* ) ac_must_keep_next=true ;;
esac
fi
as_fn_append ac_configure_args " '$ac_arg'"
;;
esac
done
done
{ ac_configure_args0=; unset ac_configure_args0;}
{ ac_configure_args1=; unset ac_configure_args1;}
# When interrupted or exit'd, cleanup temporary files, and complete
# config.log. We remove comments because anyway the quotes in there
# would cause problems or look ugly.
# WARNING: Use '\'' to represent an apostrophe within the trap.
# WARNING: Do not start the trap code with a newline, due to a FreeBSD 4.0 bug.
trap 'exit_status=$?
# Save into config.log some information that might help in debugging.
{
echo
$as_echo "## ---------------- ##
## Cache variables. ##
## ---------------- ##"
echo
# The following way of writing the cache mishandles newlines in values,
(
for ac_var in `(set) 2>&1 | sed -n '\''s/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'\''`; do
eval ac_val=\$$ac_var
case $ac_val in #(
*${as_nl}*)
case $ac_var in #(
*_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5
$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;;
esac
case $ac_var in #(
_ | IFS | as_nl) ;; #(
BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #(
*) { eval $ac_var=; unset $ac_var;} ;;
esac ;;
esac
done
(set) 2>&1 |
case $as_nl`(ac_space='\'' '\''; set) 2>&1` in #(
*${as_nl}ac_space=\ *)
sed -n \
"s/'\''/'\''\\\\'\'''\''/g;
s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\''\\2'\''/p"
;; #(
*)
sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
;;
esac |
sort
)
echo
$as_echo "## ----------------- ##
## Output variables. ##
## ----------------- ##"
echo
for ac_var in $ac_subst_vars
do
eval ac_val=\$$ac_var
case $ac_val in
*\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
esac
$as_echo "$ac_var='\''$ac_val'\''"
done | sort
echo
if test -n "$ac_subst_files"; then
$as_echo "## ------------------- ##
## File substitutions. ##
## ------------------- ##"
echo
for ac_var in $ac_subst_files
do
eval ac_val=\$$ac_var
case $ac_val in
*\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
esac
$as_echo "$ac_var='\''$ac_val'\''"
done | sort
echo
fi
if test -s confdefs.h; then
$as_echo "## ----------- ##
## confdefs.h. ##
## ----------- ##"
echo
cat confdefs.h
echo
fi
test "$ac_signal" != 0 &&
$as_echo "$as_me: caught signal $ac_signal"
$as_echo "$as_me: exit $exit_status"
} >&5
rm -f core *.core core.conftest.* &&
rm -f -r conftest* confdefs* conf$$* $ac_clean_files &&
exit $exit_status
' 0
for ac_signal in 1 2 13 15; do
trap 'ac_signal='$ac_signal'; as_fn_exit 1' $ac_signal
done
ac_signal=0
# confdefs.h avoids OS command line length limits that DEFS can exceed.
rm -f -r conftest* confdefs.h
$as_echo "/* confdefs.h */" > confdefs.h
# Predefined preprocessor variables.
cat >>confdefs.h <<_ACEOF
#define PACKAGE_NAME "$PACKAGE_NAME"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_TARNAME "$PACKAGE_TARNAME"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_VERSION "$PACKAGE_VERSION"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_STRING "$PACKAGE_STRING"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_BUGREPORT "$PACKAGE_BUGREPORT"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_URL "$PACKAGE_URL"
_ACEOF
# Let the site file select an alternate cache file if it wants to.
# Prefer an explicitly selected file to automatically selected ones.
ac_site_file1=NONE
ac_site_file2=NONE
if test -n "$CONFIG_SITE"; then
# We do not want a PATH search for config.site.
case $CONFIG_SITE in #((
-*) ac_site_file1=./$CONFIG_SITE;;
*/*) ac_site_file1=$CONFIG_SITE;;
*) ac_site_file1=./$CONFIG_SITE;;
esac
elif test "x$prefix" != xNONE; then
ac_site_file1=$prefix/share/config.site
ac_site_file2=$prefix/etc/config.site
else
ac_site_file1=$ac_default_prefix/share/config.site
ac_site_file2=$ac_default_prefix/etc/config.site
fi
for ac_site_file in "$ac_site_file1" "$ac_site_file2"
do
test "x$ac_site_file" = xNONE && continue
if test /dev/null != "$ac_site_file" && test -r "$ac_site_file"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: loading site script $ac_site_file" >&5
$as_echo "$as_me: loading site script $ac_site_file" >&6;}
sed 's/^/| /' "$ac_site_file" >&5
. "$ac_site_file" \
|| { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "failed to load site script $ac_site_file
See \`config.log' for more details" "$LINENO" 5; }
fi
done
if test -r "$cache_file"; then
# Some versions of bash will fail to source /dev/null (special files
# actually), so we avoid doing that. DJGPP emulates it as a regular file.
if test /dev/null != "$cache_file" && test -f "$cache_file"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: loading cache $cache_file" >&5
$as_echo "$as_me: loading cache $cache_file" >&6;}
case $cache_file in
[\\/]* | ?:[\\/]* ) . "$cache_file";;
*) . "./$cache_file";;
esac
fi
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: creating cache $cache_file" >&5
$as_echo "$as_me: creating cache $cache_file" >&6;}
>$cache_file
fi
# Check that the precious variables saved in the cache have kept the same
# value.
ac_cache_corrupted=false
for ac_var in $ac_precious_vars; do
eval ac_old_set=\$ac_cv_env_${ac_var}_set
eval ac_new_set=\$ac_env_${ac_var}_set
eval ac_old_val=\$ac_cv_env_${ac_var}_value
eval ac_new_val=\$ac_env_${ac_var}_value
case $ac_old_set,$ac_new_set in
set,)
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5
$as_echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;}
ac_cache_corrupted=: ;;
,set)
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was not set in the previous run" >&5
$as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;}
ac_cache_corrupted=: ;;
,);;
*)
if test "x$ac_old_val" != "x$ac_new_val"; then
# differences in whitespace do not lead to failure.
ac_old_val_w=`echo x $ac_old_val`
ac_new_val_w=`echo x $ac_new_val`
if test "$ac_old_val_w" != "$ac_new_val_w"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' has changed since the previous run:" >&5
$as_echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;}
ac_cache_corrupted=:
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&5
$as_echo "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;}
eval $ac_var=\$ac_old_val
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: former value: \`$ac_old_val'" >&5
$as_echo "$as_me: former value: \`$ac_old_val'" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: current value: \`$ac_new_val'" >&5
$as_echo "$as_me: current value: \`$ac_new_val'" >&2;}
fi;;
esac
# Pass precious variables to config.status.
if test "$ac_new_set" = set; then
case $ac_new_val in
*\'*) ac_arg=$ac_var=`$as_echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;;
*) ac_arg=$ac_var=$ac_new_val ;;
esac
case " $ac_configure_args " in
*" '$ac_arg' "*) ;; # Avoid dups. Use of quotes ensures accuracy.
*) as_fn_append ac_configure_args " '$ac_arg'" ;;
esac
fi
done
if $ac_cache_corrupted; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: changes in the environment can compromise the build" >&5
$as_echo "$as_me: error: changes in the environment can compromise the build" >&2;}
as_fn_error $? "run \`make distclean' and/or \`rm $cache_file' and start over" "$LINENO" 5
fi
## -------------------- ##
## Main body of script. ##
## -------------------- ##
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
test "$program_prefix" != NONE &&
program_transform_name="s&^&$program_prefix&;$program_transform_name"
# Use a double $ so make ignores it.
test "$program_suffix" != NONE &&
program_transform_name="s&\$&$program_suffix&;$program_transform_name"
# Double any \ or $.
# By default was `s,x,x', remove it if useless.
ac_script='s/[\\$]/&&/g;s/;s,x,x,$//'
program_transform_name=`$as_echo "$program_transform_name" | sed "$ac_script"`
saveCFLAGS=$CFLAGS
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
if test -n "$ac_tool_prefix"; then
for ac_prog in gcc cc egcs cl.exe
do
# Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args.
set dummy $ac_tool_prefix$ac_prog; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_CC+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$CC"; then
ac_cv_prog_CC="$CC" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_CC="$ac_tool_prefix$ac_prog"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
CC=$ac_cv_prog_CC
if test -n "$CC"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
$as_echo "$CC" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
test -n "$CC" && break
done
fi
if test -z "$CC"; then
ac_ct_CC=$CC
for ac_prog in gcc cc egcs cl.exe
do
# Extract the first word of "$ac_prog", so it can be a program name with args.
set dummy $ac_prog; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_ac_ct_CC+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$ac_ct_CC"; then
ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_ac_ct_CC="$ac_prog"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
ac_ct_CC=$ac_cv_prog_ac_ct_CC
if test -n "$ac_ct_CC"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_CC" >&5
$as_echo "$ac_ct_CC" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
test -n "$ac_ct_CC" && break
done
if test "x$ac_ct_CC" = x; then
CC=""
else
case $cross_compiling:$ac_tool_warned in
yes:)
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
ac_tool_warned=yes ;;
esac
CC=$ac_ct_CC
fi
fi
test -z "$CC" && { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "no acceptable C compiler found in \$PATH
See \`config.log' for more details" "$LINENO" 5; }
# Provide some information about the compiler.
$as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler version" >&5
set X $ac_compile
ac_compiler=$2
for ac_option in --version -v -V -qversion; do
{ { ac_try="$ac_compiler $ac_option >&5"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_compiler $ac_option >&5") 2>conftest.err
ac_status=$?
if test -s conftest.err; then
sed '10a\
... rest of stderr output deleted ...
10q' conftest.err >conftest.er1
cat conftest.er1 >&5
fi
rm -f conftest.er1 conftest.err
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }
done
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
_ACEOF
ac_clean_files_save=$ac_clean_files
ac_clean_files="$ac_clean_files a.out a.out.dSYM a.exe b.out"
# Try to create an executable without -o first, disregard a.out.
# It will help us diagnose broken compilers, and finding out an intuition
# of exeext.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the C compiler works" >&5
$as_echo_n "checking whether the C compiler works... " >&6; }
ac_link_default=`$as_echo "$ac_link" | sed 's/ -o *conftest[^ ]*//'`
# The possible output files:
ac_files="a.out conftest.exe conftest a.exe a_out.exe b.out conftest.*"
ac_rmfiles=
for ac_file in $ac_files
do
case $ac_file in
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;;
* ) ac_rmfiles="$ac_rmfiles $ac_file";;
esac
done
rm -f $ac_rmfiles
if { { ac_try="$ac_link_default"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link_default") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; then :
# Autoconf-2.13 could set the ac_cv_exeext variable to `no'.
# So ignore a value of `no', otherwise this would lead to `EXEEXT = no'
# in a Makefile. We should not override ac_cv_exeext if it was cached,
# so that the user can short-circuit this test for compilers unknown to
# Autoconf.
for ac_file in $ac_files ''
do
test -f "$ac_file" || continue
case $ac_file in
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj )
;;
[ab].out )
# We found the default executable, but exeext='' is most
# certainly right.
break;;
*.* )
if test "${ac_cv_exeext+set}" = set && test "$ac_cv_exeext" != no;
then :; else
ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
fi
# We set ac_cv_exeext here because the later test for it is not
# safe: cross compilers may not add the suffix if given an `-o'
# argument, so we may need to know it at that point already.
# Even if this section looks crufty: it has the advantage of
# actually working.
break;;
* )
break;;
esac
done
test "$ac_cv_exeext" = no && ac_cv_exeext=
else
ac_file=''
fi
if test -z "$ac_file"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error 77 "C compiler cannot create executables
See \`config.log' for more details" "$LINENO" 5; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler default output file name" >&5
$as_echo_n "checking for C compiler default output file name... " >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_file" >&5
$as_echo "$ac_file" >&6; }
ac_exeext=$ac_cv_exeext
rm -f -r a.out a.out.dSYM a.exe conftest$ac_cv_exeext b.out
ac_clean_files=$ac_clean_files_save
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for suffix of executables" >&5
$as_echo_n "checking for suffix of executables... " >&6; }
if { { ac_try="$ac_link"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; then :
# If both `conftest.exe' and `conftest' are `present' (well, observable)
# catch `conftest.exe'. For instance with Cygwin, `ls conftest' will
# work properly (i.e., refer to `conftest.exe'), while it won't with
# `rm'.
for ac_file in conftest.exe conftest conftest.*; do
test -f "$ac_file" || continue
case $ac_file in
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;;
*.* ) ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
break;;
* ) break;;
esac
done
else
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "cannot compute suffix of executables: cannot compile and link
See \`config.log' for more details" "$LINENO" 5; }
fi
rm -f conftest conftest$ac_cv_exeext
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_exeext" >&5
$as_echo "$ac_cv_exeext" >&6; }
rm -f conftest.$ac_ext
EXEEXT=$ac_cv_exeext
ac_exeext=$EXEEXT
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
int
main ()
{
FILE *f = fopen ("conftest.out", "w");
return ferror (f) || fclose (f) != 0;
;
return 0;
}
_ACEOF
ac_clean_files="$ac_clean_files conftest.out"
# Check that the compiler produces executables we can run. If not, either
# the compiler is broken, or we cross compile.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are cross compiling" >&5
$as_echo_n "checking whether we are cross compiling... " >&6; }
if test "$cross_compiling" != yes; then
{ { ac_try="$ac_link"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }
if { ac_try='./conftest$ac_cv_exeext'
{ { case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_try") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; }; then
cross_compiling=no
else
if test "$cross_compiling" = maybe; then
cross_compiling=yes
else
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "cannot run C compiled programs.
If you meant to cross compile, use \`--host'.
See \`config.log' for more details" "$LINENO" 5; }
fi
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $cross_compiling" >&5
$as_echo "$cross_compiling" >&6; }
rm -f conftest.$ac_ext conftest$ac_cv_exeext conftest.out
ac_clean_files=$ac_clean_files_save
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for suffix of object files" >&5
$as_echo_n "checking for suffix of object files... " >&6; }
if ${ac_cv_objext+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
_ACEOF
rm -f conftest.o conftest.obj
if { { ac_try="$ac_compile"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_compile") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; then :
for ac_file in conftest.o conftest.obj conftest.*; do
test -f "$ac_file" || continue;
case $ac_file in
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM ) ;;
*) ac_cv_objext=`expr "$ac_file" : '.*\.\(.*\)'`
break;;
esac
done
else
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "cannot compute suffix of object files: cannot compile
See \`config.log' for more details" "$LINENO" 5; }
fi
rm -f conftest.$ac_cv_objext conftest.$ac_ext
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_objext" >&5
$as_echo "$ac_cv_objext" >&6; }
OBJEXT=$ac_cv_objext
ac_objext=$OBJEXT
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are using the GNU C compiler" >&5
$as_echo_n "checking whether we are using the GNU C compiler... " >&6; }
if ${ac_cv_c_compiler_gnu+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
#ifndef __GNUC__
choke me
#endif
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
ac_compiler_gnu=yes
else
ac_compiler_gnu=no
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
ac_cv_c_compiler_gnu=$ac_compiler_gnu
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_c_compiler_gnu" >&5
$as_echo "$ac_cv_c_compiler_gnu" >&6; }
if test $ac_compiler_gnu = yes; then
GCC=yes
else
GCC=
fi
ac_test_CFLAGS=${CFLAGS+set}
ac_save_CFLAGS=$CFLAGS
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CC accepts -g" >&5
$as_echo_n "checking whether $CC accepts -g... " >&6; }
if ${ac_cv_prog_cc_g+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_save_c_werror_flag=$ac_c_werror_flag
ac_c_werror_flag=yes
ac_cv_prog_cc_g=no
CFLAGS="-g"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
ac_cv_prog_cc_g=yes
else
CFLAGS=""
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
else
ac_c_werror_flag=$ac_save_c_werror_flag
CFLAGS="-g"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
ac_cv_prog_cc_g=yes
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
ac_c_werror_flag=$ac_save_c_werror_flag
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_g" >&5
$as_echo "$ac_cv_prog_cc_g" >&6; }
if test "$ac_test_CFLAGS" = set; then
CFLAGS=$ac_save_CFLAGS
elif test $ac_cv_prog_cc_g = yes; then
if test "$GCC" = yes; then
CFLAGS="-g -O2"
else
CFLAGS="-g"
fi
else
if test "$GCC" = yes; then
CFLAGS="-O2"
else
CFLAGS=
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $CC option to accept ISO C89" >&5
$as_echo_n "checking for $CC option to accept ISO C89... " >&6; }
if ${ac_cv_prog_cc_c89+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_cv_prog_cc_c89=no
ac_save_CC=$CC
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
#include
struct stat;
/* Most of the following tests are stolen from RCS 5.7's src/conf.sh. */
struct buf { int x; };
FILE * (*rcsopen) (struct buf *, struct stat *, int);
static char *e (p, i)
char **p;
int i;
{
return p[i];
}
static char *f (char * (*g) (char **, int), char **p, ...)
{
char *s;
va_list v;
va_start (v,p);
s = g (p, va_arg (v,int));
va_end (v);
return s;
}
/* OSF 4.0 Compaq cc is some sort of almost-ANSI by default. It has
function prototypes and stuff, but not '\xHH' hex character constants.
These don't provoke an error unfortunately, instead are silently treated
as 'x'. The following induces an error, until -std is added to get
proper ANSI mode. Curiously '\x00'!='x' always comes out true, for an
array size at least. It's necessary to write '\x00'==0 to get something
that's true only with -std. */
int osf4_cc_array ['\x00' == 0 ? 1 : -1];
/* IBM C 6 for AIX is almost-ANSI by default, but it replaces macro parameters
inside strings and character constants. */
#define FOO(x) 'x'
int xlc6_cc_array[FOO(a) == 'x' ? 1 : -1];
int test (int i, double x);
struct s1 {int (*f) (int a);};
struct s2 {int (*f) (double a);};
int pairnames (int, char **, FILE *(*)(struct buf *, struct stat *, int), int, int);
int argc;
char **argv;
int
main ()
{
return f (e, argv, 0) != argv[0] || f (e, argv, 1) != argv[1];
;
return 0;
}
_ACEOF
for ac_arg in '' -qlanglvl=extc89 -qlanglvl=ansi -std \
-Ae "-Aa -D_HPUX_SOURCE" "-Xc -D__EXTENSIONS__"
do
CC="$ac_save_CC $ac_arg"
if ac_fn_c_try_compile "$LINENO"; then :
ac_cv_prog_cc_c89=$ac_arg
fi
rm -f core conftest.err conftest.$ac_objext
test "x$ac_cv_prog_cc_c89" != "xno" && break
done
rm -f conftest.$ac_ext
CC=$ac_save_CC
fi
# AC_CACHE_VAL
case "x$ac_cv_prog_cc_c89" in
x)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: none needed" >&5
$as_echo "none needed" >&6; } ;;
xno)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5
$as_echo "unsupported" >&6; } ;;
*)
CC="$CC $ac_cv_prog_cc_c89"
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c89" >&5
$as_echo "$ac_cv_prog_cc_c89" >&6; } ;;
esac
if test "x$ac_cv_prog_cc_c89" != xno; then :
fi
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $CC option to accept ISO C99" >&5
$as_echo_n "checking for $CC option to accept ISO C99... " >&6; }
if ${ac_cv_prog_cc_c99+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_cv_prog_cc_c99=no
ac_save_CC=$CC
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
#include
#include
#include
#include
// Check varargs macros. These examples are taken from C99 6.10.3.5.
#define debug(...) fprintf (stderr, __VA_ARGS__)
#define showlist(...) puts (#__VA_ARGS__)
#define report(test,...) ((test) ? puts (#test) : printf (__VA_ARGS__))
static void
test_varargs_macros (void)
{
int x = 1234;
int y = 5678;
debug ("Flag");
debug ("X = %d\n", x);
showlist (The first, second, and third items.);
report (x>y, "x is %d but y is %d", x, y);
}
// Check long long types.
#define BIG64 18446744073709551615ull
#define BIG32 4294967295ul
#define BIG_OK (BIG64 / BIG32 == 4294967297ull && BIG64 % BIG32 == 0)
#if !BIG_OK
your preprocessor is broken;
#endif
#if BIG_OK
#else
your preprocessor is broken;
#endif
static long long int bignum = -9223372036854775807LL;
static unsigned long long int ubignum = BIG64;
struct incomplete_array
{
int datasize;
double data[];
};
struct named_init {
int number;
const wchar_t *name;
double average;
};
typedef const char *ccp;
static inline int
test_restrict (ccp restrict text)
{
// See if C++-style comments work.
// Iterate through items via the restricted pointer.
// Also check for declarations in for loops.
for (unsigned int i = 0; *(text+i) != '\0'; ++i)
continue;
return 0;
}
// Check varargs and va_copy.
static void
test_varargs (const char *format, ...)
{
va_list args;
va_start (args, format);
va_list args_copy;
va_copy (args_copy, args);
const char *str;
int number;
float fnumber;
while (*format)
{
switch (*format++)
{
case 's': // string
str = va_arg (args_copy, const char *);
break;
case 'd': // int
number = va_arg (args_copy, int);
break;
case 'f': // float
fnumber = va_arg (args_copy, double);
break;
default:
break;
}
}
va_end (args_copy);
va_end (args);
}
int
main ()
{
// Check bool.
_Bool success = false;
// Check restrict.
if (test_restrict ("String literal") == 0)
success = true;
char *restrict newvar = "Another string";
// Check varargs.
test_varargs ("s, d' f .", "string", 65, 34.234);
test_varargs_macros ();
// Check flexible array members.
struct incomplete_array *ia =
malloc (sizeof (struct incomplete_array) + (sizeof (double) * 10));
ia->datasize = 10;
for (int i = 0; i < ia->datasize; ++i)
ia->data[i] = i * 1.234;
// Check named initializers.
struct named_init ni = {
.number = 34,
.name = L"Test wide string",
.average = 543.34343,
};
ni.number = 58;
int dynamic_array[ni.number];
dynamic_array[ni.number - 1] = 543;
// work around unused variable warnings
return (!success || bignum == 0LL || ubignum == 0uLL || newvar[0] == 'x'
|| dynamic_array[ni.number - 1] != 543);
;
return 0;
}
_ACEOF
for ac_arg in '' -std=gnu99 -std=c99 -c99 -AC99 -D_STDC_C99= -qlanglvl=extc99
do
CC="$ac_save_CC $ac_arg"
if ac_fn_c_try_compile "$LINENO"; then :
ac_cv_prog_cc_c99=$ac_arg
fi
rm -f core conftest.err conftest.$ac_objext
test "x$ac_cv_prog_cc_c99" != "xno" && break
done
rm -f conftest.$ac_ext
CC=$ac_save_CC
fi
# AC_CACHE_VAL
case "x$ac_cv_prog_cc_c99" in
x)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: none needed" >&5
$as_echo "none needed" >&6; } ;;
xno)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5
$as_echo "unsupported" >&6; } ;;
*)
CC="$CC $ac_cv_prog_cc_c99"
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c99" >&5
$as_echo "$ac_cv_prog_cc_c99" >&6; } ;;
esac
if test "x$ac_cv_prog_cc_c99" != xno; then :
fi
if test "$CC" = cl.exe -a -z "$saveCFLAGS" ; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: setting special CFLAGS value for cl" >&5
$as_echo "$as_me: setting special CFLAGS value for cl" >&6;}
CFLAGS="-O2 -W3 -nologo"
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for an ANSI C-conforming const" >&5
$as_echo_n "checking for an ANSI C-conforming const... " >&6; }
if ${ac_cv_c_const+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
#ifndef __cplusplus
/* Ultrix mips cc rejects this sort of thing. */
typedef int charset[2];
const charset cs = { 0, 0 };
/* SunOS 4.1.1 cc rejects this. */
char const *const *pcpcc;
char **ppc;
/* NEC SVR4.0.2 mips cc rejects this. */
struct point {int x, y;};
static struct point const zero = {0,0};
/* AIX XL C 1.02.0.0 rejects this.
It does not let you subtract one const X* pointer from another in
an arm of an if-expression whose if-part is not a constant
expression */
const char *g = "string";
pcpcc = &g + (g ? g-g : 0);
/* HPUX 7.0 cc rejects these. */
++pcpcc;
ppc = (char**) pcpcc;
pcpcc = (char const *const *) ppc;
{ /* SCO 3.2v4 cc rejects this sort of thing. */
char tx;
char *t = &tx;
char const *s = 0 ? (char *) 0 : (char const *) 0;
*t++ = 0;
if (s) return 0;
}
{ /* Someone thinks the Sun supposedly-ANSI compiler will reject this. */
int x[] = {25, 17};
const int *foo = &x[0];
++foo;
}
{ /* Sun SC1.0 ANSI compiler rejects this -- but not the above. */
typedef const int *iptr;
iptr p = 0;
++p;
}
{ /* AIX XL C 1.02.0.0 rejects this sort of thing, saying
"k.c", line 2.27: 1506-025 (S) Operand must be a modifiable lvalue. */
struct s { int j; const int *ap[3]; } bx;
struct s *b = &bx; b->j = 5;
}
{ /* ULTRIX-32 V3.1 (Rev 9) vcc rejects this */
const int foo = 10;
if (!foo) return 0;
}
return !cs[0] && !zero.x;
#endif
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
ac_cv_c_const=yes
else
ac_cv_c_const=no
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_c_const" >&5
$as_echo "$ac_cv_c_const" >&6; }
if test $ac_cv_c_const = no; then
$as_echo "#define const /**/" >>confdefs.h
fi
ac_aux_dir=
for ac_dir in "$srcdir" "$srcdir/.." "$srcdir/../.."; do
if test -f "$ac_dir/install-sh"; then
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/install-sh -c"
break
elif test -f "$ac_dir/install.sh"; then
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/install.sh -c"
break
elif test -f "$ac_dir/shtool"; then
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/shtool install -c"
break
fi
done
if test -z "$ac_aux_dir"; then
as_fn_error $? "cannot find install-sh, install.sh, or shtool in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" "$LINENO" 5
fi
# These three variables are undocumented and unsupported,
# and are intended to be withdrawn in a future Autoconf release.
# They can cause serious problems if a builder's source tree is in a directory
# whose full name contains unusual characters.
ac_config_guess="$SHELL $ac_aux_dir/config.guess" # Please don't use this var.
ac_config_sub="$SHELL $ac_aux_dir/config.sub" # Please don't use this var.
ac_configure="$SHELL $ac_aux_dir/configure" # Please don't use this var.
# Find a good install program. We prefer a C program (faster),
# so one script is as good as another. But avoid the broken or
# incompatible versions:
# SysV /etc/install, /usr/sbin/install
# SunOS /usr/etc/install
# IRIX /sbin/install
# AIX /bin/install
# AmigaOS /C/install, which installs bootblocks on floppy discs
# AIX 4 /usr/bin/installbsd, which doesn't work without a -g flag
# AFS /usr/afsws/bin/install, which mishandles nonexistent args
# SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff"
# OS/2's system install, which has a completely different semantic
# ./install, which can be erroneously created by make from ./install.sh.
# Reject install programs that cannot install multiple files.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for a BSD-compatible install" >&5
$as_echo_n "checking for a BSD-compatible install... " >&6; }
if test -z "$INSTALL"; then
if ${ac_cv_path_install+:} false; then :
$as_echo_n "(cached) " >&6
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
# Account for people who put trailing slashes in PATH elements.
case $as_dir/ in #((
./ | .// | /[cC]/* | \
/etc/* | /usr/sbin/* | /usr/etc/* | /sbin/* | /usr/afsws/bin/* | \
?:[\\/]os2[\\/]install[\\/]* | ?:[\\/]OS2[\\/]INSTALL[\\/]* | \
/usr/ucb/* ) ;;
*)
# OSF1 and SCO ODT 3.0 have their own names for install.
# Don't use installbsd from OSF since it installs stuff as root
# by default.
for ac_prog in ginstall scoinst install; do
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_prog$ac_exec_ext"; then
if test $ac_prog = install &&
grep dspmsg "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then
# AIX install. It has an incompatible calling convention.
:
elif test $ac_prog = install &&
grep pwplus "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then
# program-specific install script used by HP pwplus--don't use.
:
else
rm -rf conftest.one conftest.two conftest.dir
echo one > conftest.one
echo two > conftest.two
mkdir conftest.dir
if "$as_dir/$ac_prog$ac_exec_ext" -c conftest.one conftest.two "`pwd`/conftest.dir" &&
test -s conftest.one && test -s conftest.two &&
test -s conftest.dir/conftest.one &&
test -s conftest.dir/conftest.two
then
ac_cv_path_install="$as_dir/$ac_prog$ac_exec_ext -c"
break 3
fi
fi
fi
done
done
;;
esac
done
IFS=$as_save_IFS
rm -rf conftest.one conftest.two conftest.dir
fi
if test "${ac_cv_path_install+set}" = set; then
INSTALL=$ac_cv_path_install
else
# As a last resort, use the slow shell script. Don't cache a
# value for INSTALL within a source directory, because that will
# break other packages using the cache if that directory is
# removed, or if the value is a relative name.
INSTALL=$ac_install_sh
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $INSTALL" >&5
$as_echo "$INSTALL" >&6; }
# Use test -z because SunOS4 sh mishandles braces in ${var-val}.
# It thinks the first close brace ends the variable substitution.
test -z "$INSTALL_PROGRAM" && INSTALL_PROGRAM='${INSTALL}'
test -z "$INSTALL_SCRIPT" && INSTALL_SCRIPT='${INSTALL}'
test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644'
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for a thread-safe mkdir -p" >&5
$as_echo_n "checking for a thread-safe mkdir -p... " >&6; }
if test -z "$MKDIR_P"; then
if ${ac_cv_path_mkdir+:} false; then :
$as_echo_n "(cached) " >&6
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH$PATH_SEPARATOR/opt/sfw/bin
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_prog in mkdir gmkdir; do
for ac_exec_ext in '' $ac_executable_extensions; do
as_fn_executable_p "$as_dir/$ac_prog$ac_exec_ext" || continue
case `"$as_dir/$ac_prog$ac_exec_ext" --version 2>&1` in #(
'mkdir (GNU coreutils) '* | \
'mkdir (coreutils) '* | \
'mkdir (fileutils) '4.1*)
ac_cv_path_mkdir=$as_dir/$ac_prog$ac_exec_ext
break 3;;
esac
done
done
done
IFS=$as_save_IFS
fi
test -d ./--version && rmdir ./--version
if test "${ac_cv_path_mkdir+set}" = set; then
MKDIR_P="$ac_cv_path_mkdir -p"
else
# As a last resort, use the slow shell script. Don't cache a
# value for MKDIR_P within a source directory, because that will
# break other packages using the cache if that directory is
# removed, or if the value is a relative name.
MKDIR_P="$ac_install_sh -d"
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $MKDIR_P" >&5
$as_echo "$MKDIR_P" >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing sin" >&5
$as_echo_n "checking for library containing sin... " >&6; }
if ${ac_cv_search_sin+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_func_search_save_LIBS=$LIBS
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char sin ();
int
main ()
{
return sin ();
;
return 0;
}
_ACEOF
for ac_lib in '' m; do
if test -z "$ac_lib"; then
ac_res="none required"
else
ac_res=-l$ac_lib
LIBS="-l$ac_lib $ac_func_search_save_LIBS"
fi
if ac_fn_c_try_link "$LINENO"; then :
ac_cv_search_sin=$ac_res
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext
if ${ac_cv_search_sin+:} false; then :
break
fi
done
if ${ac_cv_search_sin+:} false; then :
else
ac_cv_search_sin=no
fi
rm conftest.$ac_ext
LIBS=$ac_func_search_save_LIBS
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_sin" >&5
$as_echo "$ac_cv_search_sin" >&6; }
ac_res=$ac_cv_search_sin
if test "$ac_res" != no; then :
test "$ac_res" = "none required" || LIBS="$ac_res $LIBS"
fi
{ ac_cv_lib_readline_readline=; unset ac_cv_lib_readline_readline;}
for termlib in "" -ltermcap -lncurses -lcurses; do
if test "$ac_cv_lib_readline_readline" != yes ; then
{ ac_cv_lib_readline_readline=; unset ac_cv_lib_readline_readline;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for readline in -lreadline" >&5
$as_echo_n "checking for readline in -lreadline... " >&6; }
if ${ac_cv_lib_readline_readline+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_check_lib_save_LIBS=$LIBS
LIBS="-lreadline $termlib $LIBS"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char readline ();
int
main ()
{
return readline ();
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
ac_cv_lib_readline_readline=yes
else
ac_cv_lib_readline_readline=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
LIBS=$ac_check_lib_save_LIBS
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_readline_readline" >&5
$as_echo "$ac_cv_lib_readline_readline" >&6; }
if test "x$ac_cv_lib_readline_readline" = xyes; then :
LIBS="-lreadline $termlib $LIBS";DEFIS="$DEFIS -DREADLINE"
fi
fi
done
if test "$ac_cv_lib_readline_readline" = yes; then
ac_fn_c_check_decl "$LINENO" "rl_completion_suppress_append" "ac_cv_have_decl_rl_completion_suppress_append" "#include
"
if test "x$ac_cv_have_decl_rl_completion_suppress_append" = xyes; then :
else
DEFIS="$DEFIS -DNO_SUPPRESS_APPEND"
fi
fi
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking how to run the C preprocessor" >&5
$as_echo_n "checking how to run the C preprocessor... " >&6; }
# On Suns, sometimes $CPP names a directory.
if test -n "$CPP" && test -d "$CPP"; then
CPP=
fi
if test -z "$CPP"; then
if ${ac_cv_prog_CPP+:} false; then :
$as_echo_n "(cached) " >&6
else
# Double quotes because CPP needs to be expanded
for CPP in "$CC -E" "$CC -E -traditional-cpp" "/lib/cpp"
do
ac_preproc_ok=false
for ac_c_preproc_warn_flag in '' yes
do
# Use a header file that comes with gcc, so configuring glibc
# with a fresh cross-compiler works.
# Prefer to if __STDC__ is defined, since
# exists even on freestanding compilers.
# On the NeXT, cc -E runs the code through the compiler's parser,
# not just through cpp. "Syntax error" is here to catch this case.
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#ifdef __STDC__
# include
#else
# include
#endif
Syntax error
_ACEOF
if ac_fn_c_try_cpp "$LINENO"; then :
else
# Broken: fails on valid input.
continue
fi
rm -f conftest.err conftest.i conftest.$ac_ext
# OK, works on sane cases. Now check whether nonexistent headers
# can be detected and how.
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
_ACEOF
if ac_fn_c_try_cpp "$LINENO"; then :
# Broken: success on invalid input.
continue
else
# Passes both tests.
ac_preproc_ok=:
break
fi
rm -f conftest.err conftest.i conftest.$ac_ext
done
# Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped.
rm -f conftest.i conftest.err conftest.$ac_ext
if $ac_preproc_ok; then :
break
fi
done
ac_cv_prog_CPP=$CPP
fi
CPP=$ac_cv_prog_CPP
else
ac_cv_prog_CPP=$CPP
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CPP" >&5
$as_echo "$CPP" >&6; }
ac_preproc_ok=false
for ac_c_preproc_warn_flag in '' yes
do
# Use a header file that comes with gcc, so configuring glibc
# with a fresh cross-compiler works.
# Prefer to if __STDC__ is defined, since
# exists even on freestanding compilers.
# On the NeXT, cc -E runs the code through the compiler's parser,
# not just through cpp. "Syntax error" is here to catch this case.
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#ifdef __STDC__
# include
#else
# include
#endif
Syntax error
_ACEOF
if ac_fn_c_try_cpp "$LINENO"; then :
else
# Broken: fails on valid input.
continue
fi
rm -f conftest.err conftest.i conftest.$ac_ext
# OK, works on sane cases. Now check whether nonexistent headers
# can be detected and how.
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
_ACEOF
if ac_fn_c_try_cpp "$LINENO"; then :
# Broken: success on invalid input.
continue
else
# Passes both tests.
ac_preproc_ok=:
break
fi
rm -f conftest.err conftest.i conftest.$ac_ext
done
# Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped.
rm -f conftest.i conftest.err conftest.$ac_ext
if $ac_preproc_ok; then :
else
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "C preprocessor \"$CPP\" fails sanity check
See \`config.log' for more details" "$LINENO" 5; }
fi
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for grep that handles long lines and -e" >&5
$as_echo_n "checking for grep that handles long lines and -e... " >&6; }
if ${ac_cv_path_GREP+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -z "$GREP"; then
ac_path_GREP_found=false
# Loop through the user's path and test for each of PROGNAME-LIST
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH$PATH_SEPARATOR/usr/xpg4/bin
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_prog in grep ggrep; do
for ac_exec_ext in '' $ac_executable_extensions; do
ac_path_GREP="$as_dir/$ac_prog$ac_exec_ext"
as_fn_executable_p "$ac_path_GREP" || continue
# Check for GNU ac_path_GREP and select it if it is found.
# Check for GNU $ac_path_GREP
case `"$ac_path_GREP" --version 2>&1` in
*GNU*)
ac_cv_path_GREP="$ac_path_GREP" ac_path_GREP_found=:;;
*)
ac_count=0
$as_echo_n 0123456789 >"conftest.in"
while :
do
cat "conftest.in" "conftest.in" >"conftest.tmp"
mv "conftest.tmp" "conftest.in"
cp "conftest.in" "conftest.nl"
$as_echo 'GREP' >> "conftest.nl"
"$ac_path_GREP" -e 'GREP$' -e '-(cannot match)-' < "conftest.nl" >"conftest.out" 2>/dev/null || break
diff "conftest.out" "conftest.nl" >/dev/null 2>&1 || break
as_fn_arith $ac_count + 1 && ac_count=$as_val
if test $ac_count -gt ${ac_path_GREP_max-0}; then
# Best one so far, save it but keep looking for a better one
ac_cv_path_GREP="$ac_path_GREP"
ac_path_GREP_max=$ac_count
fi
# 10*(2^10) chars as input seems more than enough
test $ac_count -gt 10 && break
done
rm -f conftest.in conftest.tmp conftest.nl conftest.out;;
esac
$ac_path_GREP_found && break 3
done
done
done
IFS=$as_save_IFS
if test -z "$ac_cv_path_GREP"; then
as_fn_error $? "no acceptable grep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5
fi
else
ac_cv_path_GREP=$GREP
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_path_GREP" >&5
$as_echo "$ac_cv_path_GREP" >&6; }
GREP="$ac_cv_path_GREP"
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for egrep" >&5
$as_echo_n "checking for egrep... " >&6; }
if ${ac_cv_path_EGREP+:} false; then :
$as_echo_n "(cached) " >&6
else
if echo a | $GREP -E '(a|b)' >/dev/null 2>&1
then ac_cv_path_EGREP="$GREP -E"
else
if test -z "$EGREP"; then
ac_path_EGREP_found=false
# Loop through the user's path and test for each of PROGNAME-LIST
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH$PATH_SEPARATOR/usr/xpg4/bin
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_prog in egrep; do
for ac_exec_ext in '' $ac_executable_extensions; do
ac_path_EGREP="$as_dir/$ac_prog$ac_exec_ext"
as_fn_executable_p "$ac_path_EGREP" || continue
# Check for GNU ac_path_EGREP and select it if it is found.
# Check for GNU $ac_path_EGREP
case `"$ac_path_EGREP" --version 2>&1` in
*GNU*)
ac_cv_path_EGREP="$ac_path_EGREP" ac_path_EGREP_found=:;;
*)
ac_count=0
$as_echo_n 0123456789 >"conftest.in"
while :
do
cat "conftest.in" "conftest.in" >"conftest.tmp"
mv "conftest.tmp" "conftest.in"
cp "conftest.in" "conftest.nl"
$as_echo 'EGREP' >> "conftest.nl"
"$ac_path_EGREP" 'EGREP$' < "conftest.nl" >"conftest.out" 2>/dev/null || break
diff "conftest.out" "conftest.nl" >/dev/null 2>&1 || break
as_fn_arith $ac_count + 1 && ac_count=$as_val
if test $ac_count -gt ${ac_path_EGREP_max-0}; then
# Best one so far, save it but keep looking for a better one
ac_cv_path_EGREP="$ac_path_EGREP"
ac_path_EGREP_max=$ac_count
fi
# 10*(2^10) chars as input seems more than enough
test $ac_count -gt 10 && break
done
rm -f conftest.in conftest.tmp conftest.nl conftest.out;;
esac
$ac_path_EGREP_found && break 3
done
done
done
IFS=$as_save_IFS
if test -z "$ac_cv_path_EGREP"; then
as_fn_error $? "no acceptable egrep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5
fi
else
ac_cv_path_EGREP=$EGREP
fi
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_path_EGREP" >&5
$as_echo "$ac_cv_path_EGREP" >&6; }
EGREP="$ac_cv_path_EGREP"
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for ANSI C header files" >&5
$as_echo_n "checking for ANSI C header files... " >&6; }
if ${ac_cv_header_stdc+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
#include
#include
#include
int
main ()
{
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
ac_cv_header_stdc=yes
else
ac_cv_header_stdc=no
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
if test $ac_cv_header_stdc = yes; then
# SunOS 4.x string.h does not declare mem*, contrary to ANSI.
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
_ACEOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
$EGREP "memchr" >/dev/null 2>&1; then :
else
ac_cv_header_stdc=no
fi
rm -f conftest*
fi
if test $ac_cv_header_stdc = yes; then
# ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
_ACEOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
$EGREP "free" >/dev/null 2>&1; then :
else
ac_cv_header_stdc=no
fi
rm -f conftest*
fi
if test $ac_cv_header_stdc = yes; then
# /bin/cc in Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi.
if test "$cross_compiling" = yes; then :
:
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
#include
#if ((' ' & 0x0FF) == 0x020)
# define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
# define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c))
#else
# define ISLOWER(c) \
(('a' <= (c) && (c) <= 'i') \
|| ('j' <= (c) && (c) <= 'r') \
|| ('s' <= (c) && (c) <= 'z'))
# define TOUPPER(c) (ISLOWER(c) ? ((c) | 0x40) : (c))
#endif
#define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
int
main ()
{
int i;
for (i = 0; i < 256; i++)
if (XOR (islower (i), ISLOWER (i))
|| toupper (i) != TOUPPER (i))
return 2;
return 0;
}
_ACEOF
if ac_fn_c_try_run "$LINENO"; then :
else
ac_cv_header_stdc=no
fi
rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
conftest.$ac_objext conftest.beam conftest.$ac_ext
fi
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_header_stdc" >&5
$as_echo "$ac_cv_header_stdc" >&6; }
if test $ac_cv_header_stdc = yes; then
$as_echo "#define STDC_HEADERS 1" >>confdefs.h
fi
# On IRIX 5.3, sys/types and inttypes.h are conflicting.
for ac_header in sys/types.h sys/stat.h stdlib.h string.h memory.h strings.h \
inttypes.h stdint.h unistd.h
do :
as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh`
ac_fn_c_check_header_compile "$LINENO" "$ac_header" "$as_ac_Header" "$ac_includes_default
"
if eval test \"x\$"$as_ac_Header"\" = x"yes"; then :
cat >>confdefs.h <<_ACEOF
#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1
_ACEOF
fi
done
ac_fn_c_check_header_mongrel "$LINENO" "string.h" "ac_cv_header_string_h" "$ac_includes_default"
if test "x$ac_cv_header_string_h" = xyes; then :
else
DEFIS="$DEFIS -DSTRINGS_H"
fi
ac_fn_c_check_header_mongrel "$LINENO" "stdlib.h" "ac_cv_header_stdlib_h" "$ac_includes_default"
if test "x$ac_cv_header_stdlib_h" = xyes; then :
else
DEFIS="$DEFIS -DNO_STDLIB_H"
fi
ac_fn_c_check_func "$LINENO" "strchr" "ac_cv_func_strchr"
if test "x$ac_cv_func_strchr" = xyes; then :
else
DEFIS="$DEFIS -DNO_STRCHR"
fi
ac_fn_c_check_func "$LINENO" "strspn" "ac_cv_func_strspn"
if test "x$ac_cv_func_strspn" = xyes; then :
else
DEFIS="$DEFIS -DNO_STRSPN";STRFUNC="strfunc.$OBJEXT"
fi
ac_fn_c_check_func "$LINENO" "strtok" "ac_cv_func_strtok"
if test "x$ac_cv_func_strtok" = xyes; then :
else
DEFIS="$DEFIS -DNO_STRTOK";STRFUNC="strfunc.$OBJEXT"
fi
ac_fn_c_check_func "$LINENO" "setenv" "ac_cv_func_setenv"
if test "x$ac_cv_func_setenv" = xyes; then :
else
DEFIS="$DEFIS -DNO_SETENV"
fi
ac_fn_c_check_func "$LINENO" "setlocale" "ac_cv_func_setlocale"
if test "x$ac_cv_func_setlocale" = xyes; then :
else
DEFIS="$DEFIS -DNO_SETLOCALE"
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for locale and UTF-8 support" >&5
$as_echo_n "checking for locale and UTF-8 support... " >&6; }
if ${am_cv_utf8+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#define _XOPEN_SOURCE 600
#include
#include
#include
int
main ()
{
wchar_t *out;char *in;char *res;
res=setlocale(LC_CTYPE,"");res=in;
mbsrtowcs(out, &res, 2, NULL);
wcswidth(out,2);
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
am_cv_utf8=yes
else
am_cv_utf8=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_utf8" >&5
$as_echo "$am_cv_utf8" >&6; }
if test $am_cv_utf8 = yes; then
DEFIS="$DEFIS -DSUPPORT_UTF8"
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for isfinite" >&5
$as_echo_n "checking for isfinite... " >&6; }
if ${am_cv_isfinite+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#define _XOPEN_SOURCE 600
#include
int
main ()
{
float a;a=1;isfinite(a);
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
am_cv_isfinite=yes
else
am_cv_isfinite=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_isfinite" >&5
$as_echo "$am_cv_isfinite" >&6; }
if test $am_cv_isfinite = no; then
DEFIS="$DEFIS -DNO_ISFINITE"
fi
# Extract the first word of "mksinfo", so it can be a program name with args.
set dummy mksinfo; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_mkstoolkit+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$mkstoolkit"; then
ac_cv_prog_mkstoolkit="$mkstoolkit" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_mkstoolkit="found"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
test -z "$ac_cv_prog_mkstoolkit" && ac_cv_prog_mkstoolkit="no"
fi
fi
mkstoolkit=$ac_cv_prog_mkstoolkit
if test -n "$mkstoolkit"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $mkstoolkit" >&5
$as_echo "$mkstoolkit" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
if test $mkstoolkit = found; then
if mksinfo > /dev/null; then
DEFIS="$DEFIS -DHAVE_MKS_TOOLKIT"
echo 'using MKS Toolkit'
MKSFIX=".POSIX:"
else
echo 'mksinfo failed... not using MKS Toolkit'
fi
fi
# Extract the first word of "python", so it can be a program name with args.
set dummy python; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_PYTHON+:} false; then :
$as_echo_n "(cached) " >&6
else
case $PYTHON in
[\\/]* | ?:[\\/]*)
ac_cv_path_PYTHON="$PYTHON" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_PYTHON="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
test -z "$ac_cv_path_PYTHON" && ac_cv_path_PYTHON="no"
;;
esac
fi
PYTHON=$ac_cv_path_PYTHON
if test -n "$PYTHON"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $PYTHON" >&5
$as_echo "$PYTHON" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
if test $PYTHON = no; then
HAVE_PYTHON=no
echo ' Units will work without python but the currency update'
echo ' script, units_cur, will not be installed'
PYTHON=''
else
HAVE_PYTHON=yes
fi
# Check whether --enable-relocation was given.
if test "${enable_relocation+set}" = set; then :
enableval=$enable_relocation; if test $enable_relocation = yes ;then
UDAT=""
echo relocation enabled
else
UDAT="$datadir/units/"
echo relocation disabled
fi
else
UDAT="$datadir/units/"
fi
ac_config_files="$ac_config_files Makefile"
cat >confcache <<\_ACEOF
# This file is a shell script that caches the results of configure
# tests run on this system so they can be shared between configure
# scripts and configure runs, see configure's option --config-cache.
# It is not useful on other systems. If it contains results you don't
# want to keep, you may remove or edit it.
#
# config.status only pays attention to the cache file if you give it
# the --recheck option to rerun configure.
#
# `ac_cv_env_foo' variables (set or unset) will be overridden when
# loading this file, other *unset* `ac_cv_foo' will be assigned the
# following values.
_ACEOF
# The following way of writing the cache mishandles newlines in values,
# but we know of no workaround that is simple, portable, and efficient.
# So, we kill variables containing newlines.
# Ultrix sh set writes to stderr and can't be redirected directly,
# and sets the high bit in the cache file unless we assign to the vars.
(
for ac_var in `(set) 2>&1 | sed -n 's/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'`; do
eval ac_val=\$$ac_var
case $ac_val in #(
*${as_nl}*)
case $ac_var in #(
*_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5
$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;;
esac
case $ac_var in #(
_ | IFS | as_nl) ;; #(
BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #(
*) { eval $ac_var=; unset $ac_var;} ;;
esac ;;
esac
done
(set) 2>&1 |
case $as_nl`(ac_space=' '; set) 2>&1` in #(
*${as_nl}ac_space=\ *)
# `set' does not quote correctly, so add quotes: double-quote
# substitution turns \\\\ into \\, and sed turns \\ into \.
sed -n \
"s/'/'\\\\''/g;
s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\\2'/p"
;; #(
*)
# `set' quotes correctly as required by POSIX, so do not add quotes.
sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
;;
esac |
sort
) |
sed '
/^ac_cv_env_/b end
t clear
:clear
s/^\([^=]*\)=\(.*[{}].*\)$/test "${\1+set}" = set || &/
t end
s/^\([^=]*\)=\(.*\)$/\1=${\1=\2}/
:end' >>confcache
if diff "$cache_file" confcache >/dev/null 2>&1; then :; else
if test -w "$cache_file"; then
if test "x$cache_file" != "x/dev/null"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: updating cache $cache_file" >&5
$as_echo "$as_me: updating cache $cache_file" >&6;}
if test ! -f "$cache_file" || test -h "$cache_file"; then
cat confcache >"$cache_file"
else
case $cache_file in #(
*/* | ?:*)
mv -f confcache "$cache_file"$$ &&
mv -f "$cache_file"$$ "$cache_file" ;; #(
*)
mv -f confcache "$cache_file" ;;
esac
fi
fi
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: not updating unwritable cache $cache_file" >&5
$as_echo "$as_me: not updating unwritable cache $cache_file" >&6;}
fi
fi
rm -f confcache
test "x$prefix" = xNONE && prefix=$ac_default_prefix
# Let make expand exec_prefix.
test "x$exec_prefix" = xNONE && exec_prefix='${prefix}'
# Transform confdefs.h into DEFS.
# Protect against shell expansion while executing Makefile rules.
# Protect against Makefile macro expansion.
#
# If the first sed substitution is executed (which looks for macros that
# take arguments), then branch to the quote section. Otherwise,
# look for a macro that doesn't take arguments.
ac_script='
:mline
/\\$/{
N
s,\\\n,,
b mline
}
t clear
:clear
s/^[ ]*#[ ]*define[ ][ ]*\([^ (][^ (]*([^)]*)\)[ ]*\(.*\)/-D\1=\2/g
t quote
s/^[ ]*#[ ]*define[ ][ ]*\([^ ][^ ]*\)[ ]*\(.*\)/-D\1=\2/g
t quote
b any
:quote
s/[ `~#$^&*(){}\\|;'\''"<>?]/\\&/g
s/\[/\\&/g
s/\]/\\&/g
s/\$/$$/g
H
:any
${
g
s/^\n//
s/\n/ /g
p
}
'
DEFS=`sed -n "$ac_script" confdefs.h`
ac_libobjs=
ac_ltlibobjs=
for ac_i in : $LIBOBJS; do test "x$ac_i" = x: && continue
# 1. Remove the extension, and $U if already installed.
ac_script='s/\$U\././;s/\.o$//;s/\.obj$//'
ac_i=`$as_echo "$ac_i" | sed "$ac_script"`
# 2. Prepend LIBOBJDIR. When used with automake>=1.10 LIBOBJDIR
# will be set to the directory where LIBOBJS objects are built.
as_fn_append ac_libobjs " \${LIBOBJDIR}$ac_i\$U.$ac_objext"
as_fn_append ac_ltlibobjs " \${LIBOBJDIR}$ac_i"'$U.lo'
done
LIBOBJS=$ac_libobjs
LTLIBOBJS=$ac_ltlibobjs
: "${CONFIG_STATUS=./config.status}"
ac_write_fail=0
ac_clean_files_save=$ac_clean_files
ac_clean_files="$ac_clean_files $CONFIG_STATUS"
{ $as_echo "$as_me:${as_lineno-$LINENO}: creating $CONFIG_STATUS" >&5
$as_echo "$as_me: creating $CONFIG_STATUS" >&6;}
as_write_fail=0
cat >$CONFIG_STATUS <<_ASEOF || as_write_fail=1
#! $SHELL
# Generated by $as_me.
# Run this file to recreate the current configuration.
# Compiler output produced by configure, useful for debugging
# configure, is in config.log if it exists.
debug=false
ac_cs_recheck=false
ac_cs_silent=false
SHELL=\${CONFIG_SHELL-$SHELL}
export SHELL
_ASEOF
cat >>$CONFIG_STATUS <<\_ASEOF || as_write_fail=1
## -------------------- ##
## M4sh Initialization. ##
## -------------------- ##
# Be more Bourne compatible
DUALCASE=1; export DUALCASE # for MKS sh
if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then :
emulate sh
NULLCMD=:
# Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
# is contrary to our usage. Disable this feature.
alias -g '${1+"$@"}'='"$@"'
setopt NO_GLOB_SUBST
else
case `(set -o) 2>/dev/null` in #(
*posix*) :
set -o posix ;; #(
*) :
;;
esac
fi
as_nl='
'
export as_nl
# Printing a long string crashes Solaris 7 /usr/bin/printf.
as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
# Prefer a ksh shell builtin over an external printf program on Solaris,
# but without wasting forks for bash or zsh.
if test -z "$BASH_VERSION$ZSH_VERSION" \
&& (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='print -r --'
as_echo_n='print -rn --'
elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='printf %s\n'
as_echo_n='printf %s'
else
if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
as_echo_n='/usr/ucb/echo -n'
else
as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
as_echo_n_body='eval
arg=$1;
case $arg in #(
*"$as_nl"*)
expr "X$arg" : "X\\(.*\\)$as_nl";
arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
esac;
expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
'
export as_echo_n_body
as_echo_n='sh -c $as_echo_n_body as_echo'
fi
export as_echo_body
as_echo='sh -c $as_echo_body as_echo'
fi
# The user is always right.
if test "${PATH_SEPARATOR+set}" != set; then
PATH_SEPARATOR=:
(PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
(PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
PATH_SEPARATOR=';'
}
fi
# IFS
# We need space, tab and new line, in precisely that order. Quoting is
# there to prevent editors from complaining about space-tab.
# (If _AS_PATH_WALK were called with IFS unset, it would disable word
# splitting by setting IFS to empty value.)
IFS=" "" $as_nl"
# Find who we are. Look in the path if we contain no directory separator.
as_myself=
case $0 in #((
*[\\/]* ) as_myself=$0 ;;
*) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
done
IFS=$as_save_IFS
;;
esac
# We did not find ourselves, most probably we were run as `sh COMMAND'
# in which case we are not to be found in the path.
if test "x$as_myself" = x; then
as_myself=$0
fi
if test ! -f "$as_myself"; then
$as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
exit 1
fi
# Unset variables that we do not need and which cause bugs (e.g. in
# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1"
# suppresses any "Segmentation fault" message there. '((' could
# trigger a bug in pdksh 5.2.14.
for as_var in BASH_ENV ENV MAIL MAILPATH
do eval test x\${$as_var+set} = xset \
&& ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || :
done
PS1='$ '
PS2='> '
PS4='+ '
# NLS nuisances.
LC_ALL=C
export LC_ALL
LANGUAGE=C
export LANGUAGE
# CDPATH.
(unset CDPATH) >/dev/null 2>&1 && unset CDPATH
# as_fn_error STATUS ERROR [LINENO LOG_FD]
# ----------------------------------------
# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are
# provided, also output the error to LOG_FD, referencing LINENO. Then exit the
# script with STATUS, using 1 if that was 0.
as_fn_error ()
{
as_status=$1; test $as_status -eq 0 && as_status=1
if test "$4"; then
as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
$as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4
fi
$as_echo "$as_me: error: $2" >&2
as_fn_exit $as_status
} # as_fn_error
# as_fn_set_status STATUS
# -----------------------
# Set $? to STATUS, without forking.
as_fn_set_status ()
{
return $1
} # as_fn_set_status
# as_fn_exit STATUS
# -----------------
# Exit the shell with STATUS, even in a "trap 0" or "set -e" context.
as_fn_exit ()
{
set +e
as_fn_set_status $1
exit $1
} # as_fn_exit
# as_fn_unset VAR
# ---------------
# Portably unset VAR.
as_fn_unset ()
{
{ eval $1=; unset $1;}
}
as_unset=as_fn_unset
# as_fn_append VAR VALUE
# ----------------------
# Append the text in VALUE to the end of the definition contained in VAR. Take
# advantage of any shell optimizations that allow amortized linear growth over
# repeated appends, instead of the typical quadratic growth present in naive
# implementations.
if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then :
eval 'as_fn_append ()
{
eval $1+=\$2
}'
else
as_fn_append ()
{
eval $1=\$$1\$2
}
fi # as_fn_append
# as_fn_arith ARG...
# ------------------
# Perform arithmetic evaluation on the ARGs, and store the result in the
# global $as_val. Take advantage of shells that can avoid forks. The arguments
# must be portable across $(()) and expr.
if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then :
eval 'as_fn_arith ()
{
as_val=$(( $* ))
}'
else
as_fn_arith ()
{
as_val=`expr "$@" || test $? -eq 1`
}
fi # as_fn_arith
if expr a : '\(a\)' >/dev/null 2>&1 &&
test "X`expr 00001 : '.*\(...\)'`" = X001; then
as_expr=expr
else
as_expr=false
fi
if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
as_basename=basename
else
as_basename=false
fi
if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
as_dirname=dirname
else
as_dirname=false
fi
as_me=`$as_basename -- "$0" ||
$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
X"$0" : 'X\(//\)$' \| \
X"$0" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X/"$0" |
sed '/^.*\/\([^/][^/]*\)\/*$/{
s//\1/
q
}
/^X\/\(\/\/\)$/{
s//\1/
q
}
/^X\/\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
# Avoid depending upon Character Ranges.
as_cr_letters='abcdefghijklmnopqrstuvwxyz'
as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
as_cr_Letters=$as_cr_letters$as_cr_LETTERS
as_cr_digits='0123456789'
as_cr_alnum=$as_cr_Letters$as_cr_digits
ECHO_C= ECHO_N= ECHO_T=
case `echo -n x` in #(((((
-n*)
case `echo 'xy\c'` in
*c*) ECHO_T=' ';; # ECHO_T is single tab character.
xy) ECHO_C='\c';;
*) echo `echo ksh88 bug on AIX 6.1` > /dev/null
ECHO_T=' ';;
esac;;
*)
ECHO_N='-n';;
esac
rm -f conf$$ conf$$.exe conf$$.file
if test -d conf$$.dir; then
rm -f conf$$.dir/conf$$.file
else
rm -f conf$$.dir
mkdir conf$$.dir 2>/dev/null
fi
if (echo >conf$$.file) 2>/dev/null; then
if ln -s conf$$.file conf$$ 2>/dev/null; then
as_ln_s='ln -s'
# ... but there are two gotchas:
# 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
# 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
# In both cases, we have to default to `cp -pR'.
ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
as_ln_s='cp -pR'
elif ln conf$$.file conf$$ 2>/dev/null; then
as_ln_s=ln
else
as_ln_s='cp -pR'
fi
else
as_ln_s='cp -pR'
fi
rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
rmdir conf$$.dir 2>/dev/null
# as_fn_mkdir_p
# -------------
# Create "$as_dir" as a directory, including parents if necessary.
as_fn_mkdir_p ()
{
case $as_dir in #(
-*) as_dir=./$as_dir;;
esac
test -d "$as_dir" || eval $as_mkdir_p || {
as_dirs=
while :; do
case $as_dir in #(
*\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
*) as_qdir=$as_dir;;
esac
as_dirs="'$as_qdir' $as_dirs"
as_dir=`$as_dirname -- "$as_dir" ||
$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$as_dir" : 'X\(//\)[^/]' \| \
X"$as_dir" : 'X\(//\)$' \| \
X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$as_dir" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
test -d "$as_dir" && break
done
test -z "$as_dirs" || eval "mkdir $as_dirs"
} || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir"
} # as_fn_mkdir_p
if mkdir -p . 2>/dev/null; then
as_mkdir_p='mkdir -p "$as_dir"'
else
test -d ./-p && rmdir ./-p
as_mkdir_p=false
fi
# as_fn_executable_p FILE
# -----------------------
# Test if FILE is an executable regular file.
as_fn_executable_p ()
{
test -f "$1" && test -x "$1"
} # as_fn_executable_p
as_test_x='test -x'
as_executable_p=as_fn_executable_p
# Sed expression to map a string onto a valid CPP name.
as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
# Sed expression to map a string onto a valid variable name.
as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
exec 6>&1
## ----------------------------------- ##
## Main body of $CONFIG_STATUS script. ##
## ----------------------------------- ##
_ASEOF
test $as_write_fail = 0 && chmod +x $CONFIG_STATUS || ac_write_fail=1
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# Save the log message, to keep $0 and so on meaningful, and to
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
This file was extended by GNU units $as_me 2.12, which was
generated by GNU Autoconf 2.69. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
CONFIG_HEADERS = $CONFIG_HEADERS
CONFIG_LINKS = $CONFIG_LINKS
CONFIG_COMMANDS = $CONFIG_COMMANDS
$ $0 $@
on `(hostname || uname -n) 2>/dev/null | sed 1q`
"
_ACEOF
case $ac_config_files in *"
"*) set x $ac_config_files; shift; ac_config_files=$*;;
esac
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
# Files that config.status was made for.
config_files="$ac_config_files"
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
ac_cs_usage="\
\`$as_me' instantiates files and other configuration actions
from templates according to the current configuration. Unless the files
and actions are specified as TAGs, all are instantiated by default.
Usage: $0 [OPTION]... [TAG]...
-h, --help print this help, then exit
-V, --version print version number and configuration settings, then exit
--config print configuration, then exit
-q, --quiet, --silent
do not print progress messages
-d, --debug don't remove temporary files
--recheck update $as_me by reconfiguring in the same conditions
--file=FILE[:TEMPLATE]
instantiate the configuration file FILE
Configuration files:
$config_files
Report bugs to .
GNU units home page: .
General help using GNU software: ."
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
ac_cs_version="\\
GNU units config.status 2.12
configured by $0, generated by GNU Autoconf 2.69,
with options \\"\$ac_cs_config\\"
Copyright (C) 2012 Free Software Foundation, Inc.
This config.status script is free software; the Free Software Foundation
gives unlimited permission to copy, distribute and modify it."
ac_pwd='$ac_pwd'
srcdir='$srcdir'
INSTALL='$INSTALL'
MKDIR_P='$MKDIR_P'
test -n "\$AWK" || AWK=awk
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# The default lists apply if the user does not specify any file.
ac_need_defaults=:
while test $# != 0
do
case $1 in
--*=?*)
ac_option=`expr "X$1" : 'X\([^=]*\)='`
ac_optarg=`expr "X$1" : 'X[^=]*=\(.*\)'`
ac_shift=:
;;
--*=)
ac_option=`expr "X$1" : 'X\([^=]*\)='`
ac_optarg=
ac_shift=:
;;
*)
ac_option=$1
ac_optarg=$2
ac_shift=shift
;;
esac
case $ac_option in
# Handling of the options.
-recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
ac_cs_recheck=: ;;
--version | --versio | --versi | --vers | --ver | --ve | --v | -V )
$as_echo "$ac_cs_version"; exit ;;
--config | --confi | --conf | --con | --co | --c )
$as_echo "$ac_cs_config"; exit ;;
--debug | --debu | --deb | --de | --d | -d )
debug=: ;;
--file | --fil | --fi | --f )
$ac_shift
case $ac_optarg in
*\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;
'') as_fn_error $? "missing file argument" ;;
esac
as_fn_append CONFIG_FILES " '$ac_optarg'"
ac_need_defaults=false;;
--he | --h | --help | --hel | -h )
$as_echo "$ac_cs_usage"; exit ;;
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil | --si | --s)
ac_cs_silent=: ;;
# This is an error.
-*) as_fn_error $? "unrecognized option: \`$1'
Try \`$0 --help' for more information." ;;
*) as_fn_append ac_config_targets " $1"
ac_need_defaults=false ;;
esac
shift
done
ac_configure_extra_args=
if $ac_cs_silent; then
exec 6>/dev/null
ac_configure_extra_args="$ac_configure_extra_args --silent"
fi
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
if \$ac_cs_recheck; then
set X $SHELL '$0' $ac_configure_args \$ac_configure_extra_args --no-create --no-recursion
shift
\$as_echo "running CONFIG_SHELL=$SHELL \$*" >&6
CONFIG_SHELL='$SHELL'
export CONFIG_SHELL
exec "\$@"
fi
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
exec 5>>config.log
{
echo
sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
## Running $as_me. ##
_ASBOX
$as_echo "$ac_log"
} >&5
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# Handling of arguments.
for ac_config_target in $ac_config_targets
do
case $ac_config_target in
"Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;;
*) as_fn_error $? "invalid argument: \`$ac_config_target'" "$LINENO" 5;;
esac
done
# If the user did not use the arguments to specify the items to instantiate,
# then the envvar interface is used. Set only those that are not.
# We use the long form for the default assignment because of an extremely
# bizarre bug on SunOS 4.1.3.
if $ac_need_defaults; then
test "${CONFIG_FILES+set}" = set || CONFIG_FILES=$config_files
fi
# Have a temporary directory for convenience. Make it in the build tree
# simply because there is no reason against having it here, and in addition,
# creating and moving files from /tmp can sometimes cause problems.
# Hook for its removal unless debugging.
# Note that there is a small window in which the directory will not be cleaned:
# after its creation but before its name has been assigned to `$tmp'.
$debug ||
{
tmp= ac_tmp=
trap 'exit_status=$?
: "${ac_tmp:=$tmp}"
{ test ! -d "$ac_tmp" || rm -fr "$ac_tmp"; } && exit $exit_status
' 0
trap 'as_fn_exit 1' 1 2 13 15
}
# Create a (secure) tmp directory for tmp files.
{
tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` &&
test -d "$tmp"
} ||
{
tmp=./conf$$-$RANDOM
(umask 077 && mkdir "$tmp")
} || as_fn_error $? "cannot create a temporary directory in ." "$LINENO" 5
ac_tmp=$tmp
# Set up the scripts for CONFIG_FILES section.
# No need to generate them if there are no CONFIG_FILES.
# This happens for instance with `./config.status config.h'.
if test -n "$CONFIG_FILES"; then
ac_cr=`echo X | tr X '\015'`
# On cygwin, bash can eat \r inside `` if the user requested igncr.
# But we know of no other shell where ac_cr would be empty at this
# point, so we can use a bashism as a fallback.
if test "x$ac_cr" = x; then
eval ac_cr=\$\'\\r\'
fi
ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' /dev/null`
if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then
ac_cs_awk_cr='\\r'
else
ac_cs_awk_cr=$ac_cr
fi
echo 'BEGIN {' >"$ac_tmp/subs1.awk" &&
_ACEOF
{
echo "cat >conf$$subs.awk <<_ACEOF" &&
echo "$ac_subst_vars" | sed 's/.*/&!$&$ac_delim/' &&
echo "_ACEOF"
} >conf$$subs.sh ||
as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
ac_delim_num=`echo "$ac_subst_vars" | grep -c '^'`
ac_delim='%!_!# '
for ac_last_try in false false false false false :; do
. ./conf$$subs.sh ||
as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
ac_delim_n=`sed -n "s/.*$ac_delim\$/X/p" conf$$subs.awk | grep -c X`
if test $ac_delim_n = $ac_delim_num; then
break
elif $ac_last_try; then
as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
else
ac_delim="$ac_delim!$ac_delim _$ac_delim!! "
fi
done
rm -f conf$$subs.sh
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
cat >>"\$ac_tmp/subs1.awk" <<\\_ACAWK &&
_ACEOF
sed -n '
h
s/^/S["/; s/!.*/"]=/
p
g
s/^[^!]*!//
:repl
t repl
s/'"$ac_delim"'$//
t delim
:nl
h
s/\(.\{148\}\)..*/\1/
t more1
s/["\\]/\\&/g; s/^/"/; s/$/\\n"\\/
p
n
b repl
:more1
s/["\\]/\\&/g; s/^/"/; s/$/"\\/
p
g
s/.\{148\}//
t nl
:delim
h
s/\(.\{148\}\)..*/\1/
t more2
s/["\\]/\\&/g; s/^/"/; s/$/"/
p
b
:more2
s/["\\]/\\&/g; s/^/"/; s/$/"\\/
p
g
s/.\{148\}//
t delim
' >$CONFIG_STATUS || ac_write_fail=1
rm -f conf$$subs.awk
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
_ACAWK
cat >>"\$ac_tmp/subs1.awk" <<_ACAWK &&
for (key in S) S_is_set[key] = 1
FS = ""
}
{
line = $ 0
nfields = split(line, field, "@")
substed = 0
len = length(field[1])
for (i = 2; i < nfields; i++) {
key = field[i]
keylen = length(key)
if (S_is_set[key]) {
value = S[key]
line = substr(line, 1, len) "" value "" substr(line, len + keylen + 3)
len += length(value) + length(field[++i])
substed = 1
} else
len += 1 + keylen
}
print line
}
_ACAWK
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
if sed "s/$ac_cr//" < /dev/null > /dev/null 2>&1; then
sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g"
else
cat
fi < "$ac_tmp/subs1.awk" > "$ac_tmp/subs.awk" \
|| as_fn_error $? "could not setup config files machinery" "$LINENO" 5
_ACEOF
# VPATH may cause trouble with some makes, so we remove sole $(srcdir),
# ${srcdir} and @srcdir@ entries from VPATH if srcdir is ".", strip leading and
# trailing colons and then remove the whole line if VPATH becomes empty
# (actually we leave an empty line to preserve line numbers).
if test "x$srcdir" = x.; then
ac_vpsub='/^[ ]*VPATH[ ]*=[ ]*/{
h
s///
s/^/:/
s/[ ]*$/:/
s/:\$(srcdir):/:/g
s/:\${srcdir}:/:/g
s/:@srcdir@:/:/g
s/^:*//
s/:*$//
x
s/\(=[ ]*\).*/\1/
G
s/\n//
s/^[^=]*=[ ]*$//
}'
fi
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
fi # test -n "$CONFIG_FILES"
eval set X " :F $CONFIG_FILES "
shift
for ac_tag
do
case $ac_tag in
:[FHLC]) ac_mode=$ac_tag; continue;;
esac
case $ac_mode$ac_tag in
:[FHL]*:*);;
:L* | :C*:*) as_fn_error $? "invalid tag \`$ac_tag'" "$LINENO" 5;;
:[FH]-) ac_tag=-:-;;
:[FH]*) ac_tag=$ac_tag:$ac_tag.in;;
esac
ac_save_IFS=$IFS
IFS=:
set x $ac_tag
IFS=$ac_save_IFS
shift
ac_file=$1
shift
case $ac_mode in
:L) ac_source=$1;;
:[FH])
ac_file_inputs=
for ac_f
do
case $ac_f in
-) ac_f="$ac_tmp/stdin";;
*) # Look for the file first in the build tree, then in the source tree
# (if the path is not absolute). The absolute path cannot be DOS-style,
# because $ac_f cannot contain `:'.
test -f "$ac_f" ||
case $ac_f in
[\\/$]*) false;;
*) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";;
esac ||
as_fn_error 1 "cannot find input file: \`$ac_f'" "$LINENO" 5;;
esac
case $ac_f in *\'*) ac_f=`$as_echo "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac
as_fn_append ac_file_inputs " '$ac_f'"
done
# Let's still pretend it is `configure' which instantiates (i.e., don't
# use $as_me), people would be surprised to read:
# /* config.h. Generated by config.status. */
configure_input='Generated from '`
$as_echo "$*" | sed 's|^[^:]*/||;s|:[^:]*/|, |g'
`' by configure.'
if test x"$ac_file" != x-; then
configure_input="$ac_file. $configure_input"
{ $as_echo "$as_me:${as_lineno-$LINENO}: creating $ac_file" >&5
$as_echo "$as_me: creating $ac_file" >&6;}
fi
# Neutralize special characters interpreted by sed in replacement strings.
case $configure_input in #(
*\&* | *\|* | *\\* )
ac_sed_conf_input=`$as_echo "$configure_input" |
sed 's/[\\\\&|]/\\\\&/g'`;; #(
*) ac_sed_conf_input=$configure_input;;
esac
case $ac_tag in
*:-:* | *:-) cat >"$ac_tmp/stdin" \
|| as_fn_error $? "could not create $ac_file" "$LINENO" 5 ;;
esac
;;
esac
ac_dir=`$as_dirname -- "$ac_file" ||
$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$ac_file" : 'X\(//\)[^/]' \| \
X"$ac_file" : 'X\(//\)$' \| \
X"$ac_file" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$ac_file" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
as_dir="$ac_dir"; as_fn_mkdir_p
ac_builddir=.
case "$ac_dir" in
.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
*)
ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
# A ".." for each directory in $ac_dir_suffix.
ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
case $ac_top_builddir_sub in
"") ac_top_builddir_sub=. ac_top_build_prefix= ;;
*) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
esac ;;
esac
ac_abs_top_builddir=$ac_pwd
ac_abs_builddir=$ac_pwd$ac_dir_suffix
# for backward compatibility:
ac_top_builddir=$ac_top_build_prefix
case $srcdir in
.) # We are building in place.
ac_srcdir=.
ac_top_srcdir=$ac_top_builddir_sub
ac_abs_top_srcdir=$ac_pwd ;;
[\\/]* | ?:[\\/]* ) # Absolute name.
ac_srcdir=$srcdir$ac_dir_suffix;
ac_top_srcdir=$srcdir
ac_abs_top_srcdir=$srcdir ;;
*) # Relative name.
ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
ac_top_srcdir=$ac_top_build_prefix$srcdir
ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
esac
ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
case $ac_mode in
:F)
#
# CONFIG_FILE
#
case $INSTALL in
[\\/$]* | ?:[\\/]* ) ac_INSTALL=$INSTALL ;;
*) ac_INSTALL=$ac_top_build_prefix$INSTALL ;;
esac
ac_MKDIR_P=$MKDIR_P
case $MKDIR_P in
[\\/$]* | ?:[\\/]* ) ;;
*/*) ac_MKDIR_P=$ac_top_build_prefix$MKDIR_P ;;
esac
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# If the template does not know about datarootdir, expand it.
# FIXME: This hack should be removed a few years after 2.60.
ac_datarootdir_hack=; ac_datarootdir_seen=
ac_sed_dataroot='
/datarootdir/ {
p
q
}
/@datadir@/p
/@docdir@/p
/@infodir@/p
/@localedir@/p
/@mandir@/p'
case `eval "sed -n \"\$ac_sed_dataroot\" $ac_file_inputs"` in
*datarootdir*) ac_datarootdir_seen=yes;;
*@datadir@*|*@docdir@*|*@infodir@*|*@localedir@*|*@mandir@*)
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&5
$as_echo "$as_me: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&2;}
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_datarootdir_hack='
s&@datadir@&$datadir&g
s&@docdir@&$docdir&g
s&@infodir@&$infodir&g
s&@localedir@&$localedir&g
s&@mandir@&$mandir&g
s&\\\${datarootdir}&$datarootdir&g' ;;
esac
_ACEOF
# Neutralize VPATH when `$srcdir' = `.'.
# Shell code in configure.ac might set extrasub.
# FIXME: do we really want to maintain this feature?
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_sed_extra="$ac_vpsub
$extrasub
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
:t
/@[a-zA-Z_][a-zA-Z_0-9]*@/!b
s|@configure_input@|$ac_sed_conf_input|;t t
s&@top_builddir@&$ac_top_builddir_sub&;t t
s&@top_build_prefix@&$ac_top_build_prefix&;t t
s&@srcdir@&$ac_srcdir&;t t
s&@abs_srcdir@&$ac_abs_srcdir&;t t
s&@top_srcdir@&$ac_top_srcdir&;t t
s&@abs_top_srcdir@&$ac_abs_top_srcdir&;t t
s&@builddir@&$ac_builddir&;t t
s&@abs_builddir@&$ac_abs_builddir&;t t
s&@abs_top_builddir@&$ac_abs_top_builddir&;t t
s&@INSTALL@&$ac_INSTALL&;t t
s&@MKDIR_P@&$ac_MKDIR_P&;t t
$ac_datarootdir_hack
"
eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$ac_tmp/subs.awk" \
>$ac_tmp/out || as_fn_error $? "could not create $ac_file" "$LINENO" 5
test -z "$ac_datarootdir_hack$ac_datarootdir_seen" &&
{ ac_out=`sed -n '/\${datarootdir}/p' "$ac_tmp/out"`; test -n "$ac_out"; } &&
{ ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' \
"$ac_tmp/out"`; test -z "$ac_out"; } &&
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file contains a reference to the variable \`datarootdir'
which seems to be undefined. Please make sure it is defined" >&5
$as_echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir'
which seems to be undefined. Please make sure it is defined" >&2;}
rm -f "$ac_tmp/stdin"
case $ac_file in
-) cat "$ac_tmp/out" && rm -f "$ac_tmp/out";;
*) rm -f "$ac_file" && mv "$ac_tmp/out" "$ac_file";;
esac \
|| as_fn_error $? "could not create $ac_file" "$LINENO" 5
;;
esac
done # for ac_tag
as_fn_exit 0
_ACEOF
ac_clean_files=$ac_clean_files_save
test $ac_write_fail = 0 ||
as_fn_error $? "write failure creating $CONFIG_STATUS" "$LINENO" 5
# configure is writing to config.log, and then calls config.status.
# config.status does its own redirection, appending to config.log.
# Unfortunately, on DOS this fails, as config.log is still kept open
# by configure, so config.status won't be able to write to it; its
# output is simply discarded. So we exec the FD to /dev/null,
# effectively closing config.log, so it can be properly (re)opened and
# appended to by config.status. When coming back to configure, we
# need to make the FD available again.
if test "$no_create" != yes; then
ac_cs_success=:
ac_config_status_args=
test "$silent" = yes &&
ac_config_status_args="$ac_config_status_args --quiet"
exec 5>/dev/null
$SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false
exec 5>>config.log
# Use ||, not &&, to avoid exiting from the if with $? = 1, which
# would make configure fail if this is the last instruction.
$ac_cs_success || as_fn_exit 1
fi
if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: unrecognized options: $ac_unrecognized_opts" >&5
$as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;}
fi
units-2.12/units.h 0000664 0001750 0001750 00000010746 12472715341 013411 0 ustar adrian adrian /*
* units, a program for units conversion
* Copyright (C) 1996, 1997, 1999, 2000, 2001, 2014 Free Software Foundation, Inc
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 3 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*
* This program was written by Adrian Mariano (adrianm@gnu.org)
*/
#include
#include
/* Apparently popen and pclose require leading _ under windows */
#if defined(_MSC_VER) || defined(__MINGW32__)
# define popen _popen
# define pclose _pclose
#endif
#ifdef NO_ISFINITE
# if defined _WIN32 && defined _MSC_VER
# define isfinite(x) (!_isnan(x) && _finite(x))
# else
# define isfinite(x) ( -DBL_MAX <= (x) && (x) <= DBL_MAX )
# endif
#endif
#ifdef STRINGS_H
# include
#else
# include
#endif
#ifndef NO_STDLIB_H
# include
#else
char *malloc(), *realloc(), *getenv();
#endif
#ifndef strchr
# ifdef NO_STRCHR
# define strchr(a,b) index((a),(b))
# else
char *strchr();
# endif
#endif /* !strchr */
#define E_NORMAL 0
#define E_PARSE 1
#define E_PRODOVERFLOW 2
#define E_REDUCE 3
#define E_BADSUM 4
#define E_NOTANUMBER 5
#define E_NOTROOT 6
#define E_UNKNOWNUNIT 7
#define E_FUNC 8 /* If errno is set after calling a function */
#define E_BADFUNCTYPE 9
#define E_BADFUNCARG 10
#define E_NOTINDOMAIN 11
#define E_BADFUNCDIMEN 12
#define E_NOINVERSE 13
#define E_PARSEMEM 14
#define E_FUNARGDEF 15
#define E_FILE 16
#define E_BADFILE 17
#define E_MEMORY 18
#define E_BADNUM 19
#define E_UNITEND 20
#define E_LASTUNSET 21
#define E_IRRATIONAL_EXPONENT 22
#define E_BASE_NOTROOT 23
#define E_DIMEXPONENT 24
#define E_NOTAFUNC 25
#define WHITE " \t\n"
extern char *errormsg[];
/*
Data type used to store a single unit being operated on.
The numerator and denominator arrays contain lists of units
(strings) which are terminated by a null pointer. The special
string NULLUNIT is used to mark blank units that occur in the
middle of the list.
*/
extern char *NULLUNIT;
#define MAXSUBUNITS 100 /* Size of internal unit reduction buffer */
struct unittype {
char *numerator[MAXSUBUNITS];
char *denominator[MAXSUBUNITS];
double factor;
};
struct functype {
char *param;
char *def;
char *dimen;
double *domain_min, *domain_max;
int domain_min_open, domain_max_open;
};
struct pair {
double location, value;
};
struct func {
char *name;
struct functype forward;
struct functype inverse;
struct pair *table;
int tablelen;
char *tableunit;
struct func *next;
int skip_error_check; /* do not check for errors when running units -c */
int linenumber;
char *file; /* file where defined */
};
struct parseflag {
int oldstar; /* Does '*' have higher precedence than '/' */
int minusminus; /* Does '-' character give subtraction */
};
extern struct parseflag parserflags;
extern struct unittype *parameter_value;
extern char *function_parameter;
extern int lastunitset;
extern struct unittype lastunit;
void *mymalloc(int bytes,char *mesg);
int hassubscript(const char *str, int length);
void initializeunit(struct unittype *theunit);
void freeunit(struct unittype *theunit);
void unitcopy(struct unittype *dest,struct unittype *src);
int divunit(struct unittype *left, struct unittype *right);
void invertunit(struct unittype *theunit);
int multunit(struct unittype *left, struct unittype *right);
int expunit(struct unittype *theunit, int power);
int addunit(struct unittype *unita, struct unittype *unitb);
int rootunit(struct unittype *inunit,int n);
int unitpower(struct unittype *base, struct unittype *exponent);
char *dupstr(const char *str);
int unit2num(struct unittype *input);
struct func *fnlookup(const char *str, int length);
int evalfunc(struct unittype *theunit, struct func *infunc, int inverse,
int allerror);
int parseunit(struct unittype *output, char *input,char **errstr,int *errloc);
units-2.12/units.texinfo 0000664 0001750 0001750 00000374613 12606610543 014641 0 ustar adrian adrian \input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename units.info
@settitle Units: A Unit Conversion Program and Scientific Calculator
@finalout
@setchapternewpage off
@firstparagraphindent none
@set EDITION 2.11
@set VERSION 2.12
@c %**end of header
@c ifman .\"
@copying
This manual is for GNU Units (version @value{VERSION}),
which performs units conversions and units calculations.
Copyright @copyright{} 1996, 1997, 1999, 2000, 2001, 2002, 2004, 2005, 2007,
2011--2015 Free Software Foundation, Inc.
@quotation
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts.
@c end ifman
@c noman
A copy of the license is included in the section entitled
``GNU Free Documentation License''.
@end quotation
@end copying
@c end noman
@defcodeindex op
@syncodeindex op cp
@c noman
@dircategory Science
@direntry
* Units: (units). Units conversion and scientific calculation.
@end direntry
@c end noman
@c man .TH UNITS 1 "19 March 2014"
@c man .SH NAME
@c man units \(em unit conversion and calculation program
@titlepage
@title Units Conversion
@subtitle Edition @value{EDITION} for @command{units} Version @value{VERSION}
@author Adrian Mariano
@page
@vskip 0pt plus 1filll
@insertcopying
@end titlepage
@contents
@iftex
@headings off
@everyheading Units Conversion @| @| @thispage
@end iftex
@ifnottex
@node Top
@top Units Conversion
@c noman
This manual describes the @command{units} command for units conversion and
how you can use it as a powerful scientific calculator that keeps
track of units.
This is Edition @value{EDITION} of @cite{The Units Conversion Manual}
for @command{units} Version @value{VERSION}.
@c end noman
@end ifnottex
@menu
* Overview:: What does @command{units} do?
* Interactive Use:: How to use @command{units}.
* Command Line Use:: How to use @command{units} non-interactively.
* Unit Definitions:: What units are defined?
* Unit Expressions:: Forming compound units.
* Nonlinear Conversions:: Nonlinear unit conversions (e.g., temperature).
* Unit Lists:: Conversion to sums of units (e.g., feet and inches).
* Logging Calculations:: Logging conversions and calculations in a file.
* Invoking Units:: Command line options.
* Defining Your Own Units:: Adding your own unit definitions
* Numeric Output Format:: How to change the output format
* Localization:: How to define and use regional unit names.
* Environment Vars:: Environment variables used by @command{units}.
* Data Files:: Descriptions and locations of units data files.
* Unicode Support:: Support for Unicode (UTF-8).
* Readline Support:: Unit name completion and editing.
* Currency:: Updating currency exchange rates.
* Database Syntax:: Summary of database command syntax.
* GNU Free Documentation License:: License.
* Index:: General index.
@end menu
@c noman
@node Overview
@chapter Overview of @command{units}
@c end noman
@c ifman
@ignore
@c '.PP' for consistency with spacing before other sections.
.PP
.SH SYNOPSIS
.PP
.CW units
.RI [ options ]
.RI [ from-unit
.RI [ to-unit ]]
.PP
.SH DESCRIPTION
@end ignore
@c end ifman
The @command{units} program converts quantities expressed in various
systems of measurement to their equivalents in other systems of
measurement. Like many similar programs, it can handle multiplicative
scale changes. It can also handle nonlinear conversions such as
Fahrenheit to
@c man Celsius;
@c noman
Celsius;@footnote{But Fahrenheit to
Celsius is linear, you insist. Not so. A transformation @math{T} is linear if
@math{T(x+y)=T(x)+T(y)} and this fails for @math{T(x)=ax+b}. This transformation is
affine, but not linear. }
@pxref{Temperature Conversions}.
@c end noman
@c man see \fITemperature Conversions\fP.
The program can also perform conversions from and to sums of
units, such as converting between meters and feet plus inches.
Basic operation is simple: you enter the units that you want to convert
@emph{from} and the units that you want to convert @emph{to}.
You can use the program interactively with prompts, or you can use it
from the command line.
Beyond simple unit conversions, @command{units} can be used as a
general-purpose scientific calculator that keeps track of units in its
calculations. You can form arbitrary complex mathematical expressions
of dimensions including sums, products, quotients, powers, and even roots
of dimensions. Thus you can ensure accuracy and dimensional consistency
when working with long expressions that involve many different units
that may combine in complex ways; for an illustration,
@c man see \fIComplicated Unit Expressions\fP.
@c noman
@pxref{Complicated Unit Expressions}.
@c end noman
The units are defined in an external data file. You can use the
extensive data file that comes with this program, or you can
provide your own data file to suit your needs. You can also use your
own data file to supplement the standard data file.
You can change the default behavior of @command{units} with various
options given on the command line. @xref{Invoking Units}, for a
description of the available options.
@node Interactive Use
@chapter Interacting with @command{units}
@cindex interactive use
To invoke units for interactive use, type @kbd{units} at your shell
prompt. The program will print something like this:
@example
@group
Currency exchange rates from www.timegenie.com on 2014-03-05
2860 units, 109 prefixes, 85 nonlinear units
You have:
@end group
@end example
@noindent
At the @w{@samp{You have:}} prompt, type the quantity and units that
you are converting @emph{from}. For example, if you want to convert ten
meters to feet, type @kbd{10 meters}. Next, @command{units} will print
@w{@samp{You want:}}. You should type the units you want to convert
@emph{to}. To convert to feet, you would type @kbd{feet}. If the
@command{readline} library was compiled in then @key{tab} will
complete unit names. @xref{Readline Support}, for more information
about @command{readline}. To quit the program under Unix, press
@key{Ctrl-C} or @key{Ctrl-D}. Under Windows, press @key{Ctrl-C} or
@key{Ctrl-Z}; with the latter, you may also need to press @key{Enter}.
The result will be displayed in two ways. The first line of output,
which is marked with a @samp{*} to indicate multiplication, gives the
result of the conversion you have asked for. The second line of output,
which is marked with a @samp{/} to indicate division, gives the inverse
of the conversion factor. If you convert 10 meters to feet,
@command{units} will print
@example
@group
* 32.808399
/ 0.03048
@end group
@end example
@noindent
which tells you that 10 meters equals about 32.8 feet.
The second number gives the conversion in the opposite direction.
In this case, it tells you that 1 foot is equal to about
0.03 dekameters since the dekameter is 10 meters.
It also tells you that 1/32.8 is about 0.03.
The @command{units} program prints the inverse because sometimes it is a
more convenient number. In the example above, for example, the inverse
value is an exact conversion: a foot is exactly 0.03048 dekameters.
But the number given the other direction is inexact.
If you convert grains to pounds, you will see the following:
@example
@group
You have: grains
You want: pounds
* 0.00014285714
/ 7000
@end group
@end example
@noindent
From the second line of the output you can immediately see that a grain
is equal to a seven thousandth of a pound. This is not so obvious from
the first line of the output.
If you find the output format confusing, try using the
@option{--verbose} option:
@cindex verbose output
@example
@group
You have: grain
You want: aeginamina
grain = 0.00010416667 aeginamina
grain = (1 / 9600) aeginamina
@end group
@end example
@noindent
If you request a conversion between units that measure reciprocal
dimensions, then @command{units} will display the conversion results with an extra
note indicating that reciprocal conversion has been done:
@cindex reciprocal conversion
@example
@group
You have: 6 ohms
You want: siemens
reciprocal conversion
* 0.16666667
/ 6
@end group
@end example
@noindent
Reciprocal conversion can be suppressed by using the @option{--strict} option.
As usual, use
the @option{--verbose} option to get more comprehensible output:
@cindex verbose output
@cindex strict conversion
@example
@group
You have: tex
You want: typp
reciprocal conversion
1 / tex = 496.05465 typp
1 / tex = (1 / 0.0020159069) typp
You have: 20 mph
You want: sec/mile
reciprocal conversion
1 / 20 mph = 180 sec/mile
1 / 20 mph = (1 / 0.0055555556) sec/mile
@end group
@end example
@noindent
If you enter incompatible unit types, the @command{units} program will
print a message indicating that the units are not conformable and
it will display the reduced form for each unit:
@cindex incompatible units
@cindex non-conformable units
@example
@group
You have: ergs/hour
You want: fathoms kg^2 / day
conformability error
2.7777778e-11 kg m^2 / sec^3
2.1166667e-05 kg^2 m / sec
@end group
@end example
@noindent
If you only want to find the reduced form or definition of a unit,
simply press @key{Enter} at the @w{@samp{You want:}} prompt. Here is an
example:
@example
@group
You have: jansky
You want:
Definition: fluxunit = 1e-26 W/m^2 Hz = 1e-26 kg / s^2
@end group
@end example
@noindent
The output from @command{units} indicates that the jansky is defined to be
equal to a fluxunit which in turn is defined to be a certain combination
of watts, meters, and hertz. The fully reduced (and in this case
somewhat more cryptic) form appears on the far right.
Some named units are treated as dimensionless in some situations.
These units include the radian and steradian. These units will be
treated as equal to 1 in units conversions. Power is equal to torque
times angular velocity. This conversion can only be performed if the
radian is dimensionless.
@example
@group
You have: (14 ft lbf) (12 radians/sec)
You want: watts
* 227.77742
/ 0.0043902509
@end group
@end example
@noindent
It is also possible to compute roots and other non-integer powers of
dimensionless units; this allows computations such as the altitude of
geosynchronous orbit:
@example
@group
You have: cuberoot(G earthmass / (circle/siderealday)^2) - earthradius
You want: miles
* 22243.267
/ 4.4957425e-05
@end group
@end example
@noindent
Named dimensionless units are not treated as dimensionless
in other contexts. They cannot be used as exponents
so for example, @samp{meter^radian} is forbidden.
@cindex dimensionless units
@cindex @samp{?} to show conformable units
@cindex conformable units, @samp{?} to show
If you want a list of options you can type @kbd{?} at the
@w{@samp{You want:}} prompt. The program will display a list of named
units that are conformable with the unit that you entered at the
@w{@samp{You have:}} prompt above. Conformable unit @emph{combinations}
will not appear on this list.
@cindex help
Typing @kbd{help} at either prompt displays a short help message.
You can also type @kbd{help} followed by a unit name. This will
invoke a pager on the units data base at the point where that unit
is defined. You can read the definition and comments that may
give more details or historical information about the unit. (You
can generally quit out of the page by pressing @samp{q}.)
Typing @kbd{search} @var{text} will display a list of all of the units
whose names contain @var{text} as a substring along with their definitions.
This may help in the case where you aren't sure of the right unit name.
@node Command Line Use
@chapter Using @command{units} Non-Interactively
@cindex command-line unit conversion
@cindex non-interactive unit conversion
The @command{units} program can perform units conversions non-interactively
from the command line. To do this, type the command, type the original
unit expression, and type the new units you want. If a units
expression contains non-alphanumeric characters, you may need to protect
it from interpretation by the shell using single or double quote
characters.
If you type
@example
units "2 liters" quarts
@end example
@noindent
then @command{units} will print
@example
@group
* 2.1133764
/ 0.47317647
@end group
@end example
@noindent
and then exit.
The output tells you that 2 liters is about 2.1 quarts, or alternatively that
a quart is about 0.47 times 2 liters.
If the conversion is successful, then @command{units} will return success (zero)
to the calling environment. If you enter non-conformable
units then @command{units} will print a message giving the reduced form of
each unit and it will return failure (nonzero) to the calling environment.
When you invoke @command{units} with only one argument, it will print out
the definition of the specified unit. It will return failure if the
unit is not defined and success if the unit is defined.
@node Unit Definitions
@chapter Unit Definitions
@cindex unit definitions
The conversion information is read from a units data file that
is called @file{definitions.units} and is usually located in
the @file{/usr/share/units} directory.
If you invoke @command{units} with the @option{-V} option, it will print
the location of this file.
The default
file includes definitions for all familiar units, abbreviations and
metric prefixes. It also includes many obscure or archaic units.
Many constants of nature are defined, including these:
@example
pi @r{ratio of circumference to diameter}
c @r{speed of light}
e @r{charge on an electron}
force @r{acceleration of gravity}
mole @r{Avogadro's number}
water @r{pressure per unit height of water}
Hg @r{pressure per unit height of mercury}
au @r{astronomical unit}
k @r{Boltzman's constant}
mu0 @r{permeability of vacuum}
epsilon0 @r{permittivity of vacuum}
G @r{Gravitational constant}
mach @r{speed of sound}
@end example
@noindent
The standard data file includes atomic masses for all of the elements
and numerous other constants. Also included are the densities of
various ingredients used in baking so that @samp{2@tie{}cups flour_sifted}
can be converted to @samp{grams}. This is not an exhaustive list.
Consult the units data file to see the complete list, or to see the
definitions that are used.
@cindex measure, Imperial
@cindex Imperial measure
@cindex British Imperial measure
The @samp{pound} is a unit of mass. To get force, multiply by the
force conversion unit @samp{force} or use the shorthand @samp{lbf}.
(Note that @samp{g} is already taken as the standard abbreviation for
the gram.) The unit @samp{ounce} is also a unit of mass. The fluid
ounce is @samp{fluidounce} or @samp{floz}. When British capacity
units differ from their US counterparts, such as the British Imperial
gallon, the unit is defined both ways with @samp{br} and @samp{us}
prefixes. Your locale settings will determine the value of the
unprefixed unit. Currency is prefixed with its country
name: @samp{belgiumfranc}, @samp{britainpound}.
@cindex units, lookup method
When searching for a unit, if the specified string does not appear
exactly as a unit name, then the @command{units} program will try to
remove a trailing @samp{s}, @samp{es}. Next units will replace a
trailing @samp{ies} with @samp{y}. If that fails,
@command{units} will check for a prefix. The database includes all
of the standard metric prefixes. Only one prefix is permitted per
unit, so @samp{micromicrofarad} will fail. However, prefixes can
appear alone with no unit following them, so
@samp{micro*microfarad} will work, as will @samp{micro microfarad}.
@cindex prefixes
To find out which units and prefixes are available, read the standard
units data file, which is extensively annotated.
@section English Customary Units
@cindex volume measure, English customary
English customary units differ in various ways in different
regions. In Britain a complex system of volume measurements featured
different gallons for different materials such as a wine gallon and
ale gallon that different by twenty percent. This complexity was
swept away in 1824 by a reform that created an entirely new gallon,
the British Imperial gallon defined as the volume occupied by ten
pounds of water. Meanwhile in the USA the gallon is derived from the
1707 Winchester wine gallon, which is 231 cubic inches. These gallons
differ by about twenty percent. By default if @command{units} runs in
the @samp{en_GB} locale you will get the British volume measures. If
it runs in the @samp{en_US} locale you will get the US volume
measures. In other locales the default values are the US
definitions. If you wish to force different definitions then set the
environment variable @env{UNITS_ENGLISH} to either @samp{US} or
@samp{GB} to set the desired definitions independent of the locale.
@cindex length measure, English customary
@cindex length measure, UK
@cindex survey measure, US
@cindex US survey measure
@cindex survey mile, US
@cindex US survey foot
@cindex State Plane Coordinate System, US
@cindex US State Plane Coordinate System
@cindex survey foot, US
@cindex US survey mile
@cindex mile, international
@cindex international mile
@cindex yard, international
@cindex international yard
Before 1959, the value of a yard (and other units of measure defined in
terms of it) differed slightly among English-speaking countries. In
1959, Australia, Canada, New Zealand, the United Kingdom, the United
States, and South Africa adopted the Canadian value of 1@tie{}yard =
0.9144@tie{}m (exactly), which was approximately halfway between the
values used by the UK and the US; it had the additional advantage of
making 1@tie{}inch = 2.54@tie{}cm (exactly). This new standard was
termed the @dfn{International Yard}. Australia, Canada, and the UK then
defined all customary lengths in terms of the International Yard
(Australia did not define the furlong or rod); because many US land
surveys were in terms of the pre-1959 units, the US continued to define
customary surveyors' units (furlong, chain, rod, and link) in terms of
the previous value for the foot, which was termed the
@dfn{US survey foot}. The US defined a @dfn{US survey mile} as 5280 US
survey feet, and defined a @dfn{statute mile} as a US survey mile. The
US values for these units differ from the international values by about
2@tie{}ppm.
The @command{units} program uses the international values for these
units; the US values can be obtained by using either the @samp{US} or
the @samp{survey} prefix. In either case, the simple familiar
relationships among the units are maintained, e.g., 1 @samp{furlong} =
660 @samp{ft}, and 1 @samp{USfurlong} = 660 @samp{USft}, though the
metric equivalents differ slightly between the two cases.
The @samp{US} prefix or the @samp{survey} prefix can also be used to
obtain the US survey mile and the value of the US yard prior to 1959,
e.g., @samp{USmile} or @samp{surveymile} (but @emph{not}
@samp{USsurveymile}). To get the US value of the statute mile, use
either @samp{USstatutemile} or @samp{USmile}.
Except for distances that extend over hundreds of miles (such as in the
US State Plane Coordinate System), the differences in the miles are
usually insignificant:
@example
@group
You have: 100 surveymile - 100 mile
You want: inch
* 12.672025
/ 0.078913984
@end group
@end example
@noindent
The pre-1959 UK values for these units can be obtained with the prefix
@samp{UK}.
In the US, the acre is officially defined in terms of the US survey
foot, but @command{units} uses a definition based on the international
foot. If you want the official US acre use @samp{USacre} and
similarly use @samp{USacrefoot} for the official US version of that
unit. The difference between these units is about 4 parts per million.
@node Unit Expressions
@chapter Unit Expressions
@cindex unit expressions
@menu
* Operators:: The usual arithmetic operators, with a few extras
* Sums and Differences of Units:: Adding and subtracting units
* Numbers as Units:: A number is a dimensionless unit
* Built-in Functions:: Trigonometric functions, logarithms, roots
* Previous Result:: Inserting the result of the previous conversion
* Complicated Unit Expressions:: A complicated example
* Backwards Compatibility:: Alternate behavior for @samp{*} and @samp{-}
@end menu
@node Operators
@section Operators
@cindex operators
You can enter more complicated units by combining units with operations
such as multiplication, division, powers, addition, subtraction, and
parentheses for grouping. You can use the customary symbols for these
operators when @command{units} is invoked with its default options.
Additionally, @command{units} supports some extensions, including high
priority multiplication using a space, and a high priority numerical
division operator (@samp{|}) that can simplify some expressions.
@cindex products of units
@cindex quotients of units
@cindex units quotients
@cindex multiplication of units
@cindex division of units
@cindex operator, @samp{per}
@cindex @samp{per} operator
@cindex operator, space
@cindex operator, star (@samp{*})
@cindex star (@samp{*}) operator
@cindex @samp{*} operator
@cindex operator, slash (@samp{/})
@cindex slash (@samp{/}) operator
@cindex operator, solidus (@samp{/})
@cindex solidus (@samp{/}) operator
You multiply units using a space or an asterisk (@samp{*}).
The next example shows both forms:
@example
@group
You have: arabicfoot * arabictradepound * force
You want: ft lbf
* 0.7296
/ 1.370614
@end group
@end example
@noindent
You can divide units using the slash (@samp{/}) or with @samp{per}:
@example
@group
You have: furlongs per fortnight
You want: m/s
* 0.00016630986
/ 6012.8727
@end group
@end example
@cindex parentheses
@noindent
You can use parentheses for grouping:
@example
@group
You have: (1/2) kg / (kg/meter)
You want: league
* 0.00010356166
/ 9656.0833
@end group
@end example
@cindex operator precedence
@cindex parentheses
@noindent
Multiplication using a space has a higher precedence
than division using a slash and is evaluated left to right;
in effect, the first @samp{/} character marks the beginning of the
denominator of a unit expression.
This makes it simple to enter a quotient with several terms in the
denominator: @w{@samp{J / mol K}}.
The @samp{*} and @samp{/} operators have the same precedence, and are
evaluated left to right; if you multiply with @samp{*}, you must group
the terms in the denominator with parentheses: @w{@samp{J / (mol * K)}}.
@cindex fractions, numerical
@cindex numerical fractions
@cindex division of numbers
@cindex operator, vertical bar (@samp{|})
@cindex vertical bar (@samp{|}) operator
@cindex @samp{|} operator
The higher precedence of the space operator may not always be advantageous.
For example, @w{@samp{m/s s/day}} is equivalent to
@w{@samp{m / s s day}} and has dimensions of length per time cubed.
Similarly, @w{@samp{1/2 meter}} refers to a unit of reciprocal length
equivalent to 0.5/meter, perhaps not what you would intend if
you entered that expression. The get a half meter you would need to
use parentheses: @w{@samp{(1/2) meter}}.
The @samp{*} operator is convenient for multiplying a sequence of
quotients. For example, @w{@samp{m/s * s/day}} is equivalent to
@samp{m/day}. Similarly, you could write @w{@samp{1/2 * meter}} to get
half a meter.
The @command{units} program supports another option for numerical fractions:
you can indicate division of @emph{numbers} with the vertical bar
(@samp{|}), so if you wanted half a meter you could write
@w{@samp{1|2 meter}}.
You cannot use the vertical bar to indicate division of non-numerical
units (e.g., @samp{m|s} results in an error message).
@cindex powers
@cindex exponent operator
@cindex operator, caret (@samp{^})
@cindex operator, (@samp{**})
@cindex @samp{**} operator
@cindex parentheses
Powers of units can be specified using the @samp{^} character, as shown in
the following example, or by simple concatenation of a unit and its
exponent: @samp{cm3} is equivalent to @samp{cm^3};
if the exponent is more than one digit, the @samp{^} is required.
You can also use @samp{**} as an exponent operator.
@example
@group
You have: cm^3
You want: gallons
* 0.00026417205
/ 3785.4118
@end group
@end example
@noindent
Concatenation only works with a single unit name: if you write @samp{(m/s)2},
@command{units} will treat it as multiplication by 2.
@cindex prefixes and exponents
When a unit includes a prefix, exponent operators apply to the
combination, so @samp{centimeter3} gives cubic centimeters. If you
separate the prefix from the unit with any multiplication operator (e.g.,
@samp{centi meter^3}), the prefix is treated as a separate unit, so
the exponent applies only to the unit without the prefix. The second
example is equivalent to @samp{centi * (meter^3)}, and gives a hundredth
of a cubic meter, not a cubic centimeter. The @command{units} program
is limited internally to products of 99 units; accordingly, expressions
like @samp{meter^100} or @samp{joule^34} (represented internally as
@w{@samp{kg^34 m^68 / s^68}}) will fail.
The @samp{|}
operator has the highest precedence, so you can write the square root of
two thirds as @samp{2|3^1|2}.
The @samp{^} operator has the second highest precedence, and is
evaluated right to left, as usual:
@example
@group
You have: 5 * 2^3^2
You want:
Definition: 2560
@end group
@end example
@noindent
With a dimensionless base unit, any dimensionless exponent is meaningful
(e.g., @samp{pi^exp(2.371)}). Even though angle is sometimes treated as
dimensionless, exponents cannot have dimensions of angle:
@example
@group
You have: 2^radian
^
Exponent not dimensionless
@end group
@end example
@noindent
If the base unit is not dimensionless, the
exponent must be a rational number @w{@var{p}/@var{q}}, and the
dimension of the unit must be a power of @var{q}, so @samp{gallon^2|3}
works but @samp{acre^2|3} fails. An exponent using the slash (@samp{/})
operator (e.g., @samp{gallon^(2/3)}) is also acceptable; the parentheses
are needed because the precedence of @samp{^} is higher than that of
@samp{/}. Since @command{units} cannot represent dimensions with
exponents greater than 99, a fully reduced exponent must have
@w{@var{q} < 100}. When raising a non-dimensionless unit to a power,
@command{units} attempts to convert a decimal exponent to a rational
number with @w{@var{q} < 100}. If this is not possible
@command{units} displays an error message:
@example
@group
You have: ft^1.234
Base unit not dimensionless; rational exponent required
@end group
@end example
@noindent
A decimal exponent must match its rational representation to machine
precision, so @samp{acre^1.5} works but @samp{gallon^0.666} does not.
@node Sums and Differences of Units
@section Sums and Differences of Units
@cindex sums and differences of units
@cindex units, sums and differences
@cindex operator, plus (@samp{+})
@cindex plus (@samp{+}) operator
@cindex @samp{+} operator
@cindex operator, minus (@samp{-})
@cindex minus (@samp{-}) operator, subtraction
@cindex operator, hyphen (@samp{-}) as subtraction
@cindex @samp{-} as subtraction operator
@noindent
You may sometimes want to add values of
different units that are outside the SI.
You may also wish to use @command{units} as a
calculator that keeps track of units. Sums of conformable units are written with
the @samp{+} character, and differences with the @samp{-} character.
@cindex sums of units
@cindex addition of units
@cindex subtraction of units
@cindex differences of units
@example
@group
You have: 2 hours + 23 minutes + 32 seconds
You want: seconds
* 8612
/ 0.00011611705
@end group
@group
You have: 12 ft + 3 in
You want: cm
* 373.38
/ 0.0026782366
@end group
@group
You have: 2 btu + 450 ft lbf
You want: btu
* 2.5782804
/ 0.38785542
@end group
@end example
@noindent
The expressions that are added or subtracted must reduce to identical
expressions in primitive units, or an error message will be displayed:
@example
@group
You have: 12 printerspoint - 4 heredium
^
Illegal sum of non-conformable units
@end group
@end example
@cindex parentheses
@noindent
As usual, the precedence for @samp{+} and @samp{-} is lower than that of
the other operators.
A fractional quantity such as 2@tie{}1/2 cups can be given as
@samp{(2+1|2) cups}; the parentheses are necessary because
multiplication has higher precedence than addition. If you omit the
parentheses, @command{units} attempts to add @samp{2} and
@samp{1|2 cups}, and you get an error message:
@example
@group
You have: 2+1|2 cups
^
Illegal sum or difference of non-conformable units
@end group
@end example
@noindent
The expression could also be correctly written as @samp{(2+1/2) cups}.
If you write @samp{2@tie{}1|2 cups} the space is interpreted as
@emph{multiplication} so the result is the same as @samp{1 cup}.
The @samp{+} and @samp{-} characters sometimes appears in exponents like
@samp{3.43e+8}. This leads to an ambiguity in an expression like
@samp{3e+2 yC}. The unit @samp{e} is a small unit of charge, so this
can be regarded as equivalent to @samp{(3e+2) yC} or @samp{(3 e)+(2 yC)}.
This ambiguity is resolved by always interpreting @samp{+} and @samp{-} as part
of an exponent if possible.
@node Numbers as Units
@section Numbers as Units
@cindex numbers as units
For @command{units}, numbers are just another kind of unit. They can
appear as many times as you like and in any order in a unit expression.
For example, to find the volume of a box that is 2 ft by 3 ft by 12 ft
in steres, you could do the following:
@example
@group
You have: 2 ft 3 ft 12 ft
You want: stere
* 2.038813
/ 0.49048148
You have: $ 5 / yard
You want: cents / inch
* 13.888889
/ 0.072
@end group
@end example
@noindent
And the second example shows how the dollar sign in the units conversion
can precede the five. Be careful: @command{units} will interpret
@samp{$5} with no space as equivalent to @samp{dollar^5}.
@node Built-in Functions
@section Built-in Functions
@cindex functions, built in
Several built-in functions are provided: @samp{sin}, @samp{cos},
@samp{tan}, @samp{ln}, @samp{log}, @samp{log2}, @samp{exp}, @samp{acos},
@samp{atan} and @samp{asin}. The @samp{sin}, @samp{cos}, and @samp{tan}
functions require either a dimensionless argument or an argument with
dimensions of angle.
@example
@group
You have: sin(30 degrees)
You want:
Definition: 0.5
You have: sin(pi/2)
You want:
Definition: 1
You have: sin(3 kg)
^
Unit not dimensionless
@end group
@end example
@noindent
The other functions on the list require dimensionless arguments. The
inverse trigonometric functions return arguments with dimensions of
angle.
@cindex roots
@cindex square roots
If you wish to take roots of units, you may use the @samp{sqrt} or
@samp{cuberoot} functions. These functions require that the argument
have the appropriate root. You can obtain higher roots by using
fractional exponents:
@example
@group
You have: sqrt(acre)
You want: feet
* 208.71074
/ 0.0047913202
You have: (400 W/m^2 / stefanboltzmann)^(1/4)
You have:
Definition: 289.80882 K
You have: cuberoot(hectare)
^
Unit not a root
@end group
@end example
@node Previous Result
@section Previous Result
@cindex previous result
@cindex @samp{_} to use result of previous conversion
@noindent
You can insert the result of the previous conversion using the
underscore (@samp{_}). It is useful when you want to
convert the same input to several different units, for example
@example
@group
You have: 2.3 tonrefrigeration
You want: btu/hr
* 27600
/ 3.6231884e-005
You have: _
You want: kW
* 8.0887615
/ 0.12362832
@end group
@end example
@noindent
Suppose you want to do some deep frying that requires an oil depth of
2@tie{}inches. You have 1/2 gallon of oil, and want to know the
largest-diameter pan that will maintain the required depth. The
nonlinear unit @samp{circlearea} gives the @emph{radius} of the circle
(@pxref{Other Nonlinear Units}, for a more detailed description) in SI
units; you want the @emph{diameter} in @emph{inches}:
@example
@group
You have: 1|2 gallon / 2 in
You want: circlearea
0.10890173 m
@end group
@group
You have: 2 _
You want: in
* 8.5749393
/ 0.1166189
@end group
@end example
@noindent
In most cases, surrounding white space is optional, so the previous
example could have used @samp{2_}. If @samp{_} follows a non-numerical
unit symbol, however, the space is required:
@example
@group
You have: m_
^
Parse error
@end group
@end example
@noindent
When @samp{_} is followed by a digit, the operation is multiplication
rather than exponentiation, so that @samp{_2}, is equivalent to
@w{@samp{_ * 2}} rather than @samp{_^2}.
You can use the @samp{_} symbol any number of times; for example,
@example
@group
You have: m
You want:
Definition: 1 m
You have: _ _
You want:
Definition: 1 m^2
@end group
@end example
@noindent
Using @samp{_} before a conversion has been performed (e.g.,
immediately after invocation) generates an error:
@set codequoteundirected
@c man .if \n(.g .tr '\(aq
@example
@group
You have: _
^
No previous result; '_' not set
@end group
@end example
@c man .if \n(.g .tr ''
@clear codequoteundirected
@noindent
Accordingly, @samp{_} serves no purpose when @command{units} is invoked
non-interactively.
If @command{units} is invoked with the @option{--verbose} option
(@pxref{Invoking Units}), the value of @samp{_} is not expanded:
@example
@group
You have: mile
You want: ft
mile = 5280 ft
mile = (1 / 0.00018939394) ft
You have: _
You want: m
_ = 1609.344 m
_ = (1 / 0.00062137119) m
@end group
@end example
@noindent
You can give @samp{_} at the @w{@samp{You want:}} prompt, but it
usually is not very useful.
@node Complicated Unit Expressions
@section Complicated Unit Expressions
@cindex unit expressions, complicated
@noindent
The @command{units} program is especially helpful in ensuring accuracy
and dimensional consistency when converting lengthy unit expressions.
@c noman
@cindex Darcy--Weisbach equation
For example, one form of the Darcy--Weisbach fluid-flow equation is
@tex
$$
\Delta P = {8 \over \pi^2} \rho fL { Q^2 \over d^5}
$$
@end tex
@ifnottex
@example
Delta P = (8/pi^2) rho f L (Q^2 / d^5)
@end example
@end ifnottex
@noindent
where @math{ \Delta P} is the pressure drop, @math{\rho} is the mass density,
@math{f} is the (dimensionless) friction factor, @math{L} is the length
of the pipe, @math{Q} is the volumetric flow rate, and @math{d}
is the pipe diameter.
It might be desired to have the equation in the form
@tex
$$
\Delta P = A_1 \rho fL {Q^2 \over d^5}
$$
@end tex
@ifnottex
@example
Delta P = A1 rho f L (Q^2 / d^5)
@end example
@end ifnottex
@c end noman
@c -----------------------------------
@c nroff--assume neqn is not available
@c -----------------------------------
@c man .if t .ig ++
@c man For example, one form of the Darcy-Weisbach fluid-flow equation is
@c man .RS 5n
@c man .PP
@c man Delta \fIP\fP = (8 / pi)^2 (rho \fIfLQ\fP^2) / \fId\fP^5,
@c man .RE
@c man .PP
@c man where Delta \fIP\fP is the pressure drop, rho is the mass density,
@c man \fIf\fP is the (dimensionless) friction factor, \fIL\fP is the length
@c man of the pipe, \fIQ\fP is the volumetric flow rate, and \fId\fP
@c man is the pipe diameter.
@c man It might be desired to have the equation in the form
@c man .RS 5n
@c man .PP
@c man Delta \fIP\fP = A1 rho \fIfLQ\fP^2 / \fId\fP^5
@c man .RE
@c man .PP
@c man .++
@c -----
@c troff
@c -----
@c man .if n .ig ++
@c man .EQ
@c man delim $$
@c man .EN
@c don't assume en dash is available
@c man For example, one form of the Darcy\-Weisbach fluid-flow equation is
@c man .RS 5n
@c man .PP
@c man .EQ
@c man DELTA P = 8 over pi sup 2 rho fL Q sup 2 over d sup 5 ,
@c man .EN
@c man .RE
@c man .PP
@c man where $DELTA P$ is the pressure drop, $rho$ is the mass density,
@c man $f$ is the (dimensionless) friction factor, $L$ is the length
@c man of the pipe, $Q$ is the volumetric flow rate, and $d$
@c man is the pipe diameter.
@c man It might be desired to have the equation in the form
@c man .RS 5n
@c man .PP
@c man .EQ
@c man DELTA P = A sub 1 rho fL Q sup 2 over d sup 5
@c man .EN
@c man .RE
@c man .PP
@c man .EQ
@c man delim off
@c man .EN
@c man .++
@c
@noindent
that accepted the user's normal units; for typical units used in the US,
the required conversion could be something like
@example
@group
You have: (8/pi^2)(lbm/ft^3)ft(ft^3/s)^2(1/in^5)
You want: psi
* 43.533969
/ 0.022970568
@end group
@end example
@cindex parentheses
@noindent
The parentheses allow individual terms in the expression to be entered naturally,
as they might be read from the formula. Alternatively, the
multiplication could be done with the @samp{*} rather than a space;
then parentheses are needed only around @samp{ft^3/s} because of its
exponent:
@example
@group
You have: 8/pi^2 * lbm/ft^3 * ft * (ft^3/s)^2 /in^5
You want: psi
* 43.533969
/ 0.022970568
@end group
@end example
@noindent
Without parentheses, and using spaces for multiplication, the previous
conversion would need to be entered as
@example
@group
You have: 8 lb ft ft^3 ft^3 / pi^2 ft^3 s^2 in^5
You want: psi
* 43.533969
/ 0.022970568
@end group
@end example
@node Backwards Compatibility
@section Backwards Compatibility: @samp{*} and @samp{-}
@cindex backwards compatibility
@cindex compatibility
@cindex compatibility with earlier versions
The original @command{units} assigned multiplication a higher
precedence than division using the slash. This differs from the
usual precedence rules, which give multiplication and division equal
precedence, and can be confusing for people who think
of units as a calculator.
The star operator (@samp{*}) included in this @command{units} program
has, by default, the same precedence as division,
and hence follows the usual precedence rules. For backwards
compatibility you can invoke @command{units}
with the @option{--oldstar}
option. Then @samp{*} has a higher precedence than
division, and the same precedence as multiplication using the space.
@cindex @samp{-} as multiplication operator
@cindex operator, hyphen (@samp{-}) as multiplication
@cindex multiplication, hyphen
@cindex hyphen as multiplication operator
Historically, the hyphen (@samp{-}) has been used in technical
publications to indicate products of units, and the original
@command{units} program treated it as a multiplication operator.
Because @command{units} provides
several other ways to obtain unit products, and because @samp{-} is a
subtraction operator in general algebraic expressions, @command{units}
treats the binary @samp{-} as a subtraction operator by default.
For backwards compatibility use the @option{--product} option, which
causes @command{units} to treat the binary @samp{-} operator as a
product operator. When @samp{-} is a multiplication operator
it has the same precedence as multiplication with a space, giving it a
higher precedence than division.
When @samp{-} is used as a unary operator it negates its operand.
Regardless of the @command{units} options, if
@samp{-} appears after @samp{(} or after
@samp{+} then it will act as a negation operator. So you can always compute 20
degrees minus 12 minutes by entering @samp{20@tie{}degrees + -12@tie{}arcmin}.
You must use this construction when you define new units because you
cannot know what options will be in force when your definition is
processed.
@cindex defining units with `-'
@node Nonlinear Conversions
@chapter Nonlinear Unit Conversions
@cindex nonlinear unit conversions
Nonlinear units are represented using functional notation. They make
possible nonlinear unit conversions such as temperature.
@menu
* Temperature Conversions:: Conversion between temperature scales
* Other Nonlinear Units:: Ring size, wire gauge, abrasive grit size
@end menu
@node Temperature Conversions
@section Temperature Conversions
@cindex temperature conversions
Conversions between temperatures are different from linear conversions
between temperature @emph{increments}---see the example below. The
absolute temperature conversions are handled by units starting with
@samp{temp}, and you must use functional notation.
The temperature-increment conversions are done using units starting
with @samp{deg} and they do not require functional notation.
@example
@group
You have: tempF(45)
You want: tempC
7.2222222
You have: 45 degF
You want: degC
* 25
/ 0.04
@end group
@end example
@noindent
Think of @samp{tempF(@var{x})} not as a function but as a notation that
indicates that @var{x} should have units of @samp{tempF} attached to
it. @xref{Defining Nonlinear Units}. The first conversion shows that if it's 45
degrees Fahrenheit outside, it's 7.2 degrees Celsius. The second
conversion indicates that a change of 45 degrees Fahrenheit corresponds
to a change of 25 degrees Celsius. The conversion from
@samp{tempF(@var{x})} is to absolute temperature, so that
@example
@group
You have: tempF(45)
You want: degR
* 504.67
/ 0.0019814929
@end group
@end example
@noindent
gives the same result as
@example
@group
You have: tempF(45)
You want: tempR
* 504.67
/ 0.0019814929
@end group
@end example
@noindent
But if you convert @samp{tempF(@var{x})} to @samp{degC}, the output is
probably not what you expect:
@example
@group
You have: tempF(45)
You want: degC
* 280.37222
/ 0.0035666871
@end group
@end example
@noindent
The result is the temperature in K, because @samp{degC} is defined as
@samp{K}, the Kelvin. For consistent results, use the @samp{temp@var{X}} units
when converting to a temperature rather than converting a temperature
increment.
The @samp{tempC()} and @samp{tempF()} definitions are limited to
positive absolute temperatures, and giving a value that would result in
a negative absolute temperature generates an error message:
@example
@group
You have: tempC(-275)
^
Argument of function outside domain
^
@end group
@end example
@node Other Nonlinear Units
@section Other Nonlinear Units
@cindex nonlinear units, other
Some other examples of nonlinear units are numerous different ring
sizes and wire gauges, the grit sizes used for abrasives, the decibel
scale, shoe size, scales for the density of sugar (e.g., baume).
The standard data file also supplies units for computing the area of a
circle and the volume of a sphere. See the standard units data file
for more details.
Wire gauges
with multiple zeroes are signified using negative numbers where two
zeroes is @samp{-1}. Alternatively, you can use the synonyms @samp{g00},
@samp{g000}, and so on that are defined in the standard units data file.
@cindex wire gauge
@example
@group
You have: wiregauge(11)
You want: inches
* 0.090742002
/ 11.020255
You have: brwiregauge(g00)
You want: inches
* 0.348
/ 2.8735632
You have: 1 mm
You want: wiregauge
18.201919
You have: grit_P(600)
You want: grit_ansicoated
342.76923
@end group
@end example
@noindent
The last example shows the conversion from P graded sand paper,
which is the European standard and may be marked ``P600'' on the back,
to the USA standard.
@cindex abrasive grit size
You can compute the area of a circle using the nonlinear unit,
@samp{circlearea}. You can also do this using the circularinch or
circleinch. The next example shows two ways to compute the area of a
circle with a five inch radius and one way to compute the volume of a
sphere with a radius of one meter.
@cindex circle, area of
@cindex sphere, volume of
@example
@group
You have: circlearea(5 in)
You want: in2
* 78.539816
/ 0.012732395
You have: 10^2 circleinch
You want: in2
* 78.539816
/ 0.012732395
You have: spherevol(meter)
You want: ft3
* 147.92573
/ 0.0067601492
@end group
@end example
@noindent
The inverse of a nonlinear conversion is indicated by prefixing a tilde
(@samp{~}) to the nonlinear unit name:
@example
@group
You have: ~wiregauge(0.090742002 inches)
You want:
Definition: 11
@end group
@end example
@noindent
You can give a nonlinear unit definition without an argument or
parentheses, and press @key{Enter} at the @w{@samp{You want:}} prompt to
get the definition of a nonlinear unit; if the definition is not valid
for all real numbers, the range of validity is also given. If the
definition requires specific units this information is also
displayed:
@example
@group
You have: tempC
Definition: tempC(x) = x K + stdtemp
defined for x >= -273.15
You have: ~tempC
Definition: ~tempC(tempC) = (tempC +(-stdtemp))/K
defined for tempC >= 0 K
You have: circlearea
Definition: circlearea(r) = pi r^2
r has units m
@end group
@end example
@noindent
To see the definition of the inverse use the @samp{~} notation. In
this case the parameter in the functional definition will
usually be the name of the unit. Note that the inverse for
@samp{tempC} shows that it requires units of @samp{K} in the
specification of the allowed range of values.
Nonlinear unit conversions are described in more detail in
@ref{Defining Nonlinear Units}.
@node Unit Lists
@chapter Unit Lists: Conversion to Sums of Units
@cindex sums of units
@cindex unit lists
@cindex units, sums of
Outside of the SI, it is sometimes desirable to convert a single
unit to a sum of units---for example, feet to feet plus inches.
The conversion @emph{from} sums of units was described in
@ref{Sums and Differences of Units}, and is a simple matter of adding
the units with the @samp{+} sign:
@example
@group
You have: 12 ft + 3 in + 3|8 in
You want: ft
* 12.28125
/ 0.081424936
@end group
@end example
@noindent
Although you can similarly write a sum of units to convert @emph{to},
the result will not be the conversion to the units in the sum, but
rather the conversion to the particular sum that you have entered:
@example
@group
You have: 12.28125 ft
You want: ft + in + 1|8 in
* 11.228571
/ 0.089058524
@end group
@end example
@noindent
The unit expression given at the @w{@samp{You want:}} prompt is
equivalent to asking for conversion to multiples of
@samp{1@tie{}ft + 1@tie{}in + 1|8@tie{}in}, which is 1.09375 ft, so the
conversion in the previous example is equivalent to
@example
@group
You have: 12.28125 ft
You want: 1.09375 ft
* 11.228571
/ 0.089058524
@end group
@end example
@noindent
In converting to a sum of units like miles, feet and inches, you
typically want the largest integral value for the first unit, followed
by the largest integral value for the next, and the remainder converted
to the last unit.
You can do this conversion easily with @command{units} using a special
syntax for lists of units. You must list the desired units in order
from largest to smallest, separated by the semicolon (@samp{;})
character:
@example
@group
You have: 12.28125 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3|8 in
@end group
@end example
@noindent
The conversion always gives integer coefficients on the units in the
list, except possibly the last unit when the conversion is not exact:
@example
@group
You have: 12.28126 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3.00096 * 1|8 in
@end group
@end example
@noindent
The order in which you list the units is important:
@example
@group
You have: 3 kg
You want: oz;lb
105 oz + 0.051367866 lb
You have: 3 kg
You want: lb;oz
6 lb + 9.8218858 oz
@end group
@end example
@noindent
Listing ounces before pounds produces a technically correct result,
but not a very useful one. You must list the units in descending
order of size in order to get the most useful result.
Ending a unit list with the separator @samp{;}
has the same effect as repeating the last
unit on the list, so @samp{ft;in;1|8 in;} is equivalent to
@samp{ft;in;1|8 in;1|8 in}. With the example above, this gives
@example
@group
You have: 12.28126 ft
You want: ft;in;1|8 in;
12 ft + 3 in + 3|8 in + 0.00096 * 1|8 in
@end group
@end example
@noindent
in effect separating the integer and fractional parts of the
coefficient for the last unit. If you instead
prefer to round the last coefficient to an integer
you can do this with the @option{--round} (@option{-r}) option.
With the previous example, the result is
@example
@group
You have: 12.28126 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3|8 in (rounded down to nearest 1|8 in)
@end group
@end example
@noindent
When you use the @option{-r} option, repeating the last unit on the
list has no effect (e.g., @samp{ft;in;1|8 in;1|8 in} is equivalent to
@samp{ft;in;1|8 in}), and hence neither does ending a list with a
@samp{;}. With a single unit and the @option{-r} option, a terminal @samp{;}
@emph{does} have an effect: it causes @command{units} to treat the
single unit as a list and produce a rounded value for the single unit.
Without the extra @samp{;}, the @option{-r} option has no effect on
single unit conversions. This example shows the output using the
@option{-r} option:
@example
@group
You have: 12.28126 ft
You want: in
* 147.37512
/ 0.0067854058
You have: 12.28126 ft
You want: in;
147 in (rounded down to nearest in)
@end group
@end example
@noindent
Each unit that appears in the list must be conformable with the first
unit on the list, and of course the listed units must also be
conformable with the unit that you enter at the @w{@samp{You have:}}
prompt.
@example
@group
You have: meter
You want: ft;kg
^
conformability error
ft = 0.3048 m
kg = 1 kg
@end group
@group
You have: meter
You want: lb;oz
conformability error
1 m
0.45359237 kg
@end group
@end example
@noindent
In the first case, @command{units} reports the disagreement between
units appearing on the list. In the second case, @command{units}
reports disagreement between the unit you entered and the desired
conversion. This conformability error is based on the first
unit on the unit list.
Other common candidates for conversion to sums of units are
angles and time:
@example
@group
You have: 23.437754 deg
You want; deg;arcmin;arcsec
23 deg + 26 arcmin + 15.9144 arcsec
@end group
@group
You have: 7.2319 hr
You want: hr;min;sec
7 hr + 13 min + 54.84 sec
@end group
@end example
@noindent
In North America, recipes for cooking typically measure ingredients by
volume, and use units that are not always convenient multiples of each
other. Suppose that you have a recipe for 6 and you wish to make a
portion for 1. If the recipe calls for 2@tie{}1/2 cups of an
ingredient, you might wish to know the measurements in terms of
measuring devices you have available, you could use @command{units} and
enter
@example
@group
You have: (2+1|2) cup / 6
You want: cup;1|2 cup;1|3 cup;1|4 cup;tbsp;tsp;1|2 tsp;1|4 tsp
1|3 cup + 1 tbsp + 1 tsp
@end group
@end example
@noindent
By default, if a unit in a list begins with fraction of the form
1|@var{x} and its multiplier is an integer, the fraction is given as
the product of the multiplier and the numerator; for example,
@example
@group
You have: 12.28125 ft
You want: ft;in;1|8 in;
12 ft + 3 in + 3|8 in
@end group
@end example
@noindent
In many cases, such as the example above, this is what is wanted, but
sometimes it is not. For example, a cooking recipe for 6 might call
for 5@tie{}1/4 cup of an ingredient, but you want a portion for 2, and
your 1-cup measure is not available; you might try
@example
@group
You have: (5+1|4) cup / 3
You want: 1|2 cup;1|3 cup;1|4 cup
3|2 cup + 1|4 cup
@end group
@end example
@noindent
This result might be fine for a baker who has a 1@tie{}1/2-cup measure
(and recognizes the equivalence), but it may not be as useful to
someone with more limited set of measures, who does want to do
additional calculations, and only wants to know ``How many 1/2-cup
measures to I need to add?'' After all, that's what was actually
asked. With the @option{--show-factor} option, the factor will not be
combined with a unity numerator, so that you get
@example
@group
You have: (5+1|4) cup / 3
You want: 1|2 cup;1|3 cup;1|4 cup
3 * 1|2 cup + 1|4 cup
@end group
@end example
@noindent
A user-specified fractional unit with a numerator other than 1 is never
overridden, however---if a unit list specifies @samp{3|4 cup;1|2 cup},
a result equivalent to 1@tie{}1/2 cups will always be shown as
@samp{2 * 3|4@tie{}cup} whether or not the @option{--show-factor} option
is given.
Some applications for unit lists may be less obvious. Suppose that you
have a postal scale and wish to ensure that it's accurate at 1@tie{}oz,
but have only metric calibration weights. You might try
@example
@group
You have: 1 oz
You want: 100 g;50 g; 20 g;10 g;5 g;2 g;1 g;
20 g + 5 g + 2 g + 1 g + 0.34952312 * 1 g
@end group
@end example
@noindent
You might then place one each of the 20@tie{}g, 5@tie{}g, 2@tie{}g, and
1@tie{}g weights on the scale and hope that it indicates close to
@example
@group
You have: 20 g + 5 g + 2 g + 1 g
You want: oz;
0.98767093 oz
@end group
@end example
@noindent
Appending @samp{;} to @samp{oz} forces a one-line display that includes
the unit; here the integer part of the result is zero, so it is not
displayed.
A unit list such as
@example
cup;1|2@tie{}cup;1|3@tie{}cup;1|4@tie{}cup;tbsp;tsp;1|2@tie{}tsp;1|4@tie{}tsp
@end example
@noindent
can be tedious to enter. The @command{units} program provides shorthand names
for some common combinations:
@example
hms @r{hours, minutes, seconds}
dms @r{angle: degrees, minutes, seconds}
time @r{years, days, hours, minutes and seconds}
usvol @r{US cooking volume: cups and smaller}
@end example
@noindent
Using these shorthands, or @dfn{unit list aliases},
you can do the following conversions:
@example
@group
You have: anomalisticyear
You want: time
1 year + 25 min + 3.4653216 sec
You have: 1|6 cup
You want: usvol
2 tbsp + 2 tsp
@end group
@end example
@noindent
You cannot combine a unit list alias with other units: it must appear
alone at the @w{@samp{You want:}} prompt.
You can display the definition of a unit list alias by entering it at
the @w{@samp{You have:}} prompt:
@example
@group
You have: dms
Definition: unit list, deg;arcmin;arcsec
@end group
@end example
@noindent
When you specify compact output with @option{--compact},
@option{--terse} or @option{-t} and perform conversion to a unit list,
@command{units} lists the conversion factors for each unit in the
list, separated by semicolons.
@example
@group
You have: year
You want: day;min;sec
365;348;45.974678
@end group
@end example
@noindent
Unlike the case of regular
output, zeros @emph{are} included in this output list:
@example
@group
You have: liter
You want: cup;1|2 cup;1|4 cup;tbsp
4;0;0;3.6280454
@end group
@end example
@node Logging Calculations
@chapter Logging Calculations
@cindex logging calculations
@cindex log file
The @option{--log} option allows you to save the results of calculations
in a file; this can be useful if you need a permanent record of your
work. For example, the fluid-flow conversion in
@ref{Complicated Unit Expressions}, is lengthy, and if you were to use
it in designing a piping system, you might want a record of it for the
project file. If the interactive session
@example
@group
# Conversion factor A1 for pressure drop
# dP = A1 rho f L Q^2/d^5
You have: (8/pi^2) (lbm/ft^3)ft(ft^3/s)^2(1/in^5) # Input units
You want: psi
* 43.533969
/ 0.022970568
@end group
@end example
@noindent
were logged, the log file would contain
@example
@group
### Log started Fri Oct 02 15:55:35 2015
# Conversion factor A1 for pressure drop
# dP = A1 rho f L Q^2/d^5
From: (8/pi^2) (lbm/ft^3)ft(ft^3/s)^2(1/in^5) # Input units
To: psi
* 43.533969
/ 0.022970568
@end group
@end example
@noindent
The time is written to the log file when the file is opened.
The use of comments can help clarify the meaning of calculations for
the log.
The log includes conformability errors between the units at the
@w{@samp{You have:}} and @w{@samp{You want:}} prompts, but not other
errors, including lack of conformability of items in sums or differences
or among items in a unit list. For example, a conversion between zenith
angle and elevation angle could involve
@example
@group
You have: 90 deg - (5 deg + 22 min + 9 sec)
^
Illegal sum or difference of non-conformable units
You have: 90 deg - (5 deg + 22 arcmin + 9 arcsec)
You want: dms
84 deg + 37 arcmin + 51 arcsec
You have: _
You want: deg
* 84.630833
/ 0.011816024
You have:
@end group
@end example
@noindent
The log file would contain
@example
@group
From: 90 deg - (5 deg + 22 arcmin + 9 arcsec)
To: deg;arcmin;arcsec
84 deg + 37 arcmin + 51 arcsec
From: _
To: deg
* 84.630833
/ 0.011816024
@end group
@end example
@noindent
The initial entry error (forgetting that minutes have dimension of time,
and that arcminutes must be used for dimensions of angle) does not
appear in the output. When converting to a unit list alias,
@command{units} expands the alias in the log file.
The @samp{From:} and @samp{To:} tags are written to the log file even if
the @option{--quiet} option is given. If the log file exists when
@command{units} is invoked, the new results are appended to the log file.
The time is written to the log file each time the file is opened.
The @option{--log} option is ignored when @command{units} is used
non-interactively.
@node Invoking Units
@chapter Invoking @command{units}
@cindex invoking units
@cindex command-line options
You invoke @command{units} like this:
@example
units [@var{options}] [@var{from-unit} [@var{to-unit}]]
@end example
@noindent
If the @var{from-unit} and @var{to-unit} are omitted, the program
will use interactive prompts to determine which conversions to perform.
@xref{Interactive Use}.
If both @var{from-unit} and @var{to-unit} are given, @command{units} will
print the result of that single conversion and then exit.
If only @var{from-unit} appears on the command line, @command{units} will
display the definition of that unit and exit.
Units specified on the command line may need
to be quoted to protect them from shell interpretation and to group
them into two arguments. @xref{Command Line Use}.
The default behavior of @command{units} can be changed by various
options given on the command line. In most cases, the options may be
given in either short form (a single @samp{-} followed by a single
character)
or long form (@samp{--} followed by a word or hyphen-separated words).
Short-form options are cryptic but require
less typing; long-form options require more typing but are more
explanatory and may be more mnemonic. With long-form options you need
only enter sufficient characters to uniquely identify the option to
the program. For example, @samp{--out@tie{}%f} works, but
@samp{--o@tie{}%f} fails because @command{units} has other long options
beginning with @samp{o}. However, @samp{--q} works because
@samp{--quiet} is the only long option beginning with @samp{q}.
Some options require
arguments to specify a value (e.g., @samp{-d@tie{}12} or
@samp{--digits@tie{}12}). Short-form options that do not take
arguments may be concatenated (e.g., @samp{-erS} is equivalent to
@samp{-e@tie{}-r@tie{}-S}); the last option in such a list may be one
that takes an argument (e.g., @samp{-ed@tie{}12}). With short-form
options, the space between an option and its argument is optional (e.g.,
@samp{-d12} is equivalent to @samp{-d@tie{}12}). Long-form options may
not be concatenated, and the space between a long-form option and its
argument is required. Short-form and long-form options may be
intermixed on the command line. Options may be given in any order, but
when incompatible options (e.g., @option{--output-format} and
@option{--exponential}) are given in combination, behavior is controlled
by the last option given. For example, @samp{-o%.12f@tie{}-e} gives
exponential format with the default eight significant digits).
The following options are available:
@table @env
@item -c
@itemx --check
@opindex -c @r{(option for} @command{units}@r{)}
@opindex --check @r{(option for} @command{units}@r{)}
Check that all units and prefixes defined in the units data file reduce
to primitive units. Print a list of all units that
cannot be reduced. Also display some other diagnostics about
suspicious definitions in the units data file. Only definitions active
in the current locale are checked. You should always run
@command{units} with this option after modifying a units data file.
@item --check-verbose
@itemx --verbose-check
@opindex --check-verbose @r{(option for} @command{units}@r{)}
@opindex --verbose-check @r{(option for} @command{units}@r{)}
Like the @option{--check} option, this option prints a list of units that
cannot be reduced. But to help find unit definitions that cause
endless loops,
it lists the units as they are checked.
If @command{units} hangs, then the last unit to be printed has a bad
definition. Only definitions active in the current locale are checked.
@item -d @var{ndigits}
@itemx --digits @var{ndigits}
@opindex -d @r{(option for} @command{units}@r{)}
@opindex --digits @r{(option for} @command{units}@r{)}
Set the number of significant digits in the output to the value
specified (which must be greater than zero). For example,
@samp{-d@tie{}12} sets the number of significant digits to 12.
With exponential output @command{units} displays one digit to the left
of the decimal
@c man point
@c noman
point@footnote{This document refers to ``decimal point,'' but strictly,
the @dfn{radix} separates the integer and fractional parts of a
floating-point number; in English-speaking countries, the radix is a
point (@samp{.}), but in most other countries it is a comma (@samp{,}).}
@c end noman
and eleven digits to the right of the decimal point.
On most systems, the maximum number of internally meaningful digits is
15; if you specify a greater number than your system's maximum, @command{units}
will print a warning and set the number to the largest meaningful
value. To directly set the maximum value, give an argument
of @code{max} (e.g., @samp{-d@tie{}max}). Be aware, of course, that
``significant'' here refers only to the @emph{display} of numbers; if
results depend on physical constants not known to this precision, the
physically meaningful precision may be less than that shown. The
@option{--digits} option conflicts with the @option{--output-format}
option.
@item -e
@itemx --exponential
@opindex -e @r{(option for} @command{units}@r{)}
@opindex --exponential @r{(option for} @command{units}@r{)}
Set the numeric output format to exponential (i.e., scientific
notation), like that used in the Unix @command{units} program.
The default precision is eight significant digits (seven digits to the
right of the decimal point); this can be changed with the
@option{--digits} option. The @option{--exponential}
option conflicts with the @option{--output-format} option.
@item -o @var{format}
@itemx --output-format @var{format}
@opindex -o @r{(option for} @command{units}@r{)}
@opindex --output-format @r{(option for} @command{units}@r{)}
This option affords complete control over the numeric output format
using the specified @var{format}. The format is a single floating
point numeric format for the @code{printf()} function in the
C programming language. All compilers support the format types @samp{g}
and @samp{G} to specify significant digits, @samp{e} and @samp{E} for
scientific notation, and @samp{f} for fixed-point decimal.
The ISO C99 standard introduced the @samp{F} type for fixed-point
decimal and the @samp{a} and @samp{A} types for hexadecimal
floating point; these types are allowed with compilers that support
them. The default format is @samp{%.8g}; for greater precision, you
could specify @samp{-o@tie{}%.15g}. @xref{Numeric Output Format}, and
the documentation for @code{printf()} for more detailed descriptions of the
format specification. The @option{--output-format} option affords the
greatest control of the output appearance, but requires at least
rudimentary knowledge of the @code{printf()} format syntax. If you
don't want to bother with the @code{printf()} syntax, you can specify
greater precision more simply with the @option{--digits} option or
select exponential format with @option{--exponential}. The
@option{--output-format} option is incompatible with the
@option{--exponential} and @option{--digits} options.
@item -f @var{filename}
@itemx --file @var{filename}
@opindex -f @r{(option for} @command{units}@r{)}
@opindex --file @r{(option for} @command{units}@r{)}
Instruct @command{units} to load the units file @var{filename}. You
can specify up to 25 units files on the command line. When you use
this option, @command{units} will load @emph{only} the files you list
on the command line; it will not load the standard file or your
personal units file unless you explicitly list them. If @var{filename}
is the empty string (@w{@samp{-f ""}}), the default units file (or that
specified by @env{UNITSFILE}) will be loaded in addition to any others
specified with @samp{-f}.
@item -L @var{logfile}
@itemx --log @var{logfile}
@opindex -L @r{(option for} @command{units}@r{)}
@opindex --log @r{(option for} @command{units}@r{)}
Save the results of calculations in the file @var{logfile}; this can be
useful if it is important to have a record of unit conversions or other
calculations that are to be used extensively or in a critical activity
such as a program or design project. If @var{logfile} exits, the new
results are appended to the file.
This option is ignored when @command{units} is used non-interactively.
@xref{Logging Calculations}, for a more detailed description and some
examples.
@item -H @var{filename}
@itemx --history @var{filename}
@opindex -f @r{(option for} @command{units}@r{)}
@opindex --file @r{(option for} @command{units}@r{)}
Instruct @command{units} to save history to @var{filename}, so that a
record of your commands is available for retrieval across different
@command{units} invocations. To prevent the history from being saved
set @var{filename} to the emptry string (@w{@samp{-f ""}}). This
option has no effect if readline is not available.
@item -h
@itemx --help
@opindex -h @r{(option for} @command{units}@r{)}
@opindex --help @r{(option for} @command{units}@r{)}
Print out a summary of the options for @command{units}.
@item -m
@itemx --minus
@opindex -m @r{(option for} @command{units}@r{)}
@opindex --minus @r{(option for} @command{units}@r{)}
Causes @samp{-} to be interpreted as a subtraction operator. This is
the default behavior.
@item -p
@itemx --product
@opindex -p @r{(option for} @command{units}@r{)}
@opindex --product @r{(option for} @command{units}@r{)}
Causes @samp{-} to be interpreted as a multiplication operator when it
has two operands. It will act as a negation operator when it has only one
operand: @samp{(-3)}. By default @samp{-} is treated as a
subtraction operator.
@item --oldstar
@opindex --oldstar @r{(option for} @command{units}@r{)}
Causes @samp{*} to have the old-style precedence, higher than the
precedence of division so that @samp{1/2*3} will equal @samp{1/6}.
@item --newstar
@opindex --newstar @r{(option for} @command{units}@r{)}
Forces @samp{*} to have the new (default) precedence that follows
the usual rules of algebra: the precedence of @samp{*} is the same as
the precedence of @samp{/}, so that @samp{1/2*3} will equal @samp{3/2}.
@item --compact
@opindex --compact @r{(option for} @command{units}@r{)}
Give compact output featuring only the conversion factor. This turns
off the @option{--verbose} option.
@item -q
@itemx --quiet
@itemx --silent
@opindex -q @r{(option for} @command{units}@r{)}
@opindex --quiet @r{(option for} @command{units}@r{)}
@opindex --silent @r{(option for} @command{units}@r{)}
Suppress prompting of the user for units and the display of statistics
about the number of units loaded.
@item -n
@itemx --nolists
Disable conversion to unit lists.
@item -r
@itemx --round
When converting to a combination of units given by a unit list, round
the value of the last unit in the list to the nearest integer.
@item -S
@itemx --show-factor
When converting to a combination of units specified in a list,
always show a non-unity factor before a unit that
begins with a fraction with a unity denominator. By default, if the
unit in a list begins with fraction of the form 1|@var{x} and
its multiplier is an integer other than 1, the fraction is given as the
product of the multiplier and the numerator (e.g., @samp{3|8@tie{}in}
rather than @samp{3 * 1|8@tie{}in}). In some cases, this is not what is
wanted; for example, the results for a cooking recipe might show
@samp{3 * 1|2@tie{}cup} as @samp{3|2@tie{}cup}.
With the @option{--show-factor} option, a
result equivalent to 1.5 cups will display as @samp{3 * 1|2@tie{}cup}
rather than @samp{3|2@tie{}cup}. A user-specified fractional unit with
a numerator other than 1 is never overridden, however---if a unit list
specifies @samp{3|4 cup;1|2 cup}, a result equivalent to 1@tie{}1/2 cups
will always be shown as @samp{2 * 3|4@tie{}cup} whether or not the
@option{--show-factor} option is given.
@item -s
@itemx --strict
@opindex -s @r{(option for} @command{units}@r{)}
@opindex --strict @r{(option for} @command{units}@r{)}
Suppress conversion of units to their reciprocal units. For
example, @command{units} will normally convert hertz to seconds
because these units are reciprocals of each other. The strict option
requires that units be strictly conformable to perform a conversion, and
will give an error if you attempt to convert hertz to seconds.
@item -1
@itemx --one-line
@opindex -1 @r{(option for} @command{units}@r{)}
@opindex --one-line @r{(option for} @command{units}@r{)}
Give only one line of output (the forward conversion). Do not print
the reverse conversion. If a reciprocal conversion is
performed then @command{units} will still print the ``reciprocal
conversion'' line.
@item -t
@itemx --terse
@opindex -t @r{(option for} @command{units}@r{)}
@opindex --terse @r{(option for} @command{units}@r{)}
Give terse output when converting units. This option can be used when
calling @command{units} from another program so that the output is easy to
parse. This option has the combined
effect of these options: @option{--strict} @option{--quiet} @option{--one-line}
@option{--compact}. When combined with @option{--version} it produces
a display showing only the program name and version number.
@item -v
@itemx --verbose
@opindex -v @r{(option for} @command{units}@r{)}
@opindex --verbose @r{(option for} @command{units}@r{)}
Give slightly more verbose output when converting units. When combined
with the @option{-c} option this gives the same effect as
@option{--check-verbose}. When combined with @option{--version}
produces a more detailed output, equivalent to the @option{--info}
option.
@item -V
@itemx --version
@opindex -V @r{(option for} @command{units}@r{)}
@opindex --version @r{(option for} @command{units}@r{)}
Print the program version number, tell whether the @command{readline}
library has been included, tell whether UTF-8 support has been included;
give the locale, the location of the default units data file, and the
location of the personal units data file; indicate if the personal units
data file does not exist.
When given in combination with the @option{--terse} option, the program
prints only the version number and exits.
When given in combination with the @option{--verbose} option, the
program, the @option{--version} option has the same effect as the
@option{--info} option below.
@item -I
@itemx --info
@opindex -I @r{(option for} @command{units}@r{)}
@opindex --info @r{(option for} @command{units}@r{)}
Print the information given with the @option{--version} option, show the
pathname of the units program, show the status of the @env{UNITSFILE}
and @env{MYUNITSFILE} environment variables, and additional information
about how @command{units} locates the related files. On systems running
Microsoft Windows, the status of the @env{UNITSLOCALE} environment
variable and information about the related locale map are also given.
This option is usually of interest only to developers and
administrators, but it can sometimes be useful for troubleshooting.
Combining the @option{--version} and @option{--verbose} options has the
same effect as giving @option{--info}.
@item -U
@itemx --unitsfile
@opindex -U @r{(option for} @command{units}@r{)}
@opindex --unitsfile @r{(option for} @command{units}@r{)}
Print the location of the default units data file and exit; if the file
cannot be found, print ``Units data file not found''.
@item -l @var{locale}
@itemx --locale @var{locale}
Print the information given with the @option{--version} option, show the
@opindex --locale @r{(option for} @command{units}@r{)}
@opindex -l @r{(option for} @command{units}@r{)}
Force a specified locale such as @samp{en_GB} to get British
definitions by default. This overrides the locale determined from
system settings or environment variables.
@xref{Locale}, for a description of locale format.
@end table
@node Defining Your Own Units
@chapter Adding Your Own Definitions
@menu
* Units Data Files:: Where are units defined?
* Defining New Units:: Writing your own unit and prefix definitions
* Defining Nonlinear Units:: Writing your own nonlinear unit definitions
* Piecewise Linear Units:: Writing your own piecewise linear definitions
* Defining Unit List Aliases:: Writing your own unit list aliases
@end menu
@node Units Data Files
@section Units Data Files
@cindex additional units data files
@cindex data files, additional
@cindex units data files, additional
@cindex @samp{!include}
@cindex command, @samp{!include}
@cindex including additional units data files
The units and prefixes that @command{units} can convert are
defined in the units
data file, typically @file{/usr/share/units/definitions.units}.
If you can't find this file, run @command{units@tie{}--version} to get
information on the file locations for your installation. Although you
can extend or modify this data file if you have appropriate user
privileges, it's usually better to put extensions in separate files so
that the definitions will be preserved if you update @command{units}.
You can include additional data files in the units database using
the @samp{!include} command in the standard units data file. For
example
@example
!include /usr/local/share/units/local.units
@end example
@noindent
might be appropriate for a site-wide supplemental data file.
The location of the @samp{!include} statement in the standard units
data file is important; later definitions replace earlier ones,
so any definitions in an included file will override definitions before
the @samp{!include} statement in the standard units data file.
With normal invocation, no warning is given about redefinitions; to
ensure that you don't have an unintended redefinition, run
@command{units@tie{}-c} after making changes to any units data file.
@cindex personal units data file
@cindex units data file, personal
If you want to add your own units in addition to or in place of
standard or site-wide supplemental units data files, you can include
them in the @file{.units} file in your home directory. If this
file exists it is read after the standard units data file, so that any
definitions in this file will replace definitions of the same units in
the standard data file or in files included from the standard data
file. This file will not be read if any units files are specified on
the command line. (Under Windows the personal units file is
named @file{unitdef.units}.) Running @w{@command{units -V}} will
display the location and name of your personal units file.
The @command{units} program first tries to determine your home
directory from the @env{HOME} environment variable. On systems running
Microsoft Windows, if @env{HOME} does not exist, @command{units}
attempts to find your home directory from @env{HOMEDRIVE},
@env{HOMEPATH} and @env{USERPROFILE}.
@cindex MYUNITSFILE environment variable
@cindex environment variable, MYUNITSFILE
You can specify an arbitrary file as your personal units data file with
the @env{MYUNITSFILE} environment variable; if this variable exists, its
value is used without searching your home directory.
The default units data files are described in more detail in
@ref{Data Files}.
@node Defining New Units
@section Defining New Units and Prefixes
@cindex defining units
@cindex units, definition of
@cindex units definitions, adding
@cindex units definitions, changing
@cindex prefixes, definition of
@cindex defining prefixes
@cindex primitive units
@cindex units, primitive
@cindex @samp{!} to indicate primitive units
@cindex command, @samp{!} to indicate primitive units
A unit is specified on a single line by giving its name and an
equivalence. Comments start with a @samp{#} character, which can appear
anywhere in a line. The backslash character (@samp{\})
acts as a continuation
character if it appears as the last character on a line, making it
possible to spread definitions out over several lines if desired.
A file can be included by giving the command @samp{!include} followed by
the file's name. The @samp{!} must be the first character on the
line. The file will be sought in the same directory as the
parent file unless you give a full path. The name of the file to be
included cannot contain the comment character @samp{#}.
@cindex include files
Unit names must not contain any of the operator characters @samp{+},
@samp{-}, @samp{*}, @samp{/}, @samp{|}, @samp{^}, @samp{;}, @samp{~},
the comment character @samp{#}, or parentheses. They cannot begin or
end with an underscore (@samp{_}), a comma (@samp{,}) or a decimal point
(@samp{.}). The figure dash (U+2012), typographical minus (`@minus{}';
U+2212), and en dash (`--'; U+2013) are converted to the operator
@samp{-}, so none of these characters can appear in unit names. Names
cannot begin with a digit, and if a name ends in a digit other than
zero, the digit must be preceded by a string beginning with an
underscore, and afterwards consisting only of digits, decimal points, or
commas. For example, @samp{foo_2}, @samp{foo_2,1}, or @samp{foo_3.14}
are valid names but @samp{foo2} or @samp{foo_a2} are invalid.
You could define nitrous oxide as
@example
N2O nitrogen 2 + oxygen
@end example
@noindent
but would need to define nitrogen dioxide as
@example
NO_2 nitrogen + oxygen 2
@end example
@noindent
Be careful to define new units in terms of old ones so that a
reduction leads to the primitive units, which are marked with @samp{!}
characters. Dimensionless units are indicated by using the string
@samp{!dimensionless} for the unit definition.
@cindex dimensionless units, defining
When adding new units, be sure to use the @option{-c} option to check
that the new units reduce properly. If you create a loop in the units
definitions, then @command{units} will hang when invoked with the
@option{-c} option. You will need to use the @option{--check-verbose}
option, which prints out each unit as it is checked. The program will
still hang, but the last unit printed will be the unit that caused the
infinite loop.
@cindex parentheses
If you define any units that contain
@samp{+} characters, carefully check them because the @option{-c} option
will not catch non-conformable sums. Be careful with the @samp{-}
operator as well. When used as a binary operator, the @samp{-}
character can perform addition or multiplication
depending on the options used to invoke @command{units}.
To ensure consistent behavior use @samp{-} only as a unary negation
operator when writing units definitions. To multiply two units leave a
space or use the @samp{*} operator with care, recalling that it has
two possible precedence values and may require parentheses to ensure
consistent behavior. To compute the difference
of @samp{foo} and @samp{bar} write @samp{foo+(-bar)} or even @samp{foo+-bar}.
Here is an example of a short data file that defines some basic
units:
@example
@group
m ! # The meter is a primitive unit
sec ! # The second is a primitive unit
rad !dimensionless # A dimensionless primitive unit
micro- 1e-6 # Define a prefix
minute 60 sec # A minute is 60 seconds
hour 60 min # An hour is 60 minutes
inch 0.0254 m # Inch defined in terms of meters
ft 12 inches # The foot defined in terms of inches
mile 5280 ft # And the mile
@end group
@end example
@cindex parentheses
@noindent
A unit that ends with a @samp{-} character is a prefix. If a prefix
definition contains any @samp{/} characters, be sure they are protected
by parentheses. If you define @samp{half- 1/2} then @samp{halfmeter}
would be equivalent to @samp{1 / (2@tie{}meter)}.
@node Defining Nonlinear Units
@section Defining Nonlinear Units
@cindex defining nonlinear units
@cindex nonlinear units, defining
@cindex nonlinear unit conversions
Some unit conversions of interest are nonlinear; for
example, temperature conversions between the Fahrenheit and Celsius
scales cannot be done by simply multiplying by conversion factors.
When you give a linear unit definition such as @samp{inch 2.54@tie{}cm}
you are providing information that @command{units} uses to convert
values in inches into primitive units of meters. For nonlinear units,
you give a functional definition that provides the same information.
Nonlinear units are represented using a functional notation.
It is best to regard this notation not as a function call but
as a way of adding units to a number, much the same way that
writing a linear unit name after a number adds units to that number.
Internally, nonlinear units are defined by a pair of functions
that convert to and from linear units in the database, so that
an eventual conversion to primitive units is possible.
Here is an example nonlinear unit definition:
@example
@group
tempF(x) units=[1;K] domain=[-459.67,) range=[0,) \
(x+(-32)) degF + stdtemp ; (tempF+(-stdtemp))/degF + 32
@end group
@end example
@noindent
A nonlinear unit definition comprises a unit name, a formal parameter
name, two functions, and optional specifications for units, the domain,
and the range (the domain of the inverse function). The functions tell
@command{units} how to convert to and from the new unit. To produce
valid results, the arguments of these functions need to have the correct
dimensions and be within the domains for which the functions are
defined.
@cindex parentheses
The definition begins with the unit name followed immediately (with no
spaces) by a @samp{(} character. In the parentheses is the name of the
formal parameter. Next is an optional specification of the units
required by the functions in the definition. In the example above,
the @samp{units=[1;K]} specification indicates that the
@samp{tempF} function requires an input argument conformable with
@samp{1} (i.e., the argument is dimensionless), and that the inverse
function requires an input argument conformable with @samp{K}. For
normal nonlinear units definition, the forward function will always take
a dimensionless argument; in general, the inverse function will need
units that match the quantity measured by your nonlinear unit.
Specifying the units enables @command{units} to perform error checking
on function arguments, and also to assign units to domain and range
specifications, which are described later.
Next the function definitions appear. In the example above, the
@samp{tempF} function is defined by
@example
@group
tempF(x) = (x+(-32)) degF + stdtemp
@end group
@end example
@noindent
This gives a rule for converting @samp{x} in the units @samp{tempF}
to linear units of absolute temperature, which makes it possible to
convert from tempF to other units.
To enable conversions to Fahrenheit, you must give a rule for the
inverse conversions. The inverse will be @samp{x(tempF)} and its
definition appears after a @samp{;} character. In our example, the
inverse is
@example
@group
x(tempF) = (tempF+(-stdtemp))/degF + 32
@end group
@end example
@noindent
This inverse definition takes an absolute temperature as its argument
and converts it to the Fahrenheit temperature. The inverse can be
omitted by leaving out the @samp{;} character and the inverse
definition, but then conversions @emph{to} the unit will not be
possible. If the inverse definition is omitted, the @option{--check}
option will display a warning. It is up to you to calculate and enter
the correct inverse function to obtain proper conversions; the
@option{--check} option tests the inverse at one point and prints an
error if it is not valid there, but this is not a guarantee that your
inverse is correct.
With some definitions, the units may vary. For example, the definition
@example
@group
square(x) x^2
@end group
@end example
@noindent
can have any arbitrary units, and can also take dimensionless arguments.
In such a case, you should @emph{not} specify units.
If a definition takes a root of its arguments, the definition is valid
only for units that yield such a root. For example,
@example
@group
squirt(x) sqrt(x)
@end group
@end example
@noindent
is valid for a dimensionless argument, and for arguments with even
powers of units.
@cindex domain, nonlinear unit definitions
@cindex range, nonlinear unit definitions
Some definitions may not be valid for all real numbers. In such cases,
@command{units} can handle errors better if you specify an appropriate
domain and range. You specify the domain and range as shown below:
@example
@group
baume(d) units=[1;g/cm^3] domain=[0,130.5] range=[1,10] \
(145/(145-d)) g/cm^3 ; (baume+-g/cm^3) 145 / baume
@end group
@end example
@noindent
In this example the domain is specified after @samp{domain=} with
the endpoints given in brackets. In accord with mathematical
convention, square brackets indicate a closed interval (one that
includes its endpoints), and parentheses indicate an open interval (one
that does not include its endpoints). An interval can be open or closed
on one or both ends; an interval that is unbounded on either end is
indicated by omitting the limit on that end. For example, a quantity to
which decibel (dB) is applied may have any value greater than zero, so
the range is indicated by @samp{(0,)}:
@example
@group
decibel(x) units=[1;1] range=(0,) 10^(x/10); 10 log(decibel)
@end group
@end example
@noindent
If the domain or range is given, the second endpoint must be greater
than the first.
The domain and range specifications can appear independently and in any
order along with the units specification.
The values for the domain and range endpoints are attached to the units
given in the units specification, and if necessary, the parameter value
is adjusted for comparison with the endpoints. For example, if a
definition includes @samp{units=[1;ft]} and @samp{range=[3,)}, the range
will be taken as 3@tie{}ft to infinity. If the function is passed a
parameter of @w{@samp{900 mm}}, that value will be adjusted to
2.9527559@tie{}ft, which is outside the specified range.
If you omit the units specification from the previous example,
@command{units} can not tell whether you intend the lower endpoint
to be 3@tie{}ft or 3@tie{}microfurlongs, and can not adjust the
parameter value of 900@tie{}mm for comparison. Without units,
numerical values other than zero or plus or minus infinity for domain or
range endpoints are meaningless, and accordingly they are not allowed. If
you give other values without units then the definition will be ignored
and you will get an error message.
Although the units, domain, and range specifications are optional, it's
best to give them when they are applicable; doing so allows
@command{units} to perform better error checking and give more helpful
error messages. Giving the domain and range also enables the
@option{--check} option to find a point in the domain to use for its
point check of your inverse definition.
You can make synonyms for nonlinear units by providing both the
forward and inverse functions; inverse functions can be obtained using
the @samp{~} operator. So to create a synonym for @samp{tempF} you
could write
@example
@group
fahrenheit(x) units=[1;K] tempF(x); ~tempF(fahrenheit)
@end group
@end example
@noindent
This is useful for creating a nonlinear unit
definition that differs slightly from an existing definition without
having to repeat the original functions. For example,
@example
dBW(x) units=[1;W] range=[0,) dB(x) W ; ~dB(dBW/W)
@end example
@noindent
If you wish a synonym to refer to an existing nonlinear unit without
modification, you can do so more simply by adding the synonym with
appended parentheses as a new unit, with the existing nonlinear
unit---without parentheses---as the definition. So to create a synonym
for @samp{tempF} you could write
@example
fahrenheit() tempF
@end example
@noindent
The definition must be a nonlinear unit; for example, the synonym
@example
fahrenheit() meter
@end example
@noindent
will result in an error message when @command{units} starts.
@cindex units functions
@cindex functions of units
You may occasionally wish to define a function that operates on units.
This can be done using a nonlinear unit definition. For example, the
definition below provides conversion between radius and the area of a
circle. This definition requires a length as input and
produces an area as output, as indicated by the @samp{units=} specification.
Specifying the range as the nonnegative numbers can prevent cryptic
error messages.
@example
@group
circlearea(r) units=[m;m^2] range=[0,) pi r^2 ; sqrt(circlearea/pi)
@end group
@end example
@node Piecewise Linear Units
@section Defining Piecewise Linear Units
@cindex defining piecewise linear units
@cindex linear interpolation
@cindex units, piecewise linear
@cindex piecewise linear units
Sometimes you may be interested in a piecewise linear unit such as
many wire gauges. Piecewise linear units can be defined by specifying
conversions to linear units on a list of points.
Conversion at other points will be done by linear interpolation.
A partial definition of zinc gauge is
@example
@group
zincgauge[in] 1 0.002, 10 0.02, 15 0.04, 19 0.06, 23 0.1
@end group
@end example
@noindent
In this example, @samp{zincgauge} is the name of the piecewise linear
unit. The definition of such a unit is indicated by the
embedded @samp{[} character. After the bracket, you should indicate the
units to be attached to the numbers in the table.
No spaces can appear before the
@samp{]} character, so a definition like @samp{foo[kg meters]} is
invalid; instead write @samp{foo[kg*meters]}. The definition of the
unit consists of a list of pairs optionally separated by commas.
This list defines a function for converting from the piecewise linear
unit to linear units. The
first item in each pair is the function argument; the second item is the
value of the function at that argument (in the units specified in brackets).
In this example,
we define @samp{zincgauge} at five points. For example, we set
@samp{zincgauge(1)} equal to @w{@samp{0.002 in}}. Definitions like this
may be more readable if written using continuation characters as
@example
@group
zincgauge[in] \
1 0.002 \
10 0.02 \
15 0.04 \
19 0.06 \
23 0.1
@end group
@end example
@noindent
With the preceding definition, the following conversion can be
performed:
@example
@group
You have: zincgauge(10)
You want: in
* 0.02
/ 50
You have: .01 inch
You want: zincgauge
5
@end group
@end example
@noindent
If you define a piecewise linear unit that is not strictly monotonic,
then the inverse will not be well defined. If the inverse is requested
for such a unit, @command{units} will return the smallest inverse.
After adding nonlinear units definitions, you should normally run
@w{@command{units --check}} to check for errors. If the @samp{units}
keyword is not given, the @option{--check} option checks a nonlinear unit
definition using a dimensionless argument, and then checks using an
arbitrary combination of units, as well as the square and cube of that
combination; a warning is given if any of these tests fail. For
example,
@set codequoteundirected
@example
@group
Warning: function 'squirt(x)' defined as 'sqrt(x)'
failed for some test inputs:
squirt(7(kg K)^1): Unit not a root
squirt(7(kg K)^3): Unit not a root
@end group
@end example
@clear codequoteundirected
@noindent
Running @w{@command{units --check}} will print a warning if a
non-monotonic piecewise linear unit is encountered. For example, the
relationship between ANSI coated abrasive designation and mean particle
size is non-monotonic in the vicinity of 800 grit:
@example
@group
ansicoated[micron] \
. . .
600 10.55 \
800 11.5 \
1000 9.5 \
@end group
@end example
@noindent
Running @w{@command{units --check}} would give the error message
@set codequoteundirected
@example
@group
Table 'ansicoated' lacks unique inverse around entry 800
@end group
@end example
@clear codequoteundirected
@noindent
Although the inverse is not well defined in this region, it's not really
an error. Viewing such error messages can be tedious, and if there are
enough of them, they can distract from true errors. Error checking for
nonlinear unit definitions can be suppressed by giving the
@samp{noerror} keyword; for the examples above, this could be done as
@example
@group
squirt(x) noerror domain=[0,) range=[0,) sqrt(x); squirt^2
ansicoated[micron] noerror \
. . .
@end group
@end example
@noindent
Use the @samp{noerror} keyword with caution. The safest approach after
adding a nonlinear unit definition is to run @w{@command{units --check}}
and confirm that there are no actual errors before adding the
@samp{noerror} keyword.
@node Defining Unit List Aliases
@section Defining Unit List Aliases
@cindex defining unit list aliases
@cindex unit list aliases, defining
@cindex @samp{!unitlist}
@cindex command, @samp{!unitlist}
Unit list aliases are treated differently from unit definitions,
because they are a data entry shorthand rather than a true definition
for a new unit.
A unit list alias definition begins with @samp{!unitlist} and includes the
alias and the definition; for example, the aliases included in the
standard units data file are
@example
@group
!unitlist hms hr;min;sec
!unitlist time year;day;hr;min;sec
!unitlist dms deg;arcmin;arcsec
!unitlist ftin ft;in;1|8 in
!unitlist usvol cup;3|4 cup;2|3 cup;1|2 cup;1|3 cup;1|4 cup;\
tbsp;tsp;1|2 tsp;1|4 tsp;1|8 tsp
@end group
@end example
@noindent
Unit list aliases are only for unit lists, so the definition must
include a @samp{;}. Unit list aliases can never be combined with
units or other unit list aliases, so the definition of @samp{time}
shown above could @emph{not} have been shortened to
@samp{year;day;hms}.
As usual, be sure to run @w{@command{units --check}} to ensure that the
units listed in unit list aliases are conformable.
@node Numeric Output Format
@chapter Numeric Output Format
@cindex numeric output format
@cindex output format
@menu
* Format Specification:: The output format specification
* Flags:: Optional format flags
* Field Width:: Specifying output field width
* Precision:: Specifying output precision
@end menu
By default, @code{units} shows results to eight significant
digits. You can change this with the @option{--exponential},
@option{--digits}, and @option{--output-format} options. The first
sets an exponential format (i.e., scientific notation) like that used
in the original Unix @command{units} program, the second allows you to
specify a different number of significant digits, and the last allows
you to control the output appearance using the format for the
@code{printf()} function in the C programming language. If you only
want to change the number of significant digits or specify exponential
format type, use the @option{--digits} and @option{--exponential}
options. The @option{--output-format} option affords the greatest
control of the output appearance, but requires at least rudimentary
knowledge of the @code{printf()} format syntax. @xref{Invoking Units},
for descriptions of these options.
@node Format Specification
@section Format Specification
@cindex output format specification
@cindex format specification, output
The format specification recognized with the @option{--output-format}
option is a subset of that for @code{printf()}. The format specification has
the form
@c noman
@code{%}[@i{flags}][@i{width}][@code{.}@i{precision}]@i{type};
@c end noman
@c ifman
@ignore
.\".CW "%\fR[\fP\fIflags\fP\fR][\fP\fIwidth\fP\fR][\fP.\fIprecision\fP\fR]\fP\fItype\fP" ;
@code{%}[@i{flags}][@i{width}][\c
@code{.}@i{precision}]@i{type};
@end ignore
@c end ifman
it must begin with @samp{%}, and must end with a floating-point type
specifier:
@samp{g} or @samp{G} to specify the number of significant digits,
@samp{e} or @samp{E} for scientific notation, and @samp{f} for
fixed-point decimal. The ISO C99 standard added the @samp{F} type for
fixed-point decimal and the @samp{a} and @samp{A} types for hexadecimal
floating point; these types are allowed with compilers that support
them. Type length modifiers (e.g., @samp{L} to indicate a long double)
are inapplicable and are not allowed.
The default format for @command{units} is @samp{%.8g};
for greater precision, you could specify @samp{-o@tie{}%.15g}.
The @samp{g} and @samp{G} format types use exponential format whenever
the exponent would be less than @minus{}4, so the value 0.000013
displays as @samp{1.3e-005}. These types also use exponential notation
when the exponent is greater than or equal to the precision, so with the
default format, the value
@c
@tex
$5\times 10^7$
@end tex
@ifnottex
@c noman
5e7
@c end noman
@c man .if t .ig ++
@c man 5e7
@c man .++
@c man .if n .ig ++
@c man .EQ
@c man 5 times 10 sup 7
@c man .EN
@c man .++
@end ifnottex
displays as @samp{50000000} and the value
@tex
$5\times 10^8$
@end tex
@ifnottex
@c noman
5e8
@c end noman
@c man .if t .ig ++
@c man 5e8
@c man .++
@c man .if n .ig ++
@c man .EQ
@c man 5 times 10 sup 8
@c man .EN
@c man .++
@end ifnottex
displays as @samp{5e+008}. If you prefer fixed-point display, you might
specify @samp{-o@tie{}%.8f}; however, small numbers will display very
few significant digits, and values less than
@tex
$0.5\times10^{-8}$
@end tex
@ifnottex
@c noman
0.5e@minus{}8
@c end noman
@c man .if t .ig ++
@c man 0.5e\-8
@c man .++
@c man .if n .ig ++
@c man .EQ
@c man 0.5 times 10 sup -8
@c man .EN
@c man .++
@end ifnottex
will show nothing but zeros.
The format specification may include one or more optional flags:
@samp{+}, @samp{@tie{}} (space), @samp{#}, @samp{-}, or @samp{0} (the
digit zero). The digit-grouping flag
@c noman
@set codequoteundirected
@samp{'} (apostrophe)
@clear codequoteundirected
@c end noman
@c if the troff formatter is groff, ensure an ASCII single quote
@c man .ie \n(.g .CQ "\(aq"
@c man .el .CQ "'"
is allowed with compilers that support it. Flags are followed by an
optional value for the minimum field width, and an optional precision
specification that begins with a period (e.g., @samp{.6}). The field
width includes the digits, decimal point, the exponent, thousands
separators (with the digit-grouping flag), and the sign if any of these
are shown.
@node Flags
@section Flags
@cindex output format flags
@cindex flags, output format
The @samp{+} flag causes the output to have a sign (@samp{+} or @samp{-}).
The space flag @samp{@tie{}} is similar to the @samp{+} flag, except
that when the value is positive, it is prefixed with a space rather than
a plus sign; this flag is ignored if the @samp{+} flag is also given.
The @samp{+} or @samp{@tie{}} flag could be useful if conversions might
include positive and negative results, and you wanted to align
the decimal points in exponential notation.
@c
The @samp{#} flag causes the output value to contain a decimal point in
all cases; by default, the output contains a decimal point only if there
are digits (which can be trailing zeros) to the right of the point.
With the @samp{g} or @samp{G} types, the @samp{#} flag also prevents the
suppression of trailing zeros.
@c
The digit-grouping flag
@c noman
@set codequoteundirected
@samp{'}
@clear codequoteundirected
@c end noman
@c if the troff formatter is groff, ensure an ASCII single quote
@c man .ie \n(.g .CQ "\(aq"
@c man .el .CQ "'"
shows a thousands separator in digits to the left of the decimal point.
@c (e.g., @samp{1,234.56}).
This can be useful when displaying large numbers in fixed-point decimal;
for example, with the format @samp{%f},
@example
You have: mile
You want: microfurlong
* 8000000.000000
/ 0.000000
@end example
@noindent
the magnitude of the first result may not be immediately obvious without
counting the digits to the left of the decimal point. If the thousands
separator is the comma (@samp{,}), the output with the format
@c noman
@set codequoteundirected
@samp{%'f}
@clear codequoteundirected
@c end noman
@c if the troff formatter is groff, ensure an ASCII single quote
@c man .ie \n(.g .CQ "%\(aqf"
@c man .el .CQ "%'f"
might be
@example
You have: mile
You want: microfurlong
* 8,000,000.000000
/ 0.000000
@end example
@noindent
making the magnitude readily apparent. Unfortunately, few compilers
support the digit-grouping flag.
@c
With the @samp{-} flag, the output value is left aligned within the
specified field width. If a field width greater than needed to show the
output value is specified, the @samp{0} (zero) flag causes the output
value to be left padded with zeros until the specified field width is
reached; for example, with the format @samp{%011.6f},
@example
You have: troypound
You want: grain
* 5760.000000
/ 0000.000174
@end example
@noindent
The @samp{0} flag has no effect if the @samp{-} (left align) flag is
given.
@node Field Width
@section Field Width
@cindex output field width
By default, the output value is left aligned and shown with the minimum
width necessary for the specified (or default) precision. If a field
width greater than this is specified, the value shown is right aligned,
and padded on the left with enough spaces to provide the specified field
width. A width specification is typically used with fixed-point decimal
to have columns of numbers align at the decimal point; this arguably is
less useful with @command{units} than with long columnar output, but it
may nonetheless assist in quickly assessing the relative magnitudes of
results. For example, with the format @samp{%12.6f},
@example
@group
You have: km
You want: in
* 39370.078740
/ 0.000025
@end group
@group
You have: km
You want: rod
* 198.838782
/ 0.005029
@end group
@group
You have: km
You want: furlong
* 4.970970
/ 0.201168
@end group
@end example
@node Precision
@section Precision
@cindex output precision
@cindex precision, output
The meaning of ``precision'' depends on the format type. With @samp{g}
or @samp{G}, it specifies the number of significant digits (like the
@option{--digits} option); with @samp{e}, @samp{E}, @samp{f}, or
@samp{F}, it specifies the maximum number of digits to be shown after
the decimal point.
@c
With the @samp{g} and @samp{G} format types, trailing zeros are
suppressed, so the results may sometimes have fewer digits than the
specified precision (as indicated above, the @samp{#} flag causes
trailing zeros to be displayed).
The default precision is 6, so @samp{%g} is equivalent to @samp{%.6g},
and would show the output to six significant digits. Similarly,
@samp{%e} or @samp{%f} would show the output with six digits after the
decimal point.
The C @code{printf()} function allows a precision of arbitrary size, whether or
not all of the digits are meaningful. With most compilers, the maximum
internal precision with @command{units} is 15 decimal digits (or 13
hexadecimal digits).
With the @option{--digits} option, you are limited
to the maximum internal precision; with the @option{--output-format}
option, you may specify a precision greater than this, but it may not be
meaningful. In some cases, specifying excess precision can result in
rounding artifacts. For example, a pound is exactly 7000 grains, but
with the format @samp{%.18g}, the output might be
@example
You have: pound
You want: grain
* 6999.9999999999991
/ 0.00014285714285714287
@end example
@noindent
With the format @samp{%.25g} you might get the following:
@example
You have: 1/3
You want:
Definition: 0.333333333333333314829616256247
@end example
@noindent
In this case the displayed value includes a series of digits that represent the
underlying binary floating-point approximation to 1/3 but are not
meaningful for the desired computation.
In general, the result with excess precision is system dependent.
@c
The precision affects only the @emph{display} of numbers; if a result
relies on physical constants that are not known to the specified
precision, the number of physically meaningful digits may be less than
the number of digits shown.
See the documentation for @code{printf()} for more detailed descriptions of the
format specification.
The @option{--output-format} option is incompatible with the
@option{--exponential} or @option{--digits} options; if the former is
given in combination with either of the latter, the format is controlled
by the last option given.
@node Localization
@chapter Localization
@cindex environment dependent definitions
@cindex localization
@cindex @samp{!locale}
@cindex command, @samp{!locale}
@cindex @samp{!endlocale}
@cindex command, @samp{!endlocale}
@cindex command, @samp{!endvar}
@cindex command, @samp{!var}
@cindex command, @samp{!varnot}
@cindex command, @samp{!set}
@cindex command, @samp{!message}
@menu
* Locale:: What is a locale?
* Additional Localization:: When the locale isn't enough
@end menu
Some units have different values in different locations. The
localization feature accommodates this by allowing a units data file to
specify definitions that depend on the user's locale.
@node Locale
@section Locale
@cindex locale
A locale is a subset of a user's environment that indicates the user's
language and country, and some attendant preferences, such as the
formatting of dates. The @command{units} program attempts to determine
the locale from the POSIX setlocale function; if this cannot be done,
@command{units} examines the environment
variables @env{LC_CTYPE} and @env{LANG}.
On POSIX systems, a locale is of the form
@var{language}@code{_}@var{country}, where @var{language} is the
two-character code from ISO 639-1 and @var{country} is the two-character
code from ISO 3166-1; @var{language} is lower case and @var{country} is
upper case. For example, the POSIX locale for the United Kingdom is @code{en_GB}.
@cindex @file{locale_map.txt}
@cindex setlocale function
On systems running Microsoft Windows, the value returned by setlocale()
is different from that on POSIX systems; @command{units} attempts to map
the Windows value to a POSIX value by means of a table in the file
@file{locale_map.txt} in the same directory as the other data files. The
file includes entries for many combinations of language and country, and
can be extended to include other combinations. The @file{locale_map.txt}
file comprises two tab-separated columns; each entry is of the form
@display
@var{Windows-locale}@ @ @ @var{POSIX-locale}
@end display
@noindent
where @var{POSIX-locale} is as described above, and @var{Windows-locale}
typically spells out both the language and country. For example, the
entry for the United States is
@example
English_United States en_US
@end example
@noindent
You can force @command{units} to run in a desired locale by using the
@option{-l} option.
In order to create unit definitions for a particular locale you begin
a block of definitions in a unit datafile with @samp{!locale} followed
by a locale name. The @samp{!} must be the first character on the
line. The @command{units} program reads the following
definitions only if the current locale matches. You end the block of
localized units with @samp{!endlocale}. Here is an example, which
defines the British gallon.
@example
@group
!locale en_GB
gallon 4.54609 liter
!endlocale
@end group
@end example
@node Additional Localization
@section Additional Localization
Sometimes the locale isn't sufficient to determine unit preferences.
There could be regional preferences, or a company could have specific
preferences. Though probably uncommon, such differences could arise
with the choice of English customary units outside of English-speaking
countries. To address this, @command{units} allows specifying
definitions that depend on environment variable settings.
The environment variables can be controled based on the current locale,
or the user can set them to force a particular group of definitions.
A conditional block of definitions in a units data file begins with
either @samp{!var} or @samp{!varnot} following by an environment
variable name and then a space separated
list of values. The leading @samp{!} must appear in the first column of a units
data file, and the conditional block is terminated by @samp{!endvar}.
Definitions in blocks beginning with @samp{!var} are executed only if the
environment variable is exactly equal to one of the listed values.
Definitions in blocks beginning with @samp{!varnot} are executed only if the
environment variable does @emph{not} equal any of the list values.
The inch has long been a customary measure of length in many places.
The word comes from the latin @emph{uncia} meaning ``one twelfth,''
referring to its relationship with the foot. By the 20th century, the
inch was officially defined in English-speaking countries relative to
the yard, but until 1959, the yard differed slightly among those
countries. In France the customary inch, which was displaced in 1799
by the meter, had a different length based on a french foot. These
customary definitions could be accommodated as follows:
@example
@group
!var INCH_UNIT usa
yard 3600|3937 m
!endvar
@end group
@group
!var INCH_UNIT canada
yard 0.9144 meter
!endvar
@end group
@group
!var INCH_UNIT uk
yard 0.91439841 meter
!endvar
@end group
@group
!var INCH_UNIT canada uk usa
foot 1|3 yard
inch 1|12 foot
!endvar
@end group
@group
!var INCH_UNIT france
foot 144|443.296 m
inch 1|12 foot
line 1|12 inch
!endvar
@end group
@group
!varnot INCH_UNIT usa uk france canada
!message Unknown value for INCH_UNIT
!endvar
@end group
@end example
@noindent
When @command{units} reads the above definitions it will check the
environment variable @env{INCH_UNIT} and load only the definitions for
the appropriate section. If @env{INCH_UNIT} is unset or is not set to
one of the four values listed then @command{units} will run the last
block. In this case that block uses the
@samp{!message} command to display a warning message. Alternatively
that block could set default values.
In order to create default values that are overridden by user settings
the data file can use the @samp{!set} command, which sets an
environment variable @emph{only if it is not already set}; these
settings are only for the current @command{units} invocation and do
not persist. So if the example above were preceded by
@samp{!set INCH_UNIT france} then this would make @samp{france} the
default value for @env{INCH_UNIT}. If the user had set the variable
in the environment before invoking @command{units}, then
@command{units} would use the user's value.
To link these settings to the user's locale you combine the @samp{!set}
command with the @samp{!locale} command.
If you wanted to combine the above example with suitable locales you
could do by @emph{preceding} the above definition with the following:
@example
@group
!locale en_US
!set INCH_UNIT usa
!endlocale
!locale en_GB
!set INCH_UNIT uk
!endlocale
!locale en_CA
!set INCH_UNIT canada
!endlocale
!locale fr_FR
!set INCH_UNIT france
!endlocale
!set INCH_UNIT france
@end group
@end example
@noindent
These definitions set the overall default for @env{INCH_UNIT} to
@samp{france} and set default values for four locales appropriately.
The overall default setting comes last so that it only applies when
@env{INCH_UNIT} was not set by one of the other commands or by the
user.
If the variable given after @samp{!var} or @samp{!varnot} is undefined
then @command{units} prints an error message and ignores the
definitions that follow. Use @samp{!set} to create defaults to
prevent this situation from arising. The @option{-c}
option only checks the definitions that are active for the current
environment and locale, so when adding new definitions take care to
check that all cases give rise to a well defined set of definitions.
@node Environment Vars
@chapter Environment Variables
@cindex environment variables
The @command{units} program uses the following environment variables:
@table @env
@item HOME
@cindex HOME environment variable
@cindex environment variable, HOME
Specifies the location of your home directory; it is used by
@command{units} to find a personal units data file @samp{.units}. On
systems running Microsoft Windows, the file is @samp{unitdef.units}, and
if @env{HOME} does not exist, @command{units} tries to determine your
home directory from the @env{HOMEDRIVE} and @env{HOMEPATH} environment
variables; if these variables do not exist, units finally tries
@env{USERPROFILE}---typically @file{C:\Users\@var{username}} (Windows
Vista and Windows@tie{}7) or
@w{@file{C:\Documents and Settings\@var{username}}} (Windows@tie{}XP).
@item LC_CTYPE, LANG
@cindex LANG environment variable
@cindex LC_CTYPE environment variable
@cindex environment variable, LANG
@cindex environment variable, LC_CTYPE
Checked to determine the locale if @command{units} cannot obtain it
from the operating system. Sections of the
standard units data file are specific to certain locales.
@item MYUNITSFILE
@cindex MYUNITSFILE environment variable
@cindex environment variable, MYUNITSFILE
Specifies your personal units data file. If this variable exists,
@command{units} uses its value rather than searching your home
directory for @samp{.units}. The personal units file will not be
loaded if any data files are given using the @option{-f} option.
@item PAGER
@cindex PAGER environment variable
@cindex environment variable, PAGER
@cindex help
Specifies the pager to use for help and for displaying the conformable
units. The help function browses the units database and calls
the pager using the @samp{+n}@var{n} syntax for specifying a line
number. The default pager is @command{more}; @env{PAGER} can be used
to specify alternatives such as @command{less}, @command{pg},
@command{emacs}, or @command{vi}.
@item UNITS_ENGLISH
@cindex UNITS_ENGLISH environment variable
@cindex environment variable, UNITS_ENGLISH
Set to either @samp{US} or
@samp{GB} to choose United States or British volume definitions,
overriding the default from your locale.
@item UNITSFILE
@cindex UNITSFILE environment variable
@cindex environment variable, UNITSFILE
Specifies the units data file to use (instead of the default).
You can only specify a single units data file using this environment
variable. If units data files are given using the @option{-f} option,
the file specified by @env{UNITSFILE} will be not be loaded unless the
@option{-f} option is given with the empty string
(@w{@samp{units -f ""}}).
@item UNITSLOCALEMAP
@cindex UNITSLOCALEMAP environment variable
@cindex environment variable, UNITSLOCALEMAP
Windows only; this variable has no effect on Unix-like systems.
Specifies the units locale map file to use (instead of the default).
This variable seldom needs to be set, but you can use it to ensure that
the locale map file will be found if you specify a location for the
units data file using either the @option{-f} option or the
@env{UNITSFILE} environment variable, and that location does not also
contain the locale map file.
@end table
@node Data Files
@chapter Data Files
@cindex files, data
@cindex data files
The @command{units} program uses two default data files:
@file{definitions.units} and @file{currency.units}. The program can
also use an optional personal units data file @file{.units}
(@file{unitdef.units} under Windows) located in the user's home
directory. The personal units data file is described in more detail in
@ref{Units Data Files}.
On Unix-like systems, the data files are typically located in
@file{/usr/share/units} if @command{units} is provided with the
operating system, or in @file{/usr/local/share/units} if @command{units}
is compiled from the source distribution.
On systems running Microsoft Windows, the files may be in the same
locations if Unix-like commands are available, a Unix-like file
structure is present (e.g., @file{C:/usr/local}), and @command{units} is
compiled from the source distribution. If Unix-like commands are not
available, a more common location is
@w{@file{C:\Program Files (x86)\GNU\units}} (for 64-bit Windows
installations) or @w{@file{C:\Program Files\GNU\units}} (for 32-bit
installations).
If @command{units} is obtained from the GNU Win32 Project
(@uref{http://gnuwin32.sourceforge.net/}), the files are commonly in
@w{@file{C:\Program Files\GnuWin32\share\units}}.
If the default units data file is not an absolute pathname,
@command{units} will look for the file in the directory that contains
the @command{units} program; if the file is not found there,
@command{units} will look in a directory @code{../share/units} relative
to the directory with the @command{units} program.
You can determine the location of the files by running
@w{@command{units --version}}. Running @w{@command{units --info}}
will give you additional information about the files, how
@command{units} will attempt to find them, and the status of the
related environment variables.
@node Unicode Support
@chapter Unicode Support
@cindex Unicode support
@cindex UTF-8
@cindex @samp{!utf8}
@cindex command, @samp{!utf8}
@cindex @samp{!endutf8}
@cindex command, @samp{!endutf8}
The standard units data file is in Unicode, using UTF-8 encoding. Most
definitions use only ASCII characters (i.e., code points U+0000 through
U+007F); definitions using non-ASCII characters appear in blocks
beginning with @samp{!utf8} and ending with @samp{!endutf8}.
When @command{units} starts, it checks the locale to determine the
character set. If @command{units} is compiled with Unicode support and
definitions; otherwise these definitions are ignored. When Unicode
support is active, @command{units} will check every line of all of the
units data files for invalid or non-printing UTF-8 sequences; if such
sequences occur, @command{units} ignores the entire line. In addition
to checking validity, @command{units} determines the display width of
non-ASCII characters to ensure proper positioning of the pointer in some
error messages and to align columns for the @samp{search} and @samp{?}
commands.
At present, @command{units} does not support Unicode under Microsoft
Windows. The UTF-16 and UTF-32 encodings are not supported on any
systems.
If definitions that contain non-ASCII characters are added to a units
data file, those definitions should be enclosed within @samp{!utf8}
@dots{} @samp{!endutf8} to ensure that they are only loaded when
Unicode support is available. As usual, the @samp{!} must appear as
the first character on the line. As discussed in
@ref{Units Data Files}, it's usually best to put such definitions in
supplemental data files linked by an @samp{!include} command or in a
personal units data file.
When Unicode support is not active, @command{units} makes no assumptions
about character encoding, except that characters in the range 00--7F
hexadecimal correspond to ASCII encoding. Non-ASCII characters are
simply sequences of bytes, and have no special meanings; for definitions
in supplementary units data files, you can use any encoding consistent
with this assumption. For example, if you wish to use non-ASCII
characters in definitions when running @command{units} under Windows,
you can use a character set such as Windows ``ANSI'' (code page 1252 in
the US and Western Europe). You can even use UTF-8, though some
messages may be improperly aligned, and @command{units} will not detect
invalid UTF-8 sequences. If you use UTF-8 encoding when Unicode support
is not active, you should place any definitions with non-ASCII
characters @emph{outside} @samp{!utf8} @dots{} @samp{!endutf8}
blocks---otherwise, they will be ignored.
Typeset material other than code examples usually uses the Unicode minus
(U+2212) rather than the ASCII hyphen-minus operator (U+002D) used in
@command{units}; the figure dash (U+2012) and en dash (U+2013) are also
occasionally used. To allow such material to be copied and pasted for
interactive use or in units data files, @command{units} converts these
characters to U+002D before further processing. Because of this, none
of these characters can appear in unit names.
@node Readline Support
@chapter Readline Support
@cindex @command{readline}, use with @command{units}
If the @command{readline} package has been compiled in, then when
@command{units} is used interactively, numerous command line editing
features are available. To check if your version of @command{units}
includes @command{readline}, invoke the program with the
@option{--version} option.
For complete information about @command{readline}, consult the
documentation for the @command{readline} package. Without any
configuration, @command{units} will allow editing in the style of
emacs. Of particular use with @command{units} are the completion
commands.
@cindex @samp{?} for unit completion with @command{readline}
@cindex unit completion using @samp{?} (@command{readline} only)
@cindex completion, unit, using @samp{?} (@command{readline} only)
If you type a few characters and then hit @key{ESC} followed by
@kbd{?} then @command{units} will display a list of all the units that
start with the characters typed. For example, if you type @kbd{metr} and
then request completion, you will see something like this:
@cindex unit name completion
@example
@group
You have: metr
metre metriccup metrichorsepower metrictenth
metretes metricfifth metricounce metricton
metriccarat metricgrain metricquart metricyarncount
You have: metr
@end group
@end example
@noindent
If there is a unique way to complete a unitname, you can hit the @key{TAB} key
and @command{units} will provide the rest of the unit name. If @command{units}
beeps, it means that there is no unique completion. Pressing the @key{TAB}
key a second time will print the list of all completions.
The readline library also keeps a history of the values you enter.
You can move through this history using the up and down arrows. The
history is saved to the file @file{.units_history} in your home
directory so that it will persist across multiple @command{units}
invocations. If you wish to keep work for a certain project separate
you can change the history filename using the @option{--history}
option. You could, for example, make an alias for @command{units} to
@command{units --history .units_history} so that @command{units} would
save separate history in the current directory.
The length of each history file is limited to 5000 lines. Note also that if
you run several concurrent copies of @command{units} each one will save
its new history to the history file upon exit.
@node Currency
@chapter Updating Currency Exchange Rates
@cindex currency, updating
@cindex exchange rates, updating
The units program includes currency exchange rates and prices for some
precious metals in the database. Of course, these values change over
time, sometimes very rapidly, and @command{units} cannot provide real
time values. To update the exchange rates run the
@command{units_cur}, which rewrites the files containing the currency
rates, typically @file{/usr/share/units/currency.units}. This program
requires @command{python} and the @command{unidecode} package, and must
be run with suitable permissions to write the file. To keep the rates
updated automatically, run it using a cron job on a Unix-like system, or
a similar scheduling program on a different system. Currency exchange
rates are taken from Time Genie (@uref{http://www.timegenie.com}) and
precious metals pricing from Packetizer (@uref{www.packetizer.com}).
These sites update once per day, so there is no benefit in running the
update script more often than daily. You can run @command{units_cur}
with a filename specified on the command line and it will write the data
to that file. If you give @samp{-} for the file it will write to
standard output.
@node Database Syntax
@chapter Database Command Syntax
@cindex database syntax summary
@cindex syntax of units database
@cindex commands in units database
@table @t
@item @var{unit} @var{definition}
Define a regular unit.
@item @var{prefix}- @var{definition}
Define a prefix.
@item @var{funcname}(@var{var}) noerror units=[@var{in-units},@var{out-units}] domain=[@var{x1},@var{x2}] range=[@var{y1},@var{y2}] @var{definition(var)} ; @var{inverse(funcname)}
Define a nonlinear unit or unit function. The four optional keywords @command{noerror},
@command{units=}, @command{range=} and @command{domain=} can appear in
any order. The definition of the inverse is optional.
@item @var{tabname}[@var{out-units}] noerror @var{pair-list}
Define a piecewise linear unit. The pair list gives the points on the
table listed in ascending order. The @command{noerror} keyword is
optional.
@item !endlocale
End a block of definitions beginning with @samp{!locale}
@item !endutf8
End a block of definitions begun with @samp{!utf8}
@item !endvar
End a block of definitions begun with @samp{!var} or @samp{!varnot}
@item !include @var{file}
Include the specified file.
@item !locale @var{value}
Load the following definitions only of the locale is set to
@var{value}.
@item !message @var{text}
Display @var{text} when the database is read unless the quiet
option (@option{-q}) is enabled.
@item !set @var{variable} @var{value}
Sets the environment variable, @var{variable}, to the specified
value @emph{only if} it is not already set.
@item !unitlist @var{alias} @var{definition}
Define a unit list alias.
@item !utf8
Load the following definitions only if @command{units} is running with
UTF-8 enabled.
@item !var @var{envar} @var{value-list}
Load the block of definitions that follows only if the environment
variable @var{envar} is set to one of the values listed in the
space-separated value list. If @var{envar} is not set,
@command{units} prints an error message and ignores the block of
definitions.
@item !varnot @var{envar} @var{value-list}
Load the block of definitions that follows only if the environment
variable @var{envar} is set to value that is @emph{not} listed in the
space-separated value list. If @var{envar} is not set, @command{units}
prints an error message and ignores the block of definitions.
@end table
@node GNU Free Documentation License
@chapter GNU Free Documentation License
@include fdl-1.3.texi
@node Index
@unnumbered Index
@printindex cp
@bye
@c man .SH FILES
@c man @DATAFILE@ \(em the standard units data file
@c man .SH AUTHOR
units-2.12/README.Win 0000664 0001750 0001750 00000017326 12316637517 013520 0 ustar adrian adrian With Unix-Like Utilities
========================
If you have Unix-like utilities, you may be able to build and install in
much the same manner as on most Unix-like systems with a few
adjustments. Version 2.11 was built using Microsoft Visual C/C++ 6.0,
Visual C/C++ Express 9.0 and 10.0, and the MKS Toolkit version 9.6 under
Windows XP, SP3--see README.MKS for the details.
Without Unix-Like Utilities
===========================
If you have Microsoft Visual C/C++ or Visual Studio but don't have Unix-
like utilities, you may be able to build and install using Makefile.Win.
nmake /f Makefile.Win
nmake /f Makefile.Win installprog
By default, the units executable and data files are placed in the
directory given by %ProgramFiles%\GNU\units; in most cases, this is
C:\Program Files\GNU\units.
You can preview the installation directories with
nmake /f Makefile.Win showdest
If the destination directories don't exist, they will be created during
installation. You can change these locations by editing Makefile.Win.
If you want to run units from a command prompt or from the Run box, you
can add the installation directory to the PATH environment variable.
Alternatively, you can create a shortcut to the program and place it in
a convenient location.
Icons
=====
The installation creates an association between the units data files and
the notepad editor, and associates these files with icons in
unitsfile.ico. An additional icon file, unitsprog.ico, is provided in
case you wish to use it in a shortcut to the units program.
Updating Currency Definitions
=============================
The script units_cur.py can be used to update currency definitions (if
your system hides file extensions, this script will display as
units_cur). The script requires Python (available from
http://www.python.org/) and the unidecode package (available at
http://pypi.python.org/).
Installing Python
-----------------
If you want to use the currency updater, install Python and then install
the unidecode package. Unless you have (or anticipate having)
applications that depend on Python 2, the best choice is probably to
install Python 3.
To install the unidecode package, follow the instructions in the
PKG-INFO file included with the package. You then should be able to run
units_cur.py using the shortcut on the Start Menu, or if you have added
the units installation directory to your PATH, from a command window.
Installing units_cur.py
-----------------------
To create the appropriate script for the version of Python that you will
be using, use either
nmake /f Makefile.Win currency2 (for Python 2)
or
nmake /f Makefile.Win currency3 (for Python 3)
The script will then be installed when using the 'installprog' target.
Setting PATHEXT
---------------
If you add ".py" to the PATHEXT environment variable, you can simply
type "units_cur" to run the updater from a command window. You can do
this from a command window by typing
set PATHEXT=%PATHEXT%;.py
but you'll need to do this with every new instance. You can make a
permanent change by adding ";.py" to PATHEXT from the Advanced tab of
the System dialog: click the 'Environment Variables' button, find
PATHEXT in either the list of User variables or the list of System
variables; click the Edit button, make the change, and click 'OK'.
Updating Currency Definitions from a Command Prompt
---------------------------------------------------
Unless you run the currency-update script from the program installation
directory, you will need to modify units_cur.py to give the full
pathname of the output file currency.units, i.e., change
outfile = 'currency.units'
to
outfile = '/currency.units'
For the default installation directory, this would be
outfile = 'C:/Program Files/GNU/units/currency.units'
Be sure to use forward slashes to avoid confusing Python. The best
approach is to modify this file before installation after creating it
with the 'currency?' target.
Automatic Updates
-----------------
The easiest way to keep currency values up to date is by having the
Windows Task Scheduler run units_cur.py on a regular basis.
Python Version
--------------
By default, the currency updater is configured to use Python 3. If you
have older programs that depend on Python 2 and do not wish to install
Python 3, rename units_cur to "units_cur3" and rename units_cur2 to
"units_cur". If your system is configured to not hide filename
extensions, these files will show a ".py" extension; if that's the case,
be sure to retain the ".py" when renaming, because the extension is
needed for Windows to know how to process the script.
If you have both Python 2 and Python 3 installed, the Python launcher
will use the latest installed version of Python 2 by default, and the
default units_cur will fail. The easiest approach here is to run nmake
using the 'currency2' target as shown above before installing to let
Python 2 handle the script--the result from either script is the same.
If you want to use Python 3, you can do it several ways, including
* Changing the first line of the default units_cur from
#!/usr/bin/python to "#!python3". The default directive is for
compatibility with Unix-like systems; the Python launcher for
Windows simply interprets it to mean "use Python", and doesn't
actually expect to find the program in /usr/bin. The "#!python3"
form tells the Python launcher to find and use Python 3.
This should work fine for double clicking the script's icon or
running it from a command window, but it may fail if the script is
run from a Unix-like shell that interprets the "#!" directive
literally.
* Confirming that the Python launcher py.exe is in the Windows
directory (usually C:\Windows) and changing the first line of the
default units_cur from #!/usr/bin/python to "#!C:\Windows\py.exe - 3";
this will cause the Python launcher to use the latest installed
version of Python 3. A fully qualified pathname is interpreted
literally by the Python launcher, so if the Python launcher is
located elsewhere, the first line should give that location.
This approach should work for a Unix-like shell as well as the
Windows command interpreter.
* Setting the environment variable PY_PYTHON to "3"; the best way to
do this is from the Advanced tab of the System dialog. This also
should work for both Windows and Unix-like command interpreters, but
it will affect all Python scripts.
Example
=======
If you are using Python 3 and installing units in the default location
of C:/Program Files/GNU/units, the process would be to
1. Build the executable by running
nmake /f Makefile.Win
2. Create the currency updater script by running
nmake /f Makefile.Win currency3
3. Modify units_cur.py so that the output file is given by
outfile = 'C:/Program Files/GNU/units/currency.units'
4. Confirm the installation location by running
nmake /f Makefile.Win showdest
It is assumed that the program will be installed in a subdirectory
of the standard location for executables (typically,
C:\Program Files), and a warning is given if this directory does not
exist. Ignore the warning if you are intentionally installing in
another location.
5. Install the files by running
nmake /f Makefile.Win installprog
6. Ensure that currency.units is writable by ordinary users. The
installation should do this automatically, but if for some reason it
does not, set permissions manually by adding 'Modify' permission for
the appropriate groups (typically 'Power Users' and 'Users')
This build and installation were tested for units 2.11 using Microsoft
Visual C/C++ 6, 9.0, and 10.0 under Windows XP SP3.
-- Jeff Conrad (jeff_conrad@msn.com) 1 April 2014
units-2.12/texi2man 0000775 0001750 0001750 00000032250 12270035511 013533 0 ustar adrian adrian #!/usr/bin/perl
# $Id: $
# Written by Adrian Mariano, additional features by Eric Backus and
# Jeff Conrad.
# Script to translate a texinfo file into an nroff/troff manual page.
# last revision: 20 January 2014 Jeff Conrad
$version="1.01s";
$html=0;
$example=0;
$ignore=0;
$tex=0;
$doman=0;
$title=0;
$diditem=0;
$justdidlp=1;
$noman=0;
$manprefix="";
$args=($#ARGV < 0) ? "stdin" : "@ARGV";
printf(".\\\"Do not edit this file. It was created from %s\n", $args);
printf(".\\\"using texi2man version %s on %s", $version, `date`);
while(<>)
{
# use font CW in tables
if (/\@c man\s+l\s/)
{
s/\@c man //;
s/l/lfCWp-1/;
print;
next;
}
if (s/\@c man //)
{
print;
if (/\.TH/) { add_extensions(); }
next;
}
if (/\@c noman/) { $noman=1; next; }
if (/\@c end noman/) { $noman=0; next; }
if ($noman) { next; }
if (/\@c ifman\s*(.*)/) { $doman=1; $manprefix = $1; next; }
if (/\@c end ifman/) { $doman=0; $manprefix = ""; next; }
if (/^\\input/) { next; }
if (/^\*/) { next; }
if (/^START-INFO-DIR-ENTRY/) { next; }
if (/^END-INFO-DIR-ENTRY/) { next; }
if (/\@titlepage/) { $title=1; next; }
if (/\@end titlepage/) { $title=0; next; }
if (/\@tex/) { $tex=1; next; }
if (/\@end tex/) { $tex=0; next; }
if (/\@ignore/) { $ignore=1; next; }
if (/\@end ignore/) { $ignore=0; next; }
if (/\@ifhtml/) { $html=1; next; }
if (/\@end ifhtml/) { $html=0; next; }
if (!$doman && ($ignore || $html || $title || $tex)) { next; }
if (/\@codequoteundirected/) { next; }
s/\@\*$/\n\.br/g;
s/^\@\*/.br/g;
s/\@\*$/\n.br/g;
s/\@ / /g;
s/\@dmn\{([^}]*)}/\\|$1/g;
s/\@tie\{}/\@no_break_space\{}/g;
s/\@w\{}/\@no_break_space\{}/g;
s/\@backslashchar\{}/\\e/g;
# ellipsis, defined in extensions
s/\@dots\{}/\\*(El/g;
s/\@cite\{([^}]*)}/\@in_sgl_quotes\{$1}/g;
s/\@url\{([^}]*)}/\@in_sgl_quotes\{$1}/g;
s/\@email\{([^}]*)}/\@in_sgl_quotes\{$1}/g;
s/\@dfn\{([^}]*)}/\@in_italics\{$1}/g;
s/\@emph\{([^}]*)}/\@in_italics\{$1}/g;
s/\@i\{([^}]*)}/\@in_italics\{$1}/g;
s/\@r\{([^}]*)}/\@in_roman\{$1}/g;
s/\@var\{([^}]*)}/\@in_italics\{$1}/g;
s/\@b\{([^}]*)}/\@in_bold\{$1}/g;
s/\@strong\{([^}]*)}/\@in_bold\{$1}/g;
# remove trailing comma from xref because man won't include the page number
s/\@xref\{([^}]*)},/\@xref\{$1}/g;
s/\@xref\{([^}]*)}/See \@in_italics\{$1}/g;
s/\@ref\{([^}]*)}/\@ref\{$1}/g;
s/\@ref\{([^}]*)}/\@in_italics\{$1}/g;
s/\@pxref\{([^}]*)}/see \@in_italics\{$1}/g;
s/\@uref\{([^}]*)}/\@in_roman\{$1}/g;
if (/\@chapter.*\@command/)
{
s/\@command\{([^}]*)}/\@in_italics\{$1}/g;
}
# show in constant-width font
s/\@code\{([^}]*)}/\@constwid\{$1}/g;
s/\@command\{([^}]*)}/\@constwid\{$1}/g;
s/\@env\{([^}]*)}/\@constwid\{$1}/g;
# show in constant-width oblique font
s/\@kbd\{([^}]*)}/\@constwidI\{$1}/g;
# show in constant-width font with single quotes
s/\@file\{([^}]*)}/\@constwidQ\{$1}/g;
s/\@option\{([^}]*)}/\@constwidQ\{$1}/g;
# Pass ASCII double quotes to .CQ encoded as two double quotes
# disallow single quotes here because groff converts them to
# typographical closing quotes.
# This substitution works only in very limited circumstances, and
# needs extension to handle the general case of ASCII quotes in
# sample text
s/\@samp\{([^}]*)["']{2,2}}/\@samp\{$1""""}/g;
s/\@samp\{(.*\@(tie|no_break_space)\{})["']{2,2}}/\@samp\{$1""""}/g;
s/\@samp\{([^}]*)}/\@constwidQ\{$1}/g;
s/\@sc\{([^}]*)}/\@to_upper\{$1}/g;
s/\@key\{([^}]*)}/\@in_italics\{$1}/g;
s/\@footnote\{([^}]*)}/\@in_square_br\{$1}/g;
s/\@math\{([^}]*)}/\@no_decoration\{$1}/g;
if (/\@w\{([^}]*)}/) {
s/\@w\{([^}]*)}/\@no_break_word\{$1}/g;
}
s/\@minus\{}/\\-/g;
s/\@copyright\{}/\\(co/g;
s/\@noindent//;
s/\@\{/{/g;
s/\@}/}/g;
s/\@\@/@/g;
s/---/\\(em/g;
s/\@in_sgl_quotes\{([^}]+)}/`$1'/g;
s/\@in_dbl_quotes\{([^}]+)}/\"$1\"/g;
s/\@in_italics\{([^}]+)}/\\fI$1\\fP/g;
s/\@in_roman\{([^}]+)}/\\fR$1\\fP/g;
s/\@in_bold\{([^}]+)}/\\fB$1\\fP/g;
s/\@to_upper\{([^}]*)}/\U$1\E/g;
s/\@no_decoration\{([^}]*)}/$1/g;
if (/\@no_break_word\{([^}]+)}(\S*)/) {
$_ = no_break_word("$_", '@no_break_word');
}
s/\@no_break_space\{}/\\ /g;
s/\@[ ]/ /g;
s/\@in_angle_br\{([^}]*)}/<$1>/g;
s/\@in_square_br\{([^}]*)}/[$1]/g;
# set up to use CW, CI, and CQ macros
# put every instance on a new line
# ensure that prepended and appended macros go on separate lines
# separate concatenated commands with spaces
s/([}])(\@constwid[IQ]*)/$1 $2/g;
s/(\@constwid[IQ]*\{[^}]+})(\@)/$1 $2/g;
# space before -> newline
s/\s+(\S*\@constwid[IQ]*\{[^}]+}\S*)/\n$1/g;
# space after -> newline
s/(\S*\@constwid[IQ]*\{[^}]+}\S*)\s+/$1\n/g;
if (/(\S*)\@constwidI\{([^}]+)}(\S*)/) {
$_ = CW_macro("$_", '@constwidI', ".CI");
}
if (/(\S*)\@constwidQ\{([^}]+)}(\S*)/) {
$_ = CW_macro("$_", '@constwidQ', ".CQ");
}
if (/(\S*)\@constwid\{([^}]+)}(\S*)/) {
$_ = CW_macro("$_", '@constwid', ".CW");
}
# handle backslash character in sample
s/(\.C[IQW]\s+\S+\s+)"\\"/$1"\\e"/g;
s/(\.C[IQW]\s+)"\\"/$1"\\e"/g;
# handle backslash character in Windows pathname
# starts with a drive specifier ...
if (/(\.C[IQW]\s+"[[:alpha:]]:)/) {
# don't change font switches or escaped spaces
s/(\S)\\(?!(\s|f[RIBP]|f\([A-Z]{2}))/$1\\e/g;
}
# some versions of n/troff don't have \(en, so use \-
# don't replace double hyphens in C[IQW] macros; assume true en
# dashes will be closed up to previous word
s/([^" ]+)--/$1\\-/g;
s/\@value\{([^\s]+)}/$value{$1}/eg;
if (/\@set\s+([^\s]+)\s+(.*)$/) { $value{$1} = $2; next; }
if (/\@clear\s+([^\s]+)\s+(.*)$/) { delete $value{$1}; next; }
# works only for @item and @itemx as used in units(1)
if (/\@itemx (.*)/)
{
$samp = $1;
# add hair space to visually separate the hyphens in roman type
$samp =~ s/--/-\\^-/;
$samp =~ s/-([[:alnum:]])/-\\^$1/;
if (!$diditem)
{ printf(".TP\n.BR \"$samp\""); }
else
{ printf(" \", \" \"$samp\""); }
$diditem=1; next;
}
elsif ($diditem) { printf("\n"); $diditem=0; }
if (/\@item (.*)/)
{
$samp = $1;
# add hair space to visually separate the hyphens in roman type
$samp =~ s/--/-\\^-/;
$samp =~ s/-([[:alnum:]])/-\\^$1/;
printf("%s.TP\n%s.BR \"$samp\"", $manprefix, $manprefix);
$diditem=1;
next;
}
if (s/\@chapter (.*)/.SH \U$1\E/)
{
# restore proper case on font switches
s/\\FR/\\fR/g;
s/\\FI/\\f(BI/g; # chapter headings (SH in man) are bold
s/\\FP/\\fP/g;
printf("%s%s", $manprefix, $_);
$justdidlp=1;
next;
}
if (s/\@section (.*)/$1/)
{
printf("%s.SS %s", $manprefix, $_);
next;
}
# FIXME? why do we need $manprefix for these?
# input/output example macros
if (/\@example/) { printf("%s.ES\n", $manprefix); $example=1; next; }
if (/\@end example/) { printf("%s.EE\n", $manprefix); $example=0; $justdidlp=0; next; }
if (/\@smallexample/) { printf("%s.ES S\n", $manprefix); $example=1; next; }
if (/\@end smallexample/) { printf("%s.EE\n", $manprefix); $example=0; $justdidlp=0; next; }
# no CW font
if (/\@display/) { printf("%s.DS\n", $manprefix, $manprefix); $example=1; next; }
if (/\@end display/) { printf("%s.DE\n", $manprefix, $manprefix); $example=0; next; }
# no CW font, no indent
if (/\@format/) { printf("%s.nf\n", $manprefix); $example=1; next; }
if (/\@end format/) { printf("%s.fi\n", $manprefix); $example=0; next; }
if ($example) { s/\\\s*$/\\e\n/ };
if (!$example && /^\s*$/ && !$doman)
{
if ($justdidlp) { next; }
printf(".PP\n");
$justdidlp=1;
next;
}
if (/^\@/) { next; }
printf("%s%s", $manprefix, $_);
if (!$doman) { $justdidlp=0; }
}
# Extensions to legacy man macro package. groff loads the man macro file
# after the call of TH, so these definitions must likewise follow that
# call of TH if they are overwrite any groff extensions with the same
# names that might be added in the future.
sub add_extensions
{
# ensure that ASCII circumflex U+005E (^) is not remapped with groff
printf(".\\\"\n");
printf(".\\\" ensure that ASCII circumflex U+005E (^) is not remapped with groff\n");
printf(".if \\n(.g .tr ^\\(ha\n");
# ellipsis: space periods with troff but not with nroff
printf(".\\\" ellipsis: space periods with troff but not with nroff\n");
printf(".if n .ds El \\&...\n");
printf(".if t .ds El \\&.\\ .\\ .\n");
# constant-width font
printf(".\\\"\n");
printf(".\\\" Extensions to man macros\n");
printf(".\\\"\n");
printf(".\\\" Constant-width font\n");
printf(".de CW\n");
printf(".hy 0\n");
# just single quotes with nroff
printf(".if n \\{\\\n");
printf(".ie \\\\n(.\$>2 \\&\\\\\$1'\\\\\$2'\\\\\$3\n");
printf(".el \\&'\\\\\$1'\\\\\$2\n");
printf(".\\}\n");
# constant-width font with troff
printf(".if t \\{\\\n");
printf(".ie \\\\n(.\$>2 \\&\\\\\$1\\f(CW\\\\\$2\\fR\\\\\$3\n");
printf(".el \\&\\f(CW\\\\\$1\\fR\\\\\$2\n");
printf(".\\}\n");
printf(".hy 14\n");
printf("..\n");
# constant-width oblique font
printf(".\\\" Constant-width oblique font\n");
printf(".de CI\n");
printf(".hy 0\n");
# single quotes with nroff
printf(".if n \\{\\\n");
printf(".ie \\\\n(.\$>2 \\&\\\\\$1'\\fI\\\\\$2\\fR'\\\\\$3\n");
printf(".el \\&'\\fI\\\\\$1\\fR'\\\\\$2\n");
printf(".\\}\n");
# constant-width oblique font with troff
printf(".if t \\{\\\n");
printf(".ie \\\\n(.\$>2 \\&\\\\\$1\\f(CI\\\\\$2\\fR\\\\\$3\n");
printf(".el \\&\\f(CI\\\\\$1\\fR\\\\\$2\n");
printf(".\\}\n");
printf(".hy 14\n");
printf("..\n");
# constant-width font with quotes with troff
printf(".\\\" Constant-width font with quotes\n");
printf(".de CQ\n");
printf(".hy 0\n");
# just single quotes with nroff
printf(".if n \\{\\\n");
printf(".ie \\\\n(.\$>2 \\&\\\\\$1'\\\\\$2'\\\\\$3\n");
printf(".el \\&'\\\\\$1'\\\\\$2\n");
printf(".\\}\n");
# constant-width font with troff
printf(".if t \\{\\\n");
# quotes passed as literal text encoded as \(fm
# make it a double quote because groff converts ` and ' to opening and
# closing quotes
printf(".ie \\\\n(.\$>2 \\&\\\\\$1`\\f(CW\\\\\$2\\fR'\\\\\$3\n");
printf(".el \\&`\\f(CW\\\\\$1\\fR'\\\\\$2\n");
printf(".\\}\n");
printf(".hy 14\n");
printf("..\n");
# Display Start--indent, no fill
printf(".\\\" Display start\n");
printf(".de DS\n");
printf(".hy 0\n");
printf(".if t .in +4n\n");
printf(".if n .in +3n\n");
printf(".nf\n");
printf("..\n");
# Display End
printf(".\\\" Display end\n");
printf(".de DE\n");
printf(".fi\n");
printf(".in\n");
printf(".hy 14\n");
printf("..\n");
# Example Start--like display, but with font CW
printf(".\\\" Example start\n");
printf(".de ES\n");
# call before size or font change to get consistent indent
printf(".DS\n");
# CW font with troff; optionally reduce size
printf(".if t \\{\\\n");
printf(".if '\\\\\$1'S' \\{\\\n");
printf(".nr Ex 1\n");
printf(".ps -1\n");
printf(".\\}\n");
printf(".el .nr Ex 0\n");
printf(".nr mE \\\\n(.f\n");
printf(".ft CW\n");
printf(".\\}\n");
printf("..\n");
# Example End
printf(".\\\" Example end\n");
printf(".de EE\n");
# restore font and size with troff
printf(".if t \\{\\\n");
printf(".ft \\\\n(mE\n");
printf(".if \\\\n(Ex=1 .ps\n");
printf(".\\}\n");
printf(".DE\n");
printf("..\n");
}
# convert texinfo commands to .C[IQW] macros
sub CW_macro
{
my $line = shift;
my $from = shift;
my $to = shift;
# prepended and appended punctuation
$line =~ s/(\S+)$from\{([^}]+)}(\S+)/$to $1 "$2" $3/g;
# prepended punctuation
$line =~ s/(\S+)$from\{([^}]+)}/$to $1 "$2" ""/g;
# appended punctuation
$line =~ s/$from\{([^}]+)}(\S+)/$to "$1" $2/g;
# just the argument
$line =~ s/$from\{([^}]+)}/$to "$1"/g;
return $line;
}
# convert all spaces within @w{...} to unbreakable
sub no_break_word
{
my $line = shift;
my $pattern = (shift) . "\{";
my $len = length($pattern);
my $ndx = -1;
my $bracelevel = 0;
my $char;
while (($ndx = index($line, $pattern, $ndx)) > -1) {
# get rid of the @ command and opening brace
substr($line, $ndx, $len, '');
$bracelevel = 1;
while ($bracelevel > 0) {
$char = substr($line, $ndx, 1);
# end of line and braces not closed
if ($char eq "") {
last;
}
elsif ($char eq '{') {
$bracelevel++;
}
elsif ($char eq '}') {
$bracelevel--;
}
# make spaces nonbreaking
if ($char eq ' ') {
substr($line, $ndx++, 1, '\ ');
$ndx++;
# assume multiple spaces are not wanted
while (substr($line, $ndx, 1) eq ' ') {
substr($line, $ndx, 1, '');
}
}
$ndx++;
}
# get rid of the closing brace for the @ command. This should
# always be true unless theres an internal brace mismatch ...
if (substr($line, $ndx - 1, 1) eq '}' ) {
substr($line, $ndx - 1, 1, '');
}
else {
die "Missing closing '}'";
}
}
return $line;
}
units-2.12/NEWS 0000664 0001750 0001750 00000024472 12607610570 012574 0 ustar adrian adrian GNU units NEWS - User visible changes.
Copyright (C) 1996, 1997, 1999-2007, 2010-2015 Free Software Foundation, Inc.
Version 2.12 - 14 October 2015
* Updated and revised units database, with constants now based on 2014 CODATA.
* Readline history is persistent and is saved to ~/.units_history, or
to the file specified with --history (-H) option.
* Fixed bug where '_' didn't give last result after conversion to function.
* Fixed sporadic segmentation fault with --log.
* Comments allowed on interactive input with '#', most useful with logging.
* Added configure test for rl_completion_suppress_append, which helps
compilation under MacOS.
* Comment processing happens before checking UTF-8 validity---comments
are allowed to contain bogus UTF-8.
* Changed units_cur to skip bogus precious metals data from timegenie
and to skip currencies with no rate.
Version 2.11 - 2 April 2014 (bug fix release)
* Many long options didn't work.
* units_cur wouldn't print to stdout
Version 2.10 - 19 March 2014
* Added '_' to represent the previous result.
* Added support for rational exponents with numerators larger than 1 so you
can do calculations like liter^2|3.
* Added logging with --log (-L) option.
* Fixed some unit definitions (R_infinity, planckmass), and added
R_K90 and K_J90 for the conventional values of the von Klitzing and
Josephson constants.
* Don't use readline unless reading from a tty. This makes it much faster to
run units through a pipe and also gives consistent behavior between versions
compiled with and without readline.
* Display of nonlinear unit definitions shows the range over which the unit is
defined and the required dimensions of the argument.
* Unit completion with readline will now complete nonlinear units, functions
(e.g. cuberoot), prefixes, and unit list aliases. It will no longer insert a
space after the completion.
* Running "units --version" returns success.
* Combining "--version" with "--terse" gives a terse version output.
* Combining "--version" with "--verbose" or running with "--info" gives a
detailed output of how units was compiled and where its supporting files are
found.
* A nonlinear unit can be defined equal to another nonlinear unit using the
syntax: "newfunc() oldfunc".
* Domain and range specified with nonlinear units can be open intervals,
indicated by parentheses instead of brackets.
* The "noerror" keyword on a nonlinear unit supresses error checking with
"units --check" for that unit.
* Changes to units_cur to work with timegenie changes and to support Python 3.
The Python module unidecode is now required for units_cur.
* The method for finding supporting files has changed when units is compiled to
be relocatable. See the manual for details. The --enable-path-search
configure option is replaced by --enable-relocation.
* Fix to compile with Bison 3.0.
* Improved error messages for various cases.
* Units can be compiled and installed under Windows with Microsoft Visual C++
using Makefile.Win. A Windows binary distribution is available.
* Some simple icons are included.
Version 2.02 - 11 July 2013
* Added support for %a and %A output formats (hexadecimal floating point), and
eliminated the restriction on the number of displayed digits when specifying
an output format with the --output-format (-o) option. Improved error
handling for formats specified with --output-format.
* Added --digits (-d) to specify the number of digits to display. Giving
'--digits max' (-dmax) will use the full available precision.
* Added support for various Unicode minus sign symbols. Units now treats the
figure dash (U+2012), the en dash (U+2013), and the minus (U+2212) as
identical to the ASCII hyphen/minus symbol (U+002D).
* The !message command in units data files has been fixed so it does not
produce output when the --quiet option is given.
* Improved error handling when unit names end with numbers without a '_'.
* Removed six unicode entries from definition.units that were flagged as
invalid under MacOS.
* Modified units_cur to work with XML format as the txt format disappeared.
* Corrected error in definition of the nat.
* Improved manual.
Version 2.01 - 24 October 2012 (bug fix release)
* Fixed error in electronmass
* New definition for au
* Fixed DESTDIR support for installation
* Changed configure script for success with Solaris
* Small changes to manual
Version 2.00 - 6 June 2012
General changes:
* Unit lists provide conversion to sums of units (e.g. feet and inches).
* Added --round (-r) and --show-factor (-S) options for use with unit lists.
* Added unit lists aliases (e.g. time, usvol).
* A python script, units_cur, can update currency data.
* Units now flushes its output so you can talk to it with a pipe.
* Units now works in UTF-8 if the system supports it.
* Added --locale (-l) option to set the locale.
* English units such as the gallon are defined in all locales, with US
definitions by default except in the en_BG locale. You can force
the desired definition (Great Britain or US) by setting the
environment variable UNITS_ENGLISH to GB or US.
* Revised and extended the documentation, with more examples.
* Added locale mapping to address Windows locale names.
* Updated and revised units database, including UTF-8 definitions and
the 2010 CODATA.
* Fixed parsing bug for "1..2" or "1.2.3". These now give an error.
* Unit names can end with a number in the form of a subscript that
starts with a '_', as in 'X_3'.
* Units now performs error checking on the printf format specified with the
--output-format (-o) option.
Changes for units definition files:
* Changed location and names of unit database, splitting off currency
Files are /usr/local/share/units/{definitions,currency}.units and
the personal units file is $HOME/.units instead of $HOME/units.dat.
(Under windows personal unit file is unitdef.units.)
* Personal units filename can be changed with MYUNITSFILE environment variable.
* Prefixes can be defined in any order: it is no longer necessary to
define longer ones before shorter ones.
* New definitions replace previous ones. Personal units file is read
after the system file rather than before.
* Changed syntax for function definitions. Instead of [in-unit,out-unit]
you must now write units=[in-unit,out-unit]. Use 'units -c' to find
places in your personal data files that need to be updated.
* Add optional domain and range to function definitions with syntax
domain=[min,max] and range=[min,max]. Either min or max can be
omitted to signal infinity.
* Unit list aliases can be defined with !unitlist command.
* Added !var and !varnot and !endvar to include definitions based on
environment variable settings.
* Added !set to set environment variables (if they aren't already set).
* Added !message to display a message
* Data files are in UTF-8, with !utf8 and !endutf8 commands to mark
definitions that require UTF-8 support.
* Improved error handling when reading units.dat.
Version 1.88 - 15 Feb 2010
* Updated units.dat
* Fixed bug involving readline version 4.2
Version 1.87 - 25 Sep 2007
* Units reads ~/.units.dat if it exists before reading the standard
units database.
* Added support for ** as an exponent operator.
* Type 'search text' to list units that contain 'text' in their name.
* Precedence of '*' changed to match precedence of '/'.
(Multiplication by juxtaposition retains a higher precedence than
'/'.) The --oldstar option selects the old precedence and --newstar
forces the new precedence.
Version 1.86 - 10 Nov 2006
* Added --one-line (-1) option which causes the program to print only
one line of output.
* Added --compact option which causes the program to print only the
conversion factors and a newline on output.
* Added build support for DESTDIR.
* Made minor changes that allow the program to be compiled into a
library and linked with other programs.
* Fixed bug that caused bus error on Intel Mac.
Version 1.85 - 20 May 2005
* The '-' character by default indicates subtraction. Multiplication can be
obtained by '*' or ' '. The --product (-p) option selects the old behavior
where '-' acts as a multiplication operator. The --minus (-m) option forces
the default behavior where '-' indicates subtraction.
* Handing of radian and steradian changed. These units are now treated as
conformable with 1 for units conversions. This is indicated by the
"!dimensionless" tag in units.dat.
* Unit files can be included using !include.
* Multiple -f (--file) options can appear on the command line; giving
a null filename (-f '') causes the default units database to be loaded.
* Added -t (--terse) option.
* Improved error checking for units.dat.
* Corrected and extended units.dat.
Version 1.81 - October 28, 2002
* Fixed missing definition of "au" in units.dat.
Version 1.80 - June 16, 2002
* Rewritten parser supports
- () for grouping
- noninteger powers of numbers (e.g. 3^0.25)
- functions with dimensionless arguments (log, ln, log2, sin, cos, tan, exp)
- roots of units: sqrt(unit), cuberoot(unit), and higher roots as unit^(1|4)
* Functions can be defined in units.dat, and conversion to a function
performed by specifying the function name alone as the "want" item.
* Unit conversions can be specified as tables with linear interpolation.
* The "help" command summarizes operations, and "help unit" browses the units
database at the definition of the specified unit.
* Specifying "?" for the want unit gets a list of all conformable units.
* Support for locales added.
* Units file extended and corrected.
Version 1.55 - July 30, 1999
* Added over 600 new units and corrected errors in the units data file.
* Minor bug fix affecting unit name completion.
Version 1.54 - July 15, 1997
* Switched order of prefix and plural handling (plurals are now done first)
* Added reciprocal unit conversion and --strict (-s) option
* Fixed some erroneous unit definitions, added currency codes and other units
* Improved Makefile (exec-prefix, program-transform-name supported)
* Bug fixes
Version 1.53 - Jan 13, 1997
* Added units containing ISO 8859-1 characters
* Bug fixes
Version 1.52 - Dec 18, 1996
* Sums of conformable units
* Printing of unit definitions
* Unitname completion with readline
* Added --verbose (-v) option and moved --version to -V
* Improved portability, old style C support, improved Makefile
units-2.12/units.txt 0000664 0001750 0001750 00000330423 12607541441 013774 0 ustar adrian adrian UNITS(1) General Commands Manual UNITS(1)
NAME
units -- unit conversion and calculation program
SYNOPSIS
'units' [options] [from-unit [to-unit]]
DESCRIPTION
The 'units' program converts quantities expressed in various systems of
measurement to their equivalents in other systems of measurement. Like
many similar programs, it can handle multiplicative scale changes. It
can also handle nonlinear conversions such as Fahrenheit to Celsius;
see Temperature Conversions. The program can also perform conversions
from and to sums of units, such as converting between meters and feet
plus inches.
Basic operation is simple: you enter the units that you want to convert
from and the units that you want to convert to. You can use the pro-
gram interactively with prompts, or you can use it from the command
line.
Beyond simple unit conversions, 'units' can be used as a general-pur-
pose scientific calculator that keeps track of units in its calcula-
tions. You can form arbitrary complex mathematical expressions of
dimensions including sums, products, quotients, powers, and even roots
of dimensions. Thus you can ensure accuracy and dimensional consis-
tency when working with long expressions that involve many different
units that may combine in complex ways; for an illustration, see Com-
plicated Unit Expressions.
The units are defined in an external data file. You can use the exten-
sive data file that comes with this program, or you can provide your
own data file to suit your needs. You can also use your own data file
to supplement the standard data file.
You can change the default behavior of 'units' with various options
given on the command line. See Invoking Units for a description of the
available options.
INTERACTING WITH UNITS
To invoke units for interactive use, type 'units' at your shell prompt.
The program will print something like this:
Currency exchange rates from www.timegenie.com on 2014-03-05
2860 units, 109 prefixes, 85 nonlinear units
You have:
At the 'You have:' prompt, type the quantity and units that you are
converting from. For example, if you want to convert ten meters to
feet, type '10 meters'. Next, 'units' will print 'You want:'. You
should type the units you want to convert to. To convert to feet, you
would type 'feet'. If the 'readline' library was compiled in then tab
will complete unit names. See Readline Support for more information
about 'readline'. To quit the program under Unix, press Ctrl-C or
Ctrl-D. Under Windows, press Ctrl-C or Ctrl-Z; with the latter, you may
also need to press Enter.
The result will be displayed in two ways. The first line of output,
which is marked with a '*' to indicate multiplication, gives the result
of the conversion you have asked for. The second line of output, which
is marked with a '/' to indicate division, gives the inverse of the
conversion factor. If you convert 10 meters to feet, 'units' will
print
* 32.808399
/ 0.03048
which tells you that 10 meters equals about 32.8 feet. The second num-
ber gives the conversion in the opposite direction. In this case, it
tells you that 1 foot is equal to about 0.03 dekameters since the
dekameter is 10 meters. It also tells you that 1/32.8 is about 0.03.
The 'units' program prints the inverse because sometimes it is a more
convenient number. In the example above, for example, the inverse
value is an exact conversion: a foot is exactly 0.03048 dekameters.
But the number given the other direction is inexact.
If you convert grains to pounds, you will see the following:
You have: grains
You want: pounds
* 0.00014285714
/ 7000
From the second line of the output you can immediately see that a
grain is equal to a seven thousandth of a pound. This is not so obvi-
ous from the first line of the output. If you find the output format
confusing, try using the '--verbose' option:
You have: grain
You want: aeginamina
grain = 0.00010416667 aeginamina
grain = (1 / 9600) aeginamina
If you request a conversion between units that measure reciprocal
dimensions, then 'units' will display the conversion results with an
extra note indicating that reciprocal conversion has been done:
You have: 6 ohms
You want: siemens
reciprocal conversion
* 0.16666667
/ 6
Reciprocal conversion can be suppressed by using the '--strict' option.
As usual, use the '--verbose' option to get more comprehensible output:
You have: tex
You want: typp
reciprocal conversion
1 / tex = 496.05465 typp
1 / tex = (1 / 0.0020159069) typp
You have: 20 mph
You want: sec/mile
reciprocal conversion
1 / 20 mph = 180 sec/mile
1 / 20 mph = (1 / 0.0055555556) sec/mile
If you enter incompatible unit types, the 'units' program will print a
message indicating that the units are not conformable and it will dis-
play the reduced form for each unit:
You have: ergs/hour
You want: fathoms kg^2 / day
conformability error
2.7777778e-11 kg m^2 / sec^3
2.1166667e-05 kg^2 m / sec
If you only want to find the reduced form or definition of a unit, sim-
ply press Enter at the 'You want:' prompt. Here is an example:
You have: jansky
You want:
Definition: fluxunit = 1e-26 W/m^2 Hz = 1e-26 kg / s^2
The output from 'units' indicates that the jansky is defined to be
equal to a fluxunit which in turn is defined to be a certain combina-
tion of watts, meters, and hertz. The fully reduced (and in this case
somewhat more cryptic) form appears on the far right.
Some named units are treated as dimensionless in some situations.
These units include the radian and steradian. These units will be
treated as equal to 1 in units conversions. Power is equal to torque
times angular velocity. This conversion can only be performed if the
radian is dimensionless.
You have: (14 ft lbf) (12 radians/sec)
You want: watts
* 227.77742
/ 0.0043902509
It is also possible to compute roots and other non-integer powers of
dimensionless units; this allows computations such as the altitude of
geosynchronous orbit:
You have: cuberoot(G earthmass / (circle/siderealday)^2) - earthradius
You want: miles
* 22243.267
/ 4.4957425e-05
Named dimensionless units are not treated as dimensionless in other
contexts. They cannot be used as exponents so for example,
'meter^radian' is forbidden.
If you want a list of options you can type '?' at the 'You want:'
prompt. The program will display a list of named units that are con-
formable with the unit that you entered at the 'You have:' prompt
above. Conformable unit combinations will not appear on this list.
Typing 'help' at either prompt displays a short help message. You can
also type 'help' followed by a unit name. This will invoke a pager on
the units data base at the point where that unit is defined. You can
read the definition and comments that may give more details or histori-
cal information about the unit. (You can generally quit out of the
page by pressing 'q'.)
Typing 'search' text will display a list of all of the units whose
names contain text as a substring along with their definitions. This
may help in the case where you aren't sure of the right unit name.
USING UNITS NON-INTERACTIVELY
The 'units' program can perform units conversions non-interactively
from the command line. To do this, type the command, type the original
unit expression, and type the new units you want. If a units expres-
sion contains non-alphanumeric characters, you may need to protect it
from interpretation by the shell using single or double quote charac-
ters.
If you type
units "2 liters" quarts
then 'units' will print
* 2.1133764
/ 0.47317647
and then exit. The output tells you that 2 liters is about 2.1 quarts,
or alternatively that a quart is about 0.47 times 2 liters.
If the conversion is successful, then 'units' will return success
(zero) to the calling environment. If you enter non-conformable units
then 'units' will print a message giving the reduced form of each unit
and it will return failure (nonzero) to the calling environment.
When you invoke 'units' with only one argument, it will print out the
definition of the specified unit. It will return failure if the unit
is not defined and success if the unit is defined.
UNIT DEFINITIONS
The conversion information is read from a units data file that is
called 'definitions.units' and is usually located in the
'/usr/share/units' directory. If you invoke 'units' with the '-V'
option, it will print the location of this file. The default file
includes definitions for all familiar units, abbreviations and metric
prefixes. It also includes many obscure or archaic units.
Many constants of nature are defined, including these:
pi ratio of circumference to diameter
c speed of light
e charge on an electron
force acceleration of gravity
mole Avogadro's number
water pressure per unit height of water
Hg pressure per unit height of mercury
au astronomical unit
k Boltzman's constant
mu0 permeability of vacuum
epsilon0 permittivity of vacuum
G Gravitational constant
mach speed of sound
The standard data file includes atomic masses for all of the elements
and numerous other constants. Also included are the densities of vari-
ous ingredients used in baking so that '2 cups flour_sifted' can be
converted to 'grams'. This is not an exhaustive list. Consult the
units data file to see the complete list, or to see the definitions
that are used.
The 'pound' is a unit of mass. To get force, multiply by the force
conversion unit 'force' or use the shorthand 'lbf'. (Note that 'g' is
already taken as the standard abbreviation for the gram.) The unit
'ounce' is also a unit of mass. The fluid ounce is 'fluidounce' or
'floz'. When British capacity units differ from their US counterparts,
such as the British Imperial gallon, the unit is defined both ways with
'br' and 'us' prefixes. Your locale settings will determine the value
of the unprefixed unit. Currency is prefixed with its country name:
'belgiumfranc', 'britainpound'.
When searching for a unit, if the specified string does not appear
exactly as a unit name, then the 'units' program will try to remove a
trailing 's', 'es'. Next units will replace a trailing 'ies' with 'y'.
If that fails, 'units' will check for a prefix. The database includes
all of the standard metric prefixes. Only one prefix is permitted per
unit, so 'micromicrofarad' will fail. However, prefixes can appear
alone with no unit following them, so 'micro*microfarad' will work, as
will 'micro microfarad'.
To find out which units and prefixes are available, read the standard
units data file, which is extensively annotated.
English Customary Units
English customary units differ in various ways in different regions.
In Britain a complex system of volume measurements featured different
gallons for different materials such as a wine gallon and ale gallon
that different by twenty percent. This complexity was swept away in
1824 by a reform that created an entirely new gallon, the British Impe-
rial gallon defined as the volume occupied by ten pounds of water.
Meanwhile in the USA the gallon is derived from the 1707 Winchester
wine gallon, which is 231 cubic inches. These gallons differ by about
twenty percent. By default if 'units' runs in the 'en_GB' locale you
will get the British volume measures. If it runs in the 'en_US' locale
you will get the US volume measures. In other locales the default val-
ues are the US definitions. If you wish to force different definitions
then set the environment variable 'UNITS_ENGLISH' to either 'US' or
'GB' to set the desired definitions independent of the locale.
Before 1959, the value of a yard (and other units of measure defined in
terms of it) differed slightly among English-speaking countries. In
1959, Australia, Canada, New Zealand, the United Kingdom, the United
States, and South Africa adopted the Canadian value of 1 yard =
0.9144 m (exactly), which was approximately halfway between the values
used by the UK and the US; it had the additional advantage of making
1 inch = 2.54 cm (exactly). This new standard was termed the Interna-
tional Yard. Australia, Canada, and the UK then defined all customary
lengths in terms of the International Yard (Australia did not define
the furlong or rod); because many US land surveys were in terms of the
pre-1959 units, the US continued to define customary surveyors' units
(furlong, chain, rod, and link) in terms of the previous value for the
foot, which was termed the US survey foot. The US defined a US survey
mile as 5280 US survey feet, and defined a statute mile as a US survey
mile. The US values for these units differ from the international val-
ues by about 2 ppm.
The 'units' program uses the international values for these units; the
US values can be obtained by using either the 'US' or the 'survey' pre-
fix. In either case, the simple familiar relationships among the units
are maintained, e.g., 1 'furlong' = 660 'ft', and 1 'USfurlong' = 660
'USft', though the metric equivalents differ slightly between the two
cases. The 'US' prefix or the 'survey' prefix can also be used to
obtain the US survey mile and the value of the US yard prior to 1959,
e.g., 'USmile' or 'surveymile' (but not 'USsurveymile'). To get the US
value of the statute mile, use either 'USstatutemile' or 'USmile'.
Except for distances that extend over hundreds of miles (such as in the
US State Plane Coordinate System), the differences in the miles are
usually insignificant:
You have: 100 surveymile - 100 mile
You want: inch
* 12.672025
/ 0.078913984
The pre-1959 UK values for these units can be obtained with the prefix
'UK'.
In the US, the acre is officially defined in terms of the US survey
foot, but 'units' uses a definition based on the international foot.
If you want the official US acre use 'USacre' and similarly use
'USacrefoot' for the official US version of that unit. The difference
between these units is about 4 parts per million.
UNIT EXPRESSIONS
Operators
You can enter more complicated units by combining units with operations
such as multiplication, division, powers, addition, subtraction, and
parentheses for grouping. You can use the customary symbols for these
operators when 'units' is invoked with its default options. Addition-
ally, 'units' supports some extensions, including high priority multi-
plication using a space, and a high priority numerical division opera-
tor ('|') that can simplify some expressions.
You multiply units using a space or an asterisk ('*'). The next exam-
ple shows both forms:
You have: arabicfoot * arabictradepound * force
You want: ft lbf
* 0.7296
/ 1.370614
You can divide units using the slash ('/') or with 'per':
You have: furlongs per fortnight
You want: m/s
* 0.00016630986
/ 6012.8727
You can use parentheses for grouping:
You have: (1/2) kg / (kg/meter)
You want: league
* 0.00010356166
/ 9656.0833
Multiplication using a space has a higher precedence than division
using a slash and is evaluated left to right; in effect, the first '/'
character marks the beginning of the denominator of a unit expression.
This makes it simple to enter a quotient with several terms in the
denominator: 'J / mol K'. The '*' and '/' operators have the same
precedence, and are evaluated left to right; if you multiply with '*',
you must group the terms in the denominator with parentheses:
'J / (mol * K)'.
The higher precedence of the space operator may not always be advanta-
geous. For example, 'm/s s/day' is equivalent to 'm / s s day' and has
dimensions of length per time cubed. Similarly, '1/2 meter' refers to
a unit of reciprocal length equivalent to 0.5/meter, perhaps not what
you would intend if you entered that expression. The get a half meter
you would need to use parentheses: '(1/2) meter'. The '*' operator is
convenient for multiplying a sequence of quotients. For example,
'm/s * s/day' is equivalent to 'm/day'. Similarly, you could write
'1/2 * meter' to get half a meter.
The 'units' program supports another option for numerical fractions:
you can indicate division of numbers with the vertical bar ('|'), so if
you wanted half a meter you could write '1|2 meter'. You cannot use
the vertical bar to indicate division of non-numerical units (e.g.,
'm|s' results in an error message).
Powers of units can be specified using the '^' character, as shown in
the following example, or by simple concatenation of a unit and its
exponent: 'cm3' is equivalent to 'cm^3'; if the exponent is more than
one digit, the '^' is required. You can also use '**' as an exponent
operator.
You have: cm^3
You want: gallons
* 0.00026417205
/ 3785.4118
Concatenation only works with a single unit name: if you write
'(m/s)2', 'units' will treat it as multiplication by 2. When a unit
includes a prefix, exponent operators apply to the combination, so
'centimeter3' gives cubic centimeters. If you separate the prefix from
the unit with any multiplication operator (e.g., 'centi meter^3'), the
prefix is treated as a separate unit, so the exponent applies only to
the unit without the prefix. The second example is equivalent to
'centi * (meter^3)', and gives a hundredth of a cubic meter, not a
cubic centimeter. The 'units' program is limited internally to prod-
ucts of 99 units; accordingly, expressions like 'meter^100' or
'joule^34' (represented internally as 'kg^34 m^68 / s^68') will fail.
The '|' operator has the highest precedence, so you can write the
square root of two thirds as '2|3^1|2'. The '^' operator has the sec-
ond highest precedence, and is evaluated right to left, as usual:
You have: 5 * 2^3^2
You want:
Definition: 2560
With a dimensionless base unit, any dimensionless exponent is meaning-
ful (e.g., 'pi^exp(2.371)'). Even though angle is sometimes treated as
dimensionless, exponents cannot have dimensions of angle:
You have: 2^radian
^
Exponent not dimensionless
If the base unit is not dimensionless, the exponent must be a rational
number p/q, and the dimension of the unit must be a power of q, so
'gallon^2|3' works but 'acre^2|3' fails. An exponent using the slash
('/') operator (e.g., 'gallon^(2/3)') is also acceptable; the parenthe-
ses are needed because the precedence of '^' is higher than that of
'/'. Since 'units' cannot represent dimensions with exponents greater
than 99, a fully reduced exponent must have q < 100. When raising a
non-dimensionless unit to a power, 'units' attempts to convert a deci-
mal exponent to a rational number with q < 100. If this is not possi-
ble 'units' displays an error message:
You have: ft^1.234
Base unit not dimensionless; rational exponent required
A decimal exponent must match its rational representation to machine
precision, so 'acre^1.5' works but 'gallon^0.666' does not.
Sums and Differences of Units
You may sometimes want to add values of different units that are out-
side the SI. You may also wish to use 'units' as a calculator that
keeps track of units. Sums of conformable units are written with the
'+' character, and differences with the '-' character.
You have: 2 hours + 23 minutes + 32 seconds
You want: seconds
* 8612
/ 0.00011611705
You have: 12 ft + 3 in
You want: cm
* 373.38
/ 0.0026782366
You have: 2 btu + 450 ft lbf
You want: btu
* 2.5782804
/ 0.38785542
The expressions that are added or subtracted must reduce to identical
expressions in primitive units, or an error message will be displayed:
You have: 12 printerspoint - 4 heredium
^
Illegal sum of non-conformable units
As usual, the precedence for '+' and '-' is lower than that of the
other operators. A fractional quantity such as 2 1/2 cups can be given
as '(2+1|2) cups'; the parentheses are necessary because multiplication
has higher precedence than addition. If you omit the parentheses,
'units' attempts to add '2' and '1|2 cups', and you get an error mes-
sage:
You have: 2+1|2 cups
^
Illegal sum or difference of non-conformable units
The expression could also be correctly written as '(2+1/2) cups'. If
you write '2 1|2 cups' the space is interpreted as multiplication so
the result is the same as '1 cup'.
The '+' and '-' characters sometimes appears in exponents like
'3.43e+8'. This leads to an ambiguity in an expression like '3e+2 yC'.
The unit 'e' is a small unit of charge, so this can be regarded as
equivalent to '(3e+2) yC' or '(3 e)+(2 yC)'. This ambiguity is
resolved by always interpreting '+' and '-' as part of an exponent if
possible.
Numbers as Units
For 'units', numbers are just another kind of unit. They can appear as
many times as you like and in any order in a unit expression. For
example, to find the volume of a box that is 2 ft by 3 ft by 12 ft in
steres, you could do the following:
You have: 2 ft 3 ft 12 ft
You want: stere
* 2.038813
/ 0.49048148
You have: $ 5 / yard
You want: cents / inch
* 13.888889
/ 0.072
And the second example shows how the dollar sign in the units conver-
sion can precede the five. Be careful: 'units' will interpret '$5'
with no space as equivalent to 'dollar^5'.
Built-in Functions
Several built-in functions are provided: 'sin', 'cos', 'tan', 'ln',
'log', 'log2', 'exp', 'acos', 'atan' and 'asin'. The 'sin', 'cos', and
'tan' functions require either a dimensionless argument or an argument
with dimensions of angle.
You have: sin(30 degrees)
You want:
Definition: 0.5
You have: sin(pi/2)
You want:
Definition: 1
You have: sin(3 kg)
^
Unit not dimensionless
The other functions on the list require dimensionless arguments. The
inverse trigonometric functions return arguments with dimensions of
angle.
If you wish to take roots of units, you may use the 'sqrt' or
'cuberoot' functions. These functions require that the argument have
the appropriate root. You can obtain higher roots by using fractional
exponents:
You have: sqrt(acre)
You want: feet
* 208.71074
/ 0.0047913202
You have: (400 W/m^2 / stefanboltzmann)^(1/4)
You have:
Definition: 289.80882 K
You have: cuberoot(hectare)
^
Unit not a root
Previous Result
You can insert the result of the previous conversion using the under-
score ('_'). It is useful when you want to convert the same input to
several different units, for example
You have: 2.3 tonrefrigeration
You want: btu/hr
* 27600
/ 3.6231884e-005
You have: _
You want: kW
* 8.0887615
/ 0.12362832
Suppose you want to do some deep frying that requires an oil depth of
2 inches. You have 1/2 gallon of oil, and want to know the largest-
diameter pan that will maintain the required depth. The nonlinear unit
'circlearea' gives the radius of the circle (see Other Nonlinear Units,
for a more detailed description) in SI units; you want the diameter in
inches:
You have: 1|2 gallon / 2 in
You want: circlearea
0.10890173 m
You have: 2 _
You want: in
* 8.5749393
/ 0.1166189
In most cases, surrounding white space is optional, so the previous
example could have used '2_'. If '_' follows a non-numerical unit sym-
bol, however, the space is required:
You have: m_
^
Parse error
When '_' is followed by a digit, the operation is multiplication rather
than exponentiation, so that '_2', is equivalent to '_ * 2' rather than
'_^2'.
You can use the '_' symbol any number of times; for example,
You have: m
You want:
Definition: 1 m
You have: _ _
You want:
Definition: 1 m^2
Using '_' before a conversion has been performed (e.g., immediately
after invocation) generates an error:
You have: _
^
No previous result; '_' not set
Accordingly, '_' serves no purpose when 'units' is invoked non-interac-
tively.
If 'units' is invoked with the '--verbose' option (see Invoking Units),
the value of '_' is not expanded:
You have: mile
You want: ft
mile = 5280 ft
mile = (1 / 0.00018939394) ft
You have: _
You want: m
_ = 1609.344 m
_ = (1 / 0.00062137119) m
You can give '_' at the 'You want:' prompt, but it usually is not very
useful.
Complicated Unit Expressions
The 'units' program is especially helpful in ensuring accuracy and
dimensional consistency when converting lengthy unit expressions. For
example, one form of the Darcy-Weisbach fluid-flow equation is
Delta P = (8 / pi)^2 (rho fLQ^2) / d^5,
where Delta P is the pressure drop, rho is the mass density, f is the
(dimensionless) friction factor, L is the length of the pipe, Q is the
volumetric flow rate, and d is the pipe diameter. It might be desired
to have the equation in the form
Delta P = A1 rho fLQ^2 / d^5
that accepted the user's normal units; for typical units used in the
US, the required conversion could be something like
You have: (8/pi^2)(lbm/ft^3)ft(ft^3/s)^2(1/in^5)
You want: psi
* 43.533969
/ 0.022970568
The parentheses allow individual terms in the expression to be entered
naturally, as they might be read from the formula. Alternatively, the
multiplication could be done with the '*' rather than a space; then
parentheses are needed only around 'ft^3/s' because of its exponent:
You have: 8/pi^2 * lbm/ft^3 * ft * (ft^3/s)^2 /in^5
You want: psi
* 43.533969
/ 0.022970568
Without parentheses, and using spaces for multiplication, the previous
conversion would need to be entered as
You have: 8 lb ft ft^3 ft^3 / pi^2 ft^3 s^2 in^5
You want: psi
* 43.533969
/ 0.022970568
Backwards Compatibility:
'*' and '-' The original 'units' assigned multiplication a higher
precedence than division using the slash. This differs from the usual
precedence rules, which give multiplication and division equal prece-
dence, and can be confusing for people who think of units as a
calculator.
The star operator ('*') included in this 'units' program has, by
default, the same precedence as division, and hence follows the usual
precedence rules. For backwards compatibility you can invoke 'units'
with the '--oldstar' option. Then '*' has a higher precedence than
division, and the same precedence as multiplication using the space.
Historically, the hyphen ('-') has been used in technical publications
to indicate products of units, and the original 'units' program treated
it as a multiplication operator. Because 'units' provides several
other ways to obtain unit products, and because '-' is a subtraction
operator in general algebraic expressions, 'units' treats the binary
'-' as a subtraction operator by default. For backwards compatibility
use the '--product' option, which causes 'units' to treat the binary
'-' operator as a product operator. When '-' is a multiplication oper-
ator it has the same precedence as multiplication with a space, giving
it a higher precedence than division.
When '-' is used as a unary operator it negates its operand. Regard-
less of the 'units' options, if '-' appears after '(' or after '+' then
it will act as a negation operator. So you can always compute 20
degrees minus 12 minutes by entering '20 degrees + -12 arcmin'. You
must use this construction when you define new units because you cannot
know what options will be in force when your definition is processed.
NONLINEAR UNIT CONVERSIONS
Nonlinear units are represented using functional notation. They make
possible nonlinear unit conversions such as temperature.
Temperature Conversions
Conversions between temperatures are different from linear conversions
between temperature increments--see the example below. The absolute
temperature conversions are handled by units starting with 'temp', and
you must use functional notation. The temperature-increment conver-
sions are done using units starting with 'deg' and they do not require
functional notation.
You have: tempF(45)
You want: tempC
7.2222222
You have: 45 degF
You want: degC
* 25
/ 0.04
Think of 'tempF(x)' not as a function but as a notation that indicates
that x should have units of 'tempF' attached to it. See Defining Non-
linear Units. The first conversion shows that if it's 45 degrees
Fahrenheit outside, it's 7.2 degrees Celsius. The second conversion
indicates that a change of 45 degrees Fahrenheit corresponds to a
change of 25 degrees Celsius. The conversion from 'tempF(x)' is to
absolute temperature, so that
You have: tempF(45)
You want: degR
* 504.67
/ 0.0019814929
gives the same result as
You have: tempF(45)
You want: tempR
* 504.67
/ 0.0019814929
But if you convert 'tempF(x)' to 'degC', the output is probably not
what you expect:
You have: tempF(45)
You want: degC
* 280.37222
/ 0.0035666871
The result is the temperature in K, because 'degC' is defined as 'K',
the Kelvin. For consistent results, use the 'tempX' units when convert-
ing to a temperature rather than converting a temperature increment.
The 'tempC()' and 'tempF()' definitions are limited to positive abso-
lute temperatures, and giving a value that would result in a negative
absolute temperature generates an error message:
You have: tempC(-275)
^
Argument of function outside domain
^
Other Nonlinear Units
Some other examples of nonlinear units are numerous different ring
sizes and wire gauges, the grit sizes used for abrasives, the decibel
scale, shoe size, scales for the density of sugar (e.g., baume). The
standard data file also supplies units for computing the area of a cir-
cle and the volume of a sphere. See the standard units data file for
more details. Wire gauges with multiple zeroes are signified using
negative numbers where two zeroes is '-1'. Alternatively, you can use
the synonyms 'g00', 'g000', and so on that are defined in the standard
units data file.
You have: wiregauge(11)
You want: inches
* 0.090742002
/ 11.020255
You have: brwiregauge(g00)
You want: inches
* 0.348
/ 2.8735632
You have: 1 mm
You want: wiregauge
18.201919
You have: grit_P(600)
You want: grit_ansicoated
342.76923
The last example shows the conversion from P graded sand paper, which
is the European standard and may be marked ``P600'' on the back, to the
USA standard.
You can compute the area of a circle using the nonlinear unit,
'circlearea'. You can also do this using the circularinch or cir-
cleinch. The next example shows two ways to compute the area of a cir-
cle with a five inch radius and one way to compute the volume of a
sphere with a radius of one meter.
You have: circlearea(5 in)
You want: in2
* 78.539816
/ 0.012732395
You have: 10^2 circleinch
You want: in2
* 78.539816
/ 0.012732395
You have: spherevol(meter)
You want: ft3
* 147.92573
/ 0.0067601492
The inverse of a nonlinear conversion is indicated by prefixing a tilde
('~') to the nonlinear unit name:
You have: ~wiregauge(0.090742002 inches)
You want:
Definition: 11
You can give a nonlinear unit definition without an argument or paren-
theses, and press Enter at the 'You want:' prompt to get the definition
of a nonlinear unit; if the definition is not valid for all real num-
bers, the range of validity is also given. If the definition requires
specific units this information is also displayed:
You have: tempC
Definition: tempC(x) = x K + stdtemp
defined for x >= -273.15
You have: ~tempC
Definition: ~tempC(tempC) = (tempC +(-stdtemp))/K
defined for tempC >= 0 K
You have: circlearea
Definition: circlearea(r) = pi r^2
r has units m
To see the definition of the inverse use the '~' notation. In this
case the parameter in the functional definition will usually be the
name of the unit. Note that the inverse for 'tempC' shows that it
requires units of 'K' in the specification of the allowed range of val-
ues. Nonlinear unit conversions are described in more detail in Defin-
ing Nonlinear Units.
UNIT LISTS: CONVERSION TO SUMS OF UNITS
Outside of the SI, it is sometimes desirable to convert a single unit
to a sum of units--for example, feet to feet plus inches. The conver-
sion from sums of units was described in Sums and Differences of Units,
and is a simple matter of adding the units with the '+' sign:
You have: 12 ft + 3 in + 3|8 in
You want: ft
* 12.28125
/ 0.081424936
Although you can similarly write a sum of units to convert to, the
result will not be the conversion to the units in the sum, but rather
the conversion to the particular sum that you have entered:
You have: 12.28125 ft
You want: ft + in + 1|8 in
* 11.228571
/ 0.089058524
The unit expression given at the 'You want:' prompt is equivalent to
asking for conversion to multiples of '1 ft + 1 in + 1|8 in', which is
1.09375 ft, so the conversion in the previous example is equivalent to
You have: 12.28125 ft
You want: 1.09375 ft
* 11.228571
/ 0.089058524
In converting to a sum of units like miles, feet and inches, you typi-
cally want the largest integral value for the first unit, followed by
the largest integral value for the next, and the remainder converted to
the last unit. You can do this conversion easily with 'units' using a
special syntax for lists of units. You must list the desired units in
order from largest to smallest, separated by the semicolon (';') char-
acter:
You have: 12.28125 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3|8 in
The conversion always gives integer coefficients on the units in the
list, except possibly the last unit when the conversion is not exact:
You have: 12.28126 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3.00096 * 1|8 in
The order in which you list the units is important:
You have: 3 kg
You want: oz;lb
105 oz + 0.051367866 lb
You have: 3 kg
You want: lb;oz
6 lb + 9.8218858 oz
Listing ounces before pounds produces a technically correct result, but
not a very useful one. You must list the units in descending order of
size in order to get the most useful result.
Ending a unit list with the separator ';' has the same effect as
repeating the last unit on the list, so 'ft;in;1|8 in;' is equivalent
to 'ft;in;1|8 in;1|8 in'. With the example above, this gives
You have: 12.28126 ft
You want: ft;in;1|8 in;
12 ft + 3 in + 3|8 in + 0.00096 * 1|8 in
in effect separating the integer and fractional parts of the coeffi-
cient for the last unit. If you instead prefer to round the last coef-
ficient to an integer you can do this with the '--round' ('-r') option.
With the previous example, the result is
You have: 12.28126 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3|8 in (rounded down to nearest 1|8 in)
When you use the '-r' option, repeating the last unit on the list has
no effect (e.g., 'ft;in;1|8 in;1|8 in' is equivalent to 'ft;in;1|8
in'), and hence neither does ending a list with a ';'. With a single
unit and the '-r' option, a terminal ';' does have an effect: it causes
'units' to treat the single unit as a list and produce a rounded value
for the single unit. Without the extra ';', the '-r' option has no
effect on single unit conversions. This example shows the output using
the '-r' option:
You have: 12.28126 ft
You want: in
* 147.37512
/ 0.0067854058
You have: 12.28126 ft
You want: in;
147 in (rounded down to nearest in)
Each unit that appears in the list must be conformable with the first
unit on the list, and of course the listed units must also be conform-
able with the unit that you enter at the 'You have:' prompt.
You have: meter
You want: ft;kg
^
conformability error
ft = 0.3048 m
kg = 1 kg
You have: meter
You want: lb;oz
conformability error
1 m
0.45359237 kg
In the first case, 'units' reports the disagreement between units
appearing on the list. In the second case, 'units' reports disagree-
ment between the unit you entered and the desired conversion. This
conformability error is based on the first unit on the unit list.
Other common candidates for conversion to sums of units are angles and
time:
You have: 23.437754 deg
You want; deg;arcmin;arcsec
23 deg + 26 arcmin + 15.9144 arcsec
You have: 7.2319 hr
You want: hr;min;sec
7 hr + 13 min + 54.84 sec
In North America, recipes for cooking typically measure ingredients by
volume, and use units that are not always convenient multiples of each
other. Suppose that you have a recipe for 6 and you wish to make a
portion for 1. If the recipe calls for 2 1/2 cups of an ingredient,
you might wish to know the measurements in terms of measuring devices
you have available, you could use 'units' and enter
You have: (2+1|2) cup / 6
You want: cup;1|2 cup;1|3 cup;1|4 cup;tbsp;tsp;1|2 tsp;1|4 tsp
1|3 cup + 1 tbsp + 1 tsp
By default, if a unit in a list begins with fraction of the form 1|x
and its multiplier is an integer, the fraction is given as the product
of the multiplier and the numerator; for example,
You have: 12.28125 ft
You want: ft;in;1|8 in;
12 ft + 3 in + 3|8 in
In many cases, such as the example above, this is what is wanted, but
sometimes it is not. For example, a cooking recipe for 6 might call
for 5 1/4 cup of an ingredient, but you want a portion for 2, and your
1-cup measure is not available; you might try
You have: (5+1|4) cup / 3
You want: 1|2 cup;1|3 cup;1|4 cup
3|2 cup + 1|4 cup
This result might be fine for a baker who has a 1 1/2-cup measure (and
recognizes the equivalence), but it may not be as useful to someone
with more limited set of measures, who does want to do additional cal-
culations, and only wants to know ``How many 1/2-cup measures to I need
to add?'' After all, that's what was actually asked. With the
'--show-factor' option, the factor will not be combined with a unity
numerator, so that you get
You have: (5+1|4) cup / 3
You want: 1|2 cup;1|3 cup;1|4 cup
3 * 1|2 cup + 1|4 cup
A user-specified fractional unit with a numerator other than 1 is never
overridden, however--if a unit list specifies '3|4 cup;1|2 cup', a
result equivalent to 1 1/2 cups will always be shown as '2 * 3|4 cup'
whether or not the '--show-factor' option is given.
Some applications for unit lists may be less obvious. Suppose that you
have a postal scale and wish to ensure that it's accurate at 1 oz, but
have only metric calibration weights. You might try
You have: 1 oz
You want: 100 g;50 g; 20 g;10 g;5 g;2 g;1 g;
20 g + 5 g + 2 g + 1 g + 0.34952312 * 1 g
You might then place one each of the 20 g, 5 g, 2 g, and 1 g weights on
the scale and hope that it indicates close to
You have: 20 g + 5 g + 2 g + 1 g
You want: oz;
0.98767093 oz
Appending ';' to 'oz' forces a one-line display that includes the unit;
here the integer part of the result is zero, so it is not displayed.
A unit list such as
cup;1|2 cup;1|3 cup;1|4 cup;tbsp;tsp;1|2 tsp;1|4 tsp
can be tedious to enter. The 'units' program provides shorthand names
for some common combinations:
hms hours, minutes, seconds
dms angle: degrees, minutes, seconds
time years, days, hours, minutes and seconds
usvol US cooking volume: cups and smaller
Using these shorthands, or unit list aliases, you can do the following
conversions:
You have: anomalisticyear
You want: time
1 year + 25 min + 3.4653216 sec
You have: 1|6 cup
You want: usvol
2 tbsp + 2 tsp
You cannot combine a unit list alias with other units: it must appear
alone at the 'You want:' prompt.
You can display the definition of a unit list alias by entering it at
the 'You have:' prompt:
You have: dms
Definition: unit list, deg;arcmin;arcsec
When you specify compact output with '--compact', '--terse' or '-t' and
perform conversion to a unit list, 'units' lists the conversion factors
for each unit in the list, separated by semicolons.
You have: year
You want: day;min;sec
365;348;45.974678
Unlike the case of regular output, zeros are included in this output
list:
You have: liter
You want: cup;1|2 cup;1|4 cup;tbsp
4;0;0;3.6280454
LOGGING CALCULATIONS
The '--log' option allows you to save the results of calculations in a
file; this can be useful if you need a permanent record of your work.
For example, the fluid-flow conversion in Complicated Unit Expressions,
is lengthy, and if you were to use it in designing a piping system, you
might want a record of it for the project file. If the interactive
session
# Conversion factor A1 for pressure drop
# dP = A1 rho f L Q^2/d^5
You have: (8/pi^2) (lbm/ft^3)ft(ft^3/s)^2(1/in^5) # Input units
You want: psi
* 43.533969
/ 0.022970568
were logged, the log file would contain
### Log started Fri Oct 02 15:55:35 2015
# Conversion factor A1 for pressure drop
# dP = A1 rho f L Q^2/d^5
From: (8/pi^2) (lbm/ft^3)ft(ft^3/s)^2(1/in^5) # Input units
To: psi
* 43.533969
/ 0.022970568
The time is written to the log file when the file is opened.
The use of comments can help clarify the meaning of calculations for
the log. The log includes conformability errors between the units at
the 'You have:' and 'You want:' prompts, but not other errors, includ-
ing lack of conformability of items in sums or differences or among
items in a unit list. For example, a conversion between zenith angle
and elevation angle could involve
You have: 90 deg - (5 deg + 22 min + 9 sec)
^
Illegal sum or difference of non-conformable units
You have: 90 deg - (5 deg + 22 arcmin + 9 arcsec)
You want: dms
84 deg + 37 arcmin + 51 arcsec
You have: _
You want: deg
* 84.630833
/ 0.011816024
You have:
The log file would contain
From: 90 deg - (5 deg + 22 arcmin + 9 arcsec)
To: deg;arcmin;arcsec
84 deg + 37 arcmin + 51 arcsec
From: _
To: deg
* 84.630833
/ 0.011816024
The initial entry error (forgetting that minutes have dimension of
time, and that arcminutes must be used for dimensions of angle) does
not appear in the output. When converting to a unit list alias,
'units' expands the alias in the log file.
The 'From:' and 'To:' tags are written to the log file even if the
'--quiet' option is given. If the log file exists when 'units' is
invoked, the new results are appended to the log file. The time is
written to the log file each time the file is opened. The '--log'
option is ignored when 'units' is used non-interactively.
INVOKING UNITS
You invoke 'units' like this:
units [options] [from-unit [to-unit]]
If the from-unit and to-unit are omitted, the program will use interac-
tive prompts to determine which conversions to perform. See Interac-
tive Use. If both from-unit and to-unit are given, 'units' will print
the result of that single conversion and then exit. If only from-unit
appears on the command line, 'units' will display the definition of
that unit and exit. Units specified on the command line may need to be
quoted to protect them from shell interpretation and to group them into
two arguments. See Command Line Use.
The default behavior of 'units' can be changed by various options given
on the command line. In most cases, the options may be given in either
short form (a single '-' followed by a single character) or long form
('--' followed by a word or hyphen-separated words). Short-form
options are cryptic but require less typing; long-form options require
more typing but are more explanatory and may be more mnemonic. With
long-form options you need only enter sufficient characters to uniquely
identify the option to the program. For example, '--out %f' works, but
'--o %f' fails because 'units' has other long options beginning with
'o'. However, '--q' works because '--quiet' is the only long option
beginning with 'q'.
Some options require arguments to specify a value (e.g., '-d 12' or
'--digits 12'). Short-form options that do not take arguments may be
concatenated (e.g., '-erS' is equivalent to '-e -r -S'); the last
option in such a list may be one that takes an argument (e.g.,
'-ed 12'). With short-form options, the space between an option and
its argument is optional (e.g., '-d12' is equivalent to '-d 12').
Long-form options may not be concatenated, and the space between a
long-form option and its argument is required. Short-form and long-
form options may be intermixed on the command line. Options may be
given in any order, but when incompatible options (e.g., '--output-
format' and '--exponential') are given in combination, behavior is con-
trolled by the last option given. For example, '-o%.12f -e' gives
exponential format with the default eight significant digits).
The following options are available:
-c, --check
Check that all units and prefixes defined in the units data file
reduce to primitive units. Print a list of all units that can-
not be reduced. Also display some other diagnostics about sus-
picious definitions in the units data file. Only definitions
active in the current locale are checked. You should always run
'units' with this option after modifying a units data file.
--check-verbose, --verbose-check
Like the '--check' option, this option prints a list of units
that cannot be reduced. But to help find unit definitions that
cause endless loops, it lists the units as they are checked. If
'units' hangs, then the last unit to be printed has a bad defi-
nition. Only definitions active in the current locale are
checked.
-d ndigits, --digits ndigits
Set the number of significant digits in the output to the value
specified (which must be greater than zero). For example,
'-d 12' sets the number of significant digits to 12. With expo-
nential output 'units' displays one digit to the left of the
decimal point and eleven digits to the right of the decimal
point. On most systems, the maximum number of internally
meaningful digits is 15; if you specify a greater number than
your system's maximum, 'units' will print a warning and set the
number to the largest meaningful value. To directly set the
maximum value, give an argument of 'max' (e.g., '-d max'). Be
aware, of course, that ``significant'' here refers only to the
display of numbers; if results depend on physical constants not
known to this precision, the physically meaningful precision may
be less than that shown. The '--digits' option conflicts with
the '--output-format' option.
-e, --exponential
Set the numeric output format to exponential (i.e., scientific
notation), like that used in the Unix 'units' program. The
default precision is eight significant digits (seven digits to
the right of the decimal point); this can be changed with the
'--digits' option. The '--exponential' option conflicts with
the '--output-format' option.
-o format, --output-format format
This option affords complete control over the numeric output
format using the specified format. The format is a single float-
ing point numeric format for the 'printf()' function in the C
programming language. All compilers support the format types
'g' and 'G' to specify significant digits, 'e' and 'E' for sci-
entific notation, and 'f' for fixed-point decimal. The ISO C99
standard introduced the 'F' type for fixed-point decimal and the
'a' and 'A' types for hexadecimal floating point; these types
are allowed with compilers that support them. The default for-
mat is '%.8g'; for greater precision, you could specify
'-o %.15g'. See Numeric Output Format and the documentation for
'printf()' for more detailed descriptions of the format specifi-
cation. The '--output-format' option affords the greatest con-
trol of the output appearance, but requires at least rudimentary
knowledge of the 'printf()' format syntax. If you don't want to
bother with the 'printf()' syntax, you can specify greater pre-
cision more simply with the '--digits' option or select exponen-
tial format with '--exponential'. The '--output-format' option
is incompatible with the '--exponential' and '--digits' options.
-f filename, --file filename
Instruct 'units' to load the units file filename. You can spec-
ify up to 25 units files on the command line. When you use this
option, 'units' will load only the files you list on the command
line; it will not load the standard file or your personal units
file unless you explicitly list them. If filename is the empty
string ('-f ""'), the default units file (or that specified by
'UNITSFILE') will be loaded in addition to any others specified
with '-f'.
-L logfile, --log logfile
Save the results of calculations in the file logfile; this can
be useful if it is important to have a record of unit conver-
sions or other calculations that are to be used extensively or
in a critical activity such as a program or design project. If
logfile exits, the new results are appended to the file. This
option is ignored when 'units' is used non-interactively. See
Logging Calculations for a more detailed description and some
examples.
-H filename, --history filename
Instruct 'units' to save history to filename, so that a record
of your commands is available for retrieval across different
'units' invocations. To prevent the history from being saved
set filename to the emptry string ('-f ""'). This option has no
effect if readline is not available.
-h, --help
Print out a summary of the options for 'units'.
-m, --minus
Causes '-' to be interpreted as a subtraction operator. This is
the default behavior.
-p, --product
Causes '-' to be interpreted as a multiplication operator when
it has two operands. It will act as a negation operator when it
has only one operand: '(-3)'. By default '-' is treated as a
subtraction operator.
--oldstar
Causes '*' to have the old-style precedence, higher than the
precedence of division so that '1/2*3' will equal '1/6'.
--newstar
Forces '*' to have the new (default) precedence that follows the
usual rules of algebra: the precedence of '*' is the same as the
precedence of '/', so that '1/2*3' will equal '3/2'.
--compact
Give compact output featuring only the conversion factor. This
turns off the '--verbose' option.
-q, --quiet, --silent
Suppress prompting of the user for units and the display of sta-
tistics about the number of units loaded.
-n, --nolists
Disable conversion to unit lists.
-r, --round
When converting to a combination of units given by a unit list,
round the value of the last unit in the list to the nearest
integer.
-S, --show-factor
When converting to a combination of units specified in a list,
always show a non-unity factor before a unit that begins with a
fraction with a unity denominator. By default, if the unit in a
list begins with fraction of the form 1|x and its multiplier is
an integer other than 1, the fraction is given as the product of
the multiplier and the numerator (e.g., '3|8 in' rather than '3
* 1|8 in'). In some cases, this is not what is wanted; for
example, the results for a cooking recipe might show '3 *
1|2 cup' as '3|2 cup'. With the '--show-factor' option, a
result equivalent to 1.5 cups will display as '3 * 1|2 cup'
rather than '3|2 cup'. A user-specified fractional unit with a
numerator other than 1 is never overridden, however--if a unit
list specifies '3|4 cup;1|2 cup', a result equivalent to 1 1/2
cups will always be shown as '2 * 3|4 cup' whether or not the
'--show-factor' option is given.
-s, --strict
Suppress conversion of units to their reciprocal units. For
example, 'units' will normally convert hertz to seconds because
these units are reciprocals of each other. The strict option
requires that units be strictly conformable to perform a conver-
sion, and will give an error if you attempt to convert hertz to
seconds.
-1, --one-line
Give only one line of output (the forward conversion). Do not
print the reverse conversion. If a reciprocal conversion is
performed then 'units' will still print the ``reciprocal conver-
sion'' line.
-t, --terse
Give terse output when converting units. This option can be
used when calling 'units' from another program so that the
output is easy to parse. This option has the combined effect of
these options: '--strict' '--quiet' '--one-line' '--compact'.
When combined with '--version' it produces a display showing
only the program name and version number.
-v, --verbose
Give slightly more verbose output when converting units. When
combined with the '-c' option this gives the same effect as
'--check-verbose'. When combined with '--version' produces a
more detailed output, equivalent to the '--info' option.
-V, --version
Print the program version number, tell whether the 'readline'
library has been included, tell whether UTF-8 support has been
included; give the locale, the location of the default units
data file, and the location of the personal units data file;
indicate if the personal units data file does not exist.
When given in combination with the '--terse' option, the program prints
only the version number and exits.
When given in combination with the '--verbose' option, the program, the
'--version' option has the same effect as the '--info' option below.
-I, --info
Print the information given with the '--version' option, show
the pathname of the units program, show the status of the
'UNITSFILE' and 'MYUNITSFILE' environment variables, and addi-
tional information about how 'units' locates the related files.
On systems running Microsoft Windows, the status of the
'UNITSLOCALE' environment variable and information about the
related locale map are also given. This option is usually of
interest only to developers and administrators, but it can some-
times be useful for troubleshooting.
Combining the '--version' and '--verbose' options has the same effect
as giving '--info'.
-U, --unitsfile
Print the location of the default units data file and exit; if
the file cannot be found, print ``Units data file not found''.
-l locale, --locale locale
Print the information given with the '--version' option, show
the Force a specified locale such as 'en_GB' to get British def-
initions by default. This overrides the locale determined from
system settings or environment variables. See Locale for a
description of locale format.
ADDING YOUR OWN DEFINITIONS
Units Data Files
The units and prefixes that 'units' can convert are defined in the
units data file, typically '/usr/share/units/definitions.units'. If
you can't find this file, run 'units --version' to get information on
the file locations for your installation. Although you can extend or
modify this data file if you have appropriate user privileges, it's
usually better to put extensions in separate files so that the defini-
tions will be preserved if you update 'units'.
You can include additional data files in the units database using the
'!include' command in the standard units data file. For example
!include /usr/local/share/units/local.units
might be appropriate for a site-wide supplemental data file. The loca-
tion of the '!include' statement in the standard units data file is
important; later definitions replace earlier ones, so any definitions
in an included file will override definitions before the '!include'
statement in the standard units data file. With normal invocation, no
warning is given about redefinitions; to ensure that you don't have an
unintended redefinition, run 'units -c' after making changes to any
units data file.
If you want to add your own units in addition to or in place of stan-
dard or site-wide supplemental units data files, you can include them
in the '.units' file in your home directory. If this file exists it is
read after the standard units data file, so that any definitions in
this file will replace definitions of the same units in the standard
data file or in files included from the standard data file. This file
will not be read if any units files are specified on the command line.
(Under Windows the personal units file is named 'unitdef.units'.) Run-
ning 'units -V' will display the location and name of your personal
units file.
The 'units' program first tries to determine your home directory from
the 'HOME' environment variable. On systems running Microsoft Windows,
if 'HOME' does not exist, 'units' attempts to find your home directory
from 'HOMEDRIVE', 'HOMEPATH' and 'USERPROFILE'. You can specify an
arbitrary file as your personal units data file with the 'MYUNITSFILE'
environment variable; if this variable exists, its value is used with-
out searching your home directory. The default units data files are
described in more detail in Data Files.
Defining New Units and Prefixes
A unit is specified on a single line by giving its name and an equiva-
lence. Comments start with a '#' character, which can appear anywhere
in a line. The backslash character ('\') acts as a continuation char-
acter if it appears as the last character on a line, making it possible
to spread definitions out over several lines if desired. A file can be
included by giving the command '!include' followed by the file's name.
The '!' must be the first character on the line. The file will be
sought in the same directory as the parent file unless you give a full
path. The name of the file to be included cannot contain the comment
character '#'.
Unit names must not contain any of the operator characters '+', '-',
'*', '/', '|', '^', ';', '~', the comment character '#', or parenthe-
ses. They cannot begin or end with an underscore ('_'), a comma (',')
or a decimal point ('.'). The figure dash (U+2012), typographical
minus (`-'; U+2212), and en dash (`-'; U+2013) are converted to the
operator '-', so none of these characters can appear in unit names.
Names cannot begin with a digit, and if a name ends in a digit other
than zero, the digit must be preceded by a string beginning with an
underscore, and afterwards consisting only of digits, decimal points,
or commas. For example, 'foo_2', 'foo_2,1', or 'foo_3.14' are valid
names but 'foo2' or 'foo_a2' are invalid. You could define nitrous
oxide as
N2O nitrogen 2 + oxygen
but would need to define nitrogen dioxide as
NO_2 nitrogen + oxygen 2
Be careful to define new units in terms of old ones so that a reduction
leads to the primitive units, which are marked with '!' characters.
Dimensionless units are indicated by using the string '!dimensionless'
for the unit definition.
When adding new units, be sure to use the '-c' option to check that the
new units reduce properly. If you create a loop in the units defini-
tions, then 'units' will hang when invoked with the '-c' option. You
will need to use the '--check-verbose' option, which prints out each
unit as it is checked. The program will still hang, but the last unit
printed will be the unit that caused the infinite loop.
If you define any units that contain '+' characters, carefully check
them because the '-c' option will not catch non-conformable sums. Be
careful with the '-' operator as well. When used as a binary operator,
the '-' character can perform addition or multiplication depending on
the options used to invoke 'units'. To ensure consistent behavior use
'-' only as a unary negation operator when writing units definitions.
To multiply two units leave a space or use the '*' operator with care,
recalling that it has two possible precedence values and may require
parentheses to ensure consistent behavior. To compute the difference
of 'foo' and 'bar' write 'foo+(-bar)' or even 'foo+-bar'.
Here is an example of a short data file that defines some basic units:
m ! # The meter is a primitive unit
sec ! # The second is a primitive unit
rad !dimensionless # A dimensionless primitive unit
micro- 1e-6 # Define a prefix
minute 60 sec # A minute is 60 seconds
hour 60 min # An hour is 60 minutes
inch 0.0254 m # Inch defined in terms of meters
ft 12 inches # The foot defined in terms of inches
mile 5280 ft # And the mile
A unit that ends with a '-' character is a prefix. If a prefix defini-
tion contains any '/' characters, be sure they are protected by paren-
theses. If you define 'half- 1/2' then 'halfmeter' would be equivalent
to '1 / (2 meter)'.
Defining Nonlinear Units
Some unit conversions of interest are nonlinear; for example, tempera-
ture conversions between the Fahrenheit and Celsius scales cannot be
done by simply multiplying by conversion factors.
When you give a linear unit definition such as 'inch 2.54 cm' you are
providing information that 'units' uses to convert values in inches
into primitive units of meters. For nonlinear units, you give a func-
tional definition that provides the same information.
Nonlinear units are represented using a functional notation. It is
best to regard this notation not as a function call but as a way of
adding units to a number, much the same way that writing a linear unit
name after a number adds units to that number. Internally, nonlinear
units are defined by a pair of functions that convert to and from lin-
ear units in the database, so that an eventual conversion to primitive
units is possible.
Here is an example nonlinear unit definition:
tempF(x) units=[1;K] domain=[-459.67,) range=[0,) \
(x+(-32)) degF + stdtemp ; (tempF+(-stdtemp))/degF + 32
A nonlinear unit definition comprises a unit name, a formal parameter
name, two functions, and optional specifications for units, the domain,
and the range (the domain of the inverse function). The functions tell
'units' how to convert to and from the new unit. To produce valid
results, the arguments of these functions need to have the correct
dimensions and be within the domains for which the functions are
defined.
The definition begins with the unit name followed immediately (with no
spaces) by a '(' character. In the parentheses is the name of the for-
mal parameter. Next is an optional specification of the units required
by the functions in the definition. In the example above, the
'units=[1;K]' specification indicates that the 'tempF' function
requires an input argument conformable with '1' (i.e., the argument is
dimensionless), and that the inverse function requires an input argu-
ment conformable with 'K'. For normal nonlinear units definition, the
forward function will always take a dimensionless argument; in general,
the inverse function will need units that match the quantity measured
by your nonlinear unit. Specifying the units enables 'units' to per-
form error checking on function arguments, and also to assign units to
domain and range specifications, which are described later.
Next the function definitions appear. In the example above, the
'tempF' function is defined by
tempF(x) = (x+(-32)) degF + stdtemp
This gives a rule for converting 'x' in the units 'tempF' to linear
units of absolute temperature, which makes it possible to convert from
tempF to other units.
To enable conversions to Fahrenheit, you must give a rule for the
inverse conversions. The inverse will be 'x(tempF)' and its definition
appears after a ';' character. In our example, the inverse is
x(tempF) = (tempF+(-stdtemp))/degF + 32
This inverse definition takes an absolute temperature as its argument
and converts it to the Fahrenheit temperature. The inverse can be
omitted by leaving out the ';' character and the inverse definition,
but then conversions to the unit will not be possible. If the inverse
definition is omitted, the '--check' option will display a warning. It
is up to you to calculate and enter the correct inverse function to
obtain proper conversions; the '--check' option tests the inverse at
one point and prints an error if it is not valid there, but this is not
a guarantee that your inverse is correct.
With some definitions, the units may vary. For example, the definition
square(x) x^2
can have any arbitrary units, and can also take dimensionless argu-
ments. In such a case, you should not specify units. If a definition
takes a root of its arguments, the definition is valid only for units
that yield such a root. For example,
squirt(x) sqrt(x)
is valid for a dimensionless argument, and for arguments with even pow-
ers of units.
Some definitions may not be valid for all real numbers. In such cases,
'units' can handle errors better if you specify an appropriate domain
and range. You specify the domain and range as shown below:
baume(d) units=[1;g/cm^3] domain=[0,130.5] range=[1,10] \
(145/(145-d)) g/cm^3 ; (baume+-g/cm^3) 145 / baume
In this example the domain is specified after 'domain=' with the end-
points given in brackets. In accord with mathematical convention,
square brackets indicate a closed interval (one that includes its end-
points), and parentheses indicate an open interval (one that does not
include its endpoints). An interval can be open or closed on one or
both ends; an interval that is unbounded on either end is indicated by
omitting the limit on that end. For example, a quantity to which deci-
bel (dB) is applied may have any value greater than zero, so the range
is indicated by '(0,)':
decibel(x) units=[1;1] range=(0,) 10^(x/10); 10 log(decibel)
If the domain or range is given, the second endpoint must be greater
than the first.
The domain and range specifications can appear independently and in any
order along with the units specification. The values for the domain
and range endpoints are attached to the units given in the units speci-
fication, and if necessary, the parameter value is adjusted for compar-
ison with the endpoints. For example, if a definition includes
'units=[1;ft]' and 'range=[3,)', the range will be taken as 3 ft to
infinity. If the function is passed a parameter of '900 mm', that
value will be adjusted to 2.9527559 ft, which is outside the specified
range. If you omit the units specification from the previous example,
'units' can not tell whether you intend the lower endpoint to be 3 ft
or 3 microfurlongs, and can not adjust the parameter value of 900 mm
for comparison. Without units, numerical values other than zero or
plus or minus infinity for domain or range endpoints are meaningless,
and accordingly they are not allowed. If you give other values without
units then the definition will be ignored and you will get an error
message.
Although the units, domain, and range specifications are optional, it's
best to give them when they are applicable; doing so allows 'units' to
perform better error checking and give more helpful error messages.
Giving the domain and range also enables the '--check' option to find a
point in the domain to use for its point check of your inverse defini-
tion.
You can make synonyms for nonlinear units by providing both the forward
and inverse functions; inverse functions can be obtained using the '~'
operator. So to create a synonym for 'tempF' you could write
fahrenheit(x) units=[1;K] tempF(x); ~tempF(fahrenheit)
This is useful for creating a nonlinear unit definition that differs
slightly from an existing definition without having to repeat the orig-
inal functions. For example,
dBW(x) units=[1;W] range=[0,) dB(x) W ; ~dB(dBW/W)
If you wish a synonym to refer to an existing nonlinear unit without
modification, you can do so more simply by adding the synonym with
appended parentheses as a new unit, with the existing nonlinear unit--
without parentheses--as the definition. So to create a synonym for
'tempF' you could write
fahrenheit() tempF
The definition must be a nonlinear unit; for example, the synonym
fahrenheit() meter
will result in an error message when 'units' starts.
You may occasionally wish to define a function that operates on units.
This can be done using a nonlinear unit definition. For example, the
definition below provides conversion between radius and the area of a
circle. This definition requires a length as input and produces an
area as output, as indicated by the 'units=' specification. Specifying
the range as the nonnegative numbers can prevent cryptic error mes-
sages.
circlearea(r) units=[m;m^2] range=[0,) pi r^2 ; sqrt(circlearea/pi)
Defining Piecewise Linear Units
Sometimes you may be interested in a piecewise linear unit such as many
wire gauges. Piecewise linear units can be defined by specifying con-
versions to linear units on a list of points. Conversion at other
points will be done by linear interpolation. A partial definition of
zinc gauge is
zincgauge[in] 1 0.002, 10 0.02, 15 0.04, 19 0.06, 23 0.1
In this example, 'zincgauge' is the name of the piecewise linear unit.
The definition of such a unit is indicated by the embedded '[' charac-
ter. After the bracket, you should indicate the units to be attached
to the numbers in the table. No spaces can appear before the ']' char-
acter, so a definition like 'foo[kg meters]' is invalid; instead write
'foo[kg*meters]'. The definition of the unit consists of a list of
pairs optionally separated by commas. This list defines a function for
converting from the piecewise linear unit to linear units. The first
item in each pair is the function argument; the second item is the
value of the function at that argument (in the units specified in
brackets). In this example, we define 'zincgauge' at five points. For
example, we set 'zincgauge(1)' equal to '0.002 in'. Definitions like
this may be more readable if written using continuation characters
as
zincgauge[in] \
1 0.002 \
10 0.02 \
15 0.04 \
19 0.06 \
23 0.1
With the preceding definition, the following conversion can be per-
formed:
You have: zincgauge(10)
You want: in
* 0.02
/ 50
You have: .01 inch
You want: zincgauge
5
If you define a piecewise linear unit that is not strictly monotonic,
then the inverse will not be well defined. If the inverse is requested
for such a unit, 'units' will return the smallest inverse.
After adding nonlinear units definitions, you should normally run
'units --check' to check for errors. If the 'units' keyword is not
given, the '--check' option checks a nonlinear unit definition using a
dimensionless argument, and then checks using an arbitrary combination
of units, as well as the square and cube of that combination; a warning
is given if any of these tests fail. For example,
Warning: function 'squirt(x)' defined as 'sqrt(x)'
failed for some test inputs:
squirt(7(kg K)^1): Unit not a root
squirt(7(kg K)^3): Unit not a root
Running 'units --check' will print a warning if a non-monotonic piece-
wise linear unit is encountered. For example, the relationship between
ANSI coated abrasive designation and mean particle size is non-mono-
tonic in the vicinity of 800 grit:
ansicoated[micron] \
. . .
600 10.55 \
800 11.5 \
1000 9.5 \
Running 'units --check' would give the error message
Table 'ansicoated' lacks unique inverse around entry 800
Although the inverse is not well defined in this region, it's not
really an error. Viewing such error messages can be tedious, and if
there are enough of them, they can distract from true errors. Error
checking for nonlinear unit definitions can be suppressed by giving the
'noerror' keyword; for the examples above, this could be done as
squirt(x) noerror domain=[0,) range=[0,) sqrt(x); squirt^2
ansicoated[micron] noerror \
. . .
Use the 'noerror' keyword with caution. The safest approach after
adding a nonlinear unit definition is to run 'units --check' and con-
firm that there are no actual errors before adding the 'noerror' key-
word.
Defining Unit List Aliases
Unit list aliases are treated differently from unit definitions,
because they are a data entry shorthand rather than a true definition
for a new unit. A unit list alias definition begins with '!unitlist'
and includes the alias and the definition; for example, the aliases
included in the standard units data file are
!unitlist hms hr;min;sec
!unitlist time year;day;hr;min;sec
!unitlist dms deg;arcmin;arcsec
!unitlist ftin ft;in;1|8 in
!unitlist usvol cup;3|4 cup;2|3 cup;1|2 cup;1|3 cup;1|4 cup;\
tbsp;tsp;1|2 tsp;1|4 tsp;1|8 tsp
Unit list aliases are only for unit lists, so the definition must
include a ';'. Unit list aliases can never be combined with units or
other unit list aliases, so the definition of 'time' shown above could
not have been shortened to 'year;day;hms'.
As usual, be sure to run 'units --check' to ensure that the units
listed in unit list aliases are conformable.
NUMERIC OUTPUT FORMAT
By default, 'units' shows results to eight significant digits. You can
change this with the '--exponential', '--digits', and '--output-format'
options. The first sets an exponential format (i.e., scientific nota-
tion) like that used in the original Unix 'units' program, the second
allows you to specify a different number of significant digits, and the
last allows you to control the output appearance using the format for
the 'printf()' function in the C programming language. If you only
want to change the number of significant digits or specify exponential
format type, use the '--digits' and '--exponential' options. The
'--output-format' option affords the greatest control of the output
appearance, but requires at least rudimentary knowledge of the
'printf()' format syntax. See Invoking Units for descriptions of these
options.
Format Specification
The format specification recognized with the '--output-format' option
is a subset of that for 'printf()'. The format specification has the
form '%'[flags][width]['.'precision]type; it must begin with '%', and
must end with a floating-point type specifier: 'g' or 'G' to specify
the number of significant digits, 'e' or 'E' for scientific notation,
and 'f' for fixed-point decimal. The ISO C99 standard added the 'F'
type for fixed-point decimal and the 'a' and 'A' types for hexadecimal
floating point; these types are allowed with compilers that support
them. Type length modifiers (e.g., 'L' to indicate a long double) are
inapplicable and are not allowed.
The default format for 'units' is '%.8g'; for greater precision, you
could specify '-o %.15g'. The 'g' and 'G' format types use exponential
format whenever the exponent would be less than -4, so the value
0.000013 displays as '1.3e-005'. These types also use exponential
notation when the exponent is greater than or equal to the precision,
so with the default format, the value 5e7 displays as '50000000' and
the value 5e8 displays as '5e+008'. If you prefer fixed-point display,
you might specify '-o %.8f'; however, small numbers will display very
few significant digits, and values less than 0.5e-8 will show nothing
but zeros.
The format specification may include one or more optional flags: '+',
' ' (space), '#', '-', or '0' (the digit zero). The digit-grouping
flag ''' is allowed with compilers that support it. Flags are followed
by an optional value for the minimum field width, and an optional pre-
cision specification that begins with a period (e.g., '.6'). The field
width includes the digits, decimal point, the exponent, thousands sepa-
rators (with the digit-grouping flag), and the sign if any of these are
shown.
Flags
The '+' flag causes the output to have a sign ('+' or '-'). The space
flag ' ' is similar to the '+' flag, except that when the value is pos-
itive, it is prefixed with a space rather than a plus sign; this flag
is ignored if the '+' flag is also given. The '+' or ' ' flag could be
useful if conversions might include positive and negative results, and
you wanted to align the decimal points in exponential notation. The
'#' flag causes the output value to contain a decimal point in all
cases; by default, the output contains a decimal point only if there
are digits (which can be trailing zeros) to the right of the point.
With the 'g' or 'G' types, the '#' flag also prevents the suppression
of trailing zeros. The digit-grouping flag ''' shows a thousands sepa-
rator in digits to the left of the decimal point. This can be useful
when displaying large numbers in fixed-point decimal; for example, with
the format '%f',
You have: mile
You want: microfurlong
* 8000000.000000
/ 0.000000
the magnitude of the first result may not be immediately obvious with-
out counting the digits to the left of the decimal point. If the thou-
sands separator is the comma (','), the output with the format '%'f'
might be
You have: mile
You want: microfurlong
* 8,000,000.000000
/ 0.000000
making the magnitude readily apparent. Unfortunately, few compilers
support the digit-grouping flag.
With the '-' flag, the output value is left aligned within the speci-
fied field width. If a field width greater than needed to show the
output value is specified, the '0' (zero) flag causes the output value
to be left padded with zeros until the specified field width is
reached; for example, with the format '%011.6f',
You have: troypound
You want: grain
* 5760.000000
/ 0000.000174
The '0' flag has no effect if the '-' (left align) flag is given.
Field Width
By default, the output value is left aligned and shown with the minimum
width necessary for the specified (or default) precision. If a field
width greater than this is specified, the value shown is right aligned,
and padded on the left with enough spaces to provide the specified
field width. A width specification is typically used with fixed-point
decimal to have columns of numbers align at the decimal point; this
arguably is less useful with 'units' than with long columnar output,
but it may nonetheless assist in quickly assessing the relative magni-
tudes of results. For example, with the format '%12.6f',
You have: km
You want: in
* 39370.078740
/ 0.000025
You have: km
You want: rod
* 198.838782
/ 0.005029
You have: km
You want: furlong
* 4.970970
/ 0.201168
Precision
The meaning of ``precision'' depends on the format type. With 'g' or
'G', it specifies the number of significant digits (like the '--digits'
option); with 'e', 'E', 'f', or 'F', it specifies the maximum number of
digits to be shown after the decimal point.
With the 'g' and 'G' format types, trailing zeros are suppressed, so
the results may sometimes have fewer digits than the specified preci-
sion (as indicated above, the '#' flag causes trailing zeros to be dis-
played).
The default precision is 6, so '%g' is equivalent to '%.6g', and would
show the output to six significant digits. Similarly, '%e' or '%f'
would show the output with six digits after the decimal point.
The C 'printf()' function allows a precision of arbitrary size, whether
or not all of the digits are meaningful. With most compilers, the max-
imum internal precision with 'units' is 15 decimal digits (or 13 hexa-
decimal digits). With the '--digits' option, you are limited to the
maximum internal precision; with the '--output-format' option, you may
specify a precision greater than this, but it may not be meaningful.
In some cases, specifying excess precision can result in rounding arti-
facts. For example, a pound is exactly 7000 grains, but with the for-
mat '%.18g', the output might be
You have: pound
You want: grain
* 6999.9999999999991
/ 0.00014285714285714287
With the format '%.25g' you might get the following:
You have: 1/3
You want:
Definition: 0.333333333333333314829616256247
In this case the displayed value includes a series of digits that rep-
resent the underlying binary floating-point approximation to 1/3 but
are not meaningful for the desired computation. In general, the result
with excess precision is system dependent. The precision affects only
the display of numbers; if a result relies on physical constants that
are not known to the specified precision, the number of physically
meaningful digits may be less than the number of digits shown.
See the documentation for 'printf()' for more detailed descriptions of
the format specification.
The '--output-format' option is incompatible with the '--exponential'
or '--digits' options; if the former is given in combination with
either of the latter, the format is controlled by the last option
given.
LOCALIZATION
Some units have different values in different locations. The localiza-
tion feature accommodates this by allowing a units data file to specify
definitions that depend on the user's locale.
Locale
A locale is a subset of a user's environment that indicates the user's
language and country, and some attendant preferences, such as the for-
matting of dates. The 'units' program attempts to determine the locale
from the POSIX setlocale function; if this cannot be done, 'units'
examines the environment variables 'LC_CTYPE' and 'LANG'. On POSIX
systems, a locale is of the form language'_'country, where language is
the two-character code from ISO 639-1 and country is the two-character
code from ISO 3166-1; language is lower case and country is upper case.
For example, the POSIX locale for the United Kingdom is 'en_GB'.
On systems running Microsoft Windows, the value returned by setlocale()
is different from that on POSIX systems; 'units' attempts to map the
Windows value to a POSIX value by means of a table in the file
'locale_map.txt' in the same directory as the other data files. The
file includes entries for many combinations of language and country,
and can be extended to include other combinations. The
'locale_map.txt' file comprises two tab-separated columns; each entry
is of the form
Windows-locale POSIX-locale
where POSIX-locale is as described above, and Windows-locale typically
spells out both the language and country. For example, the entry for
the United States is
English_United States en_US
You can force 'units' to run in a desired locale by using the '-l'
option.
In order to create unit definitions for a particular locale you begin a
block of definitions in a unit datafile with '!locale' followed by a
locale name. The '!' must be the first character on the line. The
'units' program reads the following definitions only if the current
locale matches. You end the block of localized units with
'!endlocale'. Here is an example, which defines the British gallon.
!locale en_GB
gallon 4.54609 liter
!endlocale
Additional Localization
Sometimes the locale isn't sufficient to determine unit preferences.
There could be regional preferences, or a company could have specific
preferences. Though probably uncommon, such differences could arise
with the choice of English customary units outside of English-speaking
countries. To address this, 'units' allows specifying definitions that
depend on environment variable settings. The environment variables can
be controled based on the current locale, or the user can set them to
force a particular group of definitions.
A conditional block of definitions in a units data file begins with
either '!var' or '!varnot' following by an environment variable name
and then a space separated list of values. The leading '!' must
appear in the first column of a units data file, and the conditional
block is terminated by '!endvar'. Definitions in blocks beginning with
'!var' are executed only if the environment variable is exactly equal
to one of the listed values. Definitions in blocks beginning with
'!varnot' are executed only if the environment variable does not equal
any of the list values.
The inch has long been a customary measure of length in many places.
The word comes from the latin uncia meaning ``one twelfth,'' referring
to its relationship with the foot. By the 20th century, the inch was
officially defined in English-speaking countries relative to the yard,
but until 1959, the yard differed slightly among those countries. In
France the customary inch, which was displaced in 1799 by the meter,
had a different length based on a french foot. These customary defini-
tions could be accommodated as follows:
!var INCH_UNIT usa
yard 3600|3937 m
!endvar
!var INCH_UNIT canada
yard 0.9144 meter
!endvar
!var INCH_UNIT uk
yard 0.91439841 meter
!endvar
!var INCH_UNIT canada uk usa
foot 1|3 yard
inch 1|12 foot
!endvar
!var INCH_UNIT france
foot 144|443.296 m
inch 1|12 foot
line 1|12 inch
!endvar
!varnot INCH_UNIT usa uk france canada
!message Unknown value for INCH_UNIT
!endvar
When 'units' reads the above definitions it will check the environment
variable 'INCH_UNIT' and load only the definitions for the appropriate
section. If 'INCH_UNIT' is unset or is not set to one of the four val-
ues listed then 'units' will run the last block. In this case that
block uses the '!message' command to display a warning message. Alter-
natively that block could set default values.
In order to create default values that are overridden by user settings
the data file can use the '!set' command, which sets an environment
variable only if it is not already set; these settings are only for
the current 'units' invocation and do not persist. So if the example
above were preceded by '!set INCH_UNIT france' then this would make
'france' the default value for 'INCH_UNIT'. If the user had set the
variable in the environment before invoking 'units', then 'units' would
use the user's value.
To link these settings to the user's locale you combine the '!set' com-
mand with the '!locale' command. If you wanted to combine the above
example with suitable locales you could do by preceding the above defi-
nition with the following:
!locale en_US
!set INCH_UNIT usa
!endlocale
!locale en_GB
!set INCH_UNIT uk
!endlocale
!locale en_CA
!set INCH_UNIT canada
!endlocale
!locale fr_FR
!set INCH_UNIT france
!endlocale
!set INCH_UNIT france
These definitions set the overall default for 'INCH_UNIT' to 'france'
and set default values for four locales appropriately. The overall
default setting comes last so that it only applies when 'INCH_UNIT' was
not set by one of the other commands or by the user.
If the variable given after '!var' or '!varnot' is undefined then
'units' prints an error message and ignores the definitions that fol-
low. Use '!set' to create defaults to prevent this situation from
arising. The '-c' option only checks the definitions that are active
for the current environment and locale, so when adding new definitions
take care to check that all cases give rise to a well defined set of
definitions.
ENVIRONMENT VARIABLES
The 'units' program uses the following environment variables:
HOME Specifies the location of your home directory; it is used by
'units' to find a personal units data file '.units'. On systems
running Microsoft Windows, the file is 'unitdef.units', and if
'HOME' does not exist, 'units' tries to determine your home
directory from the 'HOMEDRIVE' and 'HOMEPATH' environment vari-
ables; if these variables do not exist, units finally tries
'USERPROFILE'--typically 'C:\Users\username' (Windows Vista and
Windows 7) or 'C:\Documents and Settings\username' (Windows XP).
LC_CTYPE, LANG
Checked to determine the locale if 'units' cannot obtain it from
the operating system. Sections of the standard units data file
are specific to certain locales.
MYUNITSFILE
Specifies your personal units data file. If this variable
exists, 'units' uses its value rather than searching your home
directory for '.units'. The personal units file will not be
loaded if any data files are given using the '-f' option.
PAGER Specifies the pager to use for help and for displaying the con-
formable units. The help function browses the units database
and calls the pager using the '+n'n syntax for specifying a line
number. The default pager is 'more'; 'PAGER' can be used to
specify alternatives such as 'less', 'pg', 'emacs', or 'vi'.
UNITS_ENGLISH
Set to either 'US' or 'GB' to choose United States or British
volume definitions, overriding the default from your locale.
UNITSFILE
Specifies the units data file to use (instead of the default).
You can only specify a single units data file using this envi-
ronment variable. If units data files are given using the '-f'
option, the file specified by 'UNITSFILE' will be not be loaded
unless the '-f' option is given with the empty string
('units -f ""').
UNITSLOCALEMAP
Windows only; this variable has no effect on Unix-like systems.
Specifies the units locale map file to use (instead of the
default). This variable seldom needs to be set, but you can use
it to ensure that the locale map file will be found if you spec-
ify a location for the units data file using either the '-f'
option or the 'UNITSFILE' environment variable, and that loca-
tion does not also contain the locale map file.
DATA FILES
The 'units' program uses two default data files: 'definitions.units'
and 'currency.units'. The program can also use an optional personal
units data file '.units' ('unitdef.units' under Windows) located in the
user's home directory. The personal units data file is described in
more detail in Units Data Files.
On Unix-like systems, the data files are typically located in
'/usr/share/units' if 'units' is provided with the operating system, or
in '/usr/local/share/units' if 'units' is compiled from the source dis-
tribution.
On systems running Microsoft Windows, the files may be in the same
locations if Unix-like commands are available, a Unix-like file struc-
ture is present (e.g., 'C:/usr/local'), and 'units' is compiled from
the source distribution. If Unix-like commands are not available, a
more common location is 'C:\Program Files (x86)\GNU\units' (for 64-bit
Windows installations) or 'C:\Program Files\GNU\units' (for 32-bit
installations).
If 'units' is obtained from the GNU Win32 Project
(http://gnuwin32.sourceforge.net/), the files are commonly in
'C:\Program Files\GnuWin32\share\units'.
If the default units data file is not an absolute pathname, 'units'
will look for the file in the directory that contains the 'units' pro-
gram; if the file is not found there, 'units' will look in a directory
'../share/units' relative to the directory with the 'units' program.
You can determine the location of the files by running
'units --version'. Running 'units --info' will give you additional
information about the files, how 'units' will attempt to find them, and
the status of the related environment variables.
UNICODE SUPPORT
The standard units data file is in Unicode, using UTF-8 encoding. Most
definitions use only ASCII characters (i.e., code points U+0000 through
U+007F); definitions using non-ASCII characters appear in blocks begin-
ning with '!utf8' and ending with '!endutf8'.
When 'units' starts, it checks the locale to determine the character
set. If 'units' is compiled with Unicode support and definitions; oth-
erwise these definitions are ignored. When Unicode support is active,
'units' will check every line of all of the units data files for
invalid or non-printing UTF-8 sequences; if such sequences occur,
'units' ignores the entire line. In addition to checking validity,
'units' determines the display width of non-ASCII characters to ensure
proper positioning of the pointer in some error messages and to align
columns for the 'search' and '?' commands.
At present, 'units' does not support Unicode under Microsoft Windows.
The UTF-16 and UTF-32 encodings are not supported on any systems.
If definitions that contain non-ASCII characters are added to a units
data file, those definitions should be enclosed within '!utf8' ...
'!endutf8' to ensure that they are only loaded when Unicode support is
available. As usual, the '!' must appear as the first character on
the line. As discussed in Units Data Files, it's usually best to put
such definitions in supplemental data files linked by an '!include'
command or in a personal units data file.
When Unicode support is not active, 'units' makes no assumptions about
character encoding, except that characters in the range 00-7F hexadeci-
mal correspond to ASCII encoding. Non-ASCII characters are simply
sequences of bytes, and have no special meanings; for definitions in
supplementary units data files, you can use any encoding consistent
with this assumption. For example, if you wish to use non-ASCII char-
acters in definitions when running 'units' under Windows, you can use a
character set such as Windows ``ANSI'' (code page 1252 in the US and
Western Europe). You can even use UTF-8, though some messages may be
improperly aligned, and 'units' will not detect invalid UTF-8
sequences. If you use UTF-8 encoding when Unicode support is not
active, you should place any definitions with non-ASCII characters out-
side '!utf8' ... '!endutf8' blocks--otherwise, they will be ignored.
Typeset material other than code examples usually uses the Unicode
minus (U+2212) rather than the ASCII hyphen-minus operator (U+002D)
used in 'units'; the figure dash (U+2012) and en dash (U+2013) are also
occasionally used. To allow such material to be copied and pasted for
interactive use or in units data files, 'units' converts these charac-
ters to U+002D before further processing. Because of this, none of
these characters can appear in unit names.
READLINE SUPPORT
If the 'readline' package has been compiled in, then when 'units' is
used interactively, numerous command line editing features are avail-
able. To check if your version of 'units' includes 'readline', invoke
the program with the '--version' option.
For complete information about 'readline', consult the documentation
for the 'readline' package. Without any configuration, 'units' will
allow editing in the style of emacs. Of particular use with 'units'
are the completion commands.
If you type a few characters and then hit ESC followed by '?' then
'units' will display a list of all the units that start with the char-
acters typed. For example, if you type 'metr' and then request comple-
tion, you will see something like this:
You have: metr
metre metriccup metrichorsepower metrictenth
metretes metricfifth metricounce metricton
metriccarat metricgrain metricquart metricyarncount
You have: metr
If there is a unique way to complete a unitname, you can hit the TAB
key and 'units' will provide the rest of the unit name. If 'units'
beeps, it means that there is no unique completion. Pressing the TAB
key a second time will print the list of all completions.
The readline library also keeps a history of the values you enter. You
can move through this history using the up and down arrows. The his-
tory is saved to the file '.units_history' in your home directory so
that it will persist across multiple 'units' invocations. If you wish
to keep work for a certain project separate you can change the history
filename using the '--history' option. You could, for example, make an
alias for 'units' to 'units --history .units_history' so that 'units'
would save separate history in the current directory. The length of
each history file is limited to 5000 lines. Note also that if you run
several concurrent copies of 'units' each one will save its new history
to the history file upon exit.
UPDATING CURRENCY EXCHANGE RATES
The units program includes currency exchange rates and prices for some
precious metals in the database. Of course, these values change over
time, sometimes very rapidly, and 'units' cannot provide real time val-
ues. To update the exchange rates run the 'units_cur', which rewrites
the files containing the currency rates, typically
'/usr/share/units/currency.units'. This program requires 'python' and
the 'unidecode' package, and must be run with suitable permissions to
write the file. To keep the rates updated automatically, run it using
a cron job on a Unix-like system, or a similar scheduling program on a
different system. Currency exchange rates are taken from Time Genie
(http://www.timegenie.com) and precious metals pricing from Packetizer
(www.packetizer.com). These sites update once per day, so there is no
benefit in running the update script more often than daily. You can
run 'units_cur' with a filename specified on the command line and it
will write the data to that file. If you give '-' for the file it will
write to standard output.
DATABASE COMMAND SYNTAX
unit definition
Define a regular unit.
prefix- definition
Define a prefix.
funcname(var) noerror units=[in-units,out-units] domain=[x1,x2]
range=[y1,y2] definition(var) ; inverse(funcname)
Define a nonlinear unit or unit function. The four optional
keywords 'noerror', 'units=', 'range=' and 'domain=' can appear
in any order. The definition of the inverse is optional.
tabname[out-units] noerror pair-list
Define a piecewise linear unit. The pair list gives the points
on the table listed in ascending order. The 'noerror' keyword
is optional.
!endlocale
End a block of definitions beginning with '!locale'
!endutf8
End a block of definitions begun with '!utf8'
!endvar
End a block of definitions begun with '!var' or '!varnot'
!include file
Include the specified file.
!locale value
Load the following definitions only of the locale is set to
value.
!message text
Display text when the database is read unless the quiet option
('-q') is enabled.
!set variable value
Sets the environment variable, variable, to the specified value
only if it is not already set.
!unitlist alias definition
Define a unit list alias.
!utf8 Load the following definitions only if 'units' is running with
UTF-8 enabled.
!var envar value-list
Load the block of definitions that follows only if the environ-
ment variable envar is set to one of the values listed in the
space-separated value list. If envar is not set, 'units' prints
an error message and ignores the block of definitions.
!varnot envar value-list
Load the block of definitions that follows only if the environ-
ment variable envar is set to value that is not listed in the
space-separated value list. If envar is not set, 'units' prints
an error message and ignores the block of definitions.
GNU FREE DOCUMENTATION LICENSE
FILES
/usr/local/share/units/definitions.units -- the standard units data
file
AUTHOR
19 March 2014 UNITS(1)
units-2.12/INSTALL 0000664 0001750 0001750 00000017051 10232761036 013115 0 ustar adrian adrian Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
The file `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
CPU-COMPANY-SYSTEM
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
==================
`configure' recognizes the following options to control how it
operates.
`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
`--help'
Print a summary of the options to `configure', and exit.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made.
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.
units-2.12/getopt.h 0000664 0001750 0001750 00000010661 12040123025 013524 0 ustar adrian adrian /* Declarations for getopt.
Copyright (C) 1989, 90, 91, 92, 93, 94 Free Software Foundation, Inc.
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2, or (at your option) any
later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, 51 Franklin Street, Fifth Floor, Boston, MA 02111 USA. */
#ifdef STRINGS_H
# include
#else
# include
#endif
#ifndef _GETOPT_H
#define _GETOPT_H 1
#ifdef __cplusplus
extern "C" {
#endif
/* For communication from `getopt' to the caller.
When `getopt' finds an option that takes an argument,
the argument value is returned here.
Also, when `ordering' is RETURN_IN_ORDER,
each non-option ARGV-element is returned here. */
extern char *optarg;
/* Index in ARGV of the next element to be scanned.
This is used for communication to and from the caller
and for communication between successive calls to `getopt'.
On entry to `getopt', zero means this is the first call; initialize.
When `getopt' returns EOF, this is the index of the first of the
non-option elements that the caller should itself scan.
Otherwise, `optind' communicates from one call to the next
how much of ARGV has been scanned so far. */
extern int optind;
/* Callers store zero here to inhibit the error message `getopt' prints
for unrecognized options. */
extern int opterr;
/* Set to an option character which was unrecognized. */
extern int optopt;
/* Describe the long-named options requested by the application.
The LONG_OPTIONS argument to getopt_long or getopt_long_only is a vector
of `struct option' terminated by an element containing a name which is
zero.
The field `has_arg' is:
no_argument (or 0) if the option does not take an argument,
required_argument (or 1) if the option requires an argument,
optional_argument (or 2) if the option takes an optional argument.
If the field `flag' is not NULL, it points to a variable that is set
to the value given in the field `val' when the option is found, but
left unchanged if the option is not found.
To have a long-named option do something other than set an `int' to
a compiled-in constant, such as set a value from `optarg', set the
option's `flag' field to zero and its `val' field to a nonzero
value (the equivalent single-letter option character, if there is
one). For long options that have a zero `flag' field, `getopt'
returns the contents of the `val' field. */
struct option
{
#if defined (__STDC__) && __STDC__
const char *name;
#else
char *name;
#endif
/* has_arg can't be an enum because some compilers complain about
type mismatches in all the code that assumes it is an int. */
int has_arg;
int *flag;
int val;
};
/* Names for the values of the `has_arg' field of `struct option'. */
#define no_argument 0
#define required_argument 1
#define optional_argument 2
#if defined (__STDC__) && __STDC__
#ifdef __GNU_LIBRARY__
/* Many other libraries have conflicting prototypes for getopt, with
differences in the consts, in stdlib.h. To avoid compilation
errors, only prototype getopt for the GNU C library. */
extern int getopt (int argc, char *const *argv, const char *shortopts);
#else /* not __GNU_LIBRARY__ */
extern int getopt ();
#endif /* __GNU_LIBRARY__ */
extern int getopt_long (int argc, char *const *argv, const char *shortopts,
const struct option *longopts, int *longind);
extern int getopt_long_only (int argc, char *const *argv,
const char *shortopts,
const struct option *longopts, int *longind);
/* Internal only. Users should not call this directly. */
extern int _getopt_internal (int argc, char *const *argv,
const char *shortopts,
const struct option *longopts, int *longind,
int long_only);
#else /* not __STDC__ */
extern int getopt ();
extern int getopt_long ();
extern int getopt_long_only ();
extern int _getopt_internal ();
#endif /* __STDC__ */
#ifdef __cplusplus
}
#endif
#endif /* _GETOPT_H */
units-2.12/units.dvi 0000664 0001750 0001750 00000734120 12607541442 013742 0 ustar adrian adrian їР ; ш TeX output 2015.10.14:1703 џџџџђ 33 ўрGѓJТжN Мj cmbx12ыJUnitsЦqConџZ versionG БИ ЊЦѓ6Kё`y
ѓ3
cmr10сEditionІf2.11forѓ7пъ b>
ѓ3
cmmi10щ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: с5Љ Gы\532UnitffExpressionsgt32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32: лы\6Ё!Gс5.1
ѓ5OpMоerators Ю щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: RHс6Є
33!G5.2
ѓ5SumsІfandDi erencesofUnits# щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: Їбс8Ё!G5.3
ѓ5NumВ!bMоersІfasUnits7$ щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: Л\с9Ё!G5.4
ѓ5Built-inІfFџeunctions Ўп щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: 3с9Ё!G5.5
ѓ5PreviousІfResult>ю щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: У&с10Ё!G5.6
ѓ5ComplicatedІfUnitExpressions л щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: с11Ё!G5.7
ѓ5BacВ!kwardsІfCompatibility:нн`т*с'and`т-с':э щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: П$с12 Gы\632NonlinearffUnitConЬversions\32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:
вФы\12џ!Gс6.1
ѓ5TџeempMоeratureІfConВ!versionsG щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ:
Ыжс13Ё!G6.2
ѓ5OtherІfNonlinearUnits,a щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ:
Ас14ІGы\732UnitffLists:32ConЬversiontoSumsofUnitsП 32ыc:Q 32:32:32:
vsы\15Є mdG832LoggingffCalculations32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:
Vъы\19 mcG932InЬvokingffы_unitsЯ_32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:
Чы\20ЁG1032AddingffYўІfourOwnDe nitions@s32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32: їлы\25џ!Gс10.1
ѓ5UnitsІfDataFilesЎ щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ:
хс25Є
33!G10.2
ѓ5De ningІfNewUnitsandPre xesГ щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ:
7жс26Ё!G10.3
ѓ5De ningІfNonlinearUnits Оc щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: Bс27Ё!G10.4
ѓ5De ningІfPiecewiseLinearUnitsRK щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: жс29Ё!G10.5
ѓ5De ningІfUnitListAliases э щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: qRс31ІGы\1132NumericffOutputFўІformat32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32: Лњы\31џ!Gс11.1
ѓ5FџeormatІfSpMоeci cationaя щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: ц&с32Ё!G11.2
ѓ5FlagsЌ щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ:
08с32Ё!G11.3
ѓ5FieldІfWidth( щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ:
ЌТс33Ё!G11.4
ѓ5PrecisionjР щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ:
юјс33џџџў ђ НЉсii 33 §ЬЭGы\1232Los3calizationwэ32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32: /Uы\34џ!Gс12.1
ѓ5LoMоcaleeъ щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: ъ"с34
33!G12.2
ѓ5AdditionalІfLoMоcalizationк щщ:нл щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ: щ:
^вс35 33Gы\1332EnЬvironmentffVўІfariables!32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:й ы\37Є џG1432DataffFilesg32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32: ~ы\38ЁG1532Unicos3deffSupport32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:
Rvы\38ЁG1632ReadlineffSupps3ort№a32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:ЇЩы\39ЁG1732Ups3datingffCurrencyExcЬhangeRatesC32ыc:Q 32:32:32:32:32:32:32: њљы\40ЁG1832DatabaseffCommandSynЬtaxEЯ32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32: §7ы\40ЁG1932GNUffFўІfreeDos3cumenЬtationLicenseіЧ32ыc:Q 32:32:32:32:32:32:32:32:Ў.ы\41ЁGIndexrИ32ыc:Q 32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:32:
* ы\49 ,Цђ GсUnitsІfConВ!versionYо*1 33 § ЬЭGыS1 ИQOvџuТerviewzГofѓVпЕT GЎ cmtt12ыVunits )=GсTheЭтunitsсprogramconВ!vertsЭquantitiesexpressedinvџdDarioussystemsofmeasurementtotheirЄ
33GequivџdDalenВ!ts;inother;systemsofmeasurement.ЛLikemanysimilar;programs,`-itcanhandleЁGmВ!ultiplicative\{scalecВ!hanges. Itcan\zalsohandlenonlinearconversionssuchasFџeahrenheitЁGtoйaCelsius;ќОѓй R cmr7Ў1 яQсseeй`Section6.1[TџeempMоeratureConВ!versions],& page13.vЮTheprogramйacanalsoЁGpMоerformYЇconВ!versionsYЈfromandtosumsofunits,isucВ!hasconВ!vertingbMоetweenmetersYЈandfeetЁGplusІfincВ!hes.Љ15!GBasicJkopMоerationissimple:%чyВ!ouentertheunitsthatyouwanttoconvertѓ9§ ':
ѓ3
cmti10фfrџpЙom!vсandtheЁGunits thatyВ!ouwanttoconvertфtoс.бYџeoucanusetheprograminteractivelywithprompts,ИorЁGyВ!ouІfcanuseitfromthecommandline.І!GBeyВ!ond simple unitconversions,:тunits сcanbMоeusedasageneral-purpMоosescienВ!ti ccal-ЁGculatorm(thatm)kВ!eepstrackofunitsm)initscalculations.ЪЩYџeoucanformarbitrarycomplexmath-ЁGematical кexpressionsofdimensions лincludingsums,?wproMоducts,quotienВ!ts,poВ!wers,?wand кevenЁGroMоotsЮЇofdimensions.ѓThВ!usyoucanensureaccuracyanddimensionalconsistencywhenwork-ЁGing!Чwithlong!ШexpressionsthatinВ!volve!Чmanydi erent!ЧunitsthatmaВ!ycombine!ЧincomplexЁGwВ!ays;Іfforanillustration,seeSection5.6[ComplicatedUnitExpressions],page11.І!GTheђunitsarede nedinanexternaldata le.РУYџeoucanusetheextensivВ!edata lethatЁGcomesMІwithMЅthisprogram,wuoryВ!oucanproВ!videyourMІowndataMІ letosuityВ!ourneeds.гYџeouЁGcanІfalsouseyВ!ourowndata letosupplementthestandarddata le.І!GYџeouUcanTcВ!hangethedefaultbMоehaВ!viorofтunitsсwithvџdDariousoptionsgivВ!enonthecommandЁGline.ннSeeІfChapter9[InВ!vokingІfUnits],page20,foradescriptionoftheaВ!vџdDailableoptions.!ќGыS2 ИQInџuТteractingzГwithыVunits )=GсTџeoxinВ!vokewunitsforinteractiveuse,яњѓprompt,Ђ
typMоethequantity єandunitsthatyouare єconvertingфfrџpЙomс.м FџeorЁGexample,xifќyВ!ou§wantto§convertten§meterstofeet,xtВ!ypMоeш10Іfmetersс.бeNext,тunits§сwillprinВ!tЁG`тYouІfwant:с'IЪS.Z=YџeouzshouldztВ!ypMоetheunitsyouwanttoconvertфtoс.Z>Tџeoconverttofeet,ЏyouЁGwВ!ouldвЏtypMоeвЎшfeetс.bЗIftheтreadlineсlibrarywВ!ascompiledinthenтtabсwillcompleteunitЁGnames.КЛSee<џChapter<ў16[ReadlineSuppMоort],Rpage39,RformoreinformationabMоoutтreadlineс.ЁGTџeoц7quitц6theprogramunderUnix,і+pressтCtrl-CсorтCtrl-Dс.OUnderWindoВ!ws,і*pressтCtrl-CЁGсorІfтCtrl-Zс;withthelatter,yВ!oumayalsoneedtopressтEnterс.І!GTherresultqwillbMоedisplaВ!yedrintworways.гThe rstqlineofoutput,ЂwhicВ!hismarkВ!edwithЁGaшL`т*с'шMtoindicatemВ!ultiplication,јЦgivesшLtheresultoftheconВ!versionшLyouhaveшLaskedfor.ЃTheЁGsecond#lineofoutput, RwhicВ!hismarkedwith$a`т/с'toindicatedivision, RgivestheinverseofЁGtheІfconВ!versionfactor.ннIfyouconvert10meterstofeet,тunitsсwillprintG ff = ѓ/уќ-=Ў1 ѓoДЧ cmr9ЌButFџ:ЋahrenheittoCelsiusislinear,YэyО9ouinsist.'zNotso.'yAПtransformationѓ5љ" cmmi9ВTaхЌislinearifВTHуЌ(ВxЛWЌ+ВyRЊЌ)B=
ВTHуЌ(ВxЌ)8+ВTЌ(ВyRЊЌ)TandthisfailsforВTЌ(ВxЌ)Ц=Вax8Ќ+ВbЌ. pThisTtransformationisane,butnotlinear. 9ђ GсUnitsІfConВ!versionYо*2 33 § ЬЭEјDт*ПЊ32.808399
33EјD/ПЊ0.03048 34GсwhicВ!h#хtells#цyouthat#ц10metersequalsabMоout32.8feet.V\ThesecondnВ!umbMоergives#цthecon-Є
33GvВ!ersionginthegЌoppMоositedirection.ШѕInthiscase,t8ittellsyВ!outhat1foMоotisequaltoabMоout0.03ЁGdekџdDametersІfsincethedekameteris10meters.ннItalsotellsyВ!outhat1/32.8isabMоout0.03.Љ !GTheЖИтunitsсprogramprinВ!tstheinversebMоecausesometimesitisamoreconvenientnumbMоer.ЁGInхtheхexampleabMоoВ!ve, Бforexample,theхinВ!versevџdDalueхisanexactconВ!version:}-aхfoMоotisexactlyЁG0.03048ІfdekџdDameters.ннButthenВ!umbMоerІfgiventheotherdirectionisinexact. !GIfІfyВ!ouconvertgrainstopMоounds,youwillseethefollowing:І.љтYouПЊhave:grainsЁ.љYouПЊwant:poundsЁ\іь*ПЊ0.00014285714Ё\іь/ПЊ70009GсFџeromCTthesecondCUlineoftheoutputyВ!oucanimmediatelyseethatagrainisequaltoasevВ!enЁGthousandthKofLapMоound.ддThisisnotsoobВ!viousfromthe rstlineoftheoutput.ддIfyВ!ou ndЁGtheІfoutputformatconfusing,tryusingtheт--verboseсoption:І.љтYouПЊhave:grainЁ.љYouПЊwant:aeginaminaЁ\іьgrainПЊ=0.00010416667aeginaminaЁ\іьgrainПЊ=(1/9600)aeginamina9GсIfеpyВ!ouеorequestaconВ!versionеpbMоetweenunitsеpthatmeasurereciproMоcaldimensions,с1thenтunitsЁGсwillРXdisplaВ!ytheРYconversionresultswithanextranoteРYindicatingthatreciproMоcalconversionЁGhasІfbMоeendone:І.љтYouПЊhave:6ohmsЁ.љYouПЊwant:siemensЁ\іьreciprocalПЊconversionЁ\іь*ПЊ0.16666667Ё\іь/ПЊ6FЬЭGсReciproMоcalуЌconВ!versionуcanbMоesuppressedbВ!yusingtheт--strictсoption.АAsusual,ђўusetheЁGт--verboseІfсoptiontogetmorecomprehensibleoutput:І.љтYouПЊhave:texЁ.љYouПЊwant:typpЁ\іьreciprocalПЊconversionЁ\іь1ПЊ/tex=496.05465typpЁ\іь1ПЊ/tex=(1/0.0020159069)typpff.љYouПЊhave:20mphЁ.љYouПЊwant:sec/mileЁ\іьreciprocalПЊconversionЁ\іь1ПЊ/20mph=180sec/mileЁ\іь1ПЊ/20mph=(1/0.0055555556)sec/mile џџGсIfюyВ!ouяenterincompatibleunittypMоes,дPtheтunitsясprogramwillprintaяmessageindicatingЁGthatІftheunitsarenotconformableanditwilldisplaВ!ythereducedformforeachunit: K ђ GсUnitsІfConВ!versionYо*3 33 § ЬЭ.љтYouПЊhave:ergs/hourЄ
33.љYouПЊwant:fathomskg^2/dayЁ.љconformabilityПЊerrorЁ\іь2.7777778e-11ПЊkgm^2/sec^3Ё\іь2.1166667e-05ПЊkg^2m/secJffGсIf{yВ!ouonlywant{to ndthereducedformorde nitionofaunit,СsimplypressтEnterсattheЄ
33G`тYouІfwant:с'MpЙprompt.ннHereІfisanexample:Љ.љтYouПЊhave:janskyЁ.љYouПЊwant:Ё\іьDefinition:ПЊfluxunit=1e-26W/m^2Hz=1e-26kg/s^20 GсThewoutputfromтunitsсindicateswЎthatthejanskyisde nedtobMоeequaltoa
uxunitwhicВ!hЁGinїЖturnїЗisde nedtobMоeacertaincomВ!binationofwВ!atts,Іmeters,andhertz.ЃЂThefullyїЖreducedЁG(andІfinthiscasesomewhatmorecryptic)formappMоearsonthefarrighВ!t.І!GSomeН namedН unitsaretreatedasdimensionlessinsomesituations." TheseunitsincludeЁGthejoradianandsteradian.)јTheseunitswillbMоetreatedasequalto1inunitsconВ!versions.ЁGPВ!owerэяisequaltotorquetimesangularvВ!eloMоcityџe.ДxThisэяconversioncanonlybMоeperformedifЁGtheІfradianisdimensionless.І.љтYouПЊhave:(14ftlbf)(12radians/sec)Ё.љYouПЊwant:wattsЁ\іь*ПЊ227.77742Ё\іь/ПЊ0.0043902509=34GсIty;isalsopMоossibletocomputerootsy:andothernon-inВ!tegerpoВ!wersy;ofdimensionlessunits;ЁGthisІfalloВ!wscomputationssuchasthealtitudeofgeosynchronousorbit:І.љтYouПЊhave:cuberoot(Gearthmass/(circle/siderealday)^2)-earthradiusЁ.љYouПЊwant:milesЁ\іь*ПЊ22243.267Ё\іь/ПЊ4.4957425e-05=33GсNameddimensionlessunitsarenottreatedasdimensionlessinotherconВ!texts.ЎъTheycannotЁGbMоeІfusedasexponenВ!tssoforexample,`тmeter^radianс'isforbidden.І!GIf.yВ!ou.wanta.listofoptionsyВ!oucantВ!ypMоeш?сatthe`тYouІfwant:с'@Aprompt.vzTheprogramЁGwill@ЊdisplaВ!yalist@ЋofnamedunitsthatareconformablewiththeunitthatyВ!ouenteredatЁGtheC_`тYouІfhave:с'>?ЫpromptC_abMоoВ!ve.МлConformableunitC`фcџpЙombinations)wсwillnotappMоearonthislist.І!GTВ!ypingDћшhelpDќсateitherpromptdisplaysDќashorthelpmessage.ЙYџeoucanalsotВ!ypMоeшhelpЁGсfolloВ!wed50byaunitname.И Thiswillinvokeapagerontheunits5/databaseatthepMоointwhereЁGthatЕunitЖisde ned.вЃYџeoucanreadthede nitionandcommenВ!tsthatmaВ!ygiveЖmoredetailsЁGorъїhistoricalъјinformationabMоouttheunit.d(YџeoucangenerallyquitoutofthepagebВ!ypressingЁG`тqс'.)І!GTВ!ypingНзшsearchНиѓ:pЎ0J
ѓ3
cmsl10хtextњзсwilldisplayНзalistofalloftheunitswhosenamesconВ!tainхtextњисasaЁGsubstringѓЭalongwiththeirde nitions.ЦThismaВ!yhelpinthecasewhereyouaren'tsureofЁGtheІfrighВ!tunitname. Ufђ GсUnitsІfConВ!versionYо*4 33 § ЬЭGыS3 ИQUsingzГыVunitsыSNon-InџuТteractively "#GсTheћtтunitsћsсprogramcanpMоerformunitsconВ!versionsћtnon-interactivelyfromћsthecommandЄ
33Gline.ДўTџeoCqdothis,jДtВ!ypMоethecommand,tВ!ypMоetheoriginalunitexpression,andtВ!ypMоethenewЁGunitsБRyВ!ouwant.ўЁIfaunitsБSexpressioncontainsnon-alphanumericcharacters,Д
youmayneedЁGtoІfprotectitfrominВ!terpretationbytheshellusingsingleordoublequotecharacters.Єи.!GIfІfyВ!outypMоeЁ.љтunitsПЊ"2liters"quartsи-GсthenІfтunitsсwillprinВ!tЁEјDт*ПЊ2.1133764
33EјD/ПЊ0.47317647 aGсandь]thenь^exit.ЏУTheoutputtellsyВ!outhat2litersisabMоout2.1quarts,§лoralternativВ!elythatЉ
33GaІfquartisabMоout0.47times2liters.Ё!GIfTtheconВ!versionTissuccessful,thenтunitsсwillreturnsuccess(zero)tothecallingen-ІGvironmenВ!t.{&Ifкдyouenternon-conformableunitsкгthenтunitsсwillprintaкгmessagegivingtheІGreducedІfformofeacВ!hunitanditwillreturnfailure(nonzero)tothecallingenvironment.и-!GWhen 0yВ!ou /invokeтunitsсwith /onlyoneargument,Ёitwillprint /outthede nitionoftheІGspMоeci edъunit.Њ]Itwillъreturnfailureiftheunitisnotde nedandsuccessiftheunitisІGde ned.#IіGыS4 ИQUnitzГDe nitions "#GсThe;2conВ!version;3informationisreadfromaunitsdata lethatiscalledтdefinitions.unitsІGсand\ isusually\loMоcatedintheт/usr/share/unitsсdirectoryџe. IfyВ!ouinvoke\тunitsсwiththeІGт-VћКсoption,itћЛwillprinВ!ttheloMоcationofthis le.нкThedefault leincludesde nitionsforallІGfamiliarеюunits,саabbreviationsandmetricpre xes.lvItalsoincludesmanВ!yobscureorarchaicІGunits.Ё!GManВ!yІfconstantsofnaturearede ned,includingthese:и-.љтpi9|ЄсratioІfofcircumferencetodiameterІ.љтc?a>sequenceofquotienВ!ts.ЄТFџeorexample,c№`тm/sІf*s/dayс'IСisequivџdDalent>to`тm/dayс'.ЁGSimilarlyџe,ІfyВ!oucouldwrite`т1/2*meterс'Hkшtogethalfameter.ЬЭ!GThe+Rтunitsсprogram+SsuppMоortsanotheroptionfornВ!umericalfractions:чЖyoucanindicateЁGdivisionofфnumbџpЙersщ.сwiththevВ!erticalbar(`т|с'),#РsoifyouwantedhalfameteryoucouldwriteЁG`т1|2Іfmeterс'IЪS.ЅYџeouЈcannotЉusethevВ!erticalbartoindicatedivisionofnon-nВ!umericalunitsЁG(e.g.,Іf`тm|sс'resultsinanerrormessage).І!GPВ!owersKСofunitsKРcanbMоespeci edusingKРthe`т^с'cВ!haracter,uasshowninKРthefollowingex-ЁGample,ЯorxЉbВ!yxЈsimpleconcatenationofaunitanditsexpMоonenВ!t:Цџ`тcm3с'isequivџdDalenВ!tto`тcm^3с';ЁGifХAtheexpMоonenВ!tismorethanonedigit, јthe`т^с'isrequired.:nYџeoucanalsouse`т**с'asanЁGexpMоonenВ!tІfoperator.І.љтYouПЊhave:cm^3Ё.љYouПЊwant:gallonsЁ\іь*ПЊ0.00026417205Ё\іь/ПЊ3785.4118;ffGсConcatenationЪ%onlyЪ&wВ!orkswithasingleunitname:%\ifyВ!ouwrite`т(m/s)2с',гтunitsсwilltreatЁGit мasmВ!ultiplicationby2.?Whenaunitincludesapre x,&zexpMоonentopMоeratorsapplytotheЁGcomВ!bination,Ђso№`тcentimeter3с'givesёcubiccentimeters.б Ifёyouseparateёthepre xfromtheЁGunit#dwith#eanВ!ymultiplicationopMоerator#e(e.g.,=`тcentiІfmeter^3с'),=thepre xistreatedasasep-ЁGarateunit,7RsotheexpMоonenВ!tappliesonlytotheunitwithoutthepre x.ЏThesecondexampleЁGisдequivџdDalenВ!tдto`тcentiІf*(meter^3)с',пxandgivВ!esдahundredthдofacubicmeter,пxnotacubicЁGcenВ!timeter..TheЂтunitsсprogramislimitedЁinternallytoproMоductsof99Ёunits;NРaccordinglyџe,ЁGexpressionswlikВ!ex`тmeter^100с'or`тjoule^34с'(represenВ!tedinternallyxas`тkg^34Іfm^68/s^68с'eK)ЁGwillІffail.І!GTheћ`т|с'ќopMоeratorhasthehighestprecedence,П soyВ!oucanwritethesquareroMоotoftВ!woЁGthirdsёјas`т2|3^1|2с'.РThe`т^с'ёљopMоeratorhasthesecondhighestprecedence,нandisevџdDaluatedЁGrighВ!tІftoleft,asusual:ЬЭ.љтYouПЊhave:5*2^3^2Ё.љYouПЊwant:Ё\іьDefinition:ПЊ2560.34GсWithкadimensionlessлbaseunit, Х5anВ!ydimensionlessexpMоonentлismeaningful(e.g.,ЁG`тpi^exp(2.371)с').TEvВ!enЭѕthoughangleissometimesЭєtreatedasdimensionless,иexpMоonentsЁGcannotІfhaВ!vedimensionsofangle: \ђ GсUnitsІfConВ!versionYо*8 33 § ЬЭ.љтYouПЊhave:2^radianЄ
33 Гц^Ё.љExponentПЊnotdimensionless-rsGсIf\фthe\хbaseunitisnotdimensionless,ktheexpMоonenВ!tmust\хbMоearationalnВ!umbMоerхpUс/хqI3с,kand\фtheЄ
33GdimensionEЙofEИtheunitmВ!ustbMоeapMоoВ!werEЙofхqс,mso`тgallon^2|3с'wВ!orksbut`тacre^2|3с'fails.ЁGAnoexpMоonenВ!tusingthepslash(`т/с')operator(e.g.,Жё`тgallon^(2/3)с')isalsopacceptable;эstheЁGparenВ!theses:KareneededbMоecause:Jtheprecedenceof`т^с'ishigherthanthatof`т/с'.ЙдSinceтunitsЁGсcannotћzrepresenВ!tdimensionsћ{withexpMоonentsgreaterthanћ{99, ЉafullyreducedexpMоonenВ!tmustЁGhaВ!veьИхqчLт<Іfс100&nY.јWhenьИraisingьЗanon-dimensionlessunittoapMоoВ!wer,ктunitsьИсattemptstoconВ!vertЁGadecimalexpMоonenВ!ttoa rationalnumbMоerwithхqчLт<Іfс100&М.ЋIfthis isnotpossibleтunitsсdisplaВ!ysЁGanІferrormessage:Љ
.љтYouПЊhave:ft^1.234Ё.љBaseПЊunitnotdimensionless;rationalexponentrequired ??GсAvѓdecimalwЌexpMоonenВ!twmustmatchitsrationalwrepresentationtomachineprecision,+§soЁG`тacre^1.5с'ІfwВ!orksbut`тgallon^0.666с'doMоesnot. EGGы\5.2Sumsf@andDi erencesofUnits33GсYџeouНmaВ!ysometimesОwanttoaddvџdDaluesОofdi erentunitsthatОareoutsidetheSI.YџeoumaВ!yЁGalsojywishjztouseтunitsсasacalculatorthatkВ!eepstrackofjzunits.ЩуSumsofconformableunitsЁGareІfwrittenwiththe`т+с'cВ!haracter,anddi erenceswiththe`т-с'character.І.љтYouПЊhave:2hours+23minutes+32secondsЁ.љYouПЊwant:secondsЁ\іь*ПЊ8612Ё\іь/ПЊ0.00011611705ЉAџџ.љYouПЊhave:12ft+3inЁ.љYouПЊwant:cmЁ\іь*ПЊ373.38Ё\іь/ПЊ0.0026782366І.љYouПЊhave:2btu+450ftlbfЁ.љYouПЊwant:btuЁ\іь*ПЊ2.5782804Ё\іь/ПЊ0.38785542:ЅЅGсThefMexpressionsfLthatareaddedorsubtractedmВ!ustreducetoidenВ!ticalexpressionsinprim-ЁGitivВ!eІfunits,oranerrormessagewillbMоedisplayed:
.љтYouПЊhave:12printerspoint-4herediumЁ lи^Ё.љIllegalПЊsumofnon-conformableunits-rsGсAsЃ;usual,зtheprecedencefor`т+с'andЃ:`т-с'isloВ!werЃ;thanthatoftheotheropMоerators.zAЂљfractionalЁGquanВ!tityЅDsuchЅEas21/2cupscanbMоegivВ!enas`т(2+1|2)Іfcupsс';ЅЅtheparenВ!thesesarenecessaryЁGbMоecause3&mВ!ultiplicationhashigher3'precedencethanaddition. IfyВ!ouomittheparentheses,ЁGтunitsІfсattemptstoadd`т2с'and`т1|2cupsс',andyВ!ougetanerrormessage: Мђ GсUnitsІfConВ!versionYо*9 33 § ЬЭ.љтYouПЊhave:2+1|2cupsЄ
33 3:^Ё.љIllegalПЊsumordifferenceofnon-conformableunits,Ч GсThe
uexpressioncouldalso
vbMоecorrectlywrittenas`т(2+1/2)Іfcupsс'.ЉуIfyВ!ouwrite`т2ПЊ1|2cupsс'Є
33GtheІfspaceisinВ!terpretedasфmultiplicџpЙation}qсsotheresultisthesameas`т1cupс'.`Ж!GThepЅ`т+с'andpЄ`т-с'cВ!haracterssometimesappMоearsinexpMоonenВ!tslike`т3.43e+8с'.ЫёThisleadstoЁGanЅыamВ!biguityinanexpressionlikeЅъ`т3e+2ІfyCс'.нДTheunit`тeс'isasmallunitofcharge,ІsothisЁGcaniѕbMоeregardedasequivџdDalenВ!tto`т(3e+2)ІfyCс'or`т(3e)+(2yC)с'.ЩИThisamВ!biguityiѕisresolvВ!edЁGbВ!yІfalwaysinterpreting`т+с'and`т-с'aspartofanexpMоonentifpMоossible.Љ DFGы\5.3NumЬbs3ersf@asUnits33GсFџeorФБтunitsс,ЬCnВ!umbMоersarejustanotherkindofunit.8ОTheycanФАappearasmanВ!ytimesasyouЁGlikВ!e{сand{тinany{тorderinaunitexpression.ЯБFџeorexample,bto ndthevВ!olumeofabMоoВ!xthatisЁG2ІfftbВ!y3ftby12ftinsteres,youcoulddothefollowing:`З.љтYouПЊhave:2ft3ft12ftЁ.љYouПЊwant:stereЁ\іь*ПЊ2.038813Ё\іь/ПЊ0.49048148ff.љYouПЊhave:$5/yardЁ.љYouПЊwant:cents/inchЁ\іь*ПЊ13.888889Ё\іь/ПЊ0.072{њNGсAndѕtheєsecondexampleshoВ!wshowѕthedollarsignintheunitsconВ!versionѕcanprecedetheЁG vВ!e.ннBeІfcareful:тunitsсwillinВ!terpret`т$5с'withnospaceasequivџdDalentto`тdollar^5с'.ІGы\5.4Built-inf@FўІfunctions33GсSevВ!eralЃYbuilt-infunctionsЃXareprovided:мW`тsinс',Ѓѕ`тcosс',`тtanс',`тlnс',`тlogс',`тlog2с',`тexpс',`тacosс',ЁG`тatanс':?and`тasinс'. gThe`тsinс',4`тcosс',and:?`тtanс'functionsrequire:>eitheradimensionlessЁGargumenВ!tІforanargumentwithdimensionsofangle.`Ж.љтYouПЊhave:sin(30degrees)Ё.љYouПЊwant:Ё\іьDefinition:ПЊ0.5Љff.љYouПЊhave:sin(pi/2)Ё.љYouПЊwant:Ё\іьDefinition:ПЊ1І.љYouПЊhave:sin(3kg)Ё s^Ё.љUnitПЊnotdimensionless `ЕGсTheWDotherfunctionsonthelistrequiredimensionlessargumenВ!ts.У|TheinversetrigonometricЁGfunctionsІfreturnargumenВ!tswithdimensionsofangle.
Їђ GсUnitsІfConВ!versionTd10 33 § ЬЭ!GIfVyВ!ouwishtotakeroMоotsofWunits,'&youmayusethe`тsqrtс'or`тcuberootс'functions.ЈиTheseЄ
33GfunctionsdrequirethattheargumenВ!thavetheappropriatecroMоot.Ќ2YџeoucanobtainhigherrootsЁGbВ!yІfusingfractionalexpMоonents:Љз .љтYouПЊhave:sqrt(acre)Ё.љYouПЊwant:feetЁ\іь*ПЊ208.71074Ё\іь/ПЊ0.0047913202Љff.љYouПЊhave:(400W/m^2/stefanboltzmann)^(1/4)Ё.љYouПЊhave:Ё\іьDefinition:ПЊ289.80882KІ.љYouПЊhave:cuberoot(hectare)Ё Фpр^Ё.љUnitПЊnotaroot Ў(ѕGы\5.5Previousf@Result33GсYџeouПcaninserttheresultofthepreviousconВ!versionПusingПtheunderscore(`т_с').)mItisusefulЁGwhenІfyВ!ouwanttoconvertthesameinputtoseveraldi erentunits,forexampleІ.љтYouПЊhave:2.3tonrefrigerationЁ.љYouПЊwant:btu/hrЁ\іь*ПЊ27600Ё\іь/ПЊ3.6231884e-005Ё.љYouПЊhave:_Ё.љYouПЊwant:kWЁ\іь*ПЊ8.0887615Ё\іь/ПЊ0.12362832m=qGсSuppMоoseДНyВ!ouwanttodosomedeepfryingthatrequiresДМanoildepthof2inches.тYџeouhaveЁG1/2gallonofoil,( andwВ!anttoknowthelargest-diameterpanthatwillmainВ!taintherequiredЁGdepth.3Theиgnonlinearиfunit`тcircleareaс'givВ!estheфrџpЙadiusО~сofthecircle(seeSection6.2[OtherЁGNonlinearcUnits],Чўpage14,foradmoredetaileddescription)inSI units;эyВ!ouwantdtheфdiameterЁGсinІfфinches цс:І.љтYouПЊhave:1|2gallon/2inЁ.љYouПЊwant:circleareaЁ\іь0.10890173ПЊm4ЬЬ.љYouПЊhave:2_Ё.љYouПЊwant:inЁ\іь*ПЊ8.5749393Ё\іь/ПЊ0.11661898pЄGсIn7mostcases,#йsurroundingwhitespaceis6optional,#кsothepreviousexamplecouldhaВ!ve7usedЁG`т2_с'.ннIfІf`т_с'folloВ!wsanon-numericalunitsymbMоol,however,thespaceisrequired:І.љтYouПЊhave:m_Ёn5ъ^Ё.љParseПЊerror Асђ GсUnitsІfConВ!versionTd11 33 § ЬЭGWhenљ`т_с'њisfolloВ!wedљbyaљdigit,theopMоerationismВ!ultiplicationratherthanexpMоonenВ!tiation,Љ
33GsoІfthat`т_2с',isequivџdDalenВ!tto`т_*2с'%эьratherthan`т_^2с'.ЄОс!GYџeouІfcanusethe`т_с'symВ!bMоolanynumbMоeroftimes;forexample,Ё.љтYouПЊhave:mІ.љYouПЊwant:І\іьDefinition:ПЊ1mІ.љYouПЊhave:__І.љYouПЊwant:І\іьDefinition:ПЊ1m^2QОрGсUsingУЁ`т_с'УЂbMоeforeaconВ!versionУЁhasbMоeenperformed(e.g.,ЪёimmediatelyafterУЂinВ!vocation)УЁgen-ІGeratesІfanerror:Ё.љтYouПЊhave:_Іhv@^І.љNoПЊpreviousresult;
_
notset*%GGсAccordinglyџe,Іf`т_с'servВ!esnopurpMоosewhenтunitsсisinvokednon-interactivelyџe.Ё!GIfёУтunitsёФсisinВ!vokedwithёУtheт--verboseсoption(seeChapter9[InВ!vokingUnits],фpageёУ20),ІGtheІfvџdDalueof`т_с'isnotexpanded:Ё.љтYouПЊhave:mileІ.љYouПЊwant:ftІ\іьmileПЊ=5280ftІ\іьmileПЊ=(1/0.00018939394)ftІ.љYouПЊhave:_І.љYouПЊwant:mІ\іь_ПЊ=1609.344mІ\іь_ПЊ=(1/0.00062137119)ml%FGсYџeouІfcangivВ!e`т_с'atthe`тYouwant:с'?иprompt,butitusuallyisnotveryuseful.\Gы\5.6Complicatedf@UnitExpressions33GсTheИтunitsИсprogramisespMоeciallyhelpfulinensuringaccuracyanddimensionalconsistencyІGwhen#conВ!verting#lengthyunit#expressions.U]Fџeorexample,BлoneformoftheDarcy{WџeeisbacВ!hІG
uid-
oВ!wІfequationis " ТaщP§с=ј8=коШ fe ь
tщdќж0Ў2љщf-МLј33QќОЎ233оШ fe
$
tzщdќж0Ў5GсwhereмщPaђсisthepressureмdrop,јщсisthemassdensitВ!yџe,јщf
Xсisthe(dimensionless)frictionfactor,ІGщLEТсistheEУlengthofthepipMоe,mщQсisthevВ!olumetric
owrate,mandEУщdсisthepipMоediameter.ЛђItІGmighВ!tІfbMоedesiredtohavetheequationintheformA ТЪлщP§с=
ЇщAЄzЎ1|sщf-МLј33QќОЎ233оШ fe
$
tzщdќж0Ў5 8Gсthat.accepted.theuser'snormalunits;rfortВ!ypicalunitsusedintheUS,therequiredcon-ІGvВ!ersionІfcouldbMоesomethinglikeЁ.љтYouПЊhave:(8/pi^2)(lbm/ft^3)ft(ft^3/s)^2(1/in^5)І.љYouПЊwant:psiІ\іь*ПЊ43.533969І\іь/ПЊ0.022970568 Й0ђ GсUnitsІfConВ!versionTd12 33 § ЬЭGThe,јparenВ!theses,їallowindividual,їtermsintheexpressiontobMоeenВ!terednaturallyџe,NastheyЄ
33GmighВ!tmbMоereadfromntheformula.ђAlternativelyџe, яthemultiplicationcouldnbMоedonewiththeЁG`т*с'Q+ratherQ,thanaspace;ІthenparenВ!thesesareneededonlyaround`тft^3/sс'bMоecauseofitsЁGexpMоonenВ!t:ЉМk.љтYouПЊhave:8/pi^2*lbm/ft^3*ft*(ft^3/s)^2/in^5Ё.љYouПЊwant:psiЁ\іь*ПЊ43.533969Ё\іь/ПЊ0.022970568;VGсWithoutЁparenВ!theses,жoandusingspacesЂformultiplication,жothepreviousconversionwouldЁGneedІftobMоeenВ!teredasІ.љтYouПЊhave:8lbftft^3ft^3/pi^2ft^3s^2in^5Ё.љYouПЊwant:psiЁ\іь*ПЊ43.533969Ё\іь/ПЊ0.022970568HчlGы\5.7BacЬkwardsf@Compatibility:`ы_*ы\'f@and`ы_-ы\'33GсThe ?original >тunitsсassignedmВ!ultiplicationahigherprecedencethandivisionusingtheslash.ЁGThis3di ersfromtheusual3precedencerules,VШwhicВ!hgive3multiplicationanddivisionequalЁGprecedence,ІfandcanbMоeconfusingforpeoplewhothinkofunitsasacalculator.І!GThe starџopMоerator(`т*с')includedinthisтunitsсprogramhas,сbВ!ydefault,thesame prece-ЁGdenceЇ asЇdivision,к+andhencefolloВ!wstheusualprecedencerules.ХFџeorbacВ!kwardscompatibilityЁGyВ!oujcankinvokeтunitskсwiththeт--oldstarсoption.юъThen`т*с'hasahigherprecedencethanЁGdivision,ІfandthesameprecedenceasmВ!ultiplicationusingthespace.І!GHistoricallyџe,ѓсtheЧ@hВ!yphenЧ?(`т-с')hasbMоeenusedintecВ!hnicalpublicationstoindicateproMоductsЁGofЊunits,.ћandЋtheoriginalтunitsсprogramtreateditasamВ!ultiplicationopMоerator.%ЊBecauseЁGтunitsr8сproВ!videsseveralotherwaystoobtainr7unitproMоducts,Ѕ,andbecause`т-с'isasubtrac-ЁGtionЙ4opMоeratoringeneralalgebraicЙ3expressions,Нштunitsсtreatsthebinary`т-с'asasubtractionЁGopMоeratorШ}bВ!ydefault.D!FџeorbackwardscompatibilityШ|usetheт--productсoption,бwhichcausesЁGтunitsЇбсtotreatЇвthebinary`т-с'opMоeratorasaproMоductoperator.т When`т-с'ЇвisamВ!ultiplica-ЁGtionЬ-opMоeratorithasthesameprecedenceasmВ!ultiplicationwithaspace,еgivingitahigherЁGprecedenceІfthandivision.І!GWhenHя`т-с'isusedasaunaryopMоeratoritH№negatesitsoperand.ХxRegardlessoftheтunitsЁGсoptions, if``т-с'_appMоearsafter`т(с'orafter`т+с'thenitwillactasanegationopMоerator.њЪSoyВ!ouЁGcanђalwВ!aysёcompute20degreesminВ!us12minВ!utesbyёentering`т20ПЊdegreesІf+-12arcminс'.ЁGYџeouГ/mВ!ustusethisconstructionwhenyoude nenewunitsbMоecauseyoucannotknowwhatЁGoptionsІfwillbMоeinforcewhenyВ!ourde nitionisprocessed.)oGыS6 ИQNonlinearzГUnitConџuТversions&ЮлGсNonlinearc7unitsarerepresenВ!tedusingfunctionalc8notation.PTheymakepMоossiblenonlinearЁGunitІfconВ!versionssuchastempMоerature.
УMђ GсUnitsІfConВ!versionTd13 33 § ЬЭGы\6.1TўІfemps3eraturef@ConЬversions33GсConВ!versionsїbMоetweenіtemperaturesїaredi erenВ!tіfromlinearconversionsіbMоetweentempMоera-Є
33GtureБtфincrџpЙementsс|seeБstheexamplebMоeloВ!w.7TheabsolutetempMоeratureconВ!versionsareБthandledЁGbВ!yзкunitsstartingwith`тtempс',$6andyoumustusefunctionalзйnotation.r9ThetempMоerature-ЁGincremenВ!t conversionsaredoneusingunitsstarting with`тdegс'andtheydonotrequireЁGfunctionalІfnotation.ЉGЏ.љтYouПЊhave:tempF(45)Ё.љYouПЊwant:tempCЁ\іь7.2222222ff.љYouПЊhave:45degFЁ.љYouПЊwant:degCЁ\іь*ПЊ25Ё\іь/ПЊ0.04nЎGсThinkФ+of`тtempF(шxт)с'Ф*notasafunctionbutasanotationthatindicatesthatхx
сshouldhaВ!veЁGunitsя\ofя[`тtempFс'attacВ!hedtoit.ИНSeeSection10.3[De ningNonlinearUnits],page27.ИОTheЁG rst№їconВ!version№јshowsthatifit's№ј45degreesFџeahrenheitoutside,@it's7.2degreesCelsius.ЁcTheЁGsecond<љconВ!versionindicatesthat<јachangeof45degreesFџeahrenheit<јcorrespMоondstoachangeЁGofІf25degreesCelsius.ннTheconВ!versionІffrom`тtempF(шxт)с'istoabsolutetempMоerature,sothatІ.љтYouПЊhave:tempF(45)Ё.љYouПЊwant:degRЁ\іь*ПЊ504.67Ё\іь/ПЊ0.00198149299сHGсgivВ!esІfthesameresultasІ.љтYouПЊhave:tempF(45)Ё.љYouПЊwant:tempRЁ\іь*ПЊ504.67Ё\іь/ПЊ0.00198149299сGGсButІfifyВ!ouconvert`тtempF(шxт)с'to`тdegCс',theoutputisprobablynotwhatyouexpMоect:І.љтYouПЊhave:tempF(45)Ё.љYouПЊwant:degCЁ\іь*ПЊ280.37222Ё\іь/ПЊ0.00356668719сHGсTheqъresultisthetempMоeratureinqыK,because`тdegCс'isde nedas`тKс',|itheKelvin.Ь_Fџeorconsis-ЁGtenВ!t6wresults,Lйusethe6v`тtempшXс'unitswhenconВ!vertingto6watempMоeratureratherthanconВ!vertingЁGaІftempMоeratureincremenВ!t.GЎ!GTheје`тtempC()с'and`тtempF()с'de nitionsјжarelimitedtopMоositivВ!eabsolutetemperatures,ЁGandаgivingЯavџdDaluethatwВ!ouldresultinanegativВ!eabsolutetempMоeraturegeneratesanerrorЁGmessage:І.љтYouПЊhave:tempC(-275)Ё Ёђф^Ё.љArgumentПЊoffunctionoutsidedomainЁ Ёђф^ аoђ GсUnitsІfConВ!versionTd14 33 § ЬЭGы\6.2Otherf@NonlinearUnits33GсSomeЮotherЮ
examplesofnonlinearunitsarenВ!umerousdi erentЮringsizesandwiregauges,Є
33GtheРфgritsizesusedforabrasivВ!es,ЧthedecibMоelscale,shoMоesize,scalesforthedensitВ!yofsugarЁG(e.g.,ч3baume).
F2Thesзstandardsиdata lealsosuppliesunitsforcomputingtheareaofaЁGcircleјяandјюthevВ!olumeofasphere.еvSeethestandardunitsdata leformoredetails.еwWireЁGgaugesљЇwithmВ!ultiplezeroMоesaresigni edusingnegativenumbMоerswheretwozeroMоesis`т-1с'.ЁGAlternativВ!elyџe,ЋЯyouwcanusethesynonВ!yms`тg00с',ЋЮ`тg000с',andsoonthatarede nedintheЁGstandardІfunitsdata le.Љi.љтYouПЊhave:wiregauge(11)Ё.љYouПЊwant:inchesЁ\іь*ПЊ0.090742002Ё\іь/ПЊ11.020255Љff.љYouПЊhave:brwiregauge(g00)Ё.љYouПЊwant:inchesЁ\іь*ПЊ0.348Ё\іь/ПЊ2.8735632І.љYouПЊhave:1mmЁ.љYouПЊwant:wiregaugeЁ\іь18.201919І.љYouПЊhave:grit_P(600)Ё.љYouПЊwant:grit_ansicoatedЁ\іь342.76923 цEGсTheђZlastexampleshoВ!wstheconversionfromPђFgradedsandpapMоer,WwhichistheEuropMоeanЁGstandardІfandmaВ!ybMоemarked\P600"ontheback,totheUSAstandard.І!GYџeouЫcancomputetheareaofacircleЪusingthenonlinearunit,(ф`тcircleareaс'. YoucanЁGalso!ўdo!џthisusingthecircularincВ!horcircleincВ!h. PІThenextexampleshoВ!wstwo!џwaystoЁGcomputeйtheareaofaкcirclewitha vВ!einchradiusandonewayкtocomputethevolumeofЁGaІfspherewitharadiusofonemeter.І.љтYouПЊhave:circlearea(5in)Ё.љYouПЊwant:in2Ё\іь*ПЊ78.539816Ё\іь/ПЊ0.012732395Љff.љYouПЊhave:10^2circleinchЁ.љYouПЊwant:in2Ё\іь*ПЊ78.539816Ё\іь/ПЊ0.012732395І.љYouПЊhave:spherevol(meter)Ё.љYouПЊwant:ft3Ё\іь*ПЊ147.92573Ё\іь/ПЊ0.0067601492 к?ђ GсUnitsІfConВ!versionTd15 33 § ЬЭGThe
+inВ!verse
,ofanonlinearconВ!versionisindicated
,bypre xinga
,tilde(`т~с')tothenonlinearЄ
33GunitІfname:ЉK.љтYouПЊhave:~wiregauge(0.090742002inches)Ё.љYouПЊwant:Ё\іьDefinition:ПЊ11+БGсYџeouЖ|cangivВ!eЖ{anonlinearunitde nitionwithoutanargumenВ!torparenВ!theses,њandpressЁGтEnterУ
сatУ the`тYouІfwant:с'?? prompttogetthede nitionofanonlinearunit;б\ifthede nitionЁGisEнnotvџdDalidforallrealnВ!umbMоers,Y,theEнrangeofvaliditВ!yisalsogiven.НЏIfthede nitionrequiresЁGspMоeci cІfunitsthisinformationisalsodisplaВ!yed:L.љтYouПЊhave:tempCЁ\іьDefinition:ПЊtempC(x)=xK+stdtempЁ ЁђфdefinedПЊforx>=-273.15Ё.љYouПЊhave:~tempCЁ\іьDefinition:ПЊ~tempC(tempC)=(tempC+(-stdtemp))/KЁ ЁђфdefinedПЊfortempC>=0KЁ.љYouПЊhave:circleareaЁ\іьDefinition:ПЊcirclearea(r)=pir^2Ё ЁђфrПЊhasunitsmzFуGсTџeoseethede nitionoftheinВ!verseusethe`т~с'notation.ў>InthiscasetheparameterinЁGtheМfunctionalЛde nitionwillusuallybMоethenameoftheunit.УоNotethattheinВ!verseМforЁG`тtempCс'CshoВ!wsthatitrequiresunitsof`тKс'inCthespMоeci cationoftheallowedrangeofvџdDalues.ЁGNonlinearxQunitxRconВ!versionsarexRdescribMоedinmoredetailinSection10.3[De ningNonlinearЁGUnits],Іfpage27."є0GыS7 ИQUnitzГLists:ConџuТversiontoSumsofUnits Ё|GсOutsideбoftheвSI,itissometimesdesirabletoconВ!vertбasingleunittoasumofunits|ЁGforvexample,,:feettofeetplusincВ!hes. TheconversionфfrџpЙomшсsumsofunitswasdescribMоedinЁGSectionц5.2ч[SumsandDi erencesofUnits],9Gpage8,9FandisasimplematterofaddingtheЁGunitsІfwiththe`т+с'sign:І.љтYouПЊhave:12ft+3in+3|8inЁ.љYouПЊwant:ftЁ\іь*ПЊ12.28125Ё\іь/ПЊ0.0814249368FхGсAlthoughVyВ!oucanVsimilarlywriteasumofunitstoconВ!vertфtoс,theVresultwillnotbMоetheЁGconВ!versionhktohltheunitsinthesum,эbutrathertheconВ!versionhktotheparticularsumthatЁGyВ!ouІfhaveentered:І.љтYouПЊhave:12.28125ftЁ.љYouПЊwant:ft+in+1|8inЁ\іь*ПЊ11.228571Ё\іь/ПЊ0.0890585248FфGсThelunitexpressiongivВ!enkatthe`тYouІfwant:с'>эфpromptisequivџdDalentktoaskingforconversionЁGtoЏ8mВ!ultiplesЏ7of`т1ПЊftІf+1in+1|8inс',рЇwhicВ!hЏ8is1.09375Џ7ft,рЈsotheЏ8conversioninЏ7thepreviousЁGexampleІfisequivџdDalenВ!tto тђ GсUnitsІfConВ!versionTd16 33 § ЬЭ.љтYouПЊhave:12.28125ftЄ
33.љYouПЊwant:1.09375ftЁ\іь*ПЊ11.228571Ё\іь/ПЊ0.0890585248GсIn5лconВ!vertingto5мasumofunitslikВ!emiles,YИfeetandincВ!hes,YИyoutypically5мwantthelargestЄ
33GinВ!tegralМvџdDalueМforthe rstunit,СfolloВ!wedМbytheМlargestintegralМvџdDalueforthenext,СandtheЁGremainderпconВ!vertedtothelastunit.)HYџeoucandothisconversioneasilywithтunitsсusingЁGaќuspMоecialsynВ!taxќtforlistsofunits.р YџeoumustlistќtthedesiredunitsinorderfromlargesttoЁGsmallest,ІfseparatedbВ!ythesemicolon(`т;с')character:Љ .љтYouПЊhave:12.28125ftЁ.љYouПЊwant:ft;in;1|8inЁ\іь12ПЊft+3in+3|8in*цgGсThehconВ!versionialwaysgivesiintegercoMоecientsonitheunitsinthelist,hexceptpMоossiblytheЁGlastІfunitwhentheconВ!versionІfisnotexact:І.љтYouПЊhave:12.28126ftЁ.љYouПЊwant:ft;in;1|8inЁ\іь12ПЊft+3in+3.00096*1|8in*цgGсTheІforderinwhicВ!hyoulisttheunitsisimpMоortant:І.љтYouПЊhave:3kgЁ.љYouПЊwant:oz;lbЁ\іь105ПЊoz+0.051367866lbff.љYouПЊhave:3kgЁ.љYouПЊwant:lb;ozЁ\іь6ПЊlb+9.8218858oz_Г3GсListingjouncesjbMоeforepoundsproducesajtecВ!hnicallycorrectresult,butnotavВ!eryusefulЁGone.Щ^YџeoumВ!ustlisttheunitsindescendingorderofsizeinordertogetthemostusefulЁGresult.І!GEnding3aunitlistwiththeseparator`т;с'4hasthesamee ectasrepMоeatingthelastunitЁGonБtheБlist,Дdso`тft;in;1|8Іfin;с'isequivџdDalenВ!tto`тft;in;1|8Іfin;1|8inс'.џsWithБtheexampleЁGabMоoВ!ve,ІfthisgivВ!esЉ.љтYouПЊhave:12.28126ftЁ.љYouПЊwant:ft;in;1|8in;Ё\іь12ПЊft+3in+3|8in+0.00096*1|8in*цfGсinЉe ectseparatingЊtheinВ!tegerandfractionalpartsofthecoMоecienВ!tforthelastunit.IfyВ!ouЁGinsteadЮЫprefertoroundthelastcoMоecienВ!ttoanintegeryoucandothiswiththeт--roundЁGс(т-rс)Іfoption.ннWiththepreviousexample,theresultisІ.љтYouПЊhave:12.28126ftЁ.љYouПЊwant:ft;in;1|8inЁ\іь12ПЊft+3in+3|8in(roundeddowntonearest1|8in)*цfGсWhenyВ!ouusetheт-rсoption,Ф~repMоeatingthelastunitonthelisthasnoe ect(e.g.,Ф`тft;in;1|8ЁGin;1|8Іfinс'
isequivџdDalenВ!tto
`тft;in;1|8inс'),,andhenceneitherdoMоesendinga
listwitha`т;с'.ЁGWithw*aw+singleunitandtheт-rсoption,aterminal`т;с'фdoџpЙes]CсhaВ!vew*ane ect:Ц@itcausesтunitsсtoЁGtreat)thesingle(unitasalistandproMоducearoundedvџdDalueforthesingleunit.бШWithoutthe эЛђ GсUnitsІfConВ!versionTd17 33 § ЬЭGextra83`т;с',\Ѕtheт-rсoptionhasno82e ectonsingleunitconВ!versions.DThisexample83showstheЄ
33GoutputІfusingtheт-rсoption:ЉX.љтYouПЊhave:12.28126ftЁ.љYouПЊwant:inЁ\іь*ПЊ147.37512Ё\іь/ПЊ0.0067854058ff.љYouПЊhave:12.28126ftЁ.љYouПЊwant:in;Ё\іь147ПЊin(roundeddowntonearestin)nОяGсEacВ!hЮ unitЮ thatappMоearsinthelistmВ!ustbMоeconformablewiththe rstunitonthelist,и andЁGofаИcoursethelistedunitsmВ!ustalsobMоeconformableаЗwiththeunitthatyouenterattheЁG`тYouІfhave:с'MpЙprompt.І.љтYouПЊhave:meterЁ.љYouПЊwant:ft;kgЁyЕ>^Ё.љconformabilityПЊerrorЁ\іьftПЊ=0.3048mЁ\іьkgПЊ=1kg\fe.љYouПЊhave:meterЁ.љYouПЊwant:lb;ozЁ.љconformabilityПЊerrorЁ\іь1ПЊmЁ\іь0.45359237ПЊkgG%VGсInFrtheFq rstcase,nuтunitsсrepMоortsthedisagreemenВ!tbMоetweenFrunitsappearingFqonthelist.О InЁGtheЃїsecondcase,ЄsтunitsсrepMоortsdisagreemenВ!tbetВ!weenЃїtheunityВ!ouenteredandthedesiredЁGconВ!version.ннThisІfconformabilityerrorisbasedonthe rstunitontheunitlist.І!GOtherІfcommoncandidatesforconВ!versionІftosumsofunitsareanglesandtime:І.љтYouПЊhave:23.437754degЁ.љYouПЊwant;deg;arcmin;arcsecЁEјD23ПЊdeg+26arcmin+15.9144arcsec4ЬЬ.љYouПЊhave:7.2319hrЁ.љYouПЊwant:hr;min;secЁEјD7ПЊhr+13min+54.84sec,О№GсInЇ
NorthAmerica,ч2recipMоesforcookingtВ!ypicallyЇ measureingredientsbyvolume,ч2anduseЁGunitsъthatъarenotalwВ!aysъconvenientmultiplesъofeachother.Њ6SuppMоosethatyouъhaveaЁGrecipMоeќcfor6andyВ!ouwishtomakeapMоortionfor1.пдIftherecipecallsfor21/2cupsofanЁGingredienВ!t,^ you9Omightwishtoknowthe9PmeasurementsintermsofmeasuringdevicesyouЁGhaВ!veІfavџdDailable,youcoulduseтunitsсandenterІ.љтYouПЊhave:(2+1|2)cup/6Ё.љYouПЊwant:cup;1|2cup;1|3cup;1|4cup;tbsp;tsp;1|2tsp;1|4tspЁ\іь1|3ПЊcup+1tbsp+1tsp љwђ GсUnitsІfConВ!versionTd18 33 § ЬЭGByм9default,)Ўifaм:unitinalistbMоeginswithfractionoftheform1т|хxсanditsmВ!ultiplierisЄ
33GanЅinВ!teger,фЇthefractionisgivenastheproMоductЅ ofthemultiplierandthenumerator;$NforЁGexample,ЉИR.љтYouПЊhave:12.28125ftЁ.љYouПЊwant:ft;in;1|8in;Ё\іь12ПЊft+3in+3|8in+ ЙGсInЉmanВ!yЉcases,ЉЏsuchasЉtheexampleabMоoВ!ve,ЉЏthisisЉwhatiswВ!anted,ЉЏbutsometimesЉitisnot.ЁGFџeorxbexample,acoMоokingxarecipexbfor6mighВ!tcallfor51/4cupofaningredienВ!t,butyouxbwantЁGaІfpMоortionfor2,andyВ!our1-cupmeasureisnotavџdDailable;youmighttryІ.љтYouПЊhave:(5+1|4)cup/3Ё.љYouПЊwant:1|2cup;1|3cup;1|4cupЁ\іь3|2ПЊcup+1|4cup+ ИGсThisЯПresultmighВ!tbMоe neforabakerЯРwhohasa11/2-cupmeasure(andrecognizestheЁGequivџdDalence), butnitmaВ!ynotbMоenasusefultosomeonewithmorelimitedsetofmeasures,ЁGwhoнмdoMоeswВ!antнмtodoadditionalcalculations,+ИandonlywВ!antsнмtoknoВ!w\Howmany1/2-ЁGcup
measures toIЌneedtoadd?" ШAfterall,jrthat'swhatwВ!asactuallyaskВ!ed. ЧWiththeЁGт--show-factor~ сoption,Дthe~!factorwillnotbMоecomВ!binedwithaunitВ!ynumerator,Дso~ thatЁGyВ!ouІfgetІ.љтYouПЊhave:(5+1|4)cup/3Ё.љYouПЊwant:1|2cup;1|3cup;1|4cupЁ\іь3ПЊ*1|2cup+1|4cup+ ЙGсA|Ѕuser-spMоeci ed|№fractionalunitwith|ёanВ!umeratorotherthan1isnevВ!eroverridden,Иnhowever|ЁGifGТaunitlistspMоeci es`т3|4Іfcup;1|2cupс',paGТresultequivџdDalenВ!tto11/2cupswillalwaysbMоeЁGshoВ!wnІfas`т2*3|4ПЊcupс'whetherornottheт--show-factorсoptionisgiven.І!GSomepЦapplicationspХforunitlistsmaВ!ybMоelessobvious.<ќSuppMоosepХthatyouhavepХapMоostalЁGscale candwish btoensurethatit'saccurateat1oz,8ЪbuthaВ!ve conlymetriccalibrationwВ!eights.ЁGYџeouІfmighВ!ttryІ.љтYouПЊhave:1ozЁ.љYouПЊwant:100g;50g;20g;10g;5g;2g;1g;Ё\іь20ПЊg+5g+2g+1g+0.34952312*1gЉ+ ИGсYџeouюmighВ!tthenplaceoneeachяofthe20g,l5g,m2g,and1gяwВ!eightsюonthescaleandhopMоeЁGthatІfitindicatesclosetoИS.љтYouПЊhave:20g+5g+2g+1gЁ.љYouПЊwant:oz;Ё\іь0.98767093ПЊozІGсAppMоendingЅн`т;с'to`тozс'forcesaЅоone-linedisplaВ!ythatincludestheunit;І heretheintegerpartЁGofІftheresultiszero,soitisnotdisplaВ!yed.ЄИR!GAІfunitlistsucВ!hasЁ.љтcup;1|2ПЊcup;1|3cup;1|4cup;tbsp;tsp;1|2tsp;1|4tspИSGсcanчIbMоeчJtedioustoenВ!ter. TheтunitsсprogramproВ!videsshorthandnamesforsomecommonЉ
33GcomВ!binations:Ё.љтhms3Мњсhours,ІfminВ!utes,secondsІ.љтdms3Мњсangle:Іfdegrees,minВ!utes,seconds ђ GсUnitsІfConВ!versionTd19 33 § ЬЭ.љтtime-§PсyВ!ears,Іfdays,hours,minutesandsecondsЄ
33.љтusvol(=ІсUSІfcoMоokingvВ!olume:cupsandsmallerЉ&gGUsingІftheseshorthands,orхunitlistaliasesс,yВ!oucandothefollowingconversions:&f.љтYouПЊhave:anomalisticyearЁ.љYouПЊwant:timeЁ\іь1ПЊyear+25min+3.4653216secЁ.љYouПЊhave:1|6cupЁ.љYouПЊwant:usvolЁ\іь2ПЊtbsp+2tspV&fGсYџeou&йcannot&иcomВ!bineaunitlistaliaswithotherunits: оТitmВ!ustappMоearaloneattheЁG`тYouІfwant:с'MpЙprompt.І!GYџeouДtcandisplaВ!yДuthede nitionofaunitlistaliasbВ!yenteringitatДuthe`тYouІfhave:с'=!єprompt:Љ&f.љтYouПЊhave:dmsЁ\іьDefinition:ПЊunitlist,deg;arcmin;arcsec!YGсWhenaЪyВ!ouaЩspMоecifycompactoutputwithт--compactс,oт--terseсorт-tсandpMоerformconВ!versionЁGto/aunit/list,ШтunitsсliststheconВ!version/factorsforeacВ!hunitinthelist,ШseparatedbВ!yЁGsemicolons.І.љтYouПЊhave:yearЁ.љYouПЊwant:day;min;secЁ.љ365;348;45.974678.ЭGсUnlikВ!eІfthecaseofregularoutput,zerosфarџpЙeyсincludedinthisoutputlist:&g.љтYouПЊhave:literЁ.љYouПЊwant:cup;1|2cup;1|4cup;tbspЁ.љ4;0;0;3.6280454DLЭGыS8 ИQLoggingzГCalculations( ЮGсTheУФт--logсoptionalloВ!wsyouУУtosavetheresultsofcalculationsina le;вrthiscanbMоeusefulЁGifЎцyВ!ouЎчneedapMоermanenВ!trecordofyВ!ourwork.ї^FџeorЎцexample,ёthe
uid-
oВ!wconversionЎцinЁGSectionчф5.6чу[ComplicatedUnitExpressions],8Bpage11,islengthВ!yџe,8CandчуifyouwereчуtouseЁGitUНindesigningapipingsystem,yВ!oumightwantarecordofitforthepro Лject le.ытIftheЁGinВ!teractiveІfsessionІ.љт#ПЊConversionfactorA1forpressuredropЁ.љ#ПЊdP=A1rhofLQ^2/d^5Ё.љYouПЊhave:(8/pi^2)(lbm/ft^3)ft(ft^3/s)^2(1/in^5)#InputunitsЁ.љYouПЊwant:psiЁ\іь*ПЊ43.533969Ё\іь/ПЊ0.022970568V&fGсwВ!ereІflogged,thelog lewouldcontain ђђ GсUnitsІfConВ!versionTd20 33 § ЬЭ.љт###ПЊLogstartedFriOct0215:55:352015ff.љ#ПЊConversionfactorA1forpressuredropЄ
33.љ#ПЊdP=A1rhofLQ^2/d^5Ё.љFrom:ПЊ(8/pi^2)(lbm/ft^3)ft(ft^3/s)^2(1/in^5)>ў#InputunitsЁ.љTo:>ўpsiЁ\іь*ПЊ43.533969Ё\іь/ПЊ0.022970568m]нGсTheІftimeiswrittentothelog lewhenthe leisopMоened.Љїx!GThe2єuseofcommenВ!tscan2ѓhelpclarifythemeaningofcalculationsforthelog. TheЄ
33Glogб$includesб#conformabilitВ!yerrorsbMоetweentheб#unitsatthe`тYouІfhave:с'A[Sand`тYouІfwant:с'ЁGprompts,Пbut
гnotothererrors,includinglacВ!kof
дconformabilityofitemsinsumsordi erencesЁGor#Damong#Eitemsinaunitlist.В'Fџeorexample,=~aconВ!version#DbMоetweenzenithangle#EandelevџdDationЁGangleІfcouldinВ!volveІ.љтYouПЊhave:90deg-(5deg+22min+9sec)Ё ј-к^Ё.љIllegalПЊsumordifferenceofnon-conformableunitsЁ.љYouПЊhave:90deg-(5deg+22arcmin+9arcsec)Ё.љYouПЊwant:dmsЁ\іь84ПЊdeg+37arcmin+51arcsecЁ.љYouПЊhave:_Ё.љYouПЊwant:degЁ\іь*ПЊ84.630833Ё\іь/ПЊ0.011816024Ё.љYouПЊhave: їvGсTheІflog lewВ!ouldcontainІ.љтFrom:ПЊ90deg-(5deg+22arcmin+9arcsec)Ё.љTo:>ўdeg;arcmin;arcsecЁ\іь84ПЊdeg+37arcmin+51arcsecЁ.љFrom:ПЊ_Ё.љTo:>ўdegЁ\іь*ПЊ84.630833Ё\іь/ПЊ0.011816024`*ЊGсTheрinitialрenВ!tryerror(forgettingthatminВ!uteshavedimensionрoftime,НandthatarcminВ!utesЁGmВ!ustКbMоeКusedfordimensionsofangle)doMоesnotappMоearintheoutput.юWhenconВ!vertingКtoЁGaІfunitlistalias,тunitsсexpandsthealiasinthelog le.їw!GThe"l`тFrom:с'"mand`тTo:с'tagsarewrittentothelog leevВ!eniftheт--quietсoptionisgivВ!en.ЁGIf_the_log leexistswhenтunitsсisinВ!voked,.the_newresultsareappMоendedtothelog le.ЁGThe_оtime_пiswrittentothelog leeacВ!htimethe leisopMоened.ЦZTheт--logсoptionisignoredЁGwhenІfтunitsсisusednon-inВ!teractivelyџe.#GыS9 ИQInџuТvokingzГыVunits GсYџeouІfinВ!vokeтunitsсlikethis: бђ GсUnitsІfConВ!versionTd21 33 § ЬЭ.љтunitsПЊ[шoptionsт][шfrom-unitт[шto-unitт]]ЉzтGсIf$@the$Aхfrom-unita@сandхto-unitсare$@omitted,CЗtheprogramwilluseinВ!teractiveprompts$Atode-Є
33GtermineЄќwhicВ!hconversionsЄћtopMоerform.йSeeChapter2[InВ!teractiveЄќUse],фЁpage1.йIfbMоothЁGхfrom-unitВсandLБхto-unitсareLВgivВ!en,vDтunitsсwillprinttheLБresultofthatsingleconВ!versionLВandЁGthen]exit.ХIfonly]хfrom-unitсappMоearsonthecommandline,l"тunitsсwilldisplaВ!ythede nitionЁGofУ}thatУ~unitandexit.5#UnitsspMоeci edonthecommandlinemaВ!yneedtobMоequotedtopro-ЁGtectМЧthemМШfromshellinВ!terpretationandtogrouptheminВ!totwoarguments.!SeeМШChapter3ЁG[CommandІfLineUse],page4.І!GThe adefaultbMоehaВ!vior `ofтunitsсcanbe `cВ!hangedbyvџdDariousoptionsgiven `onthecommandЁGline.ЛRIn>Чmost>Цcases,StheoptionsmaВ!ybMоegivenineithershortform(a>Чsingle`т-с'followedbyaЁGsingle|cВ!haracter)orlongform(`т--с'|followedbyawordorhyphen-separatedwords).ЯУShort-ЁGformnsoptionsnrarecrypticbutrequirelesstВ!yping;long-formoptionsrequiremoretВ!ypingbutЁGareЕrmoreЕqexplanatoryandmaВ!ybMоemoremnemonic. Withlong-formoptionsyВ!ouneedonlyЁGenВ!terЗ{sucientcharacterstouniquelyidentifytheoptionЗztotheprogram. Fџeorexample,ЁG`т--outПЊ%fс'ЮvwВ!orks,и{but`т--o%fс'failsЮwbMоecauseтunitsсhasotherlongoptionsbMоeginningwithЁG`тoс'.ннHoВ!wever,Іf`т--qс'wВ!orksbMоecause`т--quietс'istheonlylongoptionbeginningwith`тqс'.zу!GSome=ќoptionsrequire=§argumenВ!tstospMоecifyavџdDalue(e.g.,Ѓс`т-dПЊ12с'or`т--digits12с').ЁGShort-formЋoptionsЌthatdonottakВ!eargumentsЋmaybMоeЋconcatenated(e.g.,j`т-erSс'isequiv-ЁGalenВ!tфђtoфѓ`т-eПЊ-r-Sс');8thelastoptionфѓinsucВ!halistmaВ!ybMоeonethattakВ!esanargumenВ!tЁG(e.g.,\O`т-edПЊ12с').tWith7юshort-formoptions,thespacebMоetВ!ween7эan7юoptionanditsargumenВ!tЁGis _optional(e.g.,; `т-d12с'isequivџdDalenВ!tto`т-dПЊ12с').BЩLong-formoptionsmay `notbMоeconcate-ЁGnated,ЃPandЂthespacebMоetВ!weenЂalong-formЂoptionanditsargumenВ!tisrequired.мShort-formЁGandЩlong-formoptionsЩmaВ!ybMоeintermixedontheЩcommandline.EѓOptionsmaВ!ybMоegivenЁGin
ўanВ!yorder,ybutwhenincompatible
џoptions(e.g.,т--output-formatсandт--exponentialс)ЁGareкIgivВ!eninкHcombination,'AbMоehavioriscontrolledbyкHthelastoptiongiven.y
Fџeorexample,ЁG`т-o%.12fПЊ-eс'ІfgivВ!esexpMоonentialformatwiththedefaulteightsigni cantdigits).І!GTheІffolloВ!wingoptionsareavџdDailable: КGт-cЁG--checkMсChecВ!k.that-allunitsandpre xesde nedintheunitsdata lereducetoprimitivВ!eЁKт:units.иЧPrinВ!t$a%listofallunitsthatcannotbMоereduced.иЧAlsodisplaВ!ysomeotherЁKт:diagnosticsЬЬabMоoutЬЭsuspiciousde nitionsintheunitsdata le.QOnlyde nitionsЁKт:activВ!e!№inthe!ёcurrentloMоcalearechecked.БЖYџeoushouldalwaysrun!ётunitsсwiththisЁKт:optionІfaftermoMоdifyingaunitsdata le.ЉzтGт--check-verboseЁG--verbose-checkЁKт:сLikВ!ed theт--checkd сoption,thisoptionprintsad listofunitsthatcannotbMоere-ЁKт:duced.[_Butzцtozчhelp ndunitde nitionsthatcauseendlessloMоops,АitliststheЁKт:unitsЊastheyarecВ!hecked.шѕIfЊтunitsсhangs,ЋthenthelastЊunittobMоeprinВ!tedhasЁKт:aІfbadde nition.ннOnlyde nitionsactivВ!einthecurrentloMоcalearechecked.ІGт-dІfшndigitsЁGт--digitsІfшndigitsЁKт:сSetRtheQnВ!umbMоerofsigni cantQdigitsintheoutputtothevџdDaluespMоeci ed(whicВ!hЁKт:mВ!ust# bMоegreaterthan# zero).ВFџeorexample,=Q`т-dПЊ12с'setsthenВ!umbMоer# ofsigni canВ!tЁKт:digitscttocu12.WithexpMоonenВ!tialoutputтunitsсdisplayscuonedigittotheleftof !-ђ GсUnitsІfConВ!versionTd22 33 § ЬЭKт:the decimalpMоoinВ!tќОЎ2 сandelevendigitstothe rightofthedecimalpMоoint. FtOnЄ
33Kт:mostЖуsystems,ћthemaximВ!umnumbMоerЖтofinternallymeaningfuldigitsЖтis15;?!ifЁKт:yВ!ou&spMоecify'agreaternВ!umbMоer&thanyВ!oursystem'smaximВ!um,ЭтunitsсwillprinВ!taЁKт:wВ!arning
andsetthenumbMоertothelargestmeaningfulvџdDalue.Ј=TџeodirectlysettheЁKт:maximВ!umh(vџdDalue,tgiveanargumenth'ofтmaxс(e.g.,t`т-dПЊmaxс').Щ Beaware,tofcourse,ЁKт:thatхц\signi canВ!t"хчhererefersonlytotheфdisplayншсofnВ!umbMоers;ЇifresultsхцdependЁKт:onЂПphВ!ysicalЂРconstantsnotknownЂРtothisprecision,сеthephВ!ysicallymeaningfulЁKт:precision@кmaВ!ybMоe@йlessthanthatshown.МTheт--digitsсoption@йcon
ictswiththeЁKт:т--output-formatІfсoption.ЉчzGт-eЁG--exponentialЁKт:сSet!|the!{nВ!umericoutputformattoexpMоonenВ!tial(i.e.,Ascienti c!|notation),@likeЁKт:thatZDusedZEintheUnixтunitsсprogram.Ф|ThedefaultprecisioniseighВ!tsigni cantЁKт:digitse(sevВ!enedigitstotherighВ!tofthedecimalpMоoinВ!t);{*thiscanbeecВ!hangedwithЁKт:the&т--digitsсoption.ГETheт--exponentialсoptioncon
ictswiththeт--output-ЁKт:formatІfсoption.ІGт-oІfшformatЁGт--output-formatІfшformatЁKт:сThis
їoption
іa ordscompleteconВ!trolover
іthenumericoutputformat
іusingtheЁKт:spMоeci ed зхformatс..Theformat жisasingle
oatingpMоoinВ!tnumeric зformatfortheЁKт:тprintf()ЉХсfunctionЉЦintheCprogramminglanguage.чќAllcompilerssuppMоorttheЁKт:formatИєtВ!ypMоes`тgс'andИѕ`тGс'tospecifysigni canВ!tdigits,§`тeс'Иѕand`тEс'forscienti cЁKт:notation,н=and`тfс'for xed-pMоoinВ!tdecimal.ЧтTheISOгC99standardinВ!troMоducedЁKт:theDЄ`тFс'tВ!ypMоeDЃfor xed-poinВ!tdecimalandDЃthe`тaс'and`тAс'tВ!ypMоesforhexadecimalЁKт:
oatingПтpMоoinВ!t;ЬthesetypMоesareПсallowedwithcompilersПсthatsuppMоortthem.*PTheЁKт:defaultгрformatis`т%.8gс';jforgreaterprecision, >yВ!oucouldspMоecify`т-oПЊ%.15gс'.ЁKт:SeeљpChapter11[NumericOutputFџeormat],N2page31,andthedoMоcumenВ!tationЁKт:formтprintf()сformoreldetaileddescriptionsoftheformatspMоeci cation.ёTheЁKт:т--output-format;сoptionEсandЁKт:itsЌmВ!ultiplierЌisanintegerotherЌthan1,Ў,thefractionisgivВ!enastheproMоductofЁKт:theШмmВ!ultiplierШлandthenumerator(e.g.,бy`т3|8ПЊinс'Шлratherthan`т3Іf*1|8inс').E>InЁKт:some0cases,S thisisnot0whatiswВ!anted;uЊfor0example,theresultsfor0acoMоokingЁKт:recipMоedўmighВ!tdџshow`т3Іf*1|2ПЊcupс'dџas`т3|2cupс'.ЇWiththedџт--show-factorсop-ЁKт:tion,oaGXresultGYequivџdDalenВ!tto1.5cupswilldisplaВ!yas`т3Іf*1|2ПЊcupс'ratherGXthanЁKт:`т3|2ПЊcupс'.ЎзA{user-spMоeci edКfractionalЙunitwithanВ!umeratorotherthan1isЁKт:nevВ!erVЬoverridden,хhowever|ifaunitVЭlistspMоeci es`т3|4Іfcup;1|2cupс',хaresultЁKт:equivџdDalenВ!tѕto1і1/2cupswillalwaysіbMоeshownas`т2Іf*3|4ПЊcupс'іwhetherѕornotЁKт:theІfт--show-factorсoptionisgivВ!en.ІGт-sЁG--strict гЃсSuppressЋЭconВ!versionofunitstotheirreciproMоcalunits.юFџeorexample,'тunitsсwillЁKт:normally\tconВ!verthertz\stosecondsbMоecausetheseunitsarereciproMоcalsofeacВ!hЁKт:other.нЈTheЅШstrictЅЧoptionrequiresthatunitsbMоestrictlyconformabletopMоerformЁKт:aћconВ!version,Dandwillќgiveanerrorifќyouattempttoconvertќhertztoseconds.Gт-1ЁG--one-lineЁKт:сGivВ!eRмonlyoneRлlineofoutput(theforwardRлconversion).ТDonotRлprintthereverseЁKт:conВ!version.Ь^IfK;aKandtheloMоcationofthepMоersonalunitsЁKт:dataІf le;indicateifthepMоersonalunitsdata ledoesnotexist. M^ђ GсUnitsІfConВ!versionTd25 33 § ЬЭKт:WhenЙ9givВ!eninЙ8combinationwiththeт--terseЙ8сoption,НюtheprogramЙ9printsonlyЄ
33Kт:theІfvВ!ersionnumbMоerandexits.ЉnKт:Whenд9givВ!enд8incombinationwiththeд8т--verboseсoption,_theprogram,theЁKт:т--versionІfсoptionhasthesamee ectastheт--infoсoptionbMоeloВ!w.ЉќGт-IЁG--infoRїсPrinВ!tДtheargumenВ!tisdimensionless),L?andthattheinВ!verseЄ
33GfunctionDHrequiresDIaninputargumenВ!tconformablewith`тKс'. ЗFџeornormalnonlinearunitsЁGde nition,нЫtheвЗforwВ!ardfunctionwillвЖalwaystakeadimensionlessargument;шпingeneral,нЫtheЁGinВ!verseЧяfunctionЧюwillneedunitsthatmatcВ!hthequantityЧюmeasuredbyyourЧюnonlinearunit.ЁGSpMоecifying$фtheunits$уenablesтunitsсtoperformerror$уcВ!hecking$фonfunctionargumenВ!ts,DandЁGalsoІftoassignunitstodomainandrangespMоeci cations,whicВ!haredescribedlater.Љ !GNextЌtheЋfunctionde nitionsappMоear.ћЎIntheexampleabMоoВ!ve,]}theЌ`тtempFс'functionisЁGde nedІfbВ!y.љтtempF(x)ПЊ=(x+(-32))degF+stdtempІGсThisпgivВ!esaрruleforconverting`тxс'intheрunits`тtempFс'tolinearunitsofabsolutetempMоera-ЁGture,ІfwhicВ!hmakesitpMоossibletoconvertfromtempFtootherunits.І!GTџeoVenableconВ!versionsVtoVFahrenheit,ЈyouVmustVgivearuleforVtheinverseconversions.ЁGThe@ЊinВ!verse@ЉwillbMоe`тx(tempF)с'anditsde nitionappMоearsaftera`т;с'cВ!haracter. ЌЈInourЁGexample,ІftheinВ!verseІfis.љтx(tempF)ПЊ=(tempF+(-stdtemp))/degF+32ІGсThis*\inВ!versede nition*]takesanabsolutetempMоeratureas*]itsargumentandconverts*]ittotheЁGFџeahrenheit tempMоerature. јThe inВ!versecanbMоe omittedbyleaving outthe`т;с'cВ!haracterandЁGtheљТinВ!versede nition,butthenconversionsљСфtoЊДсtheunitwillnotbMоepossible.з№IftheinВ!verseЁGde nition#Еisomitted,=иtheт--checkсoptionwilldisplaВ!yawarning.ВLItisuptoyoutocalculateЁGandОИenВ!terОЙthecorrectinverseОЙfunctiontoobtainpropMоerconВ!versions;Jсtheт--checkОИсoptionЁGtests чthe шinВ!verseat шonepMоoint шandprints шanerrorifitisnotvџdDalidthere,>GbutthisisnotaЁGguaranВ!teeІfthatyourinverseiscorrect.І!GWithІfsomede nitions,theunitsmaВ!yvџdDaryџe.ннForІfexample,thede nition.љтsquare(x)(=Іx^2ІGсcan EhaВ!ve Fanyarbitrary Funits,9НandcanalsotakВ!edimensionlessargumenВ!ts.?{Insuch Facase,ЁGyВ!ouПюshouldфnotЩисspMоecifyunits.*vIfade nitiontakesaroMоotofПяitsarguments,ЦPthede nitionisЁGvџdDalidІfonlyforunitsthatyieldsucВ!haroMоot.ннFџeorexample,І.љтsquirt(x)(=Іsqrt(x)ІGсisІfvџdDalidforadimensionlessargumenВ!t,andforargumentswithevenpMоowersofunits.!GSomeqњde nitionsmaВ!yqљnotbMоevџdDalidforallrealnВ!umbMоers.ЬdInqњsuchcases,|uтunitsсcanhandleЁGerrorsЇкbMоetterifyВ!ouspecifyЇйanappropriatedomainandrange.т9YџeouspMоecifythedomainandЁGrangeІfasshoВ!wnbMоelow:І.љтbaume(d)ПЊunits=[1;g/cm^3]domain=[0,130.5]range=[1,10]\ЁbЖ(145/(145-d))ПЊg/cm^3;(baume+-g/cm^3)145/baume Г3GсInфJthisexamplethedomainisspMоeci edфIafter`тdomain=с'withtheendpoinВ!tsgiveninbrackets.ЁGInУcaccordУdwithmathematicalconВ!vention,№ЪsquareУcbracketsindicateУcaclosedinВ!tervџdDal(onethatЁGincludesолitsendpMоoinВ!ts),ФandparenthesesindicateanopMоenintervџdDalом(onethatdoMоesnotincludeЁGitsџ endpMоoinВ!ts).чЪAnintervџdDalcanџ
bMоeopenorџ
closedononeorbMоothends;+]aninВ!tervџdDalthatisЁGunВ!bMоoundedYoneitherendisindicatedYbyomittingthelimitonthatend.їvFџeorexample,faЁGquanВ!tityЫtowhicВ!hdecibMоel(dB)Ы4isappliedmayЫhaveanyvџdDaluegreaterthanzero,ХsotheЁGrangeІfisindicatedbВ!y`т(0,)с':.љтdecibel(x)ПЊunits=[1;1]range=(0,)10^(x/10);10log(decibel)ІGсIfІfthedomainorrangeisgivВ!en,thesecondendpMоointmustbMоegreaterthanthe rst. Rђ GсUnitsІfConВ!versionTd29 33 § ЬЭ!GTheъmdomainandъlrangespMоeci cationscanappMоearindependenВ!tlyandinanyъlorderalongЄ
33GwithxtheyunitsspMоeci cation.Ќ8ThevџdDaluesforthedomainandrangeendpMоoinВ!tsareattacВ!hedtoЁGtheЛUunitsЛVgivВ!enintheunitsspMоeci cation,Рandifnecessaryџe,РtheparametervџdDalueisadjustedЁGforpcomparisonpwiththeendpMоoinВ!ts.<]Fџeorexample,Ѓifade nitionincludes`тunits=[1;ft]с'ЁGandw`тrange=[3,)с',ЋаthewrangewillbMоetakВ!enas3fttoin nitВ!yџe.QBIfthefunctionispassedaЁGparameterъ7of`т900Іfmmс'+dE,;+thatvџdDaluewillbMоeъ8adjustedto2.9527559ft,whicВ!hisoutsidetheЁGspMоeci edrange. IfyВ!ou omittheunitsspMоeci cationfromthepreviousexample,,nтunitsсcanЁGnotћЕtellwhetheryВ!ouћЖintendћЕtheloВ!werћЕendpMоointtobMоe3ћЖftor3microfurlongs, andcannotЁGadjustэtheьparametervџdDalueof900mmforcomparison.ФqWithoutunits,лЭnВ!umericalvџdDaluesЁGotherWBthanWCzeroorplusorminВ!usin nityforWCdomainorrangeendpMоoinВ!tsaremeaningless,ЁGand4љaccordinglythey4јarenotalloВ!wed. If4љyougive4јothervџdDalueswithoutunitsthentheЁGde nitionІfwillbMоeignoredandyВ!ouwillgetanerrormessage.ЉсЉ!GAlthoughBstheunits,Vpdomain,andBsrangespMоeci cationsareoptional,Vpit'sbesttogivВ!ethemЁGwhenБ#theyareБ$applicable;ЖdoingsoalloВ!wsтunitsсtopMоerformbettererrorБ$cВ!heckingБ#andgivВ!eЁGmore1ъhelpfulerrormessages.З
Givingthedomainandrangealso1ыenablestheт--checkсoptionЁGtoІf ndapMоoinВ!tinthedomaintouseforitspoinВ!tcheckofyourinversede nition.І!GYџeouЯЁcanmakВ!esynonymsЯЂfornonlinearunitsbyprovidingbMоothЯЂtheforwardandinverseЁGfunctions;sЎinВ!verseZSfunctionsZRcanbMоeobtainedusingthe`т~с'opMоerator.ФSotocreateasynonВ!ymЁGforІf`тtempFс'yВ!oucouldwriteІ.љтfahrenheit(x)ПЊunits=[1;K]tempF(x);~tempF(fahrenheit)сЊGсThisisusefulforcreatinganonlinearunitde nitionthatdi ersslighВ!tlyfromanexistingЁGde nitionІfwithouthaВ!vingtorepMоeattheoriginalfunctions.ннFџeorexample,І.љтdBW(x) ОRunits=[1;W]ПЊrange=[0,)dB(x)W; T~dB(dBW/W)ІGсIfyВ!ouwishasynonymtorefertoanexistingnonlinearunitwithoutmoMоdi cation,youcanЁGdoБ somoreБsimplybВ!yaddingthesynonВ!ymwithappMоendedparenthesesБasanewunit,ДnwithЁGtheЮ existingnonlinearЮ unit|withoutparenВ!theses|asthede nition.ХSotocreateasynonВ!ymЁGforІf`тtempFс'yВ!oucouldwriteІ.љтfahrenheit() TtempFІGсTheІfde nitionmВ!ustbMоeanonlinearunit;forexample,thesynonymІ.љтfahrenheit() TmeterІGсwillІfresultinanerrormessagewhenтunitsсstarts.сЊ!GYџeou%maВ!y%oMоccasionallywishtode neafunctionthatopMоeratesonunits.ВМThiscanbMоedoneЁGusingСaСnonlinearunitde nition.-кFџeorexample,Кthede nitionbMоeloВ!wprovidesСconversionЁGbMоetВ!weenі#radiusandі"theareaofacircle.ЭThisde nitionrequiresalengthasinputandЁGproMоduces
an
areaasoutput,+ВasindicatedbВ!ythe`тunits=с'spMоeci cation.ЊМSpecifyingthe
rangeЁGasІfthenonnegativВ!enumbMоerscanpreventcrypticerrormessages.І.љтcirclearea(r)ПЊunits=[m;m^2]range=[0,)>ўpir^2;sqrt(circlearea/pi) БGы\10.4De ningf@PiecewiseLinearUnits33GсSometimesyyВ!oumaybMоexinterestedinapiecewiselinearunitsuchxasmanywiregauges.ЁGPiecewise*?linearunitscanbMоede nedbВ!yspecifyingconВ!versions*?tolinearunitsonalistofЁGpMоoinВ!ts.ТConversionRїatRјotherpoinВ!tswillRїbedonebВ!yRїlinearinterpMоolation.ТARтpartialde nitionЁGofІfzincgaugeis Fђ GсUnitsІfConВ!versionTd30 33 § ЬЭ.љтzincgauge[in]ПЊ10.002,100.02,150.04,190.06,230.1ЉyіGсInўъthisўыexample, i`тzincgaugeс'isthenameofthepiecewiselinearunit.І Thede nitionofsucВ!hЄ
33GaыunitisъindicatedbВ!ytheembMоedded`т[с'ъcharacter.5lAfterthebracket,5youshouldindicateЁGtheкunitsк tobMоeattacВ!hedtothenВ!umbMоersкinthetable.xУNospacescanappMоearbeforeк the`т]с'ЁGcВ!haracter,)soade nitionlike`тfoo[kgІfmeters]с'isinvџdDalid;4insteadwrite`тfoo[kg*meters]с'.ЁGTheюУde nitionoftheunitconsistsofalistюФofpairsoptionallyseparatedbВ!ycommas.ЖєThisЁGlistDde nesaDfunctionforconВ!vertingDfromthepiecewiselinearunittolinearunits.НDThe rstЁGitemЭinЭeacВ!hpairisthefunctionargumenВ!t;с theseconditemisthevџdDalueofthefunctionatЁGthatбЮargumenВ!tбЭ(intheunitsspMоeci edinbracВ!kets).`InбЮthisexample,мЇwВ!ede ne`тzincgaugeс'ЁGat} vВ!epMоoints.aэFџeorexample,ВТweset`тzincgauge(1)с'equalto`т0.002Іfinс'6vx.aэDe nitionslikeЁGthisІfmaВ!ybMоemorereadableifwrittenusingcontinuationcharactersasyѕ.љтzincgauge[in]ПЊ\ЁKЗю1ПЊ0.002 T\ЁEјD10ПЊ0.02>ў\ЁEјD15ПЊ0.04>ў\ЁEјD19ПЊ0.06>ў\ЁEјD23ПЊ0.1RyѕGсWithІftheprecedingde nition,thefolloВ!wingconversioncanbMоeperformed:І.љтYouПЊhave:zincgauge(10)Ё.љYouПЊwant:inЁEјD*ПЊ0.02ЁEјD/ПЊ50Ё.љYouПЊhave:.01inchЁ.љYouПЊwant:zincgaugeЁEјD5_'GсIfZyВ!oude neZ apiecewiselinearunitthatisnotstrictlymonotonic,iHthentheinВ!verseZwillnotЁGbMоeЦwВ!ellХde ned."ќIftheinverseХisrequestedforsucВ!haunit,-нтunitsсwillreturnthesmallestЁGinВ!verse.І!GAfter Uaddingnonlinearunitsde nitions,|PyВ!oushouldnormallyrunтunitsІf--checkRпсtoЁGcВ!heck;forerrors.К=If;the`тunitsс'kВ!eyword;isnotgivВ!en,Pцtheт--checkсoptioncВ!hecks;anonlinearЁGunitПбde nitionПаusingadimensionlessargumenВ!t,Ц,andthencВ!hecksПбusinganarbitrarycomВ!bi-ЁGnation"ћofunits,B aswВ!ellasthe"њsquareandcubMоeofthatcombination;aEawarningisgivenifЁGanВ!yІfofthesetestsfail.ннFџeorexample,І.љтWarning:ПЊfunction
squirt(x)
definedas
sqrt(x)
ЁbЖfailedПЊforsometestinputs:ЁbЖsquirt(7(kgПЊK)^1):UnitnotarootЁbЖsquirt(7(kgПЊK)^3):Unitnotaroot8GсRunning стunitsІf--checkQф сwill сprinВ!tawarningifanon-monotonicpiecewiselinearunitisЁGencounВ!tered.вЧFџeor
$example,ЫtherelationshipbMоetweenANSI
coatedabrasivedesignationandЁGmeanІfparticlesizeisnon-monotonicinthevicinitВ!yof800grit:І.љтansicoated[micron]ПЊ\ЁKЗю.ПЊ..ЁEјD600ПЊ10.55\ЁEјD800ПЊ11.5\ЁEјD1000ПЊ9.5\ Ќлђ GсUnitsІfConВ!versionTd31 33 § ЬЭGRunningІfтunits--checkOя*сwВ!ouldІfgivetheerrormessageЄF*.љтTableПЊ
ansicoated
lacksuniqueinversearoundentry800ЁGсAlthoughtheinВ!verseisnotwВ!ellde nedinthisregion,нмit'snotreallyanerror.Щ^ViewingЄ
33GsucВ!hAerrorAmessagescanbMоetedious,UUandifthereareenoughofthem,UUtheycandistractfromЁGtrue(Аerrors.dМErrorcВ!hecking(Аfornonlinearunitde nitionscanbMоe(БsuppressedbВ!ygivingtheЁG`тnoerrorс'ІfkВ!eyword;fortheexamplesabMоove,thiscouldbMоedoneasЉF*.љтsquirt(x)ПЊnoerrordomain=[0,)range=[0,)sqrt(x);squirt^2Ё.љansicoated[micron]ПЊnoerror\ЁKЗю.ПЊ..,ЌGсUse*the`тnoerrorс'kВ!eyword*withcaution.ДgThesafestapproacВ!hafteraddinganonlinearunitЁGde nitionлєisлѓtorunтunitsІf--checkNZEсandcon rmthattherearenoactualerrorsbMоeforeaddingЁGtheІf`тnoerrorс'kВ!eyword. sGы\10.5De ningf@UnitListAliases33GсUnitЋлlistЋкaliasesaretreateddi erenВ!tlyfromunitde nitions,8bMоecausetheyareadataenВ!tryЁGshorthand5Фratherthanatrue5Хde nitionforanewunit.їA5 unitlistaliasde nitionbMоeginsЁGwithС`т!unitlistс'andРincludesthealiasandthede nition;<Ѓforexample,'{thealiasesincludedЁGinІfthestandardunitsdata leareІ.љт!unitlist>ўhms ОRhr;min;secЁ.љ!unitlist>ўtimeўЈyear;day;hr;min;secЁ.љ!unitlist>ўdms ОRdeg;arcmin;arcsecЁ.љ!unitlist>ўftinўЈft;in;1|8ПЊinЁ.љ!unitlist>ўusvolcup;3|4ПЊcup;2|3cup;1|2cup;1|3cup;1|4cup;\Ё Ёђфtbsp;tsp;1|2ПЊtsp;1|4tsp;1|8tspTF)GсUnitTlistSaliasesareonlyforunitlists,Оsothede nitionmВ!ustincludea`т;с'.йзUnitlistaliasesЁGcan оnevВ!er пbMоecombined пwithunitsorotherunitlistaliases,9њsothede nitionof`тtimeс'shoВ!wnЁGabMоoВ!veІfcouldфnotАPсhaВ!veІfbeenshortenedto`тyear;day;hmsс'.І!GAsbusual,5bMоesuretoarunтunitsІf--checkNе"сtoensurethattheunitslistedinunitlistaliasesЁGareІfconformable.&%юGыS11 ИQNumericzГOutputFўaGormat"lGсBySbdefault,~ тunitsсshoВ!wsresultstoSaeightsigni cantdigits.фаYџeoucanchangeSathiswiththeЁGт--exponentialс,qт--digitsс,randlет--output-formatlжсoptions.1,The rstsetsanexpMоonenВ!tialЁGformat
Н(i.e.,gscienВ!ti cnotation)
Мlikethat
МusedintheoriginalUnixтunitsсprogram,gtheЁGsecondТalloВ!wsТyoutoТspMоecifyadi erentТnumbMоerofТsigni cantdigits, andtheТlastallowsЁGyВ!ou ,to +controltheoutput +appMоearanceusingtheformatfortheтprintf()сfunctionintheCЁGprogramming
хlanguage.}ВIfyВ!ouonly
цwanttochangethenumbMоerofsigni cantdigitsorspMоecifyЁGexpMоonenВ!tialEћformattypMоe,mпusetheт--digitsEњсandт--exponentialсoptions.МTheт--output-ЁGformatїсoptiona ordstheїgreatestconВ!troloftheoutputappMоearance, ЦbutrequiresatleastЁGrudimenВ!tary knowledgeoftheтprintf()сformatsyntax.oSeeChapter9[InvokingUnits],ЁGpageІf20,fordescriptionsoftheseoptions. Й8ђ GсUnitsІfConВ!versionTd32 33 § ЬЭGы\11.1FўІformatf@Sps3eci cation33GсTheмformatspMоeci cationrecognizedwiththeнт--output-formatсoptionisasubsetofthatЄ
33Gfor,Ттprintf()с.ЕQTheformatspMоeci cationhastheformт%с[ф
ags цс][фwidth з с][т.фprџpЙecisionс]фtype вЁс;UNit,ТmВ!ustЁGbMоegin)Сwith`т%с',JandmВ!ust)Рendwitha
oating-poinВ!ttypMоe)Рspeci er:ф`тgс')Сor`тGс'tospMоecifytheЁGnВ!umbMоerOёofO№signi cantdigits,a;`тeс'O№or`тEс'forscienВ!ti cnotation,a;and`тfс'for xed-pMоoinВ!tdecimal.ЁGTheЂ§ISOЂќC99standardaddedthe`тFс'tВ!ypMоefor xed-poinВ!tdecimalandthe`тaс'and`тAс'typMоesЁGforѓЂhexadecimal
oatingpMоoinВ!t;@thesetypMоesareallowedwithcompilersthatsuppMоortthem.ЁGTВ!ypMоe!length"modi ers(e.g.,j`тLс'to"indicatealongdouble)areinapplicableandarenotЁGalloВ!wed.ЉтП!GThe§Qdefault§Rformatforтunitsсis`т%.8gс';ЈЦforgreaterprecision,г yВ!oucouldspMоecifyЁG`т-oПЊ%.15gс'.$5Theh`тgс'hand`тGс'formattВ!ypMоesuseexpMоonenВ!tialformatwhenevВ!ertheexpMоonenВ!tЁGwВ!ouldУJbMоeУKlessthanъ с4,ЪsothevџdDalue0.000013displaВ!ysas`т1.3e-005с'.4ThesetВ!ypMоesalsouseЁGexpMоonenВ!tialћЂnotationћЃwhentheexponenВ!tisћЃgreaterthanorequaltotheprecision,ђsowithЁGthe,default-format,бthevџdDalue5^yъс10ќОЎ7 сdisplaВ!ysas-`т50000000с'andthevџdDalue5^yъс10ќОЎ8сdisplaВ!ysЁGasйH`т5e+008с'.vIfyВ!ouprefer xed-pMоointdisplayџe,ц youmightйGspMоecify`т-oПЊ%.8fс';ђЙhowever,ц smallЁGnВ!umbMоersоwillпdisplayveryfewпsigni cantdigits,/Gсmakingc-thec,magnitudereadilyapparenВ!t.1Unfortunatelyџe,^fewcompilerssuppMоortthedigit-Љ
33GgroupingІf
ag.Ё!GWithЙгthe`т-с'
ag,щ#theoutputvџdDalueisleftЙвalignedwithinthespMоeci ed eldwidth.Ifa eldІGwidthњ"greaterњ!thanneededtoshoВ!wtheoutputvџdDalueisspMоeci ed,the`т0с'(zero)
agcausesІGtheСKoutputСJvџdDaluetobMоeleftpaddedwithzerosunВ!tilthespMоeci ed eldwidthisreacВ!hed;ЮНforІGexample,Іfwiththeformat`т%011.6fс',Ё.љтYouПЊhave:troypoundІ.љYouПЊwant:grainІ\іь*ПЊ5760.000000І\іь/ПЊ0000.000174ЁGсTheІf`т0с'
aghasnoe ectifthe`т-с'(leftalign)
agisgivВ!en. Gы\11.3Fieldf@Width33GсByг2default,оftheoutputг3vџdDalueisleftalignedandshoВ!wnwiththeminimВ!umwidthnecessaryІGfordothednspMоeci ed(ordefault)precision.їIfa eldwidthgreaterthanthisisspMоeci ed,№theІGvџdDalueЧdshoВ!wnЧeisrightЧealigned,ЃandpaddedontheleftwithenoughspacestoproВ!videtheІGspMоeci edАE eldАDwidth.ћyAАwidthspeci cationАEistВ!ypicallyАDusedwith xed-poinВ!tАDdecimaltoІGhaВ!veTcolumnsT ofnВ!umbMоersTalignatthedecimalpMоoinВ!t;othisarguablyislessusefulwithтunitsІGсthanќwithlongcolumnaroutput,kЁbutћitmaВ!ynonethelessassistinquicklyassessingtheІGrelativВ!eІfmagnitudesofresults.ннFџeorexample,withtheformat`т%12.6fс',Ё.љтYouПЊhave:kmІ.љYouПЊwant:inІ\іь*ПЊ39370.078740І\іь/ ОR0.000025Є4ЬЬ.љYouПЊhave:kmІ.љYouПЊwant:rodІ\іь*>ў198.838782І\іь/ ОR0.005029Ё.љYouПЊhave:kmІ.љYouПЊwant:furlongІ\іь* ОR4.970970І\іь/ ОR0.201168D )Gы\11.4Precision33GсTheg%meaningg$of\precision"depMоendsontheformattВ!ypMоe. With`тgс'or`тGс',TitspMоeci estheІGnВ!umbMоerдЇofsigni canВ!tдЈdigits(liketheт--digitsсoption);ыШwith`тeс',р7`тEс',р8`тfс',orдЇ`тFс',itspMоeci esІGtheІfmaximВ!umnumbMоerofdigitstobeshoВ!wnafterthedecimalpoinВ!t.Є>!GWith/ёthe/ђ`тgс'and`тGс'formattВ!ypMоes,Ttrailingzerosaresuppressed,sothe/ђresultsmaВ!yІGsometimesYhaВ!vefewerdigitsthanZthespMоeci edprecision(asindicatedaboВ!ve,Чthe`т#с'
agІGcausesІftrailingzerostobMоedisplaВ!yed).Ё!GThe\defaultprecision]is6,so`т%gс'isequivџdDalenВ!tto`т%.6gс',andwouldshow]theoutputtoІGsix"signi canВ!t!digits.л Similarlyџe,Щ`т%eс'or`т%fс'wВ!ouldshow!theoutputwithsixdigitsaftertheІGdecimalІfpMоoinВ!t. " и ђ GсUnitsІfConВ!versionTd34 33 § ЬЭ!GTheш2Cш!тprintf()ш3сfunctionalloВ!wsaprecisionofarbitrarysize,јЅwhetherornotalloftheЄ
33GdigitsD{aremeaningful.И WithmostDzcompilers,l themaximВ!uminternalprecisionwithтunitsЁGсisP15decimaldigits(or13hexadecimaldigits).е+Withtheт--digitsсoption,yВ!ouarelimitedЁGtoјлtheјмmaximВ!uminternalprecision;"withјмtheт--output-formatсoption,
yyoumayјмspMоecifyaЁGprecisiongreaterthanthis, "butitmaВ!ynotbMоemeaningful.л@Insomecases, !specifyingexcessЁGprecisiona'canresultina&roundingartifacts.ЦШFџeorexample,o apMоoundisexactly7000grains,butЁGwithІftheformat`т%.18gс',theoutputmighВ!tbMоeЉQ.љтYouПЊhave:poundЁ.љYouПЊwant:grainЁ\іь*ПЊ6999.9999999999991Ё\іь/ПЊ0.00014285714285714287ІGсWithІftheformat`т%.25gс'yВ!oumightgetthefollowing:Q.љтYouПЊhave:1/3Ё.љYouПЊwant:Ё\іьDefinition:ПЊ0.333333333333333314829616256247ІGсIn{чthiscasethe{цdisplaВ!yed{чvџdDalueincludesaseriesofdigitsthatrepresenВ!ttheunderlyingbinaryЁG
oating-pMоoinВ!tsЌapproximationto1/3butaresЋnotmeaningfulforthedesiredcomputation.ЁGIn general,-theresultwith excessprecisionissystemdepMоendenВ!t.кpTheprecisiona ectsonlyЁGthe9фdisplay1сofnВ!umbMоers;if9
a9resultreliesonphВ!ysicalconstants9
thatarenotknoВ!wntotheЁGspMоeci edprecision,6ђthenВ!umberofphВ!ysicallymeaningfuldigitsmaybMоelessthanthenumbMоerЁGofІfdigitsshoВ!wn.І!GSeeжthedoMоcumenВ!tationforзтprintf()сformoredetaileddescriptionsoftheformatspMоeci-ЁG cation.І!GThe65т--output-format64сoptionisincompatiblewiththeт--exponentialсorт--digitsсop-ЁGtions;Pyif%theformerisgivВ!enincombinationwitheitherof%thelatter,?ItheformatiscontrolledЁGbВ!yІfthelastoptiongiven."<ЏGыS12 ИQLo =calization ;GсSomeјsunitshaВ!veјsdi erentјtvџdDaluesindi erentloMоcations.дThelocalizationfeatureaccommo-ЁGdates
thisbВ!y
allowing
aunitsdata letospMоecifyde nitionsthatdepend
ontheuser'sЁGloMоcale. -Gы\12.1Los3cale33GсAёloMоcaleћisasubsetofauser'senВ!vironmentћthatњindicatestheuser'slanguageandcounВ!tryџe,ЁGandHїsomeattendanВ!tpreferences,БsuchastheformattingofHјdates. ХTheтunitsсprogramЁGattempts ^todeterminetheloMоcale ]fromthePOSIX ўen_USPuGсYџeouІfcanforceтunitsсtoruninadesiredloMоcalebВ!yusingtheт-lсoption.І!GIny&ordery'tocreateunitde nitionsforaparticularloMоcaleyВ!oubMоeginabloMоcВ!kofde nitionsЁGin aџunitdata lewith`т!localeс'folloВ!wedby aloMоcalename. 8ЊThe`т!с'mВ!ustbMоethe rstЁGcВ!haracter1ontheline.ЖюThe1тunitsсprogramreadsthefollowingde nitions1onlyifthecurrentЁGloMоcaleкэmatcВ!hes.
YџeouкюendtheblocВ!koflocalizedкюunitswith`т!endlocaleс'.
Hereisanexample,ЁGwhicВ!hІfde nestheBritishgallon.Pu.љт!localeПЊen_GBЁ.љgallon(=І4.54609ПЊliterЁ.љ!endlocale9JGы\12.2Additionalf@Los3calization33GсSometimescОthecПloMоcaleisn'tsucienВ!ttodetermineunitpreferences.ЧІTherecouldbMоeregionalЁGpreferences,ЏХorzВacompanВ!ycouldhavespMоeci cpreferences.ZТThoughprobablyuncommon,ЁGsucВ!hкdi erencesкcouldarisewiththecВ!hoiceofEnglishcustomaryunitsoutsideofEnglish-ЁGspMоeakingйРcounВ!tries.wыTџeoaddressthis,&тunitsсallowsspMоecifyingde nitionsthatdependonЁGenВ!vironmentsзvџdDariablesжsettings.F/TheenВ!vironmentvџdDariablessзcanbMоeconВ!troledbasedontheЁGcurrenВ!tІfloMоcale,ortheusercansetthemtoforceaparticulargroupofde nitions.І!GAчЈconditionalш1252in>theUS=ьandWџeesternEuropMоe).ЄфYoucan>evВ!enuseUTF-8,c§thoughsomemes-ЁGsagesцMmaВ!ybMоeцLimproperlyцMaligned, ИandтunitsсwillnotdetectinВ!vџdDalidUTF-8sequences.еIfyВ!ouЁGuseеgUTF-8еhencoMоdingwhenUnicoMоdesupportеhisnotactivВ!e,с'youshouldеgplaceanyеgde nitionsЁGwithЅnon-ASCIMоIcВ!haractersЅфoutsidex6с`т!utf8с'Oy.Ї..Зљ`т!endutf8с'blocВ!ks|otherwise,ЅПtheyЅwillbeЁGignored.Љ !GTВ!ypMоesetl}materialotherl~thancodeexamplesusuallyusesthel~UnicodeminВ!us(Uт+с2212)ЁGratherЃZthanЃYtheASCIMоIЃhВ!yphen-minusЃZoperatorЃY(Uт+с002D)ЃusedinЃZтunitsс;!гthe guredashЁG(Uт+с2012)1andendash(Uт+с2013)1arealsooMоccasionallyused.jTџeoalloВ!wsuch1materialtobMоeЁGcopiedРandpastedforinВ!teractiveПuseРorinunitsdata les,GтunitsсconВ!vertsРthesecВ!haractersЁGtoДБUт+с002DДbMоeforefurtherprocessing.НBecauseofthis,ИCnoneoftheseДАcВ!haracterscanappearЁGinІfunitnames.!иGыS16 ИQReadlinezГSupp =ortаРGсIf`Wtheтreadline`VсpacВ!kџdDagehasbMоeencompiledin,ЮвthenwhenтunitsсisusedinВ!teractivelyџe,ЁGnВ!umerousB"commandB!lineeditingfeaturesareaВ!vџdDailable.БTџeocheckB"ifyВ!ourversionB!ofтunitsЁGсincludesІfтreadlineс,inВ!vokeІftheprogramwiththeт--versionсoption.І!GFџeorF'completeF(informationabMоoutтreadlineс,YgconsultthedoMоcumenВ!tationfortheтreadlineЁGсpacВ!kџdDage.WithoutЗђanyЗѓcon guration,ќUтunitsсwillalloweditingЗѓinthestyleЗѓofemacs.OfЁGparticularІfusewithтunitsсarethecompletioncommands. !GIf7yВ!outypMоeafewcharactersandthenhit7тESCсfollowedbyш?сthenтunitsсwilldisplayaЁGlistZofalltheZunitsthatstartwiththecВ!haracterstypMоed.ФFџeorZexample,iЧifyouZtypMоeшmetrсandЁGthenІfrequestcompletion,yВ!ouwillseesomethinglikethis:І.љтYouПЊhave:metrЁ.љmetreJЛЂmetriccup3Мњmetrichorsepower TmetrictenthЁ.љmetretes9|Єmetricfifth(=ІmetricouncemetrictonЁ.љmetriccarat(=ІmetricgrainmetricquartmetricyarncountЁ.љYouПЊhave:metrDьOGсIfSЏthereisauniquewВ!aySАtoSЏcompleteaunitname,П yВ!oucanhittheтTABсkВ!eyandтunitsЁGсwilllproВ!videltherestoftheunitname.0{IfтunitsсbMоeeps,'itmeansthatthereisnouniqueЁGcompletion.ннPressingІftheтTABсkВ!eyasecondtimewillprintthelistofallcompletions.І!GThejreadlinelibraryalsojkВ!eepsahistoryofthevџdDaluesyВ!ouenter.ЩМYџeoucanmovethroughЁGthis@history?usingtheupanddoВ!wnarrows.Џ&Thehistory@issaВ!vedto@the leт.units_historyЁGсin:еyВ!ourhomedirectory:жsothatitwillpMоersistacrossmultipleтunits:жсinvoMоcations.КIfyouwishЁGtoшkВ!eepщworkforщacertainpro ЛjectseparateyВ!oucancВ!hangethehistory lenameusingtheЁGт--history!№сoption.P|Yџeoucould,@вforexample,@гmakВ!eanalias!ёforтunitsсtoтunitsІf--historyЁG.units_historyІсsothatЅтunitsсwВ!ouldsaveseparatehistoryЅinthecurrentdirectoryџe. TheЁGlength]ofeacВ!h\history leislimitedto5000lines.кNotealsothatifyВ!ourunsevВ!eralconcurrentЁGcopiesІfofтunitsсeacВ!honewillsaveitsnewhistorytothehistory leupMоonexit. ( )Ьђ GсUnitsІfConВ!versionTd40 33 § ЬЭGыS17 ИQUp =datingzГCurrencyExcџuТhangeRatesЉS4GсTheчunitsшprogramincludescurrencyexcВ!hangeratesandpricesforsomepreciousЄ
33GmetalsЅШintheЅЩdatabase.
мOfcourse,e thesevџdDaluescВ!hangeovertime,e sometimesveryЁGrapidlyџe,4уand~ЫтunitsсcannotproВ!viderealtimevџdDalues.
g ToupMоdatetheexcВ!hangeratesЁGrunЌUtheЌTтunits_curс,mЯwhicВ!hrewritesthe lesconВ!tainingthecurrencyrates,mЯtВ!ypicallyЁGт/usr/share/units/currency.unitsс.WjThisyprogramyrequiresтpythonсandtheтunidecodeЁGсpacВ!kџdDage,њКandPDmustPEbMоerunwithsuitablepermissionstowritethe le. лwTџeokВ!eeptheЁGratesЇupMоdatedЇautomaticallyџe,чFrunitusingacronjobonaUnix-likВ!esystem,чForasimilarЁGscВ!heduling7 programonadi erentsystem.ЌCurrencyexchangeratesaretakenfromTimeЁGGeniey+(тhttp: Ќ/ Ќ / Ъwww.timegenie.comс)y+andy*preciousmetalspricingfromPВ!acketizer(тwww Ќ .ЁGpacketizercб.LЩcomс).K|These FsitesupMоdate EonceperdaВ!yџe,>Оso Ethereisnobene t EinrunningtheЁGupMоdateщscriptmoreщoftenthandailyџe.Ї[Youcanщrunтunits_curсwitha lenamespMоeci edonЁGtheуcommandтlineanditwillwritethedatatothat le.,SIfyВ!ougive`т-с'тforthe leitwillЁGwriteІftostandardoutput. йGыS18 ИQDatabasezГCommandSynџuТtaxІGшunitПЊdefinitionЁKт:сDe neІfaregularunit.Љ ЭGшprefixт-ПЊшdefinitionЁKт:сDe neІfapre x.ІGшfuncnameт(шvarт)ПЊnoerrorunits=[шin-unitsт,шout-unitsт]domain=[шx1т,шx2т]ЁGrange=[шy1т,шy2т]ПЊшdefinition(var)т;шinverse(funcname)ЁKт:сDe neБaВnonlinearunitorunitfunction.ж ThefouroptionalkВ!eywordsБтnoerrorс,ЁKт:тunits=с,Ятrange=Uэсandтdomain=сcanappMоearinanВ!yorder.ьsThede nitionoftheЁKт:inВ!verseІfisoptional. ЮGшtabnameт[шout-unitsт]ПЊnoerrorшpair-listЁKт:сDe ne#apiecewiselinearunit.гЧThepairlistgivВ!esthepMоointsonthetablelistedЁKт:inІfascendingorder.ннTheтnoerrorсkВ!eywordІfisoptional.ІGт!endlocaleЁKт:сEndІfabloMоcВ!kofde nitionsbeginningwith`т!localeс'ІGт!endutf8 гЃсEndІfabloMоcВ!kofde nitionsbegunwith`т!utf8с'ІGт!endvarMсEndІfabloMоcВ!kofde nitionsbegunwith`т!varс'or`т!varnotс'ІGт!includeПЊшfileЁKт:сIncludeІfthespMоeci ed le.ІGт!localeПЊшvalueЁKт:сLoadІfthefolloВ!wingde nitionsonlyoftheloMоcaleissettoхvџdDalueс.ІGт!messageПЊшtextЁKт:сDisplaВ!ywJхtextДJсwhenthewKdatabaseisreadunlessthequietoption(т-qс)isenabled.ІGт!setПЊшvariablevalueЁKт:сSetsъVtheenВ!vironmentъWvџdDariable,ћRхvariableс,toъVthespMоeci edvџdDalueъWфonly)jifdoMоcumentation:Гafreeprogramshould>comewithmanualsЁ'ПЋproВ!vidingurtheussamefreedomsthatthesoftВ!wareurdoMоes.ЭButthisLicenseisnotlimitedtoЁ'ПЋsoftВ!wareтmanuals;БЁitуcanbMоeusedforanВ!ytextualwВ!ork,ЏСregardlessofsub ЛjectmatterorЁ'ПЋwhetherЧ2itispublishedasaprinВ!tedbMоook.@BWџeeЧ2recommendthisLicenseprincipallyforЁ'ПЋwВ!orksІfwhosepurpMоoseisinstructionorreference.х
-1.'ПЋAPPLICABILITYІfANDDEFINITIONSІ'ПЋThisЬ>LicenseЬ=appliestoanВ!ymanualЬ=orotherwork,ГinanyЬ=medium,ДthatcontainsЬ>aЁ'ПЋnotice§ placed§ bВ!ythecopВ!yright§ holdersaying§ itcanbMоedistributedunderthetermsЁ'ПЋofthisLicense.l=SucВ!hanoticegrantsaworld-wide,З
royalty-freelicense,ЗunlimitedinЁ'ПЋduration,т
tooЗuseoЖthatwВ!orkundertheconditionsstatedherein.
9ЯThe\DoMоcumenВ!t",Ё'ПЋbMоeloВ!w,tkrefersgьtoanysuchgэmanualorwork.Щ
AnymembMоerofthegэpublicisalicensee,tkandЁ'ПЋisџaddressedas\yВ!ou".І@Yџeouacceptthelicenseifyoucopyџe, юmoMоdifyordistributetheworkЁ'ПЋinІfawВ!ayІfrequiringpMоermissionundercopВ!yrightІflaw. * Gyђ GсUnitsІfConВ!versionTd42 33 § ЬЭ'ПЋA І\MoMоdi ed РVџeersion" СoftheDocumenВ!tmeans Сanyworkcontainingthe СDoMоcumentorЄ
33'ПЋahpMоortiongofit,ЙheithercopiedvВ!erbatim,ЙhorwithmoMоdi cationsand/ortranslatedinВ!toЁ'ПЋanotherІflanguage.ЉјБ'ПЋA \Secondary РSection"is СanamedappMоendixorafronВ!t-mattersectionoftheDoMоcumenВ!tЁ'ПЋthat/dealsexclusivВ!ely0withtherelationshipofthepublishersorauthorsoftheDoMоcumenВ!tЁ'ПЋtoz
thezDoMоcumenВ!t'soverallzsub Лject(ortorelatedmatters)andconВ!tainsnothingthatЁ'ПЋcouldиЎfallиЏdirectlywithinthatoВ!verallsub Лject.tЕ(Thus,%@iftheиЎDoMоcumentisinиЏpartaЁ'ПЋtextbMоookеofе
mathematics,џMaSecondarySectionmaВ!ynotexplainanВ!ymathematics.)=TheЁ'ПЋrelationshipGоcouldbMоeamatterofhistoricalconnectionwiththesub ЛjectorwithrelatedЁ'ПЋmatters,jorBјofBїlegal,commercial,j philosophical,ethicalorpMоoliticalBјpositionregardingЁ'ПЋthem.јА'ПЋTher\InВ!vџdDariantsSections"arecertainSecondarySectionswhosetitlesaredesignated,0жasЁ'ПЋbMоeing2Dthose2CofInВ!vџdDariant2DSections,I}inthenoticethatsaВ!ysthattheDoMоcumenВ!tisreleasedЁ'ПЋunderS5thisLicense.Т"IfS4asectiondoMоesnot ttheabMоoВ!veS5de nitionofSecondarythenitisЁ'ПЋnotгalloВ!wedtoгbMоedesignatedasInvџdDariant.eSTheDoMоcumentmayгcontainzeroInvџdDariantЁ'ПЋSections.ЂФIfѕtheDoMоcumenВ!tdoesѕnotidenВ!tifyanyInvџdDariantSectionsthenѕtherearenone.І'ПЋThef\CoВ!verfЌTџeexts"arecertainshortpassagesoftextthatarelisted,ОasFџeronВ!t-CoverЁ'ПЋTџeexts-orBacВ!k-Cover,Texts,"8in-thenoticethat,saВ!ysthattheDoMоcument,isreleasedunderЁ'ПЋthisLicense.ЏAAnFџeronВ!t-CoverTџeextmaybMоeatmost5words,6andaBack-CoverTџeextmayЁ'ПЋbMоeІfatmost25wВ!ords.јА'ПЋACІ\TџeransparenВ!t"CЮcopyofCЯtheDoMоcumentmeansaCЯmachine-readablecopyџe,k(representedЁ'ПЋinJmaformatJnwhosespMоeci cationisaВ!vџdDailabletothegeneralpublic,snthatissuitableforЁ'ПЋrevisingЮрtheЮпdoMоcumenВ!tstraightforwardlywithЮпgenerictexteditorsor(forimagescom-Ё'ПЋpMоosedкУofкФpixels)genericpainВ!tprogramsor(fordraВ!wings)somewidelyaВ!vџdDailabledrawingЁ'ПЋeditor,
њand}пthatissuitableforinputto}рtextformattersorforautomatictranslationtoЁ'ПЋa9OvџdDarietВ!yof9Nformatssuitableforinputtotextformatters.ЙA93copВ!ymadeinanotherwiseЁ'ПЋTџeransparenВ!tц leformatхwhosemarkup,Мorabsenceofmarkup,МhasbMоeenarrangedtoЁ'ПЋthВ!wart0ћor0ќdiscouragesubsequenВ!tmoMоdi cationbВ!yreadersisnotTџeransparenВ!t.ЖКAnimageЁ'ПЋformat ЩisnotTџeransparenВ!tifused Шforanysubstantialamountoftext.MA ЉcopythatisЁ'ПЋnotІf\TџeransparenВ!t"iscalled\Opaque".І'ПЋExamplesкZofкYsuitableformatsforTџeransparenВ!tcopiesincludeplainASCIMоIйЩwithoutЁ'ПЋmarkup, kTџeexinfoѕinputformat,LaTў,Г[wEB Xinputformat,SGMLѕorXMLusingapubliclyЁ'ПЋaВ!vџdDailable
эDTD,andstandard-conformingsimpleHTML,PostScriptorPDF
гdesignedЁ'ПЋforEбhВ!umanmoMоdi cation.М ExamplesEвoftransparentimageformatsincludePNG,XCFЁ'ПЋandНмJPG.НнOpaqueformatsincludeproprietaryformatsthatcanbMоereadandeditedЁ'ПЋonlyѕbВ!yѕproprietarywordproMоcessors, [SGMLѕ|orXMLforwhicВ!hѕtheDTDand/orpro-Ё'ПЋcessingltoMоolsmarenotgenerallyaВ!vџdDailable,(andthemacВ!hine-generatedHTML,PВ!ostScriptЁ'ПЋorІfPDFproMоducedbВ!ysomewordproMоcessorsforoutputpurposesonlyџe.јА'ПЋThe м\Title лPВ!age"means,<љforaprinВ!tedbMоook,<љthe мtitlepageitself,<љplussucВ!hfollowingЁ'ПЋpagesRУasareneededtohold,c}legiblyџe,theRУmaterialthisRТLicenserequirestoappMоearintheЁ'ПЋtitle1.page.ЖЪFџeorwВ!orks1-informatswhicВ!hdonothaВ!ve1.anytitle1.pageassucВ!h,H\TitlePage"Ё'ПЋmeansthetextnearthemostprominenВ!tappMоearanceofthewВ!ork'stitle,ЏXprecedingtheЁ'ПЋbMоeginningІfofthebodyofthetext.І'ПЋThe)\publisher"means)anВ!ypMоersonorentitythatdistributes)copiesoftheDoMоcumentЁ'ПЋtoІfthepublic. + Vtђ GсUnitsІfConВ!versionTd43 33 § ЬЭ'ПЋAэsectionђ\EnВ!titledXYZ"meansanamedѓsubunitoftheDoMоcumenВ!twhosetitleeitherЄ
33'ПЋisUЊpreciselyUЉXYZUorconВ!tainsXYZinparenВ!thesesUЉfollowingUЊtextthattranslatesXYZUinЁ'ПЋanotherўЏlanguage.Ѕі(HereXYZўstandsforaspMоeci csectionnamemenВ!tionedbeloВ!w, :suchЁ'ПЋasaa\AcВ!knowledgements",o/\Dedications",\EndorsemenВ!ts",or\History".)ЦлTџeo\PreservВ!eЁ'ПЋtheTitle"ofsucВ!hasectionwhenyВ!oumoMоdifytheDoMоcumenВ!tmeansthatitremainsaЁ'ПЋsectionІf\EnВ!titledXYZ"accordingtothisde nition.Љ&g'ПЋTheSuDoMоcumenВ!tmayincludeWџearrantyDisclaimersnextSvtothenoticewhichstatesthatЁ'ПЋthisЙLicenseappliesКtotheDoMоcumenВ!t. зTheseWџearrantyDisclaimersКareconsideredtoЁ'ПЋbMоe§includedўbВ!yreferenceinthisLicense,МЃbutonlyasregardsdisclaimingwВ!arranties:Ё'ПЋanВ!ynothernimplicationthattheseWџearranВ!tyDisclaimersnmayhavenisvoidnandhasnoЁ'ПЋe ectІfonthemeaningofthisLicense.&h-2.'ПЋVERBAџeTIMІfCOPYINGІ'ПЋYџeouљmaВ!ycopyanddistributetheDoMоcumentinanymedium,Ю eithercommerciallyorЁ'ПЋnoncommerciallyџe,zЊproВ!vided that thisLicense,the copВ!yright notices,and thelicenseЁ'ПЋnoticeKsaВ!yingK
thisLicenseappliestotheDoMоcumenВ!tarereproMоducedinallcopies,t7andЁ'ПЋthat1'yВ!ouaddno1(otherconditionswhatsoMоevertothoseofthisLicense.ЖЩYџeoumaynotuseЁ'ПЋtecВ!hnicalђmeasuresђtoobstructorconВ!trolthereadingorfurthercopВ!yingofthecopiesЁ'ПЋyВ!ouђЧmakeђШordistribute.ЁўHowever,ДyoumayacceptђШcompMоensationinexchangeђШforcopies.Ё'ПЋIfо yВ!ouо distributealargeenoughnВ!umbMоerofо copiesyВ!oumustо alsofolloВ!wtheconditionsЁ'ПЋinІfsection3.І'ПЋYџeou}ьmaВ!yalso}ыlendcopies,Й7underthesameconditionsstatedabMоoВ!ve,Й8andyou}ьmaypubliclyЁ'ПЋdisplaВ!yІfcopies.І-3.'ПЋCOPYINGІfINQUANTITY&h'ПЋIfУyВ!ouТpublishprintedТcopies(orcopiesinmediathatcommonlyhaВ!veprintedcovers)УofЁ'ПЋtheб.DoMоcumenВ!t,лпnumberingб.morethanб-100,лрandtheб.DocumenВ!t'slicenseб-noticerequiresЁ'ПЋCoВ!ver мTџeexts,<љyou лmustenclosethecopies лincoversthatcarryџe,<љclearly лandlegibly,<љallЁ'ПЋtheseД@CoВ!verTџeexts:љFronВ!t-CoverTџeextsonthefrontcover,їЕandBack-CoverTџeextsonЁ'ПЋtheіbacВ!kѕcover.б
BothcoversmustѕalsoclearlyandlegiblyidenВ!tifyyouasѕthepublisherЁ'ПЋof ,these +copies.H/ThefronВ!tcovermustpresent +thefulltitlewithallwВ!ordsofthetitleЁ'ПЋequallyГxprominenВ!tandГyvisible.YџeoumayГyaddothermaterialonthecoВ!versГxinaddition.Ё'ПЋCopВ!yingY4withY3changeslimitedY3tothecoВ!vers,
чasY3longastheypreservВ!ethetitleoftheЁ'ПЋDoMоcumenВ!tuandsatisfytheseconditions,ЈХcanbetreateduasvВ!erbatimcopyinginotherЁ'ПЋrespMоects.І'ПЋIfю|therequiredю}textsforeithercoВ!verю|aretoMоovВ!oluminousto tlegiblyџe, youshouldputЁ'ПЋtheђ rstђoneslisted(asmanВ!yas treasonably)ontheactualcoВ!ver,љandcontinueђtheЁ'ПЋrestІfonВ!toadjacentpages.І'ПЋIf?|yВ!ou?{publishordistributeOpaquecopiesoftheDoMоcumenВ!tnumbMоering?|morethan100,Ё'ПЋyВ!ou\3musteither\4includeamachine-readableTџeransparentcopyalong\4witheachOpaqueЁ'ПЋcopВ!yџe,[>or7state7inorwitheacВ!hOpaquecopy7acomputer-networkloMоcation7fromwhichЁ'ПЋtheщSgeneralщRnetВ!work-usingpublichasщRaccesstodownloadusingщRpublic-standardnetworkЁ'ПЋprotoMоcolsЌ=acompleteЌ>TџeransparenВ!tcopyoftheDoMоcument,эГfreeofaddedmaterial.яcIfЁ'ПЋyВ!ouЊusetheЊlatteroption,ъљyoumustЊtakereasonablyprudentsteps,ъјwhenyoubMоeginЁ'ПЋdistributionlofmOpaquecopiesinquanВ!tityџe,гЎtolensurethatthisTџeransparenВ!tcopylwillЁ'ПЋremain CthВ!usaccessible DatthestatedloMоcationuntil Datleastoneyearafter Dthelasttime , i
ђ GсUnitsІfConВ!versionTd44 33 § ЬЭ'ПЋyВ!oukdistributekanOpaquecopyk(directlyorthroughyourkagentsorretailers)kofthatЄ
33'ПЋeditionІftothepublic.ЉFх'ПЋIt&Nisrequested,FHbutnotrequired,FGthatyВ!oucontacttheauthorsoftheDoMоcumentwellЁ'ПЋbMоeforeoХredistributingoФanВ!ylargenumbMоeroФofcopies,zВtogivВ!ethemacВ!hancetoproВ!videyouЁ'ПЋwithІfanupMоdatedvВ!ersionoftheDocumenВ!t.І-4.'ПЋMODIFICAџeTIONSІ'ПЋYџeou*maВ!ycopyand)distributeaMoMоdi edVџeersionoftheDoMоcumenВ!tundertheconditionsЁ'ПЋof
sections
2and3abMоoВ!ve,П]providedthat
yourelease
theMoMоdi edVџeersionunderpreciselyЁ'ПЋthis{оLicense,`withthe{пMoMоdi edVџeersion llingtheroleoftheDoMоcumenВ!t,`thus{оlicensingЁ'ПЋdistributionИandmoMоdi cationЙoftheModi edVџeersiontowhoevВ!erЙpossessesacopВ!yofЁ'ПЋit.ннInІfaddition,yВ!oumustdothesethingsintheMoMоdi edVџeersion:Fф*ђФA.=nUseэpintheTitlePВ!age(andonthecovers,џ2ifany)atitledistinctfromthatoftheЁ=nDoMоcumenВ!t,+andfromthoseofpreviousversions(whichshould,+iftherewereanyџe,Ё=nbMоeТјlistedintheHistoryТїsectionoftheDocumenВ!t).3YџeoumayТїusethesametitleasЁ=naІfpreviousvВ!ersioniftheoriginalpublisherofthatversiongivespMоermission.І+gB.=nListЊ\ontheTitleЊ[PВ!age,ЋZasauthors,ЋYoneormorepMоersonsorenВ!titiesrespMоonsibleforЁ=nauthorship"of"themoMоdi cationsintheMoMоdi edVџeersion,<|togetherwithatleast vВ!eЁ=nofпИtheprincipalauthorsoftheDoMоcumenВ!t(allofitsprincipalauthors,uifithasfewerЁ=nthanІf vВ!e),unlesstheyreleaseyoufromthisrequirement.І+@ЂC.=nStateБгonБвtheTitlepagethenameofthepublisheroftheMoMоdi edVџeersion,ДastheЁ=npublisher.І*ЫеD.=nPreservВ!eІfallthecopyrightnoticesoftheDoMоcument.І+ЕoE.=nAddФeanФdappropriatecopВ!yrightnoticeФeforyourФemoMоdi cationsadjacentФetotheotherЁ=ncopВ!yrightІfnotices.І,LF.=nInclude,hSimmediatelyXЮafterthecopВ!yrightXЮnotices,alicensenoticegivingthepublicЁ=npMоermissionяЫtoяЪusetheMoMоdi edVџeersionunderthetermsofthisLicense,PintheformЁ=nshoВ!wnІfintheAddendumbMоelow.Fф*nG.=nPreservВ!eМminМlthatlicensenoticethefulllistsofInВ!vџdDariantSectionsМmandrequiredCoВ!verЁ=nTџeextsІfgivВ!enintheDoMоcument'slicensenotice.І*ђФH.=nIncludeІfanunalteredcopВ!yofthisLicense.І/4чI.=nPreservВ!eкtheкsectionEntitledк\History",чPreserveitsкTitle,чandaddtoitanitemЁ=nstating_ at_ leastthetitle,mQyВ!ear,newauthors,and_ publisheroftheMoMоdi edVџeersionЁ=nasФXgivВ!enonФWtheTitlePage.7ГIfФWthereisnosectionEntitled\History"ФWintheDoMоcu-Ё=nmenВ!t,O#create-eone-dstatingthetitle,O$year,O#authors,and-epublisher-doftheDoMоcumentЁ=nasWgivВ!enonitsTitlePage,FthenaddanitemdescribingtheMoMоdi edVџeersionasЁ=nstatedІfintheprevioussenВ!tence.І-ЂJ.=nPreservВ!eцthenetworkloMоcation,ѕњifanyџe,ѕњgivenintheDoMоcumentцforpublicaccesstoЁ=naН
TџeransparenВ!tcopyНoftheDoMоcument,УMandlikewisethenetworkНloMоcationsgiveninЁ=ntheЭDoMоcumenВ!tЭforpreviousversionsЭitwasbasedon.S6TheseЭmaybMоeplacedЭintheЁ=n\History"8section.ІЮYџeou9maВ!yomitanetВ!work8loMоcationforawВ!orkthatwВ!aspublishedЁ=natKleastfourKyВ!earsbMоeforetheDocumenВ!titself,t@oriftheoriginalKpublisheroftheЁ=nvВ!ersionІfitreferstogivespMоermission. - zъђ GсUnitsІfConВ!versionTd45 33 § ЬЭ*ЄхK.=nFџeorйranВ!ysectionEntitled\Acknowledgements"or\Dedications",oPreservetheTitleЄ
33=nof/Rthe/Qsection,G#andpreservВ!einthesectionallthesubstanceandtoneofeacВ!hoftheЁ=nconВ!tributorІfacknowledgementsand/ordedicationsgiventherein.Љ,Q*L.=nPreservВ!e?дall?гtheInvџdDariant?гSectionsoftheDoMоcumenВ!t,f/unalteredintheirtextandЁ=ninPмtheirPнtitles.н@SectionnВ!umbMоersorPнtheequivџdDalentPнarenotconsideredpartoftheЁ=nsectionІftitles. ) M.=nDeleteА5anВ!ysectionEntitledА4\Endorsements".ћJSuchasectionА4maynotbMоeincludedЁ=ninІftheMoMоdi edVџeersion.І*ђФN.=nDog!notg"retitleanВ!yexistingsectiontobMоeEnВ!titled\Endorsements"g"ortocon
ictinЁ=ntitleІfwithanВ!yInvџdDariantSection. *ЄхO.=nPreservВ!eІfanyWџearrantyDisclaimers.ЬЮ'ПЋIfиtheзMoMоdi edVџeersionincludesnewfronВ!t-mattersectionsorappMоendicesthatqualifyЁ'ПЋasXSecondaryX SectionsandconВ!tainnomaterialcopiedfromtheDoMоcumenВ!t,gДyoumayXatЁ'ПЋyВ!ourуkoptionуldesignatesomeorallofthesesectionsasinВ!vџdDariant.эTџeodoуkthis,ђaddtheirЁ'ПЋtitles@Ћtothelist@ЌofInВ!vџdDariant@ЋSectionsintheMoMоdi edVџeersion'slicensenotice.ЌЌTheseЁ'ПЋtitlesІfmВ!ustbMоedistinctfromanyothersectiontitles.І'ПЋYџeoupmaВ!yqaddasectionEntitledq\Endorsements",sВprovideditcontainsqnothingbutЁ'ПЋendorsemenВ!tsofyourMoMоdi edVџeersionbyvџdDariousparties|forexample,ZstatementsofЁ'ПЋpMоeerD
revieworDthatthetexthasbeenDapproВ!vedD
byanorganizationDastheauthoritativeЁ'ПЋde nitionІfofastandard. 'ПЋYџeouf,maВ!yf-addapassageofupto vВ!ewordsf-asaFџeronВ!t-Coverf,Text,sandf-apassageofupЁ'ПЋto@25wВ!ords@asaBack-CoverTџeext,Tьto@theendofthelistofCoВ!ver@TџeextsintheMoMоdi edЁ'ПЋVџeersion.е+OnlyN+oneN*passageofFronВ!t-CoverN*TextN+andoneN*ofBacВ!k-CoverN+TextN*mayN+bMоeЁ'ПЋaddedNСbВ!y(orthrougharrangementsmadeby)NТanyoneentityџe.РІIftheDoMоcumentalreadyЁ'ПЋincludesЩaШcoВ!vertextШforthesamecoВ!ver,/!previouslyaddedbyШyouorШbyarrangementЁ'ПЋmade:ЧbВ!ythesameentityyouareactingonbMоehalfof,_пyoumay:Шnotaddanother;їbutЁ'ПЋyВ!ou)mayreplace*theoldone,2onexplicitpMоermissionfromthepreviouspublisherthatЁ'ПЋaddedІftheoldone.І'ПЋThe^author(s)]andpublisher(s)oftheDoMоcumenВ!tdonotbВ!ythisLicensegivВ!epMоermissionЁ'ПЋtoЄjusetheirЄknamesforpublicitВ!yforortoassertorimplyendorsemenВ!tofanВ!yMoMоdi edЁ'ПЋVџeersion. -5.'ПЋCOMBININGІfDOCUMENTSІ'ПЋYџeouІЧmaВ!yІШcombinetheDoMоcumentІШwithotherdoMоcumenВ!tsreleasedunderthisLicense,Ё'ПЋundersthetermstde nedinsection4abMоoВ!vesformodi edvВ!ersions,гЗprovidedsthatyВ!ouЁ'ПЋinclude in thecomВ!binationalloftheInВ!vџdDariant SectionsofalloftheoriginaldoMоcumenВ!ts,Ё'ПЋunmoMоdi ed,L3and5Іlist5ЇthemallasInВ!vџdDariant5ІSectionsofyВ!ourcombined5Їworkin5ЇitslicenseЁ'ПЋnotice,ІfandthatyВ!oupreservealltheirWџearrantyDisclaimers. 'ПЋTheЂ@comВ!binedworkneedonlycontainonecopyofthisLicense,ЃandmultipleidenticalЁ'ПЋInВ!vџdDariantцнSectionsmaВ!ybMоereplacedwithasingleцмcopyџe.BIftherearemultipleInvџdDariantЁ'ПЋSections6Чwith6Шthesamenamebutdi erenВ!tcontents,Mmake6ШthetitleofeacВ!hsuch6ЧsectionЁ'ПЋuniquebbВ!ycaddingattheendofit,1"inparenВ!theses,1!thenameoftheoriginalauthororЁ'ПЋpublisher ofthat ~sectionifknoВ!wn,!orelseauniquenВ!umbMоer.ІMakethe sameadjustmenВ!tЁ'ПЋtoюtheюsectiontitlesinthelistofInВ!vџdDariantюSectionsinthelicensenoticeofthecomВ!binedЁ'ПЋwВ!ork. . ђ GсUnitsІfConВ!versionTd46 33 § ЬЭ'ПЋInі"theі#comВ!bination,Jyoumustі#combineanyі#sectionsEntitledі#\History"inthevџdDari-Є
33'ПЋousмлoriginalмкdoMоcumenВ!ts,ъxformingonesectionEnВ!titled\History";јlikewiseмкcombineanyЁ'ПЋsectionsбEnВ!titled\Acknowledgements",лПandanysectionsEntitled\Dedications".]чYџeouЁ'ПЋmВ!ustІfdeleteallsectionsEntitled\Endorsements."ЉЬЭ-6.'ПЋCOLLECTIONSІfOFDOCUMENTSЬЮ'ПЋYџeouвЄmaВ!ymakeacollectionconsistingofвЃtheDoMоcumentandotherdoMоcumentsreleasedЁ'ПЋunderthisLicense,sкandreplacetheindividualcopiesofthisLicenseinthevџdDariousЁ'ПЋdoMоcumenВ!ts Dwith Casinglecopy Cthatisincludedinthecollection,yЛproВ!videdthatyВ!ouЁ'ПЋfolloВ!wtthetrulesofthisLicenseforvВ!erbatimcopyingtofeachtofthedoMоcumenВ!tsinallЁ'ПЋotherІfrespMоects.І'ПЋYџeouЦ=maВ!yextractasingledoMоcumentfromsuchacollection,Ю2anddistributeitindividu-Ё'ПЋally4under4thisLicense,WnproВ!videdyou4insertacopВ!yofthisLicenseinВ!totheextractedЁ'ПЋdoMоcumenВ!t,љјandщBfollowщAthisLicenseinallotherrespMоectsregardingvВ!erbatimcopyingщAofЁ'ПЋthatІfdoMоcumenВ!t.І-7.'ПЋAВ!GGREGAџeTIONІfWITHINDEPENDENTWORKSЬЮ'ПЋA]Цcompilation]иoftheDoMоcumenВ!t]йoritsderivџdDativeswithother]йseparateandindepMоendentЁ'ПЋdoMоcumenВ!tsџhorџiworks,Љinoronџiavolumeџiofastorageordistributionmedium,ЉiscalledЁ'ПЋan \aggregate"ifthe
copВ!yright resultingfromthecompilationisnotusedtolimittheЁ'ПЋlegal1 righВ!ts1ofthecompilation'susersbMоeyВ!ondwhattheindividualwВ!orkspMоermit.ЖОWhenЁ'ПЋtheDoMоcumenВ!tisincludedinanaggregate,л№thisLicensedoesnotapplytotheotherЁ'ПЋwВ!orksІfintheaggregatewhicharenotthemselvesderivџdDativeworksoftheDoMоcument.І'ПЋIfЛVtheCoВ!verЛVTџeextrequiremenВ!tofsection3ЛUisapplicabletothesecopiesoftheDoMоcument,Ё'ПЋthenАDifАEtheDoMоcumenВ!tislessthanonehalfoftheenВ!tireaggregate,с~theDoMоcumenВ!t'sCoverЁ'ПЋTџeexts0maВ!ybMоeplacedoncoversthatbrackettheDoMоcumentwithinthe0aggregate,GАortheЁ'ПЋelectronic5qequivџdDalenВ!t5pofcovers5piftheDoMоcumenВ!tisinelectronicform.ќOtherwisetheyЁ'ПЋmВ!ustІfappMоearonprintedcoversthatbracketthewholeaggregate.ЬЮ-8.'ПЋTRANSLAџeTIONІ'ПЋTџeranslationЬЏisЬАconsideredakindofmoMоdi cation,AsoyВ!oumayЬАdistributetranslationsЁ'ПЋofTўtheT§DoMоcumenВ!tunderthetermsofsection4. щЃReplacingInВ!vџdDariantSectionsTўwithЁ'ПЋtranslationsvВrequiresvГspMоecialpermissionfromtheirvГcopВ!yrightvВholders,ъФbutyouvВmayЁ'ПЋinclude№ktranslationsofsome№jorallInВ!vџdDariant№kSectionsinadditiontotheoriginalvВ!ersionsЁ'ПЋofЦ theseЦ InВ!vџdDariantSections.= YџeouЦ mayincludeЦ atranslationofthisLicense,Ю
andalltheЁ'ПЋlicenseђњnoticesђћintheDoMоcumenВ!t,F andanyђњWџearrantyDisclaimers,F providedђћthatyouЁ'ПЋalsoЯ includeЮџtheoriginalEnglishvВ!ersionofthisLicenseandtheoriginalvВ!ersionsofЁ'ПЋthosenoticesanddisclaimers.5хIncaseofadisagreemenВ!tbMоetweenthetranslationandЁ'ПЋthe:original:vВ!ersionofthisLicenseoranoticeordisclaimer,_ theoriginalvВ!ersionwillЁ'ПЋprevџdDail.І'ПЋIfpшasectioninpщtheDoMоcumenВ!tisEntitled\Acknowledgements",{\Dedications",orpш\His-Ё'ПЋtory",AПthe(requiremenВ!t(section4)toPreserveitsTitle(section1)willtypicallyrequireЁ'ПЋcВ!hangingІftheactualtitle.ЬЮ-9.'ПЋTERMINAџeTIONІ'ПЋYџeoumaВ!ynotcopyџe,ОmoMоdify,sublicense,ordistributetheDoMоcumenВ!texceptasexpresslyЁ'ПЋproВ!videdЁ№underЁёthisLicense.а|AnyЁёattemptotherwisetocopВ!yџe,ргmoMоdify,рвsublicense,orЁ'ПЋdistributeІfitisvВ!oid,andwillautomaticallyterminateyourrightsunderthisLicense. / Gђ GсUnitsІfConВ!versionTd47 33 § ЬЭ'ПЋHoВ!wever,ѓЗifфAyouф@ceaseallviolationofthisLicense,ѓИthenyВ!ourlicensefromaparticularЄ
33'ПЋcopВ!yrightJholderisJreinstated(a)proВ!visionallyџe,sunlessanduntilJthecopyrightholderЁ'ПЋexplicitlyс_and nallyterminatesyВ!ourlicense,0 and(b)pMоermanentlyџe,0 ifthecopyrightЁ'ПЋholder"failstonotifyyВ!ouoftheviolation"bysomereasonablemeanspriorto60daysЁ'ПЋafterІfthecessation.Љ(і'ПЋMoreoВ!ver,Я8yourЧ
licenseЧfromaparticularcopВ!yrightЧ
holderisreinstatedpMоermanenВ!tlyifЁ'ПЋtheV`copВ!yrightholderVanoti esyouoftheviolationVabysomereasonablemeans,fbthisistheЁ'ПЋ rstWtimeyВ!ouWhaveWreceivednoticeofviolationWofthisLicense(foranyWwork)fromthatЁ'ПЋcopВ!yrightењholder,соandyВ!oucuretheviolationpriorељto30daysafteryourељreceiptoftheЁ'ПЋnotice.(ї'ПЋTџeerminationNuofyВ!ourrightsunderthissectionNtdoMоesnotterminatethelicensesofpartiesЁ'ПЋwhoqhaВ!vereceivedcopiesorrightsfromyoupunderthisLicense.ЊўIfyourrightshaveЁ'ПЋbMоeen Юterminatedandnot ЭpermanenВ!tlyreinstated,:Йreceiptofacopyofsome ЭoralloftheЁ'ПЋsameІfmaterialdoMоesnotgivВ!eyouanyrightstouseit.І10.'ПЋFUTUREІfREVISIONSOFTHISLICENSE(ї'ПЋTheџaFџereeџbSoftВ!wareFџeoundationџbmaypublishџbnew,UrevisedvВ!ersionsoftheGNUџ FџereeЁ'ПЋDoMоcumenВ!tationйтLicenseйуfromtimetotime.xRSuchnewйуversionswillbMоesimilarйуinspiritЁ'ПЋto цthepresenВ!tversion,?
butmaydi erindetailtoaddress хnewproblemsorconcerns.Ё'ПЋSeeІfтhttp://www.gnu.org/copyleft/с.І'ПЋEacВ!hзversionoftheLicenseisgivenadistinguishingversionnumbMоer.дIftheDocumenВ!tЁ'ПЋspMоeci esrthataparticularnВ!umberedrversionofthisLicense\oranylaterversion"Ё'ПЋappliesцQtoцPit,іLyВ!ouhaveцQtheoptionцPoffollowingthetermsцPandconditionseitherofthatЁ'ПЋspMоeci edvВ!ersionorofanylaterversionthathasbMоeenpublished(notasadraft)byЁ'ПЋtheю!Fџereeю"SoftВ!wareFџeoundation.ЕIfю"theDoMоcumentю"doesю!notspecifyю"avВ!ersionnumbMоerю!ofЁ'ПЋthis$License,D)yВ!oumaychoMоose$anyversioneverpublished(notasadraft)bytheFџereeЁ'ПЋSoftВ!wareжUFџeoundation.mЉIftheDoMоcumenВ!tspeci esthataproВ!xyжTcandecidewhichfutureЁ'ПЋvВ!ersionsщ)ofщ*thisLicensecanbMоeused,љкthatproВ!xy'spublicstatementщ*ofacceptanceofaЁ'ПЋvВ!ersionІfpMоermanentlyauthorizesyoutochoMоosethatversionfortheDoMоcument.І11.'ПЋRELICENSING(ї'ПЋ\MassivВ!e{"Multiauthor{#CollabMоorationSite"(or\MMCzьSite")meansany{#WџeorldWideЁ'ПЋWџeebLeservВ!erthatpublishescopyrightableLfworksandalsoprovidesprominentfacilitiesЁ'ПЋforM anВ!ybMоodytoeditthosewВ!orks.РEAMpublicwikithatManybMоodycaneditisanexampleofЁ'ПЋsucВ!h Yaserver.ЕA ?\Massive XMultiauthorCollabMоoration"(or\MMC") >containedintheЁ'ПЋsiteІfmeansanВ!ysetofcopyrightableworksthuspublishedontheMMCsite.І'ПЋ\CC-BY-SA"8Єmeans8Щthe8ЪCreativВ!eCommonsAttribution-Share8ЪAlike3.08Ъlicensepub-Ё'ПЋlished8bВ!y8CreativeCommons8CorpMоoration,N(anot-for-pro tcorpMоorationwithaprincipalЁ'ПЋplaceђofbusinessinSanFџerancisco,7ЃCalifornia,7ЂaswВ!ellasfuturecopyleftversionsofthatЁ'ПЋlicenseІfpublishedbВ!ythatsameorganization.(ї'ПЋ\IncorpMоorate"zmeanstopublishyorrepublishaDocumenВ!t,Џ?inwholeoryinpart,aspartЁ'ПЋofІfanotherDoMоcumenВ!t.І'ПЋAn&\MMC&U ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:pЌ31ЁGoutputTformat
ags ѕњ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:'ЕЌ32ЁGoutputTformatspAЧeci cationњ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЫЕЌ32ІGoutputTprecisionl ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:H'Ќ33 § ЬЭ ѓс№ы\P. ѓс№ЌPџ:ЋAО9GERTenvironmentvџ|rariable}Й ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЏtЌ37Є
л ѓс№parenО9theses ю ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ЬЌ6,T7,8,11,26,27Ё ѓс№`ЩperЌ'TopAЧeratorк* ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: хЌ6Љ
к ѓс№pAЧersonalTunitsdata leѕ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: 'ZЌ25Ё ѓс№piecewiseTlinearunitsPK ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:Ќ29Ё ѓс№plusT(`Щ+Ќ')opAЧeratori ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:[Ќ8І ѓс№pAЧoО9wersќЅ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ._Ќ7Ё ѓс№precision,ToutputлС ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:
|Ќ33Ё ѓс№pre xesq ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЃDЌ5І ѓс№pre xesTandexpAЧonenО9ts і ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:МАЌ7Ё ѓс№pre xes,Tde nitionofко ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: Ќ26Ё ѓс№previousTresult& ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:X>Ќ10І ѓс№primitivО9eTunitsP ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:A Ќ26Ё ѓс№proAЧductsTofunitsе ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: YЌ6Є 3 ѓс№ы\Q. ѓс№ЌquotienО9tsTofunits ё ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:#ZЌ6Ё ѓс№ы\R. ѓс№Ќrange,Tnonlinearunitde nitions У ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:=}Ќ28І ѓс№ЩreadlineЌ,TusewithЩunitsrЛ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЄuЌ39Є
л ѓс№reciproAЧcalTconО9versionKQ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:} Ќ2Ё ѓс№roAЧotsy ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЋCЌ9 я ѓс№ы\S. ѓс№ЌsetloAЧcaleTfunction жо ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:Ќ34Ё ѓс№slashT(`Щ/Ќ')opAЧeratorц ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: UЌ6І ѓс№solidusT(`Щ/Ќ')opAЧerator) ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:KфЌ6Ё ѓс№sphere,TvО9olumeof Вп ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:фЌ14Ё ѓс№squareTroAЧotsNѕ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЏЌ9І ѓс№starT(`Щ*Ќ')opAЧeratorъ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: >Ќ6Ё ѓс№StateTPlaneCoAЧordinateSystem,US ф ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ТЌ5І ѓс№strictTconО9version. ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:_ЬЌ2Ё ѓс№subtractionTofunits ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:пZЌ8Ё ѓс№sumsTanddi erencesofunits~? ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЏњЌ8І ѓс№sumsTofunitsђ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: $SЌ8,T15Ё ѓс№survО9eyTfoAЧot,US дг ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:Ќ5Ё ѓс№survО9eyTmeasure,US ы ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:КЅЌ5І ѓс№survО9eyTmile,USPд ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:Ќ5Ё ѓс№synО9taxTofunitsdatabase я ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:=ЉЌ40Є 3 ѓс№ы\T. ѓс№ЌtempAЧeratureTconО9versionsJі ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:|АЌ13Ё ѓс№ы\U. ѓс№ЌUnicoAЧdeTsupportr) ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЃуЌ38І ѓс№unitTcompletionusing`Щ?Ќ'(ЩreadlineЌonly) ЦЮ ХUВ: p ХU: ХU: ХU: ХU: ХU:јЌ39Є
л ѓс№unitTde nitionsЅ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:Ю_Ќ4Ё ѓс№unitTexpressionsя ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ЦЌ6І ѓс№unitTexpressions,complicatedk ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЦЌ11Ё ѓс№unitTlistaliases,de ningMD ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:~џЌ31 4 AЈђ GсUnitsІfConВ!versionTd52 33 ўXN џH~ПGЌunitTlistsиI ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:
Ќ15Є
Ы^GunitTnamecompletion ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:IиЌ39ЁGunitsTdata le,pAЧersonal ЌМ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:оwЌ25Љ
Ы_GunitsTdata les,additional ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЧЫЌ25ЁGunitsTde nitions,adding ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЧЫЌ26ЁGunitsTde nitions,cО9hangingu- ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ІшЌ26ЁGunitsTfunctionsљ- ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: *чЌ29ЁGunitsTquotienО9ts g ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:=!Ќ6ЁGunits,Tde nitionof ј3 ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:)юЌ26ІGunits,TloAЧokupmethod9њ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:kЕЌ5ЁGunits,Tpiecewiselinearh ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:9"Ќ29ЁGunits,TprimitivО9e дЅ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:`Ќ26ЁGunits,Tsumsanddi erences]\ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:Ќ8ЁGunits,TsumsofАв ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:тЌ15ЁGUNITS ЅЦ c4 ЦgѓENGLISHTenО9vironmentvџ|rariable§џ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: /ЙЌ37ІGUNITSFILETenО9vironmentvџ|rariableЯT ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: Ќ37ЁGUNITSLOCALEMAPTenО9vironmentvџ|rariable й ХUВ: p ХU: ХU: ХU:
зЌ37ЁGUSTStatePlaneCoAЧordinateSystem Г ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:PmЌ5 џH~П ѓс№USTsurvО9eyfoAЧot~ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:A9Ќ5Є
x ѓс№USTsurvО9eymeasureбЮ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: Ќ5Љ
y ѓс№USTsurvО9eymileЗ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ЫqЌ5Ё ѓс№UTF-8еE ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: џЌ38 :Ћ ѓс№ы\V
u ѓс№ЌvО9erbAЧoseToutputќ3 ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: -юЌ2І ѓс№vО9erticalTbar(`Щ|Ќ')opAЧerator цр ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:Ќ7Ё ѓс№vО9olumeTmeasure,Englishcustomary В ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:ФlЌ5Є ;я ѓс№ы\W
t ѓс№ЌwireTgauges ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:G-Ќ14Ё ѓс№ы\Y
u ѓс№ЌyО9ard,Tinternational ЗЋ ХUВ: p ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU: ХU:щfЌ5ј уР ; ш33УЏџ 8ѓcЗсgЃ ff cmmi12ѓ_пЕT ff cmtt12ѓ\ТжN ff cmbx12ѓVпЕT GЎ cmtt12ѓSТжN GЎ cmbx12ѓJТжN Мj cmbx12ѓEпъ b>
ѓ3
cmmi10ѓ=пъ2:
sys.stderr.write('Usage: {0} [filename]\n\n'.format(sys.argv[0]))
sys.stderr.write('Update currency information for \'units\' into the specified\n')
sys.stderr.write('filename or the default location, \'{0}\'.\n'.format(outfile))
sys.exit(1)
try:
currencies = ET.parse(urllib.request.urlopen('http://rss.timegenie.com/forex.xml')).findall('data')
except IOError as exc:
sys.stderr.write('Error connecting to currency server. {0}\n'.format(exc))
sys.exit(1)
# print codes here
codes = [x.find('code').text for x in currencies]
names = [x.find('description').text for x in currencies]
values = [x.find('rate').text for x in currencies]
# Sometimes currency rates are missing from the xml file
# Delete such currencies
while True:
try:
none = values.index(None)
sys.stderr.write('no rate for "%s" (%s)\n' % (names[none], codes[none]))
del codes[none]
del names[none]
del values[none]
except ValueError:
break
# Precious metals are showing up with weird prices (per gram?)
# Delete them
metalcodes = ['XAG','XAU','XPD','XPT']
for i in range(len(metalcodes)):
try:
badind = codes.index(metalcodes[i])
del codes[badind]
del names[badind]
del values[badind]
except ValueError:
break
names = [x.lower().replace(' ','') for x in names]
foundunicode=False
for i in range(len(names)):
if names[i] == 'anguilla(ecd)':
names[i] = 'eastcaribbeandollar'
if isinstance(names[i],str): # this test needed only for python2
ascii = unidecode(names[i])
else:
ascii = names[i]
if names[i] != ascii:
if not foundunicode:
foundunicode = True
outstr += '# Unicode Currency Names\n\n!utf8\n'
outstr += names[i] + ' ' *(23-len(names[i])) + ascii + '\n'
names[i] = ascii
if foundunicode:
outstr += '!endutf8\n\n'
outstr += '# ISO Currency Codes\n\n'
outstr += '\n'.join([x + ' '*20 + y for x,y in zip(codes,names)])
usd = codes.index('USD')
euro = codes.index('EUR')
usdval = values[usd]
values = ['1|' + x +' euro' for x in values]
values[euro] = usdval + ' US$'
del names[usd]
del values[usd]
# print rates here
now = datetime.now()
outstr += '\n\n# Currency exchange rates from Time Genie (www.timegenie.com)\n'
outstr += '\n!message Currency exchange rates from www.timegenie.com on '+now.strftime('%Y-%m-%d')+'\n\n'
maxlen = max(list(map(len,names))) + 2
outstr += '\n'.join([x.ljust(maxlen) + y for x,y in zip(names, values)])
# precious metals prices
outstr += '\n\n# Precious metals prices from http://services.packetizer.com/spotprices/\n\n'
try:
spotprices = ET.parse(urllib.request.urlopen('http://services.packetizer.com/spotprices/?f=xml'))
except IOError as exc:
sys.stderr.write('Error connecting to spotprices server. {0}\n'.format(exc))
sys.exit(1)
metals = ['gold','platinum','silver']
for metal in metals:
outstr += '{0} {1} US$/troyounce\n'.format((metal+'price').ljust(15), spotprices.find(metal).text)
try:
if outfile == '-':
info = codecs.lookup('utf8')
outfile = codecs.StreamReaderWriter(sys.stdout, info.streamreader, info.streamwriter)
else:
outfile = codecs.open(outfile,'w','utf8')
except IOError as exc:
sys.stderr.write('Unable to write to output file. {0}\n'.format(exc))
sys.exit(1)
outfile.write(outstr.replace('\n',os.linesep))
# In python3, open(outfile,mode='w',encoding='utf8') should work
# and then the explicit newline handling won't be needed
units-2.12/Makefile.Win 0000664 0001750 0001750 00000006601 12316637514 014267 0 ustar adrian adrian # Makefile for units, a program for units conversion
# created for Microsoft Visual C/C++ under Microsoft Windows(R)
#
# Copyright (C) 1996, 1997, 1999, 2005, 2006, 2012, 2013, 2014
# Free Software Foundation, Inc
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
#
#
# The units program was written by Adrian Mariano (adrianm@gnu.org).
# This makefile was written by Adrian Mariano and Jeff Conrad
# (jeff_conrad@msn.com), and tested with Microsoft Visual C/C++ 6.0,
# 9.0, and 10.0 under Windows XP SP3.
# Change these to suit the system configuration
# Normal location for 32-bit executable on 64-bit system
# ProgFilesDir = %ProgramFiles(x86)%
# Normal location
ProgFilesDir = %ProgramFiles%
bindir = "$(ProgFilesDir)\GNU\units"
datadir = "$(ProgFilesDir)\GNU\units"
srcdir = .
# These are for Microsoft Visual C; edit to suit for other compilers.
# Do NOT give the 'Za' flag with MSVC.
CC = cl
CFLAGS = /O2 /W3 /nologo
OBJS = units.obj getopt.obj getopt1.obj parse.obj
CDEFS = /DNO_SETENV /DNO_ISFINITE /D_CRT_SECURE_NO_WARNINGS
UDEFS = /DUNITSFILE=\"definitions.units\" /DLOCALEMAP=\"locale_map.txt\"
units.exe: $(OBJS)
$(CC) $(CFLAGS) $(CDEFS) $(UDEFS) $(OBJS) $(LIBS)
units.obj: units.c units.h
getopt.obj: getopt.c
$(CC) $(CFLAGS) $(CDEFS) /c getopt.c
getopt1.obj: getopt1.c getopt.h
$(CC) $(CFLAGS) $(CDEFS) /c getopt1.c
units.obj: units.c
$(CC) $(CFLAGS) $(CDEFS) $(UDEFS) /c units.c
parse.obj: parse.tab.c units.h
$(CC) $(CFLAGS) $(CDEFS) /c parse.tab.c
del /f/q parse.obj
rename parse.tab.obj parse.obj
showdest:
@echo datadir=$(datadir) & echo bindir=$(bindir)
@if not exist "$(ProgFilesDir)" \
echo '$(ProgFilesDir)' does not exist and will be created
currency2:
copy /y units_cur2 units_cur.py
currency3:
copy /y units_cur3 units_cur.py
installprog: units.exe
$(srcdir)\winmkdirs $(bindir) $(datadir)
copy /y units.exe $(bindir)
copy /y definitions.units $(datadir)
copy /y currency.units $(datadir)
copy /y locale_map.txt $(datadir)
copy /y unitsfile.ico $(datadir)
copy /y unitsprog.ico $(datadir)
cacls $(datadir)\definitions.units /e /g Users:c
cacls $(datadir)\definitions.units /e /g "Power Users":c
cacls $(datadir)\currency.units /e /g Users:c
cacls $(datadir)\currency.units /e /g "Power Users":c
if exist units_cur.py ( \
copy /y units_cur.py $(datadir) & \
cacls $(datadir)\units_cur.py /e /g Users:c & \
cacls $(datadir)\units_cur.py /e /g "Power Users":c \
)
assoc .units=Units.DataFile
# change this if you want a different editor for units data files
for %%i in (notepad.exe) do \
if exist %%~$$PATH:i (ftype Units.DataFile="%%~$$PATH:i" "%1") \
else (ftype Units.DataFile=notepad.exe "%1")
reg add "HKCR\Units.DataFile\DefaultIcon" /f /ve /d $(datadir)\unitsfile.ico /t REG_SZ
clean:
del /f/q $(OBJS)
units-2.12/ChangeLog 0000664 0001750 0001750 00000034305 12407773204 013645 0 ustar adrian adrian 2014-09-22 Adrian Mariano
* units.c (readunits): changed comment processing to happen before
unicode validity check, so that comments can contain bogus unicode
(if desired).
2014-03-28 Adrian Mariano
* units.c (main): Changed getprogname->getprogramname to avoid
CYGWIN conflict.
2014-01-23 Adrian Mariano
* units.c (processargs): Only print error message for invalid
entries plus the short message on how to get longer help.
2014-01-03 Adrian Mariano
* parse.y: Switch to %parse-param and %lex-param so that parser
will work with Bison 3.0.
2013-12-20 Adrian Mariano
* units.c: Put functions into hash table like the table used for
prefixes.
* units.c (unitpower): Convert exponents to rationals using new
function float2rat. This enables support for rational exponents
with numerators larger than 1.
* units.c (completeunits): Rewrote this function to handle hashed
functions as well as prefixes and built in functions.
2011-01-23 Adrian Mariano
* parse.y (yylex): Tweaked scanner to raise a new error (BADNUMBER)
when a number is immediately followed by more numeric characters.
This prevents things like 1.2.3 and 1..2 which were both legal and
had possibly unexpected parsings before. Added new error code to
units.h and new error message to units.c.
2010-05-20 Adrian Mariano
* units.c: Added utf8 support. Added code to check for !utf8 in
units.dat. Added better checking for locale. Added strwidth() to
determine with of a utf8 string, and corrected code to use this
function where appropriate.
2009-12-05 Adrian Mariano
* units.c (rootunit): Fixed bug (n & 1==0) is always false
* Numerous minor changes for eliminating warnings with -Wall
2009-10-03 Adrian Mariano
* units.c (main): Changed RL_READLINE_VERSION test from > to >=.
2007-05-18 adrian
* units.c (personalunitsfile): Added personalunitsfile() function
to find ~/.units.dat if it exists. Added code in main() to load
this file (first) when no -f specifications occur.
(tryallunits): Modified to perform searching either for
conformable units or for text matching units. This required
changes to addtolist() as well.
* parse.y: Added entry to support x^-y when - is not a multiply
operator. Added MULTSTAR type and support for lower multiply
precedence for '*'. Added special check for '**' operator as the
old code didn't work.
2006-02-26 adrian
* units.c: Added -1/--one-line option to display one line of
output only.
* units.c: Added --compact option to print output with only the
conversion factor.
* units.c: Changed verbose variable. Now it is 1 for normal
output, zero for less output and 2 for more verbose output. The
--compact option sets it to zero, and --verbose sets it to 2. The
--terse option now simply sets other options.
2005-09-10 adrian
* parse.y: Declared err as static and added %name-prefix to parser
to make it possible to use units as a library. Note that
declaring err as static also averts a bus error on the Intel Mac.
2004-12-12 adrian
* units.c (checkunits): Added check for units that use '-' as a
binary operator. These units will act differently depending on
the way the program is invoked, so print a warning.
* units.c (compareproducts): Modified to use a pointer to a function
to decide whether a unit should be regarded as dimensionless. Added
functions ignore_dimless(), ignore_primitive() and ignore_nothing()
to use for invoking compareproducts. Modified compareunits to take
this parameter as well.
2004-06-20 Adrian Mariano
* parse.y: Added MINUS token and changed lexer to treat '-'
according to the global variable minusminus either as MINUS or in
the old fashion as MULTMINUS.
* parse.y (funcunit): Added call to freeunit() to close memory leak.
* units.c (compareproducts): Altered this function to use
isdimless() when comparing units so that dimensionless units can
be ignored in the comparison. Added isdimless() which checks
whether a unit is defined as NODIM.
2003-12-04 Adrian Mariano
* units.c (lookupunit): Added check for -ies plural
2003-09-20 Adrian Mariano
* units.c (readunits): Wrote in a file to capture error messages,
pass back an error return instead of calling exit(), do included
units files with "!include", give error on nested "!locale"
statements.
2003-05-09 Adrian Mariano
* units.c: (readunits): Added error checking for function and
prefix names.
2002-05-06 Adrian Mariano
* units.c (reduceunit): The last change to reduceunit was screwed
up. Corrected it.
2001-11-26 Adrian Mariano
* units.c (readunits): Added locale checks to support the
'!locale' syntax in units.dat.
* configure.in: Added --enable-path-search option which replaces
the use of an empty datadir for specifying path searching.
2001-08-30 Adrian Mariano
* units.c (reduceunit): Separated two calls to reduceproduct().
This fixes a bug where "Unit reduction error" occurs instead of
"Unknown unit".
2001-08-17 Adrian Mariano
* units.c (tryallunits): Added signal() calls to ignore the
SIGPIPE signal and hopefully prevent premature termination.
2000-05-28 Adrian Mariano
* units.c (addtolist): Modified tryallunits() to search function
definitions and produce a sorted list, piped through the pager.
Modified ishelpquery to invoke ishelpquery to produce a list.
2000-04-18 Adrian Mariano
* units.c (fgetscont): Added fix for backslash at the end of the
buffer.
2000-04-13 Adrian Mariano
* units.c (readunits): Set "userfile" when a path search is
performed so that "help" can find the data file.
(ishelpquery): Modified to find functions and prefixes.
2000-04-12 Adrian Mariano
* units.c (ishelpquery): Wrote new function to print help messages
by invoking a pager on units.dat. This required new field in
unitlist structure, and code in main() to check for the "help"
command.
2000-04-10 Adrian Mariano
* parse.y: rewrote parser rules for correct unary '-'.
* units.c (showdefinition): Substantially simplified and made
correct for expressions that start with an operator (/ or -).
2000-04-09 Adrian Mariano
* units.c (isfunction): Fixed call to removepadding()
2000-02-12 Adrian Mariano
* units.c (fgetscont): Fixed buffer full test
1999-04-27 Adrian Mariano
* units.c (addsubunit,addsubunitlist): Changed overflow test.
Mon Aug 17 13:12:01 1998 Adrian Mariano
* units.c (addunit): Added declaration for handlesum() so that it
isn't called before being declared. Moved handlesum down the code
past completereduce() so that handlesum doesn't call
completereduce() before its definition.
Sun Mar 8 10:08:56 1998 Adrian Mariano
* units.c (main): Set rl_basic_word_break_characters to delimit
words properly for unit completion.
Mon Jun 9 19:12:08 1997 Adrian Mariano
* units.c (lookupunit): Switched order of prefix and plural
handling so that plurals are handled first. (This fixes the
problem of "pints" being interpreted as p- plus ints.)
Sun Apr 6 01:01:24 1997 Adrian Mariano
* units.c (removepadding): Added check for zero length strings.
This caused units to hang when invoked with arguments that
consisted only of whitespace.
Mon Mar 10 19:23:21 1997 Adrian Mariano
* units.c: Changed 2 strdup() calls into dupstr() calls.
Sun Mar 2 18:02:16 1997 Adrian Mariano
* units.c: replaced sscanf with strtod affecting numlength() and
addnumber(). This circumvents a bug in NeXT's C library and
yields simpler code.
Wed Feb 12 22:28:42 1997 Adrian Mariano
* units.c (showanswer): Fixed to give slightly better display when
verbose mode is active.
Tue Jan 21 18:51:58 1997 Adrian Mariano
* units.c: Changed showanswer() to convert reciprocal units.
Added -s,--strict option to disable this conversion.
Mon Jan 13 20:37:26 1997 Adrian Mariano
* units.c: Added addnumber() because recursive call to addunit()
was causing problems with strtok.
Tue Dec 31 00:57:42 1996 Adrian Mariano
* units.c (prefixhash): Changed to AND with 127 because signed
chars seem to be causing segmentation faults with 8 bit
characters. Changed size of the table to 128 to correspond.
Thu Dec 26 13:54:59 1996 Adrian Mariano
* units.c (completeunits): Added 1 to mymalloc() call so there is
enough space. (This fixes the tab bug.)
Mon Dec 9 23:46:27 1996 Adrian Mariano
* unit.c (addunit): Changed logic for calling handlesum() to check
that the character immediately before the '+' is not an 'e' since
this would probably be an exponent.
Mon Dec 7 10:47:43 1996 Adrian Mariano
* units.c (lookupunit): Added tempbuf variable to prevent problems
when the output from one call to lookupunit is used as input to a
later call to lookupunit.
* units.c: Changed main() and processargs() to allow invoking
units with just one unit specified on the command line.
Tue Dec 3 14:19:33 1996 Adrian Mariano
* units.c: added verbose option, changed showanswer() to give
verbose display, removed first argument from showunit(), added new
function removepadding() to trim whitespace.
* New file: texi2man, a perl script for converting the texinfo
documentation into the man page format. Makefile.in changed to
generate units.man from units.texinfo.
Mon Dec 2 14:10:56 1996 Adrian Mariano
* units.c: New functions handlesum(), addsubunitlist(), and
productoverflow().
(addunit): Call handlesum() if there are '+' characters in the
string to be added. This handles sums of conformable units.
Added free() calls to free savescr when returning with an error.
Sun Dec 1 17:30:52 1996 Adrian Mariano
* units.c: Added isblank() and showdefinition(). Changed main()
to call showdefinition if the second unit entered is blank. Also
changed the loop to re-prompt the user for the first unit until
something nonblank is entered. Changed showunit() to take two
arguments.
Wed Nov 27 23:08:33 1996 Adrian Mariano
* units.c: Added function completeunits() for doing completion
when readline is in use.
* makefile.in: added support for LDFLAGS.
* units.c (lookupunits): Added tests to avoid trying plurals on
one character long base units.
Fri Nov 22 19:25:23 1996 Kaveh R. Ghazi
* Makefile.in, configure.in, units.c: add ansi2knr support.
* New files: aclocal.m4, ansi2knr.1 and ansi2knr.c.
Fri Nov 22 10:33:43 1996 Adrian Mariano
* units.c: Added removespaces() function called from addunits() to
remove spaces around '^' characters so the user doesn't have to be
so careful.
Thu Nov 21 23:39:09 1996 Adrian Mariano
* units.c (lookupunit): Added check to return the input if it is a
number. This was made necessary by the change in the handling of
numbers which broke the '^' operator on numbers.
Thu Nov 21 15:22:40 1996 Adrian Mariano
* units.c (numlength): Changed test for sscanf to require a return
value of exactly 1. For some reason, sscanf sometimes returns -1
instead of 0 when no fields were read.
Thu Nov 21 09:17:26 1996 Adrian Mariano
* Makefile.in: Added ALL_CFLAGS so that CFLAGS can be used by the
user.
* configure.in: Added fix to look for ncurses library to go with
readline. (Required by some linux version.)
Wed Nov 20 14:03:22 1996 Adrian Mariano
* configure.in: Added check for const support.
* Makefile.in: added VPATH, fixed a few places where $(srcdir) was
needed, fixed the install targets to create directories if
necessary by calling mkinstalldirs. Fixed man pages install
target.
Sun Nov 17 00:05:12 1996 Adrian Mariano
* units.c: Added numlength() to handle "numbers" with multiple 'e'
or '.' characters. Changed number evaluation in addunit() to do
something reasonable when multiple '|' characters appear. Now
number evaluation is done by sscanf() instead of atof(). Removed
handling of numbers with no trailing space from lookupunit() and
added it to addunit() with a recursive call.
Thu Nov 1 16:18:08 1996 Adrian Mariano
* units.c: Fixed up portability for string.h, stdlib.h. Added
declarations for string functions and atof().
* units.c: Removed calls to tolower() since they turned out to be
unportable.
Sun Sep 8 10:19:43 1996 Adrian Mariano
* units.c: Added long options, made option flag variables global.
* units.c: Added freeunit() function to free units (which was
never done), and uncommented two free() calls in cancelunit().
* units.c: Added processargs() function to tidy things up.
Thu Sep 5 01:18:52 1996 Adrian Mariano
* units.c: Removed all the static char * buffers and added
support for readline(). Added growbuffer() and fgetslong() and
getuser().
* units.c (readunits): Rewrote parsing to be cleaner and to remove
trailing white space in units.
Copyright (C) 1996, 1997, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006
Free Software Foundation, Inc
units-2.12/install-sh 0000775 0001750 0001750 00000033255 12320330320 014060 0 ustar adrian adrian #!/bin/sh
# install - install a program, script, or datafile
scriptversion=2011-11-20.07; # UTC
# This originates from X11R5 (mit/util/scripts/install.sh), which was
# later released in X11R6 (xc/config/util/install.sh) with the
# following copyright and license.
#
# Copyright (C) 1994 X Consortium
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to
# deal in the Software without restriction, including without limitation the
# rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
# sell copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
# AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC-
# TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
#
# Except as contained in this notice, the name of the X Consortium shall not
# be used in advertising or otherwise to promote the sale, use or other deal-
# ings in this Software without prior written authorization from the X Consor-
# tium.
#
#
# FSF changes to this file are in the public domain.
#
# Calling this script install-sh is preferred over install.sh, to prevent
# 'make' implicit rules from creating a file called install from it
# when there is no Makefile.
#
# This script is compatible with the BSD install script, but was written
# from scratch.
nl='
'
IFS=" "" $nl"
# set DOITPROG to echo to test this script
# Don't use :- since 4.3BSD and earlier shells don't like it.
doit=${DOITPROG-}
if test -z "$doit"; then
doit_exec=exec
else
doit_exec=$doit
fi
# Put in absolute file names if you don't have them in your path;
# or use environment vars.
chgrpprog=${CHGRPPROG-chgrp}
chmodprog=${CHMODPROG-chmod}
chownprog=${CHOWNPROG-chown}
cmpprog=${CMPPROG-cmp}
cpprog=${CPPROG-cp}
mkdirprog=${MKDIRPROG-mkdir}
mvprog=${MVPROG-mv}
rmprog=${RMPROG-rm}
stripprog=${STRIPPROG-strip}
posix_glob='?'
initialize_posix_glob='
test "$posix_glob" != "?" || {
if (set -f) 2>/dev/null; then
posix_glob=
else
posix_glob=:
fi
}
'
posix_mkdir=
# Desired mode of installed file.
mode=0755
chgrpcmd=
chmodcmd=$chmodprog
chowncmd=
mvcmd=$mvprog
rmcmd="$rmprog -f"
stripcmd=
src=
dst=
dir_arg=
dst_arg=
copy_on_change=false
no_target_directory=
usage="\
Usage: $0 [OPTION]... [-T] SRCFILE DSTFILE
or: $0 [OPTION]... SRCFILES... DIRECTORY
or: $0 [OPTION]... -t DIRECTORY SRCFILES...
or: $0 [OPTION]... -d DIRECTORIES...
In the 1st form, copy SRCFILE to DSTFILE.
In the 2nd and 3rd, copy all SRCFILES to DIRECTORY.
In the 4th, create DIRECTORIES.
Options:
--help display this help and exit.
--version display version info and exit.
-c (ignored)
-C install only if different (preserve the last data modification time)
-d create directories instead of installing files.
-g GROUP $chgrpprog installed files to GROUP.
-m MODE $chmodprog installed files to MODE.
-o USER $chownprog installed files to USER.
-s $stripprog installed files.
-t DIRECTORY install into DIRECTORY.
-T report an error if DSTFILE is a directory.
Environment variables override the default commands:
CHGRPPROG CHMODPROG CHOWNPROG CMPPROG CPPROG MKDIRPROG MVPROG
RMPROG STRIPPROG
"
while test $# -ne 0; do
case $1 in
-c) ;;
-C) copy_on_change=true;;
-d) dir_arg=true;;
-g) chgrpcmd="$chgrpprog $2"
shift;;
--help) echo "$usage"; exit $?;;
-m) mode=$2
case $mode in
*' '* | *' '* | *'
'* | *'*'* | *'?'* | *'['*)
echo "$0: invalid mode: $mode" >&2
exit 1;;
esac
shift;;
-o) chowncmd="$chownprog $2"
shift;;
-s) stripcmd=$stripprog;;
-t) dst_arg=$2
# Protect names problematic for 'test' and other utilities.
case $dst_arg in
-* | [=\(\)!]) dst_arg=./$dst_arg;;
esac
shift;;
-T) no_target_directory=true;;
--version) echo "$0 $scriptversion"; exit $?;;
--) shift
break;;
-*) echo "$0: invalid option: $1" >&2
exit 1;;
*) break;;
esac
shift
done
if test $# -ne 0 && test -z "$dir_arg$dst_arg"; then
# When -d is used, all remaining arguments are directories to create.
# When -t is used, the destination is already specified.
# Otherwise, the last argument is the destination. Remove it from $@.
for arg
do
if test -n "$dst_arg"; then
# $@ is not empty: it contains at least $arg.
set fnord "$@" "$dst_arg"
shift # fnord
fi
shift # arg
dst_arg=$arg
# Protect names problematic for 'test' and other utilities.
case $dst_arg in
-* | [=\(\)!]) dst_arg=./$dst_arg;;
esac
done
fi
if test $# -eq 0; then
if test -z "$dir_arg"; then
echo "$0: no input file specified." >&2
exit 1
fi
# It's OK to call 'install-sh -d' without argument.
# This can happen when creating conditional directories.
exit 0
fi
if test -z "$dir_arg"; then
do_exit='(exit $ret); exit $ret'
trap "ret=129; $do_exit" 1
trap "ret=130; $do_exit" 2
trap "ret=141; $do_exit" 13
trap "ret=143; $do_exit" 15
# Set umask so as not to create temps with too-generous modes.
# However, 'strip' requires both read and write access to temps.
case $mode in
# Optimize common cases.
*644) cp_umask=133;;
*755) cp_umask=22;;
*[0-7])
if test -z "$stripcmd"; then
u_plus_rw=
else
u_plus_rw='% 200'
fi
cp_umask=`expr '(' 777 - $mode % 1000 ')' $u_plus_rw`;;
*)
if test -z "$stripcmd"; then
u_plus_rw=
else
u_plus_rw=,u+rw
fi
cp_umask=$mode$u_plus_rw;;
esac
fi
for src
do
# Protect names problematic for 'test' and other utilities.
case $src in
-* | [=\(\)!]) src=./$src;;
esac
if test -n "$dir_arg"; then
dst=$src
dstdir=$dst
test -d "$dstdir"
dstdir_status=$?
else
# Waiting for this to be detected by the "$cpprog $src $dsttmp" command
# might cause directories to be created, which would be especially bad
# if $src (and thus $dsttmp) contains '*'.
if test ! -f "$src" && test ! -d "$src"; then
echo "$0: $src does not exist." >&2
exit 1
fi
if test -z "$dst_arg"; then
echo "$0: no destination specified." >&2
exit 1
fi
dst=$dst_arg
# If destination is a directory, append the input filename; won't work
# if double slashes aren't ignored.
if test -d "$dst"; then
if test -n "$no_target_directory"; then
echo "$0: $dst_arg: Is a directory" >&2
exit 1
fi
dstdir=$dst
dst=$dstdir/`basename "$src"`
dstdir_status=0
else
# Prefer dirname, but fall back on a substitute if dirname fails.
dstdir=`
(dirname "$dst") 2>/dev/null ||
expr X"$dst" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$dst" : 'X\(//\)[^/]' \| \
X"$dst" : 'X\(//\)$' \| \
X"$dst" : 'X\(/\)' \| . 2>/dev/null ||
echo X"$dst" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'
`
test -d "$dstdir"
dstdir_status=$?
fi
fi
obsolete_mkdir_used=false
if test $dstdir_status != 0; then
case $posix_mkdir in
'')
# Create intermediate dirs using mode 755 as modified by the umask.
# This is like FreeBSD 'install' as of 1997-10-28.
umask=`umask`
case $stripcmd.$umask in
# Optimize common cases.
*[2367][2367]) mkdir_umask=$umask;;
.*0[02][02] | .[02][02] | .[02]) mkdir_umask=22;;
*[0-7])
mkdir_umask=`expr $umask + 22 \
- $umask % 100 % 40 + $umask % 20 \
- $umask % 10 % 4 + $umask % 2
`;;
*) mkdir_umask=$umask,go-w;;
esac
# With -d, create the new directory with the user-specified mode.
# Otherwise, rely on $mkdir_umask.
if test -n "$dir_arg"; then
mkdir_mode=-m$mode
else
mkdir_mode=
fi
posix_mkdir=false
case $umask in
*[123567][0-7][0-7])
# POSIX mkdir -p sets u+wx bits regardless of umask, which
# is incompatible with FreeBSD 'install' when (umask & 300) != 0.
;;
*)
tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$
trap 'ret=$?; rmdir "$tmpdir/d" "$tmpdir" 2>/dev/null; exit $ret' 0
if (umask $mkdir_umask &&
exec $mkdirprog $mkdir_mode -p -- "$tmpdir/d") >/dev/null 2>&1
then
if test -z "$dir_arg" || {
# Check for POSIX incompatibilities with -m.
# HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or
# other-writable bit of parent directory when it shouldn't.
# FreeBSD 6.1 mkdir -m -p sets mode of existing directory.
ls_ld_tmpdir=`ls -ld "$tmpdir"`
case $ls_ld_tmpdir in
d????-?r-*) different_mode=700;;
d????-?--*) different_mode=755;;
*) false;;
esac &&
$mkdirprog -m$different_mode -p -- "$tmpdir" && {
ls_ld_tmpdir_1=`ls -ld "$tmpdir"`
test "$ls_ld_tmpdir" = "$ls_ld_tmpdir_1"
}
}
then posix_mkdir=:
fi
rmdir "$tmpdir/d" "$tmpdir"
else
# Remove any dirs left behind by ancient mkdir implementations.
rmdir ./$mkdir_mode ./-p ./-- 2>/dev/null
fi
trap '' 0;;
esac;;
esac
if
$posix_mkdir && (
umask $mkdir_umask &&
$doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir"
)
then :
else
# The umask is ridiculous, or mkdir does not conform to POSIX,
# or it failed possibly due to a race condition. Create the
# directory the slow way, step by step, checking for races as we go.
case $dstdir in
/*) prefix='/';;
[-=\(\)!]*) prefix='./';;
*) prefix='';;
esac
eval "$initialize_posix_glob"
oIFS=$IFS
IFS=/
$posix_glob set -f
set fnord $dstdir
shift
$posix_glob set +f
IFS=$oIFS
prefixes=
for d
do
test X"$d" = X && continue
prefix=$prefix$d
if test -d "$prefix"; then
prefixes=
else
if $posix_mkdir; then
(umask=$mkdir_umask &&
$doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir") && break
# Don't fail if two instances are running concurrently.
test -d "$prefix" || exit 1
else
case $prefix in
*\'*) qprefix=`echo "$prefix" | sed "s/'/'\\\\\\\\''/g"`;;
*) qprefix=$prefix;;
esac
prefixes="$prefixes '$qprefix'"
fi
fi
prefix=$prefix/
done
if test -n "$prefixes"; then
# Don't fail if two instances are running concurrently.
(umask $mkdir_umask &&
eval "\$doit_exec \$mkdirprog $prefixes") ||
test -d "$dstdir" || exit 1
obsolete_mkdir_used=true
fi
fi
fi
if test -n "$dir_arg"; then
{ test -z "$chowncmd" || $doit $chowncmd "$dst"; } &&
{ test -z "$chgrpcmd" || $doit $chgrpcmd "$dst"; } &&
{ test "$obsolete_mkdir_used$chowncmd$chgrpcmd" = false ||
test -z "$chmodcmd" || $doit $chmodcmd $mode "$dst"; } || exit 1
else
# Make a couple of temp file names in the proper directory.
dsttmp=$dstdir/_inst.$$_
rmtmp=$dstdir/_rm.$$_
# Trap to clean up those temp files at exit.
trap 'ret=$?; rm -f "$dsttmp" "$rmtmp" && exit $ret' 0
# Copy the file name to the temp name.
(umask $cp_umask && $doit_exec $cpprog "$src" "$dsttmp") &&
# and set any options; do chmod last to preserve setuid bits.
#
# If any of these fail, we abort the whole thing. If we want to
# ignore errors from any of these, just make sure not to ignore
# errors from the above "$doit $cpprog $src $dsttmp" command.
#
{ test -z "$chowncmd" || $doit $chowncmd "$dsttmp"; } &&
{ test -z "$chgrpcmd" || $doit $chgrpcmd "$dsttmp"; } &&
{ test -z "$stripcmd" || $doit $stripcmd "$dsttmp"; } &&
{ test -z "$chmodcmd" || $doit $chmodcmd $mode "$dsttmp"; } &&
# If -C, don't bother to copy if it wouldn't change the file.
if $copy_on_change &&
old=`LC_ALL=C ls -dlL "$dst" 2>/dev/null` &&
new=`LC_ALL=C ls -dlL "$dsttmp" 2>/dev/null` &&
eval "$initialize_posix_glob" &&
$posix_glob set -f &&
set X $old && old=:$2:$4:$5:$6 &&
set X $new && new=:$2:$4:$5:$6 &&
$posix_glob set +f &&
test "$old" = "$new" &&
$cmpprog "$dst" "$dsttmp" >/dev/null 2>&1
then
rm -f "$dsttmp"
else
# Rename the file to the real destination.
$doit $mvcmd -f "$dsttmp" "$dst" 2>/dev/null ||
# The rename failed, perhaps because mv can't rename something else
# to itself, or perhaps because mv is so ancient that it does not
# support -f.
{
# Now remove or move aside any old file at destination location.
# We try this two ways since rm can't unlink itself on some
# systems and the destination file might be busy for other
# reasons. In this case, the final cleanup might fail but the new
# file should still install successfully.
{
test ! -f "$dst" ||
$doit $rmcmd -f "$dst" 2>/dev/null ||
{ $doit $mvcmd -f "$dst" "$rmtmp" 2>/dev/null &&
{ $doit $rmcmd -f "$rmtmp" 2>/dev/null; :; }
} ||
{ echo "$0: cannot unlink or rename $dst" >&2
(exit 1); exit 1
}
} &&
# Now rename the file to the real destination.
$doit $mvcmd "$dsttmp" "$dst"
}
fi || exit 1
trap '' 0
fi
done
# Local variables:
# eval: (add-hook 'write-file-hooks 'time-stamp)
# time-stamp-start: "scriptversion="
# time-stamp-format: "%:y-%02m-%02d.%02H"
# time-stamp-time-zone: "UTC"
# time-stamp-end: "; # UTC"
# End:
units-2.12/units.man 0000664 0001750 0001750 00000324315 12607015443 013731 0 ustar adrian adrian .\"Do not edit this file. It was created from units.texinfo
.\"using texi2man version 1.01s on Mon Oct 12 16:42:11 EDT 2015
.\"This manual is for GNU Units (version 2.12),
.\"which performs units conversions and units calculations.
.\"
.\"Copyright \(co 1996, 1997, 1999, 2000, 2001, 2002, 2004, 2005, 2007,
.\"2011\-2015 Free Software Foundation, Inc.
.\"
.\"Permission is granted to copy, distribute and/or modify this document
.\"under the terms of the GNU Free Documentation License, Version 1.3 or
.\"any later version published by the Free Software Foundation; with no
.\"Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
.\"Texts.
.TH UNITS 1 "19 March 2014"
.\"
.\" ensure that ASCII circumflex U+005E (^) is not remapped with groff
.if \n(.g .tr ^\(ha
.\" ellipsis: space periods with troff but not with nroff
.if n .ds El \&...
.if t .ds El \&.\ .\ .
.\"
.\" Extensions to man macros
.\"
.\" Constant-width font
.de CW
.hy 0
.if n \{\
.ie \\n(.$>2 \&\\$1'\\$2'\\$3
.el \&'\\$1'\\$2
.\}
.if t \{\
.ie \\n(.$>2 \&\\$1\f(CW\\$2\fR\\$3
.el \&\f(CW\\$1\fR\\$2
.\}
.hy 14
..
.\" Constant-width oblique font
.de CI
.hy 0
.if n \{\
.ie \\n(.$>2 \&\\$1'\fI\\$2\fR'\\$3
.el \&'\fI\\$1\fR'\\$2
.\}
.if t \{\
.ie \\n(.$>2 \&\\$1\f(CI\\$2\fR\\$3
.el \&\f(CI\\$1\fR\\$2
.\}
.hy 14
..
.\" Constant-width font with quotes
.de CQ
.hy 0
.if n \{\
.ie \\n(.$>2 \&\\$1'\\$2'\\$3
.el \&'\\$1'\\$2
.\}
.if t \{\
.ie \\n(.$>2 \&\\$1`\f(CW\\$2\fR'\\$3
.el \&`\f(CW\\$1\fR'\\$2
.\}
.hy 14
..
.\" Display start
.de DS
.hy 0
.if t .in +4n
.if n .in +3n
.nf
..
.\" Display end
.de DE
.fi
.in
.hy 14
..
.\" Example start
.de ES
.DS
.if t \{\
.if '\\$1'S' \{\
.nr Ex 1
.ps -1
.\}
.el .nr Ex 0
.nr mE \\n(.f
.ft CW
.\}
..
.\" Example end
.de EE
.if t \{\
.ft \\n(mE
.if \\n(Ex=1 .ps
.\}
.DE
..
.SH NAME
units \(em unit conversion and calculation program
.PP
.SH SYNOPSIS
.PP
.CW units
.RI [ options ]
.RI [ from-unit
.RI [ to-unit ]]
.PP
.SH DESCRIPTION
The
.CW "units"
program converts quantities expressed in various
systems of measurement to their equivalents in other systems of
measurement. Like many similar programs, it can handle multiplicative
scale changes. It can also handle nonlinear conversions such as
Fahrenheit to
Celsius;
see \fITemperature Conversions\fP.
The program can also perform conversions from and to sums of
units, such as converting between meters and feet plus inches.
.PP
Basic operation is simple: you enter the units that you want to convert
\fIfrom\fP and the units that you want to convert \fIto\fP.
You can use the program interactively with prompts, or you can use it
from the command line.
.PP
Beyond simple unit conversions,
.CW "units"
can be used as a
general-purpose scientific calculator that keeps track of units in its
calculations. You can form arbitrary complex mathematical expressions
of dimensions including sums, products, quotients, powers, and even roots
of dimensions. Thus you can ensure accuracy and dimensional consistency
when working with long expressions that involve many different units
that may combine in complex ways; for an illustration,
see \fIComplicated Unit Expressions\fP.
.PP
The units are defined in an external data file. You can use the
extensive data file that comes with this program, or you can
provide your own data file to suit your needs. You can also use your
own data file to supplement the standard data file.
.PP
You can change the default behavior of
.CW "units"
with various
options given on the command line. See \fIInvoking Units\fP for a
description of the available options.
.PP
.SH INTERACTING WITH \f(BIUNITS\fP
To invoke units for interactive use, type
.CI "units"
at your shell
prompt. The program will print something like this:
.PP
.ES
Currency exchange rates from www.timegenie.com on 2014-03-05
2860 units, 109 prefixes, 85 nonlinear units
You have:
.EE
.PP
At the
.CQ "You\ have:"
prompt, type the quantity and units that
you are converting \fIfrom\fP. For example, if you want to convert ten
meters to feet, type
.CI "10 meters" .
Next,
.CW "units"
will print
.CQ "You\ want:" .
You should type the units you want to convert
\fIto\fP. To convert to feet, you would type
.CI "feet" .
If the
.CW "readline"
library was compiled in then \fItab\fP will
complete unit names. See \fIReadline Support\fP for more information
about
.CW "readline" .
To quit the program under Unix, press
\fICtrl-C\fP or \fICtrl-D\fP. Under Windows, press \fICtrl-C\fP or
\fICtrl-Z\fP; with the latter, you may also need to press \fIEnter\fP.
.PP
The result will be displayed in two ways. The first line of output,
which is marked with a
.CQ "*"
to indicate multiplication, gives the
result of the conversion you have asked for. The second line of output,
which is marked with a
.CQ "/"
to indicate division, gives the inverse
of the conversion factor. If you convert 10 meters to feet,
.CW "units"
will print
.PP
.ES
* 32.808399
/ 0.03048
.EE
.PP
which tells you that 10 meters equals about 32.8 feet.
The second number gives the conversion in the opposite direction.
In this case, it tells you that 1 foot is equal to about
0.03 dekameters since the dekameter is 10 meters.
It also tells you that 1/32.8 is about 0.03.
.PP
The
.CW "units"
program prints the inverse because sometimes it is a
more convenient number. In the example above, for example, the inverse
value is an exact conversion: a foot is exactly 0.03048 dekameters.
But the number given the other direction is inexact.
.PP
If you convert grains to pounds, you will see the following:
.PP
.ES
You have: grains
You want: pounds
* 0.00014285714
/ 7000
.EE
.PP
From the second line of the output you can immediately see that a grain
is equal to a seven thousandth of a pound. This is not so obvious from
the first line of the output.
If you find the output format confusing, try using the
.CQ "--verbose"
option:
.PP
.ES
You have: grain
You want: aeginamina
grain = 0.00010416667 aeginamina
grain = (1 / 9600) aeginamina
.EE
.PP
If you request a conversion between units that measure reciprocal
dimensions, then
.CW "units"
will display the conversion results with an extra
note indicating that reciprocal conversion has been done:
.PP
.ES
You have: 6 ohms
You want: siemens
reciprocal conversion
* 0.16666667
/ 6
.EE
.PP
Reciprocal conversion can be suppressed by using the
.CQ "--strict"
option.
As usual, use
the
.CQ "--verbose"
option to get more comprehensible output:
.PP
.ES
You have: tex
You want: typp
reciprocal conversion
1 / tex = 496.05465 typp
1 / tex = (1 / 0.0020159069) typp
You have: 20 mph
You want: sec/mile
reciprocal conversion
1 / 20 mph = 180 sec/mile
1 / 20 mph = (1 / 0.0055555556) sec/mile
.EE
.PP
If you enter incompatible unit types, the
.CW "units"
program will
print a message indicating that the units are not conformable and
it will display the reduced form for each unit:
.PP
.ES
You have: ergs/hour
You want: fathoms kg^2 / day
conformability error
2.7777778e-11 kg m^2 / sec^3
2.1166667e-05 kg^2 m / sec
.EE
.PP
If you only want to find the reduced form or definition of a unit,
simply press \fIEnter\fP at the
.CQ "You\ want:"
prompt. Here is an
example:
.PP
.ES
You have: jansky
You want:
Definition: fluxunit = 1e-26 W/m^2 Hz = 1e-26 kg / s^2
.EE
.PP
The output from
.CW "units"
indicates that the jansky is defined to be
equal to a fluxunit which in turn is defined to be a certain combination
of watts, meters, and hertz. The fully reduced (and in this case
somewhat more cryptic) form appears on the far right.
.PP
Some named units are treated as dimensionless in some situations.
These units include the radian and steradian. These units will be
treated as equal to 1 in units conversions. Power is equal to torque
times angular velocity. This conversion can only be performed if the
radian is dimensionless.
.PP
.ES
You have: (14 ft lbf) (12 radians/sec)
You want: watts
* 227.77742
/ 0.0043902509
.EE
.PP
It is also possible to compute roots and other non-integer powers of
dimensionless units; this allows computations such as the altitude of
geosynchronous orbit:
.PP
.ES
You have: cuberoot(G earthmass / (circle/siderealday)^2) - earthradius
You want: miles
* 22243.267
/ 4.4957425e-05
.EE
.PP
Named dimensionless units are not treated as dimensionless
in other contexts. They cannot be used as exponents
so for example,
.CQ "meter^radian"
is forbidden.
.PP
If you want a list of options you can type
.CI "?"
at the
.CQ "You\ want:"
prompt. The program will display a list of named
units that are conformable with the unit that you entered at the
.CQ "You\ have:"
prompt above. Conformable unit \fIcombinations\fP
will not appear on this list.
.PP
Typing
.CI "help"
at either prompt displays a short help message.
You can also type
.CI "help"
followed by a unit name. This will
invoke a pager on the units data base at the point where that unit
is defined. You can read the definition and comments that may
give more details or historical information about the unit. (You
can generally quit out of the page by pressing
.CQ "q" .)
.PP
Typing
.CI "search"
\fItext\fP will display a list of all of the units
whose names contain \fItext\fP as a substring along with their definitions.
This may help in the case where you aren't sure of the right unit name.
.PP
.SH USING \f(BIUNITS\fP NON-INTERACTIVELY
The
.CW "units"
program can perform units conversions non-interactively
from the command line. To do this, type the command, type the original
unit expression, and type the new units you want. If a units
expression contains non-alphanumeric characters, you may need to protect
it from interpretation by the shell using single or double quote
characters.
.PP
If you type
.PP
.ES
units "2 liters" quarts
.EE
.PP
then
.CW "units"
will print
.PP
.ES
* 2.1133764
/ 0.47317647
.EE
.PP
and then exit.
The output tells you that 2 liters is about 2.1 quarts, or alternatively that
a quart is about 0.47 times 2 liters.
.PP
If the conversion is successful, then
.CW "units"
will return success (zero)
to the calling environment. If you enter non-conformable
units then
.CW "units"
will print a message giving the reduced form of
each unit and it will return failure (nonzero) to the calling environment.
.PP
When you invoke
.CW "units"
with only one argument, it will print out
the definition of the specified unit. It will return failure if the
unit is not defined and success if the unit is defined.
.PP
.SH UNIT DEFINITIONS
The conversion information is read from a units data file that
is called
.CQ "definitions.units"
and is usually located in
the
.CQ "/usr/share/units"
directory.
If you invoke
.CW "units"
with the
.CQ "-V"
option, it will print
the location of this file.
The default
file includes definitions for all familiar units, abbreviations and
metric prefixes. It also includes many obscure or archaic units.
.PP
Many constants of nature are defined, including these:
.PP
.ES
pi \fRratio of circumference to diameter\fP
c \fRspeed of light\fP
e \fRcharge on an electron\fP
force \fRacceleration of gravity\fP
mole \fRAvogadro's number\fP
water \fRpressure per unit height of water\fP
Hg \fRpressure per unit height of mercury\fP
au \fRastronomical unit\fP
k \fRBoltzman's constant\fP
mu0 \fRpermeability of vacuum\fP
epsilon0 \fRpermittivity of vacuum\fP
G \fRGravitational constant\fP
mach \fRspeed of sound\fP
.EE
.PP
The standard data file includes atomic masses for all of the elements
and numerous other constants. Also included are the densities of
various ingredients used in baking so that
.CQ "2\ cups flour_sifted"
can be converted to
.CQ "grams" .
This is not an exhaustive list.
Consult the units data file to see the complete list, or to see the
definitions that are used.
.PP
The
.CQ "pound"
is a unit of mass. To get force, multiply by the
force conversion unit
.CQ "force"
or use the shorthand
.CQ "lbf" .
(Note that
.CQ "g"
is already taken as the standard abbreviation for
the gram.) The unit
.CQ "ounce"
is also a unit of mass. The fluid
ounce is
.CQ "fluidounce"
or
.CQ "floz" .
When British capacity
units differ from their US counterparts, such as the British Imperial
gallon, the unit is defined both ways with
.CQ "br"
and
.CQ "us"
prefixes. Your locale settings will determine the value of the
unprefixed unit. Currency is prefixed with its country
name:
.CQ "belgiumfranc" ,
.CQ "britainpound" .
.PP
When searching for a unit, if the specified string does not appear
exactly as a unit name, then the
.CW "units"
program will try to
remove a trailing
.CQ "s" ,
.CQ "es" .
Next units will replace a
trailing
.CQ "ies"
with
.CQ "y" .
If that fails,
.CW "units"
will check for a prefix. The database includes all
of the standard metric prefixes. Only one prefix is permitted per
unit, so
.CQ "micromicrofarad"
will fail. However, prefixes can
appear alone with no unit following them, so
.CQ "micro*microfarad"
will work, as will
.CQ "micro microfarad" .
.PP
To find out which units and prefixes are available, read the standard
units data file, which is extensively annotated.
.PP
.SS English Customary Units
English customary units differ in various ways in different
regions. In Britain a complex system of volume measurements featured
different gallons for different materials such as a wine gallon and
ale gallon that different by twenty percent. This complexity was
swept away in 1824 by a reform that created an entirely new gallon,
the British Imperial gallon defined as the volume occupied by ten
pounds of water. Meanwhile in the USA the gallon is derived from the
1707 Winchester wine gallon, which is 231 cubic inches. These gallons
differ by about twenty percent. By default if
.CW "units"
runs in
the
.CQ "en_GB"
locale you will get the British volume measures. If
it runs in the
.CQ "en_US"
locale you will get the US volume
measures. In other locales the default values are the US
definitions. If you wish to force different definitions then set the
environment variable
.CW "UNITS_ENGLISH"
to either
.CQ "US"
or
.CQ "GB"
to set the desired definitions independent of the locale.
.PP
Before 1959, the value of a yard (and other units of measure defined in
terms of it) differed slightly among English-speaking countries. In
1959, Australia, Canada, New Zealand, the United Kingdom, the United
States, and South Africa adopted the Canadian value of 1\ yard =
0.9144\ m (exactly), which was approximately halfway between the
values used by the UK and the US; it had the additional advantage of
making 1\ inch = 2.54\ cm (exactly). This new standard was
termed the \fIInternational Yard\fP. Australia, Canada, and the UK then
defined all customary lengths in terms of the International Yard
(Australia did not define the furlong or rod); because many US land
surveys were in terms of the pre-1959 units, the US continued to define
customary surveyors' units (furlong, chain, rod, and link) in terms of
the previous value for the foot, which was termed the
\fIUS survey foot\fP. The US defined a \fIUS survey mile\fP as 5280 US
survey feet, and defined a \fIstatute mile\fP as a US survey mile. The
US values for these units differ from the international values by about
2\ ppm.
.PP
The
.CW "units"
program uses the international values for these
units; the US values can be obtained by using either the
.CQ "US"
or
the
.CQ "survey"
prefix. In either case, the simple familiar
relationships among the units are maintained, e.g., 1
.CQ "furlong"
=
660
.CQ "ft" ,
and 1
.CQ "USfurlong"
= 660
.CQ "USft" ,
though the
metric equivalents differ slightly between the two cases.
The
.CQ "US"
prefix or the
.CQ "survey"
prefix can also be used to
obtain the US survey mile and the value of the US yard prior to 1959,
e.g.,
.CQ "USmile"
or
.CQ "surveymile"
(but \fInot\fP
.CQ "USsurveymile" ).
To get the US value of the statute mile, use
either
.CQ "USstatutemile"
or
.CQ "USmile" .
.PP
Except for distances that extend over hundreds of miles (such as in the
US State Plane Coordinate System), the differences in the miles are
usually insignificant:
.PP
.ES
You have: 100 surveymile - 100 mile
You want: inch
* 12.672025
/ 0.078913984
.EE
.PP
The pre-1959 UK values for these units can be obtained with the prefix
.CQ "UK" .
.PP
In the US, the acre is officially defined in terms of the US survey
foot, but
.CW "units"
uses a definition based on the international
foot. If you want the official US acre use
.CQ "USacre"
and
similarly use
.CQ "USacrefoot"
for the official US version of that
unit. The difference between these units is about 4 parts per million.
.PP
.SH UNIT EXPRESSIONS
.SS Operators
You can enter more complicated units by combining units with operations
such as multiplication, division, powers, addition, subtraction, and
parentheses for grouping. You can use the customary symbols for these
operators when
.CW "units"
is invoked with its default options.
Additionally,
.CW "units"
supports some extensions, including high
priority multiplication using a space, and a high priority numerical
division operator
.CQ ( "|" )
that can simplify some expressions.
.PP
You multiply units using a space or an asterisk
.CQ ( "*" ).
The next example shows both forms:
.PP
.ES
You have: arabicfoot * arabictradepound * force
You want: ft lbf
* 0.7296
/ 1.370614
.EE
.PP
You can divide units using the slash
.CQ ( "/" )
or with
.CQ "per" :
.PP
.ES
You have: furlongs per fortnight
You want: m/s
* 0.00016630986
/ 6012.8727
.EE
.PP
You can use parentheses for grouping:
.PP
.ES
You have: (1/2) kg / (kg/meter)
You want: league
* 0.00010356166
/ 9656.0833
.EE
.PP
Multiplication using a space has a higher precedence
than division using a slash and is evaluated left to right;
in effect, the first
.CQ "/"
character marks the beginning of the
denominator of a unit expression.
This makes it simple to enter a quotient with several terms in the
denominator:
.CQ "J\ /\ mol\ K" .
The
.CQ "*"
and
.CQ "/"
operators have the same precedence, and are
evaluated left to right; if you multiply with
.CQ "*" ,
you must group
the terms in the denominator with parentheses:
.CQ "J\ /\ (mol\ *\ K)" .
.PP
The higher precedence of the space operator may not always be advantageous.
For example,
.CQ "m/s\ s/day"
is equivalent to
.CQ "m\ /\ s\ s\ day"
and has dimensions of length per time cubed.
Similarly,
.CQ "1/2\ meter"
refers to a unit of reciprocal length
equivalent to 0.5/meter, perhaps not what you would intend if
you entered that expression. The get a half meter you would need to
use parentheses:
.CQ "(1/2)\ meter" .
The
.CQ "*"
operator is convenient for multiplying a sequence of
quotients. For example,
.CQ "m/s\ *\ s/day"
is equivalent to
.CQ "m/day" .
Similarly, you could write
.CQ "1/2\ *\ meter"
to get
half a meter.
.PP
The
.CW "units"
program supports another option for numerical fractions:
you can indicate division of \fInumbers\fP with the vertical bar
.CQ ( "|" ),
so if you wanted half a meter you could write
.CQ "1|2\ meter" .
You cannot use the vertical bar to indicate division of non-numerical
units (e.g.,
.CQ "m|s"
results in an error message).
.PP
Powers of units can be specified using the
.CQ "^"
character, as shown in
the following example, or by simple concatenation of a unit and its
exponent:
.CQ "cm3"
is equivalent to
.CQ "cm^3" ;
if the exponent is more than one digit, the
.CQ "^"
is required.
You can also use
.CQ "**"
as an exponent operator.
.PP
.ES
You have: cm^3
You want: gallons
* 0.00026417205
/ 3785.4118
.EE
.PP
Concatenation only works with a single unit name: if you write
.CQ "(m/s)2" ,
.CW "units"
will treat it as multiplication by 2.
When a unit includes a prefix, exponent operators apply to the
combination, so
.CQ "centimeter3"
gives cubic centimeters. If you
separate the prefix from the unit with any multiplication operator (e.g.,
.CQ "centi meter^3" ),
the prefix is treated as a separate unit, so
the exponent applies only to the unit without the prefix. The second
example is equivalent to
.CQ "centi * (meter^3)" ,
and gives a hundredth
of a cubic meter, not a cubic centimeter. The
.CW "units"
program
is limited internally to products of 99 units; accordingly, expressions
like
.CQ "meter^100"
or
.CQ "joule^34"
(represented internally as
.CQ "kg^34\ m^68\ /\ s^68" )
will fail.
.PP
The
.CQ "|"
operator has the highest precedence, so you can write the square root of
two thirds as
.CQ "2|3^1|2" .
The
.CQ "^"
operator has the second highest precedence, and is
evaluated right to left, as usual:
.PP
.ES
You have: 5 * 2^3^2
You want:
Definition: 2560
.EE
.PP
With a dimensionless base unit, any dimensionless exponent is meaningful
(e.g.,
.CQ "pi^exp(2.371)" ).
Even though angle is sometimes treated as
dimensionless, exponents cannot have dimensions of angle:
.PP
.ES
You have: 2^radian
^
Exponent not dimensionless
.EE
.PP
If the base unit is not dimensionless, the
exponent must be a rational number \fIp\fP/\fIq\fP, and the
dimension of the unit must be a power of \fIq\fP, so
.CQ "gallon^2|3"
works but
.CQ "acre^2|3"
fails. An exponent using the slash
.CQ ( "/" )
operator (e.g.,
.CQ "gallon^(2/3)" )
is also acceptable; the parentheses
are needed because the precedence of
.CQ "^"
is higher than that of
.CQ "/" .
Since
.CW "units"
cannot represent dimensions with
exponents greater than 99, a fully reduced exponent must have
\fIq\fP\ <\ 100. When raising a non-dimensionless unit to a power,
.CW "units"
attempts to convert a decimal exponent to a rational
number with \fIq\fP\ <\ 100. If this is not possible
.CW "units"
displays an error message:
.PP
.ES
You have: ft^1.234
Base unit not dimensionless; rational exponent required
.EE
.PP
A decimal exponent must match its rational representation to machine
precision, so
.CQ "acre^1.5"
works but
.CQ "gallon^0.666"
does not.
.PP
.SS Sums and Differences of Units
You may sometimes want to add values of
different units that are outside the SI.
You may also wish to use
.CW "units"
as a
calculator that keeps track of units. Sums of conformable units are written with
the
.CQ "+"
character, and differences with the
.CQ "-"
character.
.PP
.ES
You have: 2 hours + 23 minutes + 32 seconds
You want: seconds
* 8612
/ 0.00011611705
You have: 12 ft + 3 in
You want: cm
* 373.38
/ 0.0026782366
You have: 2 btu + 450 ft lbf
You want: btu
* 2.5782804
/ 0.38785542
.EE
.PP
The expressions that are added or subtracted must reduce to identical
expressions in primitive units, or an error message will be displayed:
.PP
.ES
You have: 12 printerspoint - 4 heredium
^
Illegal sum of non-conformable units
.EE
.PP
As usual, the precedence for
.CQ "+"
and
.CQ "-"
is lower than that of
the other operators.
A fractional quantity such as 2\ 1/2 cups can be given as
.CQ "(2+1|2) cups" ;
the parentheses are necessary because
multiplication has higher precedence than addition. If you omit the
parentheses,
.CW "units"
attempts to add
.CQ "2"
and
.CQ "1|2 cups" ,
and you get an error message:
.PP
.ES
You have: 2+1|2 cups
^
Illegal sum or difference of non-conformable units
.EE
.PP
The expression could also be correctly written as
.CQ "(2+1/2) cups" .
If you write
.CQ "2\ 1|2 cups"
the space is interpreted as
\fImultiplication\fP so the result is the same as
.CQ "1 cup" .
.PP
The
.CQ "+"
and
.CQ "-"
characters sometimes appears in exponents like
.CQ "3.43e+8" .
This leads to an ambiguity in an expression like
.CQ "3e+2 yC" .
The unit
.CQ "e"
is a small unit of charge, so this
can be regarded as equivalent to
.CQ "(3e+2) yC"
or
.CQ "(3 e)+(2 yC)" .
This ambiguity is resolved by always interpreting
.CQ "+"
and
.CQ "-"
as part
of an exponent if possible.
.PP
.SS Numbers as Units
For
.CW "units" ,
numbers are just another kind of unit. They can
appear as many times as you like and in any order in a unit expression.
For example, to find the volume of a box that is 2 ft by 3 ft by 12 ft
in steres, you could do the following:
.PP
.ES
You have: 2 ft 3 ft 12 ft
You want: stere
* 2.038813
/ 0.49048148
You have: $ 5 / yard
You want: cents / inch
* 13.888889
/ 0.072
.EE
.PP
And the second example shows how the dollar sign in the units conversion
can precede the five. Be careful:
.CW "units"
will interpret
.CQ "$5"
with no space as equivalent to
.CQ "dollar^5" .
.PP
.SS Built-in Functions
Several built-in functions are provided:
.CQ "sin" ,
.CQ "cos" ,
.CQ "tan" ,
.CQ "ln" ,
.CQ "log" ,
.CQ "log2" ,
.CQ "exp" ,
.CQ "acos" ,
.CQ "atan"
and
.CQ "asin" .
The
.CQ "sin" ,
.CQ "cos" ,
and
.CQ "tan"
functions require either a dimensionless argument or an argument with
dimensions of angle.
.PP
.ES
You have: sin(30 degrees)
You want:
Definition: 0.5
You have: sin(pi/2)
You want:
Definition: 1
You have: sin(3 kg)
^
Unit not dimensionless
.EE
.PP
The other functions on the list require dimensionless arguments. The
inverse trigonometric functions return arguments with dimensions of
angle.
.PP
If you wish to take roots of units, you may use the
.CQ "sqrt"
or
.CQ "cuberoot"
functions. These functions require that the argument
have the appropriate root. You can obtain higher roots by using
fractional exponents:
.PP
.ES
You have: sqrt(acre)
You want: feet
* 208.71074
/ 0.0047913202
You have: (400 W/m^2 / stefanboltzmann)^(1/4)
You have:
Definition: 289.80882 K
You have: cuberoot(hectare)
^
Unit not a root
.EE
.PP
.SS Previous Result
You can insert the result of the previous conversion using the
underscore
.CQ ( "_" ).
It is useful when you want to
convert the same input to several different units, for example
.PP
.ES
You have: 2.3 tonrefrigeration
You want: btu/hr
* 27600
/ 3.6231884e-005
You have: _
You want: kW
* 8.0887615
/ 0.12362832
.EE
.PP
Suppose you want to do some deep frying that requires an oil depth of
2\ inches. You have 1/2 gallon of oil, and want to know the
largest-diameter pan that will maintain the required depth. The
nonlinear unit
.CQ "circlearea"
gives the \fIradius\fP of the circle
(see \fIOther Nonlinear Units\fP, for a more detailed description) in SI
units; you want the \fIdiameter\fP in \fIinches\fP:
.PP
.ES
You have: 1|2 gallon / 2 in
You want: circlearea
0.10890173 m
You have: 2 _
You want: in
* 8.5749393
/ 0.1166189
.EE
.PP
In most cases, surrounding white space is optional, so the previous
example could have used
.CQ "2_" .
If
.CQ "_"
follows a non-numerical
unit symbol, however, the space is required:
.PP
.ES
You have: m_
^
Parse error
.EE
.PP
When
.CQ "_"
is followed by a digit, the operation is multiplication
rather than exponentiation, so that
.CQ "_2" ,
is equivalent to
.CQ "_\ *\ 2"
rather than
.CQ "_^2" .
.PP
You can use the
.CQ "_"
symbol any number of times; for example,
.PP
.ES
You have: m
You want:
Definition: 1 m
You have: _ _
You want:
Definition: 1 m^2
.EE
.PP
Using
.CQ "_"
before a conversion has been performed (e.g.,
immediately after invocation) generates an error:
.PP
.if \n(.g .tr '\(aq
.ES
You have: _
^
No previous result; '_' not set
.EE
.if \n(.g .tr ''
.PP
Accordingly,
.CQ "_"
serves no purpose when
.CW "units"
is invoked
non-interactively.
.PP
If
.CW "units"
is invoked with the
.CQ "--verbose"
option
(see \fIInvoking Units\fP), the value of
.CQ "_"
is not expanded:
.PP
.ES
You have: mile
You want: ft
mile = 5280 ft
mile = (1 / 0.00018939394) ft
You have: _
You want: m
_ = 1609.344 m
_ = (1 / 0.00062137119) m
.EE
.PP
You can give
.CQ "_"
at the
.CQ "You\ want:"
prompt, but it
usually is not very useful.
.PP
.SS Complicated Unit Expressions
The
.CW "units"
program is especially helpful in ensuring accuracy
and dimensional consistency when converting lengthy unit expressions.
.if t .ig ++
For example, one form of the Darcy-Weisbach fluid-flow equation is
.RS 5n
.PP
Delta \fIP\fP = (8 / pi)^2 (rho \fIfLQ\fP^2) / \fId\fP^5,
.RE
.PP
where Delta \fIP\fP is the pressure drop, rho is the mass density,
\fIf\fP is the (dimensionless) friction factor, \fIL\fP is the length
of the pipe, \fIQ\fP is the volumetric flow rate, and \fId\fP
is the pipe diameter.
It might be desired to have the equation in the form
.RS 5n
.PP
Delta \fIP\fP = A1 rho \fIfLQ\fP^2 / \fId\fP^5
.RE
.PP
.++
.if n .ig ++
.EQ
delim $$
.EN
For example, one form of the Darcy\-Weisbach fluid-flow equation is
.RS 5n
.PP
.EQ
DELTA P = 8 over pi sup 2 rho fL Q sup 2 over d sup 5 ,
.EN
.RE
.PP
where $DELTA P$ is the pressure drop, $rho$ is the mass density,
$f$ is the (dimensionless) friction factor, $L$ is the length
of the pipe, $Q$ is the volumetric flow rate, and $d$
is the pipe diameter.
It might be desired to have the equation in the form
.RS 5n
.PP
.EQ
DELTA P = A sub 1 rho fL Q sup 2 over d sup 5
.EN
.RE
.PP
.EQ
delim off
.EN
.++
.PP
that accepted the user's normal units; for typical units used in the US,
the required conversion could be something like
.PP
.ES
You have: (8/pi^2)(lbm/ft^3)ft(ft^3/s)^2(1/in^5)
You want: psi
* 43.533969
/ 0.022970568
.EE
.PP
The parentheses allow individual terms in the expression to be entered naturally,
as they might be read from the formula. Alternatively, the
multiplication could be done with the
.CQ "*"
rather than a space;
then parentheses are needed only around
.CQ "ft^3/s"
because of its
exponent:
.PP
.ES
You have: 8/pi^2 * lbm/ft^3 * ft * (ft^3/s)^2 /in^5
You want: psi
* 43.533969
/ 0.022970568
.EE
.PP
Without parentheses, and using spaces for multiplication, the previous
conversion would need to be entered as
.PP
.ES
You have: 8 lb ft ft^3 ft^3 / pi^2 ft^3 s^2 in^5
You want: psi
* 43.533969
/ 0.022970568
.EE
.PP
.SS Backwards Compatibility:
.CQ "*"
and
.CQ "-"
The original
.CW "units"
assigned multiplication a higher
precedence than division using the slash. This differs from the
usual precedence rules, which give multiplication and division equal
precedence, and can be confusing for people who think
of units as a calculator.
.PP
The star operator
.CQ ( "*" )
included in this
.CW "units"
program
has, by default, the same precedence as division,
and hence follows the usual precedence rules. For backwards
compatibility you can invoke
.CW "units"
with the
.CQ "--oldstar"
option. Then
.CQ "*"
has a higher precedence than
division, and the same precedence as multiplication using the space.
.PP
Historically, the hyphen
.CQ ( "-" )
has been used in technical
publications to indicate products of units, and the original
.CW "units"
program treated it as a multiplication operator.
Because
.CW "units"
provides
several other ways to obtain unit products, and because
.CQ "-"
is a
subtraction operator in general algebraic expressions,
.CW "units"
treats the binary
.CQ "-"
as a subtraction operator by default.
For backwards compatibility use the
.CQ "--product"
option, which
causes
.CW "units"
to treat the binary
.CQ "-"
operator as a
product operator. When
.CQ "-"
is a multiplication operator
it has the same precedence as multiplication with a space, giving it a
higher precedence than division.
.PP
When
.CQ "-"
is used as a unary operator it negates its operand.
Regardless of the
.CW "units"
options, if
.CQ "-"
appears after
.CQ "("
or after
.CQ "+"
then it will act as a negation operator. So you can always compute 20
degrees minus 12 minutes by entering
.CQ "20\ degrees + -12\ arcmin" .
You must use this construction when you define new units because you
cannot know what options will be in force when your definition is
processed.
.PP
.SH NONLINEAR UNIT CONVERSIONS
Nonlinear units are represented using functional notation. They make
possible nonlinear unit conversions such as temperature.
.PP
.SS Temperature Conversions
Conversions between temperatures are different from linear conversions
between temperature \fIincrements\fP\(emsee the example below. The
absolute temperature conversions are handled by units starting with
.CQ "temp" ,
and you must use functional notation.
The temperature-increment conversions are done using units starting
with
.CQ "deg"
and they do not require functional notation.
.PP
.ES
You have: tempF(45)
You want: tempC
7.2222222
You have: 45 degF
You want: degC
* 25
/ 0.04
.EE
.PP
Think of
.CQ "tempF(\fIx\fP)"
not as a function but as a notation that
indicates that \fIx\fP should have units of
.CQ "tempF"
attached to
it. See \fIDefining Nonlinear Units\fP. The first conversion shows that if it's 45
degrees Fahrenheit outside, it's 7.2 degrees Celsius. The second
conversion indicates that a change of 45 degrees Fahrenheit corresponds
to a change of 25 degrees Celsius. The conversion from
.CQ "tempF(\fIx\fP)"
is to absolute temperature, so that
.PP
.ES
You have: tempF(45)
You want: degR
* 504.67
/ 0.0019814929
.EE
.PP
gives the same result as
.PP
.ES
You have: tempF(45)
You want: tempR
* 504.67
/ 0.0019814929
.EE
.PP
But if you convert
.CQ "tempF(\fIx\fP)"
to
.CQ "degC" ,
the output is
probably not what you expect:
.PP
.ES
You have: tempF(45)
You want: degC
* 280.37222
/ 0.0035666871
.EE
.PP
The result is the temperature in K, because
.CQ "degC"
is defined as
.CQ "K" ,
the Kelvin. For consistent results, use the
.CQ "temp\fIX\fP"
units
when converting to a temperature rather than converting a temperature
increment.
.PP
The
.CQ "tempC()"
and
.CQ "tempF()"
definitions are limited to
positive absolute temperatures, and giving a value that would result in
a negative absolute temperature generates an error message:
.PP
.ES
You have: tempC(-275)
^
Argument of function outside domain
^
.EE
.PP
.SS Other Nonlinear Units
Some other examples of nonlinear units are numerous different ring
sizes and wire gauges, the grit sizes used for abrasives, the decibel
scale, shoe size, scales for the density of sugar (e.g., baume).
The standard data file also supplies units for computing the area of a
circle and the volume of a sphere. See the standard units data file
for more details.
Wire gauges
with multiple zeroes are signified using negative numbers where two
zeroes is
.CQ "-1" .
Alternatively, you can use the synonyms
.CQ "g00" ,
.CQ "g000" ,
and so on that are defined in the standard units data file.
.PP
.ES
You have: wiregauge(11)
You want: inches
* 0.090742002
/ 11.020255
You have: brwiregauge(g00)
You want: inches
* 0.348
/ 2.8735632
You have: 1 mm
You want: wiregauge
18.201919
You have: grit_P(600)
You want: grit_ansicoated
342.76923
.EE
.PP
The last example shows the conversion from P graded sand paper,
which is the European standard and may be marked ``P600'' on the back,
to the USA standard.
.PP
You can compute the area of a circle using the nonlinear unit,
.CQ "circlearea" .
You can also do this using the circularinch or
circleinch. The next example shows two ways to compute the area of a
circle with a five inch radius and one way to compute the volume of a
sphere with a radius of one meter.
.PP
.ES
You have: circlearea(5 in)
You want: in2
* 78.539816
/ 0.012732395
You have: 10^2 circleinch
You want: in2
* 78.539816
/ 0.012732395
You have: spherevol(meter)
You want: ft3
* 147.92573
/ 0.0067601492
.EE
.PP
The inverse of a nonlinear conversion is indicated by prefixing a tilde
.CQ ( "~" )
to the nonlinear unit name:
.PP
.ES
You have: ~wiregauge(0.090742002 inches)
You want:
Definition: 11
.EE
.PP
You can give a nonlinear unit definition without an argument or
parentheses, and press \fIEnter\fP at the
.CQ "You\ want:"
prompt to
get the definition of a nonlinear unit; if the definition is not valid
for all real numbers, the range of validity is also given. If the
definition requires specific units this information is also
displayed:
.PP
.ES
You have: tempC
Definition: tempC(x) = x K + stdtemp
defined for x >= -273.15
You have: ~tempC
Definition: ~tempC(tempC) = (tempC +(-stdtemp))/K
defined for tempC >= 0 K
You have: circlearea
Definition: circlearea(r) = pi r^2
r has units m
.EE
.PP
To see the definition of the inverse use the
.CQ "~"
notation. In
this case the parameter in the functional definition will
usually be the name of the unit. Note that the inverse for
.CQ "tempC"
shows that it requires units of
.CQ "K"
in the
specification of the allowed range of values.
Nonlinear unit conversions are described in more detail in
\fIDefining Nonlinear Units\fP.
.PP
.SH UNIT LISTS: CONVERSION TO SUMS OF UNITS
Outside of the SI, it is sometimes desirable to convert a single
unit to a sum of units\(emfor example, feet to feet plus inches.
The conversion \fIfrom\fP sums of units was described in
\fISums and Differences of Units\fP, and is a simple matter of adding
the units with the
.CQ "+"
sign:
.PP
.ES
You have: 12 ft + 3 in + 3|8 in
You want: ft
* 12.28125
/ 0.081424936
.EE
.PP
Although you can similarly write a sum of units to convert \fIto\fP,
the result will not be the conversion to the units in the sum, but
rather the conversion to the particular sum that you have entered:
.PP
.ES
You have: 12.28125 ft
You want: ft + in + 1|8 in
* 11.228571
/ 0.089058524
.EE
.PP
The unit expression given at the
.CQ "You\ want:"
prompt is
equivalent to asking for conversion to multiples of
.CQ "1\ ft + 1\ in + 1|8\ in" ,
which is 1.09375 ft, so the
conversion in the previous example is equivalent to
.PP
.ES
You have: 12.28125 ft
You want: 1.09375 ft
* 11.228571
/ 0.089058524
.EE
.PP
In converting to a sum of units like miles, feet and inches, you
typically want the largest integral value for the first unit, followed
by the largest integral value for the next, and the remainder converted
to the last unit.
You can do this conversion easily with
.CW "units"
using a special
syntax for lists of units. You must list the desired units in order
from largest to smallest, separated by the semicolon
.CQ ( ";" )
character:
.PP
.ES
You have: 12.28125 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3|8 in
.EE
.PP
The conversion always gives integer coefficients on the units in the
list, except possibly the last unit when the conversion is not exact:
.PP
.ES
You have: 12.28126 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3.00096 * 1|8 in
.EE
.PP
The order in which you list the units is important:
.PP
.ES
You have: 3 kg
You want: oz;lb
105 oz + 0.051367866 lb
You have: 3 kg
You want: lb;oz
6 lb + 9.8218858 oz
.EE
.PP
Listing ounces before pounds produces a technically correct result,
but not a very useful one. You must list the units in descending
order of size in order to get the most useful result.
.PP
Ending a unit list with the separator
.CQ ";"
has the same effect as repeating the last
unit on the list, so
.CQ "ft;in;1|8 in;"
is equivalent to
.CQ "ft;in;1|8 in;1|8 in" .
With the example above, this gives
.PP
.ES
You have: 12.28126 ft
You want: ft;in;1|8 in;
12 ft + 3 in + 3|8 in + 0.00096 * 1|8 in
.EE
.PP
in effect separating the integer and fractional parts of the
coefficient for the last unit. If you instead
prefer to round the last coefficient to an integer
you can do this with the
.CQ "--round"
.CQ ( "-r" )
option.
With the previous example, the result is
.PP
.ES
You have: 12.28126 ft
You want: ft;in;1|8 in
12 ft + 3 in + 3|8 in (rounded down to nearest 1|8 in)
.EE
.PP
When you use the
.CQ "-r"
option, repeating the last unit on the
list has no effect (e.g.,
.CQ "ft;in;1|8 in;1|8 in"
is equivalent to
.CQ "ft;in;1|8 in" ),
and hence neither does ending a list with a
.CQ ";" .
With a single unit and the
.CQ "-r"
option, a terminal
.CQ ";"
\fIdoes\fP have an effect: it causes
.CW "units"
to treat the
single unit as a list and produce a rounded value for the single unit.
Without the extra
.CQ ";" ,
the
.CQ "-r"
option has no effect on
single unit conversions. This example shows the output using the
.CQ "-r"
option:
.PP
.ES
You have: 12.28126 ft
You want: in
* 147.37512
/ 0.0067854058
You have: 12.28126 ft
You want: in;
147 in (rounded down to nearest in)
.EE
.PP
Each unit that appears in the list must be conformable with the first
unit on the list, and of course the listed units must also be
conformable with the unit that you enter at the
.CQ "You\ have:"
prompt.
.PP
.ES
You have: meter
You want: ft;kg
^
conformability error
ft = 0.3048 m
kg = 1 kg
You have: meter
You want: lb;oz
conformability error
1 m
0.45359237 kg
.EE
.PP
In the first case,
.CW "units"
reports the disagreement between
units appearing on the list. In the second case,
.CW "units"
reports disagreement between the unit you entered and the desired
conversion. This conformability error is based on the first
unit on the unit list.
.PP
Other common candidates for conversion to sums of units are
angles and time:
.PP
.ES
You have: 23.437754 deg
You want; deg;arcmin;arcsec
23 deg + 26 arcmin + 15.9144 arcsec
You have: 7.2319 hr
You want: hr;min;sec
7 hr + 13 min + 54.84 sec
.EE
.PP
In North America, recipes for cooking typically measure ingredients by
volume, and use units that are not always convenient multiples of each
other. Suppose that you have a recipe for 6 and you wish to make a
portion for 1. If the recipe calls for 2\ 1/2 cups of an
ingredient, you might wish to know the measurements in terms of
measuring devices you have available, you could use
.CW "units"
and
enter
.PP
.ES
You have: (2+1|2) cup / 6
You want: cup;1|2 cup;1|3 cup;1|4 cup;tbsp;tsp;1|2 tsp;1|4 tsp
1|3 cup + 1 tbsp + 1 tsp
.EE
.PP
By default, if a unit in a list begins with fraction of the form
1|\fIx\fP and its multiplier is an integer, the fraction is given as
the product of the multiplier and the numerator; for example,
.PP
.ES
You have: 12.28125 ft
You want: ft;in;1|8 in;
12 ft + 3 in + 3|8 in
.EE
.PP
In many cases, such as the example above, this is what is wanted, but
sometimes it is not. For example, a cooking recipe for 6 might call
for 5\ 1/4 cup of an ingredient, but you want a portion for 2, and
your 1-cup measure is not available; you might try
.PP
.ES
You have: (5+1|4) cup / 3
You want: 1|2 cup;1|3 cup;1|4 cup
3|2 cup + 1|4 cup
.EE
.PP
This result might be fine for a baker who has a 1\ 1/2-cup measure
(and recognizes the equivalence), but it may not be as useful to
someone with more limited set of measures, who does want to do
additional calculations, and only wants to know ``How many 1/2-cup
measures to I need to add?'' After all, that's what was actually
asked. With the
.CQ "--show-factor"
option, the factor will not be
combined with a unity numerator, so that you get
.PP
.ES
You have: (5+1|4) cup / 3
You want: 1|2 cup;1|3 cup;1|4 cup
3 * 1|2 cup + 1|4 cup
.EE
.PP
A user-specified fractional unit with a numerator other than 1 is never
overridden, however\(emif a unit list specifies
.CQ "3|4 cup;1|2 cup" ,
a result equivalent to 1\ 1/2 cups will always be shown as
.CQ "2 * 3|4\ cup"
whether or not the
.CQ "--show-factor"
option
is given.
.PP
Some applications for unit lists may be less obvious. Suppose that you
have a postal scale and wish to ensure that it's accurate at 1\ oz,
but have only metric calibration weights. You might try
.PP
.ES
You have: 1 oz
You want: 100 g;50 g; 20 g;10 g;5 g;2 g;1 g;
20 g + 5 g + 2 g + 1 g + 0.34952312 * 1 g
.EE
.PP
You might then place one each of the 20\ g, 5\ g, 2\ g, and
1\ g weights on the scale and hope that it indicates close to
.PP
.ES
You have: 20 g + 5 g + 2 g + 1 g
You want: oz;
0.98767093 oz
.EE
.PP
Appending
.CQ ";"
to
.CQ "oz"
forces a one-line display that includes
the unit; here the integer part of the result is zero, so it is not
displayed.
.PP
A unit list such as
.PP
.ES
cup;1|2\ cup;1|3\ cup;1|4\ cup;tbsp;tsp;1|2\ tsp;1|4\ tsp
.EE
.PP
can be tedious to enter. The
.CW "units"
program provides shorthand names
for some common combinations:
.PP
.ES
hms \fRhours, minutes, seconds\fP
dms \fRangle: degrees, minutes, seconds\fP
time \fRyears, days, hours, minutes and seconds\fP
usvol \fRUS cooking volume: cups and smaller\fP
.EE
.PP
Using these shorthands, or \fIunit list aliases\fP,
you can do the following conversions:
.PP
.ES
You have: anomalisticyear
You want: time
1 year + 25 min + 3.4653216 sec
You have: 1|6 cup
You want: usvol
2 tbsp + 2 tsp
.EE
.PP
You cannot combine a unit list alias with other units: it must appear
alone at the
.CQ "You\ want:"
prompt.
.PP
You can display the definition of a unit list alias by entering it at
the
.CQ "You\ have:"
prompt:
.PP
.ES
You have: dms
Definition: unit list, deg;arcmin;arcsec
.EE
.PP
When you specify compact output with
.CQ "--compact" ,
.CQ "--terse"
or
.CQ "-t"
and perform conversion to a unit list,
.CW "units"
lists the conversion factors for each unit in the
list, separated by semicolons.
.PP
.ES
You have: year
You want: day;min;sec
365;348;45.974678
.EE
.PP
Unlike the case of regular
output, zeros \fIare\fP included in this output list:
.PP
.ES
You have: liter
You want: cup;1|2 cup;1|4 cup;tbsp
4;0;0;3.6280454
.EE
.PP
.SH LOGGING CALCULATIONS
The
.CQ "--log"
option allows you to save the results of calculations
in a file; this can be useful if you need a permanent record of your
work. For example, the fluid-flow conversion in
\fIComplicated Unit Expressions\fP, is lengthy, and if you were to use
it in designing a piping system, you might want a record of it for the
project file. If the interactive session
.PP
.ES
# Conversion factor A1 for pressure drop
# dP = A1 rho f L Q^2/d^5
You have: (8/pi^2) (lbm/ft^3)ft(ft^3/s)^2(1/in^5) # Input units
You want: psi
* 43.533969
/ 0.022970568
.EE
.PP
were logged, the log file would contain
.PP
.ES
### Log started Fri Oct 02 15:55:35 2015
# Conversion factor A1 for pressure drop
# dP = A1 rho f L Q^2/d^5
From: (8/pi^2) (lbm/ft^3)ft(ft^3/s)^2(1/in^5) # Input units
To: psi
* 43.533969
/ 0.022970568
.EE
.PP
The time is written to the log file when the file is opened.
.PP
The use of comments can help clarify the meaning of calculations for
the log.
The log includes conformability errors between the units at the
.CQ "You\ have:"
and
.CQ "You\ want:"
prompts, but not other
errors, including lack of conformability of items in sums or differences
or among items in a unit list. For example, a conversion between zenith
angle and elevation angle could involve
.PP
.ES
You have: 90 deg - (5 deg + 22 min + 9 sec)
^
Illegal sum or difference of non-conformable units
You have: 90 deg - (5 deg + 22 arcmin + 9 arcsec)
You want: dms
84 deg + 37 arcmin + 51 arcsec
You have: _
You want: deg
* 84.630833
/ 0.011816024
You have:
.EE
.PP
The log file would contain
.PP
.ES
From: 90 deg - (5 deg + 22 arcmin + 9 arcsec)
To: deg;arcmin;arcsec
84 deg + 37 arcmin + 51 arcsec
From: _
To: deg
* 84.630833
/ 0.011816024
.EE
.PP
The initial entry error (forgetting that minutes have dimension of time,
and that arcminutes must be used for dimensions of angle) does not
appear in the output. When converting to a unit list alias,
.CW "units"
expands the alias in the log file.
.PP
The
.CQ "From:"
and
.CQ "To:"
tags are written to the log file even if
the
.CQ "--quiet"
option is given. If the log file exists when
.CW "units"
is invoked, the new results are appended to the log file.
The time is written to the log file each time the file is opened.
The
.CQ "--log"
option is ignored when
.CW "units"
is used
non-interactively.
.PP
.SH INVOKING \f(BIUNITS\fP
You invoke
.CW "units"
like this:
.PP
.ES
units [\fIoptions\fP] [\fIfrom-unit\fP [\fIto-unit\fP]]
.EE
.PP
If the \fIfrom-unit\fP and \fIto-unit\fP are omitted, the program
will use interactive prompts to determine which conversions to perform.
See \fIInteractive Use\fP.
If both \fIfrom-unit\fP and \fIto-unit\fP are given,
.CW "units"
will
print the result of that single conversion and then exit.
If only \fIfrom-unit\fP appears on the command line,
.CW "units"
will
display the definition of that unit and exit.
Units specified on the command line may need
to be quoted to protect them from shell interpretation and to group
them into two arguments. See \fICommand Line Use\fP.
.PP
The default behavior of
.CW "units"
can be changed by various
options given on the command line. In most cases, the options may be
given in either short form (a single
.CQ "-"
followed by a single
character)
or long form
.CQ ( "--" ""
followed by a word or hyphen-separated words).
Short-form options are cryptic but require
less typing; long-form options require more typing but are more
explanatory and may be more mnemonic. With long-form options you need
only enter sufficient characters to uniquely identify the option to
the program. For example,
.CQ "--out\ %f"
works, but
.CQ "--o\ %f"
fails because
.CW "units"
has other long options
beginning with
.CQ "o" .
However,
.CQ "--q"
works because
.CQ "--quiet"
is the only long option beginning with
.CQ "q" .
.PP
Some options require
arguments to specify a value (e.g.,
.CQ "-d\ 12"
or
.CQ "--digits\ 12" ).
Short-form options that do not take
arguments may be concatenated (e.g.,
.CQ "-erS"
is equivalent to
.CQ "-e\ -r\ -S" );
the last option in such a list may be one
that takes an argument (e.g.,
.CQ "-ed\ 12" ).
With short-form
options, the space between an option and its argument is optional (e.g.,
.CQ "-d12"
is equivalent to
.CQ "-d\ 12" ).
Long-form options may
not be concatenated, and the space between a long-form option and its
argument is required. Short-form and long-form options may be
intermixed on the command line. Options may be given in any order, but
when incompatible options (e.g.,
.CQ "--output-format"
and
.CQ "--exponential" )
are given in combination, behavior is controlled
by the last option given. For example,
.CQ "-o%.12f\ -e"
gives
exponential format with the default eight significant digits).
.PP
The following options are available:
.PP
.TP
.BR "-\^c" ", " "-\^-\^check"
Check that all units and prefixes defined in the units data file reduce
to primitive units. Print a list of all units that
cannot be reduced. Also display some other diagnostics about
suspicious definitions in the units data file. Only definitions active
in the current locale are checked. You should always run
.CW "units"
with this option after modifying a units data file.
.PP
.TP
.BR "-\^-\^check-verbose" ", " "-\^-\^verbose-check"
Like the
.CQ "--check"
option, this option prints a list of units that
cannot be reduced. But to help find unit definitions that cause
endless loops,
it lists the units as they are checked.
If
.CW "units"
hangs, then the last unit to be printed has a bad
definition. Only definitions active in the current locale are checked.
.PP
.TP
.BR "-\^d \fIndigits\fP" ", " "-\^-\^digits \fIndigits\fP"
Set the number of significant digits in the output to the value
specified (which must be greater than zero). For example,
.CQ "-d\ 12"
sets the number of significant digits to 12.
With exponential output
.CW "units"
displays one digit to the left
of the decimal
point
and eleven digits to the right of the decimal point.
On most systems, the maximum number of internally meaningful digits is
15; if you specify a greater number than your system's maximum,
.CW "units"
will print a warning and set the number to the largest meaningful
value. To directly set the maximum value, give an argument
of
.CW "max"
(e.g.,
.CQ "-d\ max" ).
Be aware, of course, that
``significant'' here refers only to the \fIdisplay\fP of numbers; if
results depend on physical constants not known to this precision, the
physically meaningful precision may be less than that shown. The
.CQ "--digits"
option conflicts with the
.CQ "--output-format"
option.
.PP
.TP
.BR "-\^e" ", " "-\^-\^exponential"
Set the numeric output format to exponential (i.e., scientific
notation), like that used in the Unix
.CW "units"
program.
The default precision is eight significant digits (seven digits to the
right of the decimal point); this can be changed with the
.CQ "--digits"
option. The
.CQ "--exponential"
option conflicts with the
.CQ "--output-format"
option.
.PP
.TP
.BR "-\^o \fIformat\fP" ", " "-\^-\^output-format \fIformat\fP"
This option affords complete control over the numeric output format
using the specified \fIformat\fP. The format is a single floating
point numeric format for the
.CW "printf()"
function in the
C programming language. All compilers support the format types
.CQ "g"
and
.CQ "G"
to specify significant digits,
.CQ "e"
and
.CQ "E"
for
scientific notation, and
.CQ "f"
for fixed-point decimal.
The ISO C99 standard introduced the
.CQ "F"
type for fixed-point
decimal and the
.CQ "a"
and
.CQ "A"
types for hexadecimal
floating point; these types are allowed with compilers that support
them. The default format is
.CQ "%.8g" ;
for greater precision, you
could specify
.CQ "-o\ %.15g" .
See \fINumeric Output Format\fP and
the documentation for
.CW "printf()"
for more detailed descriptions of the
format specification. The
.CQ "--output-format"
option affords the
greatest control of the output appearance, but requires at least
rudimentary knowledge of the
.CW "printf()"
format syntax. If you
don't want to bother with the
.CW "printf()"
syntax, you can specify
greater precision more simply with the
.CQ "--digits"
option or
select exponential format with
.CQ "--exponential" .
The
.CQ "--output-format"
option is incompatible with the
.CQ "--exponential"
and
.CQ "--digits"
options.
.PP
.TP
.BR "-\^f \fIfilename\fP" ", " "-\^-\^file \fIfilename\fP"
Instruct
.CW "units"
to load the units file \fIfilename\fP. You
can specify up to 25 units files on the command line. When you use
this option,
.CW "units"
will load \fIonly\fP the files you list
on the command line; it will not load the standard file or your
personal units file unless you explicitly list them. If \fIfilename\fP
is the empty string
.CQ ( "-f\ """"" ),
the default units file (or that
specified by
.CW "UNITSFILE" )
will be loaded in addition to any others
specified with
.CQ "-f" .
.PP
.TP
.BR "-\^L \fIlogfile\fP" ", " "-\^-\^log \fIlogfile\fP"
Save the results of calculations in the file \fIlogfile\fP; this can be
useful if it is important to have a record of unit conversions or other
calculations that are to be used extensively or in a critical activity
such as a program or design project. If \fIlogfile\fP exits, the new
results are appended to the file.
This option is ignored when
.CW "units"
is used non-interactively.
See \fILogging Calculations\fP for a more detailed description and some
examples.
.PP
.TP
.BR "-\^H \fIfilename\fP" ", " "-\^-\^history \fIfilename\fP"
Instruct
.CW "units"
to save history to \fIfilename\fP, so that a
record of your commands is available for retrieval across different
.CW "units"
invocations. To prevent the history from being saved
set \fIfilename\fP to the emptry string
.CQ ( "-f\ """"" ).
This
option has no effect if readline is not available.
.PP
.TP
.BR "-\^h" ", " "-\^-\^help"
Print out a summary of the options for
.CW "units" .
.PP
.TP
.BR "-\^m" ", " "-\^-\^minus"
Causes
.CQ "-"
to be interpreted as a subtraction operator. This is
the default behavior.
.PP
.TP
.BR "-\^p" ", " "-\^-\^product"
Causes
.CQ "-"
to be interpreted as a multiplication operator when it
has two operands. It will act as a negation operator when it has only one
operand:
.CQ "(-3)" .
By default
.CQ "-"
is treated as a
subtraction operator.
.PP
.TP
.BR "-\^-\^oldstar"
Causes
.CQ "*"
to have the old-style precedence, higher than the
precedence of division so that
.CQ "1/2*3"
will equal
.CQ "1/6" .
.PP
.TP
.BR "-\^-\^newstar"
Forces
.CQ "*"
to have the new (default) precedence that follows
the usual rules of algebra: the precedence of
.CQ "*"
is the same as
the precedence of
.CQ "/" ,
so that
.CQ "1/2*3"
will equal
.CQ "3/2" .
.PP
.TP
.BR "-\^-\^compact"
Give compact output featuring only the conversion factor. This turns
off the
.CQ "--verbose"
option.
.PP
.TP
.BR "-\^q" ", " "-\^-\^quiet" ", " "-\^-\^silent"
Suppress prompting of the user for units and the display of statistics
about the number of units loaded.
.PP
.TP
.BR "-\^n" ", " "-\^-\^nolists"
Disable conversion to unit lists.
.PP
.TP
.BR "-\^r" ", " "-\^-\^round"
When converting to a combination of units given by a unit list, round
the value of the last unit in the list to the nearest integer.
.PP
.TP
.BR "-\^S" ", " "-\^-\^show-factor"
When converting to a combination of units specified in a list,
always show a non-unity factor before a unit that
begins with a fraction with a unity denominator. By default, if the
unit in a list begins with fraction of the form 1|\fIx\fP and
its multiplier is an integer other than 1, the fraction is given as the
product of the multiplier and the numerator (e.g.,
.CQ "3|8\ in"
rather than
.CQ "3 * 1|8\ in" ).
In some cases, this is not what is
wanted; for example, the results for a cooking recipe might show
.CQ "3 * 1|2\ cup"
as
.CQ "3|2\ cup" .
With the
.CQ "--show-factor"
option, a
result equivalent to 1.5 cups will display as
.CQ "3 * 1|2\ cup"
rather than
.CQ "3|2\ cup" .
A user-specified fractional unit with
a numerator other than 1 is never overridden, however\(emif a unit list
specifies
.CQ "3|4 cup;1|2 cup" ,
a result equivalent to 1\ 1/2 cups
will always be shown as
.CQ "2 * 3|4\ cup"
whether or not the
.CQ "--show-factor"
option is given.
.PP
.TP
.BR "-\^s" ", " "-\^-\^strict"
Suppress conversion of units to their reciprocal units. For
example,
.CW "units"
will normally convert hertz to seconds
because these units are reciprocals of each other. The strict option
requires that units be strictly conformable to perform a conversion, and
will give an error if you attempt to convert hertz to seconds.
.PP
.TP
.BR "-\^1" ", " "-\^-\^one-line"
Give only one line of output (the forward conversion). Do not print
the reverse conversion. If a reciprocal conversion is
performed then
.CW "units"
will still print the ``reciprocal
conversion'' line.
.PP
.TP
.BR "-\^t" ", " "-\^-\^terse"
Give terse output when converting units. This option can be used when
calling
.CW "units"
from another program so that the output is easy to
parse. This option has the combined
effect of these options:
.CQ "--strict"
.CQ "--quiet"
.CQ "--one-line"
.CQ "--compact" .
When combined with
.CQ "--version"
it produces
a display showing only the program name and version number.
.PP
.TP
.BR "-\^v" ", " "-\^-\^verbose"
Give slightly more verbose output when converting units. When combined
with the
.CQ "-c"
option this gives the same effect as
.CQ "--check-verbose" .
When combined with
.CQ "--version"
produces a more detailed output, equivalent to the
.CQ "--info"
option.
.PP
.TP
.BR "-\^V" ", " "-\^-\^version"
Print the program version number, tell whether the
.CW "readline"
library has been included, tell whether UTF-8 support has been included;
give the locale, the location of the default units data file, and the
location of the personal units data file; indicate if the personal units
data file does not exist.
.PP
When given in combination with the
.CQ "--terse"
option, the program
prints only the version number and exits.
.PP
When given in combination with the
.CQ "--verbose"
option, the
program, the
.CQ "--version"
option has the same effect as the
.CQ "--info"
option below.
.PP
.TP
.BR "-\^I" ", " "-\^-\^info"
Print the information given with the
.CQ "--version"
option, show the
pathname of the units program, show the status of the
.CW "UNITSFILE"
and
.CW "MYUNITSFILE"
environment variables, and additional information
about how
.CW "units"
locates the related files. On systems running
Microsoft Windows, the status of the
.CW "UNITSLOCALE"
environment
variable and information about the related locale map are also given.
This option is usually of interest only to developers and
administrators, but it can sometimes be useful for troubleshooting.
.PP
Combining the
.CQ "--version"
and
.CQ "--verbose"
options has the
same effect as giving
.CQ "--info" .
.PP
.TP
.BR "-\^U" ", " "-\^-\^unitsfile"
Print the location of the default units data file and exit; if the file
cannot be found, print ``Units data file not found''.
.PP
.TP
.BR "-\^l \fIlocale\fP" ", " "-\^-\^locale \fIlocale\fP"
Print the information given with the
.CQ "--version"
option, show the
Force a specified locale such as
.CQ "en_GB"
to get British
definitions by default. This overrides the locale determined from
system settings or environment variables.
See \fILocale\fP for a description of locale format.
.PP
.SH ADDING YOUR OWN DEFINITIONS
.SS Units Data Files
The units and prefixes that
.CW "units"
can convert are
defined in the units
data file, typically
.CQ "/usr/share/units/definitions.units" .
If you can't find this file, run
.CW "units\ --version"
to get
information on the file locations for your installation. Although you
can extend or modify this data file if you have appropriate user
privileges, it's usually better to put extensions in separate files so
that the definitions will be preserved if you update
.CW "units" .
.PP
You can include additional data files in the units database using
the
.CQ "!include"
command in the standard units data file. For
example
.PP
.ES
!include /usr/local/share/units/local.units
.EE
.PP
might be appropriate for a site-wide supplemental data file.
The location of the
.CQ "!include"
statement in the standard units
data file is important; later definitions replace earlier ones,
so any definitions in an included file will override definitions before
the
.CQ "!include"
statement in the standard units data file.
With normal invocation, no warning is given about redefinitions; to
ensure that you don't have an unintended redefinition, run
.CW "units\ -c"
after making changes to any units data file.
.PP
If you want to add your own units in addition to or in place of
standard or site-wide supplemental units data files, you can include
them in the
.CQ ".units"
file in your home directory. If this
file exists it is read after the standard units data file, so that any
definitions in this file will replace definitions of the same units in
the standard data file or in files included from the standard data
file. This file will not be read if any units files are specified on
the command line. (Under Windows the personal units file is
named
.CQ "unitdef.units" .)
Running
.CW "units\ -V"
will
display the location and name of your personal units file.
.PP
The
.CW "units"
program first tries to determine your home
directory from the
.CW "HOME"
environment variable. On systems running
Microsoft Windows, if
.CW "HOME"
does not exist,
.CW "units"
attempts to find your home directory from
.CW "HOMEDRIVE" ,
.CW "HOMEPATH"
and
.CW "USERPROFILE" .
You can specify an arbitrary file as your personal units data file with
the
.CW "MYUNITSFILE"
environment variable; if this variable exists, its
value is used without searching your home directory.
The default units data files are described in more detail in
\fIData Files\fP.
.PP
.SS Defining New Units and Prefixes
A unit is specified on a single line by giving its name and an
equivalence. Comments start with a
.CQ "#"
character, which can appear
anywhere in a line. The backslash character
.CQ ( "\e" )
acts as a continuation
character if it appears as the last character on a line, making it
possible to spread definitions out over several lines if desired.
A file can be included by giving the command
.CQ "!include"
followed by
the file's name. The
.CQ "!"
must be the first character on the
line. The file will be sought in the same directory as the
parent file unless you give a full path. The name of the file to be
included cannot contain the comment character
.CQ "#" .
.PP
Unit names must not contain any of the operator characters
.CQ "+" ,
.CQ "-" ,
.CQ "*" ,
.CQ "/" ,
.CQ "|" ,
.CQ "^" ,
.CQ ";" ,
.CQ "~" ,
the comment character
.CQ "#" ,
or parentheses. They cannot begin or
end with an underscore
.CQ ( "_" ),
a comma
.CQ ( "," )
or a decimal point
.CQ ( "." ).
The figure dash (U+2012), typographical minus (`\-';
U+2212), and en dash (`\-'; U+2013) are converted to the operator
.CQ "-" ,
so none of these characters can appear in unit names. Names
cannot begin with a digit, and if a name ends in a digit other than
zero, the digit must be preceded by a string beginning with an
underscore, and afterwards consisting only of digits, decimal points, or
commas. For example,
.CQ "foo_2" ,
.CQ "foo_2,1" ,
or
.CQ "foo_3.14"
are valid names but
.CQ "foo2"
or
.CQ "foo_a2"
are invalid.
You could define nitrous oxide as
.PP
.ES
N2O nitrogen 2 + oxygen
.EE
.PP
but would need to define nitrogen dioxide as
.PP
.ES
NO_2 nitrogen + oxygen 2
.EE
.PP
Be careful to define new units in terms of old ones so that a
reduction leads to the primitive units, which are marked with
.CQ "!"
characters. Dimensionless units are indicated by using the string
.CQ "!dimensionless"
for the unit definition.
.PP
When adding new units, be sure to use the
.CQ "-c"
option to check
that the new units reduce properly. If you create a loop in the units
definitions, then
.CW "units"
will hang when invoked with the
.CQ "-c"
option. You will need to use the
.CQ "--check-verbose"
option, which prints out each unit as it is checked. The program will
still hang, but the last unit printed will be the unit that caused the
infinite loop.
.PP
If you define any units that contain
.CQ "+"
characters, carefully check them because the
.CQ "-c"
option
will not catch non-conformable sums. Be careful with the
.CQ "-"
operator as well. When used as a binary operator, the
.CQ "-"
character can perform addition or multiplication
depending on the options used to invoke
.CW "units" .
To ensure consistent behavior use
.CQ "-"
only as a unary negation
operator when writing units definitions. To multiply two units leave a
space or use the
.CQ "*"
operator with care, recalling that it has
two possible precedence values and may require parentheses to ensure
consistent behavior. To compute the difference
of
.CQ "foo"
and
.CQ "bar"
write
.CQ "foo+(-bar)"
or even
.CQ "foo+-bar" .
.PP
Here is an example of a short data file that defines some basic
units:
.PP
.ES
m ! # The meter is a primitive unit
sec ! # The second is a primitive unit
rad !dimensionless # A dimensionless primitive unit
micro- 1e-6 # Define a prefix
minute 60 sec # A minute is 60 seconds
hour 60 min # An hour is 60 minutes
inch 0.0254 m # Inch defined in terms of meters
ft 12 inches # The foot defined in terms of inches
mile 5280 ft # And the mile
.EE
.PP
A unit that ends with a
.CQ "-"
character is a prefix. If a prefix
definition contains any
.CQ "/"
characters, be sure they are protected
by parentheses. If you define
.CQ "half- 1/2"
then
.CQ "halfmeter"
would be equivalent to
.CQ "1 / (2\ meter)" .
.PP
.SS Defining Nonlinear Units
Some unit conversions of interest are nonlinear; for
example, temperature conversions between the Fahrenheit and Celsius
scales cannot be done by simply multiplying by conversion factors.
.PP
When you give a linear unit definition such as
.CQ "inch 2.54\ cm"
you are providing information that
.CW "units"
uses to convert
values in inches into primitive units of meters. For nonlinear units,
you give a functional definition that provides the same information.
.PP
Nonlinear units are represented using a functional notation.
It is best to regard this notation not as a function call but
as a way of adding units to a number, much the same way that
writing a linear unit name after a number adds units to that number.
Internally, nonlinear units are defined by a pair of functions
that convert to and from linear units in the database, so that
an eventual conversion to primitive units is possible.
.PP
Here is an example nonlinear unit definition:
.PP
.ES
tempF(x) units=[1;K] domain=[-459.67,) range=[0,) \e
(x+(-32)) degF + stdtemp ; (tempF+(-stdtemp))/degF + 32
.EE
.PP
A nonlinear unit definition comprises a unit name, a formal parameter
name, two functions, and optional specifications for units, the domain,
and the range (the domain of the inverse function). The functions tell
.CW "units"
how to convert to and from the new unit. To produce
valid results, the arguments of these functions need to have the correct
dimensions and be within the domains for which the functions are
defined.
.PP
The definition begins with the unit name followed immediately (with no
spaces) by a
.CQ "("
character. In the parentheses is the name of the
formal parameter. Next is an optional specification of the units
required by the functions in the definition. In the example above,
the
.CQ "units=[1;K]"
specification indicates that the
.CQ "tempF"
function requires an input argument conformable with
.CQ "1"
(i.e., the argument is dimensionless), and that the inverse
function requires an input argument conformable with
.CQ "K" .
For
normal nonlinear units definition, the forward function will always take
a dimensionless argument; in general, the inverse function will need
units that match the quantity measured by your nonlinear unit.
Specifying the units enables
.CW "units"
to perform error checking
on function arguments, and also to assign units to domain and range
specifications, which are described later.
.PP
Next the function definitions appear. In the example above, the
.CQ "tempF"
function is defined by
.PP
.ES
tempF(x) = (x+(-32)) degF + stdtemp
.EE
.PP
This gives a rule for converting
.CQ "x"
in the units
.CQ "tempF"
to linear units of absolute temperature, which makes it possible to
convert from tempF to other units.
.PP
To enable conversions to Fahrenheit, you must give a rule for the
inverse conversions. The inverse will be
.CQ "x(tempF)"
and its
definition appears after a
.CQ ";"
character. In our example, the
inverse is
.PP
.ES
x(tempF) = (tempF+(-stdtemp))/degF + 32
.EE
.PP
This inverse definition takes an absolute temperature as its argument
and converts it to the Fahrenheit temperature. The inverse can be
omitted by leaving out the
.CQ ";"
character and the inverse
definition, but then conversions \fIto\fP the unit will not be
possible. If the inverse definition is omitted, the
.CQ "--check"
option will display a warning. It is up to you to calculate and enter
the correct inverse function to obtain proper conversions; the
.CQ "--check"
option tests the inverse at one point and prints an
error if it is not valid there, but this is not a guarantee that your
inverse is correct.
.PP
With some definitions, the units may vary. For example, the definition
.PP
.ES
square(x) x^2
.EE
.PP
can have any arbitrary units, and can also take dimensionless arguments.
In such a case, you should \fInot\fP specify units.
If a definition takes a root of its arguments, the definition is valid
only for units that yield such a root. For example,
.PP
.ES
squirt(x) sqrt(x)
.EE
.PP
is valid for a dimensionless argument, and for arguments with even
powers of units.
.PP
Some definitions may not be valid for all real numbers. In such cases,
.CW "units"
can handle errors better if you specify an appropriate
domain and range. You specify the domain and range as shown below:
.PP
.ES
baume(d) units=[1;g/cm^3] domain=[0,130.5] range=[1,10] \e
(145/(145-d)) g/cm^3 ; (baume+-g/cm^3) 145 / baume
.EE
.PP
In this example the domain is specified after
.CQ "domain="
with
the endpoints given in brackets. In accord with mathematical
convention, square brackets indicate a closed interval (one that
includes its endpoints), and parentheses indicate an open interval (one
that does not include its endpoints). An interval can be open or closed
on one or both ends; an interval that is unbounded on either end is
indicated by omitting the limit on that end. For example, a quantity to
which decibel (dB) is applied may have any value greater than zero, so
the range is indicated by
.CQ "(0,)" :
.PP
.ES
decibel(x) units=[1;1] range=(0,) 10^(x/10); 10 log(decibel)
.EE
.PP
If the domain or range is given, the second endpoint must be greater
than the first.
.PP
The domain and range specifications can appear independently and in any
order along with the units specification.
The values for the domain and range endpoints are attached to the units
given in the units specification, and if necessary, the parameter value
is adjusted for comparison with the endpoints. For example, if a
definition includes
.CQ "units=[1;ft]"
and
.CQ "range=[3,)" ,
the range
will be taken as 3\ ft to infinity. If the function is passed a
parameter of
.CQ "900\ mm" ,
that value will be adjusted to
2.9527559\ ft, which is outside the specified range.
If you omit the units specification from the previous example,
.CW "units"
can not tell whether you intend the lower endpoint
to be 3\ ft or 3\ microfurlongs, and can not adjust the
parameter value of 900\ mm for comparison. Without units,
numerical values other than zero or plus or minus infinity for domain or
range endpoints are meaningless, and accordingly they are not allowed. If
you give other values without units then the definition will be ignored
and you will get an error message.
.PP
Although the units, domain, and range specifications are optional, it's
best to give them when they are applicable; doing so allows
.CW "units"
to perform better error checking and give more helpful
error messages. Giving the domain and range also enables the
.CQ "--check"
option to find a point in the domain to use for its
point check of your inverse definition.
.PP
You can make synonyms for nonlinear units by providing both the
forward and inverse functions; inverse functions can be obtained using
the
.CQ "~"
operator. So to create a synonym for
.CQ "tempF"
you
could write
.PP
.ES
fahrenheit(x) units=[1;K] tempF(x); ~tempF(fahrenheit)
.EE
.PP
This is useful for creating a nonlinear unit
definition that differs slightly from an existing definition without
having to repeat the original functions. For example,
.PP
.ES
dBW(x) units=[1;W] range=[0,) dB(x) W ; ~dB(dBW/W)
.EE
.PP
If you wish a synonym to refer to an existing nonlinear unit without
modification, you can do so more simply by adding the synonym with
appended parentheses as a new unit, with the existing nonlinear
unit\(emwithout parentheses\(emas the definition. So to create a synonym
for
.CQ "tempF"
you could write
.PP
.ES
fahrenheit() tempF
.EE
.PP
The definition must be a nonlinear unit; for example, the synonym
.PP
.ES
fahrenheit() meter
.EE
.PP
will result in an error message when
.CW "units"
starts.
.PP
You may occasionally wish to define a function that operates on units.
This can be done using a nonlinear unit definition. For example, the
definition below provides conversion between radius and the area of a
circle. This definition requires a length as input and
produces an area as output, as indicated by the
.CQ "units="
specification.
Specifying the range as the nonnegative numbers can prevent cryptic
error messages.
.PP
.ES
circlearea(r) units=[m;m^2] range=[0,) pi r^2 ; sqrt(circlearea/pi)
.EE
.PP
.SS Defining Piecewise Linear Units
Sometimes you may be interested in a piecewise linear unit such as
many wire gauges. Piecewise linear units can be defined by specifying
conversions to linear units on a list of points.
Conversion at other points will be done by linear interpolation.
A partial definition of zinc gauge is
.PP
.ES
zincgauge[in] 1 0.002, 10 0.02, 15 0.04, 19 0.06, 23 0.1
.EE
.PP
In this example,
.CQ "zincgauge"
is the name of the piecewise linear
unit. The definition of such a unit is indicated by the
embedded
.CQ "["
character. After the bracket, you should indicate the
units to be attached to the numbers in the table.
No spaces can appear before the
.CQ "]"
character, so a definition like
.CQ "foo[kg meters]"
is
invalid; instead write
.CQ "foo[kg*meters]" .
The definition of the
unit consists of a list of pairs optionally separated by commas.
This list defines a function for converting from the piecewise linear
unit to linear units. The
first item in each pair is the function argument; the second item is the
value of the function at that argument (in the units specified in brackets).
In this example,
we define
.CQ "zincgauge"
at five points. For example, we set
.CQ "zincgauge(1)"
equal to
.CQ "0.002\ in" .
Definitions like this
may be more readable if written using continuation characters as
.PP
.ES
zincgauge[in] \e
1 0.002 \e
10 0.02 \e
15 0.04 \e
19 0.06 \e
23 0.1
.EE
.PP
With the preceding definition, the following conversion can be
performed:
.PP
.ES
You have: zincgauge(10)
You want: in
* 0.02
/ 50
You have: .01 inch
You want: zincgauge
5
.EE
.PP
If you define a piecewise linear unit that is not strictly monotonic,
then the inverse will not be well defined. If the inverse is requested
for such a unit,
.CW "units"
will return the smallest inverse.
.PP
After adding nonlinear units definitions, you should normally run
.CW "units\ --check"
to check for errors. If the
.CQ "units"
keyword is not given, the
.CQ "--check"
option checks a nonlinear unit
definition using a dimensionless argument, and then checks using an
arbitrary combination of units, as well as the square and cube of that
combination; a warning is given if any of these tests fail. For
example,
.PP
.ES
Warning: function 'squirt(x)' defined as 'sqrt(x)'
failed for some test inputs:
squirt(7(kg K)^1): Unit not a root
squirt(7(kg K)^3): Unit not a root
.EE
.PP
Running
.CW "units\ --check"
will print a warning if a
non-monotonic piecewise linear unit is encountered. For example, the
relationship between ANSI coated abrasive designation and mean particle
size is non-monotonic in the vicinity of 800 grit:
.PP
.ES
ansicoated[micron] \e
. . .
600 10.55 \e
800 11.5 \e
1000 9.5 \e
.EE
.PP
Running
.CW "units\ --check"
would give the error message
.PP
.ES
Table 'ansicoated' lacks unique inverse around entry 800
.EE
.PP
Although the inverse is not well defined in this region, it's not really
an error. Viewing such error messages can be tedious, and if there are
enough of them, they can distract from true errors. Error checking for
nonlinear unit definitions can be suppressed by giving the
.CQ "noerror"
keyword; for the examples above, this could be done as
.PP
.ES
squirt(x) noerror domain=[0,) range=[0,) sqrt(x); squirt^2
ansicoated[micron] noerror \e
. . .
.EE
.PP
Use the
.CQ "noerror"
keyword with caution. The safest approach after
adding a nonlinear unit definition is to run
.CW "units\ --check"
and confirm that there are no actual errors before adding the
.CQ "noerror"
keyword.
.PP
.SS Defining Unit List Aliases
Unit list aliases are treated differently from unit definitions,
because they are a data entry shorthand rather than a true definition
for a new unit.
A unit list alias definition begins with
.CQ "!unitlist"
and includes the
alias and the definition; for example, the aliases included in the
standard units data file are
.PP
.ES
!unitlist hms hr;min;sec
!unitlist time year;day;hr;min;sec
!unitlist dms deg;arcmin;arcsec
!unitlist ftin ft;in;1|8 in
!unitlist usvol cup;3|4 cup;2|3 cup;1|2 cup;1|3 cup;1|4 cup;\e
tbsp;tsp;1|2 tsp;1|4 tsp;1|8 tsp
.EE
.PP
Unit list aliases are only for unit lists, so the definition must
include a
.CQ ";" .
Unit list aliases can never be combined with
units or other unit list aliases, so the definition of
.CQ "time"
shown above could \fInot\fP have been shortened to
.CQ "year;day;hms" .
.PP
As usual, be sure to run
.CW "units\ --check"
to ensure that the
units listed in unit list aliases are conformable.
.PP
.SH NUMERIC OUTPUT FORMAT
By default,
.CW "units"
shows results to eight significant
digits. You can change this with the
.CQ "--exponential" ,
.CQ "--digits" ,
and
.CQ "--output-format"
options. The first
sets an exponential format (i.e., scientific notation) like that used
in the original Unix
.CW "units"
program, the second allows you to
specify a different number of significant digits, and the last allows
you to control the output appearance using the format for the
.CW "printf()"
function in the C programming language. If you only
want to change the number of significant digits or specify exponential
format type, use the
.CQ "--digits"
and
.CQ "--exponential"
options. The
.CQ "--output-format"
option affords the greatest
control of the output appearance, but requires at least rudimentary
knowledge of the
.CW "printf()"
format syntax. See \fIInvoking Units\fP
for descriptions of these options.
.PP
.SS Format Specification
The format specification recognized with the
.CQ "--output-format"
option is a subset of that for
.CW "printf()" .
The format specification has
the form
.\".CW "%\fR[\fP\fIflags\fP\fR][\fP\fIwidth\fP\fR][\fP.\fIprecision\fP\fR]\fP\fItype\fP" ;
.CW "%" [\fIflags\fP][\fIwidth\fP][\c
.CW "." \fIprecision\fP]\fItype\fP;
it must begin with
.CQ "%" ,
and must end with a floating-point type
specifier:
.CQ "g"
or
.CQ "G"
to specify the number of significant digits,
.CQ "e"
or
.CQ "E"
for scientific notation, and
.CQ "f"
for
fixed-point decimal. The ISO C99 standard added the
.CQ "F"
type for
fixed-point decimal and the
.CQ "a"
and
.CQ "A"
types for hexadecimal
floating point; these types are allowed with compilers that support
them. Type length modifiers (e.g.,
.CQ "L"
to indicate a long double)
are inapplicable and are not allowed.
.PP
The default format for
.CW "units"
is
.CQ "%.8g" ;
for greater precision, you could specify
.CQ "-o\ %.15g" .
The
.CQ "g"
and
.CQ "G"
format types use exponential format whenever
the exponent would be less than \-4, so the value 0.000013
displays as
.CQ "1.3e-005" .
These types also use exponential notation
when the exponent is greater than or equal to the precision, so with the
default format, the value
.if t .ig ++
5e7
.++
.if n .ig ++
.EQ
5 times 10 sup 7
.EN
.++
displays as
.CQ "50000000"
and the value
.if t .ig ++
5e8
.++
.if n .ig ++
.EQ
5 times 10 sup 8
.EN
.++
displays as
.CQ "5e+008" .
If you prefer fixed-point display, you might
specify
.CQ "-o\ %.8f" ;
however, small numbers will display very
few significant digits, and values less than
.if t .ig ++
0.5e\-8
.++
.if n .ig ++
.EQ
0.5 times 10 sup -8
.EN
.++
will show nothing but zeros.
.PP
The format specification may include one or more optional flags:
.CQ "+" ,
.CQ "\ "
(space),
.CQ "#" ,
.CQ "-" ,
or
.CQ "0"
(the
digit zero). The digit-grouping flag
.ie \n(.g .CQ "\(aq"
.el .CQ "'"
is allowed with compilers that support it. Flags are followed by an
optional value for the minimum field width, and an optional precision
specification that begins with a period (e.g.,
.CQ ".6" ).
The field
width includes the digits, decimal point, the exponent, thousands
separators (with the digit-grouping flag), and the sign if any of these
are shown.
.PP
.SS Flags
The
.CQ "+"
flag causes the output to have a sign
.CQ ( "+" ""
or
.CQ "-" ).
The space flag
.CQ "\ "
is similar to the
.CQ "+"
flag, except
that when the value is positive, it is prefixed with a space rather than
a plus sign; this flag is ignored if the
.CQ "+"
flag is also given.
The
.CQ "+"
or
.CQ "\ "
flag could be useful if conversions might
include positive and negative results, and you wanted to align
the decimal points in exponential notation.
The
.CQ "#"
flag causes the output value to contain a decimal point in
all cases; by default, the output contains a decimal point only if there
are digits (which can be trailing zeros) to the right of the point.
With the
.CQ "g"
or
.CQ "G"
types, the
.CQ "#"
flag also prevents the
suppression of trailing zeros.
The digit-grouping flag
.ie \n(.g .CQ "\(aq"
.el .CQ "'"
shows a thousands separator in digits to the left of the decimal point.
This can be useful when displaying large numbers in fixed-point decimal;
for example, with the format
.CQ "%f" ,
.PP
.ES
You have: mile
You want: microfurlong
* 8000000.000000
/ 0.000000
.EE
.PP
the magnitude of the first result may not be immediately obvious without
counting the digits to the left of the decimal point. If the thousands
separator is the comma
.CQ ( "," ),
the output with the format
.ie \n(.g .CQ "%\(aqf"
.el .CQ "%'f"
might be
.PP
.ES
You have: mile
You want: microfurlong
* 8,000,000.000000
/ 0.000000
.EE
.PP
making the magnitude readily apparent. Unfortunately, few compilers
support the digit-grouping flag.
.PP
With the
.CQ "-"
flag, the output value is left aligned within the
specified field width. If a field width greater than needed to show the
output value is specified, the
.CQ "0"
(zero) flag causes the output
value to be left padded with zeros until the specified field width is
reached; for example, with the format
.CQ "%011.6f" ,
.PP
.ES
You have: troypound
You want: grain
* 5760.000000
/ 0000.000174
.EE
.PP
The
.CQ "0"
flag has no effect if the
.CQ "-"
(left align) flag is
given.
.PP
.SS Field Width
By default, the output value is left aligned and shown with the minimum
width necessary for the specified (or default) precision. If a field
width greater than this is specified, the value shown is right aligned,
and padded on the left with enough spaces to provide the specified field
width. A width specification is typically used with fixed-point decimal
to have columns of numbers align at the decimal point; this arguably is
less useful with
.CW "units"
than with long columnar output, but it
may nonetheless assist in quickly assessing the relative magnitudes of
results. For example, with the format
.CQ "%12.6f" ,
.PP
.ES
You have: km
You want: in
* 39370.078740
/ 0.000025
You have: km
You want: rod
* 198.838782
/ 0.005029
You have: km
You want: furlong
* 4.970970
/ 0.201168
.EE
.PP
.SS Precision
The meaning of ``precision'' depends on the format type. With
.CQ "g"
or
.CQ "G" ,
it specifies the number of significant digits (like the
.CQ "--digits"
option); with
.CQ "e" ,
.CQ "E" ,
.CQ "f" ,
or
.CQ "F" ,
it specifies the maximum number of digits to be shown after
the decimal point.
.PP
With the
.CQ "g"
and
.CQ "G"
format types, trailing zeros are
suppressed, so the results may sometimes have fewer digits than the
specified precision (as indicated above, the
.CQ "#"
flag causes
trailing zeros to be displayed).
.PP
The default precision is 6, so
.CQ "%g"
is equivalent to
.CQ "%.6g" ,
and would show the output to six significant digits. Similarly,
.CQ "%e"
or
.CQ "%f"
would show the output with six digits after the
decimal point.
.PP
The C
.CW "printf()"
function allows a precision of arbitrary size, whether or
not all of the digits are meaningful. With most compilers, the maximum
internal precision with
.CW "units"
is 15 decimal digits (or 13
hexadecimal digits).
With the
.CQ "--digits"
option, you are limited
to the maximum internal precision; with the
.CQ "--output-format"
option, you may specify a precision greater than this, but it may not be
meaningful. In some cases, specifying excess precision can result in
rounding artifacts. For example, a pound is exactly 7000 grains, but
with the format
.CQ "%.18g" ,
the output might be
.PP
.ES
You have: pound
You want: grain
* 6999.9999999999991
/ 0.00014285714285714287
.EE
.PP
With the format
.CQ "%.25g"
you might get the following:
.PP
.ES
You have: 1/3
You want:
Definition: 0.333333333333333314829616256247
.EE
.PP
In this case the displayed value includes a series of digits that represent the
underlying binary floating-point approximation to 1/3 but are not
meaningful for the desired computation.
In general, the result with excess precision is system dependent.
The precision affects only the \fIdisplay\fP of numbers; if a result
relies on physical constants that are not known to the specified
precision, the number of physically meaningful digits may be less than
the number of digits shown.
.PP
See the documentation for
.CW "printf()"
for more detailed descriptions of the
format specification.
.PP
The
.CQ "--output-format"
option is incompatible with the
.CQ "--exponential"
or
.CQ "--digits"
options; if the former is
given in combination with either of the latter, the format is controlled
by the last option given.
.PP
.SH LOCALIZATION
Some units have different values in different locations. The
localization feature accommodates this by allowing a units data file to
specify definitions that depend on the user's locale.
.PP
.SS Locale
A locale is a subset of a user's environment that indicates the user's
language and country, and some attendant preferences, such as the
formatting of dates. The
.CW "units"
program attempts to determine
the locale from the POSIX setlocale function; if this cannot be done,
.CW "units"
examines the environment
variables
.CW "LC_CTYPE"
and
.CW "LANG" .
On POSIX systems, a locale is of the form
.CW \fIlanguage\fP "_" \fIcountry\fP,
where \fIlanguage\fP is the
two-character code from ISO 639-1 and \fIcountry\fP is the two-character
code from ISO 3166-1; \fIlanguage\fP is lower case and \fIcountry\fP is
upper case. For example, the POSIX locale for the United Kingdom is
.CW "en_GB" .
.PP
On systems running Microsoft Windows, the value returned by setlocale()
is different from that on POSIX systems;
.CW "units"
attempts to map
the Windows value to a POSIX value by means of a table in the file
.CQ "locale_map.txt"
in the same directory as the other data files. The
file includes entries for many combinations of language and country, and
can be extended to include other combinations. The
.CQ "locale_map.txt"
file comprises two tab-separated columns; each entry is of the form
.PP
.DS
\fIWindows-locale\fP \fIPOSIX-locale\fP
.DE
.PP
where \fIPOSIX-locale\fP is as described above, and \fIWindows-locale\fP
typically spells out both the language and country. For example, the
entry for the United States is
.PP
.ES
English_United States en_US
.EE
.PP
You can force
.CW "units"
to run in a desired locale by using the
.CQ "-l"
option.
.PP
In order to create unit definitions for a particular locale you begin
a block of definitions in a unit datafile with
.CQ "!locale"
followed
by a locale name. The
.CQ "!"
must be the first character on the
line. The
.CW "units"
program reads the following
definitions only if the current locale matches. You end the block of
localized units with
.CQ "!endlocale" .
Here is an example, which
defines the British gallon.
.PP
.ES
!locale en_GB
gallon 4.54609 liter
!endlocale
.EE
.PP
.SS Additional Localization
Sometimes the locale isn't sufficient to determine unit preferences.
There could be regional preferences, or a company could have specific
preferences. Though probably uncommon, such differences could arise
with the choice of English customary units outside of English-speaking
countries. To address this,
.CW "units"
allows specifying
definitions that depend on environment variable settings.
The environment variables can be controled based on the current locale,
or the user can set them to force a particular group of definitions.
.PP
A conditional block of definitions in a units data file begins with
either
.CQ "!var"
or
.CQ "!varnot"
following by an environment
variable name and then a space separated
list of values. The leading
.CQ "!"
must appear in the first column of a units
data file, and the conditional block is terminated by
.CQ "!endvar" .
Definitions in blocks beginning with
.CQ "!var"
are executed only if the
environment variable is exactly equal to one of the listed values.
Definitions in blocks beginning with
.CQ "!varnot"
are executed only if the
environment variable does \fInot\fP equal any of the list values.
.PP
The inch has long been a customary measure of length in many places.
The word comes from the latin \fIuncia\fP meaning ``one twelfth,''
referring to its relationship with the foot. By the 20th century, the
inch was officially defined in English-speaking countries relative to
the yard, but until 1959, the yard differed slightly among those
countries. In France the customary inch, which was displaced in 1799
by the meter, had a different length based on a french foot. These
customary definitions could be accommodated as follows:
.PP
.ES
!var INCH_UNIT usa
yard 3600|3937 m
!endvar
!var INCH_UNIT canada
yard 0.9144 meter
!endvar
!var INCH_UNIT uk
yard 0.91439841 meter
!endvar
!var INCH_UNIT canada uk usa
foot 1|3 yard
inch 1|12 foot
!endvar
!var INCH_UNIT france
foot 144|443.296 m
inch 1|12 foot
line 1|12 inch
!endvar
!varnot INCH_UNIT usa uk france canada
!message Unknown value for INCH_UNIT
!endvar
.EE
.PP
When
.CW "units"
reads the above definitions it will check the
environment variable
.CW "INCH_UNIT"
and load only the definitions for
the appropriate section. If
.CW "INCH_UNIT"
is unset or is not set to
one of the four values listed then
.CW "units"
will run the last
block. In this case that block uses the
.CQ "!message"
command to display a warning message. Alternatively
that block could set default values.
.PP
In order to create default values that are overridden by user settings
the data file can use the
.CQ "!set"
command, which sets an
environment variable \fIonly if it is not already set\fP; these
settings are only for the current
.CW "units"
invocation and do
not persist. So if the example above were preceded by
.CQ "!set INCH_UNIT france"
then this would make
.CQ "france"
the
default value for
.CW "INCH_UNIT" .
If the user had set the variable
in the environment before invoking
.CW "units" ,
then
.CW "units"
would use the user's value.
.PP
To link these settings to the user's locale you combine the
.CQ "!set"
command with the
.CQ "!locale"
command.
If you wanted to combine the above example with suitable locales you
could do by \fIpreceding\fP the above definition with the following:
.PP
.ES
!locale en_US
!set INCH_UNIT usa
!endlocale
!locale en_GB
!set INCH_UNIT uk
!endlocale
!locale en_CA
!set INCH_UNIT canada
!endlocale
!locale fr_FR
!set INCH_UNIT france
!endlocale
!set INCH_UNIT france
.EE
.PP
These definitions set the overall default for
.CW "INCH_UNIT"
to
.CQ "france"
and set default values for four locales appropriately.
The overall default setting comes last so that it only applies when
.CW "INCH_UNIT"
was not set by one of the other commands or by the
user.
.PP
If the variable given after
.CQ "!var"
or
.CQ "!varnot"
is undefined
then
.CW "units"
prints an error message and ignores the
definitions that follow. Use
.CQ "!set"
to create defaults to
prevent this situation from arising. The
.CQ "-c"
option only checks the definitions that are active for the current
environment and locale, so when adding new definitions take care to
check that all cases give rise to a well defined set of definitions.
.PP
.SH ENVIRONMENT VARIABLES
The
.CW "units"
program uses the following environment variables:
.PP
.TP
.BR "HOME"
Specifies the location of your home directory; it is used by
.CW "units"
to find a personal units data file
.CQ ".units" .
On
systems running Microsoft Windows, the file is
.CQ "unitdef.units" ,
and
if
.CW "HOME"
does not exist,
.CW "units"
tries to determine your
home directory from the
.CW "HOMEDRIVE"
and
.CW "HOMEPATH"
environment
variables; if these variables do not exist, units finally tries
.CW "USERPROFILE" \(emtypically
.CQ "C:\eUsers\e\fIusername\fP"
(Windows
Vista and Windows\ 7) or
.CQ "C:\eDocuments\ and\ Settings\e\fIusername\fP"
(Windows\ XP).
.PP
.TP
.BR "LC_CTYPE, LANG"
Checked to determine the locale if
.CW "units"
cannot obtain it
from the operating system. Sections of the
standard units data file are specific to certain locales.
.PP
.TP
.BR "MYUNITSFILE"
Specifies your personal units data file. If this variable exists,
.CW "units"
uses its value rather than searching your home
directory for
.CQ ".units" .
The personal units file will not be
loaded if any data files are given using the
.CQ "-f"
option.
.PP
.TP
.BR "PAGER"
Specifies the pager to use for help and for displaying the conformable
units. The help function browses the units database and calls
the pager using the
.CQ "+n" \fIn\fP
syntax for specifying a line
number. The default pager is
.CW "more" ;
.CW "PAGER"
can be used
to specify alternatives such as
.CW "less" ,
.CW "pg" ,
.CW "emacs" ,
or
.CW "vi" .
.PP
.TP
.BR "UNITS_ENGLISH"
Set to either
.CQ "US"
or
.CQ "GB"
to choose United States or British volume definitions,
overriding the default from your locale.
.PP
.TP
.BR "UNITSFILE"
Specifies the units data file to use (instead of the default).
You can only specify a single units data file using this environment
variable. If units data files are given using the
.CQ "-f"
option,
the file specified by
.CW "UNITSFILE"
will be not be loaded unless the
.CQ "-f"
option is given with the empty string
.CQ ( "units\ -f\ """"" ).
.PP
.TP
.BR "UNITSLOCALEMAP"
Windows only; this variable has no effect on Unix-like systems.
Specifies the units locale map file to use (instead of the default).
This variable seldom needs to be set, but you can use it to ensure that
the locale map file will be found if you specify a location for the
units data file using either the
.CQ "-f"
option or the
.CW "UNITSFILE"
environment variable, and that location does not also
contain the locale map file.
.PP
.SH DATA FILES
The
.CW "units"
program uses two default data files:
.CQ "definitions.units"
and
.CQ "currency.units" .
The program can
also use an optional personal units data file
.CQ ".units"
.CQ ( "unitdef.units" ""
under Windows) located in the user's home
directory. The personal units data file is described in more detail in
\fIUnits Data Files\fP.
.PP
On Unix-like systems, the data files are typically located in
.CQ "/usr/share/units"
if
.CW "units"
is provided with the
operating system, or in
.CQ "/usr/local/share/units"
if
.CW "units"
is compiled from the source distribution.
.PP
On systems running Microsoft Windows, the files may be in the same
locations if Unix-like commands are available, a Unix-like file
structure is present (e.g.,
.CQ "C:/usr/local" ),
and
.CW "units"
is
compiled from the source distribution. If Unix-like commands are not
available, a more common location is
.CQ "C:\eProgram\ Files\ (x86)\eGNU\eunits"
(for 64-bit Windows
installations) or
.CQ "C:\eProgram\ Files\eGNU\eunits"
(for 32-bit
installations).
.PP
If
.CW "units"
is obtained from the GNU Win32 Project
(\fRhttp://gnuwin32.sourceforge.net/\fP), the files are commonly in
.CQ "C:\eProgram\ Files\eGnuWin32\eshare\eunits" .
.PP
If the default units data file is not an absolute pathname,
.CW "units"
will look for the file in the directory that contains
the
.CW "units"
program; if the file is not found there,
.CW "units"
will look in a directory
.CW "../share/units"
relative
to the directory with the
.CW "units"
program.
.PP
You can determine the location of the files by running
.CW "units\ --version" .
Running
.CW "units\ --info"
will give you additional information about the files, how
.CW "units"
will attempt to find them, and the status of the
related environment variables.
.PP
.SH UNICODE SUPPORT
The standard units data file is in Unicode, using UTF-8 encoding. Most
definitions use only ASCII characters (i.e., code points U+0000 through
U+007F); definitions using non-ASCII characters appear in blocks
beginning with
.CQ "!utf8"
and ending with
.CQ "!endutf8" .
.PP
When
.CW "units"
starts, it checks the locale to determine the
character set. If
.CW "units"
is compiled with Unicode support and
definitions; otherwise these definitions are ignored. When Unicode
support is active,
.CW "units"
will check every line of all of the
units data files for invalid or non-printing UTF-8 sequences; if such
sequences occur,
.CW "units"
ignores the entire line. In addition
to checking validity,
.CW "units"
determines the display width of
non-ASCII characters to ensure proper positioning of the pointer in some
error messages and to align columns for the
.CQ "search"
and
.CQ "?"
commands.
.PP
At present,
.CW "units"
does not support Unicode under Microsoft
Windows. The UTF-16 and UTF-32 encodings are not supported on any
systems.
.PP
If definitions that contain non-ASCII characters are added to a units
data file, those definitions should be enclosed within
.CQ "!utf8"
\*(El
.CQ "!endutf8"
to ensure that they are only loaded when
Unicode support is available. As usual, the
.CQ "!"
must appear as
the first character on the line. As discussed in
\fIUnits Data Files\fP, it's usually best to put such definitions in
supplemental data files linked by an
.CQ "!include"
command or in a
personal units data file.
.PP
When Unicode support is not active,
.CW "units"
makes no assumptions
about character encoding, except that characters in the range 00\-7F
hexadecimal correspond to ASCII encoding. Non-ASCII characters are
simply sequences of bytes, and have no special meanings; for definitions
in supplementary units data files, you can use any encoding consistent
with this assumption. For example, if you wish to use non-ASCII
characters in definitions when running
.CW "units"
under Windows,
you can use a character set such as Windows ``ANSI'' (code page 1252 in
the US and Western Europe). You can even use UTF-8, though some
messages may be improperly aligned, and
.CW "units"
will not detect
invalid UTF-8 sequences. If you use UTF-8 encoding when Unicode support
is not active, you should place any definitions with non-ASCII
characters \fIoutside\fP
.CQ "!utf8"
\*(El
.CQ "!endutf8"
blocks\(emotherwise, they will be ignored.
.PP
Typeset material other than code examples usually uses the Unicode minus
(U+2212) rather than the ASCII hyphen-minus operator (U+002D) used in
.CW "units" ;
the figure dash (U+2012) and en dash (U+2013) are also
occasionally used. To allow such material to be copied and pasted for
interactive use or in units data files,
.CW "units"
converts these
characters to U+002D before further processing. Because of this, none
of these characters can appear in unit names.
.PP
.SH READLINE SUPPORT
If the
.CW "readline"
package has been compiled in, then when
.CW "units"
is used interactively, numerous command line editing
features are available. To check if your version of
.CW "units"
includes
.CW "readline" ,
invoke the program with the
.CQ "--version"
option.
.PP
For complete information about
.CW "readline" ,
consult the
documentation for the
.CW "readline"
package. Without any
configuration,
.CW "units"
will allow editing in the style of
emacs. Of particular use with
.CW "units"
are the completion
commands.
.PP
If you type a few characters and then hit \fIESC\fP followed by
.CI "?"
then
.CW "units"
will display a list of all the units that
start with the characters typed. For example, if you type
.CI "metr"
and
then request completion, you will see something like this:
.PP
.ES
You have: metr
metre metriccup metrichorsepower metrictenth
metretes metricfifth metricounce metricton
metriccarat metricgrain metricquart metricyarncount
You have: metr
.EE
.PP
If there is a unique way to complete a unitname, you can hit the \fITAB\fP key
and
.CW "units"
will provide the rest of the unit name. If
.CW "units"
beeps, it means that there is no unique completion. Pressing the \fITAB\fP
key a second time will print the list of all completions.
.PP
The readline library also keeps a history of the values you enter.
You can move through this history using the up and down arrows. The
history is saved to the file
.CQ ".units_history"
in your home
directory so that it will persist across multiple
.CW "units"
invocations. If you wish to keep work for a certain project separate
you can change the history filename using the
.CQ "--history"
option. You could, for example, make an alias for
.CW "units"
to
.CW "units --history .units_history"
so that
.CW "units"
would
save separate history in the current directory.
The length of each history file is limited to 5000 lines. Note also that if
you run several concurrent copies of
.CW "units"
each one will save
its new history to the history file upon exit.
.PP
.SH UPDATING CURRENCY EXCHANGE RATES
The units program includes currency exchange rates and prices for some
precious metals in the database. Of course, these values change over
time, sometimes very rapidly, and
.CW "units"
cannot provide real
time values. To update the exchange rates run the
.CW "units_cur" ,
which rewrites the files containing the currency
rates, typically
.CQ "/usr/share/units/currency.units" .
This program
requires
.CW "python"
and the
.CW "unidecode"
package, and must
be run with suitable permissions to write the file. To keep the rates
updated automatically, run it using a cron job on a Unix-like system, or
a similar scheduling program on a different system. Currency exchange
rates are taken from Time Genie (\fRhttp://www.timegenie.com\fP) and
precious metals pricing from Packetizer (\fRwww.packetizer.com\fP).
These sites update once per day, so there is no benefit in running the
update script more often than daily. You can run
.CW "units_cur"
with a filename specified on the command line and it will write the data
to that file. If you give
.CQ "-"
for the file it will write to
standard output.
.PP
.SH DATABASE COMMAND SYNTAX
.TP
.BR "\fIunit\fP \fIdefinition\fP"
Define a regular unit.
.PP
.TP
.BR "\fIprefix\fP- \fIdefinition\fP"
Define a prefix.
.PP
.TP
.BR "\fIfuncname\fP(\fIvar\fP) noerror units=[\fIin-\^units\fP,\fIout-units\fP] domain=[\fIx1\fP,\fIx2\fP] range=[\fIy1\fP,\fIy2\fP] \fIdefinition(var)\fP ; \fIinverse(funcname)\fP"
Define a nonlinear unit or unit function. The four optional keywords
.CW "noerror" ,
.CW "units=" ,
.CW "range="
and
.CW "domain="
can appear in
any order. The definition of the inverse is optional.
.PP
.TP
.BR "\fItabname\fP[\fIout-\^units\fP] noerror \fIpair-list\fP"
Define a piecewise linear unit. The pair list gives the points on the
table listed in ascending order. The
.CW "noerror"
keyword is
optional.
.PP
.TP
.BR "!endlocale"
End a block of definitions beginning with
.CQ "!locale"
.PP
.TP
.BR "!endutf8"
End a block of definitions begun with
.CQ "!utf8"
.PP
.TP
.BR "!endvar"
End a block of definitions begun with
.CQ "!var"
or
.CQ "!varnot"
.PP
.TP
.BR "!include \fIfile\fP"
Include the specified file.
.PP
.TP
.BR "!locale \fIvalue\fP"
Load the following definitions only of the locale is set to
\fIvalue\fP.
.PP
.TP
.BR "!message \fItext\fP"
Display \fItext\fP when the database is read unless the quiet
option
.CQ ( "-q" )
is enabled.
.PP
.TP
.BR "!set \fIvariable\fP \fIvalue\fP"
Sets the environment variable, \fIvariable\fP, to the specified
value \fIonly if\fP it is not already set.
.PP
.TP
.BR "!unitlist \fIalias\fP \fIdefinition\fP"
Define a unit list alias.
.PP
.TP
.BR "!utf8"
Load the following definitions only if
.CW "units"
is running with
UTF-8 enabled.
.PP
.TP
.BR "!var \fIenvar\fP \fIvalue-\^list\fP"
Load the block of definitions that follows only if the environment
variable \fIenvar\fP is set to one of the values listed in the
space-separated value list. If \fIenvar\fP is not set,
.CW "units"
prints an error message and ignores the block of
definitions.
.PP
.TP
.BR "!varnot \fIenvar\fP \fIvalue-\^list\fP"
Load the block of definitions that follows only if the environment
variable \fIenvar\fP is set to value that is \fInot\fP listed in the
space-separated value list. If \fIenvar\fP is not set,
.CW "units"
prints an error message and ignores the block of definitions.
.PP
.SH GNU FREE DOCUMENTATION LICENSE
.SH FILES
@DATAFILE@ \(em the standard units data file
.SH AUTHOR
units-2.12/units.pdf 0000664 0001750 0001750 00001310161 12607541443 013726 0 ustar adrian adrian %PDF-1.5
%адХи
1 0 obj
<<
/Length 587
/Filter /FlateDecode
>>
stream
xкmTMЂ@Нѓ+z&ЮСБ?tBL$ёАуd4Н*Д.<јяЗ_шЬfWЏ_wеЋюr№уc;ђъ`GцUOлVз&ГЃјчОіЄЪЎ[vяжц6яWл7ёбTйжvbЏuYt/NМ.Гѓ5ЗНъџЂЅ=хS>
stream
xкmTMЂ@Нѓ+z&ЮСБ?tBL0ёАуd4Н*Д.<ЬПп~UЂЮfWЏ_uНЊюv№уc;ZфеСЬЋЖЎMfGёЯ}э
I]/ЖьоЭmоЏЖoтЃЉВэФ0^'ыВш^x]fчkn{еџEK{*ЪuФpg6;Ео$4ЛЂ;ЛЕgZ8, ќВM[TхPЏRJGЄe WxmНёїE7ЗЂт в"/Вюб7ЛИІМ§j;{YЧЪ"1ўtmз|ЃoМirлхI ЩcЖзК>[TвЯEnn#злћўbХјЙћвюЋЖBSЌиEVхЖїmіхЩzs
ЋЙgЫќЕ)g ЯRЉ№133wФ xAФbъэ;ЌвaGL 6K& 0+}& і"?сА(вІвa/
Ёcь,!ЃНЅю-fі3Єй *IУx {aЊљ№sIC%в№hSєЂЈ7хЃХ}HЯ=ХЄIYЙ(юъjХЇ
џZѓщрќ4{жиSOис5сZ фЎekxvKКЗЧЌќї
м@2aТ>
stream
xкmSСnт0Нч+М$z иЈ"ЄФaKUЂе^C<аHрDN8№їѕЬV{Hєќцч= ќњиS `ОJё m}u%впE Y]^/`Лw ІЖoтУех :1LЗйжVнomyОшUџрTй жУ ўvЙЪѓDM^ug {І
ЧА Щ pmUл7Ё^ЅX[жєку{=1ю +kмНЈ8
@iaЊВЛЏш_^|гМПЕ \ЖіXq,Ц>иvюF^ёЮp=!9ђЬўк4gРъBЫЅ0pєљоо ёs#P~k@hZ+vQжкІ(СіA,хRФбf5џФІq8>KЅТ_ИX NHцад3$ЄЧ{<н0*Ђ5 cе~џPїѕЪЏТљн5WТ42^!0^#rqxЦE3xЮќ ё
Њz)cвgl1BЬювАѕ?Xqћ!ђNAЈWЛA*d§1љд)iШЇЮАХчаѓ т9чNVfЄЁkєЏVфaUJќєь?%Э5иЛbџTWЃ=бЋБЎОПЩ5ыё2щfш&p2pj ГV^ѓcHЃMcVYxLS7E =ў1тjЗ ОgШШ
endstream
endobj
6 0 obj
<<
/Length 272
/Filter /FlateDecode
>>
stream
xкНNФ0{?
ЫЄ№тнџJ@(а Й $"w№ќЌcr:$ oЂљЦкЪAЌЬЈ_о]ўЮЏК їз
Пї&Йџ\1yЧр?ЬPM ХяЂUgWСiВр]tКэs&чBКэєSѕ0}m8ИъrkЦъГfЊvѓ~ЯчіFmZѕ~tЯrЧё"Xт>яtЏю
д9MЁьh!К\(фM7 2У0sEXІ~3V,ќЉEр}оЂ§XRЕ$Zз ыШыSV Д
pу)Ыф§ BюН/њѓn ЖciчvчщзJаљДxф ' uF
endstream
endobj
14 0 obj
<<
/Length 718
/Filter /FlateDecode
>>
stream
xк}TMoл0 НчW;Щ@эъЫ_иimзЂУ0 ЛЫКk;Е0Ч.leYА??RTуЄш Lљєpј рAІT\ш<Ј7+юМгc@Ц№8$|џ )шЈкEЙ:ПN@№Ир
Ъ5^'
Ћ<
Ъ&јЮЪЮЬaЄвmЊ!9лV=§ыq"уцг wБ>xЯў гкi6у@N qЧ,aЛЮдЁЬXGбЇ0C;AнЏВ]
жЃытWш0XгЊЁy!ўGљЦE"hКъыm_YL4Њ РхјхїyьаАЈ8zщq5њЯЏS}Ь]ЄbЎшvЯEBШSЁЇЯСGЏ#ёЕЗpSЁюЗЃ У ф%ъСzMл^Б{Ё4§ТaЎ^JЙZ
yyНqИz_Ўўў?
endstream
endobj
50 0 obj
<<
/Length 2131
/Filter /FlateDecode
>>
stream
xкэ[oл6Чпћ)ќ6{9о%эЗ ЖhS У6`ЊЃЅТ ЛэІ§і#ХdJдІЗтФЯ9сџчCCЬАњGfeЁчГеХ=мОлЯЬ7/~ЙGьsKѕр<љрєоO'BЬF.Шьєп 9*2oюєlічМ^ќ}њлНЧЇо єѕG 3х1CЎ=ЊdЮaмx;]|^О^W%ЫФ|ћЏy}Ин,я+ѓВг1S 1.Љ6Ѕў:#Sc,P1іNЉwuuщЖУ ЂУШvјaS;7cј rТHцћYЙyНЎўцдq7ѕц@pЮ *иLrИ цHЈ_!\Ј/ЖтїписK0оаЭъРprУЃЇ ёЈбгsfМQ ЬЏЕІ\эыЭЙaцВоП RУн4Л5вШBj>+J$ьќMFЂ@F1DвЃBBфхЬzcW;
B@~Y < хС_B-{ьщvГьAf2дњC BЅЪЯфЫоЭгTщСјИє=1xHzЦєiZzA о^ijRРЃъ/LИњБоnТqЂ>фRхoѕC~э7#hиyF7>F_Ќ 14 ћЛ"ЙкС№`смnTTQГ1?оЏын cѓн~{Q6 є\бГ s$ыхj$фWЛИy Ўr8\xЎП:нДВ Z 1Д.ГЮдyfЧяп6еnЯ9jSШќфHВБг79йtуЩj$D0Цx '^`$Ља'goKЋrІмo`ZЩИЪ*SЫ/јџЦRдЕEWЄг0H_=rАТ@F`MЛєАfтsАR ыЫУХЮ,хцЬ,jЕbUSmV§][уЋзWиBaєлЊИo"сY}эdOЧЈ3Тj1atщ1*ѓRГ==\,TЮ{m3CjчЖX1lEЛ§UvsЭ
6 ХЮ@
EШED2bвЅGQU$sЛ2Ф-ѕzПЌ7СEЮTбПсAЗ.s}NPгь Є<!tщd9Т8
E№ySНЋЗ_TЛУz dSФ0Н СЯђPuV =йNЈk#hЧ/7І HЦLњє RђЬ!(-ЗoзѕЊмWgнжЭЌЦЊ\]yЃїvdОцХлЖЃcІw:8~| ! іЯAcдЄ zhAнвЙЅГ\щ]мњkййэfЉмзЏыЕBH§ц3tчџnьyIь[f?кgњgЪЗ/ AЋЌ§ж
YЦцб вт#њ/ЯnOЃфt>§ј B|vaёйwxдlc9CВШ]mlmOЗuНЉЪЦtмКо=uЖШ;нЪЕсЈњ`0ќхЯїd(ФџнзWв_Ё6йРMBKЩCсlУЄnЃVRп(;е{ѓъBЗЫВyЅWЃFщWюMхЯFчw STF*^ ьЎKLNЩyH$вщбєщщ ьщrgћ7Ucж=],&>тоШmиЧшВLЇЋ3Ђ *M'01К>W"*ЮЅq ћ<ЉwћбnЗн2DmІ2ЯьЗцеЖYСuЉWёk(ЂltЃ[ElЬгWЮ@jSCp01%>Др(ЫЄkt%lЯЯ§ххzuXџ#ЮщwsЛЧ
сffВоР@Bя $и\шіЉѕ qЙVМєеюєЖџE.ћбB\щЊWAnя%ЇЊцщ№tR№@5iА+#'щSУУ(""ѓMCЯ§Г3,ўа7XЗ[L<Лм\ѕіхaіYСIgџШщвuRвСЙЄС<#nр3МЃDђФU(и fХlwpЪ}iJz]EњњЩм ВвEЧьУBЗ{Р@bЛз! d ОЄO ІHШ>WMИмаІ]RД7е§й&la1нџзOПzbО+0c ийJg
яSРHЦ@Iњt h9ёЋ? ?хЊЕЇ цђю 2ѓЩ8 zвв,dЇДOS&вуФ#8=ЏЋUuYяlьЩаЪ9њпmмlNЅ3FUd ЄOкўв"" Иѓ>жі) -їзuЙ,JB BА[оCсdч|:NNPZ<с4№yT'щn'.?uД'-ЊЉWЖ4:ьп lЛыЄ-r .pІ&B~5uЄr30ЙEToЂ#КHЦt јЄ Ћ/ИОjяCлф№в^V^щK|е6аТqrї?!>fEВzLO!T
ВГрщ d ЕЄO*~юQs%гЩК<Ў5"GЛюWnY+ьtf;)f!?fA$cЬ&}:f шuХлI]m
џ{}цў;qо YШЛ3Т2б*6Хn|E ^0F@L:t fЂиoС|еїМQ ђ.ВЋ2!/и _УВnѕLe7>A%$L%уЪџ3:ѓ
endstream
endobj
87 0 obj
<<
/Length 865
/Filter /FlateDecode
>>
stream
xкхMoг0я§9ЖzўЭ
і%аФat\Ќ #RNY6~=vь4Nы8%Ѓ06MкZ7іћц}јu"Ј~P$a$б|9еhyч#dЏЊ ЇЮяfЃЃ3Ц"EГoC H"7ыЭвшЫ8Я'_g FЇГЭJ у=Cъ+wbЦ*&rЌcъєU
Ф& Т)B/V)AуyВШ&ы|Uш4Ююtъ. §FMцБљУ[я1xј}[dЈ*ЕрhSQM0ѕR§BИТд qyеѓЇЮ fлaЊвК
LК=бWюФlЛ UбKЕ, ЉR@+]АаКdFNмщ ЂFiђєМгнQVЭЈцњћЪљSg>лaЪКє(ЙQV@@ыэT)Вoг4з[ВP; !Т Џ-2Ђ _Щ{FшRЪж}ИRЭ!Ѕ\Мyr2щSj+цNЗф ТъnIlЗ<-&ЊYўШЫUБЬЊзk%UЬЦ'2OЎйП
JBoЁtг0
ЈЎХр>ч,шsиKиЩЄp0І&ЌЯ4qнтЈ%|Ќє,яD 9 =kmшrЦVwИ3Э!g\Dxq2щs&S9УмУЌ1WE>7ш43ц|КПНVхк/cхOІb-иL8р@ёафаУ?Mгg`ѕ]Ы№чџeЄМи=WїM_ЪцбEнVj8їfy^іN&}є15 Фђычп№NеYВИ1 пeVЬ ЭЛгЙ>)|O+ЩeВюh-XЈгNќ9Кидiq+DЁI `LЊjQЮ,сД№ыфЮжњxЕ\&EjЮGshK ќе'Pќ7цzѕ}Іч, з*ЇIНpLMХ КJKяќу=щ#uY'іџTїѕЙл|uЋ>ЛШчYqu>
stream
xкЕX[oгH~ЯЏGXЩ\ЮмB
ЋX@аJЫВ<д-ЉЇ-џ~Пуq mьРn ЉЧ3пwnsЮLPDRB[ЁНку $Ќ1ј"МѕB(ЂУ#фН0XЃ-ДxИIxTvXb ъMqH ф@фI№pХab5 ѓBka- j!ъј3^&:Ш*ШE@DШсNNЪZ&)ЮdАр ",u$z8ШЅїЅ* DЦСpВЪPi5Њф`lРЛRђ ЎphђXЏ
SјаЩ
ЈцЌr"рб
s&NЂУг[p ~бJa
Z!РZaI ,w!№,mЎDр\L< O2jЂ5ЌжЂcЫ4МрЦ +НтРТЏ^y 0E#< ёУ b e5|ц
G
ёХD#(Oq~ ЦNGlG ЦсeЮ S шf ;пІ№ hэ=бD; ћлg>АА Ш
Џ|Д@@Nlф|ђј|
дRьЉ }ПРовX`BўбQ0Џ0;` Eh7Ђ, C9d1q
G&гуo_ 1}3;/&гguеUГ [ыэdњЖXеыхМXaЕ ў,NЫйгњZ|PјрЁJHцуЫX(Еb ЗШ/& =гl Я`=тfшEjОYжѓwE#>@Ѓbz\\7туЊWIMЗЕ>wQsKЗ6ФwQЮЉ ЦџЂмєIUеРљР
ѕай:kЈГчЪ &?l~P~d3LF1ХdQlFБХfQlFБХfQlFБ
2
eЪ(Q(ЃPFЙхЙжвЩєнњSгОП,Ћ/щгzyZ,ГдGvф @ЗЇЈd ЦкAфIЦwbњ{}\щИЇяsќюЬІЕD§Эl$jйй\TRQfC5!ѕГб8lNKnQ-з}р0l$ ТяЌЩwtdЄїНln лI:2 Є2§ЖљqlЃЅSRшIЅ ARg ЂIНtq$:OвvBAK4ь^К4 ђ;`KчЂ t:ЄJ|ВBМјФФt(.8tєoq5СЦЦIЕхУ ъпZФЇlъјt8эіѓЛђY=hє8ё0Mvhп.gНкvtdадЯgGтsмВ;-ЊІ|4;OѕЬg§р^зn >P@qlљPE рK#ёy%}Ш|ЈиL?Q#ё$яјаpНшчsуфб9ѓгэGхSKJцгJтJгЯчЧсУeKJЫБLi/Ф=Ўл.б^}d$гЯ7R{Р
6Qц ШеЄ{љЌ '?q_иwэH9 ОЮ>эЅГ jБіTЏЕВ-"ѓiкvP:ЂЫжЅ$г@qБ#5ік ЃоХ_`;Тђ|ўѕўoўЇџЁZ/ їоSЗnжи~Юtуі 1vsХIFКsЧpћZнџЛжRОJRV?фЗаНeѓBV5цeЬЫmйКHwОQv[. L*[|п 3'C8
endstream
endobj
267 0 obj
<<
/Length 3554
/Filter /FlateDecode
>>
stream
xкНZ[лЦ~їЏа[Јжb83фLаФM
E&Љc \idІDНќћл№"qНk( /Ус3чњ#ЊUџд*VЉ1a gЋэёUDГЭ~љл+%ы6Аp3Yљ§ЭЋЏLТ<Ъеъf?%uГ[Н ~;]Лоc7ѕiгрnГР5m ЗЃЬj§ўцЇW?м %ZП#\yХR
,ЅЁVI,,й,%Ео$VџXo0c40sWК{`&MzМ|§cnЇ$q
EыцЇпј
<Ѓх7'эtБVЁNГgi*m§ВsShуzЃA[hMс(g§д4н]щdЮ=зЖnЗyPxњnи hЪКuэcлЙcЫЋ@4ytEл7юш,?ьj~и \й пЈ0b UЂ_їЉ/yЪњЩ@чШ^k ар0 7Їљ=_qsдTПVAуpфљзряхGВ(ІqфГ?ђЫmy,ЋBШшкзp :оТЩЁ8э*в{v#ьЋЎ3ulџўfB`!о\nCьќъЖ
<Ў
онЌГ8pЧ3.JДшz4(ЩЕЈпФЉ
Ю тЌSцђqЄУ$ђщ`%9вI:иS$ФШ№Ќ+5[ЙЂQМгд§Йїu/Ш>aa№`пдВЌh=xmћЃ,"
+E.t*ЅІІ/ЗћP*O xў8чя wт'GзC,ьымѓ\ѕbЪoя(dДXХ0*!Эo|_ДхнFѕhr-?№qЎм7/ rнѓ AЙрЖ;8 єюHw(:Нy-|$Ѕk~a;Ыx^6ЫД2ф}ГNT ЊZpR
nie(В
ф tуI№мыШsЏђ ї0MZЙЧ
5_чЖДШНѓP Yp!п}ЦD яFЋS+ЖШ ѕФГ ќz kрqь бa
Ш2u:8*пє#ђo)јі;ЈЋЭЙoиЉъVnIXЅxMљGЄт-?ьЙaыШ&IgЙэЋЂЋбЩLв№нЙ _љШЗръYxѕА-б.AM 3Д3MэLЂ* ^ТЊ#пЭm ћ5ВЈF<№ЭБшЅ хр
z,&б&aИюJ6yfUПуh ЗyбJГ mМыЗћдзt Т,шa9ЉЏ УlуА1"SlBЇ%іeГ fТ Џ#П(?pЅ%ZоkI8 oPкХЩbЛэAwrМр.J^-JР'^
Ї8И?ЂѓдЭЧЭр$'ЮfAUћЙ+-yСЂrєЉКА ,9Ы Р$-з апяЪБЉЅй@Бщ№&Ђ;BЗМЖdR ршKD Оq!яhт#QYA6ь8Нц)JзMCЉl[Fб#4џўfB`Ю\n3GhШ_Z>ЬЛ7xvиNbфo щ`єУЈЏїrЎ3с2|Q]Uq
Xjfћ 0еЯ хЈф(ЮЇЉЮчA№Бб,Т{л9':ЊXџp%EТ:ї \]С#|ЉФхХsФ'cFВ>;кH ЧХ&б1йђ Ьй/чDІ&К>:Т;Ц;YК9ЩЦЅ#tSр! fy-Й]ЙsГeђ=МЕТ)NqпЏmOFsEтфм*3 Ё~СЫЖоЄXћвћ L<'3с S->иСЋЧчФAлAь+н2ЁЇ1ТЏ4сkIЪh|АsћЊXНeи{(XшЈ\ућ №!3єzyьБEрfwы$ћ (ЙsЧїќPњфУЯф Тw< & :33BRc+з
ЈC
"^
gјтBTопL,ЂлgoХаf.Aюэ$Н|ф %N"[<xЃЃЫ#(НЬьHO7Пњ\ЅHЄ,b;зnђ<p0SfГЂЦOYЗо Dя!ЯМOЗ0jТЬЗ4V_&xЛЦРeGѓЦЖБЅ
J Њчч;vВ;vVт69NghРwb9 вq g\;+8ј
тЩТЅ№dЎЌхЬH$^ з
Јj,ђ:оl RxGЁўрaЕЦџt .|АГ фFVШi. `@!єЂіnЪiHk! р6TmЧр CЮpzјfБ!
8ЁўІoF}N m%Ќс @ L=8фvюяяУр#"Ѕ З~ЭЏ зxM,~йзљUѓ №ЧО|p~>KјЪЭ;]ЛсUO p ѕп1PуCqчОYДХ ФџОdы рџYIA9ЦТяОJ}r3ЈХуdе_1e6зВпЬJщЙА Ї=fijТm3ДA`єPљђ(Ш\u=аfZ:ЯCЃв5>TeЩЌcs4 j{Р"ЁЪ.КcюЁ@м-mrЯm/n~PK :iT ЭЌЩиЫЂНє ЂЭпAW*bе
йgu+MџН~ТrbѕЂж*
щИјР88сІv
6ЎЭѕО8u/1WDqЉP хA{ЈћjЧу лЅЉ |р&Н-МЋ^ЉљњЮгајЙо(0$ПЫдІ,НHxO=t
ф-д"X=o`IІб`ОЭz]ШсprдкрэЋ[ў+6`[CПВqХcхѕ$
Ђ*oЙЩДЙeкђ
Чeхv|Wфn]\з8 s;ЊЅИ}"dфй
iћН*з9оКn,t8є\шЇтшИЄahlУ83+
}WуУPy3!АC/ЖУP ВxMwПxmаєЏP pЇщFОРЦЇ&ПТ VГѓ|ЪъgИП$:`аH0(ђrЌсЊ<сoвИЧ3\ед}Зh &Ѓ^b`6йhЗRт6
ѓyвћЏ ћЫNqСиN№w 0АџЧВxhжЖLч~КVоtMЕyГ3ЫыЎ%ZЅgДўКH+5WOV(џџ*O;.~лсю ўuъьyіЁ:Сz/<Бsќћљc|+)ћгЖ|Utр Џg%>/[vГ~ vЬJ}џфљБЈ1cMќУ q)epz{aq:Е`fЉЉРЖЄr ЯЧкі|Г+лs%gРйРгzpЖ2cШaoиЛMлё
њХdЯ3рtч1M м Ъс@мЏх5ЧЂљ8ђЁъэЂЗ$ЪЧb3IбвЁ?јгbF гЏ|ХДH] j;j3В9 1СL~пЏБEFmцD+иЕгQј4№ЇЏсљбЖрFZ/О2J0ЧвIЈЌ$зKќ$ WQ2 AлђD6ѓZБdгVА>б
Ќ!РuІИБiР>Ё
FќѕT 4IИћЈєЛВ5p:КЭ|sжЙg
TЪ1ќєЖ№ѕЖ6 T'9c№vЯў=џЁя
мУфѕњЋ-ЬЦ Вф%P[ЇњjS@mLЦ УH
ЉЅЏ оНV;"OЖКЇUG@ЊеЏЏўЩщwњѕG9ЯІЋ [jfш$>kљkЊ0JSќј#ѓљљћ Бj`LО@Ё9ТЏpNјІЄЋ
ИnFXQмЭ'йё ФеЎ
X[ЫЬwBМ)NэзlТ+~
rМЙ> Ш / JaЯѓФШў,@,cѓЯЕЁM-џ%бka2Vtз$R?_ПC;А№x§~ КT№дЙІD_ЅD§&
cЋ>{*ћП* ѕё+ќlс|В8}FЦ_ТЭ23Р^Бі?cФ#ЪЊхЩНG$гR№1ХџџDюЖ P Y:шОX nЁѓYывjрїі ~n9ћHВеK_К%а?+ EиЕY`іCNъgиїB рў Е§3
endstream
endobj
275 0 obj
<<
/Length 1721
/Filter /FlateDecode
>>
stream
xкXKsл6ОћWшHeB Сgzh:M'=fCЇщІ STљАуп}Q"e*v Ю8\ }сл]РjТ?Е*ТUЧAЁѓUYн4люVL|ўхF ўѓУ§ЭэЧ$YЉ0(ТBюЗSQїеяокѕнкуићЉЉзQц=ЎЃмГmч`шЧ*ЩS/ZџqџыЭЯї'EIНб"ф|iR:5IidaОJs ЈXГ]яжА5ёт(ШУ<.
Д $њ*TТ,ЗЬa ъ .ѕьЋ,(тЗ=э].юСЛ,їz{8tL>ЃћЭ ѓ{г3ЅBўVЖА0mџЬИЭ<Ќ}з Т63ЕЕЖРЪЌ№юїч:[6ѕщэ*ќeиvOaэ+ЏэАнECБ_чІ<'_о Ds<ВЅыejуZ[іАЬдqц}їЌЗw JгЁ!і=сСsН№Hф|^S F}F8Ж
ЋйQ,ХЩаы
ЦxЖ 'ПБЎд3m%Ђ wЎ.-ь{Ќ'[z
2Ќ АDч c>_ NМO=OТ)7"Jм
gwIЙnсшСNЬ9ct* ЏДаsx"PЪГ$T Ь*b(k Ћ 2HИmГkMкuGpУlЧ1E б#Чв уLз@|\ee; в9cУЊi
Пl&rkgЉЖШ&ЂчИчјidY26b2JЕX&§fЊуСђьнГ2iЩзД3v)zц7ЁgMЙFXТѕGТЫaЅф(ъk@jйѓвЬUJР; Рк0ыџ$iex^јXе1оDРЫеоA`'ЏX rС1Ь"іЬљFa- B ЉLPьj2і:p?mq њ"4b05дMН$ЇЁоtяD=ЙУAђл^fїЖ9 OЎон-х6ХПЁhl!{ѓhяDлъnЉОИLн їЌ%nЙЪfgјюд ТPщ(O2Ѕ$K#ЫmБe:HIєФіы<ікЛA]Л в82Іэж"х A8<5> p \Uй3PїGсvcdЇсE
I)Eе T`Ї ЭПЃкАў~п Љ7=6щ(&тHуvќ R2B
хBE`IQК
TОQФб`^иRєbЯW8ІЖ >ЄXћ7z щVћhкDУТa~1скjl$pлКиNђ o Щ1ыЉэ-Е0
]Рї mћаtv [IЈќдVcOХkAЈ Ao+Ђьєж2vчjSСяЕ$h!ѓг|
ЕJг4[sЁјЅЏa*&%љ4 aV-Щ{SB pД P7Еа-xYJvOeЉ^УL$ЙІ'ЇыьЈЌщьЗЌЊtа№IHIї*м@УЎQUд ^/ Џ+IъWяўШ8="ЉЬшСКа
eмЯЂџ0пкn8Р§ф(ѕaкШВ§жЗ!ЗEЋ7Ў4=')ЁиД1 cYѕ\іFZШи67Mms#ЪќѕМHљгьЋnЁт-%Gч, пЫЬCХGrљСНЧыnКц
ЅЮѕVОћ7|~ Лф
ФSn-Ш хA7 pјнQNЈz,x@іW.Ц)аq~Ўv]п:И-8 -тyБУчмд~ьF}№&С\I!э:ћ]Эјr вXЭ#јЫјFюFV^ |FЊl*Я љс n W*uФЙz Н§іF іЯ№rќP8ЏКhТД.ы"
Bш]Щ
оЙпёВЖcУBaZkќIИ?z
ЃыBўVЧ§[ћмЧn+wАзКл одi T .(џWЂc№OzхTгЪvKѓЭ Јј$бQХ еP иxКф3П,67М]ЋЁt НўvHE/ ЯЈ; *>=ЃyС№,<;ГГЃнв юaQAщб7Aг_МcР6идЫУШ/ГX
АЕ6(xзХS90є%|Ѕ ујXыиЙЄN_н %]zAЕOгЛ kJ<Н\=!lwупџЂq9
endstream
endobj
279 0 obj
<<
/Length 2265
/Filter /FlateDecode
>>
stream
xкЅkф8ёћўљviДG'pм AшФБТvwТІуо8йоЙ_OН~lіf3вЄR)Ыѕ.zHрW=TЩУ&Mу*+ ъуАУсП~їF нзWП{zѓјЧ<PI\%zxк_Гzк=ќ3њ{п~ЕNг4њНыWz}Zщ2ВoсuЊМ,ЂtѕЏЇ?Нљіiо(зњ!х"з")UЦхCQfБJ3ъG7`i 5ц}Ч ўБqгТ ѓЕJcпбM?
§о;z~љpxЏzфЧЮ<п№QЬЈv§о
GГmЛv|7ЭђИTл:оаOiзJ
ЭјyМлглњ}К Н*рgcзI~/яё2ИЗъzХJІUkцњУ ЭWFЯhOдОИО{fшhгуп1ЃучOЪњрР&рЉЂнJES- сQ[ТzрчЮv/"с%|{ VoЇ аiАоЫсnќ#нРЁJа ыл~ДУRPc23^_gIн(ўплХIИ_alА_-ьUqЯЛ~УдЇС OcМZgY }oQwn%а ъ%Э"ћйРёэЛ%)жZФНВшRTќЧєўУѓЫ!ё5ї§нЗlЋ6нє-ФoПсВk]0јЧйПџљkD!зТМVU,аS№87ЇЌXD{PшЪ4ЮєЌ§rйВk $dmПkk3ZЯћ]fgЅВ2qk+~ЯСRDлег%#эЧЩtТЫ1J| жцAЏјљмД5^УЮЉTШoMгшЦieСч,Dрј9Ы/ Е F8е E иЖНсшD$F'>9!ЃlRL<*ВlazйЏ?ЃwыЭ
Ш§дa$#8инЂ&ЛЅ4ћS'ФТBТa5
ЧHеЦKдxwДgЖр.DS=<ЦЖVШN(IdЭ ь(
ЭР_іаPIPAЅЪn]ђo g*ъЭqN~№:IёаXЦСo ёмЕGлcEэ0Чб':5<=ђ7№э8m<ъЗЈPПооэІaqнM%ЙЉЏuLG
Ќ
fзbЪA%YфСА}< ћ ьрЙэ:ІпВBљe>#БZq~б!NёkлСИvTy>aУСНи_Јvс3SТёѓ*jWЄ7CШH!GЯсуdХ ЅщSGVЯУЦ ;*DІЦbYfQYKJZYњЅДЬ
yв
ф /тz'ЙЪП_
й7Са=УQМqЂx) jlЄn\wЉd`№ЉLВНфљnЛч@ $ЧГ,ў"X{Љљ:c"љjбљiНСц)г ЪФIЅUЂѓЄzuу3ЂU-ГrZч cиЮSЬЁfЗх/ЃP@ЂcyсрШn 8x*Р4шы]ПnЙЂЬp NМV|:jYМgЛ(@~Н Б{ЎkqTцД!9sъТщап%?гgvVrуБыќsЯ зЛIЙaля~йп~ЁCЉЇ бЋОк cs4опt HPЗCнйGпю k2 tщшuяѕХ9зW,а9'џЪyриЂ_vIЅБ.6K.rfqVхрЕ9ЕыЏэkўl(ќБоY QЉЬb%A w#sКЅЯD-1Ё2OqO%sіѓH`ШєЯђбєИЧТI/ ь?y+кјаИwїйЗsќ}Ёх&ї-S,vм
кИєвt Бщx/IpAНEoєцЎх}У Н+уЮі\Q оФIYмІЃR_MG№r7Ц№ЃkН ЌsЇnїLjJн pA9*щ
О Єtn_Лtи*.ЋлЁ9S А<РБVъџaѓ<ТфU"=9c9В^ЁЏ
§.ИcHKЬoўд.ЊЈXхЌЫJtYRWЕc0є8№кA#Єм^С< w8\>6ВЎБ^ 3+KQ$6оНB§.х^ЧЊ\V6јT~9/rў{В3+aГНОСИхыЫЩЮЧ[7сTqОeЊW96Ёщ_ `E
чMЎm[p
BЉNтЧи@!ІЊЪк5D\
!U7ЅсЃЁэKЁБЊfлФ~AСКыh яД-ч;&Оr@ЯУпИAќv"$єо ЈcKЌВшGьЩ №ЃyP7аёB}мTњЅSaщЇљєкыіn.єШ B^ўГwEЉ QьхaЏжСT KЙ+nц/|NZфЬЖMч_Њ;3Ъ-MhФaМЃъаLJ4xВиі!Е
ЋyаMЕО Кt IR6 БI4ЮfЧє ћZн_BiХЭ-sЧЃЅNЪ4Z]Ip4Ђ`|9Д ђO
&ъЮ/.
ca
ik M нSшЪа
!ЪёпYu_QЁждЭ>пшРH}А=Lo>
stream
xкЕYKsфЖОяЏђ%д"H№ФMUrpiCA-IШ|H+џњtЃ LhЇR:§ќњиХ№'vUМ+в4ЊdЙЋлwБлэЯ;Zќ№с`КУхwїяюОЯВЃ*ЎФюўДduм§;јдqиiЖн>)Ч}RК МЉШЪ<ћџмџ§н_яgAYlд)ЅR*Q"2Щ*хЅD*IЅt fy|LwFСwпWљО кМіzr8В[ЖY r&ћЇэТн>СЈ{Uцq&nщг['
"Q%Ъ]ЦQћfк|IЄQmnYrOєалsЏк}(Г,ЈUG}ш В= 3ЂТиЫи№Avw6л
$`;>ѕ >Гj[е QIOЅ }(вHРгЉзNGћ0IpП/гР Ъ*8тГоЋ8
FѕЬd,fЅэЭйtЊЁm4VњЫCЏДе1jM~
[ЇiёQЧy<узvТ2xТEаAy№ёDt ѓхB#:тЈЪtЬУЁ qZнОqуЂ0FРїДЙPЅZ
щїЬД>оиAfr 4ъ ЪР9 6)иИњjd
epp#ђ,n:\Юб.ЌІА= эt№{?O -oMкHJа=3 ./bЙ``} ;Фщ6Yп$єl
џ^~TП &*oеGtЋ-ЃжDIzВ'CОФqжxY$Ezkд Iї$Ы5пM Щ"@SЌкЈ_XIЩdЎ[щ/1%Б+nnЯNуУ42%рqU9):mі"pюЇW3аЉ:ИЈZЯ,Ѓ
s Я\Hн N-+и,ьз <
gЗБЉ№ОbФVDац
ФVЏ.љJ &' ЮЉЎЁBІk_( yБ]е.y=ѕ,
юC`кј)Ют_toс)и KњБ!иvr ^tR;H Ao<§hzлЕz.Y,Ш/YВ4S_tшK!И лЂЊОТђеДЫ Ё*БХ3В(^xј^ѓЮН*z@фuf-Юцl'5иvAММЭЗ^ ЇZ ЙОКЮ№Б\ЩДЂкGoмКRпЉА3}Y8ШЎШ'eЉчBqЗ-BЈЕ\(}НО5 <Ю1*0FЏСљ_њtзРх9w iћyџZ .HФеАф0ѓЭa/цЫhg;M[Њ?O XX
іаАПhNќиЅuюSG§S,$ЈCЩЂND;FЫ(щp ы[Nm№s Б4} Ц
0>вЉ+sИу/цDOАUnЬ cl|v7Xi/жс\?^ВеWэf+нaц
Ф@f@\БФ1;
>y=г" ўВ№хjtc Хu&j9s]Ф}љZЌOPлaIGЙѓIт*:вц\)zpЕРхQМ6,:QТ8сКFгKќІt.G}2lhє*Cџб)ЛЋЋ>Фe@ь3m6жЋVЃіd =ЧѕР;^БЛiшяЇєнЋzUYTs< fAл?уД{ZqчrfANlHt!ЊЅ>_mMхЫLнL8ЎА/Г0ќqГоЬ#}щ М-rЮA\_CСЕ+З'sёіЖ4чQv!jj лtF ЎnІЃ <й2gмжЩЭ4№ +YtЃjMck1Й+: z§h л #qЭрbшe#]+`
>џЂМН@Z} щ@5ЅеB]ќXuўoі0дд~№ЅgAБ5R]Шyэ6Евgјј t§yізаeН\ЁQЄџсСwSўИBѕ=qЎiя§ећ mаzѓоР
№СЌС-/Ѓ"oч=ЂeЉ jгзS{вНюjНьЪ QyжЯЏпVРw&?vxї4ц|qn{[ЧAП-ЬпнЮьwК)І!/(-0\l иЏ7ШUачнЯwгЋГЯНЂn[ лкfиoЉјеБЗ`ј9,N- ј7Эж>ЉkьП"ж§l0yўSуEЛS)[ў TуoPыoчџЗNЦ\ІB vњЭБRг ;лZ5 ЅЖzрѓлОГЭј Ca+гf9эop5;Зеъ %\GњЧ}CRLУNдilї[ФnзџГxЖќУл?ЬЉьђмђї9Zеп_;;љ<Ћ"ЪП'нћЫъuT§[Л:qџкўqІѕЈoі<@з Дnе0ј}Єљ#БЪRBб$Уc5| LДѓД№iПжgп"МЩРTџЄ'wйHЉЧт6_0Айv 2z }{Ђm@ожа~сflєЌ.ROgl:к9ЈЯЎQуWСџџNј/Ќis
endstream
endobj
288 0 obj
<<
/Length 3763
/Filter /FlateDecode
>>
stream
xкkуЖё{~Х~ЖШ*ЂHR|Шєі
єіЄMrmйN IОНэЏяМЈWО[,А&фp8/Ю ЅnјS7ErуД пl_%эі7мјчЯ_)wяf3_нѕэOжоЈ$.BнмяцЈюЗ7џо7еапоiЃ лц6uбЧл4ЪЎЏ {ЇЭГШоўчўЏ_НО 7ВiњBpцIЪr+mЄџтn0)OвqЂ#MHo6чPОЋлsїG_эr+;Ј$]
ѕ_поЅ6ОСF=Р ;!Ї ая;ьзШHѓ8гёэIUtЈzоuдД@ ўмХАњVб
(AљѕчzРoюRЃт\ях CЩќ:ЁhыЯРпejЇХ_Т_`XОiЇК JЦPW§№
Дн|ЙњgKЗ%nлv УС<шЛ@__nc:2 8NLљї,ЭuYЄ&Ю] |jЯЭіВ`$\EЛШ&Д; }пЗ]tУМ/eо8 Ђ
q
x*:ЂЬ@,еЉ~тйyтC8 Ќм #
ЬvИ$gнB4HмGb/89ЉhсD[47XашmbЮRїMX+іЉ vЋщbЇ ј=БЩлvЗ%ЙЖQцbЃFћЕ],(ЩqЁЌёзз]щЗOВџ@\GЯШї раОsћЎќXљ]%@PўФOUрrўмќRmЩAФpFЇUJєр"``Р&q2 4ћe&мЄкйз}ЫЯАЉe%HPrNЄек3zЬЅЭзi.ВXqWЋэUКSЇ/шF%М=ХцЄёuћПU~ЄаЬg:&oуBKџѕDџЊ е ИГё'П6й?1$xPhn+`.;юэКіШ-wE@Н'xрьЈ_Cй|7єш6Uѕч
B<йїуњRо O|[uЏщ$Щђ{_зmѓ ИNЕ3ЌїnєФxПaяРv8pї ђфЈz^їX
Б+Ђ(тЩк КUcWБШЬ{khСЇMЮќм_Хj.А::оЇ5йf6њэ67 Е зфИAЎЕ№] xуЁj@ЩїуыZnгLЧЙНP-\нБjJД6>оZb}.еbќмдmЄЃ" 5Ы]єуЙыЪfѓФc(/ќН\Уђ LеЋЕ?вЙўМPFYeНЏЮЧ]чЭпГ|сU%Xїщ|ъшГЏЋWѓbБWЅѓ8Эм2`{5Yє [QеьЮЫ@ЅMРэФ2СхbU4fCШA'ўб"2tљхrуЉdпpу ЋђA 0с=qрЈШ
мFЛv1бс Ћ
јoч;ПъsЛe`sK6Є чыўBLзxљёHъЬтjфхc=O $ЪАн6аBnЕмф [Лк-
ф FQА#рЃмНЄЋ\1.9 Оќщѓ)дEЬ{Т.ФЖћ ћўrТ*рШ.ЄУЫО Ѓ"ЖЦ^^_:qq&p#dFч|c dtQЪРЧCCь7г}Л&є)
І;p RЌjџPуХb2єэ^Вё@cf<:v)Є6-Ў
|s§ъьЌ@I$Н/\6Н.ацH
м~,џлEGЏM"Сp qYСИMЌаsЄбk4ыf_]*кЩYњЁ=zМТАћўџBc5ВзkB
Ќm3с0лcЂCLXї8ЕjјcМЎjЯ=BРь(`O
JЭkWюБ
^ІОтШЇx!-жzcф2;]lбІ ВУr*гРЏ0 .єДУz§EЋиNIpр§Лq И,РODї;ТGuю-)WЖ
=Зx)$БКЈШUD'V.=Xs"=
ц!М4HЯkЄjа ,2пІ9F+gOaя MЮ#
qДќ;жаЏзtO*3лCd }ш
kLУb/џXums.QЅ%pO лЊД-qJьпП}sџюзoўлwYКsq>VщxИ}%ЌWзт№,ЮГ1нXWЈчE=%AзАІ)ЄЫЃ
Ўъ%жчГЃшР[mц/M}ХqЭњГSq
Arћ7лIыvЗЋv^z
ї5UЦсb/lЏ@6МѓшD$KХA0YЉЙ'\OX )Ч >Pј 1lJNPY/ЖХHхДсx §ўbбђbu5№kЖGео^іћКк Ui@Rя-H )Ёѕ](ЉљU
пic_ faмёФуЏ+/§ }уЗмQб[i`СПJ_wdЩ.
ѓzТЕyє аБm1MСѓ)я0)щiсШ pY ИљУЎЋ6л~лЦ#:"ЖЂ[neкy#F?ВОG2lFЁa BХ2#
щЭн<УIcx Шэ;Jа?U гS$1|ђѕю]ЯЮвk XФ,dF'#|Ng№ЭG $ЦХЖLФьеРџyЋr йОc]№{№SќvKLa* ј-;PПidП0|
m%И1)оїD{@IЏТЗfќ]m§хїTzxыёkyY8ЖmТ%JевyЪ§NЇуч?ZMуќeЯYёќй0ЃшI3МggЋ'B№<@РО<Ч#lHРwјќ7ОХтМ Ш& *Hp.[цу'|bіЋЈtЯКlЊBћмѓл%LЂа_5$JюЬTРдѕзШЬЦfтЬ 3"DзО?$\6 уPwЫеW?mbщ-fяlЙуќС!ЫУн7?t *БQ_ 9{|sБЛ|лyАоTueMяеЉчo%РQљоazЗРсN`G/ZCТ0Ф т},MХгжпЬk7}T$Wї
LOдзђ{І$ЫЯla№ыQЛсbТ=г Ыў iЕ%
endstream
endobj
291 0 obj
<<
/Length 2120
/Filter /FlateDecode
>>
stream
xкЅYKуИОЯЏ№mхС-J$%-CВи=lщ9,В"лВ-,9ztќј|ХЂ^ ЙЧР "KЅbёЋЗ[Ў|ќЩUтЏЂ0WЛѓ;пRыуџќл;щј6`мL8џђќющЏZЏЄ/?ЋчУTдѓ~ѕ/яSЗЭzЁїSUЎШ{YБеMэ&:6Yџћљяя~~ вA№ FФљmLЌ Ћ$qЌNМџаЁр5S^хЭЪПд9aG Є(dЂ8ђЁ8
Л
L,TЄGѓYя!:RБцEу ЮmuOКD
7вџ№ЕПЬ] `ёL!ђЛ џЄЌЃpЃЄAДFs#,Њiцx[]б . Хоѓ:,а ы#Та.иXX т9Е4ЖжвSОІMлЎuRвGO2-ЫС[ѓњЎ]?\EоЛQЄn"дъUГ#+Љ
МI`ј + > Si aРчR§Я_vйЅхђsАОХ>ЧUЪ]цЪR{J GіЅЭlL
d юKSlьЪ}энuЊ?.КN,тЙ ~Џ:xw НSњ§ШKщћМDнonої^ {ЯpњЛхUZФ2їоЩEѕјzIцѓјТтDIЌнXщ;>їEиPeа>§Ъд!bІюK4юЫЎoЂ
%Хz- ѓбWФ0sЗГ]
Ђнr)$l=&ь_ ЈЗ.ТB4}
ќђлЦѕЙG&pь7tg= ЄМaJ-Э.wО
{Ћ7_
яѓ^hVћO_УIеДє ЮKЗ *Р
mіeM)пШ^#[9RнќPhHyЛPоrыKoк єЏ'ё]@Ш9ВaвЩі*Ўт `ч_LПкцЋc!ЏЖГБЬLЗььещs,{LHЩ1/ля iьaHЉІXH_ЭajrwZsїЉ]}ТbЙSлХjЎЧЁZ.мЖ!fэЙvAЇѕа}бz
Ж$<чs
ё њomС m!ІЪэ'.KГАЊsUKЙШOыѓbыM№ю $tjШH7@Bі 5& g T&Оpв
Э(vV&p0Ю g: BРћъBaEвЖЊВo"dрХпmяCn'g@,В>6x{ЎЌѓGuОљ
Т*VН=оmщГыРJЛm^цц,Љ6 ) ~aKе6 ныIA]Ax+А+к|ГTHX1Ш оYF№МщЗБ3Q5 R№3Чюїy;26нђXюPZяь |lййКwk5х(zg] іuе]p{xЋQfФы
K бшF?уэКІЮiэТЕЙ2ЌьEУL(Сf_ІјБ%wАДзТW-жH9$f-;Ёљј;CѕйЂЛwЇБЁb5;Є0bЏсЦЕqЈММЌGиDxvVВ @~XКDЂE>V]І#щхт<Ћ#љ@uvхгvЈ6maдян}ЮsЪэoф`4дхm ў:Иfb4нzКE*ДєМцюьЁ<ЧwЇ ЗЋрі`PlјvчЌЦБиG3T}Т"Ч`ѕбЫЕШ7bРъ U<ЌјLЖ!3 H(> урєД0s вЬќйЙ њѓI34FULП2eLPvЧ(г2хE6lщMщhђыМљЬЛЛјh|U2Lя C~ЇQОћтK8ЏВ/)0rфцdЧЂWЇП ћіфхYdвЯЙљ)!гmОГEоюпOЩmюГKе?N^тЬн|bИ?0 мb{јznГССlycj"|# nН
јаёSpь'ииєa9 #"mмpз)d52НЩю9Et6Ёћ
ТћaуЮTЁ1zhЗ.YН8UDBЦCBќaб-0Ц'"ЭЗ]У§6л№ьпШэЃ3уљЉљЦШqаGhB?пr у#qФРё;=ы.ur\иc.ЃЭь
N
жѕя0ђљАХ№љШЯЇё§чуг9CўБLТZdщБЫ BхЧ о7Хдi aџџ
о/
endstream
endobj
294 0 obj
<<
/Length 3205
/Filter /FlateDecode
>>
stream
xкZыoмИџПТп*Б,HхОѕzWєжХсаЋQEЋнUЃієc |чЅзЎФE,9ЄШсpц7Zн№Oн$СекOЛЩNoЂ6nќ§ЯoЬЛїГ||ѓ№cнЈРODн<ючK=юnўх§Г*Кіі^kэ}_WЗЁѕ>оЮЫЖюНV={ћяЧоќ№8n
с7r3ПЮRьЏДa~юЫЎ8EvФC єmQ АiНкsхUке
Iш^ЙШOТDЅќЬЈe?=йq'џитUљЗїБKМЧ#
NщвVщ_ДХщ\цмFqг* O6ndМпћК+rвћ)ЯEwUr1
ДЅђц4ьT 9Пw9Юьая`bЌп
ќюEЎс'6Уќ1оЉ.ЙџзЕћ3 Z=^ Ц
Z oш
|сЛ-ЕА3ЕРЕXуЗ
_л№ЋКvЙh}fѕiPD-г)eЮn8OЄ5й3иGhэФ^кШДШxДШ{(?IєЊaFС`&aУЪТ0#ч{ІП БюЙsТе SXqpЁuЋL@Iє
ё# DfmлЖуоЁЉћГ0Oі4QRlЂ Ц`в-LјаsхъAІl6ЧМЭ ZTgcжОмК:џDСЈвwЂй@Tkrc?HfЪЭїhр
by4оXCALЂ[Н~BcEЋ .ЦP ш#NЄ/мЉъ?NЫg$Ї/-г
yfКcѕcЙЅМю[0OGоЗ4A.б,%JИ№тZБI|ФlNтЛл]њВ
o"3GzАO /џН/ФXфy,!оИeg}z|ZмђР
џlА?жёKdЦP@лЇМBдoyІвzA
'B2CRЙуn!ЎЕњx
№гrqєПЙЬъdэфТС [5Ю9фВ}Ъ3бФгR хщ}Ч}
\ьWуBЏЪѓ P`
v#Hвцxж[ѕѕtгq j_жnюО]
ЙЭLшЛјuюзZxZ>9EO0еефqЋYcћбE$Бя ечІ4w~ љqи7еN2ц"Јcїов-[CpШъ1B 6 /_і
ћю{Ж 0rОS`WТwкw
Q;kЗЪКCЗ :ёc&јW_ФПWXчЬ: єЙ)КЉыZ 1Т+М9m*%ЩiЎ>јЩОbKдЯdаJgы
>кj? чpхЃзЎ38f)=хЁ+\щТІaсЁIбч80ЮўЬ^Лn(
R
ШEЉ vъ3чкЄЮDЄ;юOyS0 iњ0ѕH/`KьVм(Њ fЄт` rmtєO ЅPѓљ4n!cЗ&W§щ§mЄ0л^ѕ#кзfDЫpiЁ!љIЧgAЪћДсbбКvБ bџќuA8{+9wЭ#Руя()ьp\$(1Й'МЦ )гXџЎП
ЇЅHУ%B
p#YТЯzvуўќJMeь§Jдs"7ЯQвт#ЄПиX )$zЬЇ4zvр Юw1ЎЌю/TЩЃ5`Х7ю"NФЫЭ§џі ( ,G>ЏjсК№ТфСЖЗlнC БЫoо4dJZрЗ!ЦE {Z"РпшёПч[Вqqpxф рЗ"TЂХо6еиiХeVA(РЯИfMNq$U)ЅQЅОХwтЊr{ЄњGJERрЁ,
Г#KИ&q%Cљ#A?Z oщd|fTВьЄ7LЭEЋФџт~KџKёвЩяЈ-џљj
ВггъОш`fAжw_pПhxJ6o ]Ч)rпSнШDЎ'"
І2iW
Ќо8\зЫ0№2ЏвЫ,ЄзPBcЃp_0'јJKmЮ(Жu
R7ЅwЋ&в2ЕЁ и! ј(Yf_+E YDЇўЊ *YЂЩЏxФ(Р2?цяИ9шРe*0Ю}NЋNц R0ЩсеDѓ,ОЙуi AeУ Z)ю>№4mA!зtkтд]ђџ}]ebЃd uЊHатtЅЁr+vЅЈэЉJЃmW2cЇb)vА22ЃхЦ gc02
5ИЎФfЫВсЂ#уц
Флѓсjf|HйgЋЕъяь7
{И1OY2]CКШъ
сwrсщќ6`\ЖњмјєCЁ нDєџrЬe4х х;ЌXTYйяђv1VєDЈTЌj7ЬЊJTіa3$ы6иЊ%g5х}С
C>!ЄP }У:>*№§Ѓ%gy
№]Ћ0ыХ;@р CQ]Ћы&EЦ#WУ<ЮРћЫG'NC:MСЎ!ЏмМoъгГп+cїEЕю [эЇPЮJю;kw_]ЄР8uAAЛЮЈЌV 1ЮТЪuЇcCА}<'т[фIJd0Н#YVp #ъќ)4ш< \xm"яаqќHлjйЖ7kКdTШ"oЙCСDљ"_^Ў0мпGнwгsвуЧ ЗyVѓ+X мoU§vQъWK][EwјБVn№nVцЫмЊE'zНH'иvn,SEоњjОyxJ{)wЋТ>шh]ЎМСИ,Фг$ЗЦав2pG[љ6ЈЬ
}1нVзщЖЂБ5^Y
~=AтPеЋРЉО0ёЬHхвzЛ>ыф[LIюыjёЅ%ЉfYнь PЦ:ёЂЅ2XИЈ%УЄ,>ШУеЖ2cВУзЎ`5шBя]р"
с[ СІ фў ЙlўЄЭЦгнEжDElreаx+туЖQZћnМчфAы)vЌѕRЅGТЦЋљыЫ`9E/ JyдйЇEЩ9рјДqѕPЃЖДизaђЂdбЕMШщљВ№aCњkV^wЯF3<тРT3цдП0iЖ Рзя==5"QjѓЕЌЮY=ЬT^н
дКcбьш]Cn3оzюq? ?ы'ЌmЌiUА|2Ѓиыш[kkыGЏЫ=н #щ8 н| OЃќБCђGЬп
%і1mЅl7 rR[ПАрG[yЧP~bX8>л. јО+uT
Ц}лЇхЛџ?йјGђ№I?
п{lЅЪї 1@, Fq№ЭЩФ/ XGХ:5=<ђ>Х %.РЧ1rкјh%LР
ђД ої%гЇъ:SњjНю\<СvИDOVmЙb8џ<љфЂгНХћAо0аІ
FјG '!ГцL А ,н1№ТЇВn)Ъхc$":kЏ+tCё+цђЪB =Ю6Е>
stream
xкЕYYлШ~їЏалRёюч:/оdx ГГй ТЁ(0EЪ<< Р?>u"51@ьГКЎЎњЊЅW
~zЊUlЩ*?ОQ4кюWмјЧппhYЗ
йЪnпМћ[ЎДђSъеэnNъvЛњї[]інzcѕўвдk{_ж&ёЖ+ЁЛБ:L"/Yџћі7?пN
ЦМ#\љЅhЮжЌЂ$№Е
Ћпa
[Cя})~фІЙkГmеШЫ*}em} ђ;и,f4O§ќѕддEн3ЁКЦЖ<5ЪY]Л/Е1ШйјKуI}мRTьѕїY'TЩВу/dUтmзкУжэеаьАње юumЮdЏЇ5 я!пhЁ|ФіаIяШ?mжхЌаЂэХЮЕБі#ЩHШKoS3ЎxчЂњA+>Лi(Ч"rVoЯ*%к$ѕ$\XwВЌMзьјЫњ( ZGЙоYEаЩј#EЅ<АГOD RљQ +єу0ЩЈРыЄЊНџШ
Я $Ц ћЌЊњЮ|ГNтБoтIѓ?0ЏФxг~ъј{pЅЁцРШјaDВМ-Ў ~ЂууvYYu>'P@Ыъхћ Дvљ-]YяЙI&УFWeнЈP9йжЁ"WИpЛKх3П@J3бц$ ѕM{>Ї№ї>Ш*ЗІnћ
epygЖЫ+,` РoVЁ7P+ЯSнWХ{еЬыЕAKЕВVєx(: &
=уF]лbЫmtty6t2KЦЦЉ-rXXчвЧЫп+Љ|NП{YуLЌцхў ЮHБЎХЁ Ј-,e§РЭ(cОУъ>дxПbE9 D-ФrkЧ х=WЬ
,эg5sИ^[BЛBЋ MбЉуўCй Аeх>Фr p
кЗEжcьС Ђ#Nгєл ЃЮьЊzфЉЖи9 Ц 7
9ќIІ'пRPzШp9ЇygРиdвЫxЗаe
q^vЉ1% Ъ
ШяХ0O АёЇnъЭ2)УpЖZk:}Ги"кEЁ%п8Н:ta^ЖОеўйїГО/ЇОуЦѓІ§Сuk{ЙМ6ѕЕО dРдлyyФ ЇеR&_йrNтиЃ
I&ШЭ\DФFџFх]yh_Й!щ`ЛЎ8чМррcб9 =ghЪЋлВ;UфЛh=
|Ћь
жkГEлbиЗ6№рJй ЄЫ3@<јмѕwк76p\Ї т"Ц з!ц{ ;{ХЖХчЁkўJ4њvAv<,LЯШzYуР P
у3оАnхPЃМ 1В.x NRC$ТЁа\ob(gшРo(.фUЬQ
ќяЄ"шо")?zшa,^тюЖсы(че}оУ^pЭ
4pk&З }Ъ g
Gм ЁёзђЅmбbЪ9М№§экUAхB 2Rз§ОNЌlСcyфх
цXєрHмЄ 9ГЉЮ0 №mЗМыЫьUУИ
јёэФЊЄC ЄЈDBёЂк:є]Й-x)x§ѕЃЯ%чШ,пy 1ЎТ*тЁD,I% r LЁь+"eSЬ:ЉUјgU>T +Йj#!ЁѕrPqѕ}ЫWуwIiШJ% Э?
Гkк#bФйrxXTpћчюпБjy ApU|эh;иIпОя!Б э}Ш@Р s.БуХИpряс ыЧг6пЫЯ16AЂѕ]l Ј8}9шiЖуц[Аќ=ѕаЫ9+ЛКьИэ\^;ѕе§OKЖиѓ'^Dк8rа;пPP`GZЧ*bMh(пЙ.Ћ6cЂ[JУВv ъ#?О$^'.ЕЬ ЫјB§ЂНюћa!TYKйЊћнkЭД^a`6QСsvБIa`y=0DФgўxKD+NОв1ѓS87Ц %1 ыЫ-U8Цб 6 ї=]SН!i-5
аkx Ђ3'2Ї$dу+=гйXfёФЉ-:ЫОю?$ЧnИЫаЬ>ж$ІU%й|zЩ53,Hglџl7К>HRCашNM9ТБxьЖ-vqЃc?Вы r9%ъјXUХ~} ЁЦ|ѕfїG<љкwЩС|hВ
Ш0@/ ПCUcУ mE§ЎФ(њ_Ѕ,п7Џ%Z\еђЙЄdцVЯ-zV Ц4z-'!ЪР:@mхэ№0јхTGРёХ{ЬчA` }r>rЭnС4ЙДРAУ §Nљp|єњO[o/їЅ^qkSО
UzzЋП~ysси\sЊћ~xМ7'#РЈСрnЖтчігd FD"yВ хјAЂъЫS
e<хf)"pњ@r&0Л'SawюГиgkуq%юїБиљE ќмiє Lћ'ЂiЯљTpЦCГgйѓ[щГс0Х№љ;Џ@ЬЕ+qYхЪКђvfЉ9эпЬѓўиХЅЛЙ8Ђ+) ДшчA;8mЛ(БёЂџ21ЅЛ
endstream
endobj
301 0 obj
<<
/Length 1974
/Filter /FlateDecode
>>
stream
xкYYsл6~ЯЏаCfBеB\<ќжЄM'}шCы>tкfJSЬ"U >fњуЛРМ9vЧёLрюbo?PtТ ]Ѕс*цЄ"YхWЁyкьW8јљWдЎлРТЭdхћЋWя>JЙЂ!IУЎЎvSQWлеяСЏUбЕы
ч<јPWkЗkЊi Инp*(Hз^§јъћЋAdьщЇ&ES(MHВA(hеouПWepнЊK В њ/Уaо [mHWiМкPNЈФw?Э|тмЇВTћЌD)mРAнрu[ьvЊQUЎьѓ ^ЋКкфuЕЋCv]кЩо8T-=Мaz;иST{u/БмzlTЎeq фu_nq*+лGзpЅnEгЈМ+ pюЎ)КNUізќeЭyq ћgcТ Ё Ся (ЦлyqЙ("мoШz#X|кЁВ#:<њFcЗц5"ІBj%йр(>І_JBС№7N^MбьД[ЕЄіхf(Т&sQщ4юTяд'3Ї/х l0ѓа]q,|-iu:V>'ЅDpъобЁгZE"(kJЛlГ5{XDЄ Џq!сqьЩFNЯheАQа
7@$fЩ #+ЋЖх!Љ{csNfМыоdMC [FрщъjкуЋ%kьЂТ+Љ+
Љ`чЫтЫЫыМ xL |Р!въ"ёY-ТiLЉ№ \8e*лкaWлШDbXYeГс -Л.і}бщбMi7mЏSбї С? ]>јЖck№сo[<mI3`LПІ п#i ћуCЌеb=)ЬVєzCCVxл[м`В){ѕжО1`НPT9fфЦ(Ы)
rнgЭжРLЊЋњЇ/nз2lЖ9ЯЛЏ~WУўS6У]эюv§.'RЬ
ЦtVcDІ356=ДЊ їЅFЙФФ4 }у!}7!сБ,ЌKЄ [ыђ`вЙЫЏ\№wКdцЊjџ$RFI.]Nќ<:С№y№4яcж,+еaPМНЦlд{Нwofж"сЌ3й.БГ;d~~ZрйннМЕPцЊ}kЩXл[@G*Ќлч~ЗЋЫВжя .Н`8pnњШ /кd}хѓ[:N:bwUgіbж
yzдјЦъ$!OЪg2эwИDsЃP$T$6§Ќ4 t<|d;Џё"ёb
=@ ѓщђm WfEЗ*П9нбlC№$бџвGwЦЬ{6ш~kвЙxУ 5 G.;ЁюГУБt7
КrЕC№n!a c@@ПPь+\kВpКЌЗЇ_цЕЉс[] Ущ9|lЎЖ
%u7лЪч]иMeЫрНMт 0oзоєMТщч,ШrFдИew
ЃGЎjЏ5Ё>вяЂdкD_K*J|ємАo#ЗЊ'ЏБ zY\g Њ5њ0|НдLц'ОЩSIв(]єM}ѓ}_нЦ$єШыTЬ\єв+Qі IfМНwЇБ
ќ?HCЧ^ Щелц%ђjП3RNb>№ВЖ№@i 93=оЂП@FтбeyнЧ.o C]VНМСОВzBB>C\НбэГ3йО и
D^ЩшIU4ѓВЄч0
zWЪ]EZоW<Ычn{7"оhьmЌKTtкD чЗ@|+нкJріФЦRТ">џ бьAиЭъhюSФb
Z ДЫCб~8хЗ8MчЄРGx цкЯЕjп(еКУэWЯРjљВядЎ~ і^:ђ"'<,љ:Гf ћqѕmЁџЫKlПьshХЛЈёс;љdjќMР}љюмЇёEцјОzП
2p';NRжЬTxэмвВ0B
йЌoцРЃhљv!G
csцаЉ№Ў) ;яыЊ>ЎдiВTфОэц= Uп,?мO'чВ_xВ_џђ h>
stream
xкXYл6~п_сЗШEХх%Jпzb[
- WЕ6m %GG-њу;УЁlйб )X
с 9ЧG?1ЫјЬ(Х2mgэїмf=#тХo"ЌaaVТдЦ"ЮЩbхЛ вдЛІШЛРѓЗgбyѓLєznнH.ђњІЫ@oѕЦ5СМу ЃG<И"Шpа}[Tk$uДjrяb^вћВ#-:bЃЎ}:y#Yа2c щv&2?ЛЇDbМх ЯЏВы ЗЯЋ.ШѓЗ;\чјNОЃ%[f7zJч%сsm2Ё$tЩ>2ХХнЃбsМКмОDХmчVyuSн?лМЊаЕї(".ѕnв._9§ьVЄ$\HАDкYnm0рoѓcH4nу]>КЁ-\чйўяIџщмБ жЊDNc2HFЭ $ILQџIJL*Ѓчћ\д=VYЃЃY-$E_Nц6hЦЬПCr(-)9(ЊжAйZQЎ!Гq-ъє4V>ќIэV ЂК:ІьPыѕ1eч,ъ&hТSЌ_*хLђCYњ0х]Т<.М%,FDWС"XХxеЁhЅ Ы 1яiПqхђ-V"B0иЃG9х4Ѕ>v
9uyєNТloUTЛўLДuAЪp}Х[.Ѓћ=юЇНщж{p_ђэЎtџПЦHІшъЊqЋІX5@-67]ЙiюЬШЁоѓ'ЅFБT*av1чЩiоS<љсБ~|ѕ@QД *
IEroQRЅв*9
Бб,ѕЪGЧўВп
ІањPAЅВЏ"+ сaЃeјЖѕУ!/лЕjnC#ЪB?EnhГ-ё}bЗ.ЪA|зmhЮч2А$
jF@OЧдI9}0ѓЄOИжyYbк qСнJЪЋ%БnSЗ?@/}DИQуФ>L АЉрк.^UoмРнхеА.ЊіEY@Ќ ЃЅ?жj9х?%#8Ђ ѓЈъЊ,*уОIц&&ЋР4GиU4d]>YО FЈ]tм-
бpЕ'-ѓЁDyрhYєэд6JВФ&УZ;щ Њ Цjм:wаЕЧSЈ.ЉФxЮcI!9>
stream
xкЕXmoу6ў_ЁoUIQwбНО Ж(Зз,bЛйSlйNЖМzI6И?9,;ДрP)r43 yF<№Ч ЉLЧY0п\DvЖY4јзп/ИAp6ќлЭХѕЯJGјтУ9ДЧcЎHБнд_њђўR%a^9зhОsxЭfЫbН?+љ-НшѕAФ>а cЈ9
е)IЪДмМѕo4e<ЃFСШ ЂЋXЅДјЧeуэЩт|0нЗХрMqnїбЋrКкЧЙqwH4Ќ+Вo\ їЉ!:ѕвeCЙ)кЗ4^жnБјovUqхsubѓ8кМйИ*\чїХnlАЂ х ђmїЦ
Фe|ШTNb?ЫИtvКјTхЬїЯЯУЯдў2OqФ.&6U1ЭЖмЎзјФ
Дeќg]ю8/g<\^ђАn
Ящg^лЃ?cЬЏѓvџ>,RЦ2 p 9АБ ?#lХЬ§Ам`(STЮдВГщaЙЗV[M`аРI`UlgtzR3%ГУг0xXИ2BWIи4uѓЦ1Ќp1NЮО1ЇR&Rqhэ ё-§ЃІwMq_ж}KOMбпвУWЭ?zмж
кЂѓцФФ[пЯчuГ@V Ћs(
ЃЯВзCбм;?Фtы wз7ЎjД LєцB0=ЊэmїТЦаЮ\Й'ѕЦ2i§иЮ(U9љМ+ЩK8 ае%уђ№п-НNFLDЩѓNrІвЉ"б;њh ЪnM#й ЋеoжГй}бмxњЮE* ЏоQQ7КЭнjтЩ'тAr(тFLa
ѕџИА$щpfЪїg ЦtlЦКїУ:пй mќгєѓён4LШЬДe}ЎL*pЏ
бЧcг§сzNњяZя
д фG85г=`PjвЛЧЁњЏ`Pіъы70!
fd-п.
Ю "JИљ|E-ЋтЕЬнЉfЕXяшG,:xщH§LюКBxM?HЦ(тд1ўDп+
іГaТ|Z? 8ЪЁc !ёОpbgр2х\яwЖyОќ'чxсЊЄЪ| fЉ~uю
фў<с
ЦРєЧрпH-ХкУЖwMНййіюzАgЛьілчUѕxтR8nђ8aЪФeњ)|q &М<SЛDЈq$@ћЙЁЦЩTYЂбO_QЯ[CМѕСЄ:$ЙёУ>
bЌхK*ЂЧъ|c8Pф" Q л.иeз>ЬdІMJгZвШb.~)G1ј1oцџ§н\ЂlяђЙ1ЛінWCМњr13ПЎ
'§в-ГI@{4hп Jйуд тtn<Јъгь'К^ЕoQП# )!I<йPПeMhшMqТЄLLQћј)
XФідY№`E7ЦDdя|ќvёjпЁЃ2 caOвэ)p5Rу `LB'|лFрI1ъ8 eсЏv"b).т~яЪX2)Vzbы0 АCxYL; зaXEбЭас
љжЙ+*NLю ЩTom єNXpВх^ђП О"|пї>3gШ5щ0Чы КОDЉПTa%OA+ФГџ SArАfІ§Lч15cЉNmёMъы>>Ѓk)vФе№DЇh`ѓMKу-2Сrпzk.HъОSfn"Н w }SЉQгm3ljуУoWG3љfнzZК e F3OCrјIMOm}хВџnМ_ц#LыЕvьMUIљЂuІџ3]яЪ[aАд>
stream
xкЅYYoфИ~_сЗwЇiёа5yЪйyШУЦС`Щ ДZн-ZъшpЧџ>UЌЂЎQяиXАШтQEВъЋЃх]ђ. яEfвЛќќ.tдіxG_ўђNђМ LмЭf~||ї№sнЩPda&я ѓ їwџ
ўY}wПгZjъ{Яї*
Ж+ЁЛг2Lу@Њћ?ўэн GNRЏ g~_І85BjC2=
рЪрbлТЩдпЫрT2Рџ8fЋЊAIЏиUA 3ъ}љ\ю[Љ/к3O.kњіДГ
џ]кЂу3т@CпЇћ :ЬЛh=jл-0~ЙOM№ h l7n§ЗЇоI-dDg9ЧйУЌ8э gA[и=msІIЄІ=#ћЁВт~,јcЂ%НJЁI2-;уиPѕхЅ*sыєМЊ=БE/УОЉyхЕьO ѓH:ЪoЯпNPУD7сGАxмH$*ё3~ ;k-АhЉн,E%BwБyёћQJRUС з9 РЛo ZZХо=nЁfъЖ№2)XКCџE?t[аFшXЏNСoлЁ+ѕФAТ мщ(Y/яtЯЇ}иMЅ"
ucEы~mPИ}.>P3}И_ЕЄOѕt~Р,~б§ F!Zвo№Pж_Ђ 9_mн3чKWКЉЎP& g&FHы,ЮЖЖ| 9ЁЪ0г{п%FФnїй=|Em 5$\ы1*Ајь8FсMM9 mё\6ЏЭЧяWzDњЉЮЪ6
J(ыFBРHГlї;tТыСђщ'Zќ
MC'§nЅЏапV,арЉgJNEВЕБ
>кќ^ЫрыџлvHDрлЮxлЇВ*{ yљ@гВxЮ@)pFQВЕЅ 72`тДЛТDVюnm:C-Pр(HЮ І2aаДхБЌСn(O4L§юCЭ ѕ
дIЁЂёd|фБFФэЗ в-}NhEGьиГЩы
#ЄЧњщn\Э6ЊtF&ДЎВнIfR+}<Юэиъs(5и!vЕwЄЉёЎоРі ш
D8д PЧрz*s<оьeЉЗщUN/;O'Brёпо`Ѕпџїlцn= @ю PІ : 5О ь:дТйТцR1~\O
ЃЫЉЌПRг9#ј>ТуXйђіЖЪ1Єрй*л7-]8(df уd YзлZ
yБЂХDBЗВщhГHО!N@ЗD{u^
фм]О=*РЃ4ZЉя+ЙJ~џв6ЧжiчuЁ0NK~!ъО8Xx щЧлАgnЙЇнТ* и,}тhЪН23ХЉX:рг4ћаИ@7 Ў иFWll.MMbCиhЄ ~Ц`ЕiiрЩ:%џъС#ЎЯч№#/[џBcФЅї0іLfу]Hш0zЭЛФј4іщzWа9юКл5еощчzњъqjsAvqЕBнvgЖФD
)Элb\љф
і>HZр; м&ЉР{ щхХ{EYf5Лf5д+Yќ&!8xtё 4(m@ -;0xиЅ3{шLрвЛTьпЉР
'ЅиН gDбт{j5Mш чTЃФDК Oў:A-к5т С1иЙщЅQ"]ЧєlE§rLиbuЂг=K:ydЩЗа
| Ёь RЏВ'Ђг ќyS`xцh G 9ЗйvёX`мm!Kчpы ЃмЛp<ЎрЂОЪБyХзГNЇx6>єд[|el#kj-^ #yХnЧ [Ж!u;7TPJОA;iГЅД|ДсЉomЮAЧFв,u УЗKRЩCЧЂІыСХSk!`qнЉоJwї*еHдOsкдв`h<њЖ/доМЖbия_Z:K<ѓБєсKsCїfReйЪцжЗЁЫNЫ6БwйшS9yA к№Hўж КM)Н77НJ шHгЩ
ЂінpCZъЅBИ0) @ЋгЯЭAZ$Ё|ЕэЉdt_ЮvАА;жXЈсплл sdo3 иlѕPHВ щ37к5№ dиOЙ)
c!ГєЭтsYтBzУ ЂmУMHZ<зШ`О_Љ;mh-6ш:'. Op
C L&!Ї
ЛWёЗД5G!бн2rаО.ЇЭ~м >qNоRўгЗ!)юхRМLБOGЛќђ cPжXЫ{њжХМ"яUb%лгzЫ4јцЖ{єд-Ы`§~К@ Рў5~ѕйрСo Ћ8йОA
ЉЃЗн ьe/|DыђcЄ z
Bo0JbMPЁлky5эCКЭСd"j+?Нv{ЎЧЌбЎ^]UЬ2яЙсOI їђcмлшс9ќЃЁ1кPeВБМRКЃ№ge@4єCяAЈћтиNэxІ,iрR-ЩЄJNў Ч йВКa\*яКьБ6Б[ў y'ЙЄgл Yo\НTЬш.~р РЃШєЪџўбПЫЕџнЁыЉG.Ss$pьКqал!їКП[SЉ1ёў SЭлеХјЂFК.УЏ7ЋdјZS&э9к~ й.щъXЫжлВ K2 0§чпOPNIWЩх К
r|9@NБSQ%2ј$!ТШ|Ѕ3Ци\oъЊЌ WIћЯW:k,p>у?*OoBьЊгЉО3лЮЎг ОЃћmІWЬ=Ях{Ёv/Ja<@oг[NДcАЖGќЬ
-
\іЉ*hЇzgу(ичйЊЯЯж
c1oїХyђCKI.ўЌљgar
endstream
endobj
318 0 obj
<<
/Length 1819
/Filter /FlateDecode
>>
stream
xкХXYoлF~їЏа[ЈТкpOykмК@є!QIЎЅЕET"] v фЧwfg)eЛIкінљvNђY џ|ХГDJЉtЖкХ~ЖКQчэOg<а-pбЃ|Н<{yЉѕЧ,3>[^їZЎgяЃ_МЉч )etQsDwsFЎЊs.$Sq9џИќљьЧхў&-Ф3YBЪ#рI1Љ<T1.ёd/ДбrЩШэn`Щ6mх hЯ+ЬнЭЅ`GеGШr
TxЦИ2{AгО IЂЋљЇ\ИїЋ10&j<оs6XЯЌЏѓ1ЎrўфVЏЇЊмб`ЮVDНк3є0'H:о.PF/d\L =э.уqФ*/Vе\;W4PiЮ83аЎ ( А їЩюnЗaјнa6_(ЎЃeGjЏъrл6н #iv5ѕ~sGББХzыж^fP$ЂByЩ91y
{ рn%ЂдY)еМИЁ
ћМйPяЯ ЖщЭЙf)7мз t Э,N;ЊчpbGЖ^гШLйвU; ДuCKmэhњК-V
HjЗ4.ЪЦт№KNјс!bЈL^ещљ%B
БРЦЧ
ZЈLL'#qС#uY^[`и
HBЗ$аDRЄ Kе ЩЕЛ'Їbd`ЈXSэЁcZ:ћЛЭIеg kU шЃnэю$З ЗЇL№А§w|<-4шн{E]|ЫБ_>0ПёЖ{[4НmXЁv%У єGВt$Т0?ТвдАЯeh'ј њяDшЉУ^вbЬb5ѕD1уЯC эYnђт/^ЉЈМІvRQTЪ8ч}ѓ) ЉXadGњiъ4
ЖАwsн# 9З>б тЭkvl Zj:5ЂбUыЉфЊS.5ЫuОВЋ{ ФP6PП3 I64 Г7zSЖл5КБз "ЉўC:Ѓї8eИJ2Љ №rвІЬHгЖMcWшe6nM3MImо0д!НsnD#Ф&pЁ, ѓІaХќ>aB1щgaћЂЗ"с]тЙ~чКЇV,яpХUс] .§RћА
C+}<ЇP}ko Md,ЪS) Hv:CъЈd|Ј$!МH Юъ[1
Ua&И4х8_UЦ
ќ:ДЭА.gРTЮе4ИЇ`Ш6.[ЫЖЉѓЕ;Ч ЦїdшњшЄС n[чmYDOЄGЊ :&23-
ЬїALЃбњ}Ив
|@ ЃY`ыхЪt+Йф@. XOyD9pднURkЁЗ гqЪцИ^hесZ РP!ЅТщ)qя5х@1 БЏў__ Мх5qы "Ц т9Mзeиt№ЁnB$,гЃ(є qxЗ'Ѓxp&3ЩФ# "hЬГЋLdЯЄ79НsZЇЕн
haЛmhйжO$8_ЬуљЭ УПАїЕЧЈRз$§>я>В_ 6G5Oo ълGє|к!Щ^N}qВ:Щње?дFЁ7ОХ*"шK <ЭmU^йЋэУ>[Іх{ЪeЄ Bы>]LY#зЦЇohOцВ)єЄЫЌOk Є;ЦЄ џЉ-B %юоюxРцg СЁс№еHђ(ог8Я+ыKC\9сНAэВфYЯіЕ
ЏЌщр5Ѕ6>=i[?r $кьЭгњыЅI; tєЦmяrЌfL)~]Yчu(`% $Њ:йlw*jб оћ"№ы<эЗгa4јIњ0GРО ЦЏpRSZnNЅкwн 4тSNaюЮћJ ћB_пb$дDњИ0|єбAлѓІћД&КOu2кцЛМёv`г
6фq5ьшЂgє cdA/щ1Д`JnQтTPbs7запЖЁlо=ЙкmиКw3Тя8 QИлуUєПЖљ3Е yq}F[ТЎЊРBўЮе59ЏО.Б№њ№ м<Егjєщъ ц`ОЏnZќbIgbоэЁBїГTk Qю, іј]XБ§ЄЮs
endstream
endobj
321 0 obj
<<
/Length 1457
/Filter /FlateDecode
>>
stream
xкXKлF ОяЏ0zЉ\DyHЉЗДH єаЂhњЕfmЁzЭцз RZ{WЛ Фсp8 CV+ ?Е*фЪ#$_m+И§nEФЏ?^)A0>ќnsѕђ4]))
YЈеццTеІ\§НkЋqXЧЦшћЎ]k}Xы<ђ§PС26JцYЄѕЎ^oцRПJ>ТdS"LiЦхP&!Lаы8ЭtєЫ:VбИї= БIєsзжUыщж*
м- |M_ЈB(ЭОэ8j<ъXeb#џб5кМqCп/Zяzт йM@Когйр#5Шї в,TVяЅ2Ої-zs$f_Е;Ђънi#зФЛzЦЗsЧ ^ MС#TJ6 p1бЎЏRЊhRЇЃурKЙщz"мuяТ
Zо+*§ЖК^ЧИWgиКкГиАяhяќЎi%ГлєЉцv pњф]ИрИЗЇШКї2^ьЈOM]ЛcуЇФ:.L mPsRїFpыKZntDЫe\=t,}< ъ
qтdФЖkЧБj!|;тгUlVшg љЖъЗxГЩ q
МпеЧзС(Lс щкmЂЗ>MЎФэй`\MЙd;2'лІX бt=Ћ*§шЊzр~УT[0ЮоVД іc=VщOь,LoVЛS?ёи ШжямШyШ№~ЮС~К §СnФэлрП'nЏјћWьД
$Ph<SБZ*J$M&ЏEpNшTІ8{ЏъбїэlG}ЗЮM ш ђ Ь*'вF[з"у$
сЎэB]Иkт,"з2Ya&T;)Ё[Ёr=CPьВB0У&ЩОE
Z#љPЁУзQ2ўО];цFЂB QzLжѓЊНwApNsBe>KП47їi$ЇЙI8ЭХЂЛr/%ыћ cъ4кЛў["БЪ4ЧbЃ
:;МuэШ'ЋvЛїЁбЌTфЪџЄЄ
ДR/НА$љ&ЕдiЪЦњt&ЬsрЏћ3јСGјех<Р шфZфжЄб!Wєi/;њЄУU.ДT
*.Cѓя7шОь2ї
zкЖs#$і~ (lVhГєЖb O: 8Iг
yеnРІЉi,!66axЗ-ЧI|н
ЩљЬ{7}зЊ7ФиѕЎЄ
ЙEЉшр\wБЅgpЩОкЂЎ=IReUїwО>і АрЙѓ7Lб84сзѓLvњњ_8o 4_бv0ШF ћз. ќїѓЛћяоО"Ю9tj 8#uЃlЌЄZmЌтIРT ЄBл-^Юm XSЃГЗзвРHрcECиЖXЎЯFцGby:TЫR)ЕB[}вВт4Э оЩЅШьjЫRVDeјbuЦx#AКчXЛ>ЬI[ ч
1jU&$ ЪSХCьЖўуHдмxј$ЙАрfТvЁY26јв6GN3f$8r@
ШUa9GhtP>иdц1жIДT >ђбЖ24РMSЏ.(Au2ёН РyqvСFЧ}рсВБ3mЮш`3и оаєж< /Я6ЯЇыц}6bэLЇrYвkЦSф*[hЪ/чЋД5кKнS?гф_њдь_мћџ'ruєg
ќCWЃяC/ёћЭh>гѕUbEЁSk/3Сл(єєwР/z1+
endstream
endobj
326 0 obj
<<
/Length 2148
/Filter /FlateDecode
>>
stream
xкЅ]мЖёнПbпЂНДHJЂЂк8- ._ 'EщvЈVквнќл;У!ЕN;#8мr4 Ю93!пФ№Ч7EМQRВ"Щ7ћѓиaЛуўљ{К ю&Пyёњ iКс1+тonSV7хцcєsczЛнI)Ѓякf+TtЛyTuжРчNђ8Я"nЛљсХї7ЃЄTgЊOых у2!nNH"2[ Эtrx ЕзєйДMmJwнЃ љТфfм4ЅйыО*щѓ
јL№ЅЋ~yro#!4-эM]zйПЦiќ мА"Z!eСdеЮ/ffiЪPт`Хiпz9ЇjipйьdВ8O7;.Oiљ 'GзшsѕэJ"g9ЌЩX§в[84:щ[XуР/wІЋz8Vh[Ьт"VcAгІй*ыtE]т#П;нєN
ЈsхЉ8НЉд
Ѓ№29_лJ@UЕPyЫХ$2іК!рhnём*њв4L !мяNюXIТмўд~ТiwЧс\9яё3guбЧУ^Tі`гжD~cэк ЬwыћІЏК5УЅ`2Och<з$YрџСы.2ЉЦeю,а ЦГXI
Є#§7ФљвіМн й-ЧЪ!ЄwMРЬїЇ\8ТІЯi8vР 6§ёЋЬсЁm3Юп9WLp1w"_QРП'рvfЎMI<,t]аUкCюь3ў~K p2ЮР` Ёmnn DЃМ
U юDЙ'c@лмВaш"zыЙєAТ|їHЩџ
v]оd{!eїWэщxkЪюO.ЉЩЂЬ?k(0e< щ$ЅБZу|vЉБ|*g$чО:_О{~И;rЬ.їѓїюixGУKl_т' Ы]в (Q &p$vч>aѕWЯy'. А4IцlVГс#І=bйбД ЬЭgМ}јНѓц!1ўП~їNcуА_gэоtћBЕвЯЖјКmщ X|14vџеE,оЅ<Џ^ <L:&7УЛ0*\Є!АШљiюBzFbBЁ |qШС.9ц^!8јzђКЯ'щAіrQ
"ўmaР"ДзлЎxМ;кю
P,ЮјьИh
wї(
Ђ;вяLэч;@кќLh"iЦsфЎЬ лH,[0{Ї\Hх§$УgWс
ш)Н{"HзBОЎO%ЫдЈнЛЇK@bf Qх5ч} nЋќNЌr^\rМЧЎ ќe9Tљ Qp№lОуя'w7WЁЦшaQmiBуN!PVvпя:X[ѓЬsчіJеkSL~М}EWгуhiД-ЄFsЎlHrжtњSэљ V8^§sНgЁ=8л@я{qЅ ziцТя+=ЛІЅђі^eu]Ё;фъ*WQ+пєЉ)цRpаtЁК'ж]
9zbх
wщДГљ,џЅeщgн6uEўZЊЬЗ№ж№ЇЧЧrPw(T[Т?wЇівУЁЗ/О: ч укѕ@Аa№К >ЬЈaCмLЌВІn_yЋ о< С шќAЎёLЭЬ{v)РB=нpџ:qшg osьяљ_)3яcнЭLф\Є+рЕЏЩYѓD$
Ь§кёЗп%ИїEFkысУН}ШBсZwX!ўЎ3Xr!ЈipЙ
чАТїрО\тAГ;Н_Э#
`Y6fXЙbHСD Р ЭУ;ОvЈ{ЏЇ+6r xеНЋСЪuIіHЌcѓЋ э/)ћѓЋ+XЙt
еh1ѓq ђTw'CщfМаpOбЧЁїФжEM {мПшtЌ18Хiыл U@Э/ч~нЁуЫY2;ЏёЌdт џѕ ^}
endstream
endobj
196 0 obj
<<
/Type /ObjStm
/N 100
/First 850
/Length 1665
/Filter /FlateDecode
>>
stream
xкХY[г:~ЯЏ№#МЄО_$ДА,Bт к]ЮУChDt*Mбr~§љЦЭВmннvЄѓdзgОљьЛ"Ц)Я$чЬ[4 AfТrД8!б&%_їAЋt2Ѓ8ЦД evhSуRck
а%=гѓe`кA^IfhRЬhIeqјЎ 3A0Љ9Г
ыjСЌЁпй8n#ДgNc #{d kIЃ7.ЦВ лЄq,ипЧwёљќVPc
Д$Ёа
ОР]a=ЭcТ ј+ _\@ Ѕ#Шє;шцF@)ЩG№`}щЩo, ЅЖЩDN "гЉуШfжш$g] Yя#t
6bРЪ$ 8й C@% g*%MEЧ{ z
# H@
У2e0T =ЂrpP zЪ 2 # `]Ф[9гмвlЧ4б
k
А
X+G" "СmmИЮXЇ-жFPР@AqLS дь"LИ Х
ђИЅЈ J)3% ЃА.Bk4p 1qi№Ю І
6бAl<иФ#tАёф)7&*)
йЃгђsUWѕИцяыЊЃіuЕэЩМ*хђqіф \АЩЫцВaSішЭъЊlЋ)ЩМ]uU>kкЋЂ{Ь>ЭюHДЧIтbQNЋЯеДшЊІ^kКыcЊe^|Yіsb7ЈЪљ4§QЭКЏНшіX2ч]E?Й§HОnІХМњwУє§ђхdЪЬfЭ.ц1,Щ
ї|OtНЈПWmS_uDѓїЂэбJ?TХЇљОА]Yбч8y{(FMYУЗZ,ЖчЧёdюyYЬцUNої!§|еЖe=§бЏЗ5ЫoОPџХѕєkQЊЮю.Ї?aФе~д]q}ыљЭјѓцъЊЈg"oоGк2Ю8mІ+B<kНчІeНьљpЌpВЪЋzVііЛШ&?%М+ОйфySwPЕФьKЯГЩyЙlVэД\ЦЌ~+gUёЌЙf 8,N#фT ЙчєZьЄЎhњsFb*ZЗЊoul?fАшж8/\Ќ>uёїыЊўM5эЌlзKђdзДc
9ЅI+TюqFk.sCЧЋЩЙд лХрВМZmбк>6ѕїВЅ=ЛІь`KЄt9e
mUNЕs9хJђЙ№aЏ)рХbN'V9л<__\/кrљ LJчрЈ rЌЛ№[EДS{mzUoОm јcMа6I7HР@)p }ЃШy{MИkgїFkЄ1"ЮфЯПўf( r[НЯ?AвЮ-Њ-Й3lhуrА_ЫЁТp}U}ВОЦоHSco>PёшxџњЂя{*ЄИЦЇ G~zйЎя иСн8'wЩсn;щўGі+nwЁЂw
@u[гЃйBo#+ol ш]Чѓ*$НТ ЮTћkнЗнзВЅюMSSqWДПЈТЄW"ыPЯzгЫ=UQ>W~ цVmЫ вEЕыgбg"eKЬ?%JЛ\`ГkыsМFшИмпС{o К8bЛяШ()rzи"ИN
ћС1JђНш
<ќ:mэLЎAЩ $Ђv[ FЪЇHйЁlf,%'НіЬ\Ѓ
л=>рцСиНlо|@=|цwD0TБћ{n;Ѓы[lЙ4vSМ>
stream
xкЕYKoфЦОяЏа-dЇЭ~№eн80Хщбц
ЩYќјд=фЃ5tюbuuu=ОЊnщўєMпdжЊТх7еёCLдўсџќл-|[`мЮ8џ|їсП&ЩUњцn?uЗЛљwєЏЖ ЭжZ§Ѕk7&>mL љ~ЈaКЕ:ЮгHЇџм§§УwwaЇФ7Њ/uJч:iЋќ&ЭвжБZ?vЇ
,MЂCљЩЫCmЩЕIxЖ Q'иcЋвЩХВЇВ Їe*.lЖ\хыLj^ћGaзЪ<ЩєBМ№|У<Бѓ"NђФ8фКДё6s*%ёЉrV §=Z3wQЕйъ-O ыіП ў&QЩгсtфyЗgТIЄІў
VѓьX7~ју"іоЬ^Ж;ў\З2 Я3:mEЛтЗчЧК*цИВ/йзжcвNўтрuе5ф) џ'ёЯkюбyЂДбнoз\ЈЬфЧ @fЁЦУЕ!P'єпЎэhdTь%,НhѕuЄнЗu{Ћџѓ<№kyБ6A4§ўlXЗ .хНЖopG0њ"A%w^6 qhУgG5ЇиР,Э(vH{Ц&мJЋк3,`йБDбЎY§oжWЦFўsх G&sFuУPпSjгђыK,PБ * xOп.bё
| НВпvВж.Ћq5t жч
_ єѕљ
QЃKиЈ8 QfЊэП9РN]Я(ЊХO +OЯU&[sT
ћзGqz?JХ§^I]БХ/oЭйюзлцўjЦЩФЕА-є?ЖiЇb_БdTY('яTѓКЭ§-Јp-.ЮJЬ,Tnt'y8Т[[ЕыЈ's1И§дV 8ОчzUЭ3A) MНzPЂФЯы ЋЌШ_V0.4№Ѓћт
m^тж,с
Xхfuжd ќ]ЋГH ;ў]ЏГ\xЮЎ)ІPZгХЋЂ3|mЦwm=Є(5LvjЦэ.w2 QЦ)w~Г:чІhВ +>u ;gгh2[U ЌУ-`IОщБ2>ПiЪл о рвiщ4і
Я2С@oЂЕхЅІфЉ\@nвќnwіp Дв#учѓїf3Н75gшаOИтЎ;ЭдКќ a x|
endstream
endobj
336 0 obj
<<
/Length 1575
/Filter /FlateDecode
>>
stream
xкЕXKoуF ОчWјVЙЯj zбC[lіаmz(К-ЊXуXez$Ђ?Оф#KМЩ б ќф х"?ЙШТEЂЕШLКиTWЁЃ6w ќђ§dО0ЎFпм\Н§.2YЩХЭv uS,ў~;]Л\ioыУR%СУRЅmкІ+-У4dВќѓцЧЋї7УNRЏT 9_ж)NкNіcзфАwуЦР љЕ)т;ц5sL#ЈФs|q
XYt;;І2ФЪ3Џ9<8J=O}ьШ9 р.Gя5ьPjЛщhFlqаЛН%Z.Їб=ЂЧіx+Ћ8 ]ЩИіc^ їKXFке(ѓШЫнЮ-ЮUЊD%дBFЌjп ћЮЗG%hxСЉ8zЩ# rХЛ9АU ТсЫTЈ$!ўпы~ !~{Аяh(PЉT1ЭЖ3&d3фмc~шXЎ<8NA4$Sі/й$B'Tso'a'idТ(%7z@ ЪџCяѕsХ lsпa6u(lAЂ~фЅЎІяСцm;/rюмVБлГџ}ОС`кATдІI >ђhљтыИ\aMШЈ БY"ьЫ%+Фы[О%AZhпжMпюYъБьvg@<ІёX'}\дѓ%nCLыHљЁxsЛ\ТІ}гZsЎИ1 OqмS
ФсI}хћltv20G A>Ї ЧєЛЂ/qё ѓ 'жлЮ64Эn;GѓuPк'Ђ 4Lm
а 00"q К:vb6P_ЮпЪЂЏ ўmЗОПsЬ&вSП('KД2јМмнaйІЉ5`Ы)ёЯs 5гдѓKњАВЏ.
х§эКўg&x?пXљ УBtf)Mњt}руўѓ. 9я29ЪO nђж^_ИGpИ.)НfЖдJЄYфйKeІn\C2оЕ(лќЎБЖВюОфэ9';w К+дВКа8ЬCёЂлhЎ ,уS1РWЦhБ;o)cgсIZ Љ љeOРѕr2ёSPБОр Рq $яRv пяNK(тБ-H їАЄ
лИЬоPBCtЄмМјvQ` |я8FО'ЄeЧтYoСжS#є(шАafјќцEеЅЦгLoНAЂёVс8ФCQygYЅm=0ЗiМqMпЖЏZVi{вQрrІЕ ;Рvтn(+;л=ЃS МX|ЁH$сіРоНX|жы:o6Д#№iэЦ *ш!УщA+}Тv7М5w>2Y&1Ц ы }хс]UЭJв2cr3S"чЪщЎYЃ5ГІА#rЂ.[xnFdDЪF0шГЊIWъUM2?Aяhјuer_c$р, %І9TK<.оpАЉ)§я]ХB
%Яіћ'"U6o{-ук>ЈEЩiЭxЗq8vYZяћЪ:R@Ѓ 4;Г
ЧаeОe jOйЛТЛ.z.јЪ
,дfэЛђшRIдАA_4ДЄЉ
u%r§kЯЕМnэЙfOЮО&ЛќTXЭ9сЪуа Ц 1}(Ka0 уфБlw4rљп*П_Prњ %ЪХ^AЛfЫ8;}Іw{&ф-6§Yъз{&aІ!тФ#ЗсSВ*яvўv)лвK)їzzњ'ПH9ЋSє!Еф/\2Ў:тcx; ыІ
}(7ХМF3ч5=VWRХA^юБ П&њЩ,WНћ}с_РГЯ^iЄјUЗt2ќR0дpb7ГД
ЯЋ9>їдљЏrЏ8GуЅПWуз6 ИЄёD'ц4щn[јзјibЩхЦs:Љ, аГtТФпўJУ
endstream
endobj
340 0 obj
<<
/Length 2178
/Filter /FlateDecode
>>
stream
xкн]oуИё}
бїbE$%Kк<{EЏw}ьЅ(нU$к&V]QJ.A~|ч%Џв5Ў}*УсЬh8/вbСXхб*U*ЬуlU пEmї+ўђЇwТгmp3ЁќўўнэIВQGЙXняІЂюЋепП6ІsыR*јmж2
з2 tы L7JDй6йњ ї~їЧћёKWЊпжiХЁP1ыє§ѓzЧqPщ]бзн
ЬR c zP!грЈ
к8П№АорVіІqx2нЁ]ЛAQЎ7"ш ЖaМѕ щккіШ@ълЉъJЄa"и*iўъiђ)MІ2(~ѕ3ЊD$ESљu^я# XТjЃ[ПшPв
N.}. #зЉЕdгЊ/;ЦСІ$Gє!дЌ:Ј ySSBв?ъЖшl{ИmжІ]E~;їЃ-ЇZп,ЬТ ЈЗс6IњлЏСэрP<ъ
ЪLШgЛnщ+#пSбt Ъ;гмзЇ gHчьBТiќ5pЮБgKБIуpK ьы'G.ШtЯ8KВpкн№ыKДўg
у,7#ѓ i`Я!3Ч$Ц x: C#Й
я]g|ш;цsіЈ;sдиЬ Б]Иdџ ж
Р щЄч#п(ah#ВДЌѓгьгъв8ЬБly8§дєКО LxЗБ'щOlЩЕQ4<ТG[]ЭліёІaѕБшA8кgiЋg\жмЖ aРXђ7xљ~YlXMX8ъТѕцЩp@`cЯlымдХC
QЉ1ынЭЄzIdЋ4№Ќ]ћќлюsDЩwт5@04Fрv+PМЪQФЂNтГьЗSMиgAxЩ}UоSxФ*пsч0ЏFS7УЅС%qэs$тэS:b$*xўP|сЫиЇeќЁpg:ЃХфГGмxіќ$т4KЪvпэxРRf§W)?йERуaaЅ ;
п8ТДОёЬђ/\=я&Є1ЌіNяњqхm<Ё/Ф(еЖ WЃdтЉЕOѕщxЇюfiоfа1pyтM'йщ&дLTСш+j^ќPіu(G}<cлдО1З/б,8 О4бO§ =Эb=тЛЯrЖ о яVЦтO і' MЦ,Рf~џЛѕ&S"јДыШЁ`2 ю$ЧЬ^tяН0ЮщШХFђhh
zьjк*" {gВрПёЩсWйЃ.гУХбl6ю`6;ЬЕ§2Шв,ЬеањиZ<0їg8ЯСЛ gIiЉy0
Y8HcAUъ Н+Ѓi т?э0EZ^GЋqЋХЊЮЖ7Ы{ЪЌнџGвd_ ћяSш'80ln7ЮWяв`Ф3УЅЁ;ХА$RjітгшВ Ѓ,xс№saђ&6§8d]9oкжTF'q |8уЪ#щіuщ№vЂrA V!ЌИЦБc "
.vььK^Џ0MЗCt(46:ЂфRџх3зt`}у34m(]ЯJРPўAOЬ*И.ќp+яy9iз5gЪm~uK
GaЉYsоЖЭД]UЫѓщ5K2хfTп№СbOАїЬћtаь%(.uюоШm"Тh<kRBГм6oгЦћ7Фам0}ДјњЯP8ё№рN'pІк\Щэ П
oРЂ}QЋkMNщщьѕЦі§v+ћoOчшИdРЦЌo1б[ЪГ@?АwХьqЧё
рРк4ўбЇ2ю=ШPИМўбu_
ќKЂZт_ HъUУm>+њwЂѕ-r-r~т)rЮќёЙћ+Ё
^tkW,;ѕн
7
кїУн?>yЋ9ь
№ы0тшБ,уЧ2Мч,|fљЩи|}ГЙОы ќszФуdб;ПО,є=кXТU'PaСцr/@њч)нB OD мПбЪФ2blNzњ`A%CPu ;ЕvпGў">cзlЊсQЩЋmQwХгІрЇРdxtCjjЖЃm|qЉЖsїЁ]7:n{>^wП: їГ
р=кСіЛ4_%КѓsЊ.mS-:ЦЦЫiZ]ѓЩЂйз8ЩѕОеуч.PS№Чs~!
endstream
endobj
345 0 obj
<<
/Length 1776
/Filter /FlateDecode
>>
stream
xкXYsф4~п_1U<р Х:|тЃтиЄЈ
ыБ\j<нjyЎ8$5кVЋћыCУ1ќјЂЌPљЂкН=Еп,hђлЏxр[уъѓлЋW?$ЩЧЌ ОИZ КЊ Ђыж nЙRFolЛYtЗyЄ{g`Й<ЮгЫ?Џ~zѕ§еўЄDЊuJuтqч~з}йaзС
JXЮГРЯi' /ЮЯОЄA$4"ощЉ4ЇДД+чdЯ]
; /дбй pЩ[з^ а]7чъUІXЂNLОЬЅwurtuk №ф=ykZMТЮ_ИЯуїfивЬNњУ РЄ8 MЛНєб
Uйu>ШШ%^Єн xwїз М$хщїЩМ3QSј?'юЎЗЛn`фi AЋ0PХNjуК2|Ај/њ+0ЯЭHБkKША8#УњOdXо е>ШнћИCЪДЕ Ю7,MG"ЬОФB(,4 о2)Hхѓс]ям0џNЏ
l
Т ЬаDЏНЙ,ћ
џ§PЈ~пjLmqAХШ[.@Б2ыЄф> wяЫ
gбэ8tу@Л<№gLС ЮxО/*ЋыЪjг2с ГфgФЅрypГХVaвјі
уT3т иЌF\Б\ь OU
.,дЏС"ЖпБzмP№ЭTњvbЂ2
рW EyvF](BЙй&БЎ
Ѕ9ьCЯz\ЃОЏи>pЏСfЊСуРИ=зг]AЌкCpсtWіх kњBзЧф&~j ЇwІВё ЛЙРыЙsєЈ:ђЇЫK]>\bРLЅьlLKЉђKЪ"SiЯдZS г6цЃwџYЇP.0щ!ЅзБСdя>BѓёЏюэфйќ<2БяU`sз,j @і>JL[5cCCfкI7уH}щ% pѕЌ3шћKўI /дaсыћ$uУRИШcHЫЄ.јgLpHгч(АД+Ч**ЃэfCэ ѓMйTрLБГСЫ$рjЋgб)X"CJjьf6.4h;ЊRawКHGыC2ц ]bРЅB<уЄзnlАйуKaзzt3џХLЧбеИбИ(&0ЈЉлUДЋУYЃгыњБUЂX!S8Uљ Њ+HіV%qLsWЖЁН_"НВ}иaO
іДКїЋў#[Ў Ђ |ОщЪ]зh$ЁA Шpеd45АТЉХ|vOgЬфlO7эљЋ sІтЬ?YdЯЦ
=RЮ_ЖG{ч_ЖЗч;]>ЪЃЅ4љ№JgcЊYrMщfпџгќуOМ§IЙбєѓѓлHБa||ЅЇпСї3З8:=ЉPФЊвшvw+xЮMЉАтg$u $х]*\ЦWN
Н3ЕУ+эКbџ,R=ЕvfгRм vІ Є4rnа;дЃ/;ГйЄтвАl(AZЏ Л8їaчjhNЧїsRє7x( эTшэzт_<ЭдCх6ћмOgТ3Х4иъ3ЪИol{7
ЎЉ љ7сЩИ l#КФгоЮ&ъ Йў
ЦЏO
ѕ[Єв№3
Поњ&љПтQЙљ#уЂ37fќ@knwысF"u= Wз7цІНIЛВo[_ ЇvлНДuЮ<йШA,а&{QЎХ%eгБЉўОзSyШџ] №8
endstream
endobj
350 0 obj
<<
/Length 1724
/Filter /FlateDecode
>>
stream
xкХX[oыD~яЏt p Л{ёЕ@!qQB zp 'Yе`ЏлS~=3;ЛКЇAЁJѕ^fgggПљ6|Ср/2ЖHЄ В0]ѕ3ЃнvAОЙрVЮA$љхътђ:ЫјbЕЋZПy?7JїK_Jщ}е6KxKzeз+шњГ4і[ўОњітыеaЇH3MBЩч6Хc8OtЇaРeHfНyѓf K#яЛvK^ч.здЙю5О/45 /ЎЂшJFдGh:т8[ѕ4
'~p'Хў&/tлQћ nЧмРО+ћ~шJъЛvя4s№hЊy§}?*ыvеjOG oХхњ6ш#uз][_а[БєrЏnДјqЌКЋ/7њVтшFуі.{ьYЦ/Usб* %3ђІйж}СЬyVэ]ДяЃ хЩTъcвЪ 2Г\к{
YТЂ8EЁSxњIФF{ c Ћ]IеЊ6аSГвКlьtKкЩW lМe<ЌьвЧнAоЩЇfИ^ Ё)з9ТЁЕL, С9CoэПЁWДu
ѕNb8[ф
MяЪjoЊМS'ъhЇЏ.ѓF5[&ИК**зWЋЯsД0Ф#K?3cкэ ]ёL2O5E5ЌЫzEлЪ:ПSвhј]зvVцќxЅЦ\ёhrњgШhL3
2;Ю§aЏ}DЉH 2ЦК_л.a?Ws8 Г B'џнЋY`HABFЯЖxЬ}жЦЁH, {!Кз§Їр{wQB2ЏiM{о-ІШv]ЙkЋђ}zoзnhtю^pцA.ыTCC§рFZЛэZЮeйMQЮЦКL/Џ[cd~ЇFbЪЉwLъ5`.wНLЅU{хћМоW%3;,+Z"уѓЈB5Q)p"x lЖЎдё5ЕЫЊ|XFАFШмэ:МіЂ ЊЕјЃEmEЭbд$њ
0ЉLM3cЖ ЖnљЧL L}b-]Еj&у-|eaR7G0 гSн4Їs4uSUх6ЏЌЂЁІЋhkЕй ьИJMлјФUх+т_іBо/8fЦОxЩ
hкЃю,OУy3dђЂЎш 6 ЬУ9М;лdАчmKJ9ЇђXeTё№l;чЊёsЬЏNjk8*"зEЄ`O<ЋцМбџBGЎ?#-n{ЮџљтнЋжОЦЬцAѓ!ЬЯЬD,!*s
і-эщl+ 6
Й?Ш,лRk*z11Є 8[S2 42кхЧrA#k - а5%V"7ФR$ФЬе+н58еЯPЙ ФeШ]5Ђp;Ф3№
CЗАqАЁ'4BЖkCZ)C иоЫмъCHЧ ТAяС)Ќqь§BЄ(ѕиЭвvЖтQ RБЦhХbMcyЅr !3qЄ№Rљ џ)"ЄDr+пяСя§YД ЉSж}AeћYH3IЙРц и',МТbї&|і4@ у#rа9пs№}zу№н6m$аDi:IГ/]?gFчЅ 1Й~Ьn ! s%0шВЫ (Њ'|Є10dЗ 5sw Zюч!d P4nрТ%МЅ №_{ЙжЈШтБ KНjЛoхРQLcЫСЬi8dШУCфоФпЋЂ8`1џЎЊдН-Ёє НЧН+їЫопч
endstream
endobj
353 0 obj
<<
/Length 3425
/Filter /FlateDecode
>>
stream
xкZ[лЦ~їЏиР\ d8rШіЉ16EѕEс(-QaIЪыэЏяЙ
9дRё&иЭgЮ9ч;YuТК+г;gLRктnszвhППуЦПўіJЩКЦСЪя ^}їCнЉ4)гRн=ьBRлЛwб/m3їБ1&zгЕїкEяuе§а@76*-ђHЋћїџxѕзiЇLыВ+ѓ<)U$Х]^иDЫl]Lgб;мћЛ r ~bг$-aZмG`vрuKвuя r*Д_ЙыЛS<ЌбЬ\ЂнДtZ8эќБЛIиSяeЭтЦbЫDg Eрб*а;И WDуЁЪ№#&ЙsЗГ oЫ$Г_ZЕл5zZ%.еы'ZP3.vЪEoыњк8LjТdwyf,/Щ@ цHЅЩR#ЁЩјяуР)_oCЧ{sЈЮpDfWѓЯЛ щXГ]$чџeЈпУXыЂsЕСgЦn .чЙm№~ѕWИП&JмLQЙ$юn<ЌЉdl
й(МоЏЉКKЭзUНШЪЉКL[ЈziЂН(jћэ*x(Ры?b[ЃRMLe ёsп№]bW!Сx_уШэnч'+vЯuЧE Эї6"VТЁЦe)(Юf[В&gЁЎ=> №ћеqА|х<зD"4АnD$rдI]X0]E` QЕ)фчІыy,cЭ`њ%ыЬdзЊ]ьХ іыUЛGнцY6 lОЯ2аІЛ Тд\цфwєDЃCХ}UфQ3 Cна\а ,uє#)ѓшд
(влC=рхІ4LЯ|рк
Е§;ѓс rЄ!^7@Јчіpшzй Ѓ ќ5ЭвJцХ'рџЎ]Щ@fXз.bчОfТЛюxь&[%щћ"}иЎCШ
iVhЇRо Ш
т Jр
*.ЭС!{чШIЭЌ2FYB`tг?Сј; .#OїѕЇKу ыaржHzvйџtIяcП
w1K2Ї[ШЬлЎ8ц)_Ѓі/ш'U[]џФ+ЫРЁAMBиДкњдЕЭ\A§'P?ќQ ЫGЭю?б}]И#ЮIX3БЯмз>Ц№ЯљІЉ}X=ЄЖУрЅ№ іщRiшЅQГ9Хiн,E4Рp|Ю;aШl\єУ="0UЉNч#Eзв_ЗѕdуИCuСLљнjДйЁuиТ+§GBДLЪСФъ~ЙMДБСПЕБ @Хе~ЛЊ9RЈф<2n*LW6siЂќ%!Зем Њ7ъRq#С ЌaопДmу<6ДЛЭ ЂШч tЗРv;j9DlяP}HњЕФє0Ќ fЦєјг*ќ-j!Џ ЈщЧ
мooYЈdСaЧKSЏ'ZькШ^ №УVI-Й
c&3ёLЙ№2`ьQрЊ\(єЇЏ;: LiмЈeєЖ;ЁКrVы2qfЙђ7ќЮq?Ё#ЏВфQuМ єouВOрВ3 LERSi'оВ)НvBїђ9Іz-Gшuђ9q лf?эжї@GVNкї§ вBжnДьЗцltа)0ЙГэјЗэd`Ќ>њbЮЎХCГ?Юq
hОЙџ #ЈЮo/ -ГГaе§лU! вt§FxB
љ ћ$!ф*ЌГм!Б7Ђ7щљrjОИпЗ7н-ЎтЬЧЇИзБdїЩ7Y?ЭбЁЛW>tЃЩJОlќьэ BГЦtЛдСЫ lо* 2K
wWоаcШ&RЅfQ§І\9# й щѓёFqшэЗР NCКKlfИђ\mЄ)№YЎФDTvйJ~'ЈЃБ-7Иh UЯ(ќ4L%Ц-SNв:ч3*ЏK]/nЈЈІkСёі ЊЁЊУf~STu`гАYЋqЙ7Ь rбм§!<Ъ~
ТAТЫ\У r/\/ дЕЖџWЦJ BЎи;ЏзAУ_<4_<]:~Ц?№Uо. ,8zi<%3тЖ8шКЃ#ak\И9vgfBC6Ё!7њSѓЅJ Ш: РКЙvEћpЊьРЩ§ќВ=ц јyd4Ъgy)GXYІ№TЋш+ЋMРаЙj : Х %ЋGmuтЪrI/,хj5ш)JађyE:ПЊHЇEBе_ЮэиеЎаt6Ь^)] ы+ЩЕ&,) z0ЄcЙјУ ЪwјXрвЕЊ.nўXjЬc)3]?е =шяNЬфN8ПСvВ§Ф
ъГAz_qЖ)№љNїMЂєN\bНї-оњ$(нЫМТu№;E+vзТм;ЧЯБьT(#*Эў0YfпRщwSЭЦ PNьtЇСлрп (YPО>$UIB
~џХ@Г9V`ZaЌlRZ№&ЈV,7+fЧCНљxCАFПEШхGЃёеrќ`9ђ Г8vюЉџЅ И/5y*8С::'X_ееXё,~u M-_u~цдLЏ+zFTVЭЂWKФ
.
i ўр =
реЪЁ!\aS
з.бЌ угBXмЪ~9 / +рg DФhТЎpОmЊ}л
cГTЖ7Nо]4\sГс2)іУw"ЈЕўmў8И-22
ёЪЯУ=Ѓї\Тg_ШсЙа ПRЭЃЭЅяk/n 8v n*КвТБrгR*ЪxMC$D]FџЙ/ poуле 2KuрБўвЎтJ/юіEЅыЬЭoM
|Ђfа U/IгЋиёшшOЛ
dБёйpХSљ ;ф хЏaЭЊЩ"c&24пјsншUн§фW,}ёбOЯЮlЊџ`X&06IГ ЛМI к<[ў/К)UАPi)[Iеќ*sџHwќ+"d&+єэЉОpВюL =і&Cјљ§
О ~ѕёЬ-2-ЗљЅ[WFG
;e$еlJдЏЂэБІLLItgL?Pп=a<ёD№6ДЁъ@>WbdнFvЫВlOФkSшTфРч\ЛЇЪdў=zvІи7Vp Їы'ymyЫ}\lwрдLy$Бѕ|ЈdЕПIышАЌЭЎЈ }lј,у+ q}Иf$[ИiЮЎЏф§BоЎўѓSоZ)фЌК~^y
сWџЇUБшђ2NНЗ5IByIJ{сTў'ШЇt=jRЏLa Х .ђт7ыЎцТvW ц
gѓ?=wdФѓ
ў
7уvі}] ГрЧL§Џю;џ 6;Р87еїщimН8ЊььжўШ}УТуКѕ;РxИ`КЊё3щ\РfsЮ^Ч!ћi;ўUёвцRWСЁѕ@ѓ,ДЦѕњnЈљ!ѓ6м@n0W,xЪћVиХf:qЫ
zz7{yЇџ?^Ч*
endstream
endobj
361 0 obj
<<
/Length 3352
/Filter /FlateDecode
>>
stream
xкЕZыл6џПТPD Ф*zр>ЕASфphq-ЖР)6эjЫЎ$'йџўцARЫXЃРa5EШrц7JЎќЩU)VЙжiiецјJPoЛ_qу_?Оn
ыхїЏО}oэJДЅ\=юЦS=nWП&П4uп=ЌЕжЩЛSѓ ђфѓ*зv5<ЎЕE(ѕ№ћуп_§№WВJнЩRОР4yВТЄRfЋrkЩжmъcuР<9?ЌЗSн =ђєэ{ГЪв2зNTdЉЭь
жВ%ЯЃhЖ@UЎж#ВЊйђ
АЊLї сОmНЇ=BvњїEўкzџФмPџiчщ"џ'Н)FњА.Lќм ЋpэТZъTZцюxъpz-юЙынБ{ OжњEДHезњ]Lзјјџs-№_лЕMu8<ѓибUMньwгDЙaЌюИOкПA#/zGь
ЯЈdNqжгєFщЄc9с wЯмSсIіЋzфћYХўЉjоЯъћyоtќфEЯaЗўЌГёYЋЂLuЃФр
д}A'ДJeІйњpрљЯmа6bЅтCвJІg"ќЄЋZмC$ЯXЋАбЙtbиX(N3ЪCею]чп >~ААЬст@ВЩуCЁ?УЖnнІЧУНba|r^ХЦЄЅФ-ЭќmВЏ?у.; ЅСпv9КИAlсd6Їmи^Xmщ HmЂп.нЇФ@ќwi^-R)Ъ№ЦЖлТ.м^Tg:Пљ%nЮяX(ШГjрh18Жьм[>дzzў АИ p"ПwѕОЉвl*оз<іфZЧжэ fЙ}j№ А
@П|N D1йЩ2 ыѓЖюЮъyQм<А $]TМLZ,еЛРWw9єБѓV КЬЂУ6ЎТ Е>wѕ!№z7ЇІы§.tмебР ўhNДщ~ТWшюjOy-Ўб!шoгЕ<СkС> tСDЎеВ ћdыMпqЧИЂVПМьZй№LNOiН>]њѓЅ_яNэБъ ДДЦNHW@Ї-t-Ы,pKNaНv_ЯЇЦ5}] ЕшўЧЧєб;-7ъежЕЈY8Т№ п8q ,Щ^Жё№TГї- Wъд!ЎXЁnS
ВV&§ЌPv OxЈџ Ј`IDoњ"K.лrЋnјdа"ЧPыы"8
*НьЂ$:ьміmu$ѕГЄ~ДH7а*Аcю )>ёжёЏЂ|МТ,6y PЂ0 ЂiKЛ!hBИ Єс/1 Qаbуx њ№a-с ^ЩТclи СЉ_ bO'ѓй\Т
EЊJyхIцsЃ@*oСXgiє0ї чЉ-е4Х
EqS,Kф#DђжNњ6\@и}Tь{'ІkЬMХАсEgаУу3\ЖщєmfqњLkД33spЌkJХн0Љ`яѕЉнњЁЭщx>Ио
'жиіt№oтЃЯЎИ x#ZoИJ7ьПt] hКбнжXN"ЁВ|y+`'
TкZуЁ&_аІнпЫоJ{0%ОѓЙ=sпTўймацЦ-ggљt0nяwL7ќэ(>к]?XmЛЕЯААу ?{а=В0а xЙT{ПM|GiЂ*дяЌЛНиm?ЬLчй+sєgxѕЁј3э8жX
3PogПшgг\Eп№ќљBc9ОжЉ<гїNJN%]ЬCH=W ^`lЅДіFЄ/qTдEїџя[ГII#) Ї8З>wG0<-gyB-( 5CuуXsрАДє.Бa.цШЫWЗ]ЯЧМнЭС]>РњУЧБ!weЩ=Нc`QЕе*E mtОлЫЦљь /вBypFTeСс aљ§=т\Лр.x*JqSl Ђ x нзEљВрs"dVїВЇ_V?!tДйяўь$
мз*HшsU9rщ!З aВQ3LЦјЪPnбс}Н"МSЕ~ЩсA%
ЗCЄЃЁQ!ZЙЧE\щЩQLЫ;Э мжэ8Ў5f№иІбмАt№ўY ЗњДXDHPЦrЈ'МСZWiН11ЎpIbCэ 7ЇЫaЫЭiь&J`L8Ф'Ўe|/Вj,Xк LЉЧЌHЕІ>:7ЏпJЄCе
жr
ќЧ
Е ўIEХмiЯИЊо_&XЊьЮ!vо=UgоE&Єфп_йЕЩЯ!ЛїTгjAЧTTшЁѕ;юyў\/Si9брZgoЉѕ Э'% фБ. LmOtєX##мїfiUju6wќЫеГ4jHќ^lЌH!№
wРЬу -[[зW`л№дmкТZД ШЌЈJ,CбЬ =
07ЯvВ2ЛэЌ3pХ_(F@^U\g=И[>Цў}ыЂPъІ
Цтј
Jўе!рІщ}АцЊЖj6ЁцЧмLdјD!К0IыўМд-!ЃАIх{ЎъСe[G%h.дОр$іщ(іVЈЋNѓммЏ
5Щ!IQ5Ќд=ГЏОR С$ v^1K AЉ&9`а еЭ\ђ1
№<ј§ФАrДМмHLѓ јоЅцJFР$ypwПЂ9*1х*иЁ1єьл -эМJЇRЭ3Ё []
iп3{_яѓЪЩД&5ЙОЇЌ ђ|Ўў8upѕ;№еRЯЯЫ5/ xйDxвШТYШћ 5уБДЗP {U
И
щЋэ мЅм|Dн`xєROёЇQЎто(bjьЌ№ E:ЈjеlkП ї~GлЦВuЫЕ%ВTлY9ewG9№ОЉюхJФg|eiтL'Кў2u§ Ўo/ХQЉPі[КlъЙиГТ3DшКјkэ3 ШД "
Jѓсв oЩЃё qЂкHўѓ КEїАW!ѓ!эхk_Кќо.g
\+ыћАpИ2K\ЭCuрB[Эї, %cJN 5 п[ <д
ж#ђ\'џ~rўQtЊБH цс 9ЕЏPСЊэ эЗGЇ&ЫІWЈФ ЯТUЩвLЧУЄАХr f&ВЅRъa{№с= Фm ч+yз№7ОЛЦфэТ\Fэ_№зПвпSыи0сЌRтП`љсы
4ц nпN
ЂДЪtPZlйTf mу/Є23$вL ъMЭзМYЩB"yќніc,ЁГћ ЬГШЃйзI`-w<їс&-УrA%ЋtЅJ3ЖbЙиЊkмёg)Џ_/fjйјЂъПЇСZ[ЌйХD @3Е гЂ+O|UCЅоO,т"вЫЂ*џђгЧя?ќcЙ$ЧSlCГ{ЃuBQ wЁИЂ)љUWИT Yјv[&aј:ЧfЯмIбX71ш &аоЈ1ЎЫQR3ГгФѓВ?cВUТ?ЉRЅJЬВ~§]ЌЖаBБЦЂ:Ў$ыЋЏўЩијKВп,euZoќЗ>jzўвGф9~щSr\ШHЛNЮА[Ч[y$с1 нчЧЊvLы%o_ѓн Ѕ8@^&лmGќ)ќ!акVлpEЈ&TiЁ"QчЮє.№Ш шјIЯ?%1сѓькjлћЊ РU4Oр-Gп
љ№3ЈVВм%гFпЄЙЖX7UГTЩ Ёщiнё ЎњkO%J|rV; Ѓ*Аf уМ)дЄH/0ІЎoй-р[=д*OMЁџ}ЕЫ`ТCИ
RЪђJххў{,lq~УЦХМЂю$ЫVl ИШЧУ§sKdЧGnЪЊX|{бњўуХ#_
endstream
endobj
367 0 obj
<<
/Length 2125
/Filter /FlateDecode
>>
stream
xкЅYнлИ
Я_сЙho"ЎHъѓњvisMч :ЭіщюfЪe[ YrD)ЩўїHМtьЮЮ,? ќ аrСмб&гZqО)o"7ля7дљз/o$г
@.(~zѓј!I62ETШЭгnЩъiЛљ-јw[і!дZяЛіAeСUokZFy(§№Чг?оќэiо)QъNђЕLщ
Li Љc)ќЗ{ќЊ%Lі"ЂiК§Ўn*"\Г 2ZШYАРЧU+Ё2хчКRJV93DўЩ ЎHaaЅСpp$ш+;6ЈY t;њZІ 3<Ш ДkiВnh^њ{$уYb%Ђ(т
Д+кЕМЙђ/aЃt5KTv~сЮYњбVЛБ!zЧэРХ]6Ё#чёZѕё|ђ ы` XЄ#иАЃіАRЮjњЊьњ-ѕQKиmЭЫЫЎхu[Єeв[Pw'нa>ІЏfy№бЪ6шў/P *Ђ њ6TIшц
&qc$УKУБЁaйзC
№d9д_р А№
ОлБФ3 hdьjёЉяіН9Ў7иVЖоѓ&'А 4ЄСЋrЋ3№
|мљ ЛRпe/рgЪъ Т;
ьёЁОвЬlл8 нbчt"[jЗЈBЗДXР $`T`OЮ ywpЄfж Ў^Ююb-ЂXЏ§ѕPЕ>P
уйЉGqО#kЁРЅЬЙlиkЛ6ЌЩЋо]ъd ЙрYшdјя"u ЋM%Bi"OM№O*ы%nNЫУѓz_lтђў`NК!ЇцЗ_Л§Оnї4zП№?оБ_зї[xЦЩьљюeqy<ЄЇё&)n8.ешZш(БќќL3Й'Nуѓ`jЙvШ!ўэ фf2Ѕ"Wвыr>^#ЫF6ЉљфW3$ЏлsЌyшхцЖбНЎi;=ЋкЮкF^ЈmlgmурЖqв№ю#КъSSЂвќJщ4хRMbQКЊe;/-tJWЧ`Ц-!већЙЖЋ]1ЭУЖjK OХћ*пн Р~QБйYѓvЎ
ЭwAA5# ењvј` Яr)џчб4пй%)ЉМ|L}{ШlПНЃЄњЩ+kкљnkљрВЙОt j~ПХdЂ8'.wY ђr)Й|ОYќфЪ|ь ГЗ:WwЫ{w нѕaoз5Mч аNfДNћиэG(Мц С~hE9 _ГЏ{ѓгєlUбД{ЉШL'лщi? 4NevSSЫ Ь фёyskм3VЮpS ,Z>т=оО:єШ* кжpз:QўIєўОeџMЋѕЃКъCъЩ*3]\њq'sgЊёK=CaгJdуFюя T\Sр',q_mЖx\<СјЙ,цg, n.! =x^%S_ЊўЙГо*i§ @їэI%2 ]kяГ?}ћ<жTТ]МЁХ7сV§i<ё[лОdBЕFъИ`ІZ:{њDя98ХП?@jруLПэЉ1ќКфX:@%[гRJ§Ј|с =чuW9КЌsХ~]кч_CЮlЋэнщqыUbл5 ІНaВ,н_kK/И}щћ1ц.1љ dv;щyюI
endstream
endobj
372 0 obj
<<
/Length 2511
/Filter /FlateDecode
>>
stream
xкЫуИё>_бШeх`Є%ъ9eЬbs
ВНC&@и6нV I цуS/ъеtO/ј@КX$ѕЎКсЇюЊјЎHгЈвхнўќ&&hџxЧПџјF ^сѓћ7пПЯВ;GU\ЉЛћуђЈћУн?_кz vaІСКvСЇ]RЖ jјІ*.ѓ бЛнџѕЭ_юЇВ$y%IљІ|CS^ъHЅi
{МЖ*T&РАяЎэWЖoЪ(lBћpВ@vRVС SКчuћШ№Буб8Д3b<дщЩь<^;8}Ќw
+wСюћВ:ь
8А
џ4ѕ0О
iUL:_В<љДЫђР4WЛzЌтg (ТNS 4ftЅ pVЗ[Єк!с#WK5Н ц@њh m CW ЃЁ*ЂlЩЯ>2Уp8uOсбьЧЎП)еKЏt\эИn кF@ќСE ђ5АћњcЌД=0B-ф0NѕOxЎ!)М ЏСПOчjиvmH`йЇ&Џy:A4 ЛођЂсAЏ;aћXЗ/=еуiЕыиУбlИМ UZИСкsАmwЎCИ H<дiќшЊєЃЙ6Ш4у eНQс "mS|ЋЊЎЉэ;`IоЁVніp`гAЪЇЉVR3эЏS,*Тa|іЉ`Ueц0 {Л0ЭђЈLє?т
ѓ4ИR_кЂhг,ЈeЭДђ2" u№Жё@аЉо:хЩ- k6aГывьЩyы~d №єЙђэyЮД8aбCЎgлжc@њgБ #Є\WСП}тQUХrЌMП;№іФR ЅyъПусЦЃKјPяmyЅzв
йяйЙЉЏЮЮjКІаJќд2ш2*ѕЦQ
нљSІСо v@NTH%ЋLXlАкv#OиВKь`DOяиЋ Чe?ѓЅБгСrИi\"Ш)Y ђїї+zK
їрўФтm*8з'К џ&+ЇќЎ2`tqб 3zНx9
|TХBШxјnяmВ"uшхѓuМ$H1зe№м
о<єЉВВtлОГ
xD:Љuw ЧЈЂrЁc83PЅDz<ЗџС| Ќ:хЦЖ"\Ђј #P <0шЉn ъсвчк+ц$"ћ9j§ПGoqж Wu2 Ъbу9Н=щoЌZЖ ўx бс:и>Єј^Ќт;,9WjAЅxЅЇ(3УeЗГCИkMA нІXD1НWУ3Е ЄVВd8сEомзРЈ* ЕсЌЅ[Ќ0Й А0
ГM*30є§d м 6k;Аљ ЅчЅZЯяfЁKEQЊVК]KkБH:В+%Уї УEП$њэЩРірnНЄе 2чgFZFЊjdeФo@Й4$іdХ`#љb ЂЧ'О$UжКqУ Љ2*~=]wqйB*йГЏ2 щЂм$ёУ$~ьы§јвъчыхZ1pz2gяХ\-btфёъ
Kб ЪdР RЖTKКDсЊчЖЧ4уi7Fщ,оя №uВc
>dPDN
ЭјR$JЊЩdH ХУN7)ЊirРхцб#A?Цџђн:дєJР>РЩ|+Їй{sХUТ>Y7uм<г3p>ѓю6ЭРШФbй#5'OH
љЇupЯ dI}*еЃ1їN6Ћ ЭЂррЛ`>#ж УщZLчЭCcз%ЈјВ}њЁПIєІ 8А |0уuџQк#ј^ЖPЭe _Л
о8кѓ
ќPчЎїШ@'Q:МСЂ4WЫЪoi]kУІnэыjх чwЦ Вx 1ДЂЃtЄыxЙ У$гJX іГЗэМњм]f В§sЧЛ8ЙьK_Oљ РхXд wѕЈсsЁbЮuцOЄТl g{дВIнymяkKUdУИд/Ь
6bС
UЙzЈдкCаЙУ8MgАячYбш,яЃJѕЦ'Ћй<юwМ}ЕВ~eT^ђъK 4ЖадiR~ш6ѕ5m>9l §k$§ўFНЫЎ
endstream
endobj
377 0 obj
<<
/Length 2607
/Filter /FlateDecode
>>
stream
xкYmoм8ўо_1w_ъ ЕbЩ,c?ЕНэЂюіpMQЛ;gЦ1Юcќв4џўHђЫФг І%Є >Tф&rE4EиЭіј"rвіnCџђBВ^сLѓЭЭыwZod$В(§|Њнцїрs]інUЧq№ЖЉЏT|ЛR6(кЎЧ05вWоќѓХЯ7уJZЉgOи$TБqBf}9Иzw%Ф%џn#{{%Aїd,ШяЫў@ЃўP еАY,fB) ЦЙ
ТАНzЭ
YI,FЕцKМТй-qjЛ6?њq.t QSW8ѓ&T*ЌЪXHMsв4рјoјЭшqдИусџп^
. є"Џw8Hт;MИЙ!фв8sЯщXЛ
б,'*љзy& ]Їarp lр@МIaeМa"X=yЃЌїЭ=Б]Г
c[5{БКѕXJЁgBg у№§yt|jyч
јW[Кє &10QYпЖGN|3;xјџdЭp~MІЉq1>FЈX>JD'Aw wаЊd ,zЪћCЂуР\Ъ,ЂйCEМ# m8Ѕпi
~зч§Р Ь'[й+'ЮлџљЗї7оНџ№ѓКяН оеЙD4љтзЏ?ЭхCЩeф бoeлдЧbnj YДђЖЬo+8к :t%Јяv%њ?Џ№Y%*P6OzЉЌћЕэФ ѓАv$ ]еш8ИЦ6яB 'RdR/7Jщ -*PХ $:cTРa|ЌIЅ{шњтиБўPзe}GњПлЖщ}OяОѕ}ЄЩДO ќ
SeR"Z$Ѓ тo_ЏбЄ"Gh\ЦТ
вЃІеY№Э #0}^aЦљЮ*RGЦтйЮЛЩp7
Љ,#UЩ$^ђwМZН#%В,}nБaЌWE`!ш,тчEbјe эЫЊИXvЭЪclSf @'Ђ$w.ё:)$э> ЊЄ\}<яsRИ Ы§ЧS&2Ш§bхtіСЎ6Э'эЪiи7CНуCpmВћ иРљaеq%Є
рцњћzи}vwEzF-8ЁоЃЯЃљXё,Qц ,'ZauтEЩтьI A+Ъц-H4ЖбZ #dіьГm'кШMС*Њ,,|weу iЗЩsvл0(Z6 %*AКЈNа
[мх№\уяW7и;еЏџќђfmsЪ
3бЄ4#B<ўо=
оДР?:^w$<ЉKЦ$нЂYўЕ;bP|Ќд\|Pюъ7їQьЉ2GgЂ-wєЅeЪ3Oр]Х ъ К
іmsЄ7Ф)x\єX:вq
BкѕZ/цЕ ЉJХѓSQ7жд ЧаР]k-4МsџIхzьЅdоlгзсьѓэЖзqnљx>Ж%R IgџїtЭЏHvЪя"тфмxe!рF.ЬП|3рЕ0ї|Rg№ЋE}NF0юЖ-g-Уhј]ЦиС qЕL
%2oX"в+Л78x
tK{ <ёыUK hчї5
ўБШсqЈk рqE`ЗЩќдшpmдx,Уш ЏU
9ьЏrn\B; qйЉuF}wйo0ћѓ~ѕhЧ@f"ѕ4}WТLаKФ
Ін6ѕь$і$$iЌ?мю\юr?sУЏJ хЊя^0ю)`SЙuьrЕ+2}њзCз^wАчк-u
pRrФХTщ@ ї{К zИrЌ Р/{Кюќ
#Ф,
w`SВ
ЭЅI!Ев?Ў$0ЅPPЫ;&Жлѓ6 ўћ
ld8^АdюЬсwоњЁYЊ*Ї№ЌT№КъЭpwXЈгK пћbвЛeЂ88эЪ§ ШIЄ8IP6
вrOВiA ђщn$љщд6Р 9"} ў-Нщ78tw
kАўeчИЃA=ОРщ{џЁs7h~mKnГ Йвѕ%5QWђжй1бАЮw*ўК*яЇЛ(ЛEЉDћВЊwKА7к<_ zІ У)Au БCkжКћ,WљЭФoа3 ]Уd"іЩWGg`u`,8(ыm5ьтФjМЁРоЄ"E 5Go)ОпD!Е.0рУу?ЙхіЦЁ{пQ6}Ѓж)O HkдИёПyзю5P:;c=ngЭёш{W яэ5)ыE|М|ЈwyЛуРLѕч]аУ$№Бј Oы4bc9ъl7ЁjG0щиє,ф2Lч=pј=ЩГХёCеr|C?]йс}ЙsЏЁ N'^
єK2Эъ1 P=ЩGР TAZ1СOGb/ Dвsky!єЃЄўJш)эС1cћKo№^ЉёУa4ђќТљъ2 >`шї;Ёu ё NuЄCмД0
[т'fКЙC*7УxРчmqЊђ-Џ^фmUzхІF$\4NVДЬ5ЉчS[M#=~v.мбгМУeЉЇєxљгRєбфЦ7Т?ХЂ!зТЉPъ/
гMъbЧ=F L1JЮnЯІАZxйЉЖtЊ!Ц =љ5ЅБЮT№
NзXЛ+г_ыцUЙE&MyяѓЎЃмg §КІ6ЅІж.Ў пЂДХТэMJв] taPвчzsfVU@МkС Б 1J\RHwc2ў
8u_њlёWдM] NБц(зЈгv5РPzdvљ ЊLиФпўмШЛE39жЄ;КWgєnќ_ъќР+Х a7їPџщё
endstream
endobj
381 0 obj
<<
/Length 3682
/Filter /FlateDecode
>>
stream
xкйлЦё]_БЎ<0цРU~В-+V*\ђЪ.э8X\ЂD jЕI*пОfpдЎ\*>`.іtїє=Ѓ."јЉ<КH s]Ќ"mo.ИёъЏЌ[СТеhхWW>Ч*
ѓ(WWл1ЈЋЭХ/СыКъЛЫ1&јКЉ/uМНдYPЖ]нQQ:ЙќэъoОЙђ;ХZ?%\yN*В0k/ЬЪXFьљіre#м!:Э;Зи)ЭGњПХf3YпrЏСоmЭгЭЊіЋzЂt ЌiЇЋћb]Ъ еѕEН)кЭє]еЋлjS"П.VщZ)ЊЩъNЧуО<5"жћЫж fкш`Sєў)Л/Л'а5в pбx@kЊzН?m.UPrПп7УKa'cы4
Jр1р
У1IЛUбўРo н5RшЈкrн7энefљaЂ4дА)3D
ml V(жњmpД|Wu$ аЎzљЪКЖ,6 вќЋФе5АЦЁTGЃ)q<nЋ§ [ИH `5g!У)І`\ХAz\і!Y9Ё
д< вГќg7зЙAЈr3ЁйЖЭME.лAcД єd;h1ШД"бСЌ FE 0Z7=7ЎAtВ@@ЫщBЋкђw8ш8&xЈ -ZкЁ+/5Ё`сМжЭс С?(иW5 #и"^з2 чСOUНaгвёRb6dгЖkjRn:БаШJЏCаЎdЌЃн,iЉAЫhbЇHѓІмWжд6Ж^ЉkХјП:еuUп,эБ2i ,2т4ј
еK[й44q[ЙУ4 ї З?('0Гo7ы
.ЋБQГp}ь
"[г84А{NриЮша*$lW*юъ 4ЁеvЬрe+hBjЗьи67mq@жВіД]ЯОPЉй№wSm:(qwф Чіy{I]ж5ГИђ0ЭМh|ћђЛoзi[ПнЮлjХ|ВQ |лдЮ;]Ђh@<' UUqM
g*xYѓTwзѕхO ЭVDfОЋжmг5[1вДЖy:НH
Гф!DEVЙU+2 АE#ћїxВДiJvяЙ Шљд=P}$ЩKљёKV Х9ЕЮYЗмуCЦ5ЃCЦ. ђPB;б6<}ѕќЧE^Фj|РЫДрЧРОџђълEЮЁКЈШ
ЩpDЏјцеїЏ^>{ўїEь ЂфСЯ@#ђaaЯL0Ц6&ЪF|{Ч#nІhЏЋО-Zі^Ї:ўN zsѓџ 1yЯ5v[ѕ;nSBіјнЯЏ_<Пњс,3%5зEP8QG2=eЧ є1vЪјВGwФ)dзX )1~xWЩIєTІЮ+yИћЌwN њMl!+`бМЂxkфѓє gFб є$жB48-ЎШfЫmgГяЙяBуд zУфёљЏнК$и№$
Љ0whhB)ћЂкѓ(ЬЮЄ-%8ЁЭsJnТцТТрPiЪrІ#уtЧ§5АђЬЗ! |Н+Ч"Ъ2П<ѕT?CGdЋр7&хy/ОяHбluаcШw |l85Уг9Бфt HЃаСS zй_ФСђ. Mc ё}KЋп&хіаЭ.: lтA+ё $МИіьЩgcыzЮмTokhћi_$ЂБlЋр[ўыTБBюЫzMёЄM з>8ХvшѕEл/(л дЁ?џ\4DqЈН7ћгЂSэMћcЕFvE[ЌAьШ$шрvRЦj-Ћ(йDћpЂппюЪжzЋ U&
cзгэnЧy7СWaР}RАЂБw+П*cя'aBlЭOЭЂ r ќY7|F}N.rХ1ыxвќRњйх ЪWrд4 єgсёVУyСS ЦЌxУ2шwK%ёhКЎBЋПкP %Гі<їLа7їв їФХ љg)]ђЁ0(ЩпxиЉп ЗНјНO
6Лwh Щ^bЌSІDп эѕ-1я%mѓ-зЫкkо}ШђlЖХaІВБ ЬmГпsєzщ< :$БЭщ 4вЧ їа, јHФџ *1a ћ:ЫgR` v БDbЃ#дрЈш5:o4є$-/Cisџ#§а dxщ,-
cЁШ$Ѓ Т;ЩattМЪ5ЇTэАO$Eџul@Ё
Х, (Ni0ФИу Rёрј}Ђp >ер*х?Оx ЈKZNкл О 5ЧЂпЭЖB0jgэOV{7хy
GU УrP)~okЊ]ЮBNэ%-лЪ мє#>Р/И:|7ЩІєkqЉ11 уц 4бHcFЬИ fЋoс аS&DйlHC*ЇМCјЫ§D>љ 4ЅУдzE\}J`ўР>џРМћя9`й іO ьЩю\ЧanfцjY+ТШKЫџ ФЦЁТg5k#Z'Y=wп8t: ѓ1lпдСшэJNУ:
АШ<н 2bUА}ЭuCє &4$ОV!KNXчьж0ё-С$WO|юй№,OыЙћћУ"3<)fLйп&qt^єx@ 2\BМВЎTЉS)4еqЇчq [+ѕ!AЛh8uNыцдЪРFЂbољѕђЮ ТЩНЯK ёЙ'K,ётM[ wе9.зNЛА1aЊВљчHbЯ§ЏQ-a=ву/ш1X&3
§pГЎЕЇвD=ъ<У: |=cѓ јЯї=ЭёЛGЪх$ !~PтцО04 /i);РЬ;@[КдУннpЃ
ыІv;n=
(:ЄaлY9nцЕ гаЪ 5~Ѓ5с`i0S/8v0bЇ|фэ3KетНТMе1TrЖГбо [`о:бBXWpтI@Йй #Znі;Юxm№oв чІџ
раBpш@ЂЕ.7\A|3iўt}+3;b@-cБЯ§уРЅрm~В qёЏШё>/Ы[d(vUзs2Ѕё&l/С5vЖМЃНЮл3b/Ф6К%p0кtФРђgTуђ]q8ђ%+Ќ?ІBІ1јфmгќЎЫўYфг8~кфZЬБВЇЦdХ[Цcа,ы!
Ии%Ь
H
EеЛgуkLЫЯюЏіLXf Ццls&ь\p C +!;О
Uт@L ФѓWДvні1C@6jz RЉ,
ЌKлЄrFЉљ;|tСwнЅ3/єKД&:fh7ш'bшiPyp`ѓЉлМЛУЉЅЛЁL)>в)!З\пKWхfщБ# ј
ѕєgЅUЭhв"dоCРќыСiBЬ ђ_Y<Ђ{5qБсjіY,ѕwјGй d<~;д *Ж:Ыo0АU№Ї-7Ї5WпАЛ/M7E
msVЗ:TНЫёl?aG~ЮiWБCg;П
VНhп Х oѓsI
43 YП'ЙT*вСг
В}|~Хѕ \ч:FБЊ7ЗѕУkлюdyЧ.$rЃPЯЪљѓ;2m&-Хvби
=fРлІ=jѓуњЃ ђ,ЮDкqЧяЕ i,nю= шЄтtjхiT.ЋЛrТїд*фТ дjНDЈВa2Хц([йХlI7n?jїZч}ИIЂюjp&&NKRїwЅЋUШ)ш!U
/цАCuДЖ,Аж§?ђaЊ4БЋAУ=џцЄF\Nzй$aЊоџBБ? QH ЁuKG.Иq
1ЋгIёyhfѕ{ЙБ /`њЬщЊoјtЧ љ,мТ=ш}ѓ7ЄхёРo2млЏVk7ЋЗe{нtЅщ ѕзLБТиRУ-СWKјоыд;й0ЮВIЬXўЏЪЋІ2\n
Џыг5ФяSСІу Л%7<Ид?С0 Z{К&3JХe*Wю\LАё$'`ђЊ2чu
G^їQяАOюNм;шЏдмO/5G6TўmчШNбU;в@kгФ)_Х)ї еfuwNЉNq`йуd6ЬЌ§Њ'я3ѕ8(?iт|ћ^атђВЗ]oЌ @иН.HТenё]R5{нq^уДлS+ЏczxззE?МТЌvlOsр7ИІ; аЃ&*ЃзљчЉPюёЄ:у5ф
щЧфм lвущnMzГпюЦўџMч|ь
endstream
endobj
384 0 obj
<<
/Length 2881
/Filter /FlateDecode
>>
stream
xкйrлШён_ЁT Ь0fp з>$8qRЕЗђ`oU b$N
И8,щягзр РXNщ=WwOOпКрOнбуАHђC§&Ђйюсќх}{иИ_ьќуЧ7oпЇщТ"*дЭЧћ%ЊеЭЇрчЦ
§n Чq№cльД Оьt иЎw0мЧ*ЪГ@н/ џіцЯ 'JЉжЏd w~Ї,OB'ЬгПI Н*{љђчЮ5eїЬp{оэхrhЛ[Ыu0 -/ў9й Ъг0EЂЗ=+Іваhуw|ЧШ(cйСv2UЋqL`тОэjaЕЊмРRD.х@2 O;v*pн^хр РЧЭ^*T: UЪ TV.йTЎy L: 3 уЛа
z єpKЫGмќТэш7ХSЄaa2љTdCD:ГxкюіIЂЛ<Z&k~ь,>ДMяњСЯнё%ВђХo^п~<&KОэёP:ЭщDiЈЂXЌx)X Сg§АБЅМ#VкЦSЌЏuјІ?aыр?G*iH#zU<Ы
жkы
а pцХеОРvВ,3~Ca /oеЫ SPk/]o#њф:ЬrэeјЛзIYПVpPqT№сШ{egбNu М,Ў ЪгЩЁю>xцЪ!'п#Н.\rV3 0ЩЖяннIЎtюьСVЖёџВKГ <ЖgШsp ХЪФЪ%7AMЂ}цAg щ0 ЮРx Коіv.xГ Г([pќ§ч(і@ОjS
MЈЭ%ЖЭ$Аl"
ЯnRLЬђ.HqхBIц*(
ЌK:QaiЏВ0SУўjIІыRxАOe}>Щ"<$/ђА?ЖнР`U%ЏЁп№ћХ,p§ь}[ЫЛВЧЈ 9пo:б8ЬafХ2ЬЄСov{УїЗ;о ЈдЂ x'ќќ9wЎЧіE6"й~/ВРЮєu
АЃEЕћ?H teхiTЎo{В=рR Eр јsБуШдюаЕ{AЊь>SЃ џьНkьџ0їД!к5dё*&ApЩБпМат Џпbїи№pZE3РtAЧВw п$рУQDaЄгDN@гГX>а.< ШПДPэЊ
$ХЄrяб J_{,#CЖЁX`дУЗQt[я
ЖHWMu.ЂAnЃгYBamИ aОЖCxk*ж=ишВјР=:ІќйЮTГ ~UЎШ.]rDX{r Яш0Q&јpПbЦЏђhњў#cщЙOйHаНzЅaЊЇЄ§эЗпeЯў:ќКHЭZPЯ0'r
дВЊHг#|ћЬPйЩтЙk "ЊxўЮч
KЊйЙOq c@i_FiсљgJbF>с :ЖEP@ЄЇдїXюїьще[НА0Iehф4L; ChHЬ;ў-qЋ0Mв=gз б
Yй 'kуЉХhШЏ$;г%tэџHPЏѓdйМѕё2єТ\ЫLДЪBоc`OЦIІЩ<БTT uhЇYd^Ц@ грщYЕ)сЧѓ№/eЧУЏNшS
@\0Тrє6оъcБЌЪё(gХF?№ +& gу цјПЯ">F5BgN4Gu3ж ЂЌЕЏgЫaєXХj/9RўAїюrNж-с% 5ЋNѓр=fПххhйпхz"№Ѓ=ѕnьyаC`ЊЛiF5i.Tm#анфOрЈЋЉЊBxYgбГ]n~yЫЭјЎБэzNбЫ& 71taхIЮзl ;Sє*SЌ н&Ює#;3>
ѕЮnЛ8гЙХСD>: ъ-ЭЬрёТІ§\AГ! юkюIрkМеф2kЛкWвX8aXл` ъћ<6_э>ФRи) _дcыw" 8Fdэ@Кђ4Б
> МтИН
~/+јXВГe'ЃКТB !Ic CAњ ёЩфФObЁЛqkП8ЛЉ
Є И^IярЎ!ЭHZ#9*Й#Е5чх Ѕ rУQйгI3*ХЅU%hPSвЋeъУЌ7Ђїм§SЏ ЫжЊъ'Dию3/ыж(ЈIЉЅs рФ!\мnФЅ9eщd rPЬВ)СЊx~Ъж2ОьРpXКќlщєўNXh e2і як^сЯmЦЩ@Б %=5ЬЈЮПДoю+,: (б{УVSJЏтЎ
ѓONОЋлu№ЪІЧЪѕ%оu№`щЩ^нЙl}~iпхzSщоџ№IНћћ/RљЕ5?|8UЙЗveѓ`ј-І>Ћ8Ёkf9йJеwЅbGцc}xЯаїR2ЧwNЧCЖxDo_р7Sћ}a Ъ^v.CЉ$MrY:ЃрУr}"%ГПХзЯќEёУPхвZm6ы&- ѓftЛЅюl.јЃЦyk0ъЅ|Рhr(Н ТЇД LS{oќиЗмљфs-0=:oІYfюљ;-К1mњ[O|Kє` 8jCФIОr%рй БdKХЈ/Lќ (бSЋєиВШwВ-Y. JМ aЊБ uК;еЁЌІV"ЌбЁ)ж=u)ь бQ{ШМщБигРC?ЕTЫ=OфХvWТУ_eЈЈxФWRСq§Гc`раv ы<ZMD12дA:1ЅWт,+ЬT8erўЇ7LаZЩы n
зЫМkytтн ] []їЗЄXЩ/KSј&Ц5XpFИyрS
/5`;BїэщDљ"зlЯККЖ+Aaљ(ЬБiy~mъй тМиЋ іFЃшJ гўhіЙЏiј КВяW КEG\mРM/~ЪСUъxТЂьR"ЂОрw8IyCG{U0§Щ>
kФхє/D Е2йёщ,кt|Мр+ш,Zdо8ъ_a
ЖЊxђ%ђьЯБщ L
ЗMzЋЎЙРОдЌкЙ$Ые мЗќ:лS;[%ЦBфЈѓ+&ЁQыPBљVХ/;~љUсхxНЪСЂ]>5Vѓш+ьЈ4 =еМПўИp3зH~Oм+фrbэ<ўп,ў ЊPЖ
endstream
endobj
388 0 obj
<<
/Length 2925
/Filter /FlateDecode
>>
stream
xкйnмШён_ЁЗЅАЭn^ќ
тРY YA`ЏjШ!Ь!e ++_ККy eЫ0 6ЋеUеuеU џдU\%ZћIЏіч7AЛу/ўљЗ7J№vИaўrџці]]ЉРЯL]н цЄюЋоПjшЏwZkя/ms &о зaъ]_СыNЋ Н0Нў§ўяoўzяNТ№,!цїySу+mЇМ;чВA>`!UоОmmwЮ ъїT
'оњ/Ву9EЅ3?ЩBр*СYљIXиЧ
*Пєoр5 НсT2ќЃЊgF
рЈЋКь{ј\бЇкЫS.8jВz.ЙЋ2 Љ кWsu§@ї`рГЎќ2V]йѓ[.аЊy зЪ;_яч5kѕ!еg^R_$РKjѓыїеч_яв4ёо]Їкk;&нрЕ]7uеЙldu$wj?4Ш^Q~ $ iбЩ<ф eЫЛB NKјіTе5Џђњ э9GфчaCўд.ќXм!,.ќA оa ЫІьђzЦЪ,X_1|/ ЃзeСЋQМХn xЮ=:ёЋ("іО93X
$Ђ`y?vL0і f;ЯИnЧwАщRћ aXп Џw(ЧО:єўD)'TоБbХЪ+1ИnЄмЙі>Ая|;eFdЌjПО*eУb(ї ы
с Щ%Nќ,г?~гHм sak~^рЕQЩCпжу 9zф;I:QьЇЫ\;@аМa[X8 јћйщvЋСH3ёк ЭЎЏ jv@м$VўЩ
д?]{XAЂ/ОhAн,ЈlјВ5ЪДЛb КМЮL% _Ф#К-u№N ;?]cuHr*ЋV
2@ФqЯHsь~ГVШєrТ0Х.`QЭбoБK5ЇШМsBOWtO!jЊьjЈ$Ќk^=аЭxлиэуL§8А^НY,BqNбOLЛBy хYќќ0,gХTљAфђрнkќiВхц]ОcЈ,г Вa?GD ћШПЧХ јоР6/KtўuЁrЅйuЈЄ
mЬМН:ќЁHІйu*ycК'Њ jђsФС.рл<`Ш {р`?^4 LЎрХ**Л/
~+ЯU]ЩЂЛveN
W_rw E!; ю_о_VвсЎдќвЋa H;R:z]R§ЇФ эщ'ЁИж#эЧъlR!AЭУэИ2MGЏѕЪXoШ wщ@зіђ X2јWAI8Oжы$WЊт{ЉъЫ Fw^I ЋІаьNДОm)юМя§СБ<ЩЌ;Ъ04~ ;+Єxь,БНќtикпETRewЛ=н7#&ДuSФl ЇYb<ВЈњЧ:;У\0ИПkРм@bfоћaЩьјШяь.эmxгїyН Ё4Ж v zWњр:gЕЦfl4ШЛЎмcэМcVGKЈэУ@] Т ЛжКЉ%њbІІ дпaа6/нЦ&Щ^sfЛф&H#&P~%Ы:ЈьЙKЌoЧцEЛдТfл@,ЕrcDТЂ§NЖzЗGOзШСAUBЛTvybшЦЊТqШUм6;2љГЯѓ^§8BлЗ )єf}Гжe ЇCЉјШP^nСўЭs+ь лГ ЖшКйwб[s<є_Xн3&єcІс юЯЙШ-мГIїS,ђiџTЮњ 'їѕгwѓБШЬЙ>9х1еўЬЗwеаЁLДGгнЦвBаб >t ОхнYЛЂў{!гЎвGL{HлАeД <Еc]l%(ђrYoЋП |ИvЋЭX|hы(Cї Ыљфe ЧYщ9CЛ=rрWъіdФ^ЮAІщ b
xЯxф8эыGб"|Ь #`SС кюrZrr>VЕtтГ+С9NЌ(пДѕoЄ9WнА6чўЫ і:УЖ^2GNцЄЙјїЪ$iІ3iўf1%2ГЯчз#Ѓ!>Jv#1=NC'LвP ОнM$Пq0RбвЖИ]T
іSxсh
зgсЫќтсЅPЈ,o3Џ
5дNJЉгЅы§R-ќRБCіз ВљqПfЈФ.YrQДѓZ*~ЎEDџТю0и.ж#јeхЬhХ< Б ш*Ъ.хzTh&# Q!йzь§l}\-mзЈ mАй2 й4vFфkўщu]оCоSL] ]ХлъюxЛ?вПЫx|ћ!ИQ:№#[{Ѓ|Tк ђ#ГЊй№$eЂ[yюх фѕндk?яxwТМИхЁm 0Нv Дз06RsрЪMC, {7ИЖЫ0Ж]ё .ЗQЁMctQшfнјA6ыЌ$keS,+7aЯx,зђ|цьДiЪ.NяbЂ@к^4пCaђEкr аs<Рj!жX~л F-S.ПдLyI / HRУ QЮ$вuл
EрbЏХPДЊe2гця:ћz,hDвюУтRђS`8ЋCьцђЮцUF<НЃ6ё
o4~Їэ4ё 1я x
wZ5эИIБ1`рд G/HD§gц§ЙaЄKf*Г
y~ єк Вм Сь^S.PKЙyУцHЫЏ /s2ёвo]шиLiЈ xЩцe%#й,ёмpRЮџYт.N>u@ЁІКТo qhтееКйYReЈЅT kаж]Qoоnf.ФДЪ
i:lуkБЧ|Pџ
Ѓ#ОЃF'ИъЊ,шЊ|YѕqE=ОВw*ЧШе~ФеџЪЎEЉ0*ЖvsЫ>g Ќъэ|rвўєC_§Ц@Ю§п 8ИyЉъ !игмw3 юTјсЊi"еѕъW"е"ѓЭxр|ЂoUР; хgн щм ЏWп VЃнљЏЖъмаАЫыбp_BФН_ iZЇ
ІњЗ-H+аЌЈcVьznІёџќ 8$Ю
endstream
endobj
392 0 obj
<<
/Length 2891
/Filter /FlateDecode
>>
stream
xкЭЫnфИё>_слЊЗFѕБ$ГШуd Сь,ТиmeєшдіxБoOНHIm9ыcрШbБXЌЋЊ ^№^СUІ_ФљUйО : Џx№ пЗФ§ѓнэЗяф* ќ"(ТЋлУдmuѕбћgWOуnЏђўаwЛ(ѓ vQюaЌaКWaЇ^Tь>нўхЭnнIIН%Фќ Т еј*Эc?T13v{oрј$їЊОе5Вdю*К;Їн 9.ы0.ѕUjЛя$Hzр zhWo=5OМ,чd \е~ЈЬ О;ЂpЎі!_b *?Lјѕt'оЗССхCј rїwћ`ЗvЫУ.Iр Г}~И jEcb "Ђ(ё|N_ѓ=GыAшiв%Ўмй=ѕtЋ@юђ
шDі8<ж ЪД г12мкАЅАk\DюHтРпЮf ѕ№ДЫcдLѓЄнt#IJrrЎўs 'ИзЦ}HqxeпЕzDT4+tжBЬМ nI*}ЅiрНпхЪГєЬWнsЊщ6еLЉ2xqHЭЧ%`fesЎPС8ћ7В
N.DЅ Х
n@<Пџо ІOОђЉ4їГ(ГипБЦQюйЪDIтqo %~ ЁBѕ§Gu§S[& e;є
Y$N cЃФйcн4<њЬіРIЁ дёTќUќ9LеѓЗюDь вFю§љ і№УЙ+Р32є8f!хЏЂ|m' KуТыќнYР>'љ"8КЖэФTєLb2ёq>ћ> (2бgФЙ
ЏѕУ
мжха ЮОVу5 L[ј^d#HВuЁ/GР.KЧKЇщ"ќт|$
й @_ЙА2Ч\0, М;К`
МJA1М§Й5C]ъцтДqх^Є_ЄшKxН"ѓ~5CЯ0@NЭ8Nzйаrx_Ќ\Т:X.=Yа ЮЉqdlz}Ё5КЋЛc/нѕъ6ЫA (KДы ЩWИс сxEѓ$HAdiаА21Ќ
$ю):ТЊ3MмsЌ9ѕуБlВ52јбЉ аq}Y8ъЩ @ кp4лЕ9bІжtpХlЙ0= 0gG3YDўвfк@фГ
VШЫмR?%/ўЁСЫ 1}+rgі8ЖЉрЅfхЫ3/TПd^ќBrX|NBЈnL=}'"є=bЂчя"сb<qЛЈ IJeb'8bгS7рTsnХk{Сk$>iBњiіЊ ЊТиЂMB[D4KЕ OкР ЂЙЬ4ЕФћqМIdГ<"Ќ;рь@к% цt878 эы1WЁїc§@счмюrю"ВfЭЌ{!мЁ|ЧyџжГф№ЬКьnП/с_Жd+Ш йvфmB-Иє.\
YyфnПfаГЗ`Еx ?KыТ
жyEИЭж[4IUЄБмћТ | 8№рrWZтew§%п b[іС \gуSзsз aўa MнquчsБЙЉФ|ђКbЛmъкcБS)M2E\=T Ъ&/ё%_є[АшaВgфЂx$TЇ,Ьс&§ч дIЬЮ#_$H
slзiшЪчЗЭф
|.8ј8ылzъђІФћаЫє фpЭ
ІФгдЯвpѕ,:улф8,ѕЯdкгћ-ІЁ ТtnС5?+<+`Н§ЙчцqЈЇMянУiIЊФ$ сOпІЛ7ѕхR№jІ}%sщізO ю в
П9шаfн2іѓЕCмозл/x-Х:I $|6L љГємШO;O. nЪЧЕ]УGNUKBпд№~КЖ
ыx-ЭзzЄѓ_#HЦ{Mн*ъф 9Vи 5иЦ.ТY?дє|vКfНЦчTгUё7и*~Ы%МzwЗаt.U}'Њ:ИЭЁzwa wќ;aСћЦ@§энk @Ь*0а#aXЉ001`щi Тw0z| в-Ћ3"ћCЯй &ъЮ^0aЈ)wbСМэЉТЋ.z?QБfд\ыLИaЄo./9AjPдЭ шкTЫФмЅ3ОДЪЄл#љk JF5tяЭhF>YЯ"ђ#OPщзF_ъЃEPСЬВФйТёp~s65/џЌрЃЙ~1ЁdЭ)цF ЋQlЬХБцЯeЬнъ§?Fл|+кВ3ћМШЬЯpЯЮО =P0P :NЯJХ6E*љ 8њЛaУГТKъ
_(рїуЭWцЂќuяФ\5
f<7T]нEeѓoФЩь0?=a}БeYъiјЂ`б'=LЃ/iQЁ|k%ЙT/ЪЁtжсЄ'Ѕ ЉjЬAGdўyuЄTВЈeVсбцV!mЂїшЯй їт$Ht;jмђє"r0 8{СIеwџ#э,ц< ?ЈUёшТбГ8[4Ёa}бN
щ^lcАg[PІЭЩ.ЕЅЋьWљЙ;ж!кns3: иЎjlжс[<Ьс
_ѓGВгВ Ъ[yx|q<УќrЎeb&вюHM}ЩRнЈ!,mФ=оЈ:Єѓ~ o,kЩ
Фi w^рuWA
MнYФЕ9dg/5пЃТTДюјozPьЋ4^UЄ=ОќЫв]шЙОФс%;\ЦJцќЄH/:уEZ&к#aЫ\Ў wщVSfЈlЧЫХС>
stream
xкkoу6ђћў
Ћ\ЌUЂ^{z zњЁЂ8dїPF bmЩ'ЪIг_3Ё,)Ъ&-Dфp4їCrSM$qЉMuz'<Д?lhёг?пIЦлтnљзwп|І)тRrsГКЉ7ЗбЯ мv$IєЗЎнЊ6@T~eR3й
ЙUЬХZЛ5qЊгњ]AW%poCжuћРЮЖЉЖ;5ж1шhлЦєwSЧлV:К дъцЃМЕЇTнЅBGИGNA`@-s\Ф2ФЂџ`КДBf§ГmeІЦmн!Ё':ђЬтЂ9!єU5uMИz]ДXfEPЭэЊіт\х!1РєІ DOГ<њvы/Р ` ъgяњи3)4p ба]знwc=USфqVfsещTyх VR
Xfкa ЛяН BhђJЂХуЫ ЙСWs N:Б-ПPsюylPV!Ђ љFw6UУяT_2ч3QCџ№Еяњ@
}зЋvб* НћгьтUІ!ОЪрLt23@%Cі№~ИК,ЌзтйбэhЗюDrP&+ћЎЛ§| ЬwjрRЗЪ~^ФЂКїnOomEцhыП 4,ВцЯЉAЪ2zьэ№Eо@ЙШчМ}§Ж
Ш\Х(ЫWqаkI9wХrrыСXЧчP8aUuГЮЛn&FDC#Ь)%Їа/0Чуэ]sГR2э њёSИфt2U)рєb9џt* zВ*=3н_кг С{ \ul _Эл ЁяNAy@7CЮј3Ы н"ћ:ібо 0xЌіРљT"\8HtNёЋ?NE]ђЙЃsВ ЎВтЮєЫЉёbш|iz
YxЫ5 )ёгЬЏ4СS№пЫѕEoд)ЪєкRж{>ЁЫ[љ(RdeЂхaщЮz*Zѓа№eч_рвwTK2дХp,јгIйrDбИ5ѕд§ЊЉGГLйћй дуБCУ<2К^T7Б VщvХ_8%ѕPPNM§с2ћџСveО7ЭZЮCOи[`|ѓбДПIГQ
n\иіыiWTџ
ЇcFсeNc!УХе§й5&grзєuы! cQdиyдyУfДagшJЖ w
3ЎЙ%XљЯЖcz[
ОMнЉЎЕzєэwH№
v6 3№б WТ+JЛzUЎ8ћ7`DЋ§l"Hў<єѓЙ;LjњабГЬм8Вu>И'7П3є@М_wт,.ЧДMEyХ^!G4к31\њvСЖ;Aћзpѓ
pi=зХcC
Ќдqщ'!ХѓбЭдџ:+@йm08 q3Ыifp8я yu(|5rмBtSЋЛўвЎіЊ2ыШ'нЎКoЊЯЋєй8Aхфю@ХHVF{ h гаХІ ОыCю@n\г*П+dљЊEЙФL>7 E*ЕO~єэkњo№є%УљЬ+(ѓЎN5y\ЃО ,h ц"MtеL9Ь ь`7S0.r'г"uХ'?Б hлBeмиёЩЄEЙu
CF5 sОw,#,4А4m wgоєOќVG Dьn-ДЁчШЙ=Яйч§З{6Э/ХхРз^ЮЗA№КёГ ЋЫ$E]ЩsцDРqЃ4Mп|9№ СћЊgк№i(Ё/OXЋ[ЧExhhшои#Ц4Ш26Шo*аПЇ\ЛЎsoОLAAЖ АRџ
AtX7{№Е6ЈзыK|г
>Рqс:ќ+5пѓep жќрЪ_џ№Оё^ў_пзГh?{ЧЧZЯ5=њЎ[JПH9љCењBФЩ2ЏџtiНЯЌ}VJу$+џ`К
*/ъVаЦѕ6LЂ{SЮ8LЮ!ЕьЦ ]?рv,>Jqёd Ф4ЏЙэЖъ.ФLгћЏЕDgжфЬ@i2КЊ№}RI(ВG yюо Т;ј.зЗ>Юрфл џ§=Ћ:ўъPCДГу72ЬЮ ЦД(V<юдіјlњСVanrіwв0{-цЋvб?иЪЂЖBдkњ$* ХБo ЄhђіdЋО{гsГ /OсW8MчБSЈі/`CYР-ЈјћЪџїQ,
endstream
endobj
400 0 obj
<<
/Length 2625
/Filter /FlateDecode
>>
stream
xкYYлШ~їЏPЬ ћр!^g7и` й э mВ%ІHЧќуSGѓвpтY `X}UWUW}UнЛўФ. wRAІг]~~Ro{м1ёы_^ 7ЯўbцЏўјSэDda&v%ЋbїЮћ.ћюЮWJyoњN&о;zЖэJhњJiь)qїссЏЏ~|vЄ|ЁH8ѓћ2ХЉв,гЏC]ѕїЉёrЊжЪ4pІУ,Мяч'rkVь(ШВl\ѓъ5CU№КcљЖмъOАmлДHjяlЛЮ э4~&(S;_Є #орС|ЌK$#я}("SweооитўЪф:&A
Я^ж_РюЎaкfЈ ІmнЗW&г0мвбi:9bуMесxКѓЕЌe`Ѕi3ъьј[7=4^Uм*,ШЎk[L, Яq]kр.їаа Fџњ]kMU]6n58Иѓ!Міб8/T "СjtC2KЦsY:KЧ9ВEт#|Rк~BcаьУ8\7uUжжДмЎЯ;ВЧ^ЧН$ =Аб
K vУфAЛ2 МictујЯV Ј Tc|е
бъ0@ЪM|ЭіщХоCГ-і<ТЊЯQЉ=ће/u!oXЕЦљ3pЙчi§ щИЯБ>ES;ЪtБ- jЄXЧTїy(лў}
_ср 5ІFбMYџщ]x?OhM}ДыЎюѓЭ~ьCцџ[fQфнЙЬлІўАБї{@PZ `ЋxхO>[%Іe CiЦФІhЄђЅ.А№ dШ 0>w>§Љм шк ЙVЁї0бэzІ
xuc&РCo[G95бќЁX сpТ
'4 kуЏ"Ь1;~ћПэPoY%Э8N~wЖb
,и!ojЂ=ЛOІ )Ц0 ЭHдN,0 ФU?ЊІТ.КNz <3ЫІХФОu&щкSмє ~ вџ#8OM`1ФЃ%yj,бRЛЋ9ІWPуЯюМЪj І~);GНЉJгйnK4 Н,2+$в6ЏЪаjДs eЂTзМBЃ(AчC
UЛ)E5LМ>FљJХ#^A t#wЪ>
ctiZozGYJ№X0<ЭBнЉiСuj
Ро4ВцЁ#vДш7ыРYЮ0dИ]лGnЃN3 пЬ=<ЩY0uфЮЇМтЧВюЖРаaC<уI о=Кж pwкwуЈ#ЈпtДФ#`Ъ1Ф ѓj(ЈТH8ЮЂЏІNKeіXDl) sщы ЕKoјЛИ= РЊК0^kез*+v=aZф(3њТBTWn:zЮеГх|AШЮ>Nэў\жћЇ>vЛЌ/ЯЈЈCя
xЛ/Ьuџ БЭЁ6.ьqoк зТч
Ы=8є{X*ОЅcС§љюKS9: .{ѕMѓjlШojnorйX,жLiZ ЄEZпрыЧюВяЛ7nшe#\hXЉo29GЁЬЦ(jr=jЄ йёЪЙЬЦv lИ]P3б0ючМлэЧэ
8"sПМA"ЇфњыўЇRJ'Zeyф\Ъ*ежн~Й9п% 7ЄЫЧюAи3ж(бtH6nmУа*'ќCe#ўY4ЄЬ4RЛЭnJфwряЖЙшl2
мХЄЄДЙ,П"Ь ЈзcэьХОХЇЅіВИцвхNq8з Ш+!џгEўdn9;г[vИlm Шaн
Г6!DsAчМюуєЦШ 2
Tп^ЉщcЛСTttjщ# ца:*Cј>S
ћп_ъhвkмСж]Й,LешIjvMEоЧОЋ(Уѓ(SЋxхЉх?ДЎВ0тO J
АДЋЅT
'эMЎаўЅгpЖmc9ІНПSGznџtІEЦ§3в +П 2 Њў~ЫрQМk{opV!: ЇЁб1И9{з Џ-'ЊюИйЧЋ>u<ТQ1рбПюРШЭР#|QGЎ/xUtаы
R3мїь;LВѕљО§zKnнPќoЙwBpгj м#ЇkяГх<ИГHf^юЅЇиЌ4рV4Яѕ§Юн?<{мYЈyAsЁm%| дЁІЇEЦFgё4Нљ№lСVЛњи BЊUBpВјnIxM/ Rеy9r cЦIєвeP,ОсуВЊ o38Ю§=О` =Ѓё
;ь[уM
Л!}нФzp§$пweФЩpA>ЖцLJЈщqЧW~ЈВюшtфK[БZNYќ0дЙ+Зp
$oЧЊ' ВHЌмЙФ_G Ћ |sДXJаћ+`1 чpmнtCЧ(#Ё1H&IОH"= ~:fЮж1vЛm >;шЁ)[ВrЛоyРбp> {<јЋ;XєЎk~ыЗЯLФ2ањEШuDDЫїgMй}ЙЁdп("Ф bЈz3ѕtwЄ!ЄhmНчё2Кбz{0> aИ7mбqН0Vо^EЈ n
Жt 6ОOsѓх tШѓтЏ qц} [ЯІtЦѕVжt§Ј IЛєќv( Bf! ўВЂ
є>е -аqЕ HB>ыT9^ Йр *цOIvшЎNЏxIц§УклпмTгэ2(HлјЋ[С=ЈBвЯoыхяpnЕ?/пј%nНIљіd.єbflw?зSНо№o8JП%~Иwi5у§.u1GW7Ъ№V;!у@ХzdPoЋяќЈ8NічйкмА KХo Ё wђЖМ,~C1rK~iщмЕЄЙРА 7ЇРІiЈ
endstream
endobj
404 0 obj
<<
/Length 3362
/Filter /FlateDecode
>>
stream
xкХZылЦџюПтТ0ЏБ6ћфУўдqЂ@цЂH($Њ"хГѓзwfgvљ8вЇ PдхrИ;;Яп Љю$ќUw
МЫ
ЭяжЧWвЯ^vw4јћЏгp5 ќѓУЋo?8wЇЄ(dЁю ЖУЅ 6w?'џ8е]{П2Ц$п5Ї{%юuTЖЫQ2OЃя}јЫЋя тNNыYBЪ'