MSIR.0807 Can't declare (meth) after (meth) already invoked: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
(Automatically generated page update) |
||
| Line 1: | Line 1: | ||
A <tt>Constructor</tt> or <tt>Disallow</tt> statement in a < | A <tt>Constructor</tt> or <tt>Disallow</tt> statement in a <var>Public</var> or <var>Private</var> block specified a <tt>New</tt> or <tt>Discard</tt> method, after such a method had already been explicitly invoked. Since these methods exist for all classes, whether or not they're declared, it is possible to use them before they are declared. However, as this message indicates. such a use is invalid. Make sure the class's Public or Private block is declared before any code that uses a <tt>New</tt> or <tt>Discard</tt> message. <blockquote>An <tt>Auto New</tt> setting on a variable declaration is considered an invocation of the <tt>New</tt> method so an <tt>Auto New</tt> object should be declared after the Public and Private blocks for its class.</blockquote> | ||
[[Category:Sirius Mods messages]] | [[Category:Sirius Mods messages]] | ||
Revision as of 19:11, 23 April 2014
A Constructor or Disallow statement in a Public or Private block specified a New or Discard method, after such a method had already been explicitly invoked. Since these methods exist for all classes, whether or not they're declared, it is possible to use them before they are declared. However, as this message indicates. such a use is invalid. Make sure the class's Public or Private block is declared before any code that uses a New or Discard message.
An Auto New setting on a variable declaration is considered an invocation of the New method so an Auto New object should be declared after the Public and Private blocks for its class.