PureBasic Forums - English

If you reallocate to a larger block, there is no garbage added. The new
added memory will be initialized to 0.
Sorry, my mistake

And you should always expect a pointer change when reallocating memory.
(see the Help file for an example)
Agreed, but the idea there was only that if the pointer ...

Using ReAllocateMemory() preserves the contents of the old memory space. It may seem that it is not working in several situations:

- You reallocate a large amount of memory to a smaller amount. Since PB preserves the memory's contents, the location of your data in the system's address space will ...

I prefer PureBasic's current IDE to any and all alternatives.

This is 2004, who doesn't have DirectX 7 ?

What if the compiler retained the ability to successfully compile old code with new updates? For example, each source file includes the PB version number that the code was intended to be compiled with, and the compiler then uses the syntax, functions, and abilities of that particular version to ...

This one is more fun :D
I ran into strangeness with GetKeyState() when performed in the loop, it seemed to give false values.. So I just keep track of the key states myself so that when the program is done, the keys are returned to the state that they were in before the program started.

Global LED ...

Any language has (or ..should.. have) a modulus operator, and PB is no exception. It is documented in the ..you guessed it.. "Variables, Types, and Operators" page. Wow, imagine that.

I like the idea, but the constants would have to go along with PB's constant naming convention better. #PB_GadgetAttribute_FontName, for example.

GedB, you must not have understood his question. He wants to know if pointers to data elements will be valid after a given amount of time. For instance, let's say your program creates a pointer to a variable at address 0xF981B34. After your program has been running a while, something happens that ...

Isn't it like always 512?

I think many people don't know about that flag

My comments were directed towards the people pushing for a book for PB. I just don't see it being useful at all at this time in PB's development. I in no way meant to suggest that the documentation itself should not be kept up to date.

A big problem with having a physical book written is that PB changes constantly. That is, it changes much more often than professional languages such as VB, and there isn't as much of an emphasis on keeping old programs' code intact(not a bad thing for an evolving language like PB). With each new PB ...

Just curious

"Objects" being anything you can create or open in PB this way, such as windows, gadgets, images, files, memory, etc.