Nothing, really. Mainly it's for historical purposes. And maybe a bit of nostalgia thrown in. Might be educational to some people. Will it have any affect on FB or anyone on this forum? Probably not.

The blog post about this is pretty interesting: https://devblogs.microsoft.com/commandline/microsoft-open-sources-gw-basic/ Apparently the interpreter was originally written in some assembly-like language and then translated to assembly for various platforms, not just 8086 and DOS. Sadly they aren't...

I'm not totally sure what you mean. FB has its own idea of a vtable. I have no idea what that is, nor how it differs from GCC C++'s vtable implementation. If FB were to adopt the GCC vtable structure as its own, then perhaps more compatibility with C++ would be possible. And maybe it's already prett...

EDIT: deleted.

I believe systemctl was complaining about the mentioning of and comparisons to Free Pascal. While I take his point (this is a forum for FreeBASIC after all), I find the comparisons with other languages to be useful. In many cases, the way Free Pascal does things could influence the way FreeBASIC doe...

Are you looking to simply run something in the background, or do you need to run it in a new terminal window, or do something like Gdebi where it shows the details of the command running in a widget?

Translating headers is hard. Partly because of complicated type definitions in C and partly because there's actually two full languages that have to be translated at once: the c preprocessor language and C itself. And the result of the preprocessor depends greatly on the environment in which it is r...

Sure, if you had a working FB compiler on those platforms, you could build fbfrog natively there. It's a pure FB program after all. fbfrog is just a header translator. It doesn't care what platform the header files it is parsing comes from. Could parse a windows library's .h files on Linux if you wa...

Indeed FBC does decorate method names and overloaded functions in the same way as gcc. However you need a lot more than that to interact with most C++ classes, particularly ones that involve virtual methods (polymorphism). That requires the ability to interact with C++ objects' vtables at runtime to...

Just write your messages to standard out. Can use regular printf(). Or write them to standard error. That will never get overwritten by graphics frames or the like. And they can be redirected to a file for analysis also. Nearly all Unix applications write debugging messages this way. If you start th...

If Windows updates are done, the universal runtime dll should be present. Unlike earlier runtimes, this one is distributed through windows update.

I wonder why FreeBASIC doesn't include headers for such an important library like OpenSSL, though. Could it be because lack of manpower? FB only has headers for libraries when contributors provide them. I think maybe two people did the majority of the .bi files that are currently shipped with FB, a...

Looks like you're making great progress. Nearly all of the TODOs in that bi file look pretty easy to manually translate to FB. Are there particular ones that are tripping you up? C's for() statement is very different than FB's for. You'll have to translate that to a while loop. But there are going t...

I don't think the winver stuff has anything to do with it. The msvcrt dlls come in different flavors, with the version in the file name. msvcrt70.dll etc. These correspond to the Visual C compiler versions, not the windows versions. Unfortunately only certain versions ever shipped with the OS. Every...