love.filesystem is a MUST in threads

[cohadar]

If you do not

Code: Select all

require "love.filesystem"

in threads than user require calls do not work!

Does NOT work

Code: Select all

require "enet"
require "love.timer"
local tank = require "tank" -- fails with module not found

Works!!!?

Code: Select all

require "enet"
require "love.timer"
require "love.filesystem"
local tank = require "tank" -- it works

This is highly non-intuitive, and it is nowhere in documentation.
Either include love.filesystem by default in love threads or put some BIG RED LETTERS in thread doc.

[bartbes]

This is mentioned

When a Thread is started, it only loads the love.thread module. Every other module has to be loaded with require.

Though perhaps non-intuitive. It's also been changed for the next version.

This is highly non-intuitive, and it is nowhere in documentation.
Either include love.filesystem by default in love threads or put some BIG RED LETTERS in thread doc.

Then isn't it wonderful that having a forum account not only allows you to complain on the forums, but also to edit the wiki?

[cohadar]

What I don't understand is why user require paths in threads don't work if love.filesystem is not included.
I "see" how it can be related, but still, it is extremely non-intuitive.

I updated the thread wiki with a new notice.

[T-Bone]

I'm guessing PhysFS isn't used at all unless you load love.filesystem. No PhysFS, no way to locate files.

[bobbyjones]

I think its because love.filesystem prepends the require path

[Guard13007]

Though perhaps non-intuitive. It's also been changed for the next version.

Could you / someone who knows explain how it is being changed please?

[bartbes]

Right, so as bobbyjones kind of gets, love.filesystem installs a loader for require when it is required. (So it doesn't prepend to the path.)

As for what changed, in 0.10.0 threads will require both love.thread and love.filesystem on launch.