luac question

[slushe]

After compiling a lua script with luac--what does the file need to be named so that love can read it?

[bartbes]

Nothing different, if it's your main.lua, name it main.lua. I have to say, I can't advice you to use luac.

[slushe]

I see. Figured it might be a way to protect source.

[thelinx]

Will only work on the OS and architecture you compiled it on. So if you compiled it in 32-bit Windows, it wouldn't work on Linux, OS X, and not even 64-bit Windows.

[Jasoco]

I guess hypothetically you could compile a version on every OS then release each one as a finished launchable product separately for each platform.

[bartbes]

It should be somewhat compatible around platforms, just not versions, well lua bytecode is kind of a grey area, I don't think anyone knows exactly where it does and does not run.

[Robin]

Bytecode for "source code protection" is right up there with black cats and those little crosses.

[pekka]

The luac manual page says this.

The binary files created by luac are portable only among architectures
with the same word size and byte order.

[Felipe Budinich]

Bytecode for "source code protection" is right up there with black cats and those little crosses.

Be careful or you could get sued for religious intolerance, some people really believe that Santa is real.

But in all seriousness it could deter my mother from looking at the source code.

[Sergeant]

Will only work on the OS and architecture you compiled it on. So if you compiled it in 32-bit Windows, it wouldn't work on Linux, OS X, and not even 64-bit Windows.

Only partially correct.

The binary files created by luac are portable to all architectures with the same word size. This means that binary files created on a 32-bit platform (such as Intel) can be read without change in another 32-bit platform (such as Sparc), even if the byte order (``endianess'') is different. On the other hand, binary files created on a 16-bit platform cannot be read in a 32-bit platform.

This was taken from the 4.0 Lua manual, but the same holds true for 5.1.