I gave a .love file.T-Bone wrote:Pics or it didn't happen
Code: Select all
a = {b = {}}
c = {b = a.b}
c.b.blah = true
print(a.b.blah) -- prints true
Code: Select all
function CloneTable(tab)
rT = {}
for _,v in pairs(tab) do
rT[_] = v
end
return rT
end
Depends.Trappingnoobs wrote:Would I need to make it recursive for tables inside the table?
Yes but some are identical throughout classes, and, as you've probably seen, take up like 70 lines of space in every class, I'd rather inherit.Robin wrote:Depends.Trappingnoobs wrote:Would I need to make it recursive for tables inside the table?
Note that for classes, it would be better to make new tables in the constructor than to clone them.
Code: Select all
local function CloneTable(tab)
local rT = {} --returnTable
for key,val in pairs(tab) do
if type(val) == "table" then
rT[key] = CloneTable(val)
else
rT[key] = val
end
end
return rT
end
Dude. Subclassing.Trappingnoobs wrote:Yes but some are identical throughout classes, and, as you've probably seen, take up like 70 lines of space in every class, I'd rather inherit.
Be careful with that attitude. That never works.Trappingnoobs wrote:I came up with this. To be honest; it's got to the point I've forgotten what most of it's there for/what it does, but it works, so I hopefully won't need to ever again edit it.
Yes, that works, but there might be times were it will not. For example:Trappingnoobs wrote:Code: Select all
local function CloneTable(tab)
Code: Select all
a = {}
a.a = a
CloneTable(a) -- oops!That's what I'm doing... Inheriting is the same as subclassing; everything from class A is put into class B if class B asks for it.Robin wrote:Dude. Subclassing.Trappingnoobs wrote:Yes but some are identical throughout classes, and, as you've probably seen, take up like 70 lines of space in every class, I'd rather inherit.
Yeah; it's failed me a lot. If necessary I'll just force myself to repeatedly read it over and over until I find out why x problem is occuring. Hopefully it won't get to that.Robin wrote:Be careful with that attitude. That never works.Trappingnoobs wrote:I came up with this. To be honest; it's got to the point I've forgotten what most of it's there for/what it does, but it works, so I hopefully won't need to ever again edit it.
Any way I can protect against that? Although, if somone did that, wouldn't they have purpousefully wanted something bad to happen?Robin wrote:Yes, that works, but there might be times were it will not. For example:Trappingnoobs wrote:Code: Select all
local function CloneTable(tab)
Code: Select all
a = {} a.a = a CloneTable(a) -- oops!
Code: Select all
if val ~= args then
clone logic
else
args.key = args
end
Pics are still a good idea. Also, you should probably update the first post as it clearly states that there is no .love file. In red letters.Trappingnoobs wrote:I gave a .love file.T-Bone wrote:Pics or it didn't happen
That's red? I thought it was brown. T.tT-Bone wrote:Pics are still a good idea. Also, you should probably update the first post as it clearly states that there is no .love file. In red letters.Trappingnoobs wrote:I gave a .love file.T-Bone wrote:Pics or it didn't happen
Yes, you are.Trappingnoobs wrote:That's what I'm doing... Inheriting is the same as subclassing; everything from class A is put into class B if class B asks for it.[/quote
Not what I meant. You could make a class called Object which implements the event system. Then you let all the other classes subclass Object and voilà: one free event system.No. There are a lot of legitimate reasons for doing things like that. It would be better to not need to copy anything, by calling the constructors of the superclasses.Trappingnoobs wrote:Any way I can protect against that? Although, if somone did that, wouldn't they have purpousefully wanted something bad to happen?Trappingnoobs wrote:I'm probably wrong.