From 3e42093946d2f4b03b15e7713573a54a1878e922 Mon Sep 17 00:00:00 2001 From: eiffel-org Date: Fri, 16 Sep 2016 14:36:37 +0000 Subject: [PATCH] Update wikipage Eiffel as an expression language. (Signed-off-by:b-meyer). git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1609 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../eiffel/Technical_papers/eiffel-expression-language.wiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/trunk/eiffel/Technical_papers/eiffel-expression-language.wiki b/documentation/trunk/eiffel/Technical_papers/eiffel-expression-language.wiki index 465f056c..ffd7279d 100644 --- a/documentation/trunk/eiffel/Technical_papers/eiffel-expression-language.wiki +++ b/documentation/trunk/eiffel/Technical_papers/eiffel-expression-language.wiki @@ -11,6 +11,6 @@ To make the notations simpler, a number of extensions have been proposed. They i *Type inference (to avoid explicitly specifying the type when it can be deduced from the context). This is a facility for the programmer, useful in particular for local variables, but does not affect the type system: Eiffel remains strongly typed, it is just that you can be lazy about writing the type when there is no ambiguity. *In the same vein, omitting the entire list of generic parameters when it can be inferred. -The description of the mechanism (see the link below) is in the form of a set of slides explaining the concepts and presenting example. This is a working document and feedback is welcome. +