oo final/closed pragma can also be deduced

Raku · Nov 22, 2012 · 6d862fd · 6d862fd
1 parent 30974c6
commit 6d862fd
Showing 1 changed file with 10 additions and 3 deletions.
diff --git a/S12-objects.pod b/S12-objects.pod
@@ -13,8 +13,8 @@ Synopsis 12: Objects
 
     Created: 27 Oct 2004
 
-    Last Modified: 22 Jun 2012
-    Version: 125
+    Last Modified: 22 Nov 2012
+    Version: 126
 
 =head1 Overview
 
@@ -2154,7 +2154,14 @@ selecting global semantics of the underlying object-oriented engine:
 
     use oo :closed :final;
 
-This merely changes the application's default to closed and final,
+This forces the optimizer to consider the current file to represent
+the top-level application; however, the optimizer is also allowed to
+assume these semantics when it can determine that it is linking an
+entire application, such as when the current file is being run from
+the command line or from a mouse click.
+
+These pragmatics (whether explicit or assumed) merely change the application's
+default to closed and final,
 which means that at the end of the main compilation (C<CHECK> time)
 the optimizer is allowed to look for candidate classes to close or
 finalize.  But anyone (including the main application) can request