12.10.2026, 20:21
For F256, I can look at the test code. Since you don’t have to write the code, you can build extreme test apps.
I used DeepSeek to write it. I double checked the output with Google AI.
> Therefore, any results are automatically suspicious.
That’s the most important thing to understand. But the same can be said for your code.
So, you use it to test your and its code. For me, test code is extremely boring and tedious. A good test app may require more code than the source.
If you already understand all the implications, you don’t need AI.
Let’s say you want to do something you’re not that familiar with. I don’t have a clue on 3D graphics. With one prompt I had DeepSeek write a 3D test app in C. Moving forward with that would require a lot of work and testing, but that’s too powerful to ignore.
I was curious as to how one could write a BASIC compiler that translates to C, that supports dynamic strings, wide strings and arrays; and automatically frees them when they go out of scope. As it turns out, with GCC or Clang, not MS, you can do that with “`__attribute__((cleanup))”.
DeepSeek asked if I wanted a sample, so why not.
I now have a BASIC compiler that supports dynamic strings and arrays in a UDT, that gets freed when it goes out of scope. And it actually compiles code. I’m not going to try and write a full compiler, too many details.
It’s worth spending a little time playing around with. You don’t need it for what you already know, you need it for what you don’t know how to do or is boring and tedious. Too powerful to ignore.
I used DeepSeek to write it. I double checked the output with Google AI.
> Therefore, any results are automatically suspicious.
That’s the most important thing to understand. But the same can be said for your code.
So, you use it to test your and its code. For me, test code is extremely boring and tedious. A good test app may require more code than the source.
If you already understand all the implications, you don’t need AI.
Let’s say you want to do something you’re not that familiar with. I don’t have a clue on 3D graphics. With one prompt I had DeepSeek write a 3D test app in C. Moving forward with that would require a lot of work and testing, but that’s too powerful to ignore.
I was curious as to how one could write a BASIC compiler that translates to C, that supports dynamic strings, wide strings and arrays; and automatically frees them when they go out of scope. As it turns out, with GCC or Clang, not MS, you can do that with “`__attribute__((cleanup))”.
DeepSeek asked if I wanted a sample, so why not.
I now have a BASIC compiler that supports dynamic strings and arrays in a UDT, that gets freed when it goes out of scope. And it actually compiles code. I’m not going to try and write a full compiler, too many details.
It’s worth spending a little time playing around with. You don’t need it for what you already know, you need it for what you don’t know how to do or is boring and tedious. Too powerful to ignore.