|
|
|
Re: install ldt [message #873513 is a reply to message #873509] |
Fri, 18 May 2012 12:09 |
uiy uiy Messages: 56 Registered: May 2012 |
Member |
|
|
Yeah, I've played around with it and if I remember correctly it didn't do it on my first test. When I didn't hard code the paths. I'll play around with it some and see if I can get something to work.
Update:
When I try local or replace path and use the path to the files I get the new source result. When I use module I get no stepping(just runs through the code).
Is it possible, due to windows, that the same strings are being seen as different? The ldt source window shows a path using forward slashes while windows uses black slashes. (i.e., it's opening the exact same file for no reason so it obviously thinks it's different)
[Updated on: Fri, 18 May 2012 12:16] Report message to a moderator
|
|
|
Re: install ldt [message #873658 is a reply to message #873348] |
Fri, 18 May 2012 19:22 |
|
Wang Zhen,
An Execution Environment is a ZIP file that contains the definition of the Lua environment you are developing against (be it a standard Lua VM, the World of Warcraft environment, etc.).
We are a bit late in delivering the documentation of this format, but in a nutshell it is a bunch of Lua files documentend using LDT documentation format + a rockspec that gives this Execution Environment a name, a version, ... Additionally, the Execution Environment archive can contain pre-generated HTML documentation.
For your convenience, you can find the Lua 5.1.4 Execution Environment here.
My blog: http://blog.benjamin-cabe.com
|
|
|
Powered by
FUDForum. Page generated in 0.03524 seconds