angros47 wrote: ↑Feb 28, 2024 17:23 I wonder, will the update fix this bug too?
viewtopic.php?t=31753

Changes to string*n won't fix that bug directly, but would allow the possibility to fix that bug.

VANYA wrote: ↑Feb 28, 2024 3:58 Will this change affect null characters in the STRING type? Example:

No change to STRING, therefore no changes to CHR(0) in STRING

Proposed change is for STRING*N only.

'Procptr (member procedure address)' could support a non-member overload operators by using as second argument the user operator signature, in order to resolve the operator overload. Is such a complement expected in the short term ? In the short term, probably can be achieved because it looks to be...

Fundamentally the point of a string is to convey information to a human being. Not to a machine or algorithm? What about control characters and escape sequences? Is not 'zero terminated sequence of bytes' also a kind of format that the the producer and consumer need to agree on? Anyway, going back ...

The only thing I immediately disagree with is the idea that I would slink off. Pretty sure I consistently own up to all my failures. Why? - I think I need to do this first Who is this for? - Me, and hopefully others find it useful. At the moment unfinished existing STRING*N feels like it is in my wa...

So top down images (with negative height) ARE supported ? :D ha, I did not know. Turns out yes, negative height flips the image. ( I really was hoping for someone to dig through this. I don't even know what is common or normal with this format) RLE not supported though. So only uncompressed formats.

I have a question: would the null terminator byte be removed only in fixed length strings inside an user defined type, or in all fixed length strings? It would make a difference in case of arrays of fixed length strings (and it would allow to create unions of byte arrays and fixed length strings ar...

Another question: will be possible to use null bytes inside a fixed length string? There are currently several inconsistencies with embedded null bytes depending on type or literal string and if the expression is constant folded at compile time or evaluated at run time. My goal would be to have STR...

Another question: will be possible to use null bytes inside a fixed length string? This would not make any sense as there is no corresponding character to the null (0) byte. Not for printing but still as a null terminator -- in a list of null terminated strings. On windows, REG_MULTI_SZ comes to mi...

There is no support for pointers to fixed length strings. This reminds me of an issue: BYREF/typedefs allow pointers to [Z/W]STRING * N If the data type info were fully tracked (which within the compiler it is currently not), then: - pointer to 'STRING*N' should be 'STRING*N ptr' - pointer to Z'STR...

To change STRING* at this stage is probably going to break a lot of code, although the change you suggest will make it easier to convert QBASIC / GWBASIC programs to Freebasic. [/code] Yes probably going to break some code, but how much I wonder?. fbc sources don't use it. I don't use it. And it's ...

Past month I have been looking in to fb's string datatypes and trying to really get an understanding of where the deficiencies are. And by deficiencies I mean with what we already have, not about missing string types / features. Things like string allocation, temporary string management, safe string...

Here is a rough starting point, though many bits still to add in... Files used with BLOAD/BSAVE First byte of file: &hFD QB BSAVED BLOCK &hFE FB BSAVED BLOCK &h42 Windows Bitmap (&h42 = ASC("B")) For the QB/FB saved block, &hFD and &hFE identify the file as a QB/FB ...

In my opinion, the fbcFindBin function needs to be changed to find this file. You could try building and using a "normal" build of fbc instead of "standalone" See Normal Vs Standalone "normal": where fbc is located in <fbc-root>/bin/fbc.exe "standalone": wher...

freebasic does not reserve "std" for any special use, and there's no support for the std namespace mangling rules But if std c++ name mangling were added, I would probably do like this for syntax: extern "c++" namespace std alias "::std::" '' declarations end namespace ...