From b3e35c01b6aee7e813ab351bca126ce1f13565ed Mon Sep 17 00:00:00 2001 From: Steve Hancock Date: Sat, 20 Jan 2024 17:24:41 -0800 Subject: [PATCH] update html --- docs/perltidy.html | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/perltidy.html b/docs/perltidy.html index 93da32e9..7cdcc71a 100644 --- a/docs/perltidy.html +++ b/docs/perltidy.html @@ -4451,7 +4451,7 @@
p: package-crossing variables
-

These are lexical variables which are declared in one package and still visible in subroutines of a different package in the same file. This can be confusing, and it might cause the program to run differently, or fail, if the the packages were ever split into separate files. This issue can usually be avoided by placing code in block braces of some type. For example, this issue is often found in test code, and might be fixed by using the structure

+

These are lexical variables which are declared in one package and still visible in subroutines of a different package in the same file. This can be confusing, and it might cause the program to run differently, or fail, if the the packages were ever split into separate files. This issue can usually be avoided by placing code in block braces of some type. For example, this issue is often found in test code and can sometimes be fixed by using the structure

    main();
 
@@ -4459,7 +4459,9 @@
     ## old main code goes here
     }
-

The non-indenting-braces comment #<<< is not required but will keep the indentation of the old code unchanged. It should be noted that this check is limited to packages which are not enclosed in block braces in order skip temporary package changes.

+

The non-indenting-braces side comment #<<< is not required but will keep the indentation of the old code unchanged.

+ +

This check is only applied to package statements which are not enclosed in block braces in order avoid warnings at temporary package changes.

u: unused variables
-- 2.39.5