Procedure Test(Const *HugeString)
; do something without unintentionally changing the content
EndProcedure
3. tbc?
Just because it worked doesn't mean it works. PureBasic 6.04 (x86) and <latest stable version and current alpha/beta> (x64) on Windows 11 Home. Now started with Linux (VM: Ubuntu 22.04).
I know that these are different strings.
Maybe it is because it looks nicer (only) or maybe I do to much FreePascal at the moment.... (Sorry, if this is bothering you)
Just because it worked doesn't mean it works. PureBasic 6.04 (x86) and <latest stable version and current alpha/beta> (x64) on Windows 11 Home. Now started with Linux (VM: Ubuntu 22.04).
Not bothering me at all, I was simply curious why you wanted to replace the way PB has defined constants for over 20 years with the const keyword?
I see the use for parameters, basically a read-only pointer, but I don't see why you'd want to change # to const.
Quin wrote: Sat May 17, 2025 4:34 pm
..., but I don't see why you'd want to change # to const.
Well, I never requested a replacement. I thought of it as an addition to the language.
BTW: (I don't like changes that make existing code invalid/uncompilable and I know, that sometimes it can't be avoided.)
Just because it worked doesn't mean it works. PureBasic 6.04 (x86) and <latest stable version and current alpha/beta> (x64) on Windows 11 Home. Now started with Linux (VM: Ubuntu 22.04).
Ah, just another way to define constants, gotcha.
I personally don't really see much of a use for it, but it would work. As a parameter modifier it could be really nice though, along with Out.