Closed Kroc closed 6 years ago
I have some reservations about this simply due to the fact that I write comments like this:
' This is a comment
' about the use of the
' foo type in general.
TYPE foo
' This is a comment
' about how fieldA
' is used.
fieldA AS STRING * 10
' Same idea for fieldB.
fieldB AS INTEGER
END TYPE
In addition, it differs from the formatting of comments inside other blocks like IF...END IF
and FOR...NEXT
. An exception for TYPE...END TYPE
blocks may or may not be feasible, but even if it is, I would rather QB64 allow me to comment as I like. I can always indent/unindent the comment as necessary.
You misunderstand -- this is how QB64 formats your given text:
The first set of comments inside a TYPE
definition are always un-indented, when they should really be indented.
I'm on it. Thanks for reporting.
The development build now contains a fix for the misalignment of the first comment lines of a TYPE block. The issue also affected DECLARE LIBRARY blocks and has also been fixed on that front.
Comments placed in the first lines inside a
TYPE
block should be indented to match the definitions. See picture below for example: