The 'Fre()' FB keyword does not refresh the memory. The 'Fre()' FB keyword returns the amount (in bytes) of available or unused dynamic memory which is allocated at this time by the OS. I think that the quantity of dynamic memory allocated by the OS is not constant during the program execution. The...

The memory allocated in the heap for a string of N characters is greater than that allocated by Callocate(N) in order to optimize the execution time for string length changes (the memory is allocated by large step to minimize the number of re-allocations induced by small string length changes). We c...

__fb_uniqueid__ returns an unquoted text
__fb_quote__ return the over-quoted text
__fb_unquote__ returns the sub-quoted text

Corresponding documentation pages updated accordingly.

coderJeff wrote:Changes merged in: __fb_uniqueid__(stack) returns empty string on undefined or empty stack

OK, thanks.

I just realized that I forgot to create the documentation page for 'fb_MemCopyClear' ( 'fb_MemCopy' and 'fb_MemMove' created only). I'll take care of it now! Done: KeyPgFBMemcopyclear → fxm [new page created] Note: I discovered this oversight while reading the change line: -...

I just realized that I forgot to create the documentation page for 'fb_MemCopyClear' ('fb_MemCopy' and 'fb_MemMove' created only).
I'll take care of it now!

I don't know if you have suggestion for better terms. I've been using those terms just for myself to keep it straight what each macro returns. __fb_arg_count__ returns numerical value as unquoted text __fb_uniqueid_push__ & __fb_uniqueid_pop__ return nothing __fb_uniqueid__ returns unquoted tex...

2) I see from your example on __fb_arg_count__, we still need something like __fb_arg__(N) to get arguments from the variadic argument list. ..... Good idea, I was thinking about it too. 2) ..... To note with __fb_arg_count__, it also respects parentheses level, so __fb_arg_count__( a, b(x,y), c(x,...

About updating the documentation to include these "basic macros": - I was thinking of just adding them to the already existing 'Predefined Symbols' list / 'Intrinsic Definitions' list. - The only page where they would be functionally grouped together (under the 'Basic-Macros' tittle) woul...

First, consider this example that doesn't use unique ids. It works, because '__counter__' variable is defined in a local SCOPE and therefore allows nesting. #macro repeat ? ( count ) scope dim __counter__ as uinteger = count while( __counter__) #endmacro #macro end_repeat __counter__ -= 1 wend end ...

May be one another error at least: 'Count' is passed by value and not by reference, so its value in not changed by the procedure body (it is processed as a local variable to the procedure). Only strings, UDT instances and arrays are implicitly passed by reference in the '-lang fb' dialect: => SUB X&...

In the first version of change, parentheses when calling a macro had become systematically optional for all macros, but when CoderJeff discovered possible conflicts with other expressions containing the names of the macros as terms, it added a special declaration syntax that alone allows this. See h...

See the updated #MACRO...#ENDMACRO documentation page.

About updating the documentation to include these "basic macros": - I was thinking of just adding them to the already existing 'Predefined Symbols' list / 'Intrinsic Definitions' list. - The only page where they would be functionally grouped together (under the 'Basic-Macros' tittle) would...

A number of '__FB_UNIQUEID_POP__(stack_id)' greater than the number of '__FB_UNIQUEID_PUSH__(stack_id)' induces a compiler runtime error. Can this be fixed to rather induce a compiler error message? __FB_UNIQUEID_PUSH__(stack_id) __FB_UNIQUEID_POP__(stack_id) __FB_UNIQUEID_POP__(stack_id) Compiler o...