octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #62395] Compatability feature request - std an


From: Rik
Subject: [Octave-bug-tracker] [bug #62395] Compatability feature request - std and var optionally return mean as 2nd output
Date: Sat, 14 May 2022 21:18:27 -0400 (EDT)

Update of bug #62395 (project octave):

                  Status:          Ready For Test => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #3:

@Nicholas: Thanks for taking care of this.  I see that your changesets are
getting closer to perfection.  We have some guidelines that might be useful on
the Octave Wiki at https://wiki.octave.org/Contribute.  I don't know why they
are buried so deeply.

One thing I saw in the commit message is that you are using full paths to
files within the source tree.  We just use the file name unless there would be
confusion.  So, we write


* std.m: ....


instead of


* scripts/statistics/std.m: ....


Helpful notes for commit messages are at
https://wiki.octave.org/Commit_message_guidelines.

Second, the documentation has a very specific tone and is written in the
active voice and present tense.  There are guidlines for the help text at
https://wiki.octave.org/Help_text_style_guide.

Instead of "The function will calculate the ..." we write "Function calculates
the ...".

I made these simple changes for Octave coding conventions and then got
absorbed in cleaning up/optimizing std.m and var.m.  I checked everything in
here if you want to take a look
(http://hg.savannah.gnu.org/hgweb/octave/rev/1bf26f913b9c).

Marking bug as Fixed and closing report.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62395>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]