[Top][All Lists]

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

[Octave-bug-tracker] [bug #52787] Arithmetic functions cumsum, chop, pri

From: anonymous
Subject: [Octave-bug-tracker] [bug #52787] Arithmetic functions cumsum, chop, primes behave slight differently from document
Date: Tue, 2 Jan 2018 09:21:04 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0


                 Summary: Arithmetic functions cumsum,chop,primes behave
slight differently from document
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Tue 02 Jan 2018 02:21:02 PM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.1
        Operating System: GNU/Linux



"cumsum" document mentions parameter "extra",
but doesn't support it:

octave:1>  cumsum (1:5, 'extra')
error: cumsum: unrecognized string argument
octave:1>  cumsum (1:5, 2, 'extra')
error: cumsum: unrecognized string argument

"chop" document says that
 -- chop (X, NDIGITS, BASE)
     If BASE is not specified it defaults to 10.
but behaves as

octave:1>  chop (-pi, 5, 10)
ans = -3.1420
octave:2>  chop (-pi, 5)
ans = -3.1416

"primes" document says that
     The output data class (double, single, uint32, etc.)  is the same
     as the input class of N.
but the output class is always "double":

octave:1>  class (primes (10))
ans = double
octave:2>  class (primes (single (10)))
ans = double
octave:3>  class (primes (uint32 (10)))
ans = double


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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