One of the proposals that arose in the FreeBASIC Discussion December 2017 was to add a sound library to FreeBasic. The topic has been already discussed to some extent in this action thread, where several users showed interest in such a library: https://freebasic.net/forum/viewtopic.php?f=17&t=2...

"DWSTRING" should be avoided, because it is used in the compiler´s code. Why? 'dwstring' and 'fb.dwstring' could co-exist in compiler without conflict. Same goes for any user code. 'fb.dwstring' will not break any existing code unless 1) '"dwstring' is already defined AND, 2) have '#...

Thanks, José. Yeah, I recognize you have goals well beyond what fbc can offer natively. I completely understand your motivation to optimize for your typical usage. fb can't come close to what you have developed and offer. For a var-len wstring substitute distributed with freebasic I'm going for the ...

ustring indirection: this is absolutly necessary in my view for possible later changes ( what we currently have is maybe not something, which will stay forever. We know, what we would have to do to fix it for good, but we fear the effort ). If people code "FB_USTRING.DWSTR" and there is a...

Whatever I accept, someone will be disappointed. Recommendation for #include/namespace is based on years of experience with this project, input from other developers, feedback from users. I should be so lucky to examine every problem in isolation. What does PureBasic have to say about namespaces ( m...

I still have general issues with this added ustring.bi + tests #161 Yes, I'd like to finish this PR off; it's fairly close to the top of my todo list to get this finished and merged in. Originally, the 'ustring.bi' was pretty much copy+paste from Jose's WinFBX followed by some hack+slash. It might ...

Yes, we are not making a c++ clone. Where there is a same construct between fbc & c++, I am attempting to make those binary compatible and write unit tests for it. By following a standard(*) I'd like to allow future expansion on bindings. I'm not working to create full compatibility since it is ...

it was mentioned in the community thread, and I have seen it multiple times over the years on the forum. EVERYONE who is against adding new keywords/features to the compiler will eventually say it is because we already have too many keywords cluttering up the namespace and thus should not add any m...

Believe me, it works. You could do this: #macro wave(a, b...) wave_##a(b...) #endmacro #macro names are in the global namespace and interfere with every kind of usage. ---- For naming patterns, there are several groups of existing fb functions like Screen*, Image*, File* Regardless, putting all fun...

And why make additional inclusions in the form of "# Include"? Why can not you make direct use of sound commands like in gfxlib? All of QB's gfx statements were added by default. And a few new gfx statements were added later. Even then it was noticed that global namespace pollution was go...

Continuing my ramblings on bindings and stuff... In case everything else I posted is TLDR; - fbc can natively bind to C code and some C++ code - fbc follows itanium C++ ABI where possible - fbc feeds asm to gnu assembler - fbc feeds C code to gcc (using gcc like as high level assembler). So here's t...

Also, I have a question for coderJeff: any plan for generics? There is this work that v1ctor did early 2018: https://github.com/freebasic/fbc/pull/69 I just haven't had time to go through it. I regularly rebase it on current master , though. It has an example of a generic list. Even though it's onl...

FB can call a C++ mangled function, but since it didn't know anything about C++ vtables last time I tried it, it couldn't handle any real C++ library where inheritance was used. I think so: for single inheritance only. I haven't tested it much. Here's an example that calls a derived method though a...

Continuing... 6) Bindings for C libraries and shared libaries (DLL) With fb's runtime written in C and dependent on C run time library for support, it is necessary that fbc be able to generate code that can bind (link) to C libraries. And with possibility for shared libraries, the binding must follo...

To get an understanding of current development it may be helpful to know (review) what has already been done to get a perspective on where we are now. 1) QB Roots Undoubtedly the look and feel of the language is based on QB. In attempt to accommodate the spectrum of users, this has evolved in to 3 d...