PureBasic Forums - English

If you read that file with the RGB values at runtime there is no way to define constants. Constants are not there anymore during runtime. They are replaced with their value before compiling. What you can do however is using Maps. ; Using Longs here as they are big enough for RGB values Global NewMap...

There is no other way except with macros. Constants and macros are processed in the pre-compiler. And I don't know what API do you mean. Purebasic has no API you could use. And even Assembler will not help, especially if you use the C-Backend. :wink: Can you please explain in more detail what you wa...

And finally, even having a large *Memory is not of big help, because with WriteData(), the maximum buffer size is 2GB. I got the PB message [ERROR] WriteData(): The maximum buffer size is 2GB. PureBasic has obviously still barriers to 2GB... As far as I know the limit is not Purebasic but your oper...

I think unlimit means a meaningful range. So more than 64 kb and less than 1 mb with which the string management can also process well. Anything in the gigabyte range should be processed directly with memory areas as ArrayOfChar. <...> Actually your code does nothing meaningful. I mean, yes, the me...

As you can see in his signature he has 64 GiB of RAM. This does not mean it is free but at least it is there. :wink: However this only works if the program gets compiled with 64 bit compiler. I tested it on my system where I've got 47 GiB of free RAM but the program crashed before it had allocated a...

I just tried something similar with GNU grep and needed 1 minute and 24 seconds for finding a small string in a 19 GiB file which means that it was able to search through it with ~230 MiB/s. That was on a quite fast PC (see my profile). Interestingly the CPU time needed was just 2,8 seconds for sear...

And a bit more detail: You don't get an identifier, you get a pointer from these commands. And a pointer directly points to a memory region. If you enlarge that memory it might not have enough space behind it to be enlarged in place. Instead your operating system just allocates a completely fresh me...

It's simple: You can't.

Dafuq is this?

An Unicode array of the dimensions (250000, 1949) has 487,501,950 entries and allocates 975,003,900 bytes (~930 MiB) of memory. If you make it bigger your operating system may has trouble to simply enlarge the memory when it can not find enough free memory directly behind the currently allocated spa...

Just use the right character directly in your code: It's the first time i have try :wink: But the problem, it's when i paste this character i don't know why the PB IDE (v5.73 and 6.0) show a little black square, not the "oe" :shock: I have choose "UTF8" in the menu "File/Fi...

Just use the right character directly in your code:

VB6_to_PBx wrote: ↑Fri Mar 01, 2024 11:45 amthis is what it should calculate :
real Solution: x=129.6025714796 , y=10100

No. That's still just one of infinitely many solutions.

From my point of view it would be better to leave the current procedure as it is and have an additional procedure with the word locale inside the procedure name like FormatNumberLocale . That's a valid option. The we could also add stuff like FormatCurrencyLocale and ParseNumberLocale and similar t...

The function `FormatNumber` uses static default values for the 1000s separator and the decimal point. Instead it would make way more sense to respect the locale settings. FormatNumber does allow you to specify what to use FormatNumber(Number.d [, NbDecimals [, DecimalPoint$ [, ThousandSeparator$]]]...