Julia: Export commands do not give errors when you miss commas

[logankilpatrick]

If you do

include("file.jl")
export
   test
   test1

it doesn't give an error but it doesn't export the 2nd function. This seems weird to me.

[yuyichao]

Thus is valid syntax and this kind of issue is the best for a linter.

[logankilpatrick]

Why is this valid syntax? That’s my point; Maybe it shouldn’t be valid.

[yuyichao]

It's valid syntax because test1 is valid syntax. I can't check right now but I think if you put everything on the same line it will be an error.

[ararslan]

Yichao is right. You can't even finish a module definition at the REPL with this syntax before encountering an error:

julia> module M
       export a b
ERROR: syntax: extra token "b" after end of expression
Stacktrace:
 [1] top-level scope at REPL[6]:0

[logankilpatrick]

right but

module M
       export 
          a 
          b

is valid

[logankilpatrick]

even though b is not actually exported

[StefanKarpinski]

Right, you're evaluating b on a line by itself. Not sure there's anything we can do about this.

[logankilpatrick]

I am just making things up that may not be possible but why not just do something under the hood to evaluate the exports on the same line

[logankilpatrick]

julia> module M
       export a,b
       end
Main.M

julia> module M
       export a b
       end
ERROR: syntax: extra token "b" after end of expression
Stacktrace:
 [1] top-level scope at REPL[2]:0

[logankilpatrick]

that way if there's a missing comma it errors out rather than acts as if all is well

[StefanKarpinski]

export a
b

already means something: it means export a; b — it exports a and then evaluates b.

[logankilpatrick]

Got it. Just wanted to voice my thought. Thanks for the feedback/time!