Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EDT:EGL Language Statements"
(New page: Please see the parent of this page, EDT:EGL_Language. == Statements (Table 5) == {| width="400" cellspacing="1" cellpadding="1" border="1" style="" |- | bgcolor="#999999" align="cen...) |
|||
| Line 55: | Line 55: | ||
| bgcolor="#cccccc" | ''Label'' | | bgcolor="#cccccc" | ''Label'' | ||
| <br> | | <br> | ||
| − | | <br> | + | | done<br> |
| <br> | | <br> | ||
| <br> | | <br> | ||
| Line 73: | Line 73: | ||
| bgcolor="#cccccc" | ''Try'' | | bgcolor="#cccccc" | ''Try'' | ||
| <br> | | <br> | ||
| − | | <br> | + | | done<br> |
| <br> | | <br> | ||
| <br> | | <br> | ||
| + | |- | ||
| + | | bgcolor="#cccccc" | ''Catch'' | ||
| + | | | ||
| + | | done | ||
| + | | | ||
| + | | | ||
|- | |- | ||
| bgcolor="#cccccc" | ''Case'' | | bgcolor="#cccccc" | ''Case'' | ||
| Line 85: | Line 91: | ||
| bgcolor="#cccccc" | ''If'' | | bgcolor="#cccccc" | ''If'' | ||
| <br> | | <br> | ||
| − | | <br> | + | | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=352028 If support]<br> |
| <br> | | <br> | ||
| <br> | | <br> | ||
| Line 109: | Line 115: | ||
| bgcolor="#cccccc" | ''Exit'' | | bgcolor="#cccccc" | ''Exit'' | ||
| <br> | | <br> | ||
| − | | <br> | + | | done<br> |
| <br> | | <br> | ||
| <br> | | <br> | ||
| Line 121: | Line 127: | ||
| bgcolor="#cccccc" | ''Empty statement (a semicolon)'' | | bgcolor="#cccccc" | ''Empty statement (a semicolon)'' | ||
| <br> | | <br> | ||
| − | | <br> | + | | done<br> |
| <br> | | <br> | ||
| <br> | | <br> | ||
| Line 232: | Line 238: | ||
#EDT won't support every variation of RBD's move statement. There will be support for '''move byName''', '''move for''', and '''move for all'''. A move statement without one of the additional keywords is only allowed between two references, and it results in the target being assigned a copy of the source's value. If/when we support structured records, we might not support '''move byName''' on them because of the complex (unclean) design. | #EDT won't support every variation of RBD's move statement. There will be support for '''move byName''', '''move for''', and '''move for all'''. A move statement without one of the additional keywords is only allowed between two references, and it results in the target being assigned a copy of the source's value. If/when we support structured records, we might not support '''move byName''' on them because of the complex (unclean) design. | ||
#EDT doesn't have called programs, but services and native programs can be called. | #EDT doesn't have called programs, but services and native programs can be called. | ||
| − | #<span style="background: | + | #<span style="background: none repeat scroll 0% 0% rgb(255, 165, 0);">EDT's foreach statement will support iterating over an array.</span> |
#Support for these statements is tentative, pending the design for JPA in EDT. | #Support for these statements is tentative, pending the design for JPA in EDT. | ||
| − | #New syntax will allow setting annotations on declarations without the use of curly braces. In RBD we usually do '''<span style="font-family: times, 'Times New Roman', serif;">x int {myAnnotation = 3};</span>''' but another way to do the same thing is '''<span style="font-family: times, 'Times New Roman', serif;">x int {@myAnnotation{3}};</span>'''. In EDT we will allow that to be outside of curly braces and before the declaration, for example '''<span style="font-family: times, 'Times New Roman', serif;">@myAnnotation{3} x int;</span>'''. | + | #New syntax will allow setting annotations on declarations without the use of curly braces. In RBD we usually do '''<span style="font-family: times,'Times New Roman',serif;">x int {myAnnotation = 3};</span>''' but another way to do the same thing is '''<span style="font-family: times,'Times New Roman',serif;">x int {@myAnnotation{3}};</span>'''. In EDT we will allow that to be outside of curly braces and before the declaration, for example '''<span style="font-family: times,'Times New Roman',serif;">@myAnnotation{3} x int;</span>'''. |
Revision as of 16:39, 13 July 2011
Please see the parent of this page, EDT:EGL_Language.
Statements (Table 5)
| Statements | Core | JavaScript | Java | Debug |
| Variable declaration5 | |
|
|
|
| Const declaration | |
|
|
|
| Assignment | |
|
|
|
| Move1 | |
|
|
|
| Return | |
|
|
|
| Function invocation | |
|
|
|
| Call2 | |
|
|
|
| Label | |
done |
|
|
| Transfer | |
N/S |
|
|
| Throw | |
|
|
|
| Try | |
done |
|
|
| Catch | done | |||
| Case | |
|
|
|
| If | |
If support |
|
|
| While | |
|
|
|
| For | |
|
|
|
| Foreach3 | |
|
|
|
| Exit | |
done |
|
|
| Continue | |
|
|
|
| Empty statement (a semicolon) | |
done |
|
|
| Add | |
N/S |
|
|
| Close | |
N/S |
|
|
| Delete | |
N/S |
|
|
| Get | |
N/S |
|
|
| Replace | |
N/S |
|
|
| Execute4 | |
N/S |
|
|
| Prepare4 | |
N/S |
|
|
| Open4 | |
N/S |
|
|
| FreeSQL4 | |
N/S |
|
|
| Goto |
|
N/S | N/S | N/S |
| Set |
|
N/S | N/S | N/S |
| Converse |
|
N/S | N/S | N/S |
| Display |
|
N/S | N/S | N/S |
| Print |
|
N/S | N/S | N/S |
| Forward |
|
N/S | N/S | N/S |
| Show |
|
N/S | N/S | N/S |
| OpenUI |
|
N/S | N/S | N/S |
Notes on Table 5
- EDT won't support every variation of RBD's move statement. There will be support for move byName, move for, and move for all. A move statement without one of the additional keywords is only allowed between two references, and it results in the target being assigned a copy of the source's value. If/when we support structured records, we might not support move byName on them because of the complex (unclean) design.
- EDT doesn't have called programs, but services and native programs can be called.
- EDT's foreach statement will support iterating over an array.
- Support for these statements is tentative, pending the design for JPA in EDT.
- New syntax will allow setting annotations on declarations without the use of curly braces. In RBD we usually do x int {myAnnotation = 3}; but another way to do the same thing is x int {@myAnnotation{3}};. In EDT we will allow that to be outside of curly braces and before the declaration, for example @myAnnotation{3} x int;.