mirror of
git://git.sv.gnu.org/emacs.git
synced 2026-01-06 20:00:46 -08:00
(Named Features): Explain subfeatures better.
This commit is contained in:
parent
e1f2af9cac
commit
f690ec33f4
1 changed files with 8 additions and 2 deletions
|
|
@ -726,8 +726,14 @@ The argument @var{feature} must be a symbol. @code{provide} returns
|
|||
@var{feature}.
|
||||
|
||||
If provided, @var{subfeatures} should be a list of symbols indicating
|
||||
a set of specific subfeatures provided by this version of @var{feature}.
|
||||
You can test the presence of a subfeature using @code{featurep}.
|
||||
a set of specific subfeatures provided by this version of
|
||||
@var{feature}. You can test the presence of a subfeature using
|
||||
@code{featurep}. The idea of subfeatures is that you use them when a
|
||||
package (which is one @var{feature}) is complex enough to make it
|
||||
useful to give names to various parts or functionalities of the
|
||||
package, which might or might not be loaded, or might or might not be
|
||||
present in a given version. @xref{Network Feature Testing}, for
|
||||
an example.
|
||||
|
||||
@smallexample
|
||||
features
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue