CompuServe Messages

Release numbers?

    23-Oct-92 14:49:40
Sb: #29475-Release numbers?
Fm: Syndesis 76004,1763
To: Dean Brown 72250,2677
I made very few changes to my code, and now it runs on the A4000. There were a few dusty places in the code that were still passing a "NULL" as the memory requirements in AllocRemember() calls. I changed them to MEMF_PUBLIC. Not having an A4000 at my side, I had to make several other changes at the same time, so I'll never know if that made a difference. I also made the GetScreenData() changes described in other messages. The "out of memory" message I saw was from *our* code, not WB. The function that performed the GetScreenData() was a void function, so it couldn't have been returning the "out of memory" error, I think it was the AllocRemember(). Which leads me to a more general question looming in my mind. By virtue of cut-and-paste editing, there's a lot of places in our code that ask for MEMF_PUBLIC memory for general, private allocations. I should change these to MEMF_ANY in hope for a future version of the OS that might give MMu protection of any non-public and non-chip requests. Are there other considerations I should re-think with the advent of the A4000, in regards to the MEMF_ flags?