examples:
Code: Select all
ChunkSize = Val(ChunkSizeText)
If AllocateMemory(0, ChunkSize) = 0Code: Select all
ReadData(MemoryID(), DataSize)Code: Select all
WriteData(MemoryID(), DataSize)memory command changes since last version..
memory command changes since last version..
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:
examples:
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 ...
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 ...
My avatar is a small copy of the 4x1.8m image I created and exposed at 'Le salon international du meuble à Paris' january 2004 in Matt Sindall's 'Shades' designers exhibition. The original laminated print was designed using a 150 dpi printout.
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.
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.
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?
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?
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
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