[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
## [Octave-bug-tracker] [bug #44291] nextpow2 with vector uses length of ve

**From**: |
Carnë Draug |

**Subject**: |
[Octave-bug-tracker] [bug #44291] nextpow2 with vector uses length of vector instead of each element of vector |

**Date**: |
Wed, 18 Feb 2015 16:53:40 +0000 |

**User-agent**: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Iceweasel/31.4.0 |

URL:
<http://savannah.gnu.org/bugs/?44291>
Summary: nextpow2 with vector uses length of vector instead
of each element of vector
Project: GNU Octave
Submitted by: carandraug
Submitted on: Wed 18 Feb 2015 16:53:39 GMT
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Matlab Compatibility
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: Any
_______________________________________________________
Details:
When calling nextpow2 with a vector, Octave currently uses the length of the
vector. On the other hand, Matlab computes the nextpow2 for each element of
the vector.
octave-cli-3.8.2> nextpow2 ([15])
ans = 4
octave-cli-3.8.2> nextpow2 ([15 15]) # is computing nextpow2 (length ([15
15]))
ans = 1
I can fix this myself, but that is a backwards incompatible change (also, I
believe that Matlab behaviour here is saner but I am more used to nd signals).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?44291>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/

**[Octave-bug-tracker] [bug #44291] nextpow2 with vector uses length of vector instead of each element of vector**,
*Carnë Draug* **<=**