MSIR.0797 No method linking for implied object: Difference between revisions
mNo edit summary |
(Automatically generated page update) |
||
| Line 26: | Line 26: | ||
While perhaps slightly inconvenient, this has no negative performance impact. The above example is silly, of course, as there is no point in sorting a new, and so empty, <var>StringList</var>. | While perhaps slightly inconvenient, this has no negative performance impact. The above example is silly, of course, as there is no point in sorting a new, and so empty, <var>StringList</var>. | ||
[[Category:Sirius Mods messages]] | [[Category:Sirius Mods messages]] [[Category:MSIR.0600 - MSIR.0799]] | ||
Revision as of 16:05, 13 August 2015
A method with an implied object or class was specified, and was followed by another method. This is not allowed. For example:
%list is object stringList ... %list = new
The new method, above, has an implied class (StringList) and is treated the same as if the class was made explicit:
%list is object stringList ... %list = %(stringList):new
However, when the implied class or object syntax is used, a subsequent method cannot be linked to the previous method. The following, for example, is invalid:
%list is object stringList ... %list = new:sort('1,10,A')
Values of an enumeration are considered shared members of the class, so they are subject to this restriction, too.
In the odd cases where one might wish to perform another method on the result of a method with an implied class or object, simply split the two methods into two statements:
%list is object stringList ... %list = new %list = %list:sort('1,10,A')
While perhaps slightly inconvenient, this has no negative performance impact. The above example is silly, of course, as there is no point in sorting a new, and so empty, StringList.