The string must always be null terminated. Otherwise, it won't work with all string functions, because string functions expect a null character. Not necessarily. The only information needed by the string function is where the string ends: and that information can be provided by putting a zero at th...

Well, using generics you wouldn't have to dig deeply in the language, all you have to do is to include a simple header file. In C++ (that uses generics), if you want to implement a linked list, or an associative array, you can dig in the language, but you don't have to if you don't want. Declaring a...

This example should draw a line on the screen, over the windows already displayed

Actually, there are two possibilities: one is implementing generics, the other is implementing only some containers (dictionaries and lists, for example) as part of the language. Both solutions have advantages and disadvantages: generics and templates is surely more versatile, although more like c++...

Do you suggest to implement it using hash table or binary tree?

By the way, a ZSTRING doesn't have that issue: its length is exactly as declared, inside a type Yes, but the maximum number of useful characters for the user is 'length - 1' (because of the mandatory terminal character). I made some tests: it is actually possible to use all the characters, removing...

What is the point of using a FIELD parameter when you can already use ZSTRING? It's literally just one character to add. Maybe in QB mode the strings inside a TYPE should be treated as ZSTRINGS, just to make UDT compatible with QB (in case one is porting a program that was supposed to read a file wi...

At this point, I doubt: changing that would break too much existing FreeBasic code.

By the way, a ZSTRING doesn't have that issue: its length is exactly as declared, inside a type

1) No, I have just tested on DosBox, FreeBasic returns an error message if there is no DPMI extender. By the way, is the file CWSDPMI.EXE either in the FreeBasic directory, or in another directory in the search path, the program written in FreeBasic (and the compiler itself) can invoke it, loading a...

D.J.Peters wrote: ↑Jun 18, 2022 8:39 @angros47 can you share the ready to use compiled lib for DOS here ?

Here it is:
https://www.mediafire.com/file/0apraqvl ... bco.o/file

The reason is likely that pointers are supposed to be already aligned, since a pointer can refer to any size. If you need to align them "by hand" you aren't using them in the way they are supposed to be used

Being a proprietary software, it is not part of FreeDos

It should be available here: https://winworldpc.com/product/microsoft-mouse/

Have you tried using a different driver? Like the Microsoft drivers for Ms-DOS?

From what you said, it seems that the issue is in CTMOUSE (if with other drivers the mouse works you might have to file a bug report)

Again, it is not a bug. It is how FreeBasic is supposed to act in the old QBASIC functions could be invoked only inside expression, so an attempt to write "ShowNum(5)" would have caused an error, it should have been a sub to work In C, on the other hand, it's possible to use a function as ...

The behavior is indeed correct: to achieve the result 5 and 10 you should use: dim i as integer i=ShowNum(5)+ShowNum(10) in fact, in FreeBasic a FUNCTION can also be invoked as if it were a SUB (that is not possible in QBASIC, but is possible in C): also, while in C a command must have its parameter...