In '-lang fb', I get:
8.1 8.1 8.1
7.700000000000001 7.700000000000001 7.700000000000001
0.1571428571428572 0.1571428571428572 0.1571428571428572

For fbc version 1.20.0 only: - Can you correct the cases '2.1 pass' and '2.2 pass' at least ? (the '0' of the terminal character of zstring does not play its role of end) - Could you correct other 'NON OK' cases ('return' cases) ? - Note: Only the cases '1.1' and '1.2' are compatible with the use o...

Without going that far, you can more simply encapsulate the declaration+initialization of your var-len array in a Type. This will cause the compiler to add a constructor, and an instance of this type can then be declared shared: type udt dim fruitname(0 to 2) as string => {"apple", "o...

Since fbc version 1.20.0, the compiler always pads the STRING*N type with spaces. If you do not want spaces on the right side of your string, use rather the ZSTRING*N type: dim shared fruitname(0 to 2) as zstring * 20 => {"apple", "orange", "banana"} (with this type ZST...

Why not just use: #define C chr(0) Because const has higher operational efficiency :D Indeed, "Constants" have similar visibility rules than variables for Namespace blocks, Type blocks, and compound block statements, while "Defines" are only scoped inside compound block statemen...

Why not just use:
#define C chr(0)

Jeff, Back to : Pass Byref to a function, Return Byref from a function Assignment of the 3 types of string ( 'String' , 'String * N' , 'Zstring * N+1' ) by calling 2 types of function ( 'Byref As String' , 'Byref As Zstring' ): - either passing by reference to the function, - or returning by refere...

The test-suite has some tests for [L|R]TRIM, however does not specifically test behaviours with CHR(0) either for the string argument or the filter argument. I think behaviour should be changed - however, there are several places internally where the rtlib uses common functions to scan a string for...

Documentation updated: ProPgOperatorOverloading → fxm [added in last example a workaround for a bug in fbc versions 1.10.0/1.10.1] This is due to a bad code generation for an argument passed to a 'Byval UDT Ptr' parameter when a specific conversion environment is encountered. The workaround consist...

Well done Jeff. Otherwise I had already seen another configuration which presents the same behavior: const SHOW_CHANGE = true type ROOT extends object Declare Constructor (Byref _name As String = "") #if SHOW_CHANGE Declare Operator Let (Byref rhs As root) '' same behavior with: Declare Co...

THANK YOU This "segmentation violation" signal only appears since version 1.10.0 of fbc. The simple change: Sub PrintInfo ( ByVal ByRef p As root Ptr) is enough to correct it (otherwise, the value of the pointer passed is polluted!!!). I will try to isolate/simplify this abnormal behavior,...

Indeed, for very simple UDT with for example only numeric member fields without initializers: - the compiler does not add an implicit constructor but only allocates memory set to 0, - the compiler does not add an implicit copy-constructor but only performs a shallow (bitwise) copy, - the compiler do...

There are cases where there are no constructors or copy-constructors or destructors (neither explicit nor implicit).