Throw a warning when list index is 0.

ID:1430790
 
Nov 26 2013, 1:31 pm
Applies to:DM Language
Status: Open
Issue hasn't been assigned a status value.
I often switch between languages, and often confuse myself if lists start at 0 or 1.

Because it will throw an array out of bounds error on zero, could it perhaps throw a warning at compile time?
Nov 27 2013, 9:38 am
This isn't something you'll typically know at compile-time. But when you are hard-coding an index, an error would make sense for anything that couldn't possibly be in bounds; a warning would not. I don't know how feasible this is.
Nov 27 2013, 2:28 pm
I think it's safe to assume that if the user types in something like
if (index[0] == 1)
    // do something

The compiler would warn the user that 0 (and below) is not an acceptable index. Not sure how possible this would be using iterative indices (i.e. for var/i = 0 to 9)
Nov 27 2013, 3:22 pm
In response to Makeii
Makeii wrote:
I think it's safe to assume that if the user types in something like
> if (index[0] == 1)
>     // do something
>

The compiler would warn the user that 0 (and below) is not an acceptable index. Not sure how possible this would be using iterative indices (i.e. for var/i = 0 to 9)

I agree.
Should it be a warning or an error?

I would think it would be considered a warning, due to it still technically compiles, it would just result in a runtime error.
Nov 27 2013, 5:18 pm
Might as well make it an error, but consistently it wouldn't do well, considering using variables and iterative values wouldn't be caught by the compiler. If you're not certain, you can always define something for yourself. Just throwing this out there:
#define LI 1

for (var/i = LI to LI+10)
    // stuff goes here