Comments by "yapdog" (@yapdog) on "Low Level" channel.

  1. Yep. You basically created a memory pool. Went through all of this and and whole lot more with the dynamic memory pool component of my (non bare metal) OS. Great video 😁👍
    34
  2. 1:33 I don't believe (re)generative AI will pave the way for big advancements in human society. Right now it's driven by the stock market, not by actual usefulness. It will be a while before we get over this sugar rush, and move toward something substantive.
    18
  3. This is a prime example of why you should never ignore the #$%^%& compiler warnings!
    7
  4. Yeah, you'll just end up with memory leaks and crashes, but funny 😅 #define my_malloc malloc #define my_free free
    4
  5. Been using a mouse while coding for over 30 years, currently dealing with a project that has nearly 1000 files. No fvckin' way am I giving up my mouse just to look "cool."
    3
  6. Eff that! I've been using gotos in C for over 3 decades, and I have no intention of removing them. I use goto in virtually every function in my OS. I use them for error value reporting, jumping to the bottom of the function, thus having only 1 goto error exit point (e.g. "error_exit") and 1 success exit point (e.g. "success_exit") for every single function while having a much more descriptive error log. So, I would even modify your code example by only having the error gotos log the error then goto "error_exit" where the error return value is set. And since the cleanup may need to be performed regardless of success or failure along the way, "error_exit" then goes to "success_exit" where said cleanup is handled. Without having to check error logic, this is clean and consistent, becoming second nature when you write functions.
    2
  7. Great info! SUBSCRIBED
    1
  8. 0[myarray]..... WTH??? I've been programming in C for over 3 decades, where I've developed grammar systems, and am deep in development on a dynamic language processor, but I never knew about that syntax. However, my honest opinion: 0[myarray is utter BS. Unless someone can tell me that there's an actually usage case for it that the usual myarray[0] syntax doesn't provide, all it does is add needless ambiguity to the language and, as such, should never be used. I'm open to being proven wrong, tho.....
    1
  9. I live under a rock, and I've heard about it.
    1
  10.  @FalcoGer  Nnnope. In my dev environment, no warnings are okay! Especially not for commercial products. That mantra has been serving me well for 3 decades of C programming.
    1
  11.  @r.t.5767  Exactly.
    1
  12.  @thewindowsexperience489  It may have been, but some noobs may see it differently
    1
  13. If the comments are any indication, all you've done is create more irrational fear of pointers. Well done 😅
    1
  14. Agreed.
    1