| From: | Rod Schnell |
| Date: | 30 Aug 2000 at 19:59:04 |
| Subject: | Re: Freeing list with Classact |
> >> MEMF_PUBLIC excludes MEMF_ANY.
> > Really, why's that? I thought MEMF_PUBLIC was intended to be used with
> > memory protection at some time in the future, but wasn't actually used
> > for anything yet.
>
> That's true, Exec.doc says:
>
> MEMF_PUBLIC: Memory that must not be mapped, swapped,
> or otherwise made non-addressable. ALL
> MEMORY THAT IS REFERENCED VIA INTERRUPTS
> AND/OR BY OTHER TASKS MUST BE EITHER PUBLIC
> OR LOCKED INTO MEMORY! This includes both
> code and data.
>
Maybe I'm missing something, but how do you interpret that to mean they're
exclusive? I don't.
> And MEMF_ANY means *any* memory, not restricted like MEMF_PUBLIC. So the
MEMF_ANY basically means use any available memory, it'll use fast if there's
a big enough block, chip if not.
> flags are mutually exclusive, not that it matters, as MEMF_ANY is
> declard to 0L, but semantically it's like setting the font style to
> "PLAIN | BOLD"...
I've allways thought it was more like "BOLD|UNDERLINE". ie, one doesn't turn
the other off. Mind you, MEMF_ANY is the default, so "MEMF_PUBLIC" alone
would have the same effect, I'm just in the habit of putting it there for
clarity. Heh, for what it matters, "NULL" would have the same effect with
the current OS. :)
Regards, Rod