Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "array accessing"
-
I read this in stackoverflow today:
Welcome to every C/C++ programmers bestest friend: Undefined Behavior.
There is a lot that is not specified by the language standard, for a variety of reasons. This is one of them.
In general, whenever you encounter undefined behavior, anything might happen. The application may crash, it may freeze, it may eject your CD-ROM drive or make demons come out of your nose. It may format your harddrive or email all your porn to your grandmother.
source:
http://stackoverflow.com/questions/...1 -
I just wasted 2 hours trying to figure out why the properties of a destructured object returned undefined, even though everything was fine in JSON format. Tried to request data on the frontend from my server with a database attached. Tried accessing each object of my array separately, it worked. In a loop: dataArray[index].propertyX ... undefined??
Turns out I used the wrong property names to access the info inside each object.
🤦1 -
Swift: Have you ever noticed...
How many times the word "Safe" is used when describing Swift, yet there is no way to programmatically determine if a memory allocation failed?
How many ways this "Safe" system has a way of crashing:
1. Unwrapping a Nil Optional
2. Disconnected Outlets
3. Out-of-Range Array Access
4. Accessing Uninitialized Variables
5. EXC_BAD_ACCESS (Memory Access Errors)
6. Threading and Actor Isolation Issues
7. Type Casting Errors
8. Uncaught Language Exceptions
9. (fill in the blank?)
What frustrates me is that Swift lacks a language-level way to check if heap memory allocation succeeded. When you create an object like MyClass(), Swift assumes success—if allocation fails, the process dies instead of allowing your code to gracefully handle the failure.
And to avoid having pointers, it creates this horrendously random undocumenting syntax salad that is worse than ADA.
Swift, when you wanted a liter-bike and you get something else17 -
At the very start when I learned my first language. Didn't know where to find the "{" and "}" keys on the keyboard. Thought I would never be a dev, since I couldn't write a program without those keys.
Or when I didn't understand the notation of accessing values inside an array. Thought things like array[0] would do some magic to the array and didn't know how to access other parts of an array. I was following a book back then. -
And now I've run into a whole another issue which is really fucking strange.
Has it ever occured that a Object in java looses all it's values after being put into an array of same type?
My problem:
[code...]
Mat[] matArray = new Mat[totalFramesOfVideo];
videoCapture.open();
Mat currentFrame = new Mat();
int frameCounter = 0;
while(videoCapture.read()) {
currentFrame = (last read frame as a Mat)
matArray[frameCounter] = currentFrame;
frameCounter++;
}
then, after filling the array and accessing elements, they lose all their object values.
Eg. Before currentFrame's dimensions were 1080*1920, but matArray[index] dimensions are suddenly 0*0.6