Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "LDT/User Area/New Noteworthy/New Noteworthy 1.2"
(→New & Noteworthy 1.2) |
(→Add map/list support) |
||
Line 54: | Line 54: | ||
Using the <code>#list</code> or <code>#map</code> to type a variable or a field. | Using the <code>#list</code> or <code>#map</code> to type a variable or a field. | ||
− | See [[detailed documentation]]. | + | See [[Koneki/LDT/User_Area/Documentation_Language#List|detailed documentation]]. |
[[File:ScreenMap.png|center]] | [[File:ScreenMap.png|center]] | ||
+ | <center><small><em>Using<code>@map</code> on a type</em></small></center> | ||
+ | |||
[[File:ScreenList.png|center]] | [[File:ScreenList.png|center]] | ||
+ | <center><small><em>Using<code>@list</code> on a type</em></small></center> | ||
− | It is also possible to give a map or list | + | It is also possible to give a map or list behavior to a 'classic' type by using <code>@map</code> or <code>@list</code> keyword. |
[[File:ScreenInlineMap.png|center]] | [[File:ScreenInlineMap.png|center]] | ||
− | [[File: | + | <center><small><em>Using<code>map</code> in-line notation on a field</em></small></center> |
+ | |||
+ | [[File:ScreenInlineList.png|center]] | ||
+ | <center><small><em>Using<code>list</code> in-line notation on variable to describe function result</em></small></center> | ||
== Add __call support == | == Add __call support == |
Revision as of 10:20, 11 April 2014
Contents
New & Noteworthy 1.2
Add a library documentation to a project
since 1.2M1
By adding a .doclua
file describing an API in Lua Documentation Language in your project source path, you will have auto-completion for described API.
Debugging fix and enhancements
since 1.2M1
Here are some fixes to improve debugging experience and troubleshooting:
- Avoid a crash when evaluating an expression from the watch view.
- Use of interpreter's
LUA_PATH
ifLUA_PATH
environment variable is not available. - The debugger now logs his version and his connection status.
- Better error logging during remote debug sessions.
Extending a type
since 1.2M1
Using the @extend
keyword in a module
or type
will extend it with all fields and functions of given super type.
See detailed documentation.
Handling table field
since 1.2M1
On a variable documented with type #table, its fields are now displayed in the outline and available from auto-completion.
Rename
since 1.2M1
Pressing ALT+SHIFT+R
on a Lua variable enables to rename it and all its occurrences.
Integration of Metalua 0.7.2
since 1.2M1
LDT is now based on Metalua 0.7.2
.
Add map/list support
since 1.2M2
Using the #list
or #map
to type a variable or a field.
See detailed documentation.
@map
on a type@list
on a typeIt is also possible to give a map or list behavior to a 'classic' type by using @map
or @list
keyword.
map
in-line notation on a fieldlist
in-line notation on variable to describe function resultAdd __call support
since 1.2M2
Using the @callof
keyword in a function
to make a type 'callable'.
See detailed documentation.
Run interpreter directly automatically
since 1.2M2
Interprer is now linked to execution environment, this will allow LDT to run application with a compatible interpreter automatically.