This is exactly what I have been thinking of doing. I have also been quite interested in Gnome lately. Been wanting to develop Gnome extensions, and Gtk applications. Ironically I am also a vim/coc user. Keep the videos coming. Also a neat trick in vim, if you are hovering over a C library function like itoa() in normal mode, and you hit Shift + k, it will open a new horizontal buffer with the Linux Programmers manual information for that function
Yeah, I believe you should use snprintf instead of sprintf with the sizeof(buf) as an argument to check on the size. What you were seeing in the overflow I think was just undefined behavior which writes into some other memory that may or may not actually crash it. Perhaps the first char sized overflow was nothing critical (no idea). The strcat, strcpy, functions were more or less replaced with either strncat/strncpy or strlcat/strlcpy (which is even safer because it checks the size of the concatenated string), etc etc. (#include ) from libbsd or you could write your own if you wanted. Microsoft had some functions of their own but it seems they were not conforming with the standards. (sprintf_s or something similiar) Anyway, best to double check this and google it if you need to write something critical. Enjoyed the stream, thanks!
This is exactly what I have been thinking of doing. I have also been quite interested in Gnome lately. Been wanting to develop Gnome extensions, and Gtk applications.
Ironically I am also a vim/coc user. Keep the videos coming. Also a neat trick in vim, if you are hovering over a C library function like itoa() in normal mode, and you hit Shift + k, it will open a new horizontal buffer with the Linux Programmers manual information for that function
I see Vivaldi, I know it is a man of culture. Well done on the intro, perfect for people who enjoy video more then only going through the docs.
Hi , thanks for this , can you please inform what vim plugins you use to show the api ? Can you share the .vimrc maybe ?
Yeah, I believe you should use snprintf instead of sprintf with the sizeof(buf) as an argument to check on the size. What you were seeing in the overflow I think was just undefined behavior which writes into some other memory that may or may not actually crash it. Perhaps the first char sized overflow was nothing critical (no idea). The strcat, strcpy, functions were more or less replaced with either strncat/strncpy or strlcat/strlcpy (which is even safer because it checks the size of the concatenated string), etc etc. (#include ) from libbsd or you could write your own if you wanted. Microsoft had some functions of their own but it seems they were not conforming with the standards. (sprintf_s or something similiar) Anyway, best to double check this and google it if you need to write something critical. Enjoyed the stream, thanks!
best gtk video to learn
Nice vid.
Nice. Can you use smaller screen resolution? It will be easier to see videos on the phone. Or larger font…
Yeah, I'll pay more attention to this. I'm still playing around with resolutions, etc., to see what works best.
Will there be a part 3?
Yeah, eventually I would like to revisit this.
@@DouglasRumbaugh ETA?
Nice nice nice!!!