So
Gives me
However
Gives me
Note the lack of the blank line 6.
I'm unsure if this is feasible to be fixed, and it isn't precisely project breaking, just inconsistent behavior. Feel free to ignore this until you have a few minutes of free time.
ID:1984313
 Nov 17 2015, 9:28 am
|
|||||||||||||
| |||||||||||||
I use a .dm containing a bunch of #warn-s for reminders, and I'm unsure if this is the case with all # uses, but with #warn you need to add an extra line at the end or else it doesn't properly know where the line is.
So Gives me However Gives me Note the lack of the blank line 6. I'm unsure if this is feasible to be fixed, and it isn't precisely project breaking, just inconsistent behavior. Feel free to ignore this until you have a few minutes of free time. | |||||||||||||
|
Nov 17 2015, 10:14 am
|
|
Audeuro
 |
For what it's worth, I'm pretty sure this is the case for /any/ compiler message (errors or otherwise) generated from the last line of a file. This has been the case for...many years.
|
AFAIK this is a known issue. If you're working with files in BYOND it's in your best interest to leave a newline at the end of a code file to prevent undesired behavior like this.
It's still something that I feel should be addressed, but I fear it'll take too much time and/or is too deep in the compiler code. | |
Audeuro wrote:
For what it's worth, I'm pretty sure this is the case for /any/ compiler message (errors or otherwise) generated from the last line of a file. This has been the case for...many years. Good to know, Usdpound. I couldn't think of a case to test it with, but this does mean a few ifdefs in my code will produce undesired resulted. | |