Just a little supplement: Let's assume for a moment that we're talking about a person that is new to FreeBASIC, and also that the goal is to get this new user up and running having the least amount of knowledge possible. Maybe they are new to programming also ... it doesn't matter if we just talking...

The shown result for each of the two posts above is not demonstrative to us, because since '__FB_ARG_EXTRACT__' is not defined, then 'LAST_ARG_NUM' is not evaluated in the compiler output message. Compiler output message for both: __FB_ARG_EXTRACT__(LAST_ARG_NUM, 7, 89.78, "...

We are probably OK on the changelog.txt, these basic-macros are still new to 1.08.0. I can update the changelog to show the sytaxes though. It all depends if we consider that changelog.txt is: - only a synthesis of the modifications compared to the previous fbc version, - or otherwise as a logbook ...

How about this? __FB_ARG_LEFTOF__( expr, sep [, ret] ) __FB_ARG_RIGHTOF__( expr, sep [, ret] ) by default, if 'ret' is not given return nothing (empty token) if sep not found, otherwise return 'ret' if 'ret' is given and sep not found. Updated in current fbc/master for 1.08.0 and te...

By the way, I think the documentation is a bit imprecise on the return type of the 'Chr()' keyword. Looks to me like 'Chr()' returns (by value) a 'Zstring * N' type value if the passed parameters can be evaluated at compile time (with N = number of characters ...

I think this behavior is not specific to defining a font. The ascii code 255 when used in the first position of a string should I think be reserved exclusively as the extended code for detection of the extended keys (with 2 returned characters). Any other use (of the ascii code 255 in first position...

Yes, in QuickBasic, COMMON [SHARED] declares the variables to be transferred in a program called by CHAIN, or the variables common to several modules. Indeed, the first case (with CHAIN) is not supported by FreeBASIC. As a result, I will update the documentation as proposed. Thanks for the tip. [edi...

This can be interesting for FreeBASIC in the context of multi-threading.
But compared to your example above, in C# the 'Volatile' keyword can only be applied to the fields of a Class or Struct. Local variables cannot be declared 'Volatile'.

Thanks.

I guess you're talking about this one: Missing Documentation Missing Documentation Please edit this page to remove items when they are written or add items when they are noticed. Missing/Incomplete/Outdated Pages External Libraries - availability (windows, linux, DOS), usage, and download locations ...

changelog.txt: Version 1.08.0 [changed] ..... - fbc: double the minimum and default stacksize on 64-bit to 64Kb and 2048Kb respectively. ..... Documentation update: - CompilerCmdLine → fxm [default stack size doubled for 64-bit targets] - CatPgCompOpt → fxm [default stack size doubled for 64-bit tar...

get buf, (x,0)-(x+1,255), buf2
When x = 255, x+1 = 256, and that induces an outbound of buf's memory allocation.

To skip n optional parameters, you must put n+1 commas.

The only problem is that 'int' is already a freeBASIC keyword !
(redefine a keyword can work but is strongly discouraged)

Can we emulate a kind of TLS (Thread Local Storage) with FreeBASIC? Preamble Static variables are normally shared across all the threads. If we modify a static variable, it is visible so modified to all the threads. Unlike normal static variable, if we create a TLS static variable, every thread mus...