mirror of
https://git.savannah.gnu.org/git/make.git
synced 2025-01-12 08:40:55 +00:00
Minor editorial changes.
This commit is contained in:
parent
2153102725
commit
db3c60d235
1 changed files with 12 additions and 10 deletions
22
make.texinfo
22
make.texinfo
|
@ -2092,6 +2092,12 @@ sets @samp{bar} to @samp{a.c b.c c.c}. @xref{Setting}.
|
||||||
@cindex recursive variable reference
|
@cindex recursive variable reference
|
||||||
@cindex variable reference, recursive
|
@cindex variable reference, recursive
|
||||||
|
|
||||||
|
Recursive variable references are a complicated concept needed only for
|
||||||
|
very complex makefile programming. You need not worry about them in
|
||||||
|
general, except to know that making a variable with a dollar sign in its
|
||||||
|
name might have strange results. However, if you are the worrisome type or
|
||||||
|
are actually interested in what they do, read on.
|
||||||
|
|
||||||
Variables may be referenced inside a variable reference. This is called
|
Variables may be referenced inside a variable reference. This is called
|
||||||
a @dfn{recursive variable reference}. For example,
|
a @dfn{recursive variable reference}. For example,
|
||||||
|
|
||||||
|
@ -2209,13 +2215,9 @@ function. This is an implementation restriction which may be removed in
|
||||||
the future if the need arises, but this is not likely since there are not
|
the future if the need arises, but this is not likely since there are not
|
||||||
really any two functions you would want to give the same arguments.@refill
|
really any two functions you would want to give the same arguments.@refill
|
||||||
|
|
||||||
Recursive variable references are a complicated concept needed only for
|
Note that @dfn{recursive variable references} are quite different from
|
||||||
very complex makefile programming. You need not worry about them in
|
@dfn{recursively expanded variables} (@pxref{Flavors}), though both are
|
||||||
general, except to know that making a variable with a dollar sign in its
|
used together in complex ways when doing makefile programming.@refill
|
||||||
name might have strange results. Note also that @dfn{recursive variable
|
|
||||||
references} are quite different from @dfn{recursive variables}
|
|
||||||
(@pxref{Flavors}), though both are used together in complex ways when
|
|
||||||
doing makefile programming.@refill
|
|
||||||
|
|
||||||
@node Values, Flavors, Reference, Variables
|
@node Values, Flavors, Reference, Variables
|
||||||
@section How Variables Get Their Values
|
@section How Variables Get Their Values
|
||||||
|
@ -4778,9 +4780,9 @@ $(targets): %: %.o lib.a
|
||||||
In System V and 4.3 BSD @code{make}, files found by @code{VPATH} search
|
In System V and 4.3 BSD @code{make}, files found by @code{VPATH} search
|
||||||
(@pxref{Directory Search}) have their names changed inside command strings.
|
(@pxref{Directory Search}) have their names changed inside command strings.
|
||||||
We feel it is much cleaner to always use automatic variables and thus
|
We feel it is much cleaner to always use automatic variables and thus
|
||||||
obviate the need for this feature. However, this feature may be
|
obviate the need for this feature. We are still debating whether to
|
||||||
implemented in the near future for the sake of compatibility. (In fact, it
|
implement this for the sake of compatibility or to leave it out to avoid
|
||||||
may be implemented before anyone but the author reads this paragraph.)
|
such terrible ugliness.@refill
|
||||||
@end itemize
|
@end itemize
|
||||||
|
|
||||||
@node Concept Index, Name Index, Missing, Top
|
@node Concept Index, Name Index, Missing, Top
|
||||||
|
|
Loading…
Reference in a new issue