-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NArray overflow warning #16
Comments
The current release version of NArray does not support error/warning handling in the course of calculation, because it requires an amount of new design and development. How do we switch behaviours? Where is the error information recorded? How do we treat partially calculated array? The future version of NArray may support such features. |
I am struggling with this issue again (I think):
Please explain to me why this is not returning 299 as expected? PS If I am indeed overflowing some 256 char value, I would expect that it could be fixed by converting to an integer array:
alas, same wrong result. It seems that byte NArray cannot be converted to int NArray? (no warning no nothing):
PPS There are probably a number of different ways to solve the problem like:
But I feel that this is actually arriving at the result indirectly. |
|
Neat, however, I am still puzzled about NArray's behaviour in the above circumstances. |
I just wasted a lot of time tracking down a mistake I made: overflowing a byte NArray. Narray overflows without raising any errors - a typical C thing. Can we have an overflow warning? If this impairs performance, perhaps we can invoke some debug pragma?
The text was updated successfully, but these errors were encountered: