-
Notifications
You must be signed in to change notification settings - Fork 18
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
Started a rewrite #65
base: master
Are you sure you want to change the base?
Conversation
Created a "basics" chapter
Create a worked example that wraps libmagic
I think if you call your build script One could argue that explicitness is better though |
One of the things I always struggle with is exactly what you need to clean up when, especially when you're in a failure state. I've seen lots of C libs that use goto in this situation, because the default control flow structures just don't cut it. Here is an example. The guide could talk about this/mention that you may need to look in the C source code to know exactly what you have to free when. |
As a general rule, you'll want to release any resources you acquired during the object's lifetime. In this case the only thing that was acquired was the
This is true and actually one of the few times where I'd promote the use of EDIT: Ooh, I just found a bug in my code! We shouldn't be using |
Plugins and dynamic loading
Error handling chapter
(Rendered)
(fixes #64)