[haiku-development] Re: Haiku R1/alpha updating (was decisions)
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 08 Aug 2008 10:30:53 +0200 CEST
Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> Agreed. I'd even say that MAP_COPY is superfluous, since MAP_PRIVATE
> should
> imply that behavior -- at least I think it's pretty inconsistent ATM.
Looking at the specs, it's definitely allowed to do that; the behaviour
in this regard is just mentioned to be "unspecified".
The only reason for MAP_COPY would be that it's more expensive than a
MAP_PRIVATE that always shows the current data in an unchanged page.
Bye,
Axel.
- Follow-Ups:
- References:
- [haiku-development] Re: Haiku R1/alpha updating (was decisions)
- From: Ingo Weinhold
Other related posts:
- » [haiku-development] Re: Haiku R1/alpha updating (was decisions)
- » [haiku-development] Re: Haiku R1/alpha updating (was decisions)
- » [haiku-development] Re: Haiku R1/alpha updating (was decisions)
- » [haiku-development] Re: Haiku R1/alpha updating (was decisions)
- » [haiku-development] Re: Haiku R1/alpha updating (was decisions)
- » [haiku-development] Re: Haiku R1/alpha updating (was decisions)
- » [haiku-development] Re: Haiku R1/alpha updating (was decisions)
- » [haiku-development] Re: Haiku R1/alpha updating (was decisions)
- [haiku-development] Re: Haiku R1/alpha updating (was decisions)
- From: Ingo Weinhold