Regarding the question about what things Odin statically links when you do a default `odin build .` compile: The runtime is statically linked. For example, you don't need any C/C++ redist package on Windows.
I have been waiting for this ever since you announced it! Can’t wait to get home and get it. Big fan of your content! Congratulations on this awesome accomplishment
Looking forward to the memory management section! It's what I feel like I'm the least knowledgeable about in Odin. Since memory is supposed to be manually freed it's what has me the most worried about making a problem :D ie : when is something going to be freed automatically when it goes out of scope vs when do I need to do it myself. Similarly with the deferred call. How to use properly.
@@karl_zylinski Just got it and already loving it. Jumped straight to the Enums section because those are always fun. The remarks on the side as a 'oh by the way' are a great way to use space. It doesn't use hyper specific terminology that would require some prior understanding. Already plenty of links to other sections to say where more details about a specific term will be talked about in more depth. The if statement checking the values? Amazing, adding that it will assert if you omit the ok check will likely save quite a bit of debug time for newbies. This sentence is a bit rough though "The f32_val^ = 7 above changes the value which the pointer f32_val points to" Maybe The f32_val^ = 7 updates the value it is pointing at, thus making val = 7. The original phrasing can seem like we are updating f32_val to point to another memory address if the reader isn't thinking of value as a strictly right sided term. Writing about pointers is hard... I commend you for tackling the topic.
Congrats, currently writing mostly Ruby for game dev, bur do want to learn some Odin and C for lower level options. Picked this up to start poking through at some point. Figure it will help me be a better programmer overall with the memory management piece at the least! Edit: Will keep an eye out for the game jam, may try to do that and use this as my companion for that.
Thank you. I agree, it helps in general! Understanding manual memory management makes you better at writing code in languages such as Ruby too, because you understand what Ruby is doing automatically for you, making it possible for you to do more well-informed choices.
RAAAHHH YEAH I LOVE ODIN AND I LOVE KARL
Congratulations. I hope is does well for you.
Thanks, just bought your book and started reading!
Regarding the question about what things Odin statically links when you do a default `odin build .` compile:
The runtime is statically linked. For example, you don't need any C/C++ redist package on Windows.
Hey man keep up the good work. You are a very good teacher. Thank you for everything youve made.
Congrats on you accomplishment
Thank you!
I have been waiting for this ever since you announced it! Can’t wait to get home and get it. Big fan of your content! Congratulations on this awesome accomplishment
Thank you!! 💖
Looking forward to the memory management section! It's what I feel like I'm the least knowledgeable about in Odin. Since memory is supposed to be manually freed it's what has me the most worried about making a problem :D
ie : when is something going to be freed automatically when it goes out of scope vs when do I need to do it myself.
Similarly with the deferred call. How to use properly.
Let me know how it went! Your type of background is something that I've tried to cater to in the book. So I'm interested in if I succeeded or not
@@karl_zylinski Just got it and already loving it. Jumped straight to the Enums section because those are always fun.
The remarks on the side as a 'oh by the way' are a great way to use space.
It doesn't use hyper specific terminology that would require some prior understanding. Already plenty of links to other sections to say where more details about a specific term will be talked about in more depth.
The if statement checking the values? Amazing, adding that it will assert if you omit the ok check will likely save quite a bit of debug time for newbies.
This sentence is a bit rough though "The f32_val^ = 7 above changes the value which the pointer f32_val points to"
Maybe
The f32_val^ = 7 updates the value it is pointing at, thus making val = 7.
The original phrasing can seem like we are updating f32_val to point to another memory address if the reader isn't thinking of value as a strictly right sided term. Writing about pointers is hard... I commend you for tackling the topic.
Congrats, currently writing mostly Ruby for game dev, bur do want to learn some Odin and C for lower level options. Picked this up to start poking through at some point. Figure it will help me be a better programmer overall with the memory management piece at the least!
Edit: Will keep an eye out for the game jam, may try to do that and use this as my companion for that.
Thank you. I agree, it helps in general! Understanding manual memory management makes you better at writing code in languages such as Ruby too, because you understand what Ruby is doing automatically for you, making it possible for you to do more well-informed choices.