Using a table to remember variables and get those variables by calling the number in the sequence of which they where created.

This code doesn't seem to remember the variables like the title says, it only seems to remember the latest one not the older ones
THE APPLICATION CODE[VERY messy]

Spoiler

term.clear() term.setCursorPos(1,1)
isx="1"
--game: tower defence
--FUNCTIONS
fs.delete("TDGchache") ;
function write(text)
term.write(text)
end
function newTower( x, y )
term.setCursorPos(x,y)
write("T")
--TABLES and USEABLE version
towsx = {}
towsx[isx] = x
towsy = {}
towsy[isx] = y
print(isx)
isx= isx + 1
end

--
--[[towx.."isx" = ""..x..""
towy.."isx" = ""..y..""
isx = "isx + 1"--]]
--[[addt = fs.open("TDGchache", "a") ;
addt.writeLine(""..x.." "..y.."")
addt.close()--]]
menuClicks()
end
function placeTower()
_, button, o, t = os.pullEvent ("mouse_click") ;
if t ==10 then
placeTower()
elseif t ==11 then
placeTower()
elseif t ==12 then
placeTower()
elseif t ==19 then
placeTower()
elseif t ==18 then
placeTower()



else
newTower( o, t ) ;
end
end
function drawPath()
term.setCursorPos(1,10)
lineE = "-----------------------------------------------------"
term.write(""..lineE.."") ;
term.setCursorPos(1, 12)
term.write(""..lineE.."") ;
drawMenu()
end
function drawMenu()
term.setCursorPos(1,18)
term.write(""..lineE.."") ;
term.setCursorPos(1,19)
term.write("Buy tower Sell Tower") ; --9

end
function menuClicks()
_2, button2, x2, y2 = os.pullEvent ("mouse_click") ;
if y2 ==19 and x2 <9 then
placeTower()
elseif y2 ==19 and x2 >9 and x2 <19 then
print("hi") ;
else
menuClicks()
end
end
--[[Notes:
Need a menu bar function w/ "add a tower"
--]]


drawPath()
placeTower()

please, indent your code

I'm not quite getting what your problem is. could you explain a little bit more :P/>/>

Ehm, one thing I can make of this is that you're using the variable isx as a number, but declared it as a string ("1").

Doyle3694, on 31 October 2012 - 12:21 AM said:

please, indent your code

I never understood indenting. It's a waste of time. I find it really hard to read indented code, too.
EDIT:
I just devoloped my own version of indenting. It's easy to read yet it really easy for me to do.

sIdEkIcK_, on 31 October 2012 - 12:43 AM said:

I'm not quite getting what your problem is. could you explain a little bit more :P/>/>

When I write more to my table in the code, it erases the old data in the table rather than adding to it.

Orwell, on 31 October 2012 - 12:46 AM said:

Ehm, one thing I can make of this is that you're using the variable isx as a number, but declared it as a string ("1").

LUA finds what kind of thingy a variable is automatically.

Hithere__, on 31 October 2012 - 12:50 AM said:

Doyle3694, on 31 October 2012 - 12:21 AM said:

please, indent your code

I never understood indenting. It's a waste of time. I find it really hard to read indented code, too.

sIdEkIcK_, on 31 October 2012 - 12:43 AM said:

I'm not quite getting what your problem is. could you explain a little bit more :P/>/>

When I write more to my table in the code, it erases the old data in the table rather than adding to it.

Orwell, on 31 October 2012 - 12:46 AM said:

Ehm, one thing I can make of this is that you're using the variable isx as a number, but declared it as a string ("1").

LUA finds what kind of thingy a variable is automatically.

Indenting is valuable for seeing the scope of various blocks as well as the flow of the logic in the program. It also makes it significantly easier for most people to read the code.

When you write new data to a table at an index you've already written to, it will of course overwrite the old data at that index. This is normal behavior. If you're misusing the table, expect to get undesired results.

Lua treats table[1] and table["1"] as different indices, for good reason. If you index it as a string once and as a number another time, don't expect it to work.

You need to not be so snippy and know-it-all with those trying to help you, especially when they're right.

Lyqyd, on 31 October 2012 - 12:56 AM said:

Hithere__, on 31 October 2012 - 12:50 AM said:

Doyle3694, on 31 October 2012 - 12:21 AM said:

please, indent your code

I never understood indenting. It's a waste of time. I find it really hard to read indented code, too.

sIdEkIcK_, on 31 October 2012 - 12:43 AM said:

I'm not quite getting what your problem is. could you explain a little bit more :P/>/>

When I write more to my table in the code, it erases the old data in the table rather than adding to it.

Orwell, on 31 October 2012 - 12:46 AM said:

Ehm, one thing I can make of this is that you're using the variable isx as a number, but declared it as a string ("1").

LUA finds what kind of thingy a variable is automatically.

Indenting is valuable for seeing the scope of various blocks as well as the flow of the logic in the program. It also makes it significantly easier for most people to read the code.

When you write new data to a table at an index you've already written to, it will of course overwrite the old data at that index. This is normal behavior. If you're misusing the table, expect to get undesired results.

Lua treats table[1] and table["1"] as different indices, for good reason. If you index it as a string once and as a number another time, don't expect it to work.

You need to not be so snippy and know-it-all with those trying to help you, especially when they're right.

Thanks
To the bold text
I get like this if it's either late at night and I've gotten crudloads of errors in a program or if it's just REALLY late at night

Early in the morning for me :P/>/>

Lyqyd, on 31 October 2012 - 12:56 AM said:

Hithere__, on 31 October 2012 - 12:50 AM said:

Doyle3694, on 31 October 2012 - 12:21 AM said:

please, indent your code

I never understood indenting. It's a waste of time. I find it really hard to read indented code, too.

sIdEkIcK_, on 31 October 2012 - 12:43 AM said:

I'm not quite getting what your problem is. could you explain a little bit more :P/>/>

When I write more to my table in the code, it erases the old data in the table rather than adding to it.

Orwell, on 31 October 2012 - 12:46 AM said:

Ehm, one thing I can make of this is that you're using the variable isx as a number, but declared it as a string ("1").

LUA finds what kind of thingy a variable is automatically.

Indenting is valuable for seeing the scope of various blocks as well as the flow of the logic in the program. It also makes it significantly easier for most people to read the code.

When you write new data to a table at an index you've already written to, it will of course overwrite the old data at that index. This is normal behavior. If you're misusing the table, expect to get undesired results.

Lua treats table[1] and table["1"] as different indices, for good reason. If you index it as a string once and as a number another time, don't expect it to work.

You need to not be so snippy and know-it-all with those trying to help you, especially when they're right.

Thanks for try to help, but I tried it and it didn't work. Do I need to run another command or is this just not possible?

Hmm? What'd you try that didn't work? I'm not sure what you mean.

I need something to keep track of the number of the table[the key] and add new stuff to the table WITHOUT erasing the old stuff.

Hithere__, on 31 October 2012 - 09:55 PM said:

I need something to keep track of the number of the table[the key] and add new stuff to the table WITHOUT erasing the old stuff.

table.insert(table,"text")

Doesn't delete what is already in the table.

You want a normal queue structure. Just keep expanding the table sequentially. Insert works, but is slower.