Re: Memory mapping: MAP_PRIVATE and msync()

Liste des GroupesRevenir à cl c  
Sujet : Re: Memory mapping: MAP_PRIVATE and msync()
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.lang.c
Date : 09. Apr 2024, 03:52:48
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <uv271f$3r9k2$4@dont-email.me>
References : 1 2 3 4
User-Agent : Pan/0.155 (Kherson; fc5a80b8)
On Mon, 8 Apr 2024 12:14:30 +0100, bart wrote:

... how did you manage to figure out the meanings and
order of the parameters in order to be able to write those comments?

I read the docs.

If you have 1000s of calls to such functions, will you have those
comments plastered everwhere?

Yes.

In a language with proper named/keyword arguments, you don't need to
remember the order.

True. I take advantage of that--and defaults for omitted arguments--in
Python.

But there are people in this noisegroup who don’t like me mentioning that.

Date Sujet#  Auteur
7 Apr 24 * Memory mapping: MAP_PRIVATE and msync()11pehache
7 Apr 24 +* Re: Memory mapping: MAP_PRIVATE and msync()6pehache
7 Apr 24 i+- Re: Memory mapping: MAP_PRIVATE and msync()1pehache
8 Apr 24 i`* Re: Memory mapping: MAP_PRIVATE and msync()4Lawrence D'Oliveiro
8 Apr 24 i +- Re: Memory mapping: MAP_PRIVATE and msync()1Kaz Kylheku
8 Apr 24 i `* Re: Memory mapping: MAP_PRIVATE and msync()2bart
9 Apr 24 i  `- Re: Memory mapping: MAP_PRIVATE and msync()1Lawrence D'Oliveiro
7 Apr 24 `* Re: Memory mapping: MAP_PRIVATE and msync()4Lew Pitcher
7 Apr 24  `* Re: Memory mapping: MAP_PRIVATE and msync()3pehache
8 Apr 24   `* Re: Memory mapping: MAP_PRIVATE and msync()2pehache
8 Apr 24    `- fu2 is fne (Was: Memory mapping: =?UTF-8?Q?MAP=5FPRIVATE=20and=20msync=28=29?=)1Kenny McCormack

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal