Branch: refs/heads/yves/fix_define_tab
Home: https://github.com/Perl/perl5
Commit: 9b77eb4ac2d172ccdea18e5e53d5c37d3bb0ba0c
https://github.com/Perl/perl5/commit/9b77eb4ac2d172ccdea18e5e53d5c37d3bb0ba0c
Author: Yves Orton <[email protected]>
Date: 2022-03-11 (Fri, 11 Mar 2022)
Changed paths:
M Configure
M Porting/config_H
M config_h.SH
M cop.h
M ext/File-Glob/bsd_glob.c
M ext/File-Glob/bsd_glob.h
M ext/SDBM_File/dbu.c
M iperlsys.h
M malloc.c
M op.h
M os2/os2ish.h
M patchlevel.h
M plan9/config.plan9
M plan9/config_h.sample
M plan9/plan9ish.h
M regcomp.c
M regcomp.h
M regexec.c
M uconfig.h
M unixish.h
M util.c
M vms/vmsish.h
M win32/config_H.gc
M win32/config_H.vc
M win32/include/sys/socket.h
M win32/win32.h
M win32/win32iop.h
Log Message:
-----------
whitespace fixups for "define\t"
'#define' has seven characters, so following it with a \t makes it look
like '#define ' when it is not, which then frustrates attempts to find
where a given define is. If you *know* then you do a
git grep -P 'define\s+WHATEVER'
but if don't or you forget, you can get very confused trying to find
where a given define is located. This fixes all such cases so they
actually are 'define WHATEVER' instead.
View this patch with -w and you will see "no changes" except for
config_h.SH which needed to be changed to ensure that it produces output
that doesn't replicate the problem.
If this patch is getting in your way with blame analysis use the
-w option.
and fixup config_h.SH
