An update of some things being worked on... If we are going to make changes to string handling, (for example as discussed in this topic, temporary descriptors), I would like a way to conveniently profile the performance differences instead of having to write custom timing tests. Past couple of weeke...

Hello, when compiling this example using compiler 1.20.0 dated 04/01/2024, it gives the error: Since fbc version 1.20.0, Put# warns then crashes on compilation with an array as data. See posts above. (there are several recent changes regarding the arrays. Maybe : fbc: fix non-index array assignment...

adeyblue has the right idea. An audit will be worthwhile to identify all the junk. Some more aggressive concentrated effort than what we've been doing past several years of incremental reviews. Roadmap: Currently is a union of bug reports + TODO list + needs of developers of large fb projects + requ...

OK, I understand. I agree, this change it would be worthwhile to have some method to do both. When we made the big changes for name lookups we temporarily added a #pragma to allow old name lookup logic. We could do something similar for len/sizeof but to do 1 of 3 things: 1) old behaviour, 2) error ...

I don't think I have much thought about LEN(array) and SIZEOF(array). But even more the use of 'Len(array_name)' which is allowed (for the moment without a note in the documentation) is even more misleading because it actually always returns the value of 'Sizeof(array_element)' ! Yes, I see in compi...

I improved my code (to test the 'Byref' passing/returning to/from a function) without changing the output view: The 2 utility Sub's are transformed into macros and only the two main functions remain in the form of procedures (because, for a most reliable test possible of parameter passing, the veri...

I didn't know that the FB format function was modeled after vbdos Until I seen that comment in the source, I never would have guessed. Proving out FORMAT and PRINT USING is more than I would want to take on right now, otherwise I personally have no objection to changes if the output is more favoura...

@coderJeff I tried hhr suggestion and it seems that he is right, however, I don't know if there are cases where the suggested change would cause a problem. the format function is a complex beast and it seems that it's not finished, I know that it fails the tests with gcc-13.2 and up See the note in...

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...

Otherwise I had already seen another configuration which presents the same behavior: Your example is better for debugging. Thank you. I believe the logic is here: ast-node-arg.bas#L869 1) If we are passing to a byval parameter, then check if there is a constructor that would work (assumption at thi...

I will try to isolate/simplify this abnormal behavior, but it will not be immediate because the code is quite complex. Here is the shortest I found so far. Try fbc-1.10+ with 'SHOW_CHANGE = true|false'. When SHOW_CHANGE=true, fbc-1.10+ assigns the result of CAST() as ROOT ptr to a temporary variabl...

Thank you srvaldez & deltarho

(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...