08-26-2022, 02:06 AM
Quote:The only one _not_ doing stuff that I've already done in QB64 a zillion times is Assert. That's a weird one, but I read that it's basically C's way of handling illegal values, which we can do in QB64 with some regular IF/THEN logic.I'm not an expert about programming in C. But "assert" is supposed to be used for debugging. "assert" is not a keyword, and it's not supposed to be a function adhering to POSIX standard. A good C compiler package would define it as a macro so that when "release" version of the app is to be compiled, there is no hint of it. On a few applications, it's more embarrassing instead to see "Runtime error!" crash box from M$CRT. During debug phase, everytime an "assert" is raised, the programmer is supposed to fix it, cannot become lazy about it. Provided source code with a lot of "asserts" indicates somebody didn't have the time to finish it.