(to be removed in fbc version 1.20.0 ?) Seems like something could be improved here and need to investigate what is going on in the rtlib: - rtrim( string ) - rtrim( string, filter ) - rtrim( string, any filter ) The test-suite has some tests for [L|R]TRIM, however does not specifically test behavi...

BUG #3 with new STRING*N LSET and RSET overflow the fix-len string field by always writing a null ubyte just after the last character of the fix-len string. I assume LSET and RSET have not been updated for the new STRING*N . Yes, not updated. I forget about these statements. For interest, some thin...

It would remain to be decided whether the case 's2' declared in a UDT always generates constructor code (regardless of other member data), like the case 's3' . I would like to try keep the optimization for now even though it currently gives a more complicated rule. Ideally, the underlying implement...

Perhaps a generalization due to the final padding with null characters on the right side of the old STRING*N (fbc version 1.10.0): (to be removed in fbc version 1.20.0 ?) Seems like something could be improved here and need to investigate what is going on in the rtlib: - rtrim( string ) - rtrim( st...

Does anyone know the reason for this ? https://github.com/freebasic/fbc/blob/da8f14569e2786e11b3e66371f39ecf306da3663/src/rtlib/str_hskip.c#L23 /* fixed-len's are filled with null's as in PB, strip them too */ while( (--len >= 0) && (((int)*p == c) || ((int)*p == 0) ) ) --p; I think this co...

sed ... I believe all the other uses for "lib" are for naming output files, e.g. "lib" + "SOMENAME" + ".a", etc. I can see how would seem to work ok when producing an executable only. so definitively gcc 13 changed something. Yes, I think default is a newer s...

in fact I have to changed the hard coded path of the library directory The 'sed' expression is aggressive. It's going to replace "lib" -> "lib64" even in places where it should not be replaced. I think I see now (maybe): - The bootstrap package is partially compiled sources (ess...

On this occasion, I just noticed that the following code did not trigger the following error message from the compiler: Dim As String * 20 array() Redim As String * 10 array(0) '' no error ! This seems familiar - maybe something to do with passing array arguments? but I can't quite place it. Perhap...

Hmm, the build process looks pretty good.

Was there a version of gcc & binutils that worked in the past?

I'm not sure what to suggest next.

But if we ensure that our starting buffer is large enough to handle the assignment, here's the expected changes for VARIABLES if string*n and zstring*n and wstring*n passed to byref as string is allowed to be modified: When the starting buffer is not large enough to handle such a assignment (passin...

here is the relevant part. The C compiler is gcc 13.1.1 (clang doesn't work). What version is the fbc bootstrap compiler? Normally I would not copy over the bootstrap compiler to ./bin, but maybe I don't understand what steps you are following or what script this is from. ... nevermind, I looked mo...

I will come back to this code when bugs #1 and #2 are fixed. I have fixes for bug #1 and #2 which I should be able to push out today. I started to explore enabling copyback for string*n and zstring*n passed to byref as string. And got side tracked by already existing and unsafe combinations of impl...

Maybe a compiler warning message is missing here: (Z|W)STRING*N argument not compatible with a BYREF AS STRING parameter, but only with a BYVAL AS STRING parameter. ... which maybe makes a case for the "new" STRING*n being given a different name, as I suggested when I first commented on t...

Compatibility between old/new STRING*N (apart from remaining bugs) I will keep pushing forward to solve the bugs you posted and continue with the idea of initializing and padding spaces. But this is also interesting to me: When upgrading existing codes (to also compile and run with fbc version 1.20...

Sorry for stepping in-- When try to compile below examples,the recent fbc64.exe version 1.2.0 crashed during compiling under windows 10 64bit,but fbc64 version 1.1 is fine. https://github.com/jepalza/FB_DOOM_LIKE I have no idea what happed,so just report here. Cause is related to bug #798 fbc's rec...