I am working on a project that is used with the following syntax from the command line:
< Pre> program-name input-file
The process of inputting the program, calculating some of the stuff and telling the results on stdout.
The language of my choice is C ++ for a number of reasons, because I am not ready to argue that the computation phase will be very symbolic (the compiler feels) and will use very complex dynamically allocated data structures . Specifically, this RAI is not conducive to style programming.
I am thinking that forgetting about releasing memory is acceptable, provided I hope that the whole computing consumes less than available memory and after the OS program is finished, all the memory in one step Free to retrieve (the program ends in seconds) What is your opinion about this?
As a backup plan, if ever I need to run my project as a server or run interactively, then I felt that I can always deposit the waste collector into the source code. . Does anyone have the experience of using garbage collectors for C ++? Do they work well?
This question should not cause any problem in the specific situation described. / P>
However, this is not quite normal. The static analysis tool will complain about it. Most importantly, it creates bad habits.
Comments
Post a Comment