[SOLVED] Localizing a central function and calling via non-localized 'stub' function - is this even worth it?

Greetings, all :)/>

In the program I'm working on I have a function (drawCLI) that is called from both above and below so it can't be localized. Due to the structure of the program there is no practical way to place all the calling functions below drawCLI.

This being the only function I couldn't localize (and it being responsible for determining which elements to draw on screen) I added a 'stub' function below drawCLI (callDrawCLI) that allows me to localize drawCLI and only have the stub be non-localized. The only two functions calling the stub (callDrawCLI) are the two that are above drawCLI. This seems to work fine, so my questions are:

Is this worth it? Do I gain any advantage by doing this or is it just as well to leave drawCLI non-localized and ditch callDrawCLI()?

For me it makes no diference. But i am using the 1.5.2 minecraft version, wich may be outdated.

There's 2 ways to deal with this, personally i use my own local environment, saves me from having to deal with this at all. However, you could just define the variable that points to the function as local from the get go.

local test
local function iWillCallTest()
  test()
end
local test = function()
  print"test has been called"
end
iWillCallTest()

It dosen't matter what the variable points to at the time, only thing that matters is wether it's local or not. Your original solution would gain you nothing, as you'd still end up with a global function.

RoD, on 30 March 2014 - 06:34 PM said:

For me it makes no diference. But i am using the 1.5.2 minecraft version, wich may be outdated.

This goes for all versions of ComputerCraft because it's a Lua thing, regardless of what version.

CometWolf, on 30 March 2014 - 06:35 PM said:

There's 2 ways to deal with this, personally i use my own local environment, saves me from having to deal with this at all. However, you could just define the variable that points to the function as local from the get go.

local test
local function iWillCallTest()
  test()
end
local test = function()
  print"test has been called"
end
iWillCallTest()

It dosen't matter what the variable points to at the time, only thing that matters is wether it's local or not. Your original solution would gain you nothing, as you'd still end up with a global function.

RoD, on 30 March 2014 - 06:34 PM said:

For me it makes no diference. But i am using the 1.5.2 minecraft version, wich may be outdated.

This goes for all versions of ComputerCraft because it's a Lua thing, regardless of what version.

Right. Thanks :)/>

So, in my case I did this and it isn't working - I still run into 'attempt to call a nil'

local drawCLI

local function callDrawCLI()
  drawCLI()
end

... other functions ...

local drawCLI = function()
<drawCLI function here>

All calls still go directly to drawCLI() with the exception of the two functions that call callDrawCLI() - those two calls to callDrawCLI() still don't work. Unfortunately I don't see what I'm doing wrong and this syntax is unfamiliar to me.

Dog, on 30 March 2014 - 07:15 PM said:

So, in my case I did this and it isn't working - I still run into 'attempt to call a nil'

local drawCLI

local function callDrawCLI()
  drawCLI()
end

... other functions ...

local drawCLI = function()
<drawCLI function here>

All calls still go directly to drawCLI() with the exception of the two functions that call callDrawCLI() - those two calls to callDrawCLI() still don't work. Unfortunately I don't see what I'm doing wrong and this syntax is unfamiliar to me.

Why do you have a function just for calling other function?

You define it as a local variable once

local drawCLI

Then you redefine it as another local variable here

local drawCLI = function() --ditch the local here
<drawCLI function here>

CometWolf, on 30 March 2014 - 07:45 PM said:

You define it as a local variable once

local drawCLI

Then you redefine it as another local variable here

local drawCLI = function() --ditch the local here
<drawCLI function here>

Funny you should point out that exact thing - I suspected that, removed the 'local' in front of drawCLI = function() and it works - I just wasn't sure if that was the correct fix. As RoD pointed out, It looks like I don't even need the callDrawCLI() stub either.

Thanks, CometWolf and RoD!

CometWolf, on 30 March 2014 - 06:35 PM said:

However, you could just define the variable that points to the function as local from the get go.

The programming term for this is defining a forward declaration ;)/>

theoriginalbit, on 30 March 2014 - 11:35 PM said:

CometWolf, on 30 March 2014 - 06:35 PM said:

However, you could just define the variable that points to the function as local from the get go.

The programming term for this is defining a forward declaration ;)/>

Knowledge is power. Thanks for making me more powerful :)/>