(3) as (1), but have some option to automatically add additional namespaces to the default namespace. Preferably in some order (e.g. to disallow or allow the added namespace to override keywords in main) This is what usually is done. Typically USING, USES or IMPORT is use. (if IIRC resp C#/Pascal/Ja...

Fyi At several (SMF?) forums, late july through August there was a really high level of forum spam. At our forum, late august a lot of mitigation was done, so I lost sight of the details. The bots might still be out there and active though.

So to summarize this (if i got it right), it´s not about making FB a C++ clone, it´s about enabling FB to link to C++ libraries too, which more and more are becoming standard over plain C libraries. Concretely it is about calling C++ methods. Maybe constructors/destructors too (IOW instantiating C+...

I, for a while, had some code that could plain C wrappers from C++ classes for use at work. (Delphi), but as more and more of the SDKs I used(*) dropped plain C compatibility, I ran into the same thing as Angros47. Very few C++ classes that only use plain C types and other classes as arguments and r...

Good chance that that is the linking step. gnu ld is not the fastest linker.

You could try to play with settings (e.g. turn on or off dead code elimination etc)

- kick out all "toolchains" except one Counterproductive. People that don't take part in development shouldn't tell people that actually do something to stop. - define an absolutely clear path structure defining non-ambiguously where FB.exe expects, relative to its own location, the vario...

I feel I should mention marcov's contributions to this community. I'm not sure if he's even tried fb. Not for production or so. I played with it for a while when helping someone on IRC with the first FB ports to FreeBSD (2008ish?). I also look at source from time to time, like gfxlib during the &qu...

This is normal. Default Windows settings are power saving. The increased demand on CPU causes the CPU to increase its frequency. The algorithms for that are complex and can't always be predicted easily. You can however indicate that you want a higher performance profile (e.g. for benchmarking). Go t...

speedfixer wrote:
The topic *is* language development beyond the current version 1.07.

No, it is "fbc 1.08 development". Even if you take that to be the compiler only, there are also things like native backends, ports, optimization etc.

I think that indeed way too many of such discussions are about language. Libraries (and by that I mean libraries in FB, not headers for libraries in other languages), quality releases etc are much more important. And I do agree with Caseih's Many a project has died, or at least got seriously sidetra...

(this thread got live again, and I saw an old reply on it that could do with some updates) In my opinion, the best solution would be to rewrite the fbgfx library under OpenGL. Obvious advantages: This would be a perfectly valid opinion a few years ago, but you are writing this a week after Apple ann...

Real FORs only evaluate the bounds once to calculate a number of iterations I know you weren't referring to floating point numbers with "real" there, but that reminds me, the earliest BASIC I used was BASICA or GWBASIC, and the default variable type was floating point (single if I recall)...

Loopvars often must be simple variables, because there is an attempt to heavily optimize the loopvar, and the number of scenarios and pitfalls rises enormously. Real FORs only evaluate the bounds once to calculate a number of iterations, so the bounds don't have to be simple variables because they a...

The point is that you can't do things like you normally do, and what internet recommends. This complicates things for people mostly working on newer windows. Just like any Windows code after 2000-2005 will probably call -W functions a lot. Things like that are basically behind the advise to not add...

The point is that you can't do things like you normally do, and what internet recommends. This complicates things for people mostly working on newer windows. Just like any Windows code after 2000-2005 will probably call -W functions a lot. Things like that are basically behind the advise to not add ...