Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
beegC0de132172dI hope you at least used STL containers to allocate memory and not malloc directly
Lor-inc84271dIdk what you did, but no garbage collection normally means leaking memory. It does work well, for 5 minutes if you're lucky, then it crashes with an out of memory error.
Yamakuzure206271dIf you have normal instances and do not allocate memory yourself, the destructors will take care of everything. No need for a garbage collector at all.
thestr18370d@beegC0de @Lor-inc The app was an MFC application, which was just a few simple dialogs with the options to go back back at the beginning, which was also developed using threads and events to change the dialogs, so you could use the plugin for more than a just few minutes.
@beegC0de if by that you mean, if i used new or i didn’t, i have to say there are places i did, and there are some i didn’t. Most of when i used was to instantiate dialog views.
I tested the app many times, specifically to see if there were any leaks, but it worked great..
Only thing i know is that they checked the code and they didn’t say anything, even though there are two things i know i did terrible.. memory management and string manipulations, but if they are happy then i don’t have to worry about that 🙂
Also they want to collaborate in the future, so that’s a good sign 😃
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job
xjose97x11Just saw a variable in C named like this: long time_ago; //in a galaxy far away I laughed no stop.
Cyborg17A guy and a girl are in a Java seminar. Afterward, the guy approaches the girl and asks, "Hey gurrl, can I ge...
Unskipp24So this happened last night... Gf: my favorite bra is not fitting me anymore Me: get a new one ? Gf: but it ...