To the developers of mmg plan to continue using exit() in the code? It makes it hard for people who plan on using mmg inside another application because this causes the overall application to exit anytime there is an exit in mmg.
Normally, we use exit() for very strong failures of the applications (lack of memory, unexpected cases…). But maybe you have found an exit() that must not be here?
We don’t plan for now to remove it.
Okay, thanks for the response!
It was exiting when I used larger hausdorff values. It would give a warning about a geometrical problem, then INVALID ELEMENT, and then exit. It seems like this was a result of the remeshing process, not the input mesh, so I would’ve expected for it to return an error that it couldn’t mesh it or something.
I understand the motive in using exit() though, thanks!