doc: Use more coding conventions in Object Oriented reference example code. * examples/code/@FIRfilter/FIRfilter.m, examples/code/@FIRfilter/FIRfilter_aggregation.m, examples/code/@FIRfilter/subsasgn.m, examples/code/@FIRfilter/subsref.m, examples/code/@polynomial/display.m, examples/code/@polynomial/double.m, examples/code/@polynomial/get.m, examples/code/@polynomial/mtimes.m, examples/code/@polynomial/numel.m, examples/code/@polynomial/polynomial.m, examples/code/@polynomial/polynomial_superiorto.m, examples/code/@polynomial/polyval.m, examples/code/@polynomial/roots.m, examples/code/@polynomial/set.m, examples/code/@polynomial/subsasgn.m, examples/code/@polynomial/subsref.m: Remove "Function File" from deftypefn. Use names of variables in error messages. Surround invalid items in error messages with single quotes. Use meaningful variable names.

To cite GNU Octave in publications use:

  John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring (2015).
  GNU Octave version 4.0.0 manual: a high-level interactive language for
  numerical computations.
  URL http://www.gnu.org/software/octave/doc/interpreter/

A BibTeX entry for LaTeX users is:

  @book{,
    author    = {John W. Eaton, David Bateman, S\oren Hauberg, and Rik Wehbring},
    title     = {{GNU Octave} version 4.0.0 manual: a high-level interactive language for numerical computations},
    year      = {2015},
    url       = {http://www.gnu.org/software/octave/doc/interpreter},
  }

We have invested a lot of time and effort in creating GNU Octave, please cite it
when using it.  See also `citation pkgname' for citing Octave packages.