Examples and templates are available if you install the WinFBE editor.
They are also available separately in my GitHub repository:
https://github.com/JoseRoca/WinFBXOn-line help for the WinFBX framework:
https://github.com/JoseRoca/WinFBX/tree/master/docsThe WinFBX framework provides almost all the PowerBasic functionality missing in FreeBasic and much more. Everything compiles in both 32 and 64 bit without any changes and everything is unicode aware.
Perhaps the most important class is CWSTR, that implements support for dynamic unicode strings and works transparently with the FreeBasic string functions and operadors, as well as with the Windows API and other C libraries.
Instead of implementing "A" (ansi) and "W" (unicode) functions, I have taken advantage of casting and automatic conversions. Therefore, although all the wrappers are unicode aware, you can use STRINGs, ZSTRINGs, WSTRINGs, CWSTRs, CBSTRs, CVARs and string literals transparently. Like with the Windows API, using unicode with them will be slightly faster, since no conversions are needed.
Probably the thing that more annoys PowerBasic users new to FreeBasic is the strict type checking, that, like with C++, compels the use of the appropriate data type (or alias) and frequent type casting. It annoyed me for a while, but I have got accostumed. None of the PowerBasic SDK programmers that are using FreeBasic haved had big problems. DDT programmers will have to learn SDK programming. Don't expect a PowerBasic to FreeBasic converter.
The lack of a lead developer means that no new features are being added for the moment, but some FBer's are still maintaining the compiler fixing bugs and improving the documentation. Fixing bugs is more important to me that adding multiple inheritance or a LLVM backend.
> I wonder how stable is FB 64bits, any ideas?
I have used FB 64 bit extensively without any problem. In fact, I use 64 bit more often than 32 bit, since my main motivation to use FB was to experiment with 64 bit programming.
