Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Why programming is hard?
Message
De
26/07/2006 22:30:25
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Programmation Orientée Object
Versions des environnements
OS:
Windows XP SP1
Network:
Windows 2003 Server
Database:
Visual FoxPro
Divers
Thread ID:
01140270
Message ID:
01140552
Vues:
16
>>Wouldn't that be a typical "deadlock" situation, using computer terms? I mean, if each one waits for the other one to take the first step...
>
>Yes, I guess it is. Do you know solution for a deadlock? <g>

Humm, in computer science, a deadlock occurs when each of two processes wait for the other one to release some resource. Perhaps that is where the analogy ends... Or perhaps it doesn't.

One solution (in computer science) seems to be to always lock resources in a specified order, and to unlock them in the reverse order. Note that in many systems, once a deadlock occurs not much can be done; the solution is to avoid the deadlock in the first place. "Nevertheless, since there is no general solution for deadlock prevention, each type of deadlock must be anticipated and specially prevented." (Wikipedia)

For human relations, well, the solution would be NOT to wait the other side to take the first step. Waiting is precisely the cause of the deadlock. If the other side doesn't want to be reasonable, well, there is not much you can do, but at some moment you must try.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform