🚀 go-pugleaf

In article <232@dbase.UUCP> drc@dbase.UUCP (Dennis Cohen) writes:
>In article <3819@ecsvax.UUCP>, wmcb@ecsvax.UUCP (William C. Bauldry) writes:
>> 
>> 
>>  Having little printed resources available now...
>> Since addresses have jumped to 32 bits how is the master
>> pointer handled (bad pun)? The old format stole the high
>> order byte for flags, i.e. handle locked, etc. Could
>> some kind soul enlighten me and raise my consciousness
>> to the new type ?
>> thanks in advance.
>> 
>> Bill
>
>You address it the same way you did in the past (if you followed Apple's rules)
>and call routines for HLock, HUnlock, HGetState, HSetState, HSetRBit, HGetRBit,
>etc.  If you want to munge the bits yourself, let your customers beware that
>the software you produce will almost surely break soon (and it AIN'T Apple's
>fault, but is yours).
>
>Dennis Cohen
>Ashton-Tate Glendale Development Center
>dBASE Mac Development Team

The writing between the lines here is that we STILL use those bits in the 
master pointers (i.e. the Memory Manager is still limited to 24-bit addressing
even on a Mac II). 32-bit addressing cannot be performed under the Mac OS (as
opposed to something like A/UX) without scrapping the current methods of
tagging memory blocks and using something that stores those bits elsewhere.

Keith Rollin
Sales Tech Support
Apple Computer

Disclaimer: Any rumours I spread I got somewhere else first.