Tuesday, July 23, 2019

Digest for comp.lang.c++@googlegroups.com - 5 updates in 5 topics

aminer68@gmail.com: Jul 23 03:03PM -0700

Hello,
 
 
Read again, i correct about: Shared memory or message passing ?
 
 
Shared memory or message passing ?
 
Shared memory allows maximum speed and convenience of communication, as it can be done at memory speeds when within a computer. Shared memory is faster than message passing.
 
Please read the following about a paper of the following International Conference On Principles Of Distributed Systems, it says the following:
 
"We observe that communication overhead of message passing can often outweigh its benefits"
 
 
Read here to noticed it:
 
https://link.springer.com/chapter/10.1007/978-3-319-03850-6_7
 
 
Thank you,
Amine Moulay Ramdane.
aminer68@gmail.com: Jul 23 02:55PM -0700

Hello,
 
 
Shared memory or message passing ?
 
Shared memory allows maximum speed and convenience of communication, as it can be done at memory speeds when within a computer. Shared memory is faster than message passing.
 
Please read the following about a paper of the following International Conference On Principles Of Distributed Systems, it says the following:
 
"Communication overhead of message passing can often outweigh its benefits"
 
 
Read here to noticed it:
 
https://link.springer.com/chapter/10.1007/978-3-319-03850-6_7
 
 
Thank you,
Amine Moulay Ramdane.
ram@zedat.fu-berlin.de (Stefan Ram): Jul 23 11:49AM

>in un debugger, puoi vedere le funzioni che vengono chiamate...
 
Beh, secondo me, non è il debugger (come strumento) che
conta, ma la mentalità di debug. La capacità di avere l'idea
di debug in primo luogo. Se questo è dato, allora si può
usare anche »<<« per il debug.
Rosario19 <Ros@invalid.invalid>: Jul 23 09:28AM +0200

On Tue, 16 Jul 2019 14:28:23 +0200, Soviet_Mario wrote:
 
>[] / delege [], but further elaboration, which assigns
>content, requires it, or even reallocation.
 
>So I was asking about the behaviou
 
in un debugger, puoi vedere le funzioni che vengono chiamate...
in generale ogni obj non tuo, ha propri costruttori e tutto va bene
no leak ecc
 
se ci sono object tuoi, che abbisognano memoria dinamica allora devi
stare attento... per quel che mi riguarda in qualche esercizio la cosa
che avrei fatto, per chiarire il fatto della memoria, è stato
(ri)costruire malloc free e new e vedere come la memoria veniva
utilizzata
nei obj che avevo costruito, in particolare vedere se c'erano leak
Christian Gollwitzer <auriocus@gmx.de>: Jul 23 08:29AM +0200

Am 22.07.19 um 22:56 schrieb Vir Campestris:
> And I'll leave you to worry about whether 07/04/19 was the national
> holiday this year in the US, the 7th April this year in most of the
> world, and quite possibly 19th April 2007 if you are in China.
 
That was discussed before. It depends on the cultural background of the
writer. He could mark ambiguous dates and check them manually, but in
principle the problem has no solution.
 
Christian
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com.

No comments: