; Improve commentary in intervals.h

* src/intervals.h (INTERVAL_GENERALLY_WRITABLE_P)
(INTERVAL_EXPRESSLY_WRITABLE_P): Clarify commentary.

(cherry picked from commit 7d15d17353c02b0ded3671ecfaf2f4a8c19d43c1)

diff --git a/src/intervals.h b/src/intervals.h
index 4ddb7f12b92ad12191118b44e2dcaa4310e4af93..5718874543a3a00f5a1eb9693881dee582cd8170 100644 (file)
--- a/src/intervals.h
+++ b/src/intervals.h
@@ -204,16 +204,16 @@ set_interval_plist (INTERVAL i, Lisp_Object plist)
 #define INTERVAL_VISIBLE_P(i) \
   (i && NILP (textget ((i)->plist, Qinvisible)))
 
-/* Is this interval writable by virtue of not being marked read-only, or
-   a general value of Vinhibit_read_only (which is read from the value
-   provided as RO)?  Replace later with cache access.  */
+/* Is this interval writable by virtue of not being marked read-only
+   by the 'read-only' property (passed via RO), or due to the general
+   value of Vinhibit_read_only?  Replace later with cache access.  */
 #define INTERVAL_GENERALLY_WRITABLE_P(i, ro)                   \
   (NILP (ro) || (!NILP (Vinhibit_read_only)                    \
                 && !CONSP (Vinhibit_read_only)))
 
-/* Is this interval writable by virtue of an explicit inhibit-read-only
-   property, or the specific presence of its Qread_only property (which
-   is read from the value provided as RO) in Vinhibit_read_only?  */
+/* Is this interval writable by virtue of its explicit
+   'inhibit-read-only' property, or due to the presence of its
+   'read-only' property (passed via RO) in Vinhibit_read_only list?  */
 #define INTERVAL_EXPRESSLY_WRITABLE_P(i, ro)                   \
   (!NILP (textget ((i)->plist, Qinhibit_read_only))            \
    || (!NILP (ro)                                              \