02-09-2023, 06:36 AM
I noticed this can be done:
FUNCTION MY.NEW.FUNCTION()
- code here
MY.NEW.FUNCTION = -1
END FUNCTION
I saw the use of periods as word separators in someone else's code. I decided to use this construct on a project I'm working on. However, as the code grows (up to 4000 lines now) the IDE sometime fails to color code the SUBS and FUNCTIONS that use periods in their names. I need to move the cursor by pressing the space bar (or simply typing) and the color coding will come back, but disappear later again.
Is the IDE doing this because it does not like the use of periods in the SUB and FUNCTION names? Should I not be using this construct? I find it to be much cleaner looking than MY_NEW_FUNCTION but can revert to this if need be.
I've not run into a problem with the code compiling or running in any way, just curious behavior from the IDE I've noticed, especially like I said as the code continues to grow and only affecting SUBs and FUNCTIONs with periods in their name.
FUNCTION MY.NEW.FUNCTION()
- code here
MY.NEW.FUNCTION = -1
END FUNCTION
I saw the use of periods as word separators in someone else's code. I decided to use this construct on a project I'm working on. However, as the code grows (up to 4000 lines now) the IDE sometime fails to color code the SUBS and FUNCTIONS that use periods in their names. I need to move the cursor by pressing the space bar (or simply typing) and the color coding will come back, but disappear later again.
Is the IDE doing this because it does not like the use of periods in the SUB and FUNCTION names? Should I not be using this construct? I find it to be much cleaner looking than MY_NEW_FUNCTION but can revert to this if need be.
I've not run into a problem with the code compiling or running in any way, just curious behavior from the IDE I've noticed, especially like I said as the code continues to grow and only affecting SUBs and FUNCTIONs with periods in their name.