# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1166394187 0
# Node ID ea5c96e3cad90d92f494d6690b51d8f400f4cc17
# Parent  be5e68ff267369f757ca8753067d872e1d627ecc
(Named Features): Explain subfeatures better.

diff -r be5e68ff2673 -r ea5c96e3cad9 lispref/loading.texi
--- 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