From 81113085063616f6798af5fe23f86dcf190d2d25 Mon Sep 17 00:00:00 2001
From: halw <halw@abb3cda0-5349-4a8f-a601-0c33ac3a8c38>
Date: Thu, 30 Aug 2012 15:23:45 +0000
Subject: [PATCH] Removed old "infix" syntax in discussion, replacing with
 "alias". From community feedback.

Author:halw
Date:2012-08-30T15:23:45.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1171 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
---
 .../current/method/invitation-eiffel-i2e/i2e-classes.wiki      | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/documentation/current/method/invitation-eiffel-i2e/i2e-classes.wiki b/documentation/current/method/invitation-eiffel-i2e/i2e-classes.wiki
index 074919fe..27c93c05 100644
--- a/documentation/current/method/invitation-eiffel-i2e/i2e-classes.wiki
+++ b/documentation/current/method/invitation-eiffel-i2e/i2e-classes.wiki
@@ -102,10 +102,9 @@ In Eiffel's object-oriented programming style any operation is relative to a cer
 
 If you need to denote the current object explicitly, you may use the special entity <code>Current</code>. For example the unqualified occurrences of <code>add</code> appearing in the class text above are equivalent to <code>Current</code>. <code>add</code>. 
 
-In some cases, infix or prefix notation will be more convenient than dot notation. For example, if a class <code>VECTOR</code> offers an addition routine, most people will feel more comfortable with calls of the form <code>v + w</code> than with the dot-notation call <code>v.plus (w)</code>. To make this possible it suffices to give the routine a name of the form <code>infix</code> "+" rather than <code>plus</code>; internally, however, the operation is still a normal routine call. Prefix operators are similarly available. 
+In some cases, infix or prefix notation will be more convenient than dot notation. For example, if a class <code>VECTOR</code> offers an addition routine, most people will feel more comfortable with calls of the form <code>v + w</code> than with the dot-notation call <code>v.plus (w)</code>. To make this possible it suffices to give the routine a "<code>+</code>" alias. The operation is still a normal routine call which can be invoked with either the infix form or the dot-notation. 
 
 The above simple example has shown the basic structuring mechanism of the language: the class. A class describes objects accessible to clients through an official interface comprising some of the class features. Features are implemented as attributes or routines; the implementation of exported features may rely on other, secret ones. 
 
 
 
-