Franco Alcaraz
Franco Alcaraz
Hello, I ran your example but I did not get any errors using 'fxp-s65/46' or 'fxp-s32/23' This message **AttributeError: 'complex' object has no attribute 'dtype'** is confusing, it is like...
You're right about this issue is related to #62. When you do ```x[0]```, you get a new `Fxp` with a copy of the indexed raw value (numpy does not create...
`np.binary_repr` of `int(Fxp)` will return a binary representation of integer part of fixed point number. This function completes with _sign bit_ up to 16 bits, but those are not the...
hello @edschofield, You're right, `inaccuracy` flag should be propagated in these cases. This must be added to next patch! Now, `c` only raises `inaccuracy` flag according the result of `a_...
The method `bin` returns a string without `0b` prefix to maintain compatibility with python. So, you can add this prefix before create a new `Fxp` or when you get binary...
Yes, it would be good! I'll try to include that in next release. Thanks for the recommendation.
As you are using 2 bits for fractional part, 256.2 is rounded to 256.0. You need more fractional bits to get a fixed-point value closer to 256.2. With 2 bits...
_fxpmath_ works with _numpy_ through dispatching methods `__array_function__` and `__array_ufunc__` ([more info here](https://numpy.org/neps/nep-0018-array-function-protocol.html)) where a `Fxp` is converted to a `ndarray` before call the _numpy_ function and create a new...
Closing this issue due it's inactive.
solved in [v0.4.9](https://github.com/francof2a/fxpmath/releases/tag/v0.4.9)