From 30e7feefc9b3ac441df04a567dc8fc8c1d94e084 Mon Sep 17 00:00:00 2001 From: Mike Gerwitz Date: Fri, 15 Jul 2016 13:40:15 -0400 Subject: [PATCH] Remove strong recommendation for `public' in manual * doc/classes.texi (Defining Classes): Remove the recommendation for using the `public' keyword always (instead of omitting it), and the reference stating that it may be required in the future. This is not the case. --- doc/classes.texi | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/classes.texi b/doc/classes.texi index 9fd510b..e3fe516 100644 --- a/doc/classes.texi +++ b/doc/classes.texi @@ -225,9 +225,10 @@ a couple important notes before we continue evaluating this example: @itemize @item The first thing you will likely notice is our use of the @code{public} -keyword. This is optional (the default visibility is public), but always -recommended. Future versions of ease.js may provide warnings when the -visibility is omitted. We will get more into visibility later on. + keyword; + this is optional (the default visibility is public); + it may be omitted for a more traditional JavaScript feel. +We will get more into visibility later on (@pxref{Access Modifiers}). @item Unlike @ref{f:class-js,}, we do not use the @code{new} keyword in order to