[DELETED} TInterlocked and deadlocks

[DelphiUdIT 255]

TOPIC DELETED - SORRY

Edited 16 hours ago by DelphiUdIT

[Anders Melander 2040]

3 hours ago, DelphiUdIT said:

But no DEADLOCK.

Please; Words have meaning. Deadlock likely doesn't mean what you think it means.

 

- and, the example you gave doesn't prove anything.

 

My suggestion to someone venturing into multi-threading (and I don't know if that description fits you or not) would be that, instead of doing experiments to try and understand concurrency, they first read a lot of literature about the topic *). Concurrency is an extremely complex and broad problem space and the knowledge one get from random experiments is worth very little. Experiment a later - once there's a better understanding of the topic.

 

*) The first thing to learn is to identify the most common concurrency problem patterns - and their various solutions. I'm sure someone has written a Delphi book about that stuff.

[eivindbakkestuen 55]

5 hours ago, DelphiUdIT said:

Although not explicitly described (only BYTE, WORD, and DWORD are defined), it can be assumed that QWORDs in the X64 environment are also part of this guarantee.

Assumptions like this is like building a skyscraper on quicksand. 😄

[DelphiUdIT 255]

19 minutes ago, eivindbakkestuen said:

Assumptions like this is like building a skyscraper on quicksand. 😄

In reality that (quadwords automatic lock) is written in a little paragraph In Intel manual (I read that after). So this is rigth. 

Edited 16 hours ago by DelphiUdIT

[DelphiUdIT 255]

@Anders Melander

You are right, it is a no sense to write something about those argument here.

I delete the post.

Sorry for that.