Page 1 of 1
memory command changes since last version..
Posted: Fri May 28, 2004 8:30 pm
by dagcrack
i've seen that some memory functions doesnt work fine (wont compile, gives errors) I wondered if anyone could show me the old and new lines, how they should look like. as I cant get it working and I crashed my pc twice already, trying to sort out this crap.
examples:
Code: Select all
ChunkSize = Val(ChunkSizeText)
If AllocateMemory(0, ChunkSize) = 0
Posted: Fri May 28, 2004 8:38 pm
by GPI
RTFM
The memory-commands have changed.
Posted: Sat May 29, 2004 9:43 pm
by dagcrack
8O
I will
Posted: Sun May 30, 2004 2:16 am
by Hi-Toro
What a friendly reply!
Posted: Sun May 30, 2004 2:21 am
by fweil
dagcrack,
In the past you had to code :
AllocateMemory(0, Length, 0)
...
ReadData(UseMemory(0), Length)
ReadData(MemoryID(), Length)
Now it is more simple :
*MemoryID = AllocateMemory(Length)
...
ReadData(*MemoryID, Length)
That's it ...
Posted: Sun May 30, 2004 8:38 am
by GPI
Hi-Toro wrote:What a friendly reply!
It stand in the Histroy-Log, it stand in the manual and it exist more than one Thread about this.
Posted: Mon May 31, 2004 9:54 am
by thefool
GPI wrote:Hi-Toro wrote:What a friendly reply!
It stand in the Histroy-Log, it stand in the manual and it exist more than one Thread about this.
yeah. but still a non-friendly reply
Posted: Mon May 31, 2004 12:33 pm
by GPI
thefool wrote:yeah. but still a non-friendly reply
Maybe, but it give a solution (look at the manual).
Posted: Mon May 31, 2004 1:51 pm
by thefool
yes, its right that it was very clearly in the list of changes. Easy to find in the manual, and also easy to find posts about it in this forum.
It was a mistake to create this thread, but why answer unfriendly just because he made a mistake?
i hope you see the point. But yes, you answered his question.
Posted: Mon May 31, 2004 11:56 pm
by batcherx
Why wasn't the new simplified AllocateMemory command called AllocateMemoryx ?
How many old script got broken or had to be changed, or do people throw away their scripts after compilation?
For new PB users like me it's no problem. Howerver, for seasoned PBer it must have been unwelcomed.
As a newbie do the PB powers-that-be often introduce such radical changes?
Posted: Tue Jun 01, 2004 12:07 am
by Dare2
Hi batcherx.
I don't think this is an ongoing thing.
As I understand it, in order to get PB capable of some new tricks, this and the next few sub-releases might cause some big changes. Sort of like MS breaking away from VB for VB.NET.
I also understand it that with PB, things will be stable after the (needed) rewrites.
Adding duplication, eg, AllocateMemory and AllocateMemoryX can lead to less efficiencies, hence the clean break.
You can run more than one PB version. So old code can still be compiled using an older version. Freak explains this somewhere, I just couldn't find the post for you.
The changes are welcome, IMO, as they will open new doors for PB users and the old can still be maintained and etc using older versions.
All of the above is not official, just how I understand this particular series of releases