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 Part Types"
(→Part Types (Table 1)) |
|||
Line 33: | Line 33: | ||
| <br>done | | <br>done | ||
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=352045 JS:Record]<br> | | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=352045 JS:Record]<br> | ||
− | | <br> | + | | done<br> |
|- | |- | ||
| bgcolor="#cccccc" | ''Structured Record<sup>6</sup>''<br> | | bgcolor="#cccccc" | ''Structured Record<sup>6</sup>''<br> | ||
Line 43: | Line 43: | ||
| <br>done | | <br>done | ||
| [https://bugs.eclipse.org/bugs/show_bug.cgi?id=352035 JS:ExternalType]<br> | | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=352035 JS:ExternalType]<br> | ||
− | | <br> | + | | done<br> |
|- | |- | ||
| bgcolor="#cccccc" | ''Handler''<br> | | bgcolor="#cccccc" | ''Handler''<br> | ||
Line 53: | Line 53: | ||
| <br>done | | <br>done | ||
| done<br> | | done<br> | ||
− | | <br> | + | | done<br> |
|- | |- | ||
| bgcolor="#cccccc" | ''Service''<br> | | bgcolor="#cccccc" | ''Service''<br> | ||
Line 73: | Line 73: | ||
| <br>done | | <br>done | ||
| N/S<br> | | N/S<br> | ||
− | | <br> | + | | done<br> |
|- | |- | ||
| bgcolor="#cccccc" | ''Array''<br> | | bgcolor="#cccccc" | ''Array''<br> | ||
| <br>done | | <br>done | ||
| <br> | | <br> | ||
− | | <br> | + | | done<br> |
|- | |- | ||
| bgcolor="#cccccc" | ''Deployment Descriptor''<sup>7</sup><br> | | bgcolor="#cccccc" | ''Deployment Descriptor''<sup>7</sup><br> |
Revision as of 13:43, 20 July 2011
Please see the parent of this page, EDT:EGL Language.
Part Types (Table 1)
Part Types | Core | JavaScript | Java |
DataItem1 | 2d |
JS: DataItem |
|
Function2, 5 | done |
JS: Function overloading |
|
Top-level function2, 5 | done |
|
|
Delegate2 | done |
JS:Delegates |
|
Record6 |
done |
JS:Record |
done |
Structured Record6 |
5d |
N/S | N/S |
ExternalType |
done |
JS:ExternalType |
done |
Handler |
1d |
JS:Handler |
|
Library |
done |
done |
done |
Service |
1d |
|
|
Interface3 |
done |
|
|
Enumeration |
1d |
JS: Enumeration |
|
Program4 |
done |
N/S |
done |
Array |
done |
|
done |
Deployment Descriptor7 |
|
RUIhandlers |
REST RPC SOAP |
DataTable |
done |
N/S | N/S |
Form |
1d |
N/S | N/S |
FormGroup |
2d |
N/S | N/S |
Notes on Table 1
- In RBD a DataItem can only be used for primitive types. In EDT it can be used for any type.
- See also Table 2: Function Parameters.
- Interfaces can be implemented by services and handlers (every kind of "logic part" which can be instantiated).
- There are no called programs in EDT. Use libraries for "local calls" and services for "remote calls".
- We intend to support function overloading in all implementations, even JavaScript.
- Records (including structured records) are value types, so record variables may be declared with a question mark following the name of the type to indicate that they're nullable. Nullability means that a variable may really be null. It's not an "I'm null" flag like in RBD. A NullValueException will be thrown if you try to access a field or function of a null variable, even a record. A NullValueException will be thrown if a null variable is an operand to a math operator, an array access, a substring access, a comparison, or a bitwise operator. The string concatenation operators will work the same as in RBD with respect to nulls. :: treats null as the empty string, and ?: results in null if either operand is null. A question mark won't be allowed on the second operand of the AS and ISA operators (the name of the type).
- The deployment descriptor will ONLY be used for deployment. Neither the Java or JavaScript generator will generate the deployment descriptor.