Mercurial > emacs
changeset 74704:ea5c96e3cad9
(Named Features): Explain subfeatures better.
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Sun, 17 Dec 2006 22:23:07 +0000 |
| parents | be5e68ff2673 |
| children | b3678b1f5d53 |
| files | lispref/loading.texi |
| diffstat | 1 files changed, 8 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/loading.texi Sun Dec 17 22:20:40 2006 +0000 +++ b/lispref/loading.texi Sun Dec 17 22:23:07 2006 +0000 @@ -726,8 +726,14 @@ @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