Get caller environment

I want to achieve this without arguments, is this possible?
Example:

print(APIname) --> nil
API.name('A text')
print(APIname) --> 'A text'

or

print(API) --> nil
using('API')
print(API) --> table: xxxxx

So I could do this:

tEnv.APIname = sText -- tEnv is the Environment of the caller, sText is the argument

or

tEnv[sKey] = tAPIs[sKey] -- tEnv is the Environment of the caller, sKey is the argument, tAPIs are internal APIs

I need it also for identification: 'Who call me?
–> You get this
–> And you get this2'

You want the API to know it's own name? Or do you want the environment of the caller? The former seems to fit with your example; the latter does not.

KingofGamesYami, on 01 August 2016 - 05:46 PM said:

You want the API to know it's own name? Or do you want the environment of the caller? The former seems to fit with your example; the latter does not.

I updated the post to specify my goal.

You can kind of do this using getfenv( nStackLevel ). For example,

local function something()
  print( getfenv( 1 ).i )
end
something() --# nil
i = 1
something() --# 1

As for "who called it", you can't know that. The information literally isn't there.

KingofGamesYami, on 01 August 2016 - 07:36 PM said:

You can kind of do this using getfenv( nStackLevel ). For example,

local function something()
  print( getfenv( 1 ).i )
end
something() --# nil
i = 1
something() --# 1

As for "who called it", you can't know that. The information literally isn't there.

I think, I have to change the working wise of my program…

KingofGamesYami, on 01 August 2016 - 07:36 PM said:

As for "who called it", you can't know that. The information literally isn't there.

Luckily a lot of the built in functions that run files set a name for the file when it is loadstringed, and that is fairly easy to obtain. If I understand correctly he should be able to get the who called me information by pcalling error with a certain level to error at. He would then have to find the information he wants out of the error message. I would give a example, but I don't have much time right now.

valithor, on 01 August 2016 - 10:54 PM said:

KingofGamesYami, on 01 August 2016 - 07:36 PM said:

As for "who called it", you can't know that. The information literally isn't there.

Luckily a lot of the built in functions that run files set a name for the file when it is loadstringed, and that is fairly easy to obtain. If I understand correctly he should be able to get the who called me information by pcalling error with a certain level to error at. He would then have to find the information he wants out of the error message. I would give a example, but I don't have much time right now.

I think that would be bad code, but the solution with the top-level is the best one.