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) |
m (Sbernard.sierrawireless.com moved page LDT/User Area/New Noteworthies/New Noteworthy 1.2 to LDT/User Area/New Noteworthy/New Noteworthy 1.2) |
||
(13 intermediate revisions by the same user not shown) | |||
Line 25: | Line 25: | ||
Using the <code>@extend</code> keyword in a <code>module</code> or <code>type</code> will extend it with all fields and functions of given super type. | Using the <code>@extend</code> keyword in a <code>module</code> or <code>type</code> will extend it with all fields and functions of given super type. | ||
− | See [[detailed documentation]]. | + | See [[LDT/User_Area/Documentation_Language#Type_comment_block| detailed documentation]]. |
[[File:ScreenExtendingType.png|center]] | [[File:ScreenExtendingType.png|center]] | ||
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 [[LDT/User_Area/Documentation_Language#List|detailed documentation]]. |
− | [[File: | + | [[File:ScreenInlineMap.png|center]] |
− | + | <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> | ||
− | [[File: | + | It is also possible to give a map or list behavior to a [[LDT/User_Area/Documentation_Language#Type|type]] by using <code>@map</code> or <code>@list</code> keywords. |
− | [[File: | + | |
+ | [[File:ScreenMap.png|center]] | ||
+ | <center><small><em>Using <code>@map</code> on a type</em></small></center> | ||
+ | |||
+ | [[File:ScreenList.png|center]] | ||
+ | <center><small><em>Using <code>@list</code> on a type</em></small></center> | ||
== Add __call support == | == Add __call support == | ||
Line 68: | Line 74: | ||
<small>since 1.2M2</small> | <small>since 1.2M2</small> | ||
− | Using the <code>@callof</code> keyword in a <code>function</code> to make a type 'callable'. | + | Using the <code>@callof</code> keyword in a <code>function</code> to make a type ''callable''. |
− | See [[detailed documentation]]. | + | See [[LDT/User_Area/Documentation_Language#Callof_sample|detailed documentation]]. |
− | [[File: | + | [[File:ScreenCallOf.png|center]] |
+ | <center><small><em><code>@callof</code> in action</em></small></center> | ||
− | == | + | == Choose interpreter automatically == |
<small>since 1.2M2</small> | <small>since 1.2M2</small> | ||
− | + | Interpreters are now linked to Execution Environments, this allows ''LDT'' to run applications with a compatible interpreter automatically. | |
+ | |||
+ | [[File:ScreenAddInterpreterEE.png|center]] | ||
+ | <center><small><em>Specify an Execution Environment which match your interpreter</em></small></center> | ||
− | |||
[[File:ScreenLaunchConf.png|center]] | [[File:ScreenLaunchConf.png|center]] | ||
+ | <center><small><em>You are warned when you launch an application with an inappropriate interpreter</em></small></center> | ||
+ | |||
+ | == LuaJIT Integration == | ||
+ | |||
+ | Now, when you add your <code>LuaJit</code> to LDT, you can inspect ''FFI CData''. | ||
+ | |||
+ | [[File:ScreenAddLuaJITInterpreter.png|center]] | ||
+ | <center><small><em>Adding a <code>LuaJit</code> interpreter to LDT</em></small></center> | ||
+ | |||
+ | [[File:ScreenLuaJITDebug.png|center]] | ||
+ | <center><small><em>How <code>Cdata</code> are displayed in debugger</em></small></center> |
Latest revision as of 10:53, 16 July 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
in-line notation on a fieldlist
in-line notation on variable to describe function resultIt is also possible to give a map or list behavior to a type by using @map
or @list
keywords.
@map
on a type@list
on a typeAdd __call support
since 1.2M2
Using the @callof
keyword in a function
to make a type callable.
See detailed documentation.
@callof
in actionChoose interpreter automatically
since 1.2M2
Interpreters are now linked to Execution Environments, this allows LDT to run applications with a compatible interpreter automatically.
LuaJIT Integration
Now, when you add your LuaJit
to LDT, you can inspect FFI CData.
LuaJit
interpreter to LDTCdata
are displayed in debugger