Can't make require function work [SOLVED]

[mitzi65]

Hey people, I was trying to follow the tutorial about Simple Tiled Implementation in Lua Space and I got some errors regarding the require function.

The error message is the following:

Error Message

Untitled.png (35.2 KiB) Viewed 5714 times

And the only code I have wrote about it until now is that:

Code: Select all

local sti = require "sti"


function love.load()
  mapa = sti(teste.lua)
end


function love.update(dt)
  mapa:update(dt)
end


function love.draw()
  mapa:draw()
end

Does anybody know what is happening here?

[zorg]

Hi and welcome!

Did you download STI and put it into your project folder? It's not something that comes with löve itself.

[mitzi65]

Thanks for the welcome!

Yep,I did. The STI folder is on the same folder as main.lua. I noticed something weird about my problem too, the require function is not working when I am using it without Löve too (just as pure lua code). Could therebr a problem with my environment variables since I am using a chromebook with linux (using crouton for chroot)? (Maybe this problem should be made in a lua forum instead of a Löve one?)

[zorg]

You need to do:
local sti = require "sti/sti"
since the sti lua file is in the sti folder.

[Nixola]

You need to do:
local sti = require "sti/sti"
since the sti lua file is in the sti folder.

But that should be

Code: Select all

local sti = require "sti.sti"

Because require takes module names, not paths, so you use dots instead of slashes.

[mitzi65]

Oh, it worked! Thank you very much guys!

[raidho36]

since the sti lua file is in the sti folder.

But why? You can have an "init.lua" file in your module folder and calling "require ( modulefolder )" will call this file.

[zorg]

since the sti lua file is in the sti folder.

But why? You can have an "init.lua" file in your module folder and calling "require ( modulefolder )" will call this file.

don't ask me :V

[kikito]

But why? You can have an "init.lua" file in your module folder and calling "require ( modulefolder )" will call this file.

That's Lua's fault. The implementation of `init.lua` isn't complete. It works when the library is in certain places (like when installed by LuaRocks) but not when you are trying to use a local package. This happens consistenly in Lua 5.1, 5.2, 5.3 and LuaJIT, so I don't know whether I am getting crazy or there is some reason I don't understand.

[airstruck]

But why? You can have an "init.lua" file in your module folder and calling "require ( modulefolder )" will call this file.

That's Lua's fault. The implementation of `init.lua` isn't complete. It works when the library is in certain places (like when installed by LuaRocks) but not when you are trying to use a local package. This happens consistenly in Lua 5.1, 5.2, 5.3 and LuaJIT, so I don't know whether I am getting crazy or there is some reason I don't understand.

Are you running Debian? I had the impression this was something weird the Debian package maintainers did, and it didn't affect other platforms. I'm not sure it's Lua's fault; as far as I know they don't make any recommendation for what exactly should go in package.path (from LUA_PATH or luaconf.h), so it's just up to package maintainers to do something sensible.

It's weird that it happens in Love, though, because Love only uses the built-in loader (and package.path) as a fallback for its own loaders, which I thought fully supported the init.lua thing.