Skip to content
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

Better use the atexit function #23

Open
mr-cheff opened this issue Jun 13, 2023 · 4 comments
Open

Better use the atexit function #23

mr-cheff opened this issue Jun 13, 2023 · 4 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@mr-cheff
Copy link

f4c4629#r117789581

@mr-cheff
Copy link
Author

Also maybe, add the atexit function each time msinit or msnew is called

@Khhs167
Copy link
Owner

Khhs167 commented Jun 13, 2023

Destructors work better than atexit as of right now, as they're called automatically.

On top of this, atexit doesn't function in the same way as destructors, as destructors are invoked whenever the library is unloaded, so for dynamic loading via dlopen atexit won't work.

@Khhs167 Khhs167 added the enhancement New feature or request label Jun 13, 2023
@mr-cheff
Copy link
Author

but it's just for gcc, isn't it?

Maybe add the check if it's compiled for gcc in macros or not

@Khhs167
Copy link
Owner

Khhs167 commented Jun 18, 2023

that's exactly what I'm doing

@Khhs167 Khhs167 added this to the Next Release(1.3.0/1.2.1) milestone Jun 18, 2023
@Khhs167 Khhs167 modified the milestones: Next Release(1.3.0/1.2.1), Backlog Jul 10, 2023
@Khhs167 Khhs167 added the wontfix This will not be worked on label Jul 10, 2023
@Khhs167 Khhs167 removed this from the Backlog milestone Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants