[SOLVED] Require/local/global doubt

[coffee]

Hi, still dealing with basic Lua mistakes. Can you help me understand this please?

So I have a main.lua

Code: Select all

require ("_lib/colors.lua")

function setColor(c,a)
   love.graphics.setColor(c[1], c[2], c[3], a)
end

and a colors.lua

Code: Select all

color.black = { 0,0,0 } 

if call in main.lua

Code: Select all

setColor( color.black )

give me a "attempt to index local "c" (nil value)
but all works fine if I add

Code: Select all

color.black = { 0,0,0 } 

to main.lua

This is a local/global problem right? What I'm doing wrong?

[GijsB]

Code: Select all

require ("_lib/colors.lua")

are you sure that's the right path?

[coffee]

Code: Select all

require ("_lib/colors.lua")

are you sure that's the right path?

Sure, it would give me a "not found error" instead. I also tested that.

[coffee]

SOLVED!
I was doing

Code: Select all

color = {}

after the require and not before!
Stupid newbie!

[tentus]

Quick tip. You have this:

Code: Select all

require ("_lib/colors.lua")

You should get in the habit of doing it this way:

Code: Select all

require "_lib/colors"

The reason is that require() is going to be realigned to the Lua standard in Love 0.8.0, so require() won't support paths that include file extensions. I took out the parenthesis since they're unneeded, but that part's just an aesthetic change.

[osgeld]

heh funny, I have been doing lua systems so long I never even tried to pass an extension to love

[bartbes]

[/code]
You should get in the habit of doing it this way:

Code: Select all

require "_lib/colors"

But not. Proper syntax is:

Code: Select all

require("_lib.colors")

(and I like my parentheses, lisp represent)

[coffee]

Thanks for the tip. There is only left few days till 0.8 is released and I didn't yet saw yet a OSX test binary that worked and run in my machine. So I probably will not use 0.8 so soon.

But I'm a bit shocked and I'm sure if understanding well. That means that I must then start use files without lua extension in requires? Does that not complicate OS/editor recognition of Lua files?

BTW I just use a named "_lib" dir/folder just only to be "placed" in Finder on top of other "normal" dirs (gfx, sfx, fnt...)

[Robin]

But I'm a bit shocked and I'm sure if understanding well. That means that I must then start use files without lua extension in requires? Does that not complicate OS/editor recognition of Lua files?

What? Why?

Unless you think that the actual files would have no extension, which is not the case.

To require a file called "foo.lua" in the "lib" folder, one does:

Code: Select all

require "lib.foo"

That's consistent with how Lua normally works.

[coffee]

To require a file called "foo.lua" in the "lib" folder, one does:

Code: Select all

require "lib.foo"

That's consistent with how Lua normally works.

Ah with that example I see clearly now. Thank you for clarify Robin. Ok, will take a bit to think that way about external files (even be the Lua way) but I understand now the new mechanics.