Skip to content

Commit

Permalink
HeaderParser: spell "preprocessor" consistently
Browse files Browse the repository at this point in the history
  • Loading branch information
mauke authored and demerphq committed Feb 12, 2025
1 parent ca7f404 commit 8419236
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions regen/HeaderParser.pm
Original file line number Diff line number Diff line change
Expand Up @@ -1611,11 +1611,11 @@ is the same as
This type of comment usage is often overlooked by people writing header file
parsers for the first time.
=item Indented pre processor directives.
=item Indented preprocessor directives
It is easy to forget that there may be multiple spaces between the "#"
character and the directive. It also easy to forget that there may be spaces
in *front* of the "#" character. Both of these cases are often overlooked.
in I<front> of the "#" character. Both of these cases are often overlooked.
=back
Expand Down Expand Up @@ -1839,7 +1839,7 @@ style and form. For example:
# endif /* !defined(BAR) */
#endif /* defined(FOO) */
HeaderParser uses two space tab stops for indenting C pre-processor
HeaderParser uses two space tab stops for indenting C preprocessor
directives. It puts the spaces between the "#" and the directive. The "#" is
considered "part" of the indent, even though the space comes after it. This
means the first indent level "looks" like one space, and following indents
Expand Down

0 comments on commit 8419236

Please sign in to comment.