Allow undefined/null value for INPUT_AUTO and OUTPUT_AUTO about ev3dev-lang HOT 5 CLOSED

Are you saying that the constants *_AUTO should have the value of null? Or are you saying that blank strings should not be allowed (or only processed if the falue isn't falsey)?

from ev3dev-lang.

I'm not really sure... :-)

I guess I'm saying that an implementor should be allowed to use null as the value of the *_AUTO constants, and iff the implementor chose to do that not be required to check for the empty string in the constructors. For some languages using an empty string still would make sense, so I'm not arguing against allowing that too.

It would probably be harder to explain in the table though.

As I'm not sure exactly what problem the specification is trying to solve, maybe this isn't in line with your ambitions. But seen as a lowest common denominator I hope that the spec won't push implementors away from good practice and idiomatic use of their language.

from ev3dev-lang.

IMHO the specification should only enforce the existence of the AUTO port constants, and should allow default constructors without specifying a port (if possible in the language). Whether the AUTO constants are implemented as null or empty string is language / implementation dependent.

from ev3dev-lang.

Good idea; I think that will be better than specifying the value as we do now. I'll make that adjustment shortly.

from ev3dev-lang.

This has been added to the specification.

from ev3dev-lang.