GNU
/
easejs
1
0
Fork 0
Code Releases Activity

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.
master
Mike Gerwitz 2016-07-15 13:40:15 -04:00
parent 86df50d1ca
commit 30e7feefc9
No known key found for this signature in database
GPG Key ID: F22BB8158EE30EAB
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/classes.texi
View File

@ -225,9 +225,10 @@ a couple important notes before we continue evaluating this example:
@itemize @itemize
@item @item
The first thing you will likely notice is our use of the @code{public} 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 keyword;
recommended. Future versions of ease.js may provide warnings when the this is optional (the default visibility is public);
visibility is omitted. We will get more into visibility later on. it may be omitted for a more traditional JavaScript feel.
We will get more into visibility later on (@pxref{Access Modifiers}).
@item @item
Unlike @ref{f:class-js,}, we do not use the @code{new} keyword in order to Unlike @ref{f:class-js,}, we do not use the @code{new} keyword in order to