17.04.2026, 23:12
Hi Stanley,
thanks for your post. I have seen some very advanced code you posted and i really appreciate that!.
But in this case i must say you misunderstood a few things.
What makes you think STRING and WSTRING are not supported? I support ASCIIZ, WSTRINGZ, STRING and WSTRING, i don´t support fixed length strings like ... as STRING * x and ... WSTRING * x, i support U8, I64, F64 as well.
There is a lot of working PowerBASIC code out there, so having a compiler, which can compile this code without a major re-write, makes sense to me. 64 bit code, as you know, is a bit different and requires adjustments. So why not make existing 32 bit work again and then port it to 64 bit (without too much effort)? My work can do 64 bit!
FreeBASIC has it´s own (dynamic) string implementation, which cannot be used for COM. COM needs OLE-strings (like PB´s and mine). You can do COM in FreeBASIC though. I tried FreeBASIC myself, i even contributed a little bit to integrate (dynamic) WSTRINGs (mostly José´s work) and some other minor things. What drove me crazy about FreeBASIC was type casting and variable type hell (just like in C - typedef has it´s pros and cons).
I know, but i didn´t write code for inheritance yet.
Having a constructor and destructor (like in FreeBASIC and C and ...) may be nice, but nothing prevents you from coding it yourself. You would have to write code for a constructor and destructor anyway, if needed. So where is the major difference?
My IDE has been there for years, so why not use it for something new? Especially because it makes it easier for me (compared to any third party tool) to debug and control what´s going on
??? what for ?
Sorry, to me it seems you had a very quick read of my posts without even downloading or trying it. I accept all kinds of substantiated critic, but please don´t judge on a quick look!
thanks for your post. I have seen some very advanced code you posted and i really appreciate that!.
But in this case i must say you misunderstood a few things.
What makes you think STRING and WSTRING are not supported? I support ASCIIZ, WSTRINGZ, STRING and WSTRING, i don´t support fixed length strings like ... as STRING * x and ... WSTRING * x, i support U8, I64, F64 as well.
There is a lot of working PowerBASIC code out there, so having a compiler, which can compile this code without a major re-write, makes sense to me. 64 bit code, as you know, is a bit different and requires adjustments. So why not make existing 32 bit work again and then port it to 64 bit (without too much effort)? My work can do 64 bit!
FreeBASIC has it´s own (dynamic) string implementation, which cannot be used for COM. COM needs OLE-strings (like PB´s and mine). You can do COM in FreeBASIC though. I tried FreeBASIC myself, i even contributed a little bit to integrate (dynamic) WSTRINGs (mostly José´s work) and some other minor things. What drove me crazy about FreeBASIC was type casting and variable type hell (just like in C - typedef has it´s pros and cons).
Quote:An object is just an allocated UDT.
Inheritance is just adding another UDT in the UDT and using the added UDT to call its procedures.
I know, but i didn´t write code for inheritance yet.
Having a constructor and destructor (like in FreeBASIC and C and ...) may be nice, but nothing prevents you from coding it yourself. You would have to write code for a constructor and destructor anyway, if needed. So where is the major difference?
My IDE has been there for years, so why not use it for something new? Especially because it makes it easier for me (compared to any third party tool) to debug and control what´s going on
Quote:Also, you need a ReAlloc function.
??? what for ?
Sorry, to me it seems you had a very quick read of my posts without even downloading or trying it. I accept all kinds of substantiated critic, but please don´t judge on a quick look!