From e2260686ac7bbc1a03275b477de72f5fce872603 Mon Sep 17 00:00:00 2001
From: Steve Hancock <perltidy@users.sourceforge.net>
Date: Sat, 17 Aug 2024 15:14:16 -0700
Subject: [PATCH] update docs

---
 CHANGES.md   |  3 ++-
 bin/perltidy | 14 ++++++++++----
 2 files changed, 12 insertions(+), 5 deletions(-)

diff --git a/CHANGES.md b/CHANGES.md
index f498cb25..3d5053ad 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -18,7 +18,8 @@
       Use -cscxl=asub to prevent this.
 
     - Include check for unused constants in --dump-unusual-variables and
-      --warn-variable-types (new issue type 'c').
+      --warn-variable-types (new issue type 'c'). Also expand checks to
+      cover variables introduced with 'use vars'.
 
     - Include signature variables in --dump-unusual-variables and
       --warn-variable-types; see git #158.
diff --git a/bin/perltidy b/bin/perltidy
index 38ea377a..b4f8ae32 100755
--- a/bin/perltidy
+++ b/bin/perltidy
@@ -6078,10 +6078,16 @@ meaning:
     note          - an optional note referring to another line
 
 If there are a large number of issues it can be convenient to read the file
-into a spreadsheet. The checks are for lexical variables introduced by the
-keywords B<my>, B<state>, and B<our>, along with variables defined with
-B<use constant>.  The types of checks which are made are identified in
-the output with one of the letters B<r>, B<s>, B<p>, B<u>, and B<c> as follows:
+into a spreadsheet.
+
+The checks are made for variables introduced by the keywords B<my>, B<state>,
+and B<our>, along with variables defined with B<use vars> and B<use constant>.
+It is a good idea to also set B<use strict> in a script so that Perl itself
+can find issues with variables which appear in a script without one of these
+methods.
+
+The types of checks which are made are identified in the output with one of the
+letters B<r>, B<s>, B<p>, B<u>, and B<c> as follows:
 
 =over 4
 
-- 
2.39.5